ZXG10 iBSC

Base Station Controller

Performance Counter Reference

Version: V6.20.71

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 2013 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. 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. Additionally, the contents of this document are protected by

Revision History
Revision No. R1.7 Revision Date 20130425 Revision Reason Modification of the following counters: C901190032, C901190033, C901200032, C901200033. R1.6 20130228 Modification of the following counters: C900060053 R1.5 20121126 Modification of the following counters: C901070007, C901070014, C901070021, C901070028,

C901070035, C901070042, C901070049 R1.4 20120912 Modification of the following counters: C902270018C902270020, C902270023C902270032,

C900040003, C900040011, C901170054, C901180054 R1.3 R1.2 R1.1 R1.0 20120726 20120229 20110930 20110730 Updated to V6.20.713d Updated to V6.20.712b Updated to V6.20.711c First edition

Serial Number: SJ-20110531095035-015 Publishing Date: 2013-04-25 (R1.7)

SJ-20110531095035-015|2013-04-25 (R1.7)

ZTE Proprietary and Confidential

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-9 2.4 C900040003 Number of GPRS DL TBF release due to T3191 Timeout ............... 2-10 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-13 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-14 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 T3191 Timeout............ 2-16 2.13 C900040012 Number of EGPRS DL TBF forcing release by control plane ......... 2-17 2.14 C900040013 Number of EGPRS DL TBF release due to instance suspension ..... 2-18 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-20 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-23 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

2.26 C900040025 Number of GPRS UL signaling TBF establishment ....................... 2-25 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 2.54 C900040053 Number of discarded EGPRS DL signaling LLC frames due to life time expiration........................................................................................... 2-41 2.55 C900040054 Number of discarded EGPRS DL signaling LLC frames due to 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-62 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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.83 C900040082 Number of DL RLC pending blocks in CS2 on PDTCH.................. 2-67 2.84 C900040083 Number of DL RLC pending blocks in CS3 on PDTCH.................. 2-68 2.85 C900040084 Number of DL RLC pending blocks in CS4 on PDTCH.................. 2-69 2.86 C900040085 Number of DL RLC NACK blocks in CS1 on PDTCH .................... 2-70 2.87 C900040086 Number of DL RLC NACK blocks in CS2 on PDTCH .................... 2-71 2.88 C900040087 Number of DL RLC NACK blocks in CS3 on PDTCH .................... 2-72 2.89 C900040088 Number of DL RLC NACK blocks in CS4 on PDTCH .................... 2-73 2.90 C900040089 Number of DL RLC new blocks in CS1 on PDTCH........................ 2-74 2.91 C900040090 Number of DL RLC new blocks in CS2 on PDTCH........................ 2-75 2.92 C900040091 Number of DL RLC new blocks in CS3 on PDTCH........................ 2-76 2.93 C900040092 Number of DL RLC new blocks in CS4 on PDTCH........................ 2-77 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.96 C900040095 Number of UL RLC pending blocks in CS2 on PDTCH.................. 2-79 2.97 C900040096 Number of UL RLC pending blocks in CS3 on PDTCH.................. 2-80 2.98 C900040097 Number of UL RLC pending blocks in CS4 on PDTCH.................. 2-81 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.101 C900040100 Number of UL RLC NACK blocks in CS3 on PDTCH................... 2-84 2.102 C900040101 Number of UL RLC NACK blocks in CS4 on PDTCH................... 2-85 2.103 C900040102 Number of UL RLC new blocks in CS1 on PDTCH...................... 2-86 2.104 C900040103 Number of UL RLC new blocks in CS2 on PDTCH...................... 2-87 2.105 C900040104 Number of UL RLC new blocks in CS3 on PDTCH...................... 2-88 2.106 C900040105 Number of UL RLC new blocks in CS4 on PDTCH...................... 2-89 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 of channel allocation due to UL TBF establishment .............................................. 2-93 2.113 C900040112 Number of GPRS DL TBF resource reallocation requests due to LLC transmission............................................................................................ 2-94

IV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

2.114 C900040113 Number of GPRS DL TBF resource reallocation failure of channel allocation due to 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-97 2.117 C900040116 Number of EGPRS DL TBF resource reallocation requests due to UL TBF establishment ................................................................................ 2-98 2.118 C900040117 Number of EGPRS DL TBF resource reallocation failure due to UL TBF establishment .................................................................................... 2-99 2.119 C900040118 Number of EGPRS DL TBF resource reallocation requests due to LLC transmission ........................................................................................ 2-99 2.120 C900040119 Number of EGPRS DL TBF resource reallocation failure due to LLC transmission ..........................................................................................2-100 2.121 C900040120 Number of GPRS UL TBF establishment requests ....................2-101 2.122 C900040121 Number of GPRS UL TBF establishment failure due to database allocation failure ............................................................................................2-102 2.123 C900040122 Number of GPRS UL TBF resource reallocation requests due to DL TBF establishment................................................................................2-103 2.124 C900040123 Number of GPRS UL TBF resource reallocation failure of channel allocation due to DL TBF establishment..............................................2-104 2.125 C900040124 Number of GPRS UL TBF resource reallocation requests due to LLC transmission .......................................................................................2-105 2.126 C900040125 Number of GPRS UL TBF resource reallocation failure of channel allocation due to LLC transmission .....................................................2-105 2.127 C900040126 Number of GPRS UL TBF resource reallocation requests for resource request ...........................................................................................2-106 2.128 C900040127 Number of GPRS UL TBF resource reallocation failure due to database allocation failure for resource request ...............................................2-107 2.129 C900040128 Number of EGPRS UL TBF establishment requests...................2-108 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 to DL TBF establishment................................................................................ 2-110 2.132 C900040131 Number of EGPRS UL TBF resource reallocation failure of channel allocation due to DL TBF establishment.............................................. 2-110 2.133 C900040132 Number of EGPRS UL TBF resource reallocation requests due to LLC transmission ....................................................................................... 2-111 2.134 C900040133 Number of EGPRS UL TBF resource reallocation failure of channel allocation due to LLC transmission ..................................................... 2-112 2.135 C900040134 Number of EGPRS UL TBF resource reallocation requests for resource request ........................................................................................... 2-113
V SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

2.136 C900040135 Number of EGPRS UL TBF resource reallocation failure due to database allocation failure for resource request ............................................... 2-114 2.137 C900040136 Average number of available PDCH.......................................... 2-114 2.138 C900040137 Number of forcing conversation dynamic from PDCH to TCH by BSC.............................................................................................................. 2-115 2.139 C900040138 Average Number of PDCH used by TBF in each cell.................. 2-115 2.140 C900040139 Maximum number of used PDCH.............................................. 2-116 2.141 C900040140 Average number of used PDCH................................................ 2-116 2.142 C900040141 Number of GPRS DL TBF establishment requests before T3192 expiration ...................................................................................................... 2-117 2.143 C900040142 Number of GPRS DL TBF establishment using existing DL TBF resource ....................................................................................................... 2-118 2.144 C900040143 Number of GPRS DL TBF establishment requests on PACCH ......................................................................................................... 2-118 2.145 C900040144 Number of GPRS DL TBF establishment requests on CCCH/PCCCH .............................................................................................. 2-119 2.146 C900040145 Number of EGPRS DL TBF establishment requests before T3192 expiration............................................................................................2-120 2.147 C900040146 Number of EGPRS DL TBF establishment using existing DL TBF resource ................................................................................................2-121 2.148 C900040147 Number of EGPRS DL TBF establishment requests on PACCH .........................................................................................................2-122 2.149 C900040148 Number of EGPRS DL TBF establishment requests on CCCH/PCCCH ..............................................................................................2-123 2.150 C900040149 Number of GPRS DL signaling TBF release due to N3105 overflow ........................................................................................................2-124 2.151 C900040150 Number of GPRS DL signaling TBF release due to other reasons.........................................................................................................2-125 2.152 C900040151 Number of GPRS DL signaling TBF forcing release by control plane ............................................................................................................2-125 2.153 C900040152 Number of GPRS DL signaling TBF release due to instance suspension....................................................................................................2-126 2.154 C900040153 Number of GPRS DL signaling TBF release due to inner abnormal.......................................................................................................2-127 2.155 C900040154 Number of EGPRS DL signaling TBF release due to N3105 overflow ........................................................................................................2-128 2.156 C900040155 Number of EGPRS DL signaling TBF release due to other reasons.........................................................................................................2-129 2.157 C900040156 Number of EGPRS DL signaling TBF forcing release by control plane ............................................................................................................2-129

VI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

2.158 C900040157 Number of EGPRS DL signaling TBF release due to instance suspension....................................................................................................2-130 2.159 C900040158 Number of EGPRS DL signaling TBF release due to inner abnormal.......................................................................................................2-131 2.160 C900040159 Number of GPRS UL TBF establishments in release state .........2-132 2.161 C900040160 Number of GPRS UL TBF establishment with existing UL resource .......................................................................................................2-133 2.162 C900040161 Number of GPRS UL TBF establishment requests on PACCH .........................................................................................................2-133 2.163 C900040162 Number of EGPRS UL data TBF establishments on PACCH ......2-134 2.164 C900040163 Number of EGPRS UL TBF establishments in release state .......2-135 2.165 C900040164 Number of EGPRS UL TBF establishment with existing UL resource .......................................................................................................2-136 2.166 C900040165 Number of EGPRS UL TBF establishment requests on PACCH .........................................................................................................2-136 2.167 C900040166 Number of EGPRS UL TBF establishment requests on CCCH/PCCCH ..............................................................................................2-137 2.168 C900040167 Number of dynamic PDCH preemption for CS service................2-138 2.169 C900040168 Number of GPRS UL TBF establishment requests on CCCH/PCCCH ..............................................................................................2-138 2.170 C900040169 Number of GPRS DL TBF establishment requests on PACCH .........................................................................................................2-139 2.171 C900040170 Number of EGPRS DL TBF establishment requests on PACCH .........................................................................................................2-140 2.172 C900040171 Number of GPRS UL TBF establishment requests on PACCH .........................................................................................................2-140 2.173 C900040172 Number of DL RLC pending blocks in MCS1 on PDTCH ............2-141 2.174 C900040173 Number of DL RLC pending blocks in MCS2 on PDTCH ............2-142 2.175 C900040174 Number of DL RLC pending blocks in MCS3 on PDTCH ............2-143 2.176 C900040175 Number of DL RLC pending blocks in MCS4 on PDTCH ............2-144 2.177 C900040176 Number of DL RLC pending blocks in MCS5 on PDTCH ............2-145 2.178 C900040177 Number of DL RLC pending blocks in MCS6 on PDTCH ............2-146 2.179 C900040178 Number of DL RLC pending blocks in MCS7 on PDTCH ............2-147 2.180 C900040179 Number of DL RLC pending blocks in MCS8 on PDTCH ............2-148 2.181 C900040180 Number of DL RLC pending blocks in MCS9 on PDTCH ............2-149 2.182 C900040181 Number of DL RLC NACK blocks in MCS1 on PDTCH...............2-150 2.183 C900040182 Number of DL RLC NACK blocks in MCS2 on PDTCH...............2-151 2.184 C900040183 Number of DL RLC NACK blocks in MCS3 on PDTCH...............2-152 2.185 C900040184 Number of DL RLC NACK blocks in MCS4 on PDTCH...............2-153

VII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

2.186 C900040185 Number of DL RLC NACK blocks in MCS5 on PDTCH...............2-154 2.187 C900040186 Number of DL RLC NACK blocks in MCS6 on PDTCH...............2-155 2.188 C900040187 Number of DL RLC NACK blocks in MCS7 on PDTCH...............2-156 2.189 C900040188 Number of DL RLC NACK blocks in MCS8 on PDTCH...............2-157 2.190 C900040189 Number of DL RLC NACK blocks in MCS9 on PDTCH...............2-158 2.191 C900040190 Number of DL RLC new blocks in MCS1 on PDTCH ..................2-159 2.192 C900040191 Number of DL RLC new blocks in MCS2 on PDTCH ..................2-160 2.193 C900040192 Number of DL RLC new blocks in MCS3 on PDTCH ..................2-161 2.194 C900040193 Number of DL RLC new blocks in MCS4 on PDTCH ..................2-162 2.195 C900040194 Number of DL RLC new blocks in MCS5 on PDTCH ..................2-163 2.196 C900040195 Number of DL RLC new blocks in MCS6 on PDTCH ..................2-164 2.197 C900040196 Number of DL RLC new blocks in MCS7 on PDTCH ..................2-165 2.198 C900040197 Number of DL RLC new blocks in MCS8 on PDTCH ..................2-166 2.199 C900040198 Number of DL RLC new blocks in MCS9 on PDTCH ..................2-167 2.200 C900040199 Number of UL RLC pending blocks in MCS1 on PDTCH ............2-168 2.201 C900040200 Number of UL RLC pending blocks in MCS2 on PDTCH ............2-169 2.202 C900040201 Number of UL RLC pending blocks in MCS3 on PDTCH ............2-170 2.203 C900040202 Number of UL RLC pending blocks in MCS4 on PDTCH ............2-171 2.204 C900040203 Number of UL RLC pending blocks in MCS5 on PDTCH ............2-172 2.205 C900040204 Number of UL RLC pending blocks in MCS6 on PDTCH ............2-173 2.206 C900040205 Number of UL RLC pending blocks in MCS7 on PDTCH ............2-174 2.207 C900040206 Number of UL RLC pending blocks in MCS8 on PDTCH ............2-175 2.208 C900040207 Number of UL RLC pending blocks in MCS9 on PDTCH ............2-176 2.209 C900040208 Number of UL RLC NACK blocks in MCS1 on PDTCH...............2-177 2.210 C900040209 Number of UL RLC NACK blocks in MCS2 on PDTCH...............2-178 2.211 C900040210 Number of UL RLC NACK blocks in MCS3 on PDTCH ...............2-179 2.212 C900040211 Number of UL RLC NACK blocks in MCS4 on PDTCH ...............2-180 2.213 C900040212 Number of UL RLC NACK blocks in MCS5 on PDTCH...............2-181 2.214 C900040213 Number of UL RLC NACK blocks in MCS6 on PDTCH...............2-182 2.215 C900040214 Number of UL RLC NACK blocks in MCS7 on PDTCH...............2-183 2.216 C900040215 Number of UL RLC NACK blocks in MCS8 on PDTCH...............2-184 2.217 C900040216 Number of UL RLC NACK blocks in MCS9 on PDTCH...............2-185 2.218 C900040217 Number of UL RLC new blocks in MCS1 on PDTCH ..................2-186 2.219 C900040218 Number of UL RLC new blocks in MCS2 on PDTCH ..................2-187 2.220 C900040219 Number of UL RLC new blocks in MCS3 on PDTCH ..................2-188 2.221 C900040220 Number of UL RLC new blocks in MCS4 on PDTCH ..................2-189 2.222 C900040221 Number of UL RLC new blocks in MCS5 on PDTCH ..................2-190

VIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

2.223 C900040222 Number of UL RLC new blocks in MCS6 on PDTCH ..................2-191 2.224 C900040223 Number of UL RLC new blocks in MCS7 on PDTCH ..................2-192 2.225 C900040224 Number of UL RLC new blocks in MCS8 on PDTCH ..................2-193 2.226 C900040225 Number of UL RLC new blocks in MCS9 on PDTCH ..................2-194 2.227 C900040232 Accumulated throughput of UL GPRS TBF................................2-194 2.228 C900040233 Accumulated throughput of DL GPRS TBF................................2-195 2.229 C900040234 Accumulated throughput of UL EGPRS TBF..............................2-196 2.230 C900040235 Accumulated throughput of DL EGPRS TBF..............................2-197

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
IX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 4.26 C900060025 Number of TCH/F allocation success for assignment (speech version2)........................................................................................................ 4-39 4.27 C900060026 Number of TCH/F allocation success for assignment (speech version3)........................................................................................................ 4-40 4.28 C900060027 Number of TCH/F allocation failure due to channel activation 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
X SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 4.58 C900060057 Average number of idle TCH/F with interference band 2................ 4-84 4.59 C900060058 Average number of idle TCH/F with interference band 3................ 4-85 4.60 C900060059 Average number of idle TCH/F with interference band 4................ 4-85 4.61 C900060060 Average number of idle TCH/F with interference band 5................ 4-86 4.62 C900060061 Average number of idle TCH/H with interference band 1 ............... 4-86 4.63 C900060062 Average number of idle TCH/H with interference band 2 ............... 4-87 4.64 C900060063 Average number of idle TCH/H with interference band 3 ............... 4-87 4.65 C900060064 Average number of idle TCH/H with interference band 4 ............... 4-88 4.66 C900060065 Average number of idle TCH/H with interference band 5 ............... 4-89 4.67 C900060066 Number of samples with UL RQ = 0............................................. 4-89 4.68 C900060067 Number of samples with UL RQ = 1............................................. 4-90 4.69 C900060068 Number of samples with UL RQ = 2............................................. 4-90 4.70 C900060069 Number of samples with UL RQ = 3............................................. 4-91 4.71 C900060070 Number of samples with UL RQ = 4............................................. 4-91 4.72 C900060071 Number of samples with UL RQ = 5............................................. 4-92 4.73 C900060072 Number of samples with UL RQ = 6............................................. 4-92 4.74 C900060073 Number of samples with UL RQ = 7............................................. 4-93 4.75 C900060074 Number of samples with DL RQ = 0............................................. 4-93 4.76 C900060075 Number of samples with DL RQ = 1............................................. 4-94 4.77 C900060076 Number of samples with DL RQ = 2............................................. 4-94 4.78 C900060077 Number of samples with DL RQ = 3............................................. 4-95 4.79 C900060078 Number of samples with DL RQ = 4............................................. 4-95 4.80 C900060079 Number of samples with DL RQ = 5............................................. 4-96 4.81 C900060080 Number of samples with DL RQ = 6............................................. 4-96 4.82 C900060081 Number of samples with DL RQ = 7............................................. 4-97 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

XI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 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 from the upper layer.......................................................................4-122 4.112 C900060111 Number of incoming handover from GSM900 to GSM1800 from the lower layer...............................................................................................4-123 4.113 C900060112 Number of incoming handover success from GSM900 to GSM1800 from the lower layer .......................................................................4-124 4.114 C900060113 Number of incoming handover from GSM1800 to GSM900 from the same layer...............................................................................................4-125 4.115 C900060114 Number of incoming handover success from GSM1800 to GSM900 from the same layer .........................................................................4-126

XII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

4.116 C900060115 Number of incoming handover from GSM1800 to GSM900 from the upper layer ..............................................................................................4-127 4.117 C900060116 Number of incoming handover success from GSM1800 to GSM900 from the upper layer.........................................................................4-128 4.118 C900060117 Number of incoming handover from GSM1800 to GSM900 from the lower layer...............................................................................................4-129 4.119 C900060118 Number of incoming handover success from GSM1800 to 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 dynamic radio channel..................4-137 4.127 C900060126 Average number of unavailable dynamic 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 failure for assignment (speech version1) .........................................................4-150 4.141 C900060140 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version1) .........................................................4-151 4.142 C900060141 Number of TCH/F allocation failure due to channel activation failure for assignment (speech version2) .........................................................4-152 4.143 C900060142 Number of TCH/F allocation failure due to BTS connection failure for assignment (speech version2) .........................................................4-153

XIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

4.144 C900060143 Number of TCH/F allocation failure due to BIU connection failure for assignment (speech version2) .........................................................4-154 4.145 C900060144 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version2) .........................................................4-155 4.146 C900060145 Number of TCH/F allocation failure due to BTS connection failure for assignment (speech version3) .........................................................4-156 4.147 C900060146 Number of TCH/F allocation failure due to BIU connection failure for assignment (speech version3) .........................................................4-157 4.148 C900060147 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version3) .........................................................4-158 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 failure for assignment.....................................................................................4-161 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 4.157 C900060156 Number of TCH/F allocation failure due to channel activation failure for handover(speech version1) .............................................................4-167 4.158 C900060157 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version1) ............................................................4-169 4.159 C900060158 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version1) ............................................................4-170 4.160 C900060159 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version1) ............................................................4-171 4.161 C900060160 Number of TCH/F allocation failure due to channel activation failure for handover(speech version2) .............................................................4-172 4.162 C900060161 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version2) ............................................................4-173 4.163 C900060162 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version2) ............................................................4-174 4.164 C900060163 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version2) ............................................................4-176 4.165 C900060164 Number of TCH/F allocation failure due to channel activation failure for handover (speech version3) ............................................................4-177

XIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

4.166 C900060165 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version3) ............................................................4-178 4.167 C900060166 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version3) ............................................................4-179 4.168 C900060167 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version3) ............................................................4-180 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 failure for handover........................................................................................4-186 4.173 C900060172 Number of data TCH/F allocation failure due to TCU connection failure for handover........................................................................................4-188 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 failure for assignment (speech version1) .........................................................4-192 4.177 C900060176 Number of TCH/H allocation failure due to BTS connection failure for assignment (speech version1) .........................................................4-193 4.178 C900060177 Number of TCH/H allocation failure due to BIU connection failure for assignment (speech version1) .........................................................4-194 4.179 C900060178 Number of TCH/H allocation failure due to TCU connection failure for assignment (speech version1) .........................................................4-195 4.180 C900060179 Number of TCH/H allocation failure due to channel activation failure for handover (speech version1) ............................................................4-196 4.181 C900060180 Number of TCH/H allocation failure due to BTS connection failure for handover (speech version1) ............................................................4-197 4.182 C900060181 Number of TCH/H allocation failure due to BIU connection failure for handover (speech version1) ............................................................4-198 4.183 C900060182 Number of TCH/H allocation failure due to TCU connection failure for handover (speech version1) ............................................................4-200 4.184 C900060191 Number of TCH/H allocation failure due to channel activation failure for assignment (speech version3) .........................................................4-201 4.185 C900060192 Number of TCH/H allocation failure due to BTS connection failure for assignment (speech version3) .........................................................4-202 4.186 C900060193 Number of TCH/H allocation failure due to BIU connection failure for assignment (speech version3) .........................................................4-203 4.187 C900060194 Number of TCH/H allocation failure due to TCU connection failure for assignment (speech version3) .........................................................4-204
XV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

4.188 C900060195 Number of TCH/H allocation failure due to channel activation failure for handover (speech version3) ............................................................4-205 4.189 C900060196 Number of TCH/H allocation failure due to BTS connection failure for handover (speech version3) ............................................................4-206 4.190 C900060197 Number of TCH/H allocation failure due to BIU connection failure for handover (speech version3) ............................................................4-207 4.191 C900060198 Number of TCH/H allocation failure due to TCU connection failure for handover (speech version3) ............................................................4-208 4.192 C900060199 Number of Voice TCH/H assignment success............................4-209 4.193 C900060200 Number of Voice TCH/H assignment failure............................... 4-211 4.194 C900060201 Number of Voice TCH/H handover success ...............................4-212 4.195 C900060202 Number of data TCH/H allocation failure due to channel activation failure for assignment......................................................................4-214 4.196 C900060203 Number of data TCH/H allocation failure due to BTS connection failure for assignment.....................................................................................4-215 4.197 C900060204 Number of data TCH/H allocation failure due to BIU connection failure for assignment.....................................................................................4-216 4.198 C900060205 Number of data TCH/H allocation failure due to TCU connection failure for assignment.....................................................................................4-217 4.199 C900060206 Number of data TCH/H allocation failure due to channel activation failure for handover.........................................................................4-218 4.200 C900060207 Number of data TCH/H allocation failure due to BTS connection failure for handover........................................................................................4-219 4.201 C900060208 Number of data TCH/H allocation failure due to BIU connection failure for handover........................................................................................4-220 4.202 C900060209 Number of data TCH/H allocation failure due to TCU connection failure for handover........................................................................................4-222 4.203 C900060210 Number of data TCH/H assignment success .............................4-223 4.204 C900060211 Number of data TCH/H assignment failure.................................4-224 4.205 C900060212 Number of data TCH/H handover success.................................4-225 4.206 C900060213 Number of BSC-controlled incoming handover due to forced release..........................................................................................................4-228 4.207 C900060214 Number of BSC-controlled incoming handover due to queues..........................................................................................................4-229 4.208 C900060215 Number of BSC-controlled incoming handover due to forced handover.......................................................................................................4-230 4.209 C900060216 Number of MSC-controlled incoming handover due to forced handover.......................................................................................................4-232 4.210 C900060217 Number of unavailable defined TCH/H ......................................4-233 4.211 C900060218 Number of unavailable defined TCH/F.......................................4-234
XVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

4.212 C900060219 Number of signaling TCH/F drops due to handover failure..........4-235 4.213 C900060220 Number of voice TCH/F drops due to handover failure ...............4-237 4.214 C900060221 Number of data TCH/F drops due to handover failure ................4-239 4.215 C900060222 Number of signaling TCH/H drops due to handover failure .........4-241 4.216 C900060223 Number of data TCH/H drops due to handover failure ................4-243 4.217 C900060224 Number of TCH/H handover attempts due to UL strength ...........4-245 4.218 C900060225 Number of TCH/H handover attempts due to DL strength ...........4-246 4.219 C900060226 Number of TCH/H handover attempts due to UL quality .............4-247 4.220 C900060227 Number of TCH/H handover attempts due to DL quality .............4-247 4.221 C900060228 Number of TCH/H handover attempts due to UL interference ......4-248 4.222 C900060229 Number of TCH/H handover attempts due to DL interference ......4-249 4.223 C900060230 Number of TCH/H inter-subcell handover attempts due to good C/I ................................................................................................................4-250 4.224 C900060231 Number of TCH/H inter-subcell handover attempts due to bad C/I ................................................................................................................4-251 4.225 C900060232 Number of TCH/H handover attempts due to PBGT ...................4-252 4.226 C900060233 Number of TCH/H handover attempts due to large TA................4-253 4.227 C900060234 Number of TCH/H handover attempts due to other reasons........4-254 4.228 C900060235 Number of signaling TCH/H assignment success.......................4-255 4.229 C900060236 Number of MOC access success ..............................................4-256 4.230 C900060237 Number of dual band outgoing handover...................................4-257 4.231 C900060238 Number of dual band outgoing handover success......................4-258 4.232 C900060239 Number of dual band incoming handover ..................................4-259 4.233 C900060240 Number of dual band incoming handover success .....................4-260 4.234 C900060241 Number of SDCCH assignment attempts ..................................4-260 4.235 C900060242 Number of SDCCH assignments success .................................4-262 4.236 C900060243 Number of SDCCH assignment failure ......................................4-263 4.237 C900060244 Number of voice TCH/F drops due to radio link failure................4-264 4.238 C900060245 Number of voice TCH/H drops due to radio link failure ...............4-265

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
XVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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-3 6.2 C901000001 Number of GPRS DL TBF resumption in delay state......................... 6-3 6.3 C901000005 Number of GPRS DL TBF establishment failure on PACCH due to time out............................................................................................................ 6-4 6.4 C901000006 Number of GPRS DL TBF establishment failure on PACCH due to other reasons ................................................................................................... 6-5 6.5 C901000009 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to time out ................................................................................................. 6-6 6.6 C901000010 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to other reasons ......................................................................................... 6-7 6.7 C901000011 Number of GPRS DL TBF establishment execution on CCCH/PCCCH ................................................................................................. 6-8 6.8 C901000012 Number of GPRS DL TBF establishment execution failure on CCCH/PCCCH due to polling failed ................................................................... 6-9 6.9 C901000013 Number of GPRS DL TBF establishment execution success on CCCH/PCCCH due to polling succeeded ..........................................................6-11 6.10 C901000014 Number of GPRS DL TBF establishment success on CCCH/PCCCH ............................................................................................... 6-13 6.11 C901000015 Number of GPRS DL TBF normal release .................................... 6-15 6.12 C901000023 Number of EGPRS DL TBF resumption in delay state................... 6-16 6.13 C901000027 Number of EGPRS DL TBF establishment failure on PACCH due to time out ...................................................................................................... 6-18 6.14 C901000028 Number of EGPRS DL TBF establishment failure on PACCH due to other reasons ............................................................................................. 6-18 6.15 C901000031 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to time out ........................................................................ 6-19 6.16 C901000032 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to other reasons................................................................ 6-20 6.17 C901000033 Number of EGPRS DL TBF establishment execution on CCCH/PCCCH ............................................................................................... 6-21 6.18 C901000034 Number of EGPRS DL TBF establishment execution failure on CCCH/PCCCH due to polling failed ................................................................. 6-23 6.19 C901000035 Number of EGPRS DL TBF establishment execution success on CCCH/PCCCH due to polling succeeded ......................................................... 6-25 6.20 C901000036 Number of EGPRS DL TBF establishment success on CCCH/PCCCH ............................................................................................... 6-27
XVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

6.21 C901000037 Number of EGPRS DL TBF normal release.................................. 6-29 6.22 C901000045 Time of GPRS DL TBF connection .............................................. 6-30 6.23 C901000046 Time of EGPRS DL TBF connection ............................................ 6-31 6.24 C901000047 Time of DL signaling TBF connection........................................... 6-32 6.25 C901000048 Max number of GPRS DL TBF simultaneous establishment .......... 6-32 6.26 C901000050 Max number of EGPRS DL TBF simultaneous establishment ........ 6-33 6.27 C901000052 Number of GPRS DL signaling TBF normal release ...................... 6-33 6.28 C901000058 Number of EGPRS DL signaling TBF normal release.................... 6-35 6.29 C901000066 Number of EGPRS2-A TBF restarting in downlink delay state ....... 6-36 6.30 C901000067 Number of downlink EGPRS2-A TBF establishment requests before T3192 expires ...................................................................................... 6-36 6.31 C901000068 Number of establishing downlink EGPRS2-A TBF without requesting downlink channel resource.............................................................. 6-37 6.32 C901000069 Number of requests for establishing downlink EGPRS2-A TBF on PACCH ..................................................................................................... 6-38 6.33 C901000070 Number of Failures in Establishing Downlink EGPRS2-A TBF on PACCH Due to Timeout in Resource Assignment ............................................. 6-39 6.34 C901000071 Number of Failures in Establishing Downlink EGPRS2-A TBF on PACCH Due to Other Causes.......................................................................... 6-40 6.35 C901000072 Number of Successfully Establishing Downlink EGPRS2-A TBF on PACCH ..................................................................................................... 6-40 6.36 C901000073 Number of Requests for Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH .......................................................................................... 6-42 6.37 C901000074 Number of Failures in Establishing Downlink EGPRS2-A TBF on CCCH/PCCCH Due to Timeout in Resource Assignment .................................. 6-43 6.38 C901000075 Number of Failures in Establishing Downlink EGPRS2-A TBF on CCCH/PCCCH Due to Other Causes............................................................... 6-44 6.39 C901000076 Number of Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH ............................................................................................... 6-44 6.40 C901000077 Number of Failures in Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH Due to Polling Failure .............................................................. 6-46 6.41 C901000078 Number of Successfully Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH Due to Polling Success ....................................................... 6-48 6.42 C901000079 Number of Successfully Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH .......................................................................................... 6-50 6.43 C901000080 Times of Normal Releasing EGPRS2-A Downlink TBF.................. 6-52 6.44 C901000081 Number of Releases of EGPRS2-A Downlink TBF Due to N3105 Overflow ........................................................................................................ 6-53 6.45 C901000082 Number of Abnormal Releases of EGPRS2-A Downlink TBF......... 6-54

XIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

6.46 C901000083 Number of Abnormal Releases of EGPRS2-A Downlink TBF by Control Plane ................................................................................................. 6-54 6.47 C901000084 Number of Abnormal Releases of EGPRS2-A Downlink TBF Due to Instance Suspension................................................................................... 6-55 6.48 C901000085 Number of Abnormal Releases of EGPRS2-A Downlink TBF Due to Internal Error .............................................................................................. 6-56 6.49 C901000086 Number of EGPRS2-A Downlink Signaling TBF Establishments ..... 6-57 6.50 C901000087 Number of EGPRS2-A Downlink Data TBF Establishments........... 6-57 6.51 C901000088 Total Time of EGPRS2-A Downlink TBF Connection ..................... 6-58 6.52 C901000089 Maximum Number of EGPRS2-A Downlink TBF Established Simultaneously ............................................................................................... 6-59 6.53 C901000090 Average Number of EGPRS2-A Downlink TBF Established Simultaneously ............................................................................................... 6-59 6.54 C901000091 Number of Normal Releases of EGPRS2-A Signaling Downlink TBF ............................................................................................................... 6-59 6.55 C901000092 Number of Releases of EGPRS2-A Signaling Downlink TBF Due to N3105 Overflow .......................................................................................... 6-61 6.56 C901000093 Number of Abnormal Releases of EGPRS2-A Signaling Downlink TBF ............................................................................................................... 6-62 6.57 C901000094 Number of Abnormal Releases of EGPRS2-A Signaling Downlink TBF by Control Plane...................................................................................... 6-63 6.58 C901000095 Number of Abnormal Releases of EGPRS2-A Signaling Downlink TBF Due to Instance Suspension..................................................................... 6-63 6.59 C901000096 Number of Abnormal Releases of EGPRS2-A Signaling Downlink TBF Due to Internal Error ................................................................................ 6-64 6.60 C901000097 Number of EGPRS2-A Data Downlink TBF Establishment on PACCH .......................................................................................................... 6-65 6.61 C901000098 Peak Downlink GPRS Throughput ............................................... 6-65 6.62 C901000099 Peak Downlink EGPRS Throughput............................................. 6-65

Chapter 7 Uplink Data TBF Measurement ................................................ 7-1

7.1 Overview ........................................................................................................... 7-3 7.2 C901010001 Number of GPRS UL TBF resumption in extend uplink state ............. 7-3 7.3 C901010002 Number of GPRS UL TBF resource reassign in delay uplink state ..... 7-4 7.4 C901010006 Number of GPRS establishment failure on PACCH due to time out................................................................................................................... 7-5 7.5 C901010007 Number of GPRS establishment failure on PACCH due to other reasons............................................................................................................ 7-6 7.6 C901010010 Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to competition solving failed ........................................................................ 7-7

XX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

7.7 C901010011 Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to not receive resource request ................................................................... 7-8 7.8 C901010012 Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons ......................................................................................... 7-9 7.9 C901010013 Number of GPRS UL TBF establishment success on CCCH/PCCCH ............................................................................................... 7-10 7.10 C901010014 Number of GPRS UL TBF normal release .................................... 7-12 7.11 C901010022 Number of EGPRS UL TBF resumption in extend uplink state ....... 7-13 7.12 C901010023 Number of EGPRS UL TBF resource reassign in delay uplink state .............................................................................................................. 7-14 7.13 C901010027 Number of EGPRS establishment failure on PACCH due to time out................................................................................................................. 7-14 7.14 C901010028 Number of EGPRS establishment failure on PACCH due to other reasons.......................................................................................................... 7-15 7.15 C901010031 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to competition solving failed............................................... 7-16 7.16 C901010032 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to not receive resource request.......................................... 7-17 7.17 C901010033 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons................................................................ 7-18 7.18 C901010034 Number of EGPRS UL TBF establishment success on CCCH/PCCCH ............................................................................................... 7-19 7.19 C901010035 Number of EGPRS UL TBF normal release.................................. 7-21 7.20 C901010043 Time of GPRS UL TBF connection .............................................. 7-22 7.21 C901010044 Time of EGPRS UL TBF connection ............................................ 7-23 7.22 C901010045 Time of UL signaling TBF connection........................................... 7-23 7.23 C901010046 Max number of GPRS UL TBF simultaneous establishment .......... 7-24 7.24 C901010048 Max number of EGPRS UL TBF simultaneous establishment ........ 7-24 7.25 C901010050 Number of GPRS UL signaling TBF normal release ...................... 7-25 7.26 C901010056 Number of EGPRS UL signaling TBF normal release.................... 7-26 7.27 C901010064 Number of EGPRS2-A uplink TBF reestablishment in extended uplink state..................................................................................................... 7-27 7.28 C901010065 Number of EGPRS2-A uplink TBF resource assignments in uplink delay state............................................................................................ 7-27 7.29 C901010066 Number of EGPRS2-A uplink TBF reestablishments in released state .............................................................................................................. 7-27 7.30 C901010067 Number of EGPRS2-A uplink TBF establishments with available uplink resource ............................................................................................... 7-28 7.31 C901010068 Number of requests for establishing EGPRS2-A uplink TBF on PACCH .......................................................................................................... 7-29
XXI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

7.32 C901010069 Number of failures in establishing EGPRS2-A uplink TBF on PACCH due to timeout .................................................................................... 7-30 7.33 C901010070 Number of failures in establishing EGPRS2-A uplink TBF on PACCH due to other causes............................................................................ 7-31 7.34 C901010071 Number of Successfully Establishing EGPRS2-A Uplink TBF on PACCH .......................................................................................................... 7-31 7.35 C901010072 Number of Failures in Establishing EGPRS2-A Uplink TBF on CCCH/PCCCH Due to Other Causes............................................................... 7-32 7.36 C901010073 Number of Successfully Establishing EGPRS2-A Uplink TBF on CCCH/PCCCH ............................................................................................... 7-33 7.37 C901010074 Times of Normal Releasing EGPRS2-A Uplink TBF ...................... 7-33 7.38 C901010075 Number of Abnormal Releases of EGPRS2-A Uplink TBF Due to N3101 Overflow.............................................................................................. 7-34 7.39 C901010076 Number of Abnormal Releases of EGPRS2-A Uplink TBF Due to N3103 Overflow.............................................................................................. 7-35 7.40 C901010077 Number of Forced Releases of EGPRS2-A Uplink TBF................. 7-35 7.41 C901010078 Number of Abnormal Releases of EGPRS2-A Uplink TBF Due to Instance Suspension....................................................................................... 7-35 7.42 C901010079 Number of Abnormal Releases of EGPRS2-A Uplink TBF Due to Internal Error .................................................................................................. 7-36 7.43 C901010080 Number of EGPRS2-A Uplink Signaling TBF Establishments ........ 7-36 7.44 C901010081 Number of EGPRS2-A Uplink Data TBF Establishments ............... 7-37 7.45 C901010082 Total Time of EGPRS2-A Uplink TBF Connection ......................... 7-37 7.46 C901010083 Maximum Number of EGPRS2-A Uplink TBF Established Simultaneously ............................................................................................... 7-37 7.47 C901010084 Average Number of EGPRS2-A Uplink TBF Established Simultaneously ............................................................................................... 7-38 7.48 C901010085 Number of Normal Releases of EGPRS2-A Signaling Uplink TBF ............................................................................................................... 7-38 7.49 C901010086 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due to N3101 Overflow............................................................................ 7-39 7.50 C901010087 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due to N3103 Overflow............................................................................ 7-40 7.51 C901010088 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due to Forced Release ............................................................................ 7-40 7.52 C901010089 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due to Instance Suspension..................................................................... 7-41 7.53 C901010090 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due to Internal Error ................................................................................ 7-41

XXII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

7.54 C901010091 Number of Successfully Establishing EGPRS2-A Uplink Data TBF on PACCH .............................................................................................. 7-42 7.55 C901010092 Peak Uplink GPRS Throughput ................................................... 7-42 7.56 C901010093 Peak Uplink EGPRS Throughput ................................................. 7-42

Chapter 8 Data Flow Measurement........................................................... 8-1

8.1 Overview ........................................................................................................... 8-2 8.2 C901020001 Number of Bytes of IP packet sent to BIPB ...................................... 8-2 8.3 C901020002 Number of packets sent to BIPB...................................................... 8-3 8.4 C901020003 Number of Bytes of IP packet received from BIPB ............................ 8-4 8.5 C901020004 Number of packets received from BIPB ........................................... 8-5 8.6 C901020005 Number of Bytes of IP packet sent to GIPB ...................................... 8-6 8.7 C901020006 Number of packets sent to GIPB ..................................................... 8-6 8.8 C901020007 Number of Bytes of IP packet received from GIPB............................ 8-7 8.9 C901020008 Number of packets received from GIPB ........................................... 8-8 8.10 C901020009 Number of Bytes carried by EGPRS DL LLC frame......................... 8-9 8.11 C901020014 Number of Bytes carried by DL signaling LLC frame ..................... 8-10 8.12 C901020019 Number of Bytes carried by UL LLC frame ....................................8-11 8.13 C901020020 Number of UL LLC frames .......................................................... 8-12 8.14 C901020021 Number of Bytes of GPRS DL TBF LLC frame ............................. 8-12 8.15 C901020022 Number of Bytes of EGPRS DL TBF LLC frame ........................... 8-13 8.16 C901020023 Number of Bytes of DL signaling TBF LLC frame.......................... 8-14 8.17 C901020024 Number of Bytes of UL GPRS TBF LLC frame ............................. 8-15 8.18 C901020025 Number of Bytes of EGPRS UL TBF LLC frame ........................... 8-16 8.19 C901020026 Number of Bytes of UL signaling TBF LLC frame.......................... 8-17 8.20 C901020031 Number of GPRS UL data TBF completion .................................. 8-17 8.21 C901020034 Number of GPRS DL data TBF completion .................................. 8-18 8.22 C901020041 Number of EGPRS UL data TBF completion ................................ 8-19 8.23 C901020044 Number of EGPRS DL data TBF completion ................................ 8-20 8.24 C901020050 Number of Bytes carried by GPRS DL LLC frame......................... 8-21 8.25 C901020055 Number of DL EGPRS2-A TBF LLC Bytes ................................... 8-22 8.26 C901020056 Number of DL EGPRS2-A TBF LLC ............................................ 8-22 8.27 C901020057 Number of DL EGPRS2-A TBF LLC Discarded for Buffer Overload ........................................................................................................ 8-23 8.28 C901020058 Number of DL EGPRS2-A TBF LLC Discarded for Life Time Expiration....................................................................................................... 8-23 8.29 C901020059 Number of DL EGPRS2-A TBF LLC Discarded for Other Reasons ........................................................................................................ 8-24 8.30 C901020060 Number of UL EGPRS2-A TBF LLC Bytes ................................... 8-24
XXIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

8.31 C901020061 Number of UL EGPRS2-A TBF LLC ............................................ 8-25 8.32 C901020062 Number of DL LLC Sent Correctly Bytes in EGPRS2-A Ack Mode ............................................................................................................. 8-25 8.33 C901020063 Times of UL EGPRS2-A TBF Normal Release.............................. 8-26 8.34 C901020064 Alive Time of UL EGPRS2-A TBF ................................................ 8-26 8.35 C901020065 Number of LLC Bytes Sent by DL EGPRS2-A TBF ....................... 8-27 8.36 C901020066 Times of DL EGPRS2-A TBF Normal Release.............................. 8-27 8.37 C901020067 Alive Time of DL EGPRS2-A TBF ................................................ 8-28 8.38 C901020068 Number of LLC Bytes Received by UL EGPRS2-A TBF ................ 8-28 8.39 C901020069 Number of NACK Data Blocks Received by UL EGPRS2-A TBF ............................................................................................................... 8-29 8.40 C901020070 Number of LLC Bytes Received by DL EGPRS2-A TBF ................ 8-29 8.41 C901020071 Number of NACK Data Blocks Received by DL EGPRS2-A TBF ............................................................................................................... 8-30 8.42 C901020072 Number of DL EGPRS2-A TBF Send Current Blocks .................... 8-31 8.43 C901020077 Number of Discarded UL Signaling LLC Frames........................... 8-31 8.44 C901020078 Number of Discarded UL GPRS Data LLC Frames ....................... 8-32 8.45 C901020079 Number of Discarded UL EGPRS Data LLC Frames..................... 8-32 8.46 C901020080 Number of Discarded UL EGPRS 2A/B Data LLC Frames............. 8-33 8.47 C901020081 Number of DL Signaling LLC Frames Sent Successfully in Signaling TBF Mode ....................................................................................... 8-33 8.48 C901020082 Number of DL Data LLC Frames Sent Successfully in GPRS Data TBF Mode .............................................................................................. 8-34 8.49 C901020083 Number of DL Data LLC Frames Sent Successfully in EGPRS Data TBF Mode .............................................................................................. 8-34 8.50 C901020084 Number of DL Data LLC Frames Sent Successfully in EGPRS2A/B Data TBF Mode .......................................................................... 8-35 8.51 C901020085 Maximum number of LLC Store In Bssgp ..................................... 8-35 8.52 C901020086 Sum of Max LLC Store In Bssgp.................................................. 8-36 8.53 C901020087 Sample of BSSGP Inst................................................................ 8-36 8.54 C901020088 Sum of number due to LLC Store reach MAX ............................... 8-37 8.55 C901020089 Maximum number of LLC Trans In Bssgp..................................... 8-37 8.56 C901020090 Sum of Max LLC Trans In Bssgp ................................................. 8-38 8.57 C901020091 Sample of BSSGP Trans............................................................. 8-38 8.58 C901020092 Sum of number due to LLC Trans reach MAX .............................. 8-39

Chapter 9 Uplink-Downlink RLC Statistic Measurement ........................ 9-1

9.1 Overview ........................................................................................................... 9-3 9.2 C901030041 Bytes of GPRS DL RLC lost on PDTCH........................................... 9-5

XXIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

9.3 C901030042 Bytes of EGPRS DL RLC lost on PDTCH......................................... 9-6 9.4 C901030083 Number of UL RLC Blocks lost ........................................................ 9-6 9.5 C901030084 Bytes of GPRS UL RLC lost on PDTCH........................................... 9-7 9.6 C901030085 Bytes of EGPRS UL RLC lost on PDTCH......................................... 9-7 9.7 C901030086 Number of standstill of GPRS UL TBF receiving window ................... 9-8 9.8 C901030087 Number of standstill of EGPRS UL TBF receiving window................. 9-9 9.9 C901030088 Number of standstill of GPRS DL TBF sending window................... 9-10 9.10 C901030089 Number of standstill of EGPRS DL TBF sending window .............. 9-10 9.11 C901030090 Number of increment of DL coding mode ......................................9-11 9.12 C901030091 Number of decrement of DL coding mode .................................... 9-13 9.13 C901030092 Number of increment of UL coding mode ..................................... 9-14 9.14 C901030093 Number of decrement of UL coding mode .................................... 9-15 9.15 C901030094 Number of conversion from GMSK to 8PSK ................................. 9-16 9.16 C901030095 Number of conversion from 8PSK to GMSK ................................. 9-18 9.17 C901030098 Number of Useful Downlink RLC Pending Blocks in DAS5 Coding on PDTCH .......................................................................................... 9-19 9.18 C901030099 Number of Useful Downlink RLC Pending Blocks in DAS6 Coding on PDTCH .......................................................................................... 9-20 9.19 C901030100 Number of Useful Downlink RLC Pending Blocks in DAS7 Coding on PDTCH .......................................................................................... 9-20 9.20 C901030101 Number of Useful Downlink RLC Pending Blocks in DAS8 Coding on PDTCH .......................................................................................... 9-21 9.21 C901030102 Number of Useful Downlink RLC Pending Blocks in DAS9 Coding on PDTCH .......................................................................................... 9-21 9.22 C901030103 Number of Useful Downlink RLC Pending Blocks in DAS10 Coding on PDTCH .......................................................................................... 9-22 9.23 C901030104 Number of Useful Downlink RLC Pending Blocks in DAS11 Coding on PDTCH .......................................................................................... 9-22 9.24 C901030105 Number of Useful Downlink RLC Pending Blocks in DAS12 Coding on PDTCH .......................................................................................... 9-23 9.25 C901030106 Number of Useful Uplink RLC Pending Blocks in UAS7 Coding on PDTCH ..................................................................................................... 9-23 9.26 C901030107 Number of Useful Uplink RLC Pending Blocks in UAS8 Coding on PDTCH ..................................................................................................... 9-24 9.27 C901030108 Number of Useful Uplink RLC Pending Blocks in UAS9 Coding on PDTCH ..................................................................................................... 9-24 9.28 C901030109 Number of Useful Uplink RLC Pending Blocks in UAS10 Coding on PDTCH ..................................................................................................... 9-25 9.29 C901030110 Number of Useful Uplink RLC Pending Blocks in UAS11 Coding on PDTCH ..................................................................................................... 9-25
XXV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

9.30 C901030111 Number of Useful Downlink RLC NACK Blocks in DAS5 Coding on PDTCH ..................................................................................................... 9-26 9.31 C901030112 Number of Useful Downlink RLC NACK Blocks in DAS6 Coding on PDTCH ..................................................................................................... 9-26 9.32 C901030113 Number of Useful Downlink RLC NACK Blocks in DAS7 Coding on PDTCH ..................................................................................................... 9-27 9.33 C901030114 Number of Useful Downlink RLC NACK Blocks in DAS8 Coding on PDTCH ..................................................................................................... 9-27 9.34 C901030115 Number of Useful Downlink RLC NACK Blocks in DAS9 Coding on PDTCH ..................................................................................................... 9-28 9.35 C901030116 Number of Useful Downlink RLC NACK Blocks in DAS10 Coding on PDTCH ..................................................................................................... 9-28 9.36 C901030117 Number of Useful Downlink RLC NACK Blocks in DAS11 Coding on PDTCH ..................................................................................................... 9-29 9.37 C901030118 Number of Useful Downlink RLC NACK Blocks in DAS12 Coding on PDTCH ..................................................................................................... 9-29 9.38 C901030119 Number of Useful Uplink RLC NACK Blocks in UAS7 Coding on PDTCH .......................................................................................................... 9-30 9.39 C901030120 Number of Useful Uplink RLC NACK Blocks in UAS8 Coding on PDTCH .......................................................................................................... 9-30 9.40 C901030121 Number of Useful Uplink RLC NACK Blocks in UAS9 Coding on PDTCH .......................................................................................................... 9-31 9.41 C901030122 Number of Useful Uplink RLC NACK Blocks in UAS10 Coding on PDTCH .......................................................................................................... 9-31 9.42 C901030123 Number of Useful Uplink RLC NACK Blocks in UAS11 Coding on PDTCH .......................................................................................................... 9-32 9.43 C901030124 Number of New Downlink RLC Blocks in DAS5 Coding on PDTCH .......................................................................................................... 9-32 9.44 C901030125 Number of New Downlink RLC Blocks in DAS6 Coding on PDTCH .......................................................................................................... 9-33 9.45 C901030126 Number of New Downlink RLC Blocks in DAS7 Coding on PDTCH .......................................................................................................... 9-33 9.46 C901030127 Number of New Downlink RLC Blocks in DAS8 Coding on PDTCH .......................................................................................................... 9-34 9.47 C901030128 Number of New Downlink RLC Blocks in DAS9 Coding on PDTCH .......................................................................................................... 9-34 9.48 C901030129 Number of New Downlink RLC Blocks in DAS10 Coding on PDTCH .......................................................................................................... 9-35 9.49 C901030130 Number of New Downlink RLC Blocks in DAS11 Coding on PDTCH .......................................................................................................... 9-35

XXVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

9.50 C901030131 Number of New Downlink RLC Blocks in DAS12 Coding on PDTCH .......................................................................................................... 9-36 9.51 C901030132 Number of New Uplink RLC Blocks in UAS7 Coding on PDTCH ..... 9-36 9.52 C901030133 Number of New Uplink RLC Blocks in UAS8 Coding on PDTCH ..... 9-37 9.53 C901030134 Number of New Uplink RLC Blocks in UAS9 Coding on PDTCH ..... 9-37 9.54 C901030135 Number of New Uplink RLC Blocks in UAS10 Coding on PDTCH .......................................................................................................... 9-38 9.55 C901030136 Number of New Uplink RLC Blocks in UAS11 Coding on PDTCH .......................................................................................................... 9-38 9.56 C901030137 Times of Receive Window Stall of EGPRS2-A TBF....................... 9-39 9.57 C901030138 Times of Send Window Stall of EGPRS2-A TBF ........................... 9-39 9.58 C901030139 Times of Changes From 8PSK to 16QAM .................................... 9-40 9.59 C901030140 Times of Changes From 8PSK to 32QAM .................................... 9-40 9.60 C901030141 Times of Changes From 16QAM to 32QAM ................................. 9-41 9.61 C901030142 Times of Changes From 32QAM to 16QAM ................................. 9-41 9.62 C901030143 Times of Changes From 32QAM to 8PSK .................................... 9-41 9.63 C901030144 Times of Changes From 16QAM to 8PSK .................................... 9-42 9.64 C901030145 Times of Changes From GMSK to 16QAM ................................... 9-42 9.65 C901030146 Times of Changes From GMSK to 32QAM ................................... 9-43 9.66 C901030147 Times of Changes From 32QAM to GMSK ................................... 9-43 9.67 C901030148 Times of Changes From 16QAM to GMSK ................................... 9-43 9.68 C901030149 Times of Changes From Uplink EGPRS to EGPRS2-A ................. 9-44 9.69 C901030150 Times of Changes From Uplink EGPRS2-A to EGPRS ................. 9-44 9.70 C901030151 Times of Changes From Downlink EGPRS to EGPRS2-A ............. 9-45 9.71 C901030152 Times of Changes From Downlink EGPRS2-A to EGPRS ............. 9-45 9.72 C901030153 Number of increment of GPRS DL coding mode ........................... 9-45 9.73 C901030154 Number of decrement of GPRS DL coding mode.......................... 9-46 9.74 C901030155 Number of increment of GPRS UL coding mode ........................... 9-47 9.75 C901030156 Number of decrement of GPRS UL coding mode.......................... 9-48 9.76 C901030157 Number of increment of EGPRS DL coding mode......................... 9-48 9.77 C901030158 Number of decrement of EGPRS DL coding mode........................ 9-49 9.78 C901030159 Number of increment of EGPRS UL coding mode......................... 9-50 9.79 C901030160 Number of decrement of EGPRS UL coding mode........................ 9-50 9.80 C901030161 Number of Bytes Lost by Uplink EGPRS2-A RLC on PDTCH ........ 9-51 9.81 C901030162 Num Uplink TBF Received PAN of Using MCS ............................. 9-51 9.82 C901030163 Num Downlink TBF Received PAN of Using MCS......................... 9-52 9.83 C901030164 Num Uplink TBF Received PAN of Using UAS.............................. 9-52 9.84 C901030165 Num Downlink TBF Received PAN of Using UAS ......................... 9-52
XXVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement......................... 10-1

10.1 Overview ....................................................................................................... 10-3 10.2 C901040001 Maximum Number of Abis TS Used ............................................. 10-3 10.3 C901040002 Average Number of Abis TS Used ............................................... 10-3 10.4 C901040004 Average number of unavailable PDCH......................................... 10-4 10.5 C901040005 Number of available static PDCH................................................. 10-4 10.6 C901040006 Number of unavailable static PDCH ............................................. 10-5 10.7 C901040009 Time of DL PDCH congestion...................................................... 10-5 10.8 C901040010 Time of UL PDCH congestion...................................................... 10-6 10.9 C901040011 Time of PDCH used at least one UL/DL TBF exists....................... 10-7 10.10 C901040012 Time of PDCH used at least one UL/DL EGPRS TBF exists ........ 10-8 10.11 C901040013 Time of PDCH used at least one DL TBF exists .......................... 10-9 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-10 10.14 C901040019 Number of paging PS requests on PCH .................................... 10-11 10.15 C901040020 Number of paging CS requests on PCH ....................................10-12 10.16 C901040021 Number of immediate assignment on PCH ................................10-13 10.17 C901040022 Number of immediate assignment on PAGCH ...........................10-14 10.18 C901040023 Number of paging PS requests on PPCH ..................................10-15 10.19 C901040024 Number of paging CS requests on PPCH..................................10-16 10.20 C901040025 Number of immediate assignment on PPCH..............................10-17 10.21 C901040026 Number of Packet Channel Request on PRACH........................10-18 10.22 C901040027 Sum of Abis TS Used Sampling................................................10-19 10.23 C901040028 Number of Abis TS used sampling............................................10-19 10.24 C901040029 Sum of PDCH used sampling ...................................................10-20 10.25 C901040030 Number of PDCH used sampling ..............................................10-20 10.26 C901040031 Maximum value of Abis TS used to CS .....................................10-21 10.27 C901040032 Minimum value of Abis TS used to CS ......................................10-21 10.28 C901040033 Total value of the regular sampling used to CS ..........................10-22 10.29 C901040034 Number of sampling of CS .......................................................10-22 10.30 C901040035 Maximum value of Abis TS used to PS......................................10-23 10.31 C901040036 Minimum value of Abis TS used to PS ......................................10-23 10.32 C901040037 Total value of the regular sampling used to PS ..........................10-24 10.33 C901040038 Number of sampling of PS........................................................10-25 10.34 C901040039 MAX CS used number of exclusive ABIS ..................................10-25 10.35 C901040040 MIN CS used number of exclusive ABIS ...................................10-26 10.36 C901040041 MAX PS used number of exclusive ABIS...................................10-26

XXVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

10.37 C901040042 MIN PS used number of exclusive ABIS....................................10-27 10.38 C901040043 Average Number of GPRS User ...............................................10-27 10.39 C901040044 Maximum number of GPRS User..............................................10-28 10.40 C901040045 Average Number of EGPRS User .............................................10-28 10.41 C901040046 Maximum number of EDGE User..............................................10-29 10.42 C901040047 Number of assigned uplink radio channels ................................10-29 10.43 C901040048 Number of assigned downlink radio channels ............................10-30 10.44 C901040049 Number of requested uplink radio channels ...............................10-30 10.45 C901040050 Number of requested downlink radio channels...........................10-31 10.46 C901040051 Number of PS channel expand .................................................10-31 10.47 C901040052 Number of PS channel expand perform.....................................10-31 10.48 C901040053 Number of PS channel expand success ....................................10-32 10.49 C901040054 Total number of all TBF used uplink PDCH ...............................10-32 10.50 C901040055 Total number of all TBF used downlink PDCH ...........................10-33 10.51 C901040056 Sample number of all TBF used uplink PDCH ...........................10-34 10.52 C901040057 Sample number of all TBF used downlink PDCH ......................10-34 10.53 C901040058 Average number used uplink PDCH..........................................10-35 10.54 C901040059 Average number used downlink PDCH .....................................10-35 10.55 C901040060 Sum of uplink PDCH used sampling .........................................10-36 10.56 C901040061 Sum of downlink PDCH used sampling .....................................10-36 10.57 C901040062 Number of uplink PDCH used sampling ....................................10-37 10.58 C901040063 Number of downlink PDCH used sampling ................................10-37 10.59 C901040064 Average number of all TBF used total uplink PDCH ..................10-38 10.60 C901040065 Average number of all TBF used total downlink PDCH ..............10-39 10.61 C901040078 Time of PDCH Used at Least One UL/DL TBF Exists .................10-39 10.62 C901040079 Time of Configured EGPRS PDCH Used at Least One UL/DL EGPRS TBF Exists........................................................................................10-40 10.63 C901040080 Total number of all GPRS TBF used PDCH ...............................10-40 10.64 C901040081 Sample number of all GPRS TBF used PDCH...........................10-41 10.65 C901040082 Average number of GPRS TBF used total PDCH.......................10-41 10.66 C901040083 Total number of all EGPRS TBF used PDCH.............................10-42 10.67 C901040084 Sample number of all EGPRS TBF used PDCH.........................10-42 10.68 C901040085 Average number of EGPRS TBF used total PDCH.....................10-43 10.69 C901040086 Total number of all EGPRS TBF used EGPRS only PDCH .........10-43 10.70 C901040087 Sample number of all EGPRS TBF used EGPRS only PDCH ......10-44 10.71 C901040088 Average number of EGPRS TBF used total EGPRS only PDCH ...........................................................................................................10-44 10.72 C901040089 UL Request PDCH Times.........................................................10-45
XXIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

10.73 C901040090 UL Unsatisfied PDCH Times ....................................................10-45 10.74 C901040091 DL Request PDCH Times.........................................................10-46 10.75 C901040092 DL Unsatisfied PDCH Times ....................................................10-46 10.76 C901040093 Average Number of PDCH Allocated Per UL TBF ......................10-47 10.77 C901040094 Sample Number of PDCH Allocated Per UL TBF .......................10-47 10.78 C901040095 Average Number of PDCH Allocated Per DL TBF ......................10-48 10.79 C901040096 Sample Number of PDCH Allocated Per DL TBF .......................10-48

Chapter 11 RMM Assignment Measurement.......................................... 11-1

11.1 Overview.........................................................................................................11-4 11.2 C901050001 Number of general assignment executions for voice channel ..........11-4 11.3 C901050002 Number of assignments attempts for voice due to forced release............................................................................................................11-5 11.4 C901050003 Number of assignment executions for voice channel due to forced release .................................................................................................11-6 11.5 C901050004 Number of handover attempts for voice due to forced release.........11-7 11.6 C901050005 Number of handover executions for voice channel due to forced release............................................................................................................11-8 11.7 C901050006 Number of assignments for voice channel due to queuing ............ 11-10 11.8 C901050007 Number of assignments for execution for voice channel due to queuing......................................................................................................... 11-11 11.9 C901050008 Duration of assignment success voice channel due to queuing ...... 11-12 11.10 C901050009 Number of assignments success for voice channel due to queuing......................................................................................................... 11-13 11.11 C901050010 Number of assignments for directed retry attempts for voice channel......................................................................................................... 11-14 11.12 C901050011 Number of assignments for execution for voice channel due to directed retry ................................................................................................. 11-15 11.13 C901050012 Number of general assignments for execution for data ............... 11-16 11.14 C901050013 Number of assignments attempts for data due to forced release.......................................................................................................... 11-17 11.15 C901050014 Number of assignment executions for data due to forced release.......................................................................................................... 11-18 11.16 C901050015 Number of handover attempts for data due to forced release ...... 11-19 11.17 C901050016 Number of handover executions for data due to forced release.......................................................................................................... 11-20 11.18 C901050017 Number of assignments attempts for data due to queuing........... 11-21 11.19 C901050018 Number of assignments for execution for data due to queuing ...... 11-23 11.20 C901050019 Total duration of successful assignments for data due to queuing......................................................................................................... 11-24
XXX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

11.21 C901050020 Number of assignments success for data due to queuing ........... 11-25 11.22 C901050021 Number of assignments attempts for data due to directed retry.............................................................................................................. 11-25 11.23 C901050022 Number of assignment executions for data due to directed retry.............................................................................................................. 11-27 11.24 C901050023 Number of assignment for retry attempts FDD cell for voice channel......................................................................................................... 11-28 11.25 C901050024 Number of assignment executions for data due to directed retry to FDD cell for voice channel .......................................................................... 11-29 11.26 C901050025 Number of assignment for retry attempts FDD cell for data ......... 11-30 11.27 C901050026 Number of assignment executions for data due to directed retry to FDD cell for data........................................................................................ 11-31 11.28 C901050027 Number of assignment for retry attempts TDD cell for voice channel......................................................................................................... 11-32 11.29 C901050028 Number of assignment executions for data due to directed retry to TDD cell for voice channel .......................................................................... 11-34 11.30 C901050029 Number of assignment for retry attempts TDD cell for data ......... 11-35 11.31 C901050030 Number of assignment executions for data due to directed retry to TDD cell for data........................................................................................ 11-36 11.32 C901050031 Assignment unsuccessful due to circuit obstruction .................... 11-37 11.33 C901050032 Assignment unsuccessful due to circuit obstruction unmatched .................................................................................................... 11-38 11.34 C901050033 Assignment unsuccessful due to no valid radio resource ............ 11-39 11.35 C901050034 Assignment unsuccessful due to other causes ........................... 11-40 11.36 C901050035 Number of assignments attempts due to forced release (emergency service) ...................................................................................... 11-41 11.37 C901050036 Number of assignment executions channel due to forced release (emergency service) .......................................................................... 11-42 11.38 C901050037 Number of assignment attempts due to forced handover (emergency service) ...................................................................................... 11-43 11.39 C901050038 Number of assignment executions channel due to forced handover (emergency service) ....................................................................... 11-44 11.40 C901050039 Number of assignments channel due to queuing (emergency service)......................................................................................................... 11-45 11.41 C901050040 Number of assignments for execution channel due to queuing (emergency service) ...................................................................................... 11-46 11.42 C901050041 Number of forced handover target not found (assignment forced handover) ..................................................................................................... 11-47 11.43 C901050042 Number of send forced handover request to lower PRI user (assignment forced handover) ........................................................................ 11-48

XXXI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

11.44 C901050043 Number of received failure from lower PRI user request resource for forced handover (assignment forced handover) ............................ 11-50 11.45 C901050044 Number of lower PRI user handover failure (assignment forced handover) ..................................................................................................... 11-51 11.46 C901050045 Number of time out for wait resource (assignment forced handover) ..................................................................................................... 11-52 11.47 C901050046 Number of forced release target not found (assignment forced release) ........................................................................................................ 11-53 11.48 C901050047 Number of time out for wait resource (assignment forced release) ........................................................................................................ 11-54 11.49 C901050048 Number of get before grab released channel (assignment forced handover) ........................................................................................... 11-55 11.50 C901050049 Number of get before grab released channel(assignment forced release) ........................................................................................................ 11-56 11.51 C901050050 The count of Assignment using FULL IP A-Interface................... 11-57 11.52 C901050051 The count of Assignment using PCM over IP A-Interface ............ 11-58 11.53 C901050052 The count of Assignment using PCM over TDM A-Interface ....... 11-59 11.54 C901050053 The count of Assignment Failure caused by "Requested Codec Type or Codec Configuration not supported".................................................... 11-60 11.55 C901050054 The count of Assignment Failure caused by "Requested Codec Type or Codec Configuration unavailable" ....................................................... 11-61 11.56 C901050055 The count of Assignment Failure caused by "Requested A-Interface Type not supported"...................................................................... 11-62 11.57 C901050056 The count of Assignment Failure caused by "Requested A-Interface Type unavailable" ......................................................................... 11-63 11.58 C901050057 The count of Assignment Failure caused by "Call Identifier already allocated" .......................................................................................... 11-64 11.59 C901050058 The count of Assignment Failure caused by "Requested Redundancy Level not supported" .................................................................. 11-65 11.60 C901050059 The count of Assignment Failure caused by "Call Access Control"......................................................................................................... 11-66 11.61 C901050060 Attempt Number of mode modify for assignment ........................ 11-67 11.62 C901050061 Success Number of mode modify for assignment....................... 11-68 11.63 C901050062 Number of assignments for directed retry attempts for voice channel because of radio ............................................................................... 11-68 11.64 C901050063 Number of assignments for execution for voice channel due to directed retry because of radio ....................................................................... 11-69 11.65 C901050064 Number of assignments for directed retry attempts for data channel because of radio ............................................................................... 11-70

XXXII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

11.66 C901050065 Number of assignments for execution for data channel due to directed retry because of radio ....................................................................... 11-71 11.67 C901050066 Number of assignment success for voice channel due to directed retry ................................................................................................. 11-72 11.68 C901050067 Number of assignment success for data due to directed retry ...... 11-74 11.69 C901050068 Number of assignment success for voice channel due to directed retry to FDD cell................................................................................ 11-75 11.70 C901050069 Number of assignment success for data due to directed retry to FDD cell........................................................................................................ 11-76 11.71 C901050070 Number of assignment success for voice channel due to directed retry to TDD cell................................................................................ 11-77 11.72 C901050071 Number of assignment success for data due to directed retry to TDD cell........................................................................................................ 11-78 11.73 C901050072 Number of assignments success for voice channel due to directed retry because of radio ....................................................................... 11-79 11.74 C901050073 Number of assignments success for data due to directed retry because of radio............................................................................................ 11-80 11.75 C901050074 User/MSC Release Number During Voice TCH/F Assignment ...... 11-82 11.76 C901050075 User/MSC Release Number During Data TCH/F Assignment ...... 11-82 11.77 C901050076 User/MSC Release Number During Voice TCH/H Assignment ................................................................................................... 11-83 11.78 C901050077 User/MSC Release Number During Data TCH/H Assignment ...... 11-83 11.79 C901050078 Number of Voice TCH/F Second Assignment Attempts............... 11-84 11.80 C901050079 Number of Voice TCH/F Second Assignment Success ............... 11-84 11.81 C901050080 Number of Voice TCH/F Second Assignment Failure.................. 11-85 11.82 C901050081 Number of Data TCH/F Second Assignment Attempts................ 11-85 11.83 C901050082 Number of Data TCH/F Second Assignment Success ................ 11-86 11.84 C901050083 Number of Data TCH/F Second Assignment Failure................... 11-86 11.85 C901050084 Number of Voice TCH/H Second Assignment Attempts .............. 11-87 11.86 C901050085 Number of Voice TCH/H Second Assignment Success............... 11-87 11.87 C901050086 Number of Voice TCH/H Second Assignment Failure ................. 11-88 11.88 C901050087 Number of Data TCH/H Second Assignment Attempts ............... 11-88 11.89 C901050088 Number of Data TCH/H Second Assignment Success ................ 11-89 11.90 C901050089 Number of Data TCH/H Second Assignment Failure .................. 11-89 11.91 C901050090 Number of Voice Assignment Failure for Directed Retry.............. 11-90 11.92 C901050091 Number of Data Assignment Failure for Directed Retry............... 11-90 11.93 C901050092 The Number of Forbid Sending Assignment Command During Releasing...................................................................................................... 11-91 11.94 C901050093 Number of Reassignment Attempts........................................... 11-91
XXXIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

11.95 C901050094 Number of Reassignment Success ........................................... 11-91 11.96 C901050095 Number of Reassignment Failure.............................................. 11-92

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 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
XXXIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 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 12.48 C901060068 Number of TCH/H handover attempts during handover due to TA increase ...................................................................................................12-51 12.49 C901060069 Number of TCH/H handover attempts during handover due to TA decrease..................................................................................................12-52
XXXV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 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 12.62 C901060082 Attempts of handover on TCH/F caused by power adjustment ....................................................................................................12-63 12.63 C901060083 Attempts of handover on TCH/H caused by power adjustment ....................................................................................................12-64 12.64 C901060084 Attempts of handover on TCH/F caused by local switch .............12-65 12.65 C901060085 Attempts of handover on TCH/H caused by local switch .............12-65 12.66 C901060086 Attempts of handover on TCH/F caused by reducing band resources of IPAbis........................................................................................12-65 12.67 C901060087 Attempts of handover on TCH/H because of MASTERPWR_ALM from TRX .......................................................................12-66 12.68 C901060088 Attempts of handover on TCH/F because of MASTERPWR_ALM from TRX ......................................................................................................12-67 12.69 C901060089 Number of handover attempts due to directed retry for PBGT ......12-67 12.70 C901060090 Number of SDCCH handover attempts due to DL quality rapid drop..............................................................................................................12-68 12.71 C901060091 Number of TCH/F handover attempts due to DL quality rapid drop..............................................................................................................12-69

XXXVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

12.72 C901060092 Number of TCH/H handover attempts due to DL quality rapid drop..............................................................................................................12-70 12.73 C901060095 Number of TCH/F Handover Attempts Due to Dynamic Channel Move ............................................................................................................12-70 12.74 C901060096 Number of TCH/H Handover Attempts Due to Dynamic Channel Move ............................................................................................................12-71 12.75 C901060100 Number of MSC-Controlled Outgoing Handover Attempts Due to PBGT........................................................................................................12-72 12.76 C901060101 Number of MSC-Controlled Incoming Handover Attempts Due to PBGT........................................................................................................12-72 12.77 C901060102 Number of Inter BSC Incoming Handover Attempts Due to Large TA .......................................................................................................12-73 12.78 C901060103 Number of Inner BSC Incoming Handover Attempts Due to Large TA .......................................................................................................12-73 12.79 C901060104 Number of Dual Frequency Traffic Handover Attempts on TCH/F...........................................................................................................12-74 12.80 C901060105 Number of Dual Frequence Traffic Handover Attempts on TCH/H ..........................................................................................................12-74

Chapter 13 RMM Call Drop Measurement .............................................. 13-1

13.1 Overview ....................................................................................................... 13-6 13.2 C901070001 Number of SDCCH drops due to loss of contact with RANA .......... 13-7 13.3 C901070002 Number of SDCCH drops due to radio link failure ......................... 13-8 13.4 C901070003 Number of SDCCH drops due to LAPD link failure ........................ 13-9 13.5 C901070004 Number of SDCCH drops due to OMC-R forced release ..............13-10 13.6 C901070005 Number of SDCCH drops due to forced release by other calls ......13-10 13.7 C901070007 Number of SDCCH drops due to other failure .............................. 13-11 13.8 C901070008 Number of signaling TCH/F drops due to loss of contact with RANA ...........................................................................................................13-12 13.9 C901070009 Number of signaling TCH/F drops due to radio link failure ............13-13 13.10 C901070010 Number of signaling TCH/F drops due to LAPD link failure .........13-14 13.11 C901070011 Number of signaling TCH/F drops due to OMC-R forced release..........................................................................................................13-15 13.12 C901070012 Number of signaling TCH/F drops due to forced release by other calls .....................................................................................................13-16 13.13 C901070014 Number of signaling TCH/F drops due to other failure ................13-17 13.14 C901070015 Number of voice TCH/F drops due to loss of contact with RANA ...........................................................................................................13-18 13.15 C901070017 Number of voice TCH/F drops due to LAPD link failure ..............13-19 13.16 C901070018 Number of voice TCH/F drops due to OMC-R forced release ......13-21

XXXVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

13.17 C901070019 Number of voice TCH/F drops due to forced release by other calls..............................................................................................................13-22 13.18 C901070021 Number of voice TCH/F drops due to other failure .....................13-24 13.19 C901070022 Number of data TCH/F drops due to loss of contact with RANA ...........................................................................................................13-24 13.20 C901070023 Number of data TCH/F drops due to radio link failure .................13-26 13.21 C901070024 Number of data TCH/F drops due to LAPD link failure................13-28 13.22 C901070025 Number of data TCH/F drops due to OMC-R forced release .......13-29 13.23 C901070026 Number of data TCH/F drops due to forced release by other calls..............................................................................................................13-31 13.24 C901070028 Number of data TCH/F drops due to other failure.......................13-32 13.25 C901070029 Number of signaling TCH/H drops due to loss of contact with RANA ...........................................................................................................13-33 13.26 C901070030 Number of signaling TCH/H drops due to radio link failure ..........13-34 13.27 C901070031 Number of signaling TCH/H drops due to LAPD link failure.........13-35 13.28 C901070032 Number of signaling TCH/H drops due to OMC-R forced release..........................................................................................................13-36 13.29 C901070033 Number of signaling TCH/H drops due to forced release by other calls .....................................................................................................13-37 13.30 C901070035 Number of signaling TCH/H drops due to other failure................13-38 13.31 C901070036 Number of voice TCH/H drops due to loss of contact with RANA ...........................................................................................................13-39 13.32 C901070038 Number of voice TCH/H drops due to LAPD link failure ..............13-41 13.33 C901070039 Number of voice TCH/H drops due to OMC-R forced release ......13-42 13.34 C901070040 Number of voice TCH/H drops due to forced release by other calls..............................................................................................................13-44 13.35 C901070042 Number of voice TCH/H drops due to other failure .....................13-45 13.36 C901070043 Number of data TCH/H drops due to loss of contact with RANA ...........................................................................................................13-46 13.37 C901070044 Number of data TCH/H drops due to radio link failure.................13-48 13.38 C901070045 Number of data TCH/H drops due to LAPD link failure ...............13-49 13.39 C901070046 Number of data TCH/H drops due to OMC-R forced release.......13-51 13.40 C901070047 Number of data TCH/H drops due to forced release by other calls..............................................................................................................13-52 13.41 C901070049 Number of data TCH/H drops due to other failure ......................13-54 13.42 C901070053 Number of SDCCH link failures ................................................13-54 13.43 C901070054 Number of TCH/F link failures...................................................13-56 13.44 C901070055 Number of TCH/H link failures ..................................................13-58

XXXVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

13.45 C901070056 Number of RANA link releases due to other cause on SDCCH.........................................................................................................13-59 13.46 C901070057 Number of RANA link releases due to other cause on TCH/F ......13-60 13.47 C901070058 Number of RANA link releases due to other cause on TCH/H ......13-61 13.48 C901070059 Number of SDCCH short messages drops ................................13-62 13.49 C901070060 Number of TCH/F short messages drops ..................................13-63 13.50 C901070061 Number of TCH/H short messages drops ..................................13-63 13.51 C901070062 Number of TCH/F drops due to CS channel is forced release by PS ................................................................................................................13-64 13.52 C901070063 Number of TCH/H drops due to CS channel is forced release by PS ................................................................................................................13-65 13.53 C901070064 Number of SDCCH drops due to eMLPP forced handover..........13-65 13.54 C901070065 Number of signaling TCH/F drops due to eMLPP forced handover.......................................................................................................13-66 13.55 C901070066 Number of voice TCH/F drops due to eMLPP forced handover.......................................................................................................13-67 13.56 C901070067 Number of data TCH/F drops due to eMLPP forced handover ......13-68 13.57 C901070068 Number of sigaling TCH/H drops due to eMLPP forced handover.......................................................................................................13-69 13.58 C901070069 Number of voice TCH/H drops due to eMLPP forced handover.......................................................................................................13-70 13.59 C901070070 Number of data TCH/H drops due to eMLPP forced handover.......................................................................................................13-71 13.60 C901070071 Bad quality of UL receiving (On SDCCH) ..................................13-72 13.61 C901070072 Bad quality of DL receiving (On SDCCH) ..................................13-73 13.62 C901070073 Lower electrical level of UL (On SDCCH) ..................................13-74 13.63 C901070074 Lower electrical level of DL (On SDCCH) ..................................13-75 13.64 C901070075 Number of signaling drops due to TA too far (On SDCCH)..........13-76 13.65 C901070076 Reasons of the other radios (On SDCCH) .................................13-77 13.66 C901070077 Bad quality of UL receiving (On TCH/F) ....................................13-78 13.67 C901070078 Bad quality of DL receiving (On TCH/F) ....................................13-79 13.68 C901070079 Lower electrical level of UL (On TCH/F) ....................................13-80 13.69 C901070080 Lower electrical level of DL (On TCH/F) ....................................13-82 13.70 C901070081 Number of signaling drops due to TA too far (On TCH/F)............13-83 13.71 C901070082 Reasons of the other radios (On TCH/F) ...................................13-85 13.72 C901070083 Bad quality of UL receiving (On TCH/H) ....................................13-86 13.73 C901070084 Bad quality of DL receiving (On TCH/H) ....................................13-88 13.74 C901070085 Lower electrical level of UL (On TCH/H) ....................................13-89 13.75 C901070086 Lower electrical level of DL (On TCH/H) ....................................13-91
XXXIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

13.76 C901070087 Number of signaling drops due to TA too far (On TCH/H) ...........13-92 13.77 C901070088 Reasons of the other radios (On TCH/H)...................................13-94 13.78 C901070089 The Count of Drop Call caused by "IP Resource Reset" .............13-95 13.79 C901070090 Number of FR_V1 radio link fail ................................................13-96 13.80 C901070091 Number of FR_V2 radio link fail ................................................13-97 13.81 C901070092 Number of FR_V3 radio link fail ................................................13-97 13.82 C901070093 Number of HR_V1 radio link fail................................................13-98 13.83 C901070094 Number of HR_V3 radio link fail................................................13-98 13.84 C901070095 Number of signaling TCH/F drops due to BIPB Active/Standby Changeover ..................................................................................................13-99 13.85 C901070096 Number of voice TCH/F drops due to BIPB Active/Standby Changeover ..................................................................................................13-99 13.86 C901070097 Number of data TCH/F drops due to BIPB Active/Standby Changeover ................................................................................................13-100 13.87 C901070098 Number of signaling TCH/H drops due to BIPB Active/Standby Changeover ................................................................................................13-100 13.88 C901070099 Number of voice TCH/H drops due to BIPB Active/Standby Changeover ................................................................................................13-100 13.89 C901070100 Number of data TCH/H drops due to BIPB Active/Standby Changeover ................................................................................................13-101 13.90 C901070101 Number of SDCCH drops due to LAPD Active/Standby Changeover ................................................................................................13-101 13.91 C901070102 Number of voice TCH/F drops due to LAPD Active/Standby Changeover ................................................................................................13-102 13.92 C901070103 Number of data TCH/F drops due to LAPD Active/Standby Changeover ................................................................................................13-102 13.93 C901070104 Number of signaling TCH/F drops due to LAPD Active/Standby Changeover ................................................................................................13-102 13.94 C901070105 Number of voice TCH/H drops due to LAPD Active/Standby Changeover ................................................................................................13-103 13.95 C901070106 Number of data TCH/H drops due to LAPD Active/Standby Changeover ................................................................................................13-103 13.96 C901070107 Number of signaling TCH/H drops due to LAPD Active/Standby Changeover ................................................................................................13-104 13.97 C901070108 Number of voice TCH/F drops due to handover fail for power adjustment ..................................................................................................13-104 13.98 C901070109 Number of voice TCH/H drops due to handover fail for power adjustment ..................................................................................................13-104 13.99 C901070110 Number of SDCCH drops due to BIPB Active/Standby Changeover ................................................................................................13-105
XL SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

13.100 C901070111 Number of SDCCH drops due to BTS failure..........................13-105 13.101 C901070112 Number of signaling TCH/F drops due to BTS failure..............13-106 13.102 C901070113 Number of voice TCH/F drops due to BTS failure ...................13-107 13.103 C901070114 Number of data TCH/F drops due to BTS failure ....................13-108 13.104 C901070115 Number of signaling TCH/H drops due to BTS failure ............. 13-110 13.105 C901070116 Number of voice TCH/H drops due to BTS failure................... 13-111 13.106 C901070117 Number of data TCH/H drops due to BTS failure .................... 13-112 13.107 C901070118 Call Drop by Releasing Local Switch ..................................... 13-113 13.108 C901070119 Number of FR_V4 Radio Link Fail ......................................... 13-114 13.109 C901070120 Number of FR_V5 Radio Link Fail......................................... 13-115 13.110 C901070121 Number of HR_V4 Radio Link Fail......................................... 13-115 13.111 C901070122 Call Drop Due To Emergency Call Preemption on TCH/F ........ 13-116 13.112 C901070123 Call Drop Due to Emergency Call Preemption on TCH/H ........ 13-117 13.113 C901070126 Number of drop call on SDCCH due to IMSI Exception........... 13-117 13.114 C901070127 Number of drop call on sig TCH/F due to IMSI Exception........ 13-118 13.115 C901070128 Number of drop call on voice TCH/F due to IMSI Exception...... 13-118 13.116 C901070129 Number of drop call on data TCH/F due to IMSI Exception...... 13-119 13.117 C901070130 Number of drop call on sig TCH/H due to IMSI Exception ....... 13-119 13.118 C901070131 Number of drop call on voice TCH/H due to IMSI Exception ......13-120 13.119 C901070132 Number of drop call on data TCH/H due to IMSI Exception ......13-120 13.120 C901070133 Number of Drop Call When TCH Assign ................................13-121 13.121 C901070134 Number of Drop Call on TCH................................................13-121 13.122 C901070135 Number of Drop Call on TCH(exclude sms drop after hang-off) .....................................................................................................13-122 13.123 C901070136 Number of SDCCH Drops Due to Intra-Cell Handover Failure ........................................................................................................13-122 13.124 C901070137 Number of Speech TCH/F Drops Due to Intra-Cell Handover Failure ........................................................................................................13-123 13.125 C901070138 Number of Data TCH/F Drops Due to Intra-Cell Handover Failure ........................................................................................................13-123 13.126 C901070139 Number of Signaling TCH/F Drops Due to Intra-Cell Handover Failure ........................................................................................................13-124 13.127 C901070140 Number of Speech TCH/H Drops Due to Intra-Cell Handover Failure ........................................................................................................13-124 13.128 C901070141 Number of Data TCH/H Drops Due to Intra-Cell Handover Failure ........................................................................................................13-125 13.129 C901070142 Number of Signaling TCH/H Drops Due to Intra-Cell Handover Failure ........................................................................................................13-125

XLI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

13.130 C901070143 Number of SDCCH Drops Due to Inter-Cell Handover Failure ........................................................................................................13-126 13.131 C901070144 Number of Speech TCH/F Drops Due to Inter-Cell Handover Failure ........................................................................................................13-126 13.132 C901070145 Number of Data TCH/F Drops Due to Inter-Cell Handover Failure ........................................................................................................13-127 13.133 C901070146 Number of Signaling TCH/F Drops Due to Inter-Cell Handover Failure ........................................................................................................13-127 13.134 C901070147 Number of Speech TCH/H Drops Due to Inter-Cell Handover Failure ........................................................................................................13-128 13.135 C901070148 Number of Data TCH/H Drops Due to Inter-Cell Handover Failure ........................................................................................................13-128 13.136 C901070149 Number of Signaling TCH/H Drops Due to Inter-Cell Handover Failure ........................................................................................................13-129 13.137 C901070150 Number of SDCCH Drops Due to Outgoing Handover Failure ........................................................................................................13-129 13.138 C901070151 Number of Speech TCH/F Drops Due to Outgoing Handover Failure ........................................................................................................13-130 13.139 C901070152 Number of Data TCH/F Drops Due to Outgoing Handover Failure ........................................................................................................13-130 13.140 C901070153 Number of Signaling TCH/F Drops Due to Outgoing Handover Failure ........................................................................................................13-131 13.141 C901070154 Number of Speech TCH/H Drops Due to Outgoing Handover Failure ........................................................................................................13-131 13.142 C901070155 Number of Data TCH/H Drops Due to Outgoing Handover Failure ........................................................................................................13-132 13.143 C901070156 Number of Signaling TCH/H Drops Due to Outgoing Handover Failure ........................................................................................................13-132 13.144 C901070157 Number of Speech TCH/F Drops Due to Subcell 1 to Subcell 2 Handover Failure .........................................................................................13-133 13.145 C901070158 Number of Data TCH/F Drops Due to Subcell 1 to Subcell 2 Handover Failure .........................................................................................13-133 13.146 C901070159 Number of Signaling TCH/F Drops Due to Subcell 1 to Subcell 2 Handover Failure ......................................................................................13-134 13.147 C901070160 Number of Speech TCH/H Drops Due to Subcell 1 to Subcell 2 Handover Failure ......................................................................................13-134 13.148 C901070161 Number of Data TCH/H Drops Due to Subcell 1 to Subcell 2 Handover Failure .........................................................................................13-135 13.149 C901070162 Number of Signaling TCH/H Drops Due to Subcell 1 to Subcell 2 Handover Failure ......................................................................................13-135

XLII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

13.150 C901070163 Number of Speech TCH/F Drops Due to Subcell 2 to Subcell 1 Handover Failure .........................................................................................13-136 13.151 C901070164 Number of Data TCH/F Drops Due to Subcell 2 to Subcell 1 Handover Failure .........................................................................................13-136 13.152 C901070165 Number of Signaling TCH/F Drops Due to Subcell 2 to Subcell 1 Handover Failure ......................................................................................13-137 13.153 C901070166 Number of Speech TCH/H Drops Due to Subcell 2 to Subcell 1 Handover Failure ......................................................................................13-137 13.154 C901070167 Number of Data TCH/H Drops Due to Subcell 2 to Subcell 1 Handover Failure .........................................................................................13-138 13.155 C901070168 Number of Signaling TCH/H Drops Due to Subcell 2 to Subcell 1 Handover Failure ......................................................................................13-138 13.156 C901070172 Number of Data TCH/F Drops ..............................................13-139 13.157 C901070173 Number of Data TCH/H Drops ..............................................13-139 13.158 C901070175 Number of Drop Call on SDCCH Due to BCCH Exchange ......13-139 13.159 C901070176 Number of Drop Call on SDCCH Due to Block Channel or Abis Resource ....................................................................................................13-140 13.160 C901070177 Number of Drop Call on SDCCH Due to SD Change ..............13-140 13.161 C901070178 Number of Drop Call on SDCCH Due to Global Reset............13-140 13.162 C901070179 Number of Drop Call on SDCCH Due to Ring BTS Turn Over ...........................................................................................................13-141 13.163 C901070180 Number of Drop Call on TCH/F Due to IPA Board Fault ..........13-141 13.164 C901070181 Number of Drop Call on TCH/F Due to IPA Board Resource Fault ...........................................................................................................13-142 13.165 C901070182 Number of Drop Call on TCH/F Due to BCCH Exchange ........13-142 13.166 C901070183 Number of Drop Call on TCH/F Due to Block Channel or Abis Resource ....................................................................................................13-142 13.167 C901070184 Number of Drop Call on TCH/F Due to SD Change ................13-143 13.168 C901070185 Number of Drop Call on TCH/F Due to Circuit Fault ...............13-143 13.169 C901070186 Number of Drop Call on TCH/F Due to IFTA Cause................13-144 13.170 C901070187 Number of Drop Call on TCH/F Due to TDMA Board Fault ......13-144 13.171 C901070188 Number of Drop Call on TCH/F Due to iTC Board Fault..........13-144 13.172 C901070189 Number of Drop Call on TCH/F Due to iTC Board Resource Fault ...........................................................................................................13-145 13.173 C901070190 Number of Drop Call on TCH/F Due to TC Board Fault...........13-145 13.174 C901070191 Number of Drop Call on TCH/F Due to TC Board Resource Fault ...........................................................................................................13-146 13.175 C901070192 Number of Drop Call on TCH/F Due to Global Reset ..............13-146 13.176 C901070193 Number of Drop Call on TCH/F Due to PS Preempt ...............13-146

XLIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

13.177 C901070194 Number of Drop Call on TCH/F Due to Reassign Fail .............13-147 13.178 C901070195 Number of Drop Call on TCH/F Due to Ring BTS Turn Over ...........................................................................................................13-147 13.179 C901070198 Number of Drop Call on TCH/H Due to IPA Board Fault .........13-147 13.180 C901070199 Number of Drop Call on TCH/H Due to IPA Board Resource Fault ...........................................................................................................13-148 13.181 C901070200 Number of Drop Call on TCH/H Due to BCCH Exchange........13-148 13.182 C901070201 Number of Drop Call on TCH/H Due to Block Channel or Abis Resource ....................................................................................................13-149 13.183 C901070202 Number of Drop Call on TCH/H Due to SD Change................13-149 13.184 C901070203 Number of Drop Call on TCH/H Due to Circuit Fault ...............13-149 13.185 C901070204 Number of Drop Call on TCH/H Due to IFTA Cause ...............13-150 13.186 C901070205 Number of Drop Call on TCH/H Due to TDMA Board Fault ......13-150 13.187 C901070206 Number of Drop Call on TCH/H Due to iTC Board Fault .........13-151 13.188 C901070207 Number of Drop Call on TCH/H Due to iTC Board Resource Fault ...........................................................................................................13-151 13.189 C901070208 Number of Drop Call on TCH/H Due to TC Board Fault ..........13-151 13.190 C901070209 Number of Drop Call on TCH/H Due to TC Board Resource Fault ...........................................................................................................13-152 13.191 C901070210 Number of Drop Call on TCH/H Due to Global Reset .............13-152 13.192 C901070211 Number of Drop Call on TCH/H Due to PS Preempt ...............13-152 13.193 C901070212 Number of Drop Call on TCH/H Due to Reassign Fail.............13-153 13.194 C901070213 Number of Drop Call on TCH/H Due to Ring BTS Turn Over ...........................................................................................................13-153 13.195 C901070216 Number of Drops Due to Interf UL Handover .........................13-154 13.196 C901070217 Number of Drops Due to Interf DL Handover .........................13-154 13.197 C901070218 Number of Drops Due to QUAL UL Handover ........................13-154 13.198 C901070219 Number of Drops Due to QUAL DL Handover ........................13-155 13.199 C901070220 Number of Drops Due to LEVEL UL Handover.......................13-155 13.200 C901070221 Number of Drops Due to LEVEL DL Handover.......................13-155 13.201 C901070222 Number of Drops Due to RAPID UL Handover.......................13-156 13.202 C901070223 Number of Drops Due to PBGT Handover .............................13-156 13.203 C901070224 Number of Drops Due to MACRO to MICRO Handover ..........13-156 13.204 C901070225 Number of Drops Due to SUB Cell 1 to SUB Cell 2 Handover ....................................................................................................13-157 13.205 C901070226 Number of Drops Due to SUB Cell 2 to SUB Cell 1 Handover ....................................................................................................13-157 13.206 C901070227 Number of Drops Due to PREEMPT Handover ......................13-157 13.207 C901070228 Number of Drops Due to TRAFFIC Handover ........................13-158
XLIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

13.208 C901070229 Number of Drops Due to DLRAPID Handover........................13-158 13.209 C901070230 Number of Drops Due to HRFR Handover .............................13-158 13.210 C901070231 Number of Drops Due to RAPIDQUAL Handover ...................13-159

Chapter 14 Radio Resource Availability Measurement ........................ 14-1

14.1 Overview ....................................................................................................... 14-2 14.2 C901080003 Maximum number of busy SDCCH .............................................. 14-2 14.3 C901080004 Average number of busy SDCCH ................................................ 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-11 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.14 C901080025 TCH/F busy time(SpeechVer2) .................................................14-16 14.15 C901080026 TCH/F busy time(SpeechVer3) .................................................14-17 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 14.21 C901080045 TCH/H Busy Time (SpeechVer4) ..............................................14-23 14.22 C901080046 TCH/F Busy Time (SpeechVer4)...............................................14-24 14.23 C901080047 TCH/F Busy Time (SpeechVer5)...............................................14-25 14.24 C901080048 TRX Number of Configured BaseBand Resources .....................14-25 14.25 C901080049 TRX Number of Non-Configured BaseBand Resources..............14-26 14.26 C901080050 Success Number of Configured BaseBand Resource.................14-26 14.27 C901080051 Conflict Number of Configured Baseband Resource ..................14-27 14.28 C901080052 Number of Releasing BaseBand Resource................................14-27 14.29 C901080053 SDCCH Busy Time (Speech)....................................................14-28 14.30 C901080054 SDCCH Busy Time (SMS)........................................................14-28 14.31 C901080055 Duration of Intelligent Cell Power Off.........................................14-28 14.32 C901080058 1800M TCH/F Busy Time .........................................................14-29 14.33 C901080059 1800M TCH/H Busy Time.........................................................14-29

XLV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement......................................... 15-1

15.1 Overview ....................................................................................................... 15-9 15.2 C901090001 Number of BSC-controlled inter-cell outgoing handover attempts......................................................................................................... 15-9 15.3 C901090004 Number of MSC-controlled outgoing handover attempts...............15-10 15.4 C901090005 Number of MSC-controlled outgoing handover request failures due to unclear factors .................................................................................... 15-11 15.5 C901090006 Number of MSC-controlled outgoing handover request failures due to unavailable ground resource ................................................................15-12 15.6 C901090007 Number of MSC-controlled outgoing handover request failures due to unavailable radio resource ...................................................................15-13 15.7 C901090008 Number of MSC-controlled outgoing handover request failures due to other factors........................................................................................15-14 15.8 C901090011 Number of BSC-controlled inter-cell incoming handover attempts........................................................................................................15-15 15.9 C901090013 Number of BSC-controlled incoming handover attempts due to forced release ...............................................................................................15-16 15.10 C901090015 Number of BSC-controlled incoming handover attempts due to queue ...........................................................................................................15-18 15.11 C901090017 Number of BSC-controlled incoming handover attempts due to forced handover ............................................................................................15-19 15.12 C901090020 BSC-controlled incoming handover time due to queue ...............15-20 15.13 C901090021 Queue number of BSC-controlled incoming handover ................15-22 15.14 C901090022 BSC-controlled incoming handover success time due to queue ...........................................................................................................15-24 15.15 C901090023 Number of BSC-controlled incoming handover success due to queue ...........................................................................................................15-25 15.16 C901090024 Number of MSC-controlled incoming handover attempts ............15-26 15.17 C901090025 Number of incoming handover failure due to circuit block ...........15-27 15.18 C901090026 Number of incoming handover failure due to circuit group mismatch ......................................................................................................15-28 15.19 C901090027 Number of incoming handover failure due to unavailable radio resource .......................................................................................................15-29 15.20 C901090028 Number of incoming handover failure due to other factors ..........15-30 15.21 C901090030 Number of MSC-controlled incoming handover attempts due to forced release ...............................................................................................15-31 15.22 C901090032 Number of MSC-controlled incoming handover attempts due to queue ...........................................................................................................15-32 15.23 C901090034 Number of MSC-controlled incoming handover attempts due to forced handover ............................................................................................15-33
XLVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

15.24 C901090037 MSC-controlled incoming handover time due to queue...............15-34 15.25 C901090038 Queue number of MSC-controlled incoming handover ...............15-37 15.26 C901090039 MSC-controlled incoming handover success time due to queue ...........................................................................................................15-39 15.27 C901090040 Number of MSC-controlled incoming handover success due to queue ...........................................................................................................15-40 15.28 C901090041 Number of incoming handover attempts from the same layer and frequency ...............................................................................................15-41 15.29 C901090042 Number of incoming handover success from the same layer and frequency ...............................................................................................15-42 15.30 C901090043 Number of outgoing handover attempts to the same layer and frequency......................................................................................................15-43 15.31 C901090044 Number of outgoing handover success to the same layer and frequency......................................................................................................15-44 15.32 C901090045 Number of incoming handover attempts from undefined layer to the same frequency .......................................................................................15-45 15.33 C901090046 Number of incoming handover success from undefined layer to the same frequency .......................................................................................15-46 15.34 C901090047 Number of outgoing handover attempts from undefined layer to the same frequency .......................................................................................15-47 15.35 C901090048 Number of outgoing handover success from undefined layer to the same frequency .......................................................................................15-48 15.36 C901090049 Number of incoming handover attempts from undefined layer (GSM900) to current layer (GSM1800)............................................................15-49 15.37 C901090052 Number of outgoing handover attempts from current layer (GSM900) to undefined layer (GSM1800)........................................................15-50 15.38 C901090053 Number of outgoing handover from current layer (GSM900) to undefined layer (GSM1800)............................................................................15-51 15.39 C901090054 Number of outgoing handover success from current layer (GSM900) to undefined layer (GSM1800)........................................................15-52 15.40 C901090055 Number of incoming handover attempts from undefined layer (GSM1800) to current layer (GSM900)............................................................15-53 15.41 C901090058 Number of outgoing handover attempts from undefined layer (GSM1800) to current layer (GSM900)............................................................15-54 15.42 C901090059 Number of outgoing handover from undefined layer (GSM1800) to current layer (GSM900) ..............................................................................15-55 15.43 C901090060 Number of outgoing handover success from undefined layer (GSM1800) to current layer (GSM900)............................................................15-56 15.44 C901090061 Number of incoming handover attempts from upper layer to the same frequency.............................................................................................15-57

XLVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

15.45 C901090062 Number of incoming handover success from upper layer to the same frequency.............................................................................................15-58 15.46 C901090063 Number of outgoing handover attempts from the same frequency to upper layer.................................................................................15-59 15.47 C901090064 Number of outgoing handover success from the same frequency to upper layer.................................................................................15-60 15.48 C901090065 Number of incoming handover attempts from lower layer to the same frequency.............................................................................................15-61 15.49 C901090066 Number of incoming handover success from lower layer to the same frequency.............................................................................................15-62 15.50 C901090067 Number of outgoing handover attempts from the same frequency to lower layer .................................................................................15-63 15.51 C901090068 Number of outgoing handover success from the same frequency to lower layer .................................................................................15-64 15.52 C901090069 Number of incoming handover attempts from the same layer GSM900 to GSM1800....................................................................................15-65 15.53 C901090072 Number of outgoing handover attempts to the same layer GSM900 to GSM1800....................................................................................15-66 15.54 C901090073 Number of outgoing handover to the same layer GSM900 to GSM1800 .....................................................................................................15-67 15.55 C901090074 Number of outgoing handover success to the same layer GSM900 to GSM1800....................................................................................15-68 15.56 C901090075 Number of incoming handover attempts from GSM900 to GSM1800 from the upper layer.......................................................................15-69 15.57 C901090078 Number of outgoing handover attempts from GSM900 to GSM1800 to the upper layer...........................................................................15-70 15.58 C901090079 Number of outgoing handover from GSM900 to GSM1800 to the upper layer ..............................................................................................15-71 15.59 C901090080 Number of outgoing handover success from GSM900 to GSM1800 to the upper layer...........................................................................15-72 15.60 C901090081 Number of incoming handover attempts from GSM900 to GSM1800 from the lower layer .......................................................................15-73 15.61 C901090084 Number of outgoing handover attempts from GSM900 to GSM1800 to the lower layer ...........................................................................15-74 15.62 C901090085 Number of outgoing handover from GSM900 to GSM1800 to the lower layer...............................................................................................15-75 15.63 C901090086 Number of outgoing handover success from GSM900 to GSM1800 to the lower layer ...........................................................................15-76 15.64 C901090087 Number of incoming handover attempts from GSM1800 to GSM900 from the same layer .........................................................................15-77

XLVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

15.65 C901090090 Number of outgoing handover attempts from GSM1800 to GSM900 to the same layer.............................................................................15-78 15.66 C901090091 Number of outgoing handover from GSM1800 to GSM900 to the same layer...............................................................................................15-79 15.67 C901090092 Number of outgoing handover success from GSM1800 to GSM900 to the same layer.............................................................................15-80 15.68 C901090093 Number of incoming handover attempts from GSM1800 to GSM900 from the upper layer.........................................................................15-81 15.69 C901090096 Number of outgoing handover attempts from GSM1800 to GSM900 to the upper layer ............................................................................15-82 15.70 C901090097 Number of outgoing handover from GSM1800 to GSM900 to the upper layer ..............................................................................................15-83 15.71 C901090098 Number of outgoing handover success from GSM1800 to GSM900 to the upper layer ............................................................................15-84 15.72 C901090099 Number of incoming handover attempts from GSM1800 to GSM900 from the lower layer .........................................................................15-85 15.73 C901090102 Number of outgoing handover attempts from GSM1800 to GSM900 to the lower layer .............................................................................15-86 15.74 C901090103 Number of outgoing handover from GSM1800 to GSM900 to the lower layer...............................................................................................15-87 15.75 C901090104 Number of outgoing handover success from GSM1800 to GSM900 to the lower layer .............................................................................15-88 15.76 C901090105 Number of intra-cell handover attempts.....................................15-89 15.77 C901090108 Number of intra-cell inner-circle-to-outer-circle handover attempts........................................................................................................15-90 15.78 C901090109 Number of intra-cell inner-circle-to-outer-circle handover success ........................................................................................................15-91 15.79 C901090110 Number of intra-cell outer-circle-to-inner-circle handover attempts........................................................................................................15-92 15.80 C901090111 Number of intra-cell outer-circle-to-inner-circle handover success ........................................................................................................15-93 15.81 C901090112 Number of intra-cell inner-circle-to-inner-circle handover attempts........................................................................................................15-94 15.82 C901090113 Number of intra-cell inner-circle-to-inner-circle handover success ........................................................................................................15-95 15.83 C901090114 Number of intra-cell outer-circle-to-outer-circle handover attempts........................................................................................................15-96 15.84 C901090115 Number of intra-cell outer-circle-to-outer-circle handover success ........................................................................................................15-97 15.85 C901090116 Number of handover attempts from 2G to 3G.............................15-98 15.86 C901090117 Number of handover from 2G to 3G ..........................................15-99
XLIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

15.87 C901090118 Number of handover success from 2G to 3G ...........................15-100 15.88 C901090119 Number of handover attempts from 3G to 2G...........................15-101 15.89 C901090120 Number of handover from 3G to 2G ........................................15-102 15.90 C901090121 Number of handover success from 3G to 2G ...........................15-102 15.91 C901090122 Number of intra-cell handover attempts from TCH/F ................15-103 15.92 C901090123 Number of intra-cell TCH/F-to-TCH/F handover .......................15-104 15.93 C901090124 Number of intra-cell TCH/F-to-TCH/F handover success ..........15-105 15.94 C901090125 Number of intra-cell TCH/F-to-TCH/H handover.......................15-106 15.95 C901090126 Number of intra-cell TCH/F-to-TCH/H handover success..........15-107 15.96 C901090127 Number of intra-cell handover attempts from TCH/H ................15-108 15.97 C901090128 Number of intra-cell TCH/H-to-TCH/F handover.......................15-109 15.98 C901090129 Number of intra-cell TCH/H-to-TCH/F handover success.......... 15-110 15.99 C901090130 Number of intra-cell TCH/H-to-TCH/H handover ...................... 15-111 15.100 C901090131 Number of intra-cell TCH/H-to-TCH/H handover success ....... 15-112 15.101 C901090132 Number of inter-cell handover attempts from TCH/F............... 15-113 15.102 C901090133 Number of inter-cell TCH/F-to-TCH/F handover ..................... 15-114 15.103 C901090134 Number of inter-cell TCH/F-to-TCH/F handover success ........ 15-115 15.104 C901090135 Number of inter-cell TCH/F-to-TCH/H handover..................... 15-116 15.105 C901090136 Number of inter-cell TCH/F-to-TCH/H handover success........ 15-117 15.106 C901090137 Number of inter-cell handover attempts from TCH/H .............. 15-118 15.107 C901090138 Number of inter-cell TCH/H-to-TCH/F handover..................... 15-119 15.108 C901090139 Number of inter-cell TCH/H-to-TCH/F handover success........15-120 15.109 C901090140 Number of inter-cell TCH/H-to-TCH/H handover ....................15-121 15.110 C901090141 Number of inter-cell TCH/H-to-TCH/H handover success........15-122 15.111 C901090142 Total dual-band outgoing handover attempts ..........................15-123 15.112 C901090145 Number of dual band incoming handover attempts .................15-124 15.113 C901090148 Number of intra-cell invalid handovers ...................................15-125 15.114 C901090149 Number of BSC-controlled inter-cell incoming handover attempts due to forced release (emergency service) ......................................15-126 15.115 C901090150 Number of BSC-controlled inter-cell incoming handover (forced release) (emergency service) ............................................................15-127 15.116 C901090151 Number of BSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service) ...................................15-128 15.117 C901090152 Number of BSC-controlled inter-cell incoming handover (forced handover) (emergency service) .........................................................15-129 15.118 C901090153 Number of BSC-controlled inter-cell incoming handover attempts due to queue (emergency service) ..................................................15-131

L SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

15.119 C901090154 Number of BSC-controlled inter-cell incoming handover (queue) (emergency service) ........................................................................15-132 15.120 C901090155 Number of MSC-controlled incoming handover attempts due to forced release (emergency service)...........................................................15-133 15.121 C901090156 Number of MSC-controlled incoming handover (forced release) (emergency service) .......................................................................15-134 15.122 C901090157 Number of MSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service) ...................................15-135 15.123 C901090158 Number of MSC-controlled incoming handover (forced release) (emergency service) .......................................................................15-136 15.124 C901090159 Number of MSC-controlled incoming handover attempts due to queue (emergency service) ......................................................................15-137 15.125 C901090160 Number of MSC-controlled incoming handover (queue) (emergency service) ....................................................................................15-138 15.126 C901090161 Number of forced handover target not found (BSC-controlled inter-cell handover due to forced handover)...................................................15-139 15.127 C901090162 Number of send forced handover request to lower PRI user (BSC-controlled inter-cell handover due to forced handover) ..........................15-140 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-141 15.129 C901090164 Number of lower PRI user handover failure (BSC-controlled inter-cell handover due to forced handover)...................................................15-143 15.130 C901090165 Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced handover) ..........................15-144 15.131 C901090166 Number of forced release target not found (BSC-controlled inter-cell handover due to forced release)......................................................15-145 15.132 C901090167 Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced release) .............................15-147 15.133 C901090168 Number of HO Target not found (MSC-controlled incoming handover due to forced handover) ................................................................15-148 15.134 C901090169 Number of send forced handover request to lower PRI user (MSC-controlled incoming handover due to forced handover) .........................15-149 15.135 C901090170 Number of failure to lower PRI user request resource for forced handover (MSC-controlled incoming handover due to forced handover) ..........15-150 15.136 C901090171 Number of lower PRI user handover failure (MSC-controlled incoming handover due to forced handover) ..................................................15-150 15.137 C901090172 Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced handover) .........................15-151 15.138 C901090173 Number of forced release target not found (MSC-controlled incoming handover due to forced release) .....................................................15-152
LI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

15.139 C901090174 Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced release) ............................15-152 15.140 C901090175 Number of get before grab released channel (assignment forced handover) .........................................................................................15-153 15.141 C901090176 Number of get before grab released channel (assignment forced release) ............................................................................................15-154 15.142 C901090177 Number of handover attempts due to eMLPP forced handover.....................................................................................................15-154 15.143 C901090178 Number of handover due to eMLPP forced handover .............15-155 15.144 C901090179 Number of handover success due to eMLPP forced handover.....................................................................................................15-155 15.145 C901090180 Number of BSC-controlled inter-cell outgoing handover attempts between PLMN ..............................................................................15-156 15.146 C901090181 Number of BSC-controlled inter-cell outgoing handover between PLMN............................................................................................15-156 15.147 C901090182 Number of BSC-controlled inter-cell outgoing handover success between PLMN...............................................................................15-156 15.148 C901090183 Number of MSC-controlled outgoing handover attempts between PLMN............................................................................................15-156 15.149 C901090184 Number of MSC-controlled outgoing handover request fail between PLMN due to unknown reason ........................................................15-156 15.150 C901090185 Number of MSC-controlled outgoing handover request fail between PLMN due to unavailable ground resource ......................................15-157 15.151 C901090186 Number of MSC-controlled outgoing handover request fail between PLMN due to unavailable radio resource .........................................15-158 15.152 C901090187 Number of MSC-controlled outgoing handover request fail between PLMN due to other reasons ............................................................15-158 15.153 C901090188 Number of MSC-controlled outgoing handover between PLMN .........................................................................................................15-158 15.154 C901090189 Number of MSC-controlled outgoing handover success between PLMN............................................................................................15-160 15.155 C901090190 Number of BSC-controlled inter-cell incoming handover attempt between PLMN................................................................................15-160 15.156 C901090191 Number of BSC-controlled inter-cell incoming handover between PLMN............................................................................................15-160 15.157 C901090192 Number of BSC-controlled inter-cell incoming handover force-release attempt between PLMN ...........................................................15-160 15.158 C901090193 Number of BSC-controlled inter-cell incoming handover between PLMN due to force release .............................................................15-161 15.159 C901090194 Number of BSC-controlled inter-cell incoming handover queue attempt between PLMN................................................................................15-161
LII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

15.160 C901090195 Number of BSC-controlled inter-cell incoming handover between PLMN due to queue .......................................................................15-161 15.161 C901090196 Number of BSC-controlled inter-cell incoming handover force-handover attempt between PLMN ........................................................15-161 15.162 C901090197 Number of BSC-controlled inter-cell incoming handover between PLMN due to force handover ..........................................................15-161 15.163 C901090198 Number of BSC-controlled inter-cell incoming handover success between PLMN...............................................................................15-161 15.164 C901090199 Number of MSC-controlled incoming handover attempt between PLMN ...........................................................................................15-162 15.165 C901090200 A interface incoming handover fail between PLMN due to circuit block .................................................................................................15-163 15.166 C901090201 A interface incoming handover fail between PLMN due to circuit unmatch ............................................................................................15-164 15.167 C901090202 A interface incoming handover fail between PLMN due to unavailable radio resource ...........................................................................15-164 15.168 C901090203 A interface incoming handover fail between PLMN due to other reason................................................................................................15-165 15.169 C901090204 Number of MSC-controlled incoming handover between PLMN .........................................................................................................15-165 15.170 C901090205 Number of MSC-controlled incoming handover force-release attempt between PLMN................................................................................15-165 15.171 C901090206 Number of MSC-controlled incoming handover between PLMN due to force release .....................................................................................15-166 15.172 C901090207 Number of MSC-controlled incoming handover queue attempt between PLMN............................................................................................15-166 15.173 C901090208 Number of MSC-controlled incoming handover between PLMN due to queue ...............................................................................................15-167 15.174 C901090209 Number of MSC-controlled incoming handover force-handover attempt between PLMN................................................................................15-168 15.175 C901090210 Number of MSC-controlled incoming handover between PLMN due to force handover ..................................................................................15-169 15.176 C901090211 Number of MSC-controlled incoming handover success between PLMN ...........................................................................................15-169 15.177 C901090212 Number of handover due to Fragment reorganization.............15-169 15.178 C901090213 Number of handover success due to Fragment reorganization .............................................................................................15-169 15.179 C901090214 Number of handover attempt from AMR FR to AMR HR due to high load .....................................................................................................15-170 15.180 C901090215 Number of handover from AMR FR to AMR HR due to high load ............................................................................................................15-171
LIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

15.181 C901090216 Number of handover success from AMR FR to AMR HR due to high load .................................................................................................15-172 15.182 C901090217 Number of handover attempt from FR to HR due to high load ............................................................................................................15-172 15.183 C901090218 Number of handover from FR to HR due to high load .............15-173 15.184 C901090219 Number of handover success from FR to HR due to high load ............................................................................................................15-174 15.185 C901090220 Number of handover attempt from AMR HR to AMR FR due to bad quality ..................................................................................................15-174 15.186 C901090221 Number of handover from AMR HR to AMR FR due to bad quality.........................................................................................................15-175 15.187 C901090222 Number of handover success from AMR HR to AMR FR due to bad quality...............................................................................................15-176 15.188 C901090223 Number of handover attempt from HR to FR due to bad quality.........................................................................................................15-176 15.189 C901090224 Number of handover from HR to FR due to bad quality...........15-177 15.190 C901090225 Number of handover success from HR to FR due to bad quality.........................................................................................................15-178 15.191 C901090226 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM900 .............................................................15-178 15.192 C901090227 Number of BSC-controlled inter-cell outgoing handover, from GSM900 to GSM900....................................................................................15-179 15.193 C901090228 Number of BSC-controlled inter-cell outgoing handover success, from GSM900 to GSM900 ..............................................................15-180 15.194 C901090229 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM1800..........................................................15-181 15.195 C901090230 Number of BSC-controlled inter-cell outgoing handover, from GSM1800 to GSM1800................................................................................15-182 15.196 C901090231 Number of BSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM1800 ..........................................................15-183 15.197 C901090232 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM1800 ...........................................................15-184 15.198 C901090233 Number of BSC-controlled inter-cell outgoing handover, from GSM900 to GSM1800..................................................................................15-185 15.199 C901090234 Number of BSC-controlled inter-cell outgoing handover success, from GSM900 to GSM1800 ............................................................15-186 15.200 C901090235 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM900 ...........................................................15-187 15.201 C901090236 Number of BSC-controlled inter-cell outgoing handover, from GSM1800 to GSM900..................................................................................15-188

LIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

15.202 C901090237 Number of BSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM900 ............................................................15-189 15.203 C901090238 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM900 .............................................................15-190 15.204 C901090239 Number of MSC-controlled inter-cell outgoing handover, from GSM900 to GSM900....................................................................................15-191 15.205 C901090240 Number of MSC-controlled inter-cell outgoing handover success, from GSM900 to GSM900 ..............................................................15-192 15.206 C901090241 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM1800..........................................................15-193 15.207 C901090242 Number of MSC-controlled inter-cell outgoing handover, from GSM1800 to GSM1800................................................................................15-194 15.208 C901090243 Number of MSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM1800 ..........................................................15-195 15.209 C901090244 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM1800 ...........................................................15-196 15.210 C901090245 Number of MSC-controlled inter-cell outgoing handover, from GSM900 to GSM1800..................................................................................15-197 15.211 C901090246 Number of MSC-controlled inter-cell outgoing handover success, from GSM900 to GSM1800 ............................................................15-198 15.212 C901090247 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM900 ...........................................................15-198 15.213 C901090248 Number of MSC-controlled inter-cell outgoing handover, from GSM1800 to GSM900..................................................................................15-199 15.214 C901090249 Number of MSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM900 ............................................................15-200 15.215 C901090250 Number of Inter-BSC Incoming Handover Failure Due to New Channel Access Failure ...............................................................................15-201 15.216 C901090251 Number of Inter-BSC Incoming Handover Failure Due to MS Return to Old Channel .................................................................................15-201 15.217 C901090264 The Number of forbid sending hand command during releasing .....................................................................................................15-202 15.218 C901090265 Number of Inner BSC Direct Retry Success...........................15-203 15.219 C901090266 Number of Inter BSC Direct Retry Success............................15-203 15.220 C901090267 Number of Intra-Cell Handover Failure Lead to Return ...........15-204 15.221 C901090268 User/MSC Release Number During BSC-Controlled Inter-Cell Outgoing Handover......................................................................................15-204 15.222 C901090269 User/MSC Release Number During MSC-Controlled Inter-Cell Outgoing Handover......................................................................................15-205

Chapter 16 Adjacent Cell Handover Measurement ............................... 16-1

LV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

16.1 Overview ....................................................................................................... 16-3 16.2 C901100001 Number of handover attempts on the adjacent cell. ....................... 16-3 16.3 C901100002 Number of handover success from selected cell to the adjacent cell................................................................................................................. 16-4 16.4 C901100003 Number of handover attempts from adjacent cell to the selected cell................................................................................................................. 16-5 16.5 C901100004 Number of handover success from adjacent cell to the selected cell................................................................................................................. 16-7 16.6 C901100005 Number of handover attempts from selected cell to the adjacent cell due to better UL quality. ............................................................................ 16-8 16.7 C901100006 Number of handover attempts from selected cell to the adjacent cell due to better DL quality. ............................................................................ 16-9 16.8 C901100007 Number of handover success from selected cell to the adjacent cell due to better UL quality. ........................................................................... 16-11 16.9 C901100008 Number of handover success from selected cell to the adjacent cell due to better DL quality. ...........................................................................16-12 16.10 C901100009 Number of handover attempts from selected cell to the adjacent cell due to better UL strength..........................................................................16-13 16.11 C901100010 Number of handover attempts from selected cell to the adjacent cell due to better DL strength..........................................................................16-15 16.12 C901100011 Number of handover success from selected cell to the adjacent cell due to better UL strength..........................................................................16-16 16.13 C901100012 Number of handover success from selected cell to the adjacent cell due to better DL strength..........................................................................16-17 16.14 C901100013 Number of handover attempts from selected cell to the adjacent cell due to PBGT ...........................................................................................16-19 16.15 C901100014 Number of handover success from selected cell to the adjacent cell due to PBGT ...........................................................................................16-20 16.16 C901100015 Number of handover attempts from selected cell to the adjacent cell due to other factors. .................................................................................16-21 16.17 C901100016 Number of successful handover from selected cell to the adjacent cell due to other factors. ...................................................................16-23 16.18 C901100017 Number of pingpong handover (handover to source cell) ............16-24 16.19 C901100018 The max of RTD ......................................................................16-25 16.20 C901100019 The sum of RTD ......................................................................16-26 16.21 C901100021 Number of Receive Downlink Level of This Adjacent Cell ...........16-27 16.22 C901100022 Sum of Receive Downlink Level of This Adjacent Cell ................16-27 16.23 C901100023 Number of Update History Record of This Adjacent Cell .............16-28 16.24 C901100024 Sum of Downlink Level to Update History Record of This Adjacent Cell.................................................................................................16-28
LVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

16.25 C901100025 Sum of Used History Record Downlink Level of This Adjacent Cell...............................................................................................................16-28 16.26 C901100020 The number of RTD .................................................................16-28 16.27 C901100026 Number of handover attempts from selected cell to the adjacent cell due to DL quality rapid drop......................................................................16-29 16.28 C901100027 Number of handover success from selected cell to the adjacent cell due to DL quality rapid drop......................................................................16-30 16.29 C901100028 Number of Handover From Selected Cell to the Adjacent Cell ......16-31 16.30 C901100029 Number of Handover From the Adjacent Cell to Selected Cell ......16-32 16.31 C901100030 Number of Handover From Selected Cell to the Adjacent Cell Due to UL Quality ..........................................................................................16-33 16.32 C901100031 Number of Handover From Selected Cell to the Adjacent Cell Due to DL Quality ..........................................................................................16-34 16.33 C901100032 Number of Handover From Selected Cell to the Adjacent Cell Due to UL Strength ........................................................................................16-35 16.34 C901100033 Number of Handover From Selected Cell to the Adjacent Cell Due to DL Strength ........................................................................................16-35 16.35 C901100034 Number of Handover From Selected Cell to the Adjacent Cell Due to PBGT.................................................................................................16-36 16.36 C901100035 Number of Handover From Selected Cell to the Adjacent Cell Due to DL Quality Rapid Drop ........................................................................16-36 16.37 C901100036 Number of Handover From Selected Cell to the Adjacent Cell Due to Other Reason .....................................................................................16-37 16.38 C901100037 Number of Handover Attempts From Selected Cell to the Adjacent Cell Due to Traffic ............................................................................16-37 16.39 C901100038 Number of Handover From Selected Cell to the Adjacent Cell Due to Traffic.................................................................................................16-38 16.40 C901100039 Number of successful handovers from selected cell to the adjacent cell due to Traffic..............................................................................16-38 16.41 C901100043 Number of few MS MR received before connection failure after handover from adjacent 3G cell ......................................................................16-39 16.42 C901100044 Number of Handover Failure to the Adjacent Cell Lead to Return ..........................................................................................................16-39 16.43 C901100045 Number of Attempts in Target Cell for Directed Retry..................16-40 16.44 C901100046 Number of Perform in Target Cell for Directed Retry ...................16-40 16.45 C901100047 Number of Success in Target Cell for Directed Retry ..................16-41 16.46 C901100048 Number of SDCCH Drops Due to Handover Failure to This Cell...............................................................................................................16-41 16.47 C901100049 Number of Speech TCH Drops Due to Handover Failure to This Cell...............................................................................................................16-42

LVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

16.48 C901100050 Number of Data TCH Drops Due to Handover Failure to This Cell...............................................................................................................16-42 16.49 C901100051 Number of Signal TCH Drops Due to Handover Failure to This Cell...............................................................................................................16-43

Chapter 17 Radio Access Measurement ................................................ 17-1

17.1 Overview ....................................................................................................... 17-3 17.2 C901110001 Number of invalid access requests............................................... 17-4 17.3 C901110003 Number of MOC access success for processes ............................ 17-5 17.4 C901110006 Number of MTC access success for processes ............................. 17-5 17.5 C901110008 Number of call re-establishment access attempts.......................... 17-6 17.6 C901110009 Number of call re-establishment access success for processes ..... 17-6 17.7 C901110010 Number of call re-establishment access success .......................... 17-7 17.8 C901110011 Number of emergency calls access attempts ................................ 17-8 17.9 C901110012 Number of emergency calls access success for processes ............ 17-8 17.10 C901110013 Number of emergency calls access success ............................... 17-9 17.11 C901110014 Number of LOC access attempts...............................................17-10 17.12 C901110015 Number of LOC access success for processes ..........................17-10 17.13 C901110016 Number of LOC access success ............................................... 17-11 17.14 C901110017 Number of other causes access attempts .................................. 17-11 17.15 C901110018 Number of successful random access processes for other causes ..........................................................................................................17-12 17.16 C901110019 Number of other causes access success ...................................17-12 17.17 C901110020 Number of LMU Establishment Access attempts ........................17-13 17.18 C901110021 Number of LMU Establishment access success for processes .....................................................................................................17-14 17.19 C901110022 Number of LMU Establishment access success .........................17-14 17.20 C901110023 Number of accesses due to location update...............................17-15 17.21 C901110024 Number of Access due to CM SERVICE REQ............................17-15 17.22 C901110026 Number of CM service requests of Emergency Call ....................17-16 17.23 C901110027 Number of CM service requests of SMS ....................................17-17 17.24 C901110028 Number of CM service requests of Supplement..........................17-17 17.25 C901110029 Number of CM service requests of LCS .....................................17-18 17.26 C901110031 Number of wireless access due to call re-establishments............17-18 17.27 C901110032 Number of wireless accesses due to IMSI detachment ...............17-19 17.28 C901110033 Number of wireless accesses due to other causes .....................17-19 17.29 C901110034 Number of access due to Notification response..........................17-20 17.30 C901110035 Number of access due to Immediate setup ................................17-21 17.31 C901110036 Number of access due to Talker indication .................................17-22
LVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

17.32 C901110037 Number of access due to DATA Indication .................................17-23 17.33 C901110038 Number of access due to priority uplink request .........................17-24 17.34 C901110039 Number of access of CM service request of VGCS.....................17-25 17.35 C901110040 Number of access of CM service request of VBS .......................17-26 17.36 C901110041 Number of CS Precise Paging ..................................................17-27 17.37 C901110042 Number of CS Precise Paging Response ..................................17-28 17.38 C901110043 Number of CS First Paging .......................................................17-28 17.39 C901110044 Number of CS First Paging Response .......................................17-28 17.40 C901110045 Number of CS Second Paging ..................................................17-29 17.41 C901110046 Number of CS Second Paging Response ..................................17-29 17.42 C901110047 Number of CS Third Paging ......................................................17-30 17.43 C901110048 Number of CS Third Paging Response ......................................17-30 17.44 C901110049 Number of PS Precise Paging...................................................17-30 17.45 C901110050 Number of PS Precise Paging Response...................................17-31 17.46 C901110051 Number of PS First Paging .......................................................17-31 17.47 C901110052 Number of PS First Paging Response .......................................17-32 17.48 C901110053 Number of PS Second Paging ..................................................17-32 17.49 C901110054 Number of PS Second Paging Response ..................................17-32 17.50 C901110055 Number of PS Third Paging ......................................................17-33 17.51 C901110056 Number of PS Third Paging Response ......................................17-33 17.52 C901110057 Number of CS Precise Paging for Last Service in This Cell .........17-34 17.53 C901110058 Number of CS Precise Paging No Response for Last Service in This Cell .......................................................................................................17-34 17.54 C901110059 Number of CS First Paging for Last Service in This Cell..............17-35 17.55 C901110060 Number of CS First Paging No Response for Last Service in This Cell .......................................................................................................17-35 17.56 C901110061 Number of CS Second Paging for Last Service in This Cell.........17-36 17.57 C901110062 Number of CS Second Paging No Response for Last Service in This Cell .......................................................................................................17-36 17.58 C901110063 Number of CS Third Paging for Last Service in This Cell ............17-37 17.59 C901110064 Number of CS Third Paging No Response for Last Service in This Cell .......................................................................................................17-37 17.60 C901110065 Number of PS Precise Paging for Last Service in This Cell .........17-38 17.61 C901110066 Number of PS Precise Paging No Response for Last Service in This Cell .......................................................................................................17-38 17.62 C901110067 Number of PS First Paging for Last Service in This Cell..............17-39 17.63 C901110068 Number of PS First Paging No Response for Last Service in This Cell .......................................................................................................17-39

LIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

17.64 C901110069 Number of PS Second Paging for Last Service in This Cell .........17-40 17.65 C901110070 Number of PS Second Paging No Response for Last Service in This Cell .......................................................................................................17-40 17.66 C901110071 Number of PS Third Paging for Last Service in This Cell.............17-41 17.67 C901110072 Number of PS Third Paging No Response for Last Service in This Cell .......................................................................................................17-41 17.68 C901110073 Number of CS Precise Paging (Paging Hole Search)..................17-42 17.69 C901110074 Number of CS Precise Paging No Response (Paging Hole Search).........................................................................................................17-42 17.70 C901110075 Number of CS First Paging (Paging Hole Search) ......................17-43 17.71 C901110076 Number of CS First Paging No Response (Paging Hole Search).........................................................................................................17-43 17.72 C901110077 Number of CS Second Paging (Paging Hole Search) .................17-44 17.73 C901110078 Number of CS Second Paging No Response (Paging Hole Search).........................................................................................................17-44 17.74 C901110079 Number of CS Third Paging (Paging Hole Search) .....................17-45 17.75 C901110080 Number of CS Third Paging No Response (Paging Hole Search).........................................................................................................17-45 17.76 C901110081 Number of PS Precise Paging (Paging Hole Search)..................17-46 17.77 C901110082 Number of PS Precise Paging No Response (Paging Hole Search).........................................................................................................17-46 17.78 C901110083 Number of PS First Paging (Paging Hole Search) ......................17-47 17.79 C901110084 Number of PS First Paging No Response (Paging Hole Search).........................................................................................................17-47 17.80 C901110085 Number of PS Second Paging (Paging Hole Search)..................17-48 17.81 C901110086 Number of PS Second Paging No Response (Paging Hole Search).........................................................................................................17-48 17.82 C901110087 Number of PS Third Paging (Paging Hole Search) .....................17-49 17.83 C901110088 Number of PS Third Paging No Response (Paging Hole Search).........................................................................................................17-49

Chapter 18 Radio Measurement.............................................................. 18-1

18.1 Overview ....................................................................................................... 18-4 18.2 C901120001 Number of UL signal quality samples in wireless channels ............ 18-4 18.3 C901120002 Level of worst UL signal quality in wireless channels..................... 18-5 18.4 C901120003 Total value of UL quality level values in wireless channels ............. 18-5 18.5 C901120004 Number of DL signal quality samples in wireless channels ............ 18-6 18.6 C901120005 Level of worst DL signal quality in wireless channels..................... 18-6 18.7 C901120006 Total value of DL quality strength values in wireless channels........ 18-7

LX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

18.8 C901120007 Number of received UL signal strength samples in wireless channels ........................................................................................................ 18-8 18.9 C901120008 Maximum received UL signal strength in wireless channels ........... 18-8 18.10 C901120009 Minimum received UL signal strength in wireless channels .......... 18-9 18.11 C901120010 Total value of UL signal strength in wireless channels.................. 18-9 18.12 C901120011 Number of received DL signal strength samples in wireless channels .......................................................................................................18-10 18.13 C901120012 Maximum received DL signal strength in wireless channels ........ 18-11 18.14 C901120013 Minimum DL received signal strength in radio channels.............. 18-11 18.15 C901120014 Total value of DL signal strength in wireless channels ................18-12 18.16 C901120015 Number of TA samples in wireless channels ..............................18-12 18.17 C901120016 Maximum TA in wireless channels.............................................18-13 18.18 C901120017 Total number of TAs in wireless channels ..................................18-13 18.19 C901120018 Mean number of idle TCH/Fs with interference band 0 ...............18-14 18.20 C901120024 Mean number of idle TCH/Hs with interference band 0 ...............18-15 18.21 C901120030 Mean number of idle SDCCHs with interference band 0 .............18-15 18.22 C901120031 Mean number of idle SDCCHs with interference band 1 .............18-16 18.23 C901120032 Mean number of idle SDCCHs with interference band 2 .............18-16 18.24 C901120033 Mean number of idle SDCCHs with interference band 3 .............18-17 18.25 C901120034 Mean number of idle SDCCHs with interference band 4 .............18-17 18.26 C901120035 Mean number of idle SDCCHs with interference band 5 .............18-18 18.27 C901120053 Number of using noise suppression ..........................................18-18 18.28 C901120058 Number of samples with voice quality is excellent ......................18-19 18.29 C901120059 Number of samples with voice quality is good ............................18-19 18.30 C901120060 Number of samples with voice quality is medium........................18-20 18.31 C901120061 Number of samples with voice quality is bad..............................18-20 18.32 C901120062 Number of samples with voice quality is awfully .........................18-21 18.33 C901120063 Number of uplink error frame on FR_V1 ....................................18-22 18.34 C901120064 Total Number of uplink frame on FR_V1 ....................................18-22 18.35 C901120065 Number of uplink error frame on FR_V2 ....................................18-22 18.36 C901120066 Total Number of uplink frame on FR_V2 ....................................18-23 18.37 C901120067 Number of uplink error frame on FR_V3 ....................................18-23 18.38 C901120068 Total Number of uplink frame on FR_V3 ....................................18-23 18.39 C901120069 Number of uplink error frame on HR_V1....................................18-24 18.40 C901120070 Total Number of uplink frame on HR_V1....................................18-24 18.41 C901120071 Number of uplink error frame on HR_V3....................................18-25 18.42 C901120072 Total Number of uplink frame on HR_V3....................................18-25

LXI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

18.43 C901120073 Number of UL signal quality samples in radio channels on SDCCH.........................................................................................................18-25 18.44 C901120074 Level of worst UL signal quality in radio channels on SDCCH ......18-26 18.45 C901120075 Total value of UL quality level values in radio channels on SDCCH.........................................................................................................18-27 18.46 C901120076 Number of DL signal quality samples in radio channels on SDCCH.........................................................................................................18-27 18.47 C901120077 Level of worst DL signal quality in radio channels on SDCCH ......18-28 18.48 C901120078 Total value of DL quality strength values in radio channels on SDCCH.........................................................................................................18-28 18.49 C901120079 Number of received UL signal strength samples in radio channels on SDCCH......................................................................................18-29 18.50 C901120080 Maximum received UL signal strength in radio channels on SDCCH.........................................................................................................18-30 18.51 C901120081 Minimum received UL signal strength in radio channels on SDCCH.........................................................................................................18-30 18.52 C901120082 Total value of UL signal strength in radio channels on SDCCH.........................................................................................................18-31 18.53 C901120083 Number of received DL signal strength samples in radio channels on SDCCH......................................................................................18-31 18.54 C901120084 Maximum received DL signal strength in radio channels on SDCCH.........................................................................................................18-32 18.55 C901120085 Minimum DL received signal strength in radio channels on SDCCH.........................................................................................................18-33 18.56 C901120086 Total value of DL signal strength in radio channels on SDCCH.........................................................................................................18-33 18.57 C901120087 Number of UL signal quality samples in radio channels on TCH..............................................................................................................18-34 18.58 C901120088 Level of worst UL signal quality in radio channels on TCH ..........18-34 18.59 C901120089 Total value of UL quality level values in radio channels on TCH..............................................................................................................18-35 18.60 C901120090 Number of DL signal quality samples in radio channels on TCH..............................................................................................................18-36 18.61 C901120091 Level of worst DL signal quality in radio channels on TCH ..........18-36 18.62 C901120092 Total value of DL quality strength values in radio channels on TCH..............................................................................................................18-37 18.63 C901120093 Number of received UL signal strength samples in radio channels on TCH...........................................................................................18-37 18.64 C901120094 Maximum received UL signal strength in radio channels on TCH..............................................................................................................18-38

LXII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

18.65 C901120095 Minimum received UL signal strength in radio channels on TCH..............................................................................................................18-39 18.66 C901120096 Total value of UL signal strength in radio channels on TCH.........18-39 18.67 C901120097 Number of received DL signal strength samples in radio channels on TCH...........................................................................................18-40 18.68 C901120098 Maximum received DL signal strength in radio channels on TCH..............................................................................................................18-40 18.69 C901120099 Minimum DL received signal strength in radio channels on TCH..............................................................................................................18-41 18.70 C901120100 Total value of DL signal strength in radio channels on TCH.........18-42 18.71 C901120101 Number of samples with UL RQ = 0 on SDCCH.........................18-42 18.72 C901120102 Number of samples with UL RQ = 1 on SDCCH.........................18-43 18.73 C901120103 Number of samples with UL RQ = 2 on SDCCH.........................18-44 18.74 C901120104 Number of samples with UL RQ = 3 on SDCCH.........................18-44 18.75 C901120105 Number of samples with UL RQ = 4 on SDCCH.........................18-45 18.76 C901120106 Number of samples with UL RQ = 5 on SDCCH.........................18-46 18.77 C901120107 Number of samples with UL RQ = 6 on SDCCH.........................18-46 18.78 C901120108 Number of samples with UL RQ = 7 on SDCCH.........................18-47 18.79 C901120109 Number of samples with DL RQ = 0 on SDCCH.........................18-47 18.80 C901120110 Number of samples with DL RQ = 1 on SDCCH .........................18-48 18.81 C901120111 Number of samples with DL RQ = 2 on SDCCH .........................18-49 18.82 C901120112 Number of samples with DL RQ = 3 on SDCCH .........................18-49 18.83 C901120113 Number of samples with DL RQ = 4 on SDCCH .........................18-50 18.84 C901120114 Number of samples with DL RQ = 5 on SDCCH .........................18-51 18.85 C901120115 Number of samples with DL RQ = 6 on SDCCH .........................18-51 18.86 C901120116 Number of samples with DL RQ = 7 on SDCCH .........................18-52 18.87 C901120117 Number of samples with UL RQ = 0 on TCH ..............................18-53 18.88 C901120118 Number of samples with UL RQ = 1 on TCH ..............................18-53 18.89 C901120119 Number of samples with UL RQ = 2 on TCH ..............................18-54 18.90 C901120120 Number of samples with UL RQ = 3 on TCH..............................18-55 18.91 C901120121 Number of samples with UL RQ = 4 on TCH..............................18-55 18.92 C901120122 Number of samples with UL RQ = 5 on TCH..............................18-56 18.93 C901120123 Number of samples with UL RQ = 6 on TCH..............................18-57 18.94 C901120124 Number of samples with UL RQ = 7 on TCH..............................18-57 18.95 C901120125 Number of samples with DL RQ = 0 on TCH..............................18-58 18.96 C901120126 Number of samples with DL RQ = 1 on TCH..............................18-59 18.97 C901120127 Number of samples with DL RQ = 2 on TCH..............................18-59 18.98 C901120128 Number of samples with DL RQ = 3 on TCH..............................18-60
LXIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

18.99 C901120129 Number of samples with DL RQ = 4 on TCH..............................18-61 18.100 C901120130 Number of samples with DL RQ = 5 on TCH ............................18-61 18.101 C901120131 Number of samples with DL RQ = 6 on TCH ............................18-62 18.102 C901120132 Number of samples with DL RQ = 7 on TCH ............................18-63 18.103 C901120133 Rach Level Grade0 (Above -57 dBm) Sample..........................18-63 18.104 C901120134 Rach Level Grade1 (-57 to -62 dBm) Sample...........................18-64 18.105 C901120135 Rach Level Grade2 (-63 to -68 dBm) Sample...........................18-64 18.106 C901120136 Rach Level Grade3 (-69 to -74 dBm) Sample...........................18-65 18.107 C901120137 Rach Level Grade4 (-75 to -80 dBm) Sample...........................18-65 18.108 C901120138 Rach Level Grade5 (-81 to -86 dBm) Sample...........................18-66 18.109 C901120139 Rach Level Grade6 (-87 to -92 dBm) Sample...........................18-66 18.110 C901120140 Rach Level Grade7 (-93 to -98 dBm) Sample ...........................18-67 18.111 C901120141 Rach Level Grade8 (-99 to -104 dBm) Sample .........................18-67 18.112 C901120142 Rach Level Grade9 (Below -104 dBm) Sample ........................18-68 18.113 C901120143 Number of Sample With Interference Band ..............................18-68 18.114 C901120144 Number of Idle TCH/F With Interference Band 0.......................18-69 18.115 C901120145 Number of Idle TCH/F With Interference Band 1.......................18-69 18.116 C901120146 Number of Idle TCH/F With Interference Band 2.......................18-70 18.117 C901120147 Number of Idle TCH/F With Interference Band 3.......................18-70 18.118 C901120148 Number of Idle TCH/F With Interference Band 4.......................18-71 18.119 C901120149 Number of Idle TCH/F With Interference Band 5.......................18-71 18.120 C901120150 Number of Idle TCH/H With Interference Band 0 ......................18-72 18.121 C901120151 Number of Idle TCH/H With Interference Band 1 ......................18-72 18.122 C901120152 Number of Idle TCH/H With Interference Band 2 ......................18-73 18.123 C901120153 Number of Idle TCH/H With Interference Band 3 ......................18-73 18.124 C901120154 Number of Idle TCH/H With Interference Band 4 ......................18-74 18.125 C901120155 Number of Idle TCH/H With Interference Band 5 ......................18-74 18.126 C901120156 Number of Idle SDCCH With Interference Band 0 ....................18-75 18.127 C901120157 Number of Idle SDCCH With Interference Band 1 ....................18-75 18.128 C901120158 Number of Idle SDCCH With Interference Band 2 ....................18-76 18.129 C901120159 Number of Idle SDCCH With Interference Band 3 ....................18-76 18.130 C901120160 Number of Idle SDCCH With Interference Band 4 ....................18-77 18.131 C901120161 Number of Idle SDCCH With Interference Band 5 ....................18-77

Chapter 19 Sub Cell Statistics................................................................. 19-1

19.1 Overview ....................................................................................................... 19-6 19.2 C901130001 Number of available TCH/Fs in the second sub cell ...................... 19-6 19.3 C901130002 Number of unavailable TCH/Fs in the second sub cell................... 19-7

LXIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

19.4 C901130003 Number of available TCH/Hs in the second sub cell ...................... 19-7 19.5 C901130004 Number of unavailable TCH/Hs in the second sub cell .................. 19-8 19.6 C901130005 Number of handover attempts from the first sub cell to the second sub cell .......................................................................................................... 19-9 19.7 C901130006 Number of handover execution from the first sub cell to the second sub cell .............................................................................................19-10 19.8 C901130007 Number of handover success from the first sub cell to the second sub cell ......................................................................................................... 19-11 19.9 C901130008 Number of handover attempts from the second sub cell to the first sub cell ...................................................................................................19-12 19.10 C901130009 Number of handover execution from the second sub cell to the first sub cell ...................................................................................................19-13 19.11 C901130010 Number of handover success from the second sub cell to the first sub cell ...................................................................................................19-14 19.12 C901130011 Number of handover attempts in the second sub cell..................19-15 19.13 C901130012 Number of handover execution in the second sub cell ................19-16 19.14 C901130013 Number of handover success in the second sub cell ..................19-17 19.15 C901130014 Number of outgoing inter-cell handover attempts of the second sub cell .........................................................................................................19-18 19.16 C901130015 Number of outgoing inter-cell handover execution of the second sub cell .........................................................................................................19-19 19.17 C901130016 Number of outgoing inter-cell handover success of the second sub cell .........................................................................................................19-20 19.18 C901130017 Handover attempts due to UL receiving strength of the full rate second sub cell .............................................................................................19-21 19.19 C901130018 Handover attempts due to DL receiving strength of the full rate second sub cell .............................................................................................19-22 19.20 C901130019 Handover attempts due to UL quality of the full rate second sub cell ...............................................................................................................19-23 19.21 C901130020 Handover attempts due to DL quality of the full rate second sub cell ...............................................................................................................19-24 19.22 C901130021 Handover attempts due to PBGT of the full rate second sub cell ...............................................................................................................19-25 19.23 C901130022 Handover attempts due to traffic of the full rate second sub cell ...............................................................................................................19-26 19.24 C901130023 Handover attempts due to UL interference of the full rate second sub cell (on TCH/F)........................................................................................19-27 19.25 C901130024 Handover attempts due to DL interference of the full rate second sub cell (on TCH/F)........................................................................................19-28

LXV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

19.26 C901130025 Handover attempts due to good CI of the full rate second sub cell (on TCH/F) ..............................................................................................19-29 19.27 C901130026 Handover attempts due to bad CI of the full rate second sub cell (on TCH/F)....................................................................................................19-30 19.28 C901130027 Handover attempts due to path loss and too large TA of the full rate second sub cell (on TCH/F) .....................................................................19-31 19.29 C901130028 Handover attempts due to path loss and too small TA of the full rate second sub cell (on TCH/F) .....................................................................19-32 19.30 C901130029 Number of forced transfer handover attempts of the full rate second sub cell (on TCH/F) ............................................................................19-33 19.31 C901130030 Handover attempts due to other causes of the full rate second sub cell .........................................................................................................19-34 19.32 C901130031 Handover attempts due to UL receiving strength of the half rate second sub cell .............................................................................................19-35 19.33 C901130032 Handover attempts due to DL receiving strength of the half rate second sub cell .............................................................................................19-36 19.34 C901130033 Handover attempts due to UL quality of the half rate second sub cell ...............................................................................................................19-37 19.35 C901130034 Handover attempts due to DL quality of the half rate second sub cell ...............................................................................................................19-38 19.36 C901130035 Handover attempts due to PBGT of the half rate second sub cell ...............................................................................................................19-39 19.37 C901130036 Handover attempts due to traffic of the half rate second sub cell ...............................................................................................................19-40 19.38 C901130037 Handover attempts due to UL interference of the half rate second sub cell .............................................................................................19-41 19.39 C901130038 Handover attempts due to DL interference of the half rate second sub cell .............................................................................................19-42 19.40 C901130039 Handover attempts due to C/I of the half rate second sub cell ......19-43 19.41 C901130040 Handover attempts due to C/I of the half rate second sub cell ......19-44 19.42 C901130041 Handover attempts due to path loss and too large TA of the half rate second sub cell.......................................................................................19-45 19.43 C901130042 Handover attempts due to path loss and too small TA of the half rate second sub cell.......................................................................................19-46 19.44 C901130043 Number of forced transfer handover attempts of the half rate second sub cell .............................................................................................19-47 19.45 C901130044 Handover attempts due to other causes of the half rate second sub cell .........................................................................................................19-48 19.46 C901130045 Number of attempts of TCH/F seizure of the second sub cell (used for assignment) ....................................................................................19-49

LXVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

19.47 C901130046 Number of TCH/F seizure success of the second sub cell (used for assignment) .............................................................................................19-50 19.48 C901130047 Number of TCH/F seizure failure of the second sub cell (used for assignment) .............................................................................................19-51 19.49 C901130048 Number of attempts of TCH/F seizure of the second sub cell (used for handover) .......................................................................................19-52 19.50 C901130049 Number of TCH/F seizure success of the second sub cell (used for handover).................................................................................................19-53 19.51 C901130050 Number of TCH/F seizure failure of the second sub cell (used for handover).................................................................................................19-54 19.52 C901130051 Number of TCH/H seizure attempts of the second sub cell (used for assignment) .............................................................................................19-55 19.53 C901130052 Number of TCH/H seizure success of the second sub cell (used for assignment) .............................................................................................19-56 19.54 C901130053 Number of TCH/H seizure failure of the second sub cell (used for assignment) .............................................................................................19-56 19.55 C901130054 Number of TCH/H seizure attempts of the second sub cell (used for handover).................................................................................................19-57 19.56 C901130055 Number of TCH/H seizure success of the second sub cell (used for handover).................................................................................................19-58 19.57 C901130056 Number of TCH/H seizure failure of the second sub cell (used for handover).................................................................................................19-59 19.58 C901130057 Number of TCH/F call drops in the second sub cell ....................19-60 19.59 C901130058 Number of TCH/H call drops in the second sub cell....................19-61 19.60 C901130059 TCH/F busy time in the second sub cell.....................................19-61 19.61 C901130060 TCH/H busy time in the second sub cell ....................................19-62 19.62 C901130061 Number of TCH/F assignment attempts of the second sub cell ...............................................................................................................19-63 19.63 C901130062 Number of TCH/F assignment success of the second sub cell ...............................................................................................................19-64 19.64 C901130063 Number of TCH/F handover attempts of the second sub cell.......19-64 19.65 C901130064 Number of TCH/F handover success of the second sub cell .......19-65 19.66 C901130065 Number of TCH/H assignment attempts of the second sub cell ...............................................................................................................19-66 19.67 C901130066 Number of TCH/H assignment success of the second sub cell ...............................................................................................................19-67 19.68 C901130067 Number of TCH/H handover attempts of the second sub cell ......19-68 19.69 C901130068 Number of TCH/H handover success of the second sub cell .......19-69 19.70 C901130069 TCH/F of the first sub cell seizure success when prefer the second sub cell (used for assignment) ............................................................19-69
LXVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

19.71 C901130070 TCH/F of the first sub cell seizure success when prefer the second sub cell (used for handover) ...............................................................19-70 19.72 C901130071 TCH/H of the first sub cell seizure success when prefer the second sub cell (used for assignment) ............................................................19-71 19.73 C901130072 TCH/H of the first sub cell seizure success when prefer the second sub cell (used for handover) ...............................................................19-71 19.74 C901130073 Number of Inter-Cell Handover Attempts to the Second Sub Cell Directly From the Cell in the Same Site ...........................................................19-72 19.75 C901130074 Number of Inter-Cell Handover Execution to the Second Sub Cell Directly From the Cell in the Same Site ....................................................19-73 19.76 C901130075 Number of Inter-Cell Handover Success to the Second Sub Cell Directly From the Cell in the Same Site ...........................................................19-73 19.77 C901130076 Number of Inter-Cell Handover Attempts to the Second Sub Cell Directly From Another Site .............................................................................19-74 19.78 C901130077 Number of Inter-Cell Handover Execution to the Second Sub Cell Directly From Another Site.......................................................................19-74 19.79 C901130078 Number of Inter-Cell Handover Success to the Second Sub Cell Directly From Another Site .............................................................................19-75 19.80 C901130079 Number of Handover Attempts to the Second Sub Cell Directly From Another BSC ........................................................................................19-75 19.81 C901130080 Number of Handover Execution to the Second Sub Cell Directly From Another BSC ........................................................................................19-76 19.82 C901130081 Number of Handover Success to the Second Sub Cell Directly From Another BSC ........................................................................................19-76 19.83 C901130082 Number of Handover to the First Sub Cell Too Fast After Handover From Another Cell in the Same Site.................................................19-77 19.84 C901130083 Number of Handover to the Second Sub Cell Too Fast After Handover From Another Cell in the Same Site.................................................19-77 19.85 C901130084 Number of Handover to the First Sub Cell Too Fast After Handover From Another Site ..........................................................................19-78 19.86 C901130085 Number of Handover to the Second Sub Cell Too Fast After Handover From Another Site ..........................................................................19-78 19.87 C901130086 Sample of Subcell 2 Level Low 30dB or Below Than BCCH........19-79 19.88 C901130087 Sample of Subcell 2 Level Low 29 dB Than BCCH.....................19-79 19.89 C901130088 Sample of Subcell 2 Level Low 28 dB Than BCCH.....................19-80 19.90 C901130089 Sample of Subcell 2 Level Low 27 dB Than BCCH.....................19-80 19.91 C901130090 Sample of Subcell 2 Level Low 26 dB Than BCCH.....................19-81 19.92 C901130091 Sample of Subcell 2 Level Low 25 dB Than BCCH.....................19-81 19.93 C901130092 Sample of Subcell 2 Level Low 24 dB Than BCCH.....................19-82 19.94 C901130093 Sample of Subcell 2 Level Low 23 dB Than BCCH.....................19-82
LXVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

19.95 C901130094 Sample of Subcell 2 Level Low 22 dB Than BCCH.....................19-83 19.96 C901130095 Sample of Subcell 2 Level Low 21 dB Than BCCH.....................19-83 19.97 C901130096 Sample of Subcell 2 Level Low 20 dB Than BCCH.....................19-84 19.98 C901130097 Sample of Subcell 2 Level Low 19 dB Than BCCH.....................19-84 19.99 C901130098 Sample of Subcell 2 Level Low 18 dB Than BCCH.....................19-85 19.100 C901130099 Sample of Subcell 2 Level Low 17 dB Than BCCH...................19-85 19.101 C901130100 Sample of Subcell 2 Level Low 16 dB Than BCCH...................19-86 19.102 C901130101 Sample of Subcell 2 Level Low 15 dB Than BCCH...................19-86 19.103 C901130102 Sample of Subcell 2 Level Low 14 dB Than BCCH...................19-87 19.104 C901130103 Sample of Subcell 2 Level Low 13 dB Than BCCH...................19-87 19.105 C901130104 Sample of Subcell 2 Level Low 12 dB Than BCCH...................19-88 19.106 C901130105 Sample of Subcell 2 Level Low 11 dB Than BCCH ...................19-88 19.107 C901130106 Sample of Subcell 2 Level Low 10 dB Than BCCH...................19-89 19.108 C901130107 Sample of Subcell 2 Level Low 9 dB Than BCCH.....................19-89 19.109 C901130108 Sample of Subcell 2 Level Low 8 dB Than BCCH.....................19-90 19.110 C901130109 Sample of Subcell 2 Level Low 7 dB Than BCCH.....................19-90 19.111 C901130110 Sample of Subcell 2 Level Low 6 dB Than BCCH .....................19-91 19.112 C901130111 Sample of Subcell 2 Level Low 5 dB Than BCCH .....................19-91 19.113 C901130112 Sample of Subcell 2 Level Low 4 dB Than BCCH .....................19-92 19.114 C901130113 Sample of Subcell 2 Level Low 3 dB Than BCCH .....................19-92 19.115 C901130114 Sample of Subcell 2 Level Low 2 dB Than BCCH .....................19-93 19.116 C901130115 Sample of Subcell 2 Level Low 1 dB Than BCCH .....................19-93 19.117 C901130116 Sample of Subcell 2 Level Equal BCCH ...................................19-94 19.118 C901130117 Sample of Subcell 2 Level High 1 dB Than BCCH ....................19-94 19.119 C901130118 Sample of Subcell 2 Level High 2 dB Than BCCH ....................19-95 19.120 C901130119 Sample of Subcell 2 Level High 3 dB Than BCCH ....................19-95 19.121 C901130120 Sample of Subcell 2 Level High 4 dB Than BCCH....................19-96 19.122 C901130121 Sample of Subcell 2 Level High 5 dB Than BCCH....................19-96 19.123 C901130122 Sample of Subcell 2 Level High 6 dB Than BCCH....................19-97 19.124 C901130123 Sample of Subcell 2 Level High 7 dB Than BCCH....................19-97 19.125 C901130124 Sample of Subcell 2 Level High 8 dB Than BCCH....................19-98 19.126 C901130125 Sample of Subcell 2 Level High 9 dB Than BCCH....................19-98 19.127 C901130126 Sample of Subcell 2 Level High 10 dB Than BCCH ..................19-99 19.128 C901130127 Sample of Subcell 2 Level High 11 dB Than BCCH ..................19-99 19.129 C901130128 Sample of Subcell 2 Level High 12 dB Than BCCH ................19-100 19.130 C901130129 Sample of Subcell 2 Level High 13 dB Than BCCH ................19-100 19.131 C901130130 Sample of Subcell 2 Level High 14 dB Than BCCH ................19-101

LXIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

19.132 C901130131 Sample of Subcell 2 Level High 15 dB Than BCCH ................19-101 19.133 C901130132 Sample of Level Difference Between Subcell 2 and BCCH ......19-102 19.134 C901130133 Sum of Level Difference Between Subcell 2 and BCCH ..........19-102 19.135 C901130134 Lowest of Level Difference Between Subcell 2 and BCCH ......19-103 19.136 C901130135 Highest of Level Difference Between Subcell 2 and BCCH ......19-103 19.137 C901130136 Number of handover attempt from FR to HR(V3) due to high load in Subcell2 ...........................................................................................19-104 19.138 C901130137 Number of handover from FR to HR(V3) due to high load in Subcell2......................................................................................................19-105 19.139 C901130138 Number of handover success from FR to HR(V3) due to high load in Subcell2 ...........................................................................................19-105 19.140 C901130139 Number of handover attempt from FR to HR(V1) due to high load in Subcell2 ...........................................................................................19-106 19.141 C901130140 Number of handover from FR to HR(V1) due to high load in Subcell2......................................................................................................19-106 19.142 C901130141 Number of handover success from FR to HR(V1) due to high load in Subcell2 ...........................................................................................19-107 19.143 C901130142 Number of handover attempt from HR(V3) to FR due to bad quality in Subcell2........................................................................................19-107 19.144 C901130143 Number of handover from HR(V3) to FR due to bad quality in Subcell2......................................................................................................19-108 19.145 C901130144 Number of handover success from HR(V3) to FR due to bad quality in Subcell2........................................................................................19-108 19.146 C901130145 Number of handover attempt from HR(V1) to FR due to bad quality in Subcell2........................................................................................19-109 19.147 C901130146 Number of handover from HR(V1) to FR due to bad quality in Subcell2...................................................................................................... 19-110 19.148 C901130147 Number of handover success from HR(V1) to FR due to bad quality in Subcell2........................................................................................ 19-110 19.149 C901130150 Number of Handover Attempt From FR to HR (V1) Due to High Load in Subcell 2 ......................................................................................... 19-111 19.150 C901130151 Number of Handover From FR to HR (V1) Due to High Load in Subcell 2..................................................................................................... 19-111 19.151 C901130152 Number of Handover Success From FR to HR (V1) Due to High Load in Subcell 2 ................................................................................. 19-112 19.152 C901130153 Number of Handover Attempt From FR to HR (V3) Due to High Load in Subcell 2 ......................................................................................... 19-112 19.153 C901130154 Number of Handover From FR to HR (V3) Due to High Load in Subcell 2..................................................................................................... 19-113

LXX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

19.154 C901130155 Number of Handover Success From FR to HR (V3) Due to High Load in Subcell 2 ................................................................................. 19-113

Chapter 20 MS TA Measurement............................................................. 20-1

20.1 Overview ....................................................................................................... 20-2 20.2 C901140001 Number of TA=0 ......................................................................... 20-2 20.3 C901140033 Number of TA>63 ....................................................................... 20-3 20.4 C901140034 Number of TA=1 ......................................................................... 20-4 20.5 C901140035 Number of TA=2 ......................................................................... 20-4 20.6 C901140036 Number of TA=3 ......................................................................... 20-5 20.7 C901140037 Number of TA=4 ......................................................................... 20-5 20.8 C901140038 Number of TA=5 ......................................................................... 20-6 20.9 C901140039 Number of TA=6 ......................................................................... 20-6 20.10 C901140040 Number of TA=7 ....................................................................... 20-7 20.11 C901140041 Number of TA=8........................................................................ 20-7 20.12 C901140042 Number of TA=9 ....................................................................... 20-8 20.13 C901140043 Number of TA=10 ..................................................................... 20-8 20.14 C901140044 Number of TA=11...................................................................... 20-9 20.15 C901140045 Number of TA=12 ..................................................................... 20-9 20.16 C901140046 Number of TA=13 ....................................................................20-10 20.17 C901140047 Number of TA=14 ....................................................................20-10 20.18 C901140048 Number of TA=15 .................................................................... 20-11 20.19 C901140049 Number of TA=16 .................................................................... 20-11 20.20 C901140050 Number of TA=17 ....................................................................20-12 20.21 C901140051 Number of TA=18 ....................................................................20-12 20.22 C901140052 Number of TA=19 ....................................................................20-13 20.23 C901140053 Number of TA=20 ....................................................................20-13 20.24 C901140054 Number of TA=21 ....................................................................20-14 20.25 C901140055 Number of TA=22 ....................................................................20-14 20.26 C901140056 Number of TA=23 ....................................................................20-15 20.27 C901140057 Number of TA=24 ....................................................................20-15 20.28 C901140058 Number of TA=25 ....................................................................20-16 20.29 C901140059 Number of TA=26 ....................................................................20-16 20.30 C901140060 Number of TA=27 ....................................................................20-17 20.31 C901140061 Number of TA=28 ....................................................................20-17 20.32 C901140062 Number of TA=29 ....................................................................20-18 20.33 C901140063 Number of TA=30 ....................................................................20-18 20.34 C901140064 Number of TA=31 ....................................................................20-19

LXXI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

20.35 C901140065 Number of TA=32 ....................................................................20-19 20.36 C901140066 Number of TA=33 ....................................................................20-20 20.37 C901140067 Number of TA=34 ....................................................................20-20 20.38 C901140068 Number of TA=35 ....................................................................20-21 20.39 C901140069 Number of TA=36 ....................................................................20-21 20.40 C901140070 Number of TA=37 ....................................................................20-22 20.41 C901140071 Number of TA=38 ....................................................................20-22 20.42 C901140072 Number of TA=39 ....................................................................20-23 20.43 C901140073 Number of TA=40 ....................................................................20-23 20.44 C901140074 Number of TA=41 ....................................................................20-24 20.45 C901140075 Number of TA=42 ....................................................................20-24 20.46 C901140076 Number of TA=43 ....................................................................20-25 20.47 C901140077 Number of TA=44 ....................................................................20-25 20.48 C901140078 Number of TA=45 ....................................................................20-26 20.49 C901140079 Number of TA=46 ....................................................................20-26 20.50 C901140080 Number of TA=47 ....................................................................20-27 20.51 C901140081 Number of TA=48 ....................................................................20-27 20.52 C901140082 Number of TA=49 ....................................................................20-28 20.53 C901140083 Number of TA=50 ....................................................................20-28 20.54 C901140084 Number of TA=51 ....................................................................20-29 20.55 C901140085 Number of TA=52 ....................................................................20-29 20.56 C901140086 Number of TA=53 ....................................................................20-30 20.57 C901140087 Number of TA=54 ....................................................................20-30 20.58 C901140088 Number of TA=55 ....................................................................20-31 20.59 C901140089 Number of TA=56 ....................................................................20-31 20.60 C901140090 Number of TA=57 ....................................................................20-32 20.61 C901140091 Number of TA=58 ....................................................................20-32 20.62 C901140092 Number of TA=59 ....................................................................20-33 20.63 C901140093 Number of TA=60 ....................................................................20-33 20.64 C901140094 Number of TA=61 ....................................................................20-34 20.65 C901140095 Number of TA=62 ....................................................................20-34 20.66 C901140096 Number of TA=63 ....................................................................20-35

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

LXXII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 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 21.24 C901150026 Number of Release for Intercept Mobile Originated Short Message .......................................................................................................21-26 21.25 C901150027 Number of Release for Intercept Mobile Terminated Short Message .......................................................................................................21-27
LXXIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

21.26 C901150028 Number of Discard CM SERVICE REQUEST for Mobile Terminated Short Message.............................................................................21-28 21.27 C901150029 Number of Discard RP-DATA for Mobile Terminated Short Message .......................................................................................................21-29

Chapter 22 Uplink and Downlink PACCH Statistics .............................. 22-1

22.1 Overview ....................................................................................................... 22-2 22.2 C901160001 Number of Packet access reject message .................................... 22-2 22.3 C901160002 Number of Packet resource request message .............................. 22-3 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 22.27 C901160029 Number of Packet Measurement Order Message.......................22-25 22.28 C901160030 Number of Packet Measurement Order Message Owing to 2G/3G Inter-Operation ...................................................................................22-26 22.29 C901160031 Number of Packet Measurement Report Message .....................22-27 22.30 C901160032 Number of Packet Measurement Report Message Owing to 2G/3G Inter-Operation ...................................................................................22-28 22.31 C901160033 Number of Packet Cell Change Order Message to 3G................22-29
LXXIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics ................................... 23-1

23.1 Overview ....................................................................................................... 23-3 23.2 C901170002 Number of GPRS DL TBF establishment requests on 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 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 connection failed ...........................................................................................23-13 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 23.20 C901170023 Number of GPRS DL TBF resource reallocation failure due to Abis congestion for UL TBF establishment ......................................................23-18 23.21 C901170024 Number of GPRS DL TBF resource reallocation failure due to RR congestion for UL TBF establishment ........................................................23-19 23.22 C901170025 Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment ...............................23-20

LXXV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

23.23 C901170026 Number of GPRS DL TBF resource reallocation success of channel allocation 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 23.25 C901170028 Number of GPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment............................................23-23 23.26 C901170029 Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment ............................................23-24 23.27 C901170030 Number of GPRS DL TBF resource reallocation failure due to 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 23.29 C901170032 Number of GPRS DL TBF resource reallocation failure due to UL TBF establishment ...................................................................................23-27 23.30 C901170033 Number of GPRS DL TBF resource reallocation success due to UL TBF establishment ...................................................................................23-27 23.31 C901170036 Number of GPRS DL TBF resource reallocation failure due to Abis congestion for LLC transmission .............................................................23-27 23.32 C901170037 Number of GPRS DL TBF resource reallocation failure due to RR congestion for LLC transmission ...............................................................23-29 23.33 C901170038 Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission ......................................23-30 23.34 C901170039 Number of GPRS DL TBF resource reallocation success of channel allocation due to LLC transmission .....................................................23-31 23.35 C901170040 Number of allocated PDCH for GPRS DL TBF resource reallocation due to LLC transmission...............................................................23-32 23.36 C901170041 Number of GPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission ...................................................23-33 23.37 C901170042 Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission ...................................................23-34 23.38 C901170043 Number of GPRS DL TBF resource reallocation failure due to 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.40 C901170045 Number of GPRS DL TBF resource reallocation failure due to LLC transmission...........................................................................................23-36 23.41 C901170046 Number of GPRS DL TBF resource reallocation success due to LLC transmission...........................................................................................23-37 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
LXXVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 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 index exception ..........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 24.2 C901180002 Number of EGPRS DL TBF establishment requests on 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 connection failed ...........................................................................................24-12 24.13 C901180014 Number of EGPRS DL TBF establishment failure due to BIU connection failed ...........................................................................................24-13 24.14 C901180015 Number of EGPRS DL TBF channel activate establishment success ........................................................................................................24-14

LXXVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

24.15 C901180016 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to not receive PIA ............................................................24-15 24.16 C901180017 Number of EGPRS DL TBF establishment failure on 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 24.18 C901180019 Number of EGPRS DL TBF establishment success on PCCCH/CCCH ..............................................................................................24-17 24.19 C901180020 Number of EGPRS DL TBF establishment success on PACCH .........................................................................................................24-17 24.20 C901180023 Number of EGPRS DL TBF resource reallocation failure due to Abis congestion for UL TBF establishment ......................................................24-18 24.21 C901180024 Number of EGPRS DL TBF resource reallocation failure due to RR congestion for UL TBF establishment ........................................................24-19 24.22 C901180025 Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment ...............................24-20 24.23 C901180026 Number of EGPRS DL TBF resource reallocation success of channel allocation 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 24.25 C901180028 Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment............................................24-23 24.26 C901180029 Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment ............................................24-24 24.27 C901180030 Number of EGPRS DL TBF resource reallocation failure due to 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 24.29 C901180032 Number of EGPRS DL TBF resource reallocation failure due to UL TBF establishment ...................................................................................24-27 24.30 C901180033 Number of EGPRS DL TBF resource reallocation success due to UL TBF establishment................................................................................24-27 24.31 C901180036 Number of EGPRS DL TBF resource reallocation failure due to Abis congestion for LLC transmission .............................................................24-28 24.32 C901180037 Number of EGPRS DL TBF resource reallocation failure due to RR congestion for LLC transmission ...............................................................24-29 24.33 C901180038 Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission ......................................24-30 24.34 C901180039 Number of EGPRS DL TBF resource reallocation success of channel allocation due to LLC transmission .....................................................24-31

LXXVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

24.35 C901180040 Number of allocated PDCH for EGPRS DL TBF resource reallocation due to LLC transmission...............................................................24-32 24.36 C901180041 Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission ...................................................24-33 24.37 C901180042 Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission ...................................................24-34 24.38 C901180043 Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for LLC transmission ....................................................24-35 24.39 C901180044 Number of EGPRS DL TBF resource reallocation success of channel activate and connection for LLC transmission .....................................24-36 24.40 C901180045 Number of EGPRS DL TBF resource reallocation failure due to LLC transmission...........................................................................................24-37 24.41 C901180046 Number of EGPRS DL TBF resource reallocation success due to LLC transmission .......................................................................................24-37 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 Index exception........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 24.55 C901180060 Times of Downlink EGPRS TBF Requesting DLDC Resources.....................................................................................................24-48 24.56 C901180061 Times of Allocating Downlink DLDC Resources for EGPRS TBF ..............................................................................................................24-48

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

LXXIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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

LXXX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 connection failed ...........................................................................................25-30 25.28 C901190029 Number of GPRS UL TBF establishment failure due to BIU connection failed ...........................................................................................25-31 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 25.31 C901190032 Number of GPRS UL TBF establishhment failure on PCCCH/CCCH ..............................................................................................25-33 25.32 C901190033 Number of GPRS UL TBF establishment failure on PACCH........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 25.35 C901190038 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for DL TBF establishment ......................................................25-36 25.36 C901190039 Number of GPRS UL TBF resource reallocation failure due to RR congestion for DL TBF establishment ........................................................25-37 25.37 C901190040 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for DL TBF establishment ...............................25-38 25.38 C901190041 Number of GPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment..............................................25-39 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 25.41 C901190044 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for DL TBF establishment ............................................25-42 25.42 C901190045 Number of GPRS UL TBF resourse reallocation failure due to 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.44 C901190047 Number of GPRS UL TBF resourse reallocation failure due to DL TBF establishment ...................................................................................25-45 25.45 C901190048 Number of GPRS UL TBF resourse reallocation success due to DL TBF establishment ...................................................................................25-45 25.46 C901190051 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission .............................................................25-46

LXXXI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

25.47 C901190052 Number of GPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission ...............................................................25-47 25.48 C901190053 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission ......................................25-48 25.49 C901190054 Number of GPRS UL TBF resource reallocation success of channel allocation due to LLC transmission .....................................................25-49 25.50 C901190055 Number of allocated PDCH for GPRS UL TBF resource reallocation due to LLC transmission...............................................................25-50 25.51 C901190056 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for LLC transmission ...................................................25-51 25.52 C901190057 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for LLC transmission ...................................................25-52 25.53 C901190058 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for LLC transmission ....................................................25-53 25.54 C901190059 Number of GPRS UL TBF resourse reallocation success of channel activate for LLC transmission .............................................................25-54 25.55 C901190060 Number of GPRS UL TBF resourse reallocation failure due to LLC transmission...........................................................................................25-54 25.56 C901190061 Number of GPRS UL TBF resourse reallocation success due to LLC transmission...........................................................................................25-55 25.57 C901190062 Number of GPRS UL TBF resource reallocation requests for resource request ...........................................................................................25-55 25.58 C901190064 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for resource request ..............................................................25-55 25.59 C901190065 Number of GPRS UL TBF resource reallocation failure due to RR congestion for resource request ................................................................25-56 25.60 C901190066 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for resource request .......................................25-58 25.61 C901190067 Number of GPRS UL TBF resource reallocation success due to resource request ...........................................................................................25-59 25.62 C901190068 Number of allocated PDCH for GPRS UL TBF resource reallocation due to resource request ...............................................................25-60 25.63 C901190069 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for resource request....................................................25-61 25.64 C901190070 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for resource request ....................................................25-62 25.65 C901190071 Number of GPRS UL TBF resourse reallocation failure due to 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

LXXXII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

25.67 C901190073 Number of GPRS UL TBF resourse reallocation failure due to resource request ...........................................................................................25-65 25.68 C901190074 Number of GPRS UL TBF resourse reallocation success due to resource request ...........................................................................................25-65 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 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
LXXXIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 26.16 C901200017 Number of EGPRS UL TBF establishment failure due to UPPB-DSP channel congestion......................................................................26-15 26.17 C901200018 Number of EGPRS UL TBF establishment channel allocate success ........................................................................................................26-16 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 26.20 C901200021 Number of cell success for EGPRS UL assignment due to response paging............................................................................................26-19 26.21 C901200022 Number of cell success for EGPRS UL assignment due to cell updating........................................................................................................26-19 26.22 C901200023 Number of cell success for EGPRS UL assignment due to 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 26.26 C901200027 Number of EGPRS UL TBF establishment failure due to channel activate failed ...................................................................................26-24 26.27 C901200028 Number of EGPRS UL TBF establishment failure due to BTS connection failed ...........................................................................................26-25 26.28 C901200029 Number of EGPRS UL TBF establishment failure due to BIU connection failed ...........................................................................................26-26 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 26.31 C901200032 Number of EGPRS UL TBF establishment failure on PCCCH/CCCH ..............................................................................................26-28 26.32 C901200033 Number of EGPRS UL TBF establishment failure on PACCH ......26-29 26.33 C901200034 Number of EGPRS UL TBF establishment success on PCCCH/CCCH ..............................................................................................26-30
LXXXIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

26.34 C901200035 Number of EGPRS UL TBF establishment success on PACCH .........................................................................................................26-31 26.35 C901200038 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for DL TBF establishment ......................................................26-31 26.36 C901200039 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for DL TBF establishment ........................................................26-32 26.37 C901200040 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for DL TBF establishment ...............................26-33 26.38 C901200041 Number of EGPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment..............................................26-34 26.39 C901200042 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to DL TBF establishment .......................................................26-35 26.40 C901200043 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment............................................26-36 26.41 C901200044 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for DL TBF establishment ............................................26-37 26.42 C901200045 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for DL TBF establishment .............................................26-38 26.43 C901200046 Number of EGPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment ..............................26-39 26.44 C901200047 Number of EGPRS UL TBF resource reallocation failure due to DL TBF establishment ...................................................................................26-40 26.45 C901200048 Number of EGPRS UL TBF resource reallocation success due to DL TBF establishment................................................................................26-40 26.46 C901200051 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission .............................................................26-41 26.47 C901200052 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission ...............................................................26-42 26.48 C901200053 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission ......................................26-43 26.49 C901200054 Number of EGPRS UL TBF resource reallocation success of channel allocation due to LLC transmission .....................................................26-44 26.50 C901200055 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to LLC transmission ..............................................................26-45 26.51 C901200056 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for LLC transmission ...................................................26-46 26.52 C901200057 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for LLC transmission ...................................................26-47 26.53 C901200058 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for LLC transmission ....................................................26-48

LXXXV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

26.54 C901200059 Number of EGPRS UL TBF resource reallocation success of channel activate for LLC transmission .............................................................26-49 26.55 C901200060 Number of EGPRS UL TBF resource reallocation failure due to LLC transmission...........................................................................................26-50 26.56 C901200061 Number of EGPRS UL TBF resource reallocation success due to LLC transmission .......................................................................................26-50 26.57 C901200062 Number of EGPRS UL TBF resource reallocation requests for resource request ...........................................................................................26-51 26.58 C901200064 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for resource request ..............................................................26-51 26.59 C901200065 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for resource request ................................................................26-52 26.60 C901200066 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for resource request .......................................26-53 26.61 C901200067 Number of EGPRS UL TBF resource reallocation success due to database allocation for resource request .....................................................26-54 26.62 C901200068 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to resource request ...............................................................26-55 26.63 C901200069 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for resource request....................................................26-56 26.64 C901200070 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for resource request ....................................................26-57 26.65 C901200071 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for resource request .....................................................26-58 26.66 C901200072 Number of EGPRS UL TBF resource reallocation success of channel activate and connection for resource request ......................................26-59 26.67 C901200073 Number of EGPRS UL TBF resource reallocation failure due to resource request ...........................................................................................26-60 26.68 C901200074 Number of EGPRS UL TBF resource reallocation success due to resource request........................................................................................26-60 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-61 26.71 C901200077 Number of EGPRS UL TBF forcing release by CS .....................26-62 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-63 26.74 C901200080 Number of EGPRS UL TBF release due to NSVC unavailability .................................................................................................26-64 26.75 C901200081 Number of EGPRS UL TBF release due to BVC unavailability ......26-65
LXXXVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

26.76 C901200082 Number of EGPRS UL TBF release due to other reasons ..........26-65 26.77 C901200083 Number of UL EGPRS TBF grab resources...............................26-66 26.78 C901200084 Number of grab instance by UL EGPRS TBF ............................26-67 26.79 C901200085 Number of UL EGPRS TBF queuing .........................................26-68 26.80 C901200086 Number of UL EGPRS TBF queuing success ............................26-69 26.81 C901200087 Number of UL EGPRS TBF release TBF during queuing............26-70 26.82 C901200088 Times of Uplink EGPRS TBF Requesting DLDC Resources .......26-71 26.83 C901200089 Times of Allocating Uplink DLDC Resources for EGPRS TBF ......26-72

Chapter 27 BSSGP Flow Statistic ........................................................... 27-1

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
LXXXVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 Message Statistic ........................................................... 28-1

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-12 28.15 C901220014 Number of FLOW-CONTROL-MS messages sent by BSC .........28-13 28.16 C901220015 Number of FLOW-CONTROL-MS-ACK messages received by BSC..............................................................................................................28-14 28.17 C901220016 Number of FLOW-CONTROL-PFC messages sent by BSC........28-15 28.18 C901220017 Number of FLOW-CONTROL-PFC-ACK messages received by BSC..............................................................................................................28-16 28.19 C901220018 Number of status messages sent by BSC .................................28-17 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
LXXXVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 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-35 28.44 C901220043 Number of PS-HANDOVER-COMPLETE messages sent by BSC..............................................................................................................28-37 28.45 C901220044 Number of PS-HANDOVER-CANCEL messages sent by BSC..............................................................................................................28-38 28.46 C901220045 Number of PS-HANDOVER-REQUEST messages with Service UTRAN CCO received by BSC .......................................................................28-39

LXXXIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

28.47 C901220046 Number of CREATE-BSS-PFC messages with Service UTRAN CCO received by BSC ...................................................................................28-40

Chapter 29 TRX Measurement................................................................. 29-1

29.1 Overview ....................................................................................................... 29-4 29.2 C901230001 Number of intra-cell handover in attempts .................................... 29-4 29.3 C901230002 Number of intra-cell handover ins success ................................... 29-5 29.4 C901230003 Number of Intra-BSC inter-cell handover in attempts..................... 29-6 29.5 C901230004 Number of Intra-BSC intra-cell handover ins success.................... 29-7 29.6 C901230005 Number of Intra-MSC inter-cell handover in attempts .................... 29-8 29.7 C901230006 Number of Intra-MSC inter-cell handover in success..................... 29-9 29.8 C901230007 TCH busy time ..........................................................................29-10 29.9 C901230008 Number of TCH seizures (including handover) ............................ 29-11 29.10 C901230009 Number of call drops due to TCH LAPD breakage ..................... 29-11 29.11 C901230010 Number of call drops due to TCH radio link failure...................... 29-11 29.12 C901230011 Number of TCH handover call drops .........................................29-12 29.13 C901230012 Number of TCH/F activation attempts (including handover) ........29-13 29.14 C901230013 Number of TCH/F activation success (including handover) .........29-14 29.15 C901230014 Number of TCH/F assignment attempts ....................................29-15 29.16 C901230015 Number of TCH/F assignment success .....................................29-16 29.17 C901230016 Number of TCH/H activation attempts (including handover) ........29-17 29.18 C901230017 Number of TCH/H activation success (including handover).........29-18 29.19 C901230018 Number of TCH/H assignment attempts ....................................29-19 29.20 C901230019 Number of TCH/H assignment success.....................................29-20 29.21 C901230020 SDCCH busy time ...................................................................29-21 29.22 C901230021 Number of attempts for SDCCH................................................29-22 29.23 C901230022 Number of SDCCH call drops ...................................................29-22 29.24 C901230023 Number of SDCCH activation attempts (including handover) ......29-24 29.25 C901230024 Number of SDCCH activation success (including handover) .......29-24 29.26 C901230025 Number of SDCCH assignment attempts ..................................29-25 29.27 C901230026 Number of SDCCH assignment success ...................................29-26 29.28 C901230027 Number of samples with UL RQ = 0 ..........................................29-27 29.29 C901230028 Number of samples with UL RQ = 1 ..........................................29-28 29.30 C901230029 Number of samples with UL RQ = 2 ..........................................29-28 29.31 C901230030 Number of samples with UL RQ = 3 ..........................................29-29 29.32 C901230031 Number of samples with UL RQ = 4 ..........................................29-30 29.33 C901230032 Number of samples with UL RQ = 5 ..........................................29-30 29.34 C901230033 Number of samples with UL RQ = 6 ..........................................29-31

XC SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

29.35 C901230034 Number of samples with UL RQ = 7 ..........................................29-31 29.36 C901230035 Number of samples with DL RQ = 0 ..........................................29-32 29.37 C901230036 Number of samples with DL RQ = 1 ..........................................29-33 29.38 C901230037 Number of samples with DL RQ = 2 ..........................................29-33 29.39 C901230038 Number of samples with DL RQ = 3 ..........................................29-34 29.40 C901230039 Number of samples with DL RQ = 4 ..........................................29-34 29.41 C901230040 Number of samples with DL RQ = 5 ..........................................29-35 29.42 C901230041 Number of samples with DL RQ = 6 ..........................................29-36 29.43 C901230042 Number of samples with DL RQ = 7 ..........................................29-36 29.44 C901230043 Mean number of idle TCH/Fs with interference band 0 ...............29-37 29.45 C901230044 Mean number of idle TCH/Fs with interference band 1 ...............29-38 29.46 C901230045 Mean number of idle TCH/Fs with interference band 2 ...............29-38 29.47 C901230046 Mean number of idle TCH/Fs with interference band 3 ...............29-39 29.48 C901230047 Mean number of idle TCH/Fs with interference band 4 ...............29-39 29.49 C901230048 Mean number of idle TCH/Fs with interference band 5 ...............29-40 29.50 C901230049 Mean number of idle TCH/Hs with interference band 0...............29-40 29.51 C901230050 Mean number of idle TCH/Hs with interference band 1...............29-41 29.52 C901230051 Mean number of idle TCH/Hs with interference band 2...............29-41 29.53 C901230052 Mean number of idle TCH/Hs with interference band 3...............29-42 29.54 C901230053 Mean number of idle TCH/Hs with interference band 4...............29-42 29.55 C901230054 Mean number of idle TCH/Hs with interference band 5...............29-43 29.56 C901230055 Mean number of idle SDCCHs with interference band 0 .............29-43 29.57 C901230056 Mean number of idle SDCCHs with interference band 1 .............29-44 29.58 C901230057 Mean number of idle SDCCHs with interference band 2 .............29-44 29.59 C901230058 Mean number of idle SDCCHs with interference band 3 .............29-44 29.60 C901230059 Mean number of idle SDCCHs with interference band 4 .............29-45 29.61 C901230060 Mean number of idle SDCCHs with interference band 5 .............29-45 29.62 C901230061 Number of TRX poweroff..........................................................29-46 29.63 C901230062 Duration of TRX poweroff .........................................................29-46 29.64 C901230063 Number of uplink error frame on FR_V1 ....................................29-47 29.65 C901230064 Total Number of uplink frame on FR_V1 ....................................29-47 29.66 C901230065 Number of uplink error frame on FR_V2 ....................................29-47 29.67 C901230066 Total Number of uplink frame on FR_V2 ....................................29-48 29.68 C901230067 Number of uplink error frame on FR_V3 ....................................29-48 29.69 C901230068 Total Number of uplink frame on FR_V3 ....................................29-48 29.70 C901230069 Number of uplink error frame on HR_V1 ...................................29-49 29.71 C901230070 Total Number of uplink frame on HR_V1 ...................................29-49

XCI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

29.72 C901230071 Number of uplink error frame on HR_V3 ...................................29-50 29.73 C901230072 Total Number of uplink frame on HR_V3 ...................................29-50 29.74 C901230073 Number of Samples With Uplink RQ=0 (on SDCCH)..................29-50 29.75 C901230074 Number of Samples With Uplink RQ = 1 (on SDCCH) ................29-51 29.76 C901230075 Number of Samples With Uplink RQ = 2 (on SDCCH) ................29-51 29.77 C901230076 Number of Samples With Uplink RQ = 3 (on SDCCH) ................29-51 29.78 C901230077 Number of Samples With Uplink RQ = 4 (on SDCCH) ................29-52 29.79 C901230078 Number of Samples With Uplink RQ = 5 (on SDCCH) ................29-52 29.80 C901230079 Number of Samples With Uplink RQ = 6 (on SDCCH) ................29-53 29.81 C901230080 Number of Samples With Uplink RQ = 7 (on SDCCH) ................29-53 29.82 C901230081 Number of Samples With Downlink RQ = 0 (on SDCCH)............29-53 29.83 C901230082 Number of Samples With Downlink RQ = 1 (on SDCCH)............29-54 29.84 C901230083 Number of Samples With Downlink RQ = 2 (on SDCCH)............29-54 29.85 C901230084 Number of Samples With Downlink RQ = 3 (on SDCCH)............29-54 29.86 C901230085 Number of Samples With Downlink RQ = 4 (on SDCCH)............29-55 29.87 C901230086 Number of Samples With Downlink RQ = 5 (on SDCCH)............29-55 29.88 C901230087 Number of Samples With Downlink RQ = 6 (on SDCCH)............29-56 29.89 C901230088 Number of Samples With Downlink RQ = 7 (on SDCCH)............29-56 29.90 C901230089 Number of Samples With Uplink RQ = 0 (on TCH) .....................29-56 29.91 C901230090 Number of Samples With Uplink RQ = 1 (on TCH) .....................29-57 29.92 C901230091 Number of Samples With Uplink RQ = 2 (on TCH) .....................29-57 29.93 C901230092 Number of Samples With Uplink RQ = 3 (on TCH) .....................29-57 29.94 C901230093 Number of Samples With Uplink RQ = 4 (on TCH) .....................29-58 29.95 C901230094 Number of Samples With Uplink RQ = 5 (on TCH) .....................29-58 29.96 C901230095 Number of Samples With Uplink RQ = 6 (on TCH) .....................29-59 29.97 C901230096 Number of Samples With Uplink RQ = 7 (on TCH) .....................29-59 29.98 C901230097 Number of Samples With Downlink RQ = 0 (on TCH).................29-59 29.99 C901230098 Number of Samples With Downlink RQ = 1 (on TCH).................29-60 29.100 C901230099 Number of Samples With Downlink RQ = 2 (on TCH) ...............29-60 29.101 C901230100 Number of Samples With Downlink RQ = 3 (on TCH) ...............29-60 29.102 C901230101 Number of Samples With Downlink RQ = 4 (on TCH) ...............29-61 29.103 C901230102 Number of Samples With Downlink RQ = 5 (on TCH) ...............29-61 29.104 C901230103 Number of Samples With Downlink RQ = 6 (on TCH) ...............29-62 29.105 C901230104 Number of Samples With Downlink RQ = 7 (on TCH) ...............29-62 29.106 C901230105 Number of Sample With Interference Band..............................29-62 29.107 C901230106 Number of Idle TCH/F With Interference Band 0 ......................29-63 29.108 C901230107 Number of Idle TCH/F With Interference Band 1 ......................29-63

XCII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

29.109 C901230108 Number of Idle TCH/F With Interference Band 2 ......................29-64 29.110 C901230109 Number of Idle TCH/F With Interference Band 3 ......................29-64 29.111 C901230110 Number of Idle TCH/F With Interference Band 4 .......................29-65 29.112 C901230111 Number of Idle TCH/F With Interference Band 5 .......................29-65 29.113 C901230112 Number of Idle TCH/H With Interference Band 0 ......................29-66 29.114 C901230113 Number of Idle TCH/H With Interference Band 1 ......................29-66 29.115 C901230114 Number of Idle TCH/H With Interference Band 2 ......................29-67 29.116 C901230115 Number of Idle TCH/H With Interference Band 3 ......................29-67 29.117 C901230116 Number of Idle TCH/H With Interference Band 4 ......................29-68 29.118 C901230117 Number of Idle TCH/H With Interference Band 5 ......................29-68 29.119 C901230118 Number of Idle TCH/H With Interference Band 0 ......................29-69 29.120 C901230119 Number of Idle TCH/H With Interference Band 1 ......................29-69 29.121 C901230120 Number of Idle TCH/H With Interference Band 2......................29-70 29.122 C901230121 Number of Idle TCH/H With Interference Band 3......................29-70 29.123 C901230122 Number of Idle TCH/H With Interference Band 4......................29-71 29.124 C901230123 Number of Idle TCH/H With Interference Band 5......................29-71 29.125 C901230124 Uplink CIR Normal Grade 0 (Below -2 dB) Sample...................29-72 29.126 C901230125 Uplink CIR Normal Grade 1 (-2 to 0.5 dB) Sample ...................29-72 29.127 C901230126 Uplink CIR Normal Grade 2 (1 to 3.5 dB) Sample ....................29-72 29.128 C901230127 Uplink CIR Normal Grade 3 (4 to 6.5 dB) Sample ....................29-73 29.129 C901230128 Uplink CIR Normal Grade 4 (7 to 9.5 dB) Sample ....................29-73 29.130 C901230129 Uplink CIR Normal Grade 5 (10 to 12.5 dB) Sample.................29-73 29.131 C901230130 Uplink CIR Normal Grade 6 (13 to 15.5 dB) Sample.................29-74 29.132 C901230131 Uplink CIR Normal Grade 7 (16 to 18.5 dB) Sample.................29-74 29.133 C901230132 Uplink CIR Normal Grade 8 (19 to 21.5 dB) Sample.................29-75 29.134 C901230133 Uplink CIR Normal Grade 9 (Above 21.5 dB) Sample...............29-75 29.135 C901230134 Uplink CIR Improved Grade 0 (Below -2 dB) Sample ...............29-75 29.136 C901230135 Uplink CIR Improved Grade 1 (-2 to 0.5 dB) Sample ................29-76 29.137 C901230136 Uplink CIR Improved Grade 2 (1 to 3.5 dB) Sample .................29-76 29.138 C901230137 Uplink CIR Improved Grade 3 (4 to 6.5 dB) Sample .................29-76 29.139 C901230138 Uplink CIR Improved Grade 4 (7 to 9.5 dB) Sample .................29-77 29.140 C901230139 Uplink CIR Improved Grade 5 (10 to 12.5 dB) Sample..............29-77 29.141 C901230140 Uplink CIR Improved Grade 6 (13 to 15.5 dB) Sample..............29-78 29.142 C901230141 Uplink CIR Improved Grade 7 (16 to 18.5 dB) Sample..............29-78 29.143 C901230142 Uplink CIR Improved Grade 8 (19 to 21.5 dB) Sample..............29-78 29.144 C901230143 Uplink CIR Improved Grade 9 (Above 21.5 dB) Sample............29-79

Chapter 30 Timeslot Measurement ......................................................... 30-1

XCIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

30.1 Overview ....................................................................................................... 30-3 30.2 C901240001 Maximum value of UL RQ ........................................................... 30-3 30.3 C901240002 Minimum value of UL RQ ............................................................ 30-3 30.4 C901240003 Value of UL RQ .......................................................................... 30-4 30.5 C901240004 Number of scans of UL RQ ......................................................... 30-5 30.6 C901240005 Maximum value of DL RQ ........................................................... 30-6 30.7 C901240006 Minimum value of DL RQ ............................................................ 30-6 30.8 C901240007 Value of DL RQ .......................................................................... 30-7 30.9 C901240008 Number of scans of DL RQ ......................................................... 30-8 30.10 C901240009 Maximum value of received UL signal strength ........................... 30-8 30.11 C901240010 Minimum value of received UL signal strength ............................ 30-9 30.12 C901240011 Total value of received UL signal strength..................................30-10 30.13 C901240012 Number of received UL signal strength samples ........................ 30-11 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-13 30.17 C901240016 Number of received DL signal strength samples ........................30-14 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-16 30.21 C901240020 Number of power scans of BTS power ......................................30-17 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
XCIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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(ms) .............................30-41 30.45 C901240044 Number of activated voice channel ...........................................30-42 30.46 C901240045 Maximum Value of Uplink RQ (on SDCCH) ...............................30-43 30.47 C901240046 Minimum Value of Uplink RQ (on SDCCH) ................................30-43 30.48 C901240047 Sum of Uplink RQ (on SDCCH) ................................................30-44 30.49 C901240048 Number of Samples of Uplink RQ (on SDCCH)..........................30-44 30.50 C901240049 Maximum Value of Downlink RQ (on SDCCH) ...........................30-45 30.51 C901240050 Minimum Value of Downlink RQ (on SDCCH) ............................30-45 30.52 C901240051 Sum of Downlink RQ (on SDCCH) ............................................30-45 30.53 C901240052 Number of Samples of Downlink RQ (on SDCCH) .....................30-46 30.54 C901240053 Maximum Value of Received Uplink Signal Strength (on SDCCH) .......................................................................................................30-46 30.55 C901240054 Minimum Value of Received Uplink Signal Strength (on SDCCH) .......................................................................................................30-47 30.56 C901240055 Total Received Uplink Signal Strength on SDCCH .....................30-47 30.57 C901240056 Number of Received Uplink Signal Strength Samples (on SDCCH) .......................................................................................................30-47 30.58 C901240057 Maximum Value of Received Downlink Signal Strength (on SDCCH) .......................................................................................................30-48 30.59 C901240058 Minimum Value of Received Downlink Signal Strength (on SDCCH) .......................................................................................................30-48 30.60 C901240059 Total Value of Received Downlink Signal Strength (on SDCCH) .......................................................................................................30-49 30.61 C901240060 Number of Received Downlink Signal Strength Samples (on SDCCH) .......................................................................................................30-49 30.62 C901240061 Maximum Value of Uplink RQ (on TCH) ....................................30-49 30.63 C901240062 Minimum Value of Uplink RQ (on TCH) .....................................30-50 30.64 C901240063 Sum of Uplink RQ (on TCH) .....................................................30-50 30.65 C901240064 Number of Samples of Uplink RQ (on TCH)...............................30-51 30.66 C901240065 Maximum Value of Downlink RQ (on TCH) ................................30-51 30.67 C901240066 Minimum Value of Downlink RQ (on TCH) .................................30-51 30.68 C901240067 Sum of Downlink RQ (on TCH) .................................................30-52 30.69 C901240068 Number of samples of downlink RQ(on TCH) ............................30-52
XCV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

30.70 C901240069 Maximum Value of Received Uplink Signal Strength (on TCH) ............................................................................................................30-53 30.71 C901240070 Minimum Value of Received Uplink Signal Strength (on TCH) ......30-53 30.72 C901240071 Total Received Uplink Signal Strength on TCH ..........................30-53 30.73 C901240072 Number of Received Uplink Signal Strength Samples (on TCH) ............................................................................................................30-54 30.74 C901240073 Maximum Value of Received Downlink Signal Strength (on TCH) ............................................................................................................30-54 30.75 C901240074 Minimum Value of Received Downlink Signal Strength (on TCH) ............................................................................................................30-55 30.76 C901240075 Total Received Downlink Signal Strength on TCH ......................30-55 30.77 C901240076 Number of Received Downlink Signal Strength Samples (on TCH) ............................................................................................................30-55

Chapter 31 SDCCH Measurement ........................................................... 31-1

31.1 Overview ....................................................................................................... 31-2 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-15 31.11 C901250020 Number of SDCCH assignment attempts (MOC)........................31-15 31.12 C901250021 Number of successful SDCCH assignments (MOC) ...................31-17 31.13 C901250022 Number of unsuccessful SDCCH assignments (MOC) ...............31-18 31.14 C901250023 Number of SDCCH assignment attempts (MTC) ........................31-19 31.15 C901250024 Number of successful SDCCH assignments (MTC)....................31-20 31.16 C901250025 Number of unsuccessful SDCCH assignments (MTC) ................31-21 31.17 C901250026 Number of SDCCH assignment attempts (call re-establishment)...........................................................................................31-22 31.18 C901250027 Number of successful SDCCH assignments (call re-establishment)...........................................................................................31-23 31.19 C901250028 Number of unsuccessful SDCCH assignments (call re-establishment)...........................................................................................31-25 31.20 C901250029 Number of SDCCH assignment attempts (emergency call).........31-26 31.21 C901250030 Number of successful SDCCH assignments (emergency call) ..............................................................................................................31-27
XCVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

31.22 C901250031 Number of unsuccessful SDCCH assignments (emergency call) ..............................................................................................................31-28 31.23 C901250032 Number of SDCCH assignment attempts (LOC) ........................31-29 31.24 C901250033 Number of successful SDCCH assignments (LOC) ....................31-31 31.25 C901250034 Number of unsuccessful SDCCH assignments (LOC) ................31-32 31.26 C901250035 Number of SDCCH assignment attempts (other cause)..............31-33 31.27 C901250036 Number of successful SDCCH assignments (other cause) .........31-34 31.28 C901250037 Number of unsuccessful SDCCH assignments (other cause) ......31-35 31.29 C901250038 Count of USSD attempts to connect..........................................31-36 31.30 C901250039 Average dialoge time of USSD services ....................................31-37 31.31 C901250040 Dialog counts of USSD services ...............................................31-37

Chapter 32 TCH/F Measurement ............................................................. 32-1

32.1 Overview ....................................................................................................... 32-6 32.2 C901260002 Number of signaling TCH/F seizure success for assignment ......... 32-9 32.3 C901260005 Number of signaling TCH/F seizure success for handover............32-10 32.4 C901260007 Number of signaling TCH/F allocation attempts for assignment ......32-13 32.5 C901260010 Number of signaling TCH/F allocation attempts for handover........32-14 32.6 C901260011 Number of signaling TCH/F allocation success for handover.........32-17 32.7 C901260013 Number of signaling TCH/F assignment attempts for assignment ...................................................................................................32-19 32.8 C901260016 Number of signaling TCH/F handover attempt .............................32-20 32.9 C901260017 Number of signaling TCH/F handover success ............................32-23 32.10 C901260018 Number of signaling TCH/F handover failure with reconnection .................................................................................................32-25 32.11 C901260019 Number of signaling TCH/F handover failure without reconnection .................................................................................................32-27 32.12 C901260021 Number of voice TCH/F seizure success for assignment ............32-28 32.13 C901260024 Number of voice TCH/F seizure success for handover ...............32-29 32.14 C901260026 Number of TCH/F allocation attempts for assignment (speech version 1)......................................................................................................32-32 32.15 C901260032 Number of TCH/F allocation attempts by BSC for handover (speech version 1) .........................................................................................32-33 32.16 C901260033 Number of TCH/F allocation success by BSC for handover (speech version 1) .........................................................................................32-36 32.17 C901260038 Number of TCH/F allocation attempts for assignment (speech version 2)......................................................................................................32-38 32.18 C901260044 Number of TCH/F allocation attempts by BSC for handover (speech version 2) .........................................................................................32-40

XCVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

32.19 C901260045 Number of TCH/F allocation success by BSC for handover (speech version 2) .........................................................................................32-42 32.20 C901260050 Number of TCH/F allocation attempts by BSC for assignment (speech version 3) .........................................................................................32-45 32.21 C901260056 Number of TCH/F allocation attempts by BSC for handover (speech version 3) .........................................................................................32-46 32.22 C901260057 Number of TCH/F allocation success by BSC for handover (speech version 3) .........................................................................................32-49 32.23 C901260062 Number of voice TCH/F assignment attempts by BSC ...............32-51 32.24 C901260065 Number of voice TCH/F handover attempts ...............................32-53 32.25 C901260067 Number of Voice TCH/F handover failure with reconnection .......32-56 32.26 C901260068 Number of Voice TCH/F handover failure messages do not received by BSC............................................................................................32-57 32.27 C901260070 Number of data TCH/F seizure success for assignment .............32-58 32.28 C901260073 Number of data TCH/F seizure success for handover ................32-60 32.29 C901260075 Number of data TCH/F allocation attempts for assignment .........32-62 32.30 C901260081 Number of data TCH/F allocation attempts by BSC for handover.......................................................................................................32-64 32.31 C901260082 Number of data TCH/F allocation success for handover .............32-66 32.32 C901260087 Number of data TCH/F assignment attempts .............................32-69 32.33 C901260090 Number of data TCH/F handover attempts ................................32-70 32.34 C901260092 Number of data TCH/F handover failure with reconnection .........32-73 32.35 C901260093 Number of data TCH/F handover failure messages do not received by BSC............................................................................................32-74 32.36 C901260094 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 1) .....................................................32-75 32.37 C901260095 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 1) .........................................32-76 32.38 C901260096 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 1) .....................................................32-77 32.39 C901260097 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 1) .........................................32-79 32.40 C901260098 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 2) .....................................................32-80 32.41 C901260099 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 2) .........................................32-81 32.42 C901260100 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 2) .....................................................32-82 32.43 C901260101 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 2) .........................................32-84
XCVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

32.44 C901260102 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 3) .....................................................32-85 32.45 C901260103 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 3) .........................................32-86 32.46 C901260104 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 3) .....................................................32-87 32.47 C901260105 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 3) .........................................32-89 32.48 C901260106 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 1) ..........................................32-90 32.49 C901260107 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 1) ........................................................32-91 32.50 C901260108 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 1) ........................................................32-92 32.51 C901260109 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 1)..............................................32-93 32.52 C901260110 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 1) ...........................................................32-94 32.53 C901260111 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 1) ...........................................................32-95 32.54 C901260112 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 2) ..........................................32-96 32.55 C901260113 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 2) ........................................................32-97 32.56 C901260114 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 2) ........................................................32-98 32.57 C901260115 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 2)..............................................32-99 32.58 C901260116 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 2) .........................................................32-100 32.59 C901260117 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 2) .........................................................32-101 32.60 C901260118 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 3) ........................................32-102 32.61 C901260119 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 3) ......................................................32-103 32.62 C901260120 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 3) ......................................................32-104 32.63 C901260121 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 3)............................................32-105

XCIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

32.64 C901260122 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 3) .........................................................32-106 32.65 C901260123 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 3) .........................................................32-107 32.66 C901260124 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (data) ...........................................................32-108 32.67 C901260125 Number of TCH/F allocation failure due to request UDP port failure for assignment (data) .........................................................................32-109 32.68 C901260126 Number of TCH/F allocation failure due to AIPB connection failure for assignment (data) ......................................................................... 32-110 32.69 C901260127 Number of TCH/F allocation failure due to request AIPB resource failure for handover (data) .............................................................. 32-111 32.70 C901260128 Number of TCH/F allocation failure due to request UDP port failure for handover (data) ............................................................................ 32-112 32.71 C901260129 Number of TCH/F allocation failure due to AIPB connection failure for handover (data) ............................................................................ 32-113 32.72 C901260130 Number of assign TCH/F release by forced handover to forced handover source.......................................................................................... 32-114 32.73 C901260131 Number of assign TCH/F release by forced handover to queuing user ............................................................................................... 32-115 32.74 C901260132 Number of restore TCH/F release by forced handover to DBS............................................................................................................ 32-116 32.75 C901260133 Number of assign TCHF release by forced release to forced release source............................................................................................. 32-116 32.76 C901260134 Number of assign TCH/F release by forced release to queuing user ............................................................................................................ 32-117 32.77 C901260135 Number of restore TCH/F release by forced release to DBS...... 32-117 32.78 C901260136 Number of signaling TCH/F seizure failure for assignment (cause:Abis) ................................................................................................ 32-118 32.79 C901260137 Number of signaling TCH/F seizure failure for handover (cause:Abis) ................................................................................................ 32-119 32.80 C901260138 Number of voice TCH/F seizure failure for assignment (cause:Abis) ................................................................................................ 32-119 32.81 C901260139 Number of voice TCH/F seizure failure for handover (cause:Abis ) .................................................................................................................32-120 32.82 C901260140 Number of data TCH/F seizure failure for assignment (cause:Abis) ................................................................................................32-120 32.83 C901260141 Number of data TCH/F seizure failure for handover (cause:Abis) ................................................................................................32-121 32.84 C901260142 Number of signaling TCH/F seizure failure for assignment (cause:radio resource) .................................................................................32-121
C SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

32.85 C901260143 Number of signaling TCH/F seizure failure for handover (cause:radio resource) .................................................................................32-122 32.86 C901260144 Number of voice TCH/F seizure failure for assignment (cause:radio resource) .................................................................................32-122 32.87 C901260145 Number of voice TCH/F seizure failure for handover (cause:radio resource) .................................................................................32-123 32.88 C901260146 Number of data TCH/F seizure failure for assignment (cause:radio resource) .................................................................................32-123 32.89 C901260147 Number of data TCH/F seizure failure for handover (cause:radio resource) ....................................................................................................32-124 32.90 C901260148 Number of FR_V1 assignment attempts ..................................32-124 32.91 C901260149 Number of FR_V1 assignment success...................................32-125 32.92 C901260150 Number of FR_V2 assignment attempts ..................................32-125 32.93 C901260151 Number of FR_V2 assignment success...................................32-126 32.94 C901260152 Number of FR_V3 assignment attempts ..................................32-126 32.95 C901260153 Number of FR_V3 assignment success...................................32-127 32.96 C901260154 Number of FR_V1 handover...................................................32-127 32.97 C901260155 Number of FR_V1 handover success......................................32-128 32.98 C901260156 Number of FR_V2 handover...................................................32-128 32.99 C901260157 Number of FR_V2 handover success......................................32-129 32.100 C901260158 Number of FR_V3 handover .................................................32-129 32.101 C901260159 Number of FR_V3 handover success ....................................32-130 32.102 C901260185 Resourse releasing of ordinary users due to being grabbed (TCH/F) ......................................................................................................32-130 32.103 C901260186 Handover of ordinary users due to be grabbed (TCH/F) .........32-132 32.104 C901260187 Number of Channel Request of priority users (TCH/F)............32-133 32.105 C901260188 Number of Successful Channel seize of priority users (TCH/F) ......................................................................................................32-135 32.106 C901260189 Number of Successful grabbing channel of priority users (TCH/F) ......................................................................................................32-136 32.107 C901260190 Number of TCH/F Allocation Attempts for Assignment (Speech Version 4) ...................................................................................................32-137 32.108 C901260191 Number of TCH/F Allocation Success for Assignment (Speech Version 4) ...................................................................................................32-138 32.109 C901260192 Number of TCH/F Allocation Failure Due to Channel Activation Failure for Assignment (Speech Version 4) ....................................................32-140 32.110 C901260193 Number of TCH/F Allocation Failure Due to BIU Connection Failure for Assignment (Speech Version 4) ....................................................32-141 32.111 C901260194 Number of TCH/F Allocation Attempts by BSC for Handover (Speech Version 4) ......................................................................................32-142
CI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

32.112 C901260195 Number of TCH/F Allocation Success by BSC for Handover (Speech Version 4) ......................................................................................32-145 32.113 C901260196 Number of TCH/F Allocation Failure Due to Channel Activation Failure for Handover (Speech Version 4).......................................................32-147 32.114 C901260197 Number of TCH/F Allocation Failure Due to BIU Connection Failure for Handover (Speech Version 4).......................................................32-149 32.115 C901260198 Number of TCH/F Allocation Attempts for Assignment (Speech Version 5) ...................................................................................................32-150 32.116 C901260199 Number of TCH/F Allocation Success for Assignment (Speech Version 5) ...................................................................................................32-151 32.117 C901260200 Number of TCH/F Allocation Failure Due to Channel Activation Failure for Assignment (Speech Version 5) ....................................................32-153 32.118 C901260201 Number of TCH/F Allocation Failure Due to BIU Connection Failure for Assignment (Speech Version 5) ....................................................32-154 32.119 C901260202 Number of TCH/F Allocation Attempts by BSC for Handover (Speech Version 5) ......................................................................................32-155 32.120 C901260203 Number of TCH/F Allocation Success by BSC for Handover (Speech Version 5) ......................................................................................32-158 32.121 C901260204 Number of TCH/F Allocation Failure Due to Channel Activation Failure for Handover (Speech Version 5).......................................................32-160 32.122 C901260205 Number of TCH/F Allocation Failure Due to BIU Connection Failure for Handover (Speech Version 5).......................................................32-162 32.123 C901260206 Number of TCH/F Allocation Failure Due to Request AIPB Resource Failure for Assignment (Speech Version 4).....................................32-163 32.124 C901260207 Number of TCH/F Allocation Failure Due to Request UDP Port Failure for Assignment (Speech Version 4) ....................................................32-164 32.125 C901260208 Number of TCH/F Allocation Failure Due to AIPB Connection Failure for Assignment (Speech Version 4) ....................................................32-165 32.126 C901260209 Number of TCH/F Allocation Failure Due to Request AIPB Resource Failure for Handover (Speech Version 4)........................................32-166 32.127 C901260210 Number of TCH/F Allocation Failure Due to Request UDP Port Failure for Handover (Speech Version 4).......................................................32-167 32.128 C901260211 Number of TCH/F Allocation Failure Due to AIPB Connection Failure for Handover (Speech Version 4).......................................................32-168 32.129 C901260212 Number of TCH/F Allocation Failure Due to Request AIPB Resource Failure for Assignment (Speech Version 5).....................................32-169 32.130 C901260213 Number of TCH/F Allocation Failure Due to Request UDP Port Failure for Assignment (Speech Version 5) ....................................................32-170 32.131 C901260214 Number of TCH/F Allocation Failure Due to AIPB Connection Failure for Assignment (Speech Version 5) ....................................................32-171

CII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

32.132 C901260215 Number of TCH/F Allocation Failure Due to Request AIPB Resource Failure for Handover (Speech Version 5)........................................32-172 32.133 C901260216 Number of TCH/F Allocation Failure Due to Request UDP Port Failure for Handover (Speech Version 5).......................................................32-174 32.134 C901260217 Number of TCH/F Allocation Failure Due to AIPB Connection Failure for Handover (Speech Version 5).......................................................32-175 32.135 C901260218 Number of FR_V4 Assignment Attempts ...............................32-176 32.136 C901260219 Number of FR_V4 Assignment Success................................32-176 32.137 C901260220 Number of FR_V5 Assignment Attempts ...............................32-177 32.138 C901260221 Number of FR_V5 Assignment Success................................32-177 32.139 C901260222 Number of FR_V4 Handover ................................................32-178 32.140 C901260223 Number of FR_V4 Handover Success...................................32-178 32.141 C901260224 Number of FR_V5 Handover ................................................32-179 32.142 C901260225 Number of FR_V5 Handover Success...................................32-179

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 33.12 C901270018 Number of signaling TCH/H handover failure with reconnection .................................................................................................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
CIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 C901270050 Number of TCH/H allocation attempts for assignment (speech version 3)......................................................................................................33-41 33.21 C901270051 Number of TCH/H allocation success for assignment (speech version 3)......................................................................................................33-43 33.22 C901270056 Number of TCH/H allocation attempts by BSC for handover (speech version 3) .........................................................................................33-44 33.23 C901270057 Number of TCH/H allocation success for handover (speech version 3)......................................................................................................33-47 33.24 C901270062 Number of Voice TCH/H assignment attempts by BSC...............33-49 33.25 C901270065 Number of Voice TCH/H handover attempts ..............................33-51 33.26 C901270067 Number of Voice TCH/H handover failure with reconnection .......33-54 33.27 C901270068 Number of Voice TCH/H handover failure messages do not received by BSC............................................................................................33-55 33.28 C901270070 Number of data TCH/H seizure success for assignment .............33-56 33.29 C901270073 Number of data TCH/H seizure success for handover ................33-58 33.30 C901270075 Number of data TCH/H allocation attempts for assignment by BSC..............................................................................................................33-60 33.31 C901270076 Number of data TCH/H allocation success for assignment..........33-62 33.32 C901270081 Number of data TCH/H allocation attempts by BSC ...................33-63 33.33 C901270082 Number of data TCH/H allocation success for handover.............33-66 33.34 C901270087 Number of data TCH/H assignment attempts by BSC ................33-68 33.35 C901270090 Number of data TCH/H handover attempts................................33-70 33.36 C901270092 Number of data TCH/H handover failure with reconnection.........33-73 33.37 C901270093 Number of data TCH/H handover failure do not received by BSC..............................................................................................................33-74 33.38 C901270094 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 1) .............................................................33-76 33.39 C901270095 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 1) .........................................33-77 33.40 C901270096 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 1) .............................................................33-78 33.41 C901270097 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 1) .........................................33-79 33.42 C901270102 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 3) .............................................................33-81

CIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

33.43 C901270103 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 3) .........................................33-82 33.44 C901270104 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 3) .............................................................33-83 33.45 C901270105 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 3) .........................................33-84 33.46 C901270106 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 1) ..........................................33-86 33.47 C901270107 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 1) ........................................................33-87 33.48 C901270108 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 1) ........................................................33-88 33.49 C901270109 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 1)..............................................33-89 33.50 C901270110 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 1) ...........................................................33-90 33.51 C901270111 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 1) ...........................................................33-91 33.52 C901270118 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 3) ..........................................33-92 33.53 C901270119 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 3) ........................................................33-93 33.54 C901270120 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 3) ........................................................33-94 33.55 C901270121 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 3)..............................................33-95 33.56 C901270122 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 3) ...........................................................33-96 33.57 C901270123 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 3) ...........................................................33-97 33.58 C901270124 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (data) .............................................................33-98 33.59 C901270125 Number of TCH/H allocation failure due to request UDP port failure for assignment (data) ...........................................................................33-99 33.60 C901270126 Number of TCH/H allocation failure due to AIPB connection failure for assignment (data) .........................................................................33-100 33.61 C901270127 Number of TCH/H allocation failure due to request AIPB resource failure for handover (data) ..............................................................33-101 33.62 C901270128 Number of TCH/H allocation failure due to request UDP port failure for handover (data) ............................................................................33-102

CV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

33.63 C901270129 Number of TCH/H allocation failure due to AIPB connection failure for handover (data) ............................................................................33-103 33.64 C901270130 Number of assign TCH/H release by forced handover to forced handover source..........................................................................................33-104 33.65 C901270131 Number of assign TCH/H release by forced handover to queuing user ...............................................................................................33-104 33.66 C901270132 Number of restore TCH/H release by forced handover to DBS............................................................................................................33-105 33.67 C901270133 Number of assign TCH/H release by forced release to forced release source.............................................................................................33-105 33.68 C901270134 Number of assign TCH/H release by forced release to queuing user ............................................................................................................33-106 33.69 C901270135 Number of restore TCH/H release by forced release to DBS ......33-107 33.70 C901270136 Number of signaling TCH/H seize failure for assign due to Abis lack.............................................................................................................33-107 33.71 C901270137 Number of signaling TCH/H seize failure for handover due to Abis lack .....................................................................................................33-108 33.72 C901270138 Number of voice TCH/H seizure failure for assignment (cause:Abis) ................................................................................................33-108 33.73 C901270139 Number of voice TCH/H seizure failure for handover (cause:Abis ) .................................................................................................................33-109 33.74 C901270140 Number of data TCH/H seizure failure for assignment (cause:Abis) ................................................................................................33-109 33.75 C901270141 Number of data TCH/H seizure failure for handover (cause:Abis) ................................................................................................ 33-110 33.76 C901270142 Number of signaling TCH/H seize failure for assign due to radio resource lack............................................................................................... 33-110 33.77 C901270143 Number of signaling TCH/H seize failure for handover due to radio resource lack ...................................................................................... 33-111 33.78 C901270144 Number of voice TCH/H seizure failure for assignment (cause:radio resource) ................................................................................. 33-111 33.79 C901270145 Number of voice TCH/H seizure failure for handover (cause:radio resource) ................................................................................. 33-112 33.80 C901270146 Number of data TCH/H seizure failure for assignment (cause:radio resource) ................................................................................. 33-112 33.81 C901270147 Number of data TCH/H seizure failure for handover (cause:radio resource) .................................................................................................... 33-113 33.82 C901270148 Number of HR_V1 assignment attempts ................................. 33-113 33.83 C901270149 Number of HR_V1 assignment success .................................. 33-114 33.84 C901270150 Number of HR_V3 assignment attempts ................................. 33-114

CVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

33.85 C901270151 Number of HR_V3 assignment success .................................. 33-115 33.86 C901270152 Number of HR_V1 handover .................................................. 33-115 33.87 C901270153 Number of HR_V1 handover success ..................................... 33-116 33.88 C901270154 Number of HR_V3 handover .................................................. 33-116 33.89 C901270155 Number of HR_V3 handover success ..................................... 33-117 33.90 C901270177 Resource releasing of ordinary users due to being grabbed (TCH/H) ...................................................................................................... 33-117 33.91 C901270178 Handover of ordinary users due to being grabbed (TCH/H) ...... 33-118 33.92 C901270179 Number of Channel Request of priority users (TCH/H) .............33-120 33.93 C901270180 Number of Successful Channel seize of priority users (TCH/H) ......................................................................................................33-121 33.94 C901270181 Number of Successful grabbing channel of priority users (TCH/H) ......................................................................................................33-122 33.95 C901270182 Number of HR_V4 Assignment Attempts.................................33-123 33.96 C901270183 Number of HR_V4 Assignment Success .................................33-124 33.97 C901270184 Number of HR_V4 Handover..................................................33-124 33.98 C901270185 Number of HR_V4 Handover Success ....................................33-125 33.99 C901270186 Number of TCH/H Allocation Attempts for Assignment (Speech Version 4) ...................................................................................................33-125 33.100 C901270187 Number of TCH/H Allocation Success for Assignment (Speech Version4) ....................................................................................................33-127 33.101 C901270188 Number of TCH/H Allocation Failure Due to Channel Activation Failure for Assignment (Speech Version 4) ....................................................33-128 33.102 C901270189 Number of TCH/H Allocation Failure Due to BIU Connection Failure for Assignment (Speech Version 4) ....................................................33-129 33.103 C901270190 Number of TCH/H Allocation Attempts by BSC for Handover (Speech Version 4) ......................................................................................33-130 33.104 C901270191 Number of TCH/H Allocation Success by BSC for Handover (Speech Version 4) ......................................................................................33-133 33.105 C901270192 Number of TCH/H Allocation Failure Due to Channel Activation Failure for Handover (Speech Version 4).......................................................33-135 33.106 C901270193 Number of TCH/H Allocation Failure Due to BIU Connection Failure for Handover (Speech Version 4).......................................................33-137 33.107 C901270194 Number of TCH/H Allocation Failure Due to Request AIPB Resource Failure for Assignment (Speech Version 4).....................................33-138 33.108 C901270195 Number of TCH/H Allocation Failure Due to Request UDP Port Failure for Assignment (Speech Version 4) ....................................................33-139 33.109 C901270196 Number of TCH/H Allocation Failure Due to AIPB Connection Failure for Assignment (Speech Version 4) ....................................................33-140

CVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

33.110 C901270197 Number of TCH/H Allocation Failure Due to Request AIPB Resource Failure for Handover (Speech Version 4)........................................33-141 33.111 C901270198 Number of TCH/H Allocation Failure Due to Request UDP Port Failure for Handover (Speech Version 4).......................................................33-142 33.112 C901270199 Number of TCH/H Allocation Failure Due to AIPB Connection Failure for Handover (Speech Version 4).......................................................33-143

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-6 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
CVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 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-32 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-36 34.41 C901280040 Number of ABIS_IMM_ASSIGN_CMD messages ......................34-37 34.42 C901280041 Number of ABIS_SMS_BROADCAST_REQ messages .............34-38 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-42 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-45 34.52 C901280051 Number of ABIS_OVERLOAD messages..................................34-46 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-49 34.57 C901280056 Number of ABIS_PWRCTRL_IND messages ............................34-50 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-52 34.61 C901280063 Number of ABIS_PACKET_PBCCH_PARA messages ...............34-53 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
CIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

34.65 C901280067 Number of ABIS_PACKET_CONNECT_FAIL_IND messages .....................................................................................................34-56 34.66 C901280068 Number of ABIS_PACKET_PRACH_OVERLOAD messages ......34-57 34.67 C901280069 Number of ABIS_PACKET_PCH_OVERLOAD messages ..........34-57 34.68 C901280070 Number of ABIS_PACKET_TA_REQUEST messages ...............34-58 34.69 C901280071 Number of ABIS_PACKET_TA_REQUEST_ACK messages.......34-59 34.70 C901280072 Number of ABIS_PACKET_CHN_CONFIG_CHG messages ......34-60 34.71 C901280073 Number of ABIS_PACKET_CHN_CONFIG_CHG_RESP messages .....................................................................................................34-61 34.72 C901280074 Number of ABIS_PACKET_PIA_DEL_IND messages ................34-62 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-63 34.75 C901280077 Number of ABIS_EGPRS_PACKET_CHN_REQ messages........34-64 34.76 C901280078 Number of ABIS_PS_CHANNEL_ACTIVE messages ................34-65 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-67 34.80 C901280082 Number of ABIS_PS_CHANNEL_RELEASE_ACK messages .....................................................................................................34-68 34.81 C901280083 Number of ABIS_PS_CHANNEL_RELEASE_NACK messages .....................................................................................................34-69 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-71 34.85 C901280087 Number of ABIS_GLOBAL_RESET messages ..........................34-72 34.86 C901280088 Number of ABIS_GLOBAL_RESET_ACK messages .................34-73 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-75 34.90 C901280092 Number of ABIS_CSCONN_CMM_REQ messages ...................34-76 34.91 C901280093 Number of ABIS_CSCONN_CMM_ACK messages ...................34-77 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-79 34.95 C901280097 Number of ABIS_CCMCONN_CMM_NACK messages ..............34-80 34.96 C901280098 Number ABIS_PACKET_ACCESS_REJ messages ...................34-81 34.97 C901280099 Number of ABIS_PACKET_IMM_ASSIGN_CMD_NEW messages .....................................................................................................34-82

CX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

34.98 C901280100 Number of PACKET_DOWNLINK_ASSIGN messages ..............34-82 34.99 C901280101 Number of PACKET_UPLINK_ASSIGN messages ....................34-83 34.100 C901280102 Number of ABIS_PACKET_ACCESS_REJ_NEW messages .....................................................................................................34-84 34.101 C901280105 Peak of CS Paging Messages From CN..................................34-85 34.102 C901280106 Peak of CS Paging Messages From SGSN .............................34-86 34.103 C901280107 Peak of PS Paging Messages From SGSN .............................34-86 34.104 C901280108 Peak of Paging Messages......................................................34-87 34.105 C901280109 Time of Paging reached the threshold .....................................34-87

Chapter 35 Gb Message Statistics (BVC Cell) ....................................... 35-1

35.1 Overview ....................................................................................................... 35-2 35.2 C901290001 Sum of UL UNITDATA messages handled at BSSGP level............ 35-2 35.3 C901290002 Sum of DL UNITDATA messages handled at BSSGP level............ 35-3 35.4 C901290003 Number of RA-CAPABILITY message received ............................ 35-4 35.5 C901290004 Number of PTP packet paging received by BSC ........................... 35-4 35.6 C901290005 Number of PTP circuit paging received by BSC ............................ 35-5 35.7 C901290006 Number of RA-CAPABILITY-UPDATE message sent .................... 35-6 35.8 C901290007 Number of RA-CAPABILITY-UPDATE-ACK message received ...... 35-6 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 35.14 C901290013 Number of FLOW-CONTROL-BVC-ACK messages received by BSC..............................................................................................................35-10 35.15 C901290014 Number of FLOW-CONTROL-MS messages sent by BSC ......... 35-11 35.16 C901290015 Number of FLOW-CONTROL-MS-ACK messages received by BSC..............................................................................................................35-12 35.17 C901290016 Number of FLOW-CONTROL-PFC messages sent by BSC........35-13 35.18 C901290017 Number of FLOW-CONTROL-PFC-ACK messages received by 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-16 35.22 C901290021 Number of Status messages sent with Cell service congestion ....................................................................................................35-16
CXI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

35.23 C901290022 Number of Status messages sent with protocol error..................35-17 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-18 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-19 35.28 C901290027 Number of Status messages received with Processor overload........................................................................................................35-19 35.29 C901290028 Number of DOWNLOAD-BSS-PFC messages sent by BSC .......35-20 35.30 C901290029 Number of BVCCREATE-BSS-PFC messages received by BSC..............................................................................................................35-20 35.31 C901290030 Number of CREATE-BSS-PFC-ACK messages sent by BSC ......35-21 35.32 C901290031 Number of CREATE-BSS-PFC-NACK messages sent by BSC..............................................................................................................35-22 35.33 C901290032 Number of MODIFY-BSS-PFC messages sent by BSC ..............35-23 35.34 C901290033 Number of MODIFY-BSS-PFC-ACK messages received by BSC..............................................................................................................35-24 35.35 C901290034 Number of DELETE-BSS-PFC messages received by 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

CXII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 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.33 C901300032 Number of congestion occurrence of level 2 ..............................36-25 36.34 C901300033 Number of congestion recovery of level 2..................................36-25 36.35 C901300034 Number of congestion occurrence of level 3 ..............................36-25 36.36 C901300035 Number of congestion recovery of level 3..................................36-25 36.37 C901300036 Number of BECN.....................................................................36-26
CXIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 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.18 C901310017 Number of BVC-RESET message received ...............................37-14 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.28 C901310027 Number of status messages sent with BVCI Unknown ...............37-22 37.29 C901310028 Number of status messages sent with cell service congestion ......37-22 37.30 C901310029 Number of status messages sent with protocol error ..................37-23 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
CXIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 37.40 C901310039 Number of status messages received with cell service congestion ....................................................................................................37-29 37.41 C901310040 Number of status messages received with protocol error............37-29 37.42 C901310041 Number of status messages received with processor 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 incompatible error..........................................................................................37-34 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

CXV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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

CXVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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-36 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-37 38.38 C901320037 Sum of Periodic BS Power (SDCCH) Search Result ..................38-37 38.39 C901320038 Number of Periodic BS Power (SDCCH) Search........................38-38 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-39 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-40 38.44 C901320043 Sum of Periodic DL Signal Level (SDCCH) Search Result..........38-40 38.45 C901320044 Number of Periodic DL Signal Level (SDCCH) Search ...............38-41 38.46 C901320045 Number of BTS Power Increase Fails Due to Power Increase Freeze ..........................................................................................................38-41 38.47 C901320046 Number of Uplink CIR Normal Grade0 (Below -2 dB) Samples .......................................................................................................38-42 38.48 C901320047 Number of Uplink CIR Normal Grade1 (-2 to 0.5 dB) Samples .......................................................................................................38-42 38.49 C901320048 Number of Uplink CIR Normal Grade2 (1 to 3.5 dB) Samples ......38-43 38.50 C901320049 Number of Uplink CIR Normal Grade3 (4 to 6.5 dB) Samples ......38-43 38.51 C901320050 Number of Uplink CIR Normal Grade4 (7 to 9.5 dB) Samples ......38-44 38.52 C901320051 Number of Uplink CIR Normal Grade5 (10 to 12.5 dB) Samples .......................................................................................................38-44 38.53 C901320052 Number of Uplink CIR Normal Grade6 (13 to 15.5 dB) Samples .......................................................................................................38-45 38.54 C901320053 Number of Uplink CIR Normal Grade7 (16 to 18.5 dB) Samples .......................................................................................................38-45 38.55 C901320054 Number of Uplink CIR Normal Grade8 (19 to 21.5 dB) Samples .......................................................................................................38-46 38.56 C901320055 Number of Uplink CIR Normal Grade9 (Above 21.5 dB) Samples .......................................................................................................38-46 38.57 C901320056 Number of Uplink CIR Improved Grade0 (Below -2 dB) Samples .......................................................................................................38-47 38.58 C901320057 Number of Uplink CIR Improved Grade1 (-2 to 0.5 dB) Samples .......................................................................................................38-47 38.59 C901320058 Number of Uplink CIR Improved Grade2 (1 to 3.5 dB) Samples .......................................................................................................38-48 38.60 C901320059 Number of Uplink CIR Improved Grade3 (4 to 6.5 dB) Samples .......................................................................................................38-48

CXVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

38.61 C901320060 Number of Uplink CIR Improved Grade4 (7 to 9.5 dB) Samples .......................................................................................................38-49 38.62 C901320061 Number of Uplink CIR Improved Grade5 (10 to 12.5 dB) Samples .......................................................................................................38-49 38.63 C901320062 Number of Uplink CIR Improved Grade6 (13 to 15.5 dB) Samples .......................................................................................................38-50 38.64 C901320063 Number of Uplink CIR Improved Grade7 (16 to 18.5 dB) Samples .......................................................................................................38-50 38.65 C901320064 Number of Uplink CIR Improved Grade8 (19 to 21.5 dB) Samples .......................................................................................................38-51 38.66 C901320065 Number of Uplink CIR Improved Grade9 (Above 21.5 dB) Samples .......................................................................................................38-51 38.67 C901320070 Number of BTS Power Increase Due to Power Rescue ..............38-52 38.68 C901320071 Number of Channel Active BTS Power Change Due to Power Dynamic Share..............................................................................................38-52

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.3 C901340002 Number of PTP packet paging received by BSC ........................... 40-3 40.4 C901340003 Number of PTP circuit paging received by BSC ............................ 40-4 40.5 C901340004 Number of RA-CAPABILITY-UPDATE message sent .................... 40-4 40.6 C901340005 Number of RA-CAPABILITY-UPDATE-ACK message received ...... 40-5 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
CXVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 40.12 C901340011 Number of FLOW-CONTROL-BVC-ACK messages received by BSC............................................................................................................... 40-9 40.13 C901340012 Number of FLOW-CONTROL-MS messages sent by BSC .........40-10 40.14 C901340013 Number of FLOW-CONTROL-MS-ACK messages received by BSC.............................................................................................................. 40-11 40.15 C901340014 Number of FLOW-CONTROL-PFC messages sent by BSC........40-12 40.16 C901340015 Number of FLOW-CONTROL-PFC-ACK messages received by BSC..............................................................................................................40-13 40.17 C901340016 Number of status messages sent by BSC .................................40-13 40.18 C901340017 Number of status messages received by BSC ...........................40-14 40.19 C901340018 Number of status messages sent with BVCI Unknown ...............40-15 40.20 C901340019 Number of status messages sent with cell service congestion ......40-15 40.21 C901340020 Number of status messages sent with protocol error ..................40-16 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 40.24 C901340023 Number of status messages received with cell service congestion ....................................................................................................40-18 40.25 C901340024 Number of status messages received with protocol error............40-18 40.26 C901340025 Number of status messages received with processor overload........................................................................................................40-19 40.27 C901340026 Number of DOWNLOAD-BSS-PFC messages sent by BSC .......40-19 40.28 C901340027 Number of BVCCREATE-BSS-PFC messages received by BSC..............................................................................................................40-20 40.29 C901340028 Number of CREATE-BSS-PFC-ACK messages sent by BSC ......40-21 40.30 C901340029 Number of CREATE-BSS-PFC-NACK messages sent by BSC..............................................................................................................40-22 40.31 C901340030 Number of MODIFY-BSS-PFC messages sent by BSC ..............40-23 40.32 C901340031 Number of MODIFY-BSS-PFC-ACK messages received by BSC..............................................................................................................40-24 40.33 C901340032 Number of DELETE-BSS-PFC messages received by BSC........40-25 40.34 C901340033 Number of DELETE-BSS-PFC-ACK messages sent by BSC ......40-25 40.35 C901340034 Number of DELETE-BSS-PFC-REQ messages received by BSC..............................................................................................................40-26

CXIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

40.36 C901340035 Number of PS-HANDOVER-REQUIRED messages sent by BSC..............................................................................................................40-26 40.37 C901340036 Number of PS-HANDOVER-REQUIRED-ACK messages received by BSC............................................................................................40-27 40.38 C901340037 Number of PS-HANDOVER-REQUIRED-NACK messages received by BSC............................................................................................40-28 40.39 C901340038 Number of PS-HANDOVER-REQUEST messages received by BSC..............................................................................................................40-29 40.40 C901340039 Number of PS-HANDOVER-REQUEST-ACK messages sent by BSC..............................................................................................................40-30 40.41 C901340040 Number of PS-HANDOVER-REQUEST-NACK messages sent by BSC .........................................................................................................40-31 40.42 C901340041 Number of PS-HANDOVER-COMPLETE messages sent by BSC..............................................................................................................40-33 40.43 C901340042 Number of PS-HANDOVER-CANCEL messages sent by BSC..............................................................................................................40-34 40.44 C901340043 Number of PS-HANDOVER-REQUEST messages with Service UTRAN CCO received by BSC .......................................................................40-34 40.45 C901340044 Number of CREATE-BSS-PFC messages with Service UTRAN CCO received by BSC ...................................................................................40-35

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.4 C901350003 Number of SUSPEND message sent ........................................... 41-3 41.5 C901350004 Number of SUSPEND-ACK message received............................. 41-4 41.6 C901350005 Number of SUSPEND-NACK message received .......................... 41-5 41.7 C901350006 Number of RESUME message sent ............................................. 41-5 41.8 C901350007 Number of RESUME-ACK message received............................... 41-6 41.9 C901350008 Number of RESUME-NACK message received ............................ 41-7 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.18 C901350017 Number of BVC-RESET message received ...............................41-12
CXX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 41.28 C901350027 Number of status messages sent with BVCI Unknown ...............41-19 41.29 C901350028 Number of status messages sent with cell service congestion ......41-19 41.30 C901350029 Number of status messages sent with protocol error ..................41-20 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 incompatible error..........................................................................................41-25 41.39 C901350038 Number of status messages received with BVCI unknown..........41-26 41.40 C901350039 Number of status messages received with cell service congestion ....................................................................................................41-27 41.41 C901350040 Number of status messages received with protocol error............41-27 41.42 C901350041 Number of status messages received with processor 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

CXXI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 incompatible error..........................................................................................41-33 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 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

CXXII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 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
CXXIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 ACKNOWLEDGE messages ..........................................................................42-61 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 42.87 C901360086 Number of Release Clear Request on SDCCH ..........................42-74 42.88 C901360087 Number of Release Clear Request on TCH/F ............................42-74 42.89 C901360088 Number of Release Clear Request on TCH/H............................42-75

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

CXXIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

43.4 C901370003 Number of UL BSSMAP messages.............................................. 43-3 43.5 C901370004 Number of DL BSSMAP messages.............................................. 43-4 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 43.9 C901370008 Number of Chosen for MSC by NRI ............................................. 43-6 43.10 C901370009 Number of Chosen for MSC by Paging Source ........................... 43-7 43.11 C901370010 Number of Chosen for MSC Load Share by IMSI ........................ 43-8 43.12 C901370011 Number of Chosen for MSC Load Share by IMEI ........................ 43-8 43.13 C901370012 Number of Chosen for MSC Load Share by Reselect MSC ......... 43-9

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 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 C901380016 The times of User Plane transport without RTP multiplexing .......44-12 44.18 C901380017 The times of RTP multiplexing applied without RTP header compression..................................................................................................44-13 44.19 C901380018 The times of RTP multiplexing applied with RTP header compression..................................................................................................44-14 44.20 C901380019 Mean number of busy trunk circuits...........................................44-15 44.21 C901380020 Mean number of seizure UDP port............................................44-16

Chapter 45 Ater Message Measurement ................................................ 45-1

45.1 Overview ....................................................................................................... 45-2

CXXV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 ACKNOWLEDGE messages ..........................................................................45-10 45.17 C901390016 Number of DL BLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages ..........................................................................45-10 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 ACKNOWLEDGE messages ..........................................................................45-12 45.21 C901390020 Number of DL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages ..........................................................................45-12 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
CXXVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 ACKNOWLEDGE messages ..........................................................................45-18 45.35 C901390034 Number of DL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages ..........................................................................45-19 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 ACKNOWLEDGE messages ..........................................................................45-20 45.39 C901390038 Number of DL UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages ..........................................................................45-21 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 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

CXXVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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-2 48.2 C901420001 Number of IP packets dropped by SCTP due to some reasons...... 48-2 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
CXXVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 48.31 C901420030 Number of abort from peer .......................................................48-18 48.32 C901420031 Number of association break by retransmission .........................48-18

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 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-3 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
CXXIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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(ms)..................51-22 51.28 C901450027 The min length of packet latency period in Abis(ms)...................51-23 51.29 C901450028 The average length of packet latency period in Abis(ms) ............51-23 51.30 C901450029 The latest length of packet latency period in Abis(ms) ................51-24 51.31 C901450030 The length of packet latency period between 0 and 20 ms (20 included) in Abis ............................................................................................51-24 51.32 C901450031 The length of packet latency period between 20 ms and 40 ms (40 included) in Abis ......................................................................................51-25 51.33 C901450032 The length of packet latency period between 40 ms and 60 ms (60 included) in Abis ......................................................................................51-25 51.34 C901450033 The length of packet latency period between 60 ms and 80 ms (80 included) in Abis ......................................................................................51-26 51.35 C901450034 The length of packet latency period between 80 ms and 100 ms (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
CXXX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

51.37 C901450036 The length of packet latency period between 120 ms and 140 ms (140 included) in Abis ...............................................................................51-27 51.38 C901450037 The length of packet latency period between 140 ms and 160 ms (160 included) in Abis ...............................................................................51-28 51.39 C901450038 The length of packet latency period between 160 ms and 180 ms (180 included) in Abis ...............................................................................51-28 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(ms) ......51-29 51.42 C901450041 The min length of downlink packet latency period in Gb(ms).......51-30 51.43 C901450042 The average length of downlink packet latency period in Gb(ms) .........................................................................................................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 51.46 C901450045 The length of downlink packet latency period between 200 ms and 300 ms (300 included) in Gb ....................................................................51-32 51.47 C901450046 The length of downlink packet latency period between 300 ms and 400 ms (400 included) in Gb ....................................................................51-32 51.48 C901450047 The length of downlink packet latency period between 400 ms and 600 ms (600 included) in Gb ....................................................................51-33 51.49 C901450048 The length of downlink packet latency period between 600 ms 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(ms) ..........51-34 51.52 C901450051 The min length of uplink packet latency period in Gb(ms) ...........51-35 51.53 C901450052 The average length of uplink packet latency period in Gb(ms) ......51-35 51.54 C901450053 LLC Stall Num .........................................................................51-35 51.55 C901450054 MAC Resource Congestion ......................................................51-36 51.56 C901450055 BSSGP Resource Congestion ..................................................51-36 51.57 C901450056 Number of Pushing Down Uplink BandWidth ............................51-37 51.58 C901450057 Number of Pushing Down Downlink BandWidth ........................51-37 51.59 C901450058 Number of Pushing Up Uplink BandWidth .................................51-38 51.60 C901450059 Number of Pushing Up Downlink BandWidth .............................51-39 51.61 C901450060 PDTCH Downlink Signaling Buffer Average Length....................51-40 51.62 C901450073 Total Uplink GPRS Throughput Efficiency..................................51-40 51.63 C901450074 Total Downlink GPRS Throughput Efficiency .............................51-41

CXXXI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

51.64 C901450075 Total Uplink EGPRS Throughput Efficiency ...............................51-42 51.65 C901450076 Total Downlink EGPRS Throughput Efficiency ...........................51-43

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 52.7 C901460006 Peak Downlink throughput in FR ................................................. 52-5 52.8 C901460007 Peak Uplink throughput in FR...................................................... 52-5

Chapter 53 OMP PS Service Statistics ................................................... 53-1

53.1 Overview ....................................................................................................... 53-1 53.2 C901470001 Number of SUSPEND message sent ........................................... 53-1 53.3 C901470002 Number of SUSPEND-ACK message received............................. 53-2 53.4 C901470003 Number of SUSPEND-NACK message received .......................... 53-2 53.5 C901470004 Number of RESUME message sent ............................................. 53-3 53.6 C901470005 Number of RESUME-ACK message received............................... 53-3 53.7 C901470006 Number of RESUME-NACK message received ............................ 53-4

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 acknowledgements ......................................................................................... 54-5 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 acknowledgements ......................................................................................... 54-6 54.11 C901480010 Number of SNS-CONFIG initiated by SGSN received failed acknowledgements ......................................................................................... 54-7 54.12 C901480011 Number of SNS-ADD initiated by BSC........................................ 54-7 54.13 C901480012 Number of SNS-ADD initiated by BSC received successful acknowledgements ......................................................................................... 54-8
CXXXII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

54.14 C901480013 Number of SNS-ADD initiated by BSC received failed acknowledgements ......................................................................................... 54-8 54.15 C901480014 Number of SNS-ADD initiated by BSC without response ............. 54-9 54.16 C901480015 Number of SNS-ADD initiated by SGSN received successful acknowledgements ......................................................................................... 54-9 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 acknowledgements ........................................................................................54-12 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 acknowledgements ........................................................................................54-13 54.23 C901480022 Number of SNS-DELETE initiated by SGSN received failed acknowledgements ........................................................................................54-13 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 56.2 C901500001 Sum of UL UNITDATA messages handled at BSSGP level............ 56-1 56.3 C901500002 Sum of DL UNITDATA messages handled at BSSGP level............ 56-1
CXXXIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 57 Queue Measurement............................................................. 57-1

57.1 Overview ....................................................................................................... 57-1 57.2 C901510001 Average length of queue ............................................................. 57-1 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 HO 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
CXXXIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 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-3 62.4 C901560003 Number of received IMSI when link establish ............................... 62-4 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-5 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-6 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-7 62.11 C901560010 Number of UL DTM database resource assignment failure in dedicated mode ............................................................................................. 62-8 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-9 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-10 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-11 62.18 C901560017 Number of successfully sent LLC packet on FACCH in dedicated mode ............................................................................................62-12 62.19 C901560018 Attempt Number of DTM established due to SGSN sent LLC packets .........................................................................................................62-12 62.20 C901560019 Number of DTM attempts failure ...............................................62-13 62.21 C901560020 Number of DL DTM resource assignment success.....................62-13 62.22 C901560021 Number of DL DTM resource assignment failure........................62-14 62.23 C901560022 Number of handover(intra-cell) attempts due to DL DTM ............62-15 62.24 C901560023 Number of successfully handover occurs due to DL DTM ...........62-15 62.25 C901560024 Number of handover failure occurs due to DL DTM....................62-16 62.26 C901560025 Number of DL DTM failure occurs due to handover....................62-16

CXXXV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

62.27 C901560026 Number of successfully DL DTM establishment .........................62-17 62.28 C901560027 Number of Packet CS Request in Packet Transfer Mode............62-17 62.29 C901560028 Number of MO CS Success and PS Reallocation ......................62-18 62.30 C901560029 Number of MO CS Success and PS Non-Reallocation ...............62-18 62.31 C901560030 Number of MO CS Success and PS Release ............................62-19 62.32 C901560031 Number of MO CS Fail and PS Maintain ...................................62-19 62.33 C901560032 Number of MO CS Fail and PS Release....................................62-19 62.34 C901560033 Number of CS Paging in Packet Transfer Mode .........................62-20 62.35 C901560034 Number of MT CS Success and PS Reallocation .......................62-20 62.36 C901560035 Number of MT CS Success and PS Non-Reallocation................62-21 62.37 C901560036 Number of MT CS Success and PS Release .............................62-21 62.38 C901560037 Number of MT CS Fail and PS Maintain ....................................62-21 62.39 C901560038 Number of MT CS Fail and PS Release ....................................62-22 62.40 C901560039 Number of Packet CS Release Indication..................................62-22 62.41 C901560040 Number of CS Release and PS Maintain...................................62-23 62.42 C901560041 Number of DTM Successful Establishment................................62-23 62.43 C901560042 Number of CS drop at DTM mode.............................................62-24 62.44 C901560043 Number of PS drop at DTM mode.............................................62-24 62.45 C901560044 Peak Value of Uplink GPRS Throughput Efficiency ....................62-25 62.46 C901560045 Peak Value of Uplink EGPRS Throughput Efficiency ..................62-26 62.47 C901560046 Peak Value of Downlink GPRS Throughput Efficiency ................62-26 62.48 C901560047 Peak Value of Downlink EGPRS Throughput Efficiency..............62-27 62.49 C901560048 Number of Enhanced DTM CS Drop at DTM Mode ....................62-27 62.50 C901560049 Number of DLDC Resource Request in Dedicated Mode............62-28 62.51 C901560050 Number of DLDC Resource Assignment in Dedicated Mode.......62-28 62.52 C901560051 Number of RTTI Resource Request in Dedicated Mode .............62-28 62.53 C901560052 Number of RTTI Resource Assignment in Dedicated Mode ........62-29

Chapter 63 LAPD Measurement .............................................................. 63-1

63.1 Overview ....................................................................................................... 63-1 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

CXXXVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 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
CXXXVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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

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
CXXXVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 Reprot 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 68.3 C901620002 Number of samples of UL RQ=0 and receive level between 11 and 15 ........................................................................................................... 68-6 68.4 C901620003 Number of samples of UL RQ=0 and receive level between 16 and 20 ........................................................................................................... 68-7 68.5 C901620004 Number of samples of UL RQ=0 and receive level between 21 and 30 ........................................................................................................... 68-8 68.6 C901620005 Number of samples of UL RQ=0 and receive level between 31 and 40 ........................................................................................................... 68-8 68.7 C901620006 Number of samples of UL RQ=0 and receive level between 41 and 63 ........................................................................................................... 68-9 68.8 C901620007 Number of samples of UL RQ=1 and receive level between 0 and 10 ..........................................................................................................68-10 68.9 C901620008 Number of samples of UL RQ=1 and receive level between 11 and 15 .......................................................................................................... 68-11 68.10 C901620009 Number of samples of UL RQ=1 and receive level between 16 and 20 .......................................................................................................... 68-11 68.11 C901620010 Number of samples of UL RQ=1 and receive level between 21 and 30 ..........................................................................................................68-12 68.12 C901620011 Number of samples of UL RQ=1 and receive level between 31 and 40 ..........................................................................................................68-13 68.13 C901620012 Number of samples of UL RQ=1 and receive level between 41 and 63 ..........................................................................................................68-14 68.14 C901620013 Number of samples of UL RQ=2 and receive level between 0 and 10 ..........................................................................................................68-15 68.15 C901620014 Number of samples of UL RQ=2 and receive level between 11 and 15 ..........................................................................................................68-15

CXXXIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

68.16 C901620015 Number of samples of UL RQ=2 and receive level between 16 and 20 ..........................................................................................................68-16 68.17 C901620016 Number of samples of UL RQ=2 and receive level between 21 and 30 ..........................................................................................................68-17 68.18 C901620017 Number of samples of UL RQ=2 and receive level between 31 and 40 ..........................................................................................................68-18 68.19 C901620018 Number of samples of UL RQ=2 and receive level between 41 and 63 ..........................................................................................................68-19 68.20 C901620019 Number of samples of UL RQ=3 and receive level between 0 and 10 ..........................................................................................................68-19 68.21 C901620020 Number of samples of UL RQ=3 and receive level between 11 and 15 ..........................................................................................................68-20 68.22 C901620021 Number of samples of UL RQ=3 and receive level between 16 and 20 ..........................................................................................................68-21 68.23 C901620022 Number of samples of UL RQ=3 and receive level between 21 and 30 ..........................................................................................................68-22 68.24 C901620023 Number of samples of UL RQ=3 and receive level between 31 and 40 ..........................................................................................................68-23 68.25 C901620024 Number of samples of UL RQ=3 and receive level between 41 and 63 ..........................................................................................................68-23 68.26 C901620025 Number of samples of UL RQ=4 and receive level between 0 and 10 ..........................................................................................................68-24 68.27 C901620026 Number of samples of UL RQ=4 and receive level between 11 and 15 ..........................................................................................................68-25 68.28 C901620027 Number of samples of UL RQ=4 and receive level between 16 and 20 ..........................................................................................................68-26 68.29 C901620028 Number of samples of UL RQ=4 and receive level between 21 and 30 ..........................................................................................................68-27 68.30 C901620029 Number of samples of UL RQ=4 and receive level between 31 and 40 ..........................................................................................................68-27 68.31 C901620030 Number of samples of UL RQ=4 and receive level between 41 and 63 ..........................................................................................................68-28 68.32 C901620031 Number of samples of UL RQ=5 and receive level between 0 and 10 ..........................................................................................................68-29 68.33 C901620032 Number of samples of UL RQ=5 and receive level between 11 and 15 ..........................................................................................................68-30 68.34 C901620033 Number of samples of UL RQ=5 and receive level between 16 and 20 ..........................................................................................................68-31 68.35 C901620034 Number of samples of UL RQ=5 and receive level between 21 and 30 ..........................................................................................................68-31

CXL SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

68.36 C901620035 Number of samples of UL RQ=5 and receive level between 31 and 40 ..........................................................................................................68-32 68.37 C901620036 Number of samples of UL RQ=5 and receive level between 41 and 63 ..........................................................................................................68-33 68.38 C901620037 Number of samples of UL RQ=6 and receive level between 0 and 10 ..........................................................................................................68-34 68.39 C901620038 Number of samples of UL RQ=6 and receive level between 11 and 15 ..........................................................................................................68-35 68.40 C901620039 Number of samples of UL RQ=6 and receive level between 16 and 20 ..........................................................................................................68-35 68.41 C901620040 Number of samples of UL RQ=6 and receive level between 21 and 30 ..........................................................................................................68-36 68.42 C901620041 Number of samples of UL RQ=6 and receive level between 31 and 40 ..........................................................................................................68-37 68.43 C901620042 Number of samples of UL RQ=6 and receive level between 41 and 63 ..........................................................................................................68-38 68.44 C901620043 Number of samples of UL RQ=7 and receive level between 0 and 10 ..........................................................................................................68-39 68.45 C901620044 Number of samples of UL RQ=7 and receive level between 11 and 15 ..........................................................................................................68-39 68.46 C901620045 Number of samples of UL RQ=7 and receive level between 16 and 20 ..........................................................................................................68-40 68.47 C901620046 Number of samples of UL RQ=7 and receive level between 21 and 30 ..........................................................................................................68-41 68.48 C901620047 Number of samples of UL RQ=7 and receive level between 31 and 40 ..........................................................................................................68-42 68.49 C901620048 Number of samples of UL RQ=7 and receive level between 41 and 63 ..........................................................................................................68-43 68.50 C901620049 Number of samples of DL RQ=0 and receive level between 0 and 10 ..........................................................................................................68-43 68.51 C901620050 Number of samples of DL RQ=0 and receive level between 11 and 15 ..........................................................................................................68-44 68.52 C901620051 Number of samples of DL RQ=0 and receive level between 16 and 20 ..........................................................................................................68-45 68.53 C901620052 Number of samples of DL RQ=0 and receive level between 21 and 30 ..........................................................................................................68-46 68.54 C901620053 Number of samples of DL RQ=0 and receive level between 31 and 40 ..........................................................................................................68-47 68.55 C901620054 Number of samples of DL RQ=0 and receive level between 41 and 63 ..........................................................................................................68-47

CXLI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

68.56 C901620055 Number of samples of DL RQ=1 and receive level between 0 and 10 ..........................................................................................................68-48 68.57 C901620056 Number of samples of DL RQ=1 and receive level between 11 and 15 ..........................................................................................................68-49 68.58 C901620057 Number of samples of DL RQ=1 and receive level between 16 and 20 ..........................................................................................................68-50 68.59 C901620058 Number of samples of DL RQ=1 and receive level between 21 and 30 ..........................................................................................................68-51 68.60 C901620059 Number of samples of DL RQ=1 and receive level between 31 and 40 ..........................................................................................................68-51 68.61 C901620060 Number of samples of DL RQ=1 and receive level between 41 and 63 ..........................................................................................................68-52 68.62 C901620061 Number of samples of DL RQ=2 and receive level between 0 and 10 ..........................................................................................................68-53 68.63 C901620062 Number of samples of DL RQ=2 and receive level between 11 and 15 ..........................................................................................................68-54 68.64 C901620063 Number of samples of DL RQ=2 and receive level between 16 and 20 ..........................................................................................................68-55 68.65 C901620064 Number of samples of DL RQ=2 and receive level between 21 and 30 ..........................................................................................................68-55 68.66 C901620065 Number of samples of DL RQ=2 and receive level between 31 and 40 ..........................................................................................................68-56 68.67 C901620066 Number of samples of DL RQ=2 and receive level between 41 and 63 ..........................................................................................................68-57 68.68 C901620067 Number of samples of DL RQ=3 and receive level between 0 and 10 ..........................................................................................................68-58 68.69 C901620068 Number of samples of DL RQ=3 and receive level between 11 and 15 ..........................................................................................................68-59 68.70 C901620069 Number of samples of DL RQ=3 and receive level between 16 and 20 ..........................................................................................................68-59 68.71 C901620070 Number of samples of DL RQ=3 and receive level between 21 and 30 ..........................................................................................................68-60 68.72 C901620071 Number of samples of DL RQ=3 and receive level between 31 and 40 ..........................................................................................................68-61 68.73 C901620072 Number of samples of DL RQ=3 and receive level between 41 and 63 ..........................................................................................................68-62 68.74 C901620073 Number of samples of DL RQ=4 and receive level between 0 and 10 ..........................................................................................................68-63 68.75 C901620074 Number of samples of DL RQ=4 and receive level between 11 and 15 ..........................................................................................................68-63

CXLII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

68.76 C901620075 Number of samples of DL RQ=4 and receive level between 16 and 20 ..........................................................................................................68-64 68.77 C901620076 Number of samples of DL RQ=4 and receive level between 21 and 30 ..........................................................................................................68-65 68.78 C901620077 Number of samples of DL RQ=4 and receive level between 31 and 40 ..........................................................................................................68-66 68.79 C901620078 Number of samples of DL RQ=4 and receive level between 41 and 63 ..........................................................................................................68-67 68.80 C901620079 Number of samples of DL RQ=5 and receive level between 0 and 10 ..........................................................................................................68-67 68.81 C901620080 Number of samples of DL RQ=5 and receive level between 11 and 15 ..........................................................................................................68-68 68.82 C901620081 Number of samples of DL RQ=5 and receive level between 16 and 20 ..........................................................................................................68-69 68.83 C901620082 Number of samples of DL RQ=5 and receive level between 21 and 30 ..........................................................................................................68-70 68.84 C901620083 Number of samples of DL RQ=5 and receive level between 31 and 40 ..........................................................................................................68-71 68.85 C901620084 Number of samples of DL RQ=5 and receive level between 41 and 63 ..........................................................................................................68-71 68.86 C901620085 Number of samples of DL RQ=6 and receive level between 0 and 10 ..........................................................................................................68-72 68.87 C901620086 Number of samples of DL RQ=6 and receive level between 11 and 15 ..........................................................................................................68-73 68.88 C901620087 Number of samples of DL RQ=6 and receive level between 16 and 20 ..........................................................................................................68-74 68.89 C901620088 Number of samples of DL RQ=6 and receive level between 21 and 30 ..........................................................................................................68-75 68.90 C901620089 Number of samples of DL RQ=6 and receive level between 31 and 40 ..........................................................................................................68-75 68.91 C901620090 Number of samples of DL RQ=6 and receive level between 41 and 63 ..........................................................................................................68-76 68.92 C901620091 Number of samples of DL RQ=7 and receive level between 0 and 10 ..........................................................................................................68-77 68.93 C901620092 Number of samples of DL RQ=7 and receive level between 11 and 15 ..........................................................................................................68-78 68.94 C901620093 Number of samples of DL RQ=7 and receive level between 16 and 20 ..........................................................................................................68-79 68.95 C901620094 Number of samples of DL RQ=7 and receive level between 21 and 30 ..........................................................................................................68-79

CXLIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

68.96 C901620095 Number of samples of DL RQ=7 and receive level between 31 and 40 ..........................................................................................................68-80 68.97 C901620096 Number of samples of DL RQ=7 and receive level between 41 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 x 9............................................ 70-3 70.5 C901640004 Average length of PCH queue: 9*64 ............................................ 70-3 70.6 C901640005 The percentage of PCH Blocks validly used ................................. 70-4 70.7 C901640006 Number of paging messages seized by other hyper-priority messages while transmitting on PCH blocks..................................................... 70-4 70.8 C901640007 Number of paging messages retransmitted zero times .................. 70-5 70.9 C901640008 Number of paging messages retransmitted one times ................... 70-5 70.10 C901640009 Number of paging messages retransmitted two times ................. 70-5 70.11 C901640010 Number of paging messages retransmitted three times ............... 70-6 70.12 C901640011 Numbers of paging messages retransmitted four times ............... 70-6 70.13 C901640012 Number of ImmAss message retransmitted zero time ................. 70-7 70.14 C901640013 Number of ImmAss message retransmitted one time .................. 70-7 70.15 C901640014 Number of discarded Packet Channel Request........................... 70-7 70.16 C901640015 Number of discarded channel requests that are suspected as HO ACC ........................................................................................................ 70-8 70.17 C901640016 Number of channel requests discarded due to BP board load ...... 70-9 70.18 C901640017 Number of CS Paging MS ........................................................70-10 70.19 C901640018 Number of PS Paging MS ........................................................70-10
CXLIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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

Chapter 72 Terminal Ability Statistic ...................................................... 72-1

72.1 Terminal Ability Statistics................................................................................. 72-3 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-4 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 72.11 C901660010 Number of mobile support extend DTM GPRS multi TS ability 9................................................................................................................... 72-11 72.12 C901660011 Number of mobile support extend DTM GPRS multi TS ability 10.................................................................................................................72-12 72.13 C901660012 Number of mobile support extend DTM GPRS multi TS ability 11 .................................................................................................................72-13 72.14 C901660013 Number of mobile support extend DTM EGPRS multi TS ability 5...................................................................................................................72-14 72.15 C901660014 Number of mobile support extend DTM EGPRS multi TS ability 6...................................................................................................................72-15 72.16 C901660015 Number of mobile support extend DTM EGPRS multi TS ability 9...................................................................................................................72-16 72.17 C901660016 Number of mobile support extend DTM EGPRS multi TS ability 10.................................................................................................................72-17 72.18 C901660017 Number of mobile support extend DTM EGPRS multi TS ability 11 .................................................................................................................72-18 72.19 C901660018 Number of mobile of GPRS multi TS ability 1.............................72-19 72.20 C901660019 Number of mobile of GPRS multi TS ability 2.............................72-21 72.21 C901660020 Number of mobile of GPRS multi TS ability 3.............................72-22
CXLV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

72.22 C901660021 Number of mobile of GPRS multi TS ability 4.............................72-24 72.23 C901660022 Number of mobile of GPRS multi TS ability 5.............................72-25 72.24 C901660023 Number of mobile of GPRS multi TS ability 6.............................72-27 72.25 C901660024 Number of mobile of GPRS multi TS ability 7.............................72-28 72.26 C901660025 Number of mobile of GPRS multi TS ability 8.............................72-30 72.27 C901660026 Number of mobile of GPRS multi TS ability 9.............................72-31 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 72.30 C901660029 Number of mobile of GPRS multi TS ability 12...........................72-36 72.31 C901660030 Number of mobile of GPRS multi TS ability 30...........................72-37 72.32 C901660031 Number of mobile of GPRS multi TS ability 31...........................72-39 72.33 C901660032 Number of mobile of GPRS multi TS ability 32...........................72-40 72.34 C901660033 Number of mobile of GPRS multi TS ability 33...........................72-42 72.35 C901660034 Number of mobile of GPRS multi TS ability 34...........................72-43 72.36 C901660035 Number of mobile of EGPRS multi TS ability 1 ..........................72-45 72.37 C901660036 Number of mobile of EGPRS multi TS ability 2 ..........................72-46 72.38 C901660037 Number of mobile of EGPRS multi TS ability 3 ..........................72-48 72.39 C901660038 Number of mobile of EGPRS multi TS ability 4 ..........................72-49 72.40 C901660039 Number of mobile of EGPRS multi TS ability 5 ..........................72-51 72.41 C901660040 Number of mobile of EGPRS multi TS ability 6 ..........................72-52 72.42 C901660041 Number of mobile of EGPRS multi TS ability 7 ..........................72-54 72.43 C901660042 Number of mobile of EGPRS multi TS ability 8 ..........................72-55 72.44 C901660043 Number of mobile of EGPRS multi TS ability 9 ..........................72-57 72.45 C901660044 Number of mobile of EGPRS multi TS ability 10.........................72-58 72.46 C901660045 Number of mobile of EGPRS multi TS ability 11.........................72-60 72.47 C901660046 Number of mobile of EGPRS multi TS ability 12.........................72-61 72.48 C901660047 Number of mobile of EGPRS multi TS ability 30.........................72-63 72.49 C901660048 Number of mobile of EGPRS multi TS ability 31.........................72-64 72.50 C901660049 Number of mobile of EGPRS multi TS ability 32.........................72-66 72.51 C901660050 Number of mobile of EGPRS multi TS ability 33.........................72-67 72.52 C901660051 Number of mobile of EGPRS multi TS ability 34.........................72-69 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

CXLVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 72.67 C901660066 Number of sampling received radio access ability ......................72-84 72.68 C901660067 Number of MS Supporting Downlink EGPRS2-A........................72-85 72.69 C901660068 Number of MS Supporting Uplink EGPRS2-A ............................72-86 72.70 C901660069 Num of MS supporting PS handover .........................................72-87 72.71 C901660070 The Number of MS which Support SAIC ...................................72-88 72.72 C901660071 The Number of MS which not Support SAIC ..............................72-89 72.73 C901660072 Num of MS Supporting DLDC...................................................72-90 72.74 C901660073 Num of DTM MS Supporting DLDC...........................................72-90 72.75 C901660074 Num of MS Supporting RTTI ....................................................72-91 72.76 C901660075 Num of MS Supporting MSRD ..................................................72-91 72.77 C901660076 The Number of MS which Support DARP2 ................................72-92 72.78 C901660077 The Number of MS which Support VAMOS1..............................72-93 72.79 C901660078 The Number of MS which Support VAMOS2..............................72-94

Chapter 73 MTP3 Signaling Link Statistics............................................ 73-1

73.1 Overview ....................................................................................................... 73-2 73.2 C901670001 Duration of Signaling Link Out of Service ..................................... 73-3 73.3 C901670002 Number of Signaling Link Out of Service ...................................... 73-3 73.4 C901670003 Number of Message Signal Unit Sent .......................................... 73-3 73.5 C901670004 Octets of SIF-SIO Sent ............................................................... 73-4 73.6 C901670005 Number of Message Signal Unit Received ................................... 73-4 73.7 C901670006 Octets of SIF-SIO Received ........................................................ 73-4 73.8 C901670007 Peak Traffic of Signaling Link ...................................................... 73-4 73.9 C901670008 Peak Traffic Duration of Signaling Link......................................... 73-5 73.10 C901670009 Number of Change Over on OMP .............................................. 73-6 73.11 C901670010 Number of TFP Received .......................................................... 73-6 73.12 C901670011 Ten thousand rate of Mtp3 Link Occupy...................................... 73-6 73.13 C901670012 Number of SCCP Message Signal Unit Received ....................... 73-7 73.14 C901670013 Number of SCCP Message Signal Unit Sent .............................. 73-7

CXLVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

73.15 C901670014 Number of A2SP Message Signal Unit Received ........................ 73-8 73.16 C901670015 Number of A2SP Message Signal Unit Sent ............................... 73-8 73.17 C901670016 Number of Stm Message Signal Unit Received........................... 73-8 73.18 C901670017 Number of Stm Message Signal Unit Sent.................................. 73-8 73.19 C901670018 Number of Sltm Message Signal Unit Received .......................... 73-9 73.20 C901670019 Number of Sltm Message Signal Unit Sent ................................. 73-9 73.21 C901670020 Octets of SCCP SIF-SIO Received ............................................ 73-9 73.22 C901670021 Octets of SCCP SIF-SIO Sent ................................................... 73-9 73.23 C901670022 Octets of MTP2 SIF-SIO Received ...........................................73-10 73.24 C901670023 Octets of MTP2 SIF-SIO Sent ..................................................73-10 73.25 C901670024 Octets of Stm SIF-SIO Received ..............................................73-10 73.26 C901670025 Octets of Stm SIF-SIO Sent .....................................................73-10 73.27 C901670026 Octets of Sltm SIF-SIO Received.............................................. 73-11 73.28 C901670027 Octets of Sltm SIF-SIO Sent..................................................... 73-11 73.29 C901670028 Number of message discarded due to Congestion ..................... 73-11 73.30 C901670029 Number of restrictions Level 1 .................................................. 73-11 73.31 C901670030 Number of restrictions Level 2 ..................................................73-12 73.32 C901670031 Number of restrictions Level 3 ..................................................73-12 73.33 C901670032 Duration of Restrictions Level 1 ................................................73-12 73.34 C901670033 Duration of Restrictions Level 2 ................................................73-13 73.35 C901670034 Duration of Restrictions Level 3 ................................................73-13 73.36 C901670035 Duration of manual prohibition ..................................................73-13 73.37 C901670036 Number of local automatic change back ....................................73-14 73.38 C901670037 Number of SL restoration .........................................................73-14 73.39 C901670038 Number of Local management inhibit ........................................73-14 73.40 C901670039 Duration of SL inhibition due to Local management actions ........73-15 73.41 C901670040 Number of remote management inhibit......................................73-15 73.42 C901670041 Duration of SL inhibition due to remote management actions ......73-15 73.43 C901670042 Number of remote processor outage .........................................73-16 73.44 C901670043 Duration of SL inhibition due to remote processor outage ...........73-16 73.45 C901670044 Number of sending unaccess messages ...................................73-16 73.46 C901670045 Number of sending flow-control discarded messages.................73-17 73.47 C901670046 Ten thousand multiple bandwidth occupancy rate on outgoing signaling link .................................................................................................73-17 73.48 C901670047 Ten thousand multiple bandwidth occupancy rate on incoming signaling link ................................................................................................73-18 73.49 C901670048 Link type .................................................................................73-18 73.50 C901670049 Number of TFA sent.................................................................73-19
CXLVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

73.51 C901670050 Number of TFA received ..........................................................73-19 73.52 C901670051 Number of TFC sent ................................................................73-19 73.53 C901670052 Number of TFC received ..........................................................73-19 73.54 C901670053 Number of RST sent ................................................................73-19 73.55 C901670054 Number of RST received..........................................................73-20 73.56 C901670055 Number of TRA sent ................................................................73-20 73.57 C901670056 Number of TRA received..........................................................73-20 73.58 C901670057 Number of UPU sent................................................................73-20 73.59 C901670058 Number of UPU received .........................................................73-21 73.60 C901670059 Number of message discard controlled by license......................73-21

Chapter 74 M3UA Performance Statistics.............................................. 74-1

74.1 Overview ....................................................................................................... 74-2 74.2 C901680001 Number of data message sent..................................................... 74-2 74.3 C901680002 Number of data message received .............................................. 74-2 74.4 C901680003 Number of ASP Up message sent ............................................... 74-3 74.5 C901680004 Number of ASP Up message received ......................................... 74-3 74.6 C901680005 Number of ASP Up Ack message received .................................. 74-3 74.7 C901680006 Number of ASP Up Ack message sent......................................... 74-4 74.8 C901680007 Number of ASP Down message sent ........................................... 74-4 74.9 C901680008 Number of ASP Down message received..................................... 74-4 74.10 C901680009 Number of ASP Down Ack message received ............................ 74-5 74.11 C901680010 Number of ASP Down Ack message sent ................................... 74-5 74.12 C901680011 Number of ASP Inactive message sent ...................................... 74-5 74.13 C901680012 Number of ASP Inactive message received ................................ 74-6 74.14 C901680013 Number of ASP Inactive Ack message received ......................... 74-6 74.15 C901680014 Number of ASP Inactive Ack message sent................................ 74-6 74.16 C901680015 Number of ASP Active message sent......................................... 74-7 74.17 C901680016 Number of ASP Active message received .................................. 74-7 74.18 C901680017 Number of ASP Active Ack message received............................ 74-7 74.19 C901680018 Number of ASP Active Ack message sent .................................. 74-8 74.20 C901680019 Number of DAUD message sent................................................ 74-8 74.21 C901680020 Number of SCON message received ......................................... 74-8 74.22 C901680021 Number of DAVA message received .......................................... 74-9 74.23 C901680022 Number of DUNA message received.......................................... 74-9 74.24 C901680023 Number of invalid message received ......................................... 74-9 74.25 C901680024 Number of MGMT message sent ............................................... 74-9 74.26 C901680025 Number of MGMT message received........................................74-10

CXLIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

74.27 C901680026 Number of Heartbeat message received ...................................74-10 74.28 C901680027 Number of HeartBeat Ack message sent...................................74-10 74.29 C901680028 Bytes of data message received ............................................... 74-11 74.30 C901680029 Bytes of data message transmitted ........................................... 74-11 74.31 C901680030 Bytes of MGMT message sent.................................................. 74-11 74.32 C901680031 Bytes of MGMT message received ........................................... 74-11 74.33 C901680032 Counts of discarding messages by Flow Control........................74-12 74.34 C901680033 Number of message discard controlled by license......................74-12 74.35 C901680034 Bytes of all message sent ........................................................74-12 74.36 C901680035 Bytes of all message received ..................................................74-13 74.37 C901680036 Number of ERROR message sent ............................................74-13 74.38 C901680037 Number of ERROR message received ......................................74-13 74.39 C901680038 Number of NOTIFY message sent ............................................74-14 74.40 C901680039 Number of NOTIFY message received......................................74-14

Chapter 75 SCCP Performance Statistics .............................................. 75-1

75.1 Overview ....................................................................................................... 75-2 75.2 C901690001 Number of UDT Sent .................................................................. 75-2 75.3 C901690002 Number of UDT Received ........................................................... 75-3 75.4 C901690003 Number of UDTS Sent ................................................................ 75-3 75.5 C901690004 Number of UDTS Received ......................................................... 75-3 75.6 C901690005 Number of ERR Sent .................................................................. 75-4 75.7 C901690006 Number of ERR Received ........................................................... 75-4 75.8 C901690007 Number of SSP Sent .................................................................. 75-4 75.9 C901690008 Number of SSP Received ........................................................... 75-4 75.10 C901690009 Number of RSR Sent ................................................................ 75-4 75.11 C901690010 Number of RSR Received ......................................................... 75-5 75.12 C901690011 Number of RSC Sent ................................................................ 75-5 75.13 C901690012 Number of RSC Received ......................................................... 75-5 75.14 C901690013 Number of UnAnswered SST .................................................... 75-5 75.15 C901690014 Number of CREF Sent .............................................................. 75-6 75.16 C901690015 Number of CREF Received ....................................................... 75-6 75.17 C901690016 Number of XUDT Sent .............................................................. 75-6 75.18 C901690017 Number of XUDT Received ....................................................... 75-6 75.19 C901690018 Number of XUDTS Sent ............................................................ 75-6 75.20 C901690019 Number of XUDTS Received..................................................... 75-7 75.21 C901690020 Number of LUDT Sent .............................................................. 75-7 75.22 C901690021 Number of LUDT Received ....................................................... 75-7

CL SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

75.23 C901690022 Number of LUDTS Sent ............................................................ 75-7 75.24 C901690023 Number of LUDTS Received ..................................................... 75-8 75.25 C901690024 Number of DT1 Received.......................................................... 75-8 75.26 C901690025 Number of DT1 Sent ................................................................. 75-8 75.27 C901690026 Number of DT2 Received.......................................................... 75-8 75.28 C901690027 Number of DT2 Sent ................................................................. 75-8 75.29 C901690028 Number of CONNECTREQ Sent ............................................... 75-9 75.30 C901690029 Number of CONNECTCON Received ........................................ 75-9 75.31 C901690030 Number of CONNECTIND Received .......................................... 75-9 75.32 C901690031 Number of CONNECTRES Sent................................................ 75-9 75.33 C901690032 Number of DISCONNECTREQ Sent .........................................75-10 75.34 C901690033 Number of DISCONNECTIND received.....................................75-10 75.35 C901690034 Number of CR Sent .................................................................75-10 75.36 C901690035 Number of CR Received ..........................................................75-10 75.37 C901690036 Number of CC Sent .................................................................75-10 75.38 C901690037 Number of CC Received .......................................................... 75-11 75.39 C901690038 Number of UDT gtt .................................................................. 75-11 75.40 C901690039 Number of UDTS gtt ................................................................ 75-11 75.41 C901690040 Number of XUDT gtt ................................................................ 75-11 75.42 C901690041 Number of XUDTS gtt ..............................................................75-12 75.43 C901690042 Number of LUDT gtt.................................................................75-12 75.44 C901690043 Number of LUDTS gtt ..............................................................75-12 75.45 C901690044 Number of UDT gtt failure ........................................................75-12 75.46 C901690045 Number of UDTS gtt failure ......................................................75-13 75.47 C901690046 Number of XUDT gtt failure ......................................................75-13 75.48 C901690047 Number of XUDTS gtt failure ....................................................75-13 75.49 C901690048 Number of LUDT gtt failure.......................................................75-13 75.50 C901690049 Number of LUDTS gtt failure ....................................................75-14 75.51 C901690050 Number of CR gtt ....................................................................75-14 75.52 C901690051 Number of CR gtt failure ..........................................................75-14 75.53 C901690052 Number of gtt Count ................................................................75-15 75.54 C901690053 Number of gtt failure ................................................................75-15 75.55 C901690054 Number of N_UnitDataReq LongUserData gtt failure..................75-15 75.56 C901690055 Number of UPU received .........................................................75-15 75.57 C901690056 Number of SSA received..........................................................75-16 75.58 C901690057 Number of SSA sent ................................................................75-16 75.59 C901690058 Number of SST received ..........................................................75-16

CLI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

75.60 C901690059 Number of SST sent ................................................................75-16

Chapter 76 MTP3 Signaling Link Set Statistics ..................................... 76-1

76.1 Overview ....................................................................................................... 76-1 76.2 C901700001 Times of Signaling Link Set Out of Service ................................... 76-1 76.3 C901700002 Duration of Signaling Link Set Out of Service ............................... 76-2 76.4 C901700003 Number of Available Signaling Link.............................................. 76-2 76.5 C901700004 Linkset type ............................................................................... 76-2

Chapter 77 M3UA Error Statistics ........................................................... 77-1

77.1 Overview ....................................................................................................... 77-2 77.2 C901710001 Invalid Version(T) ....................................................................... 77-2 77.3 C901710002 Unsupported Message Class(T) .................................................. 77-2 77.4 C901710003 Unsupported Message Type(T) ................................................... 77-3 77.5 C901710004 Unexpected Message(T)............................................................. 77-3 77.6 C901710005 Unsupported Traffic Mode Type(T) .............................................. 77-3 77.7 C901710006 Invalid Routing Context(T)........................................................... 77-3 77.8 C901710007 Protocol Error(T) ........................................................................ 77-4 77.9 C901710008 Invalid Message Type(T)............................................................. 77-4 77.10 C901710009 Number of error message sent .................................................. 77-4 77.11 C901710010 Invalid Version(R) ..................................................................... 77-4 77.12 C901710011 Unsupported Message Class(R) ................................................ 77-5 77.13 C901710012 Unsupported Message Type(R) ................................................. 77-5 77.14 C901710013 Unexpected Message(R)........................................................... 77-5 77.15 C901710014 Unsupported Traffic Mode Type(R) ............................................ 77-5 77.16 C901710015 Invalid Routing Context(R) ........................................................ 77-6 77.17 C901710016 Protocol Error(R) ...................................................................... 77-6 77.18 C901710017 Invalid Message Type(R)........................................................... 77-6 77.19 C901710018 Number of error message received ............................................ 77-6 77.20 C901710019 Unknown Remote User ............................................................. 77-7 77.21 C901710020 Unequipped Remote User ......................................................... 77-7 77.22 C901710021 Inaccessible Remote User......................................................... 77-7 77.23 C901710022 Number of DUPU message received.......................................... 77-8 77.24 C901710023 Invalid Net APPEARANCE(T).................................................... 77-8 77.25 C901710024 Invalid Net APPEARANCE(R) ................................................... 77-8 77.26 C901710025 Number of DUPU message sent which cause is unknown ........... 77-8 77.27 C901710026 Number of DUPU message sent which cause is Unequipped Remote User.................................................................................................. 77-9

CLII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

77.28 C901710027 Number of DUPU message sent which cause is Inaccessible Remote User.................................................................................................. 77-9 77.29 C901710028 Number of DUPU message sent................................................ 77-9 77.30 C901710029 Number of message discard controlled by license......................77-10 77.31 C901710030 Sending invalid stream ID ........................................................77-10 77.32 C901710031 Sending refuse error, reason is management blocking ...............77-10 77.33 C901710032 Sending required ASP ID ......................................................... 77-11 77.34 C901710033 Sending invalid ASP ID ............................................................ 77-11 77.35 C901710034 Sending invalid parameter value............................................... 77-11 77.36 C901710035 Sending parameter field error ................................................... 77-11 77.37 C901710036 Sending unexpected parameter error ........................................77-12 77.38 C901710037 Sending destination status unknown .........................................77-12 77.39 C901710038 Sending missing parameter error ..............................................77-12 77.40 C901710039 Sending no configured AS for ASP ...........................................77-13 77.41 C901710040 Receiving invalid stream ID ......................................................77-13 77.42 C901710041 Receiving refuse error, reason is management blocking .............77-13 77.43 C901710042 Receiving required ASP ID.......................................................77-13 77.44 C901710043 Receiving invalid ASP ID..........................................................77-14 77.45 C901710044 Receiving invalid parameter value ............................................77-14 77.46 C901710045 Receiving parameter field error.................................................77-14 77.47 C901710046 Receiving unexpected parameter error......................................77-15 77.48 C901710047 Receiving destination status unknown.......................................77-15 77.49 C901710048 Receiving missing parameter error ...........................................77-15 77.50 C901710049 Receiving no configured AS for ASP .........................................77-15

Chapter 78 M3UA AS Performance Statistics........................................ 78-1

78.1 Overview ....................................................................................................... 78-1 78.2 C901720001 Number of service message transmitted ...................................... 78-1 78.3 C901720002 Bytes of service message transmitted .......................................... 78-2 78.4 C901720003 Number of service message received .......................................... 78-2 78.5 C901720004 Bytes of service message received.............................................. 78-2

Chapter 79 Timer Statistics ..................................................................... 79-1

79.1 Overview ....................................................................................................... 79-1 79.2 C901730001 Number of all timers ................................................................... 79-1 79.3 C901730002 Number of available timer ........................................................... 79-2 79.4 C901730003 Peak value of timer..................................................................... 79-2 79.5 C901730004 Number of success to set timer ................................................... 79-2 79.6 C901730005 Number of failure to set timer ...................................................... 79-2
CLIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 80 Scheduling Performance Statistics..................................... 80-1

80.1 Overview ....................................................................................................... 80-1 80.2 C901740001 Number of active process ........................................................... 80-1 80.3 C901740002 Number of process ..................................................................... 80-2 80.4 C901740003 Number of process scheduled ..................................................... 80-2

Chapter 81 UB Memory Performance Statistics .................................... 81-1

81.1 Overview ....................................................................................................... 81-1 81.2 C901750001 ID of UB Set............................................................................... 81-1 81.3 C901750002 Size of UB.................................................................................. 81-2 81.4 C901750003 Number of UB ............................................................................ 81-2 81.5 C901750004 Number of UB used .................................................................... 81-2

Chapter 82 Hard Disk and FLASH Performance Statistics................... 82-1

82.1 Overview ....................................................................................................... 82-1 82.2 C901760001 Disk Device ID ........................................................................... 82-1 82.3 C901760002 Total space ................................................................................ 82-1 82.4 C901760003 Free space................................................................................. 82-2

Chapter 83 SCTP Protocol Statistics...................................................... 83-1

83.1 Overview ....................................................................................................... 83-2 83.2 C901770001 Number of Association Accepted ................................................. 83-2 83.3 C901770002 Number of Association Initiated ................................................... 83-2 83.4 C901770003 Number of Association Shutdown ................................................ 83-2 83.5 C901770004 Number of Association Abort....................................................... 83-3 83.6 C901770005 Number of Chunk Retransmitted ................................................. 83-3 83.7 C901770006 Number of Unordered Chunk Sent............................................... 83-3 83.8 C901770007 Number of Unordered Chunk Received........................................ 83-3 83.9 C901770008 Number of Chunk Sent ............................................................... 83-4 83.10 C901770009 Number of Chunk Received ...................................................... 83-4 83.11 C901770010 Number of Init Sent ................................................................... 83-4 83.12 C901770011 Number of Init Received ............................................................ 83-4 83.13 C901770012 Number of Init Ack Sent ............................................................ 83-4 83.14 C901770013 Number of Init Ack Received ..................................................... 83-5 83.15 C901770014 Number of COOKIE Sent .......................................................... 83-5 83.16 C901770015 Number of Cookie Received...................................................... 83-5 83.17 C901770016 Number of Cookie Ack Sent ...................................................... 83-5 83.18 C901770017 Number of Cookie Ack Received ............................................... 83-6 83.19 C901770018 Number of Heartbeat Sent ........................................................ 83-6 83.20 C901770019 Number of Heartbeat Received ................................................. 83-6
CLIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

83.21 C901770020 Number of Heartbeat Ack Sent .................................................. 83-6 83.22 C901770021 Number of Heartbeat Ack Received ........................................... 83-6 83.23 C901770022 Number of Abort Chunk Sent..................................................... 83-7 83.24 C901770023 Number of Abort Chunk Received.............................................. 83-7 83.25 C901770024 Number of Shutdown Chunk Sent.............................................. 83-7 83.26 C901770025 Number of Shutdown Chunk Received....................................... 83-7 83.27 C901770026 Number of Shutdown Ack Chunk Sent ....................................... 83-8 83.28 C901770027 Number of Shutdown Ack Chunk Received ................................ 83-8 83.29 C901770028 Number of Shutdown Complete Sent ......................................... 83-8 83.30 C901770029 Number of Shutdown Complete Received .................................. 83-8 83.31 C901770030 Number of Error Chunk Sent ..................................................... 83-9 83.32 C901770031 Number of Error Chunk Received .............................................. 83-9 83.33 C901770032 Number of ECNE Chunk Sent ................................................... 83-9 83.34 C901770033 Number of ECNE Chunk Received ............................................ 83-9 83.35 C901770034 Number of CWR Chunk Sent....................................................83-10 83.36 C901770035 Number of CWR Chunk Received.............................................83-10 83.37 C901770036 Number of Error Packet Received.............................................83-10 83.38 C901770037 Number of OOTB Chunk Received ...........................................83-10 83.39 C901770038 Number of ULP Sent Chunk Request in association alive ........... 83-11 83.40 C901770039 Number of ULP Sent Chunk Request to SCTP OK in association alive.............................................................................................................. 83-11 83.41 C901770040 Number of ULP Sent Chunk Request during a little time............. 83-11 83.42 C901770041 Number of ULP Sent Chunk Request to SCTP OK during a little time .............................................................................................................. 83-11 83.43 C901770042 Number of SCTP Sent Chunk Request to ULP ..........................83-12 83.44 C901770043 Number of Abort Request from ULP..........................................83-12 83.45 C901770044 Number of Received Abort From Peer ......................................83-12 83.46 C901770045 Number of Link Break for Retransfer .........................................83-12

Chapter 84 SCTP Association Statistics ................................................ 84-1

84.1 Overview ....................................................................................................... 84-1 84.2 C901780001 State of association .................................................................... 84-1 84.3 C901780002 Send synchronous Msg to ULP fail .............................................. 84-2 84.4 C901780003 ULPID from ULP invalid .............................................................. 84-2 84.5 C901780004 Number of Association Initiated to ULP ........................................ 84-2 84.6 C901780005 Number of Association Accepted to ULP...................................... 84-2 84.7 C901780006 Number of Association Restarted to ULP ..................................... 84-3 84.8 C901780007 Number of Association lost to ULP .............................................. 84-3 84.9 C901780008 Number of Destroy instance ........................................................ 84-3
CLV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

84.10 C901780009 Number of Shutdown request from ULP ..................................... 84-3 84.11 C901780010 Number of Abort request from ULP ............................................ 84-4

Chapter 85 SDTB Fiber Performance Statistics .................................... 85-1

85.1 Overview ....................................................................................................... 85-2 85.2 C901790001 slot number (no description) ........................................................ 85-3 85.3 C901790002 master/slave state (no description) .............................................. 85-3 85.4 C901790003 SDH Type .................................................................................. 85-3 85.5 C901790004 Regenerator Section BIP-8 Error ................................................. 85-3 85.6 C901790005 Multiplex Section BIP-24 Error..................................................... 85-3 85.7 C901790006 VC-4 BIP-8 Error (High-order path 1) ........................................... 85-4 85.8 C901790007 VC-4 BIP-8 Error (High-order path 2) ........................................... 85-4 85.9 C901790008 VC-4 BIP-8 Error (High-order path 3) ........................................... 85-4 85.10 C901790009 Multiplex Section Remote Error Indication .................................. 85-5 85.11 C901790010 VC-4 Remote Error Indication (High-order path 1) ....................... 85-5 85.12 C901790011 VC-4 Remote Error Indication (High-order path 2) ....................... 85-5 85.13 C901790012 VC-4 Remote Error Indication (High-order path 3)....................... 85-6 85.14 C901790013 Multiplex Section Remote Background Block Error Ratio............. 85-6 85.15 C901790014 Multiplex Section Remote Errored Second Ratio......................... 85-6 85.16 C901790015 Multiplex Section Remote Errored Second ................................. 85-7 85.17 C901790016 Multiplex Section Remote Severely Errored Second ................... 85-7 85.18 C901790017 Multiplex Section Remote Unavailable Second ........................... 85-8 85.19 C901790018 VC-4 Remote Background Block Error Ratio (High-order path 1) .................................................................................................................. 85-8 85.20 C901790019 VC-4 Remote Background Block Error Ratio (High-order path 2) .................................................................................................................. 85-9 85.21 C901790020 VC-4 Remote Background Block Error Ratio (High-order path 3) .................................................................................................................. 85-9 85.22 C901790021 VC-4 Remote Errored Second Ratio (High-order path 1) ............. 85-9 85.23 C901790022 VC-4 Remote Errored Second Ratio (High-order path 2) ............85-10 85.24 C901790023 VC-4 Remote Errored Second Ratio (High-order path 3) ............85-10 85.25 C901790024 VC-4 Remote Errored Second (High-order path 1) .....................85-10 85.26 C901790025 VC-4 Remote Errored Second (High-order path 2) ..................... 85-11 85.27 C901790026 VC-4 Remote Errored Second (High-order path 3) ..................... 85-11 85.28 C901790027 VC-4 Remote Severely Errored Second (High-order path 1) ....... 85-11 85.29 C901790028 VC-4 Remote Severely Errored Second (High-order path 2) .......85-12 85.30 C901790029 VC-4 Remote Severely Errored Second (High-order path 3) .......85-12 85.31 C901790030 VC-4 Remote Unavailable Second (High-order path 1)...............85-12 85.32 C901790031 VC-4 Remote Unavailable Second (High-order path 2)...............85-13
CLVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

85.33 C901790032 VC-4 Remote Unavailable Second (High-order path 3)...............85-13 85.34 C901790033 B1(Regenerator Section) BIP-8 Background Block Error Ratio.............................................................................................................85-13 85.35 C901790034 B1(Regenerator Section) BIP-8 Errored Second Ratio ...............85-14 85.36 C901790035 B1(Regenerator Section) BIP-8 Errored Second ........................85-14 85.37 C901790036 B1(Regenerator Section) BIP-8 Severely Errored Second ..........85-14 85.38 C901790037 B1(Regenerator Section) BIP-8 Unavailable Second..................85-15 85.39 C901790038 B2(Multiplex Section) BIP-24 Background Block Error Ratio .......85-15 85.40 C901790039 B2(Multiplex Section) BIP-24 Errored Second Ratio...................85-16 85.41 C901790040 B2(Multiplex Section) BIP-24 Errored Second............................85-16 85.42 C901790041 B2(Multiplex Section) BIP-24 Severely Errored Second..............85-16 85.43 C901790042 B2(Multiplex Section) BIP-24 Unavailable Second .....................85-17 85.44 C901790043 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 1) .................................................................................................................85-17 85.45 C901790044 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 2) .................................................................................................................85-18 85.46 C901790045 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 3) .................................................................................................................85-18 85.47 C901790046 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 1) .........85-18 85.48 C901790047 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 2) .........85-19 85.49 C901790048 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 3) .........85-19 85.50 C901790049 B3(VC-4) BIP-8 Errored Second (High-order path 1) ..................85-19 85.51 C901790050 B3(VC-4) BIP-8 Errored Second (High-order path 2) ..................85-20 85.52 C901790051 B3(VC-4) BIP-8 Errored Second (High-order path 3) ..................85-20 85.53 C901790052 B3(VC-4) BIP-8 Severely Errored Second (High-order path 1) .................................................................................................................85-20 85.54 C901790053 B3(VC-4) BIP-8 Severely Errored Second (High-order path 2) .................................................................................................................85-21 85.55 C901790054 B3(VC-4) BIP-8 Severely Errored Second (High-order path 3) .................................................................................................................85-21 85.56 C901790055 B3(VC-4) BIP-8 Unavailable Second (High-order path 1)............85-21 85.57 C901790056 B3(VC-4) BIP-8 Unavailable Second (High-order path 2)............85-22 85.58 C901790057 B3(VC-4) BIP-8 Unavailable Second (High-order path 3)............85-22 85.59 C901790058 LOF second ............................................................................85-22

Chapter 86 PEB22554 E1 Performance Statistics ................................. 86-1

86.1 Overview ....................................................................................................... 86-1 86.2 C901800001 Frame type ................................................................................ 86-2 86.3 C901800002 slip Duration .............................................................................. 86-2

CLVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

86.4 C901800003 Near end available Second ......................................................... 86-2 86.5 C901800004 Near end unavailable Second...................................................... 86-3 86.6 C901800005 Near end Errored Second ........................................................... 86-3 86.7 C901800006 Near end Severely Errored Second ............................................. 86-3 86.8 C901800007 Near end Background Block Error ............................................... 86-4 86.9 C901800008 Frame Alignment Signal error...................................................... 86-4 86.10 C901800009 Cyclic Redundancy Check 4 error.............................................. 86-4 86.11 C901800010 Bit error rate(PPM).................................................................... 86-4 86.12 C901800011 Near end unavailable Second rate(One ten-thousandth).............. 86-5 86.13 C901800012 Near end Errored Second rate(One ten-thousandth) ................... 86-5 86.14 C901800013 Near end Severely Errored Second rate(One ten-thousandth) ..... 86-5 86.15 C901800014 Near end Background Block Error rate ....................................... 86-6 86.16 C901800015 far end available Second........................................................... 86-6 86.17 C901800016 far end unavailable Second ....................................................... 86-6 86.18 C901800017 far end Errored Second............................................................. 86-7 86.19 C901800018 far end Severely Errored Second ............................................... 86-7 86.20 C901800019 far end Background Block Error ................................................. 86-7 86.21 C901800020 E-Bit ERROR ........................................................................... 86-8 86.22 C901800021 far end unavailable Second rate(One ten-thousandth)................. 86-8 86.23 C901800022 far end Errored Second rate(One ten-thousandth) ...................... 86-8 86.24 C901800023 far end Severely Errored Second rate(One ten-thousandth)......... 86-9 86.25 C901800024 far end Background Block Error rate(One ten-thousandth)........... 86-9

Chapter 87 PEB22554 T1 Performance Statistics ................................. 87-1

87.1 Overview ....................................................................................................... 87-1 87.2 C901810001 Frame type ................................................................................ 87-2 87.3 C901810002 slip Duration .............................................................................. 87-2 87.4 C901810003 Near end available Second ......................................................... 87-2 87.5 C901810004 Near end unavailable Second...................................................... 87-2 87.6 C901810005 Near end Errored Second ........................................................... 87-3 87.7 C901810006 Near end Severely Errored Second ............................................ 87-3 87.8 C901810007 number of Near end Background Block Error ............................... 87-3 87.9 C901810008 number of Frame Alignment Signal error...................................... 87-4 87.10 C901810009 number of Cyclic Redundancy Check 6 error.............................. 87-4 87.11 C901810010 Bit error rate (PPM)................................................................... 87-4 87.12 C901810011 Near end unavailable Second rate(One ten-thousandth).............. 87-4 87.13 C901810012 Near end Errored Second rate (One ten-thousandth) .................. 87-5 87.14 C901810013 Near end Severely Errored Second rate(One ten-thousandth) ..... 87-5

CLVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

87.15 C901810014 Near end Background Block Error rate ....................................... 87-5

Chapter 88 MAC Port Flow Statistics ..................................................... 88-1

88.1 Overview ....................................................................................................... 88-1 88.2 C901820001 receive bytes number (high 4 bytes) ............................................ 88-1 88.3 C901820002 receive bytes number (low 4 bytes).............................................. 88-2 88.4 C901820003 transmit bytes number (high 4 bytes) ........................................... 88-2 88.5 C901820004 transmit bytes number (low 4 bytes) ............................................ 88-3 88.6 C901820005 physical band width .................................................................... 88-3 88.7 C901820006 mean receiving bit rate................................................................ 88-4 88.8 C901820007 max receiving bit rate.................................................................. 88-4 88.9 C901820008 mean transmitting bit rate............................................................ 88-4 88.10 C901820009 max transmitting bit rate ............................................................ 88-5 88.11 C901820010 Number of packets discarded at RX side (high 4 bytes) ............... 88-5 88.12 C901820011 Number of packets discarded at RX side (low 4 bytes) ................ 88-6 88.13 C901820012 Number of packets discarded at TX side (high 4 bytes) ............... 88-6 88.14 C901820013 Number of packets discarded at TX side (low 4 bytes) ................ 88-6 88.15 C901820014 Number of packets received when receiving bit rate is max during performance period .............................................................................. 88-7 88.16 C901820015 Number of packets sent when sending bit rate is max during performance period......................................................................................... 88-7

Chapter 89 AMR Rate Statistics .............................................................. 89-1

89.1 Overview ....................................................................................................... 89-2 89.2 C901830001 Total Num of DL AFS12.2k frame ................................................ 89-3 89.3 C901830002 Total Num of DL AFS10.2k frame ................................................ 89-4 89.4 C901830003 Total Num of DL AFS7.95k frame ................................................ 89-4 89.5 C901830004 Total Num of DL AFS7.40k frame ................................................ 89-5 89.6 C901830005 Total Num of DL AFS6.70k frame ................................................ 89-5 89.7 C901830006 Total Num of DL AFS5.90k frame ................................................ 89-6 89.8 C901830007 Total Num of DL AFS5.15k frame ................................................ 89-6 89.9 C901830008 Total Num of DL AFS4.75k frame ................................................ 89-7 89.10 C901830009 Total Num of DL AHS7.95k frame .............................................. 89-7 89.11 C901830010 Total Num of DL AHS7.40k frame .............................................. 89-8 89.12 C901830011 Total Num of DL AHS6.70k frame .............................................. 89-8 89.13 C901830012 Total Num of DL AHS5.90k frame .............................................. 89-9 89.14 C901830013 Total Num of DL AHS5.15k frame .............................................. 89-9 89.15 C901830014 Total Num of DL AHS4.75k frame .............................................89-10 89.16 C901830015 Total Num of UL AFS12.2k frame .............................................89-10

CLIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

89.17 C901830016 Total Num of UL AFS10.2k frame ............................................. 89-11 89.18 C901830017 Total Num of UL AFS7.95k frame ............................................. 89-11 89.19 C901830018 Total Num of UL AFS7.40k frame .............................................89-12 89.20 C901830019 Total Num of UL AFS6.70k frame .............................................89-12 89.21 C901830020 Total Num of UL AFS5.90k frame .............................................89-13 89.22 C901830021 Total Num of UL AFS5.15k frame .............................................89-13 89.23 C901830022 Total Num of UL AFS4.75k frame .............................................89-14 89.24 C901830023 Total Num of UL AHS7.95k frame .............................................89-14 89.25 C901830024 Total Num of UL AHS7.40k frame .............................................89-15 89.26 C901830025 Total Num of UL AHS6.70k frame .............................................89-15 89.27 C901830026 Total Num of UL AHS5.90k frame .............................................89-16 89.28 C901830027 Total Num of UL AHS5.15k frame .............................................89-16 89.29 C901830028 Total Num of UL AHS4.75k frame .............................................89-17 89.30 C901830029 Total Number of DL WFS12.65k Frame.....................................89-17 89.31 C901830030 Total Number of DL WFS8.85k Frame.......................................89-18 89.32 C901830031 Total Number of DL WFS6.60k Frame.......................................89-19 89.33 C901830032 Total Number of DL OWFS23.85k Frame ..................................89-19 89.34 C901830033 Total Number of DL OWFS15.85k Frame ..................................89-20 89.35 C901830034 Total Number of DL OWFS12.65k Frame ..................................89-21 89.36 C901830035 Total Number of DL OWFS8.85k Frame ....................................89-21 89.37 C901830036 Total Number of DL OWFS6.60k Frame ....................................89-22 89.38 C901830037 Total Number of DL OWHS12.65k Frame..................................89-23 89.39 C901830038 Total Number of DL OWHS8.85k Frame....................................89-24 89.40 C901830039 Total Number of DL OWHS6.60k Frame....................................89-24 89.41 C901830040 Total Number of UL WFS12.65k Frame.....................................89-25 89.42 C901830041 Total Number of UL WFS8.85k Frame.......................................89-26 89.43 C901830042 Total Number of UL WFS6.60k Frame.......................................89-26 89.44 C901830043 Total Number of UL OWFS23.85k Frame ..................................89-27 89.45 C901830044 Total Number of UL OWFS15.85k Frame ..................................89-28 89.46 C901830045 Total Number of UL OWFS12.65k Frame ..................................89-28 89.47 C901830046 Total Number of UL OWFS8.85k Frame ....................................89-29 89.48 C901830047 Total Number of UL OWFS6.60k Frame ....................................89-30 89.49 C901830048 Total Number of UL OWHS12.65k Frame..................................89-31 89.50 C901830049 Total Number of UL OWHS8.85k Frame....................................89-31 89.51 C901830050 Total Number of UL OWHS6.60k Frame....................................89-32

Chapter 90 PPP channel measurement.................................................. 90-1

90.1 C901840001 Received byte count ................................................................... 90-1

CLX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

90.2 C901840002 Received packet count................................................................ 90-1 90.3 C901840003 Received framing aborts ............................................................. 90-2 90.4 C901840004 Received FCS errors .................................................................. 90-2 90.5 C901840005 Received packets greater than maximum length........................... 90-2 90.6 C901840006 Non-octet aligned frames received .............................................. 90-3 90.7 C901840007 Received small datagrams discarded byte count .......................... 90-3 90.8 C901840008 Received jumbo packets byte count............................................. 90-3 90.9 C901840009 Received small datagrams discarded event count ........................ 90-4 90.10 C901840010 Received jumbo packets count .................................................. 90-4 90.11 C901840011 Transmitted byte count .............................................................. 90-4 90.12 C901840012 Transmitted packet count .......................................................... 90-5 90.13 C901840013 Transmit framing aborts ............................................................ 90-5 90.14 C901840014 MLPPP ID ................................................................................ 90-5 90.15 C901840015 PPP band width ....................................................................... 90-5

Chapter 91 UMAC Measurement ............................................................. 91-1

91.1 Overview ....................................................................................................... 91-3 91.2 C901850001 receive discard packets flag ........................................................ 91-3 91.3 C901850002 receive discard packets low 32bits............................................... 91-4 91.4 C901850003 receive discard packets high 32bits ............................................. 91-4 91.5 C901850004 receive bytes flag ....................................................................... 91-4 91.6 C901850005 receive bytes low 32bits .............................................................. 91-5 91.7 C901850006 receive bytes high 32bits............................................................. 91-5 91.8 C901850007 receive packets flag.................................................................... 91-5 91.9 C901850008 receive packets low 32bits .......................................................... 91-6 91.10 C901850009 receive packets high 32bits ....................................................... 91-6 91.11 C901850010 receive broadcast packets flag................................................... 91-6 91.12 C901850011 receive broadcast packets low 32bits ......................................... 91-7 91.13 C901850012 receive broadcast packets high 32bits........................................ 91-7 91.14 C901850013 receive multicast packets flag .................................................... 91-8 91.15 C901850014 receive multicast packets low 32bits .......................................... 91-8 91.16 C901850015 receive multicast packets high 32bits ......................................... 91-8 91.17 C901850016 receive CRC or align error packets flag ...................................... 91-9 91.18 C901850017 receive CRC or align error packets low 32bits............................. 91-9 91.19 C901850018 receive CRC or align error packets high 32bits ..........................91-10 91.20 C901850019 receive small than 64 bytes packets flag ...................................91-10 91.21 C901850020 receive small than 64 bytes packets low 32bits ..........................91-10 91.22 C901850021 receive small than 64 bytes packets high 32bits......................... 91-11

CLXI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

91.23 C901850022 receive large than 1518 bytes packets flag ................................ 91-11 91.24 C901850023 receive large than 1518 bytes packets low 32bits.......................91-12 91.25 C901850024 receive large than 1518 bytes packets high 32bits .....................91-12 91.26 C901850025 The flag of received fragment packets.......................................91-12 91.27 C901850026 Number of fragment packets received (low 32 bit)......................91-13 91.28 C901850027 Number of received fragment packets (high 32 bit) ....................91-13 91.29 C901850028 receive Jabber packets flag......................................................91-14 91.30 C901850029 receive Jabber packets low 32bits ............................................91-14 91.31 C901850030 receive Jabber packets high 32bits ...........................................91-14 91.32 C901850031 receive Collision count flag.......................................................91-15 91.33 C901850032 receive Collision count low 32bits .............................................91-15 91.34 C901850033 receive Collision count high 32bits ............................................91-15 91.35 C901850034 receive 64 bytes packets flag ...................................................91-16 91.36 C901850035 receive 64 bytes packets low 32bits ..........................................91-16 91.37 C901850036 receive 64 bytes packets high 32bits.........................................91-17 91.38 C901850037 receive 65 to 127 bytes packets flag .........................................91-17 91.39 C901850038 receive 65 to 127 bytes packets low 32bits................................91-17 91.40 C901850039 receive 65 to 127 bytes packets high 32bits ..............................91-18 91.41 C901850040 receive 128 to 255 bytes packets flag .......................................91-18 91.42 C901850041 receive 128 to 255 bytes packets low 32bits ..............................91-19 91.43 C901850042 receive 128 to 255 bytes packets high 32bits.............................91-19 91.44 C901850043 receive 256 to 511 bytes packets flag........................................91-19 91.45 C901850044 receive 256 to 511 bytes packets low 32bits ..............................91-20 91.46 C901850045 receive 256 to 511 bytes packets high 32bits .............................91-20 91.47 C901850046 receive 512 to 1023 bytes packets flag......................................91-21 91.48 C901850047 receive 512 to 1023 bytes packets low 32bits ............................91-21 91.49 C901850048 receive 512 to 1023 bytes packets high 32bits...........................91-21 91.50 C901850049 receive 1024 to 1518 bytes packets flag....................................91-22 91.51 C901850050 receive 1024 to 1518 bytes packets low 32bits ..........................91-22 91.52 C901850051 receive 1024 to 1518 bytes packets high 32bits .........................91-23 91.53 C901850052 send discard packets flag.........................................................91-23 91.54 C901850053 send discard packets low 32bits ...............................................91-23 91.55 C901850054 send discard packets high 32bits ..............................................91-24 91.56 C901850055 send packet bytes flag .............................................................91-24 91.57 C901850056 send packet bytes low 32bits....................................................91-24 91.58 C901850057 send packets bytes high 32bits.................................................91-25 91.59 C901850058 send packets flag ....................................................................91-25

CLXII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

91.60 C901850059 send packets low 32bits ...........................................................91-26 91.61 C901850060 send packets high 32bits..........................................................91-26 91.62 C901850061 send broadcast packets flag .....................................................91-26 91.63 C901850062 send broadcast packets low 32bits ...........................................91-27 91.64 C901850063 send broadcast packets high 32bits ..........................................91-27 91.65 C901850064 send multicast packets flag ......................................................91-27 91.66 C901850065 send multicast packets low 32bits .............................................91-28 91.67 C901850066 send multicast packets high 32bits............................................91-28 91.68 C901850067 send CRC or Align error packets flag ........................................91-28 91.69 C901850068 send CRC or Align error packets low 32bits...............................91-29 91.70 C901850069 send CRC or Align error packets high 32bits .............................91-29 91.71 C901850070 send small than 64 bytes packets flag.......................................91-30 91.72 C901850071 send small than 64 bytes packets low 32bits .............................91-30 91.73 C901850072 send small than 64 bytes packets high 32bits ............................91-30 91.74 C901850073 send large than 1518 bytes packets flag ...................................91-31 91.75 C901850074 send large than 1518 bytes packets low 32bits ..........................91-31 91.76 C901850075 send large than 1518 bytes packets high 32bits.........................91-32 91.77 C901850076 The flag of sent fragment packets .............................................91-32 91.78 C901850077 Number of sent fragment packets (low 32 bit) ............................91-32 91.79 C901850078 Number of sent fragment packets (high 32 bit)...........................91-33 91.80 C901850079 send Jabber packets flag .........................................................91-33 91.81 C901850080 send Jabber packets low 32bits ................................................91-34 91.82 C901850081 send Jabber packets high 32bits...............................................91-34 91.83 C901850082 send Collision count flag ..........................................................91-34 91.84 C901850083 send Collision count low 32bits.................................................91-35 91.85 C901850084 send Collision count high 32bits................................................91-35 91.86 C901850085 send 64 bytes packets flag .......................................................91-35 91.87 C901850086 send 64 bytes packets low 32bits .............................................91-36 91.88 C901850087 send 64 bytes packets high 32bits ............................................91-36 91.89 C901850088 send 65 to 127 bytes packets flag.............................................91-36 91.90 C901850089 send 65 to 127 bytes packets low 32bits ...................................91-37 91.91 C901850090 send 65 to 127 bytes packets high 32bits ..................................91-37 91.92 C901850091 send 128 to 255 bytes packets flag ...........................................91-38 91.93 C901850092 send 128 to 255 bytes packets low 32bits .................................91-38 91.94 C901850093 send 128 to 255 bytes packets high 32bits ................................91-38 91.95 C901850094 send 256 to 511 bytes packets flag ...........................................91-39 91.96 C901850095 send 256 to 511 bytes packets low 32bits..................................91-39

CLXIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

91.97 C901850096 send 256 to 511 bytes packets high 32bits ................................91-40 91.98 C901850097 send 512 to 1023 bytes packets flag .........................................91-40 91.99 C901850098 send 512 to 1023 bytes packets low 32bits................................91-40 91.100 C901850099 send 512 to 1023 bytes packets high 32bits ............................91-41 91.101 C901850100 send 1024 to 1518 bytes packets flag .....................................91-41 91.102 C901850101 send 1024 to 1518 bytes packets low 32bits ............................91-42 91.103 C901850102 send 1024 to 1518 bytes packets high 32bits...........................91-42 91.104 C901850103 Logic port type.......................................................................91-42

Chapter 92 Downlink EGPRS2-A TBF Statistic...................................... 92-1

92.1 C901860001 Total number DL EGPRS2-A TBF EST REQ ................................ 92-3 92.2 C901860002 Number DL EGPRS2-A TBF EST REQ CCCH/PCCCH ............... 92-3 92.3 C901860003 Number DL EGPRS2-A TBF EST REQ........................................ 92-4 92.4 C901860004 Number DL EGPRS2-A TBF est req fail CPU ............................... 92-5 92.5 C901860005 Number DL EGPRS2-A TBF Est Req Fail .................................... 92-5 92.6 C901860006 Number DL EGPRS2-A TBF EST channel allocate fail.................. 92-5 92.7 C901860007 Number DL EGPRS2-A TBF est req fail Abis cong ....................... 92-7 92.8 C901860008 Number DL EGPRS2-A TBF est req fail RR cong ......................... 92-8 92.9 C901180009 Number DL EGPRS2-A TBF est req fail UPPB-DSP channel cong .............................................................................................................. 92-9 92.10 C901860010 Number DL EGPRS2-A TBF EST channel allocate success .......92-10 92.11 C901860011 Number DL EGPRS2-A TBF successful EST ............................. 92-11 92.12 C901860012 Number DL EGPRS2-A TBF EST channel activate fail...............92-12 92.13 C901860013 Num DL EGPRS2-A TBF failed EST caused by connection with BTS ..............................................................................................................92-12 92.14 C901860014 Num DL EGPRS2-A TBF failed EST caused by connection with BIU ...............................................................................................................92-13 92.15 C901860015 Number DL EGPRS2-A TBF EST channel activate success .......92-14 92.16 C901860016 Number DL EGPRS2-A TBF EST fail........................................92-15 92.17 C901860017 Number DL EGPRS2-A TBF EST Fail MSidle PCCCH/CCCH ......92-15 92.18 C901860018 Number DL EGPRS2-A TBF EST fail MStrans ..........................92-16 92.19 C901860019 Number DL EGPRS2-A TBF EST success MSidle PCCCH/CCCH ..............................................................................................92-16 92.20 C901860020 Number DL EGPRS2-A TBF EST Success MStrans ..................92-17 92.21 C901860021 Num DL EGPRS2-A TBF res realloc req for uplink TBF establishment ................................................................................................92-17 92.22 C901860022 Number DL res realloc downlink TBF est channel allocate fail ................................................................................................................92-18 92.23 C901860023 Number DL res realloc req fail Abis cong...................................92-19

CLXIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

92.24 C901860024 Number DL res realloc req fail RR cong ....................................92-19 92.25 C901860025 Number res realloc req fail UPPB-DSP channel cong.................92-20 92.26 C901860026 Number DL res realloc downlink TBF est channel allocate success ........................................................................................................92-21 92.27 C901860027 Number PDTCH successfully allocated for DL EGPRS2-A TBF while UL TBF est ..........................................................................................92-22 92.28 C901860028 Number DL EGPRS2-A TBF res realloc downlink TBF est channel activate fail .......................................................................................92-23 92.29 C901860029 Number DL EGPRS2-A TBF res realloc downlink TBF est channel activate fail .......................................................................................92-23 92.30 C901860030 Number DL EGPRS2-A TBF res realloc downlink TBF est channel activate fail .......................................................................................92-24 92.31 C901860031 Number DL EGPRS2-A TBF res realloc downlink TBF est channel activate success ...............................................................................92-25 92.32 C901860032 Number DL EGPRS2-A TBF res realloc downlink TBF est fail ................................................................................................................92-26 92.33 C901860033 Number DL EGPRS2-A TBF Res Realloc Downlink TBF Est Success ........................................................................................................92-26 92.34 C901860034 Number DL EGPRS2-A TBF res realloc req ..............................92-26 92.35 C901860035 Number DL res realloc LLC cause channel allocate fail ..............92-27 92.36 C901860036 Number DL res realloc req LLC cause fail Abis cong..................92-28 92.37 C901860037 Number DL res realloc req LLC cause fail RR cong ...................92-28 92.38 C901860038 Number res realloc req LLC cause fail UPPB-DSP channel cong .............................................................................................................92-29 92.39 C901860039 Number DL res realloc LLC cause channel allocate success ......92-30 92.40 C901860040 Number PDTCH reallocated for DL EGPRS2-A TBF caused by LLC transfer ..................................................................................................92-31 92.41 C901860041 Number DL EGPRS2-A TBF res realloc LLC cause channel activate fail....................................................................................................92-32 92.42 C901860042 Number DL EGPRS2-A TBF res realloc LLC cause channel activate fail....................................................................................................92-32 92.43 C901860043 Number DL EGPRS2-A TBF res realloc LLC cause channel activate fail....................................................................................................92-33 92.44 C901860044 Number DL EGPRS2-A TBF res realloc LLC cause channel activate success ............................................................................................92-34 92.45 C901860045 Number DL EGPRS2-A TBF res realloc LLC cause fail ..............92-35 92.46 C901860046 Number DL EGPRS2-A TBF Res Realloc LLC Cause Success ........................................................................................................92-35 92.47 C901860047 Number of EGPRS2-A DL TBF release due to flush LL ..............92-35

CLXV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

92.48 C901860048 Number of EGPRS2-A DL TBF release due to EGPRS2-A suspend requests ..........................................................................................92-36 92.49 C901860049 Number DL EGPRS2-A TBF rel preemption radio......................92-37 92.50 C901860050 Number DL EGPRS2-A TBF rel normal.....................................92-37 92.51 C901860051 Number DL EGPRS2-A TBF rel other .......................................92-38 92.52 C901860052 Number DL EGPRS2-A TBF release caused by abnormal NSVC ...........................................................................................................92-39 92.53 C901860053 Number DL EGPRS2-A TBF release caused by abnormal BVC..............................................................................................................92-39 92.54 C901860054 Number DL EGPRS2-A TBF rel................................................92-40 92.55 C901860055 Preempted times of DL EGPRS2-A TBF ...................................92-41 92.56 C901860056 Preempted inst number of DL EGPRS2-A TBF ..........................92-41 92.57 C901860057 Times of DL EGPRS2-A TBF queuing up for resource ...............92-42 92.58 C901860058 Times of DL EGPRS2-A TBF successfully queuing up for resource .......................................................................................................92-43 92.59 C901860059 Times of DL EGPRS2-A TBF released when queuing up for resource .......................................................................................................92-43

Chapter 93 Up Link EGPRS2A TBF Statistic.......................................... 93-1

93.1 C901870001 Number of Uplink EGPRS2-A TBF Establishment Failure Due to Channel Allocation Failure............................................................................... 93-4 93.2 C901870002 Number of Uplink EGPRS2-A TBF Establishment Failures Due to Abis Congestion ......................................................................................... 93-5 93.3 C901870003 Number of Uplink EGPRS2-A TBF Establishment Failures Due to RR Congestion ........................................................................................... 93-6 93.4 C901870004 Number of uplink EGPRS2-A TBF establishment failures due to UPU resource congestion ............................................................................... 93-8 93.5 C901870005 Number of Uplink EGPRS2-A TBF EST Channel Allocation Success ......................................................................................................... 93-9 93.6 C901870006 Number of Failed Uplink EGPRS2-A TBF Establishments Due to Channel Activation Failure.............................................................................. 93-11 93.7 C901870007 Number of Failed Uplink EGPRS2-A TBF Establishments Due to BTS Connection Failure ................................................................................. 93-11 93.8 C901870008 Number of Uplink EGPRS2-A TBF Establishment Failure Due to BIU Connection Failure ..................................................................................93-12 93.9 C901870009 Number of Uplink EGPRS2-A TBF Channel Activation and Connection Success ......................................................................................93-13 93.10 C901870010 Number of Uplink EGPRS2-A TBF Establishment Failure Due to Not Receiving PIA......................................................................................93-14 93.11 C901870011 Number of Uplink EGPRS2-A TBF Reallocation Requests Due to Downlink TBF Establishment ......................................................................93-14
CLXVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

93.12 C901870012 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to Channel Allocation Failure for Downlink TBF Establishment .......93-15 93.13 C901870013 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to Abis Congestion for Downlink TBF Establishment ......................93-16 93.14 C901870014 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to RR Congestion for Downlink TBF Establishment........................93-17 93.15 C901870015 Number of uplink EGPRS2-A TBF resource reallocation failure due to UPU resource congestion as downlink TBF establishment .....................93-18 93.16 C901870016 Number of Uplink EGPRS2-A TBF Resource Reallocation Success of Channel.......................................................................................93-18 93.17 C901870017 Number of Allocated PDTCH for Uplink EGPRS2-A TBF Resource Reallocation Due to Downlink TBF Establishment.............................93-19 93.18 C901870018 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Downlink TBF Establishment Caused by Channel Activation Failure .................93-20 93.19 C901870019 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to BTS Connection Failure for Downlink TBF Establishment.................................93-21 93.20 C901870020 Number of Uplink EGPRS2-A TBF Reallocation Failure for Downlink TBF Establishment Caused by BIU Connection Failure......................93-22 93.21 C901870021 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Activation and Connection for Downlink TBF Establishment ................93-22 93.22 C901870022 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Downlink TBF Establishment ..........................................................................93-23 93.23 C901870023 Number of Uplink EGPRS2-A TBF Reallocation Success Due to Downlink TBF Establishment ......................................................................93-24 93.24 C901870024 Number of Uplink EGPRS2-A TBF Reallocation Requests Due to LLC Transmission ......................................................................................93-24 93.25 C901870025 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Channel Allocation Failure for LLC Transmission .............................................93-25 93.26 C901870026 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Abis Congestion for LLC Transmission............................................................93-26 93.27 C901870027 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to RR Congestion for LLC Transmission .............................................................93-27 93.28 C901870028 Number of uplink EGPRS2-A TBF reallocation failure due to UPU resource congestion for LLC transmission ...............................................93-28 93.29 C901870029 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Allocation for LLC Transmission ........................................................93-29 93.30 C901870030 Number of Uplink EGPRS2-A TBF Reallocation Due to LLC Transmission.................................................................................................93-29 93.31 C901870031 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Channel Activation Failure for LLC Transmission .............................................93-30

CLXVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

93.32 C901870032 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to BTS Connection Failure for LLC Transmission.................................................93-31 93.33 C901870033 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to BIU Connection Failure for LLC Transmission..................................................93-31 93.34 C901870034 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Activation and Connection for LLC Transmission ................................93-32 93.35 C901870035 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to LLC Transmission..........................................................................................93-32 93.36 C901870036 Number of Uplink EGPRS2-A TBF Reallocation Success Due to LLC Transmission ......................................................................................93-32 93.37 C901870037 Number of Uplink EGPRS2-A TBF Reallocation Requests Due to Resourece Request ...................................................................................93-33 93.38 C901870038 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Database Allocation Failure for Resource Request ..........................................93-33 93.39 C901870039 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to Abis Congestion for Resource Request .....................................93-34 93.40 C901870040 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to RR Congestion for Resource Request.......................................93-34 93.41 C901870041 Number of uplink EGPRS2-A TBF reallocation failure due to UPU resource congestion for resource request................................................93-35 93.42 C901870042 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Allocation for Resource Request .......................................................93-35 93.43 C901870043 Number of PDTCH Reallocated for Uplink EGPRS2-A TBF Triggered by Resource Request .....................................................................93-36 93.44 C901870044 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Resource Request Caused by Channel Activation Failure ................................93-36 93.45 C901870045 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to BTS Connection Failure for Resource Request................................................93-37 93.46 C901870046 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Resource Request Caused by BIU Connection Failure.....................................93-37 93.47 C901870047 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Activation and Connection for Resource Request ...............................93-38 93.48 C901870048 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Resource Request .........................................................................................93-38 93.49 C901870049 Number of Uplink EGPRS2-A TBF Reallocation Success Due to Resource Request .....................................................................................93-38 93.50 C901870050 Number of Uplink EGPRS2-A TBF Release Due to Flush LLC ..............................................................................................................93-39 93.51 C901870051 Number of Uplink EGPRS2-A TBF Release Due to Suspend Requests ......................................................................................................93-39 93.52 C901870052 Number of Uplink EGPRS2-A TBF Forced Release by CS .........93-40
CLXVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

93.53 C901870053 Number of Uplink EGPRS2-A TBF Normal Release Due to User Plane Requests .............................................................................................93-40 93.54 C901870054 Number of Uplink EGPRS2-A TBF Abnormal Release Due to Other Reason................................................................................................93-40 93.55 C901870055 Number of Uplink EGPRS2-A TBF Release Due to NSVC Problem ........................................................................................................93-41 93.56 C901870056 Number of Uplink EGPRS2-A TBF Release Due to BVC Problem ........................................................................................................93-41 93.57 C901870057 Number of Uplink EGPRS2-A TBF Release Due to Other Reason .........................................................................................................93-41 93.58 C901870058 Number of Uplink EGPRS2-A TBF Preempting Resource ..........93-42 93.59 C901870059 Number of Instances Preempted by Uplink EGPRS2-A TBF.......93-42 93.60 C901870060 Number of Uplink EGPRS2-A TBF Queuing Up for Resource ......93-43 93.61 C901870061 Number of Uplink EGPRS2-A TBF Successfully Getting Resource Through Queuing ...........................................................................93-43 93.62 C901870062 Number of Uplink EGPRS2-A TBF Released When Queuing Up for Resource ............................................................................................93-43 93.63 C901870063 Times of Uplink EGPR2A TBF Requesting DLDC Resources ......93-44 93.64 C901870064 Times of Allocating Uplink DLDC Resources for EGPRS2A TBF ....................................................................................................................93-44

Chapter 94 PS Handover Cause Measurement...................................... 94-1

94.1 Overview ....................................................................................................... 94-1 94.2 C901880001 Number of handover attempts due to uplink received strength ....... 94-1 94.3 C901880002 Number of handover attempts due to downlink received strength ......................................................................................................... 94-2 94.4 C901880003 Number of handover attempts due to uplink quality....................... 94-3 94.5 C901880004 Number of handover attempts due to downlink quality................... 94-4 94.6 C901880005 Number of handover attempts due to uplink interference............... 94-4 94.7 C901880006 Number of handover attempts due to downlink interference........... 94-5 94.8 C901880007 Number of handover attempts due to PBGT ................................. 94-6 94.9 C901880008 Number of handover attempts due to large TA.............................. 94-6 94.10 C901880009 Number of handover attempts due to uplink break up quickly ...... 94-7 94.11 C901880010 Number of handover attempts due to macro-micro switch............ 94-8 94.12 C901880011 Number of handover attempts due to high traffic ......................... 94-9 94.13 C901880012 Number of handover attempts due to a good standard level in FDD adjacent cell ........................................................................................... 94-9 94.14 C901880013 Number of handover attempts due to a good standard level in TDD adjacent cell ..........................................................................................94-10 94.15 C901880014 Number of handover attempts due to PCCN.............................. 94-11
CLXIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement ................................... 95-1

95.1 Overview ....................................................................................................... 95-2 95.2 C901890001 Number of synchronous handover executions .............................. 95-2 95.3 C901890002 Number of successful synchronous handovers ............................. 95-3 95.4 C901890003 Number of pre-synchronous handover executions ........................ 95-4 95.5 C901890004 Number of successful pre-synchronous handovers ....................... 95-5 95.6 C901890005 Number of asynchronous handover executions ............................ 95-6 95.7 C901890006 Number of successful asynchronous handovers ........................... 95-7 95.8 C901890007 Number of normal handover executions ....................................... 95-8 95.9 C901890008 Number of successful normal handovers...................................... 95-9 95.10 C901890009 Number of optimised handover executions ................................95-10 95.11 C901890010 Number of successful optimised handovers ............................... 95-11 95.12 C901890011 Number of Intra-BSC inter-cell handover out attempts ................95-12 95.13 C901890012 Number of Intra-BSC inter-cell handover out executions.............95-12 95.14 C901890013 Number of successful Intra-BSC inter-cell handover out .............95-13 95.15 C901890014 Number of Inter-BSC handover out attempts .............................95-14 95.16 C901890015 Number of Inter-BSC handover out executions ..........................95-15 95.17 C901890016 Number of successful Inter-BSC handover out ..........................95-16 95.18 C901890017 Number of handover in attempts...............................................95-17 95.19 C901890018 Number of handover in executions............................................95-17 95.20 C901890019 Number of successful handover in ............................................95-18 95.21 C901890020 Number of Intra-cell handover attempts.....................................95-19 95.22 C901890021 Number of Intra-Cell handover executions.................................95-19 95.23 C901890022 Number of successful Intra-cell handovers ................................95-20 95.24 C901890023 Number of invalid Intra-cell handovers ......................................95-20 95.25 C901890024 Number of 2G to FDD handover attempts .................................95-21 95.26 C901890025 Number of 2G to FDD handover executions ..............................95-21 95.27 C901890026 Number of successful 2G to FDD handovers .............................95-22 95.28 C901890027 Number of 2G to TDD handover attempts .................................95-23 95.29 C901890028 Number of 2G to TDD handover executions ..............................95-24 95.30 C901890029 Number of successful 2G to TDD handovers .............................95-24 95.31 C901890030 Number of 3G to 2G handover attempts ....................................95-25 95.32 C901890031 Number of 3G to 2G handover executions.................................95-26 95.33 C901890032 Number of successful 3G to 2G handovers ...............................95-27 95.34 C901890033 Number of T12 expiry ..............................................................95-27 95.35 C901890034 Number of PCCF received .......................................................95-28 95.36 C901890035 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause Create PFC Failure..........................................................95-29
CLXX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

95.37 C901890036 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause PS Handover Target not allowed ......................................95-29 95.38 C901890037 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause PS Handover not Supported in Target BSS or Target System .........................................................................................................95-30 95.39 C901890038 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause other reasons ..................................................................95-31 95.40 C901890039 Number of failure in optimised handover due to failure alloc resource .......................................................................................................95-32 95.41 C901890040 Number of failure in optimised handover due to PS handover not supported in target cell .............................................................................95-33

Chapter 96 IURG Measurement............................................................... 96-1

96.1 Overview ....................................................................................................... 96-1 96.2 C901900001 Number of relocation requests (on Iur-g) ...................................... 96-1 96.3 C901900002 Number of relocation executions (on Iur-g)................................... 96-2 96.4 C901900003 Number of relocation successes (on Iur-g) ................................... 96-4 96.5 C901900004 Number of relocation failures due to no valid radio resource (on Iur-g) ............................................................................................................. 96-5 96.6 C901900005 Number of relocation failures due to no valid terrestrial circuit resource (on Iur-g) .......................................................................................... 96-6 96.7 C901900006 Number of relocation failures due to loss of UE handover complete message (on Iur-g) ........................................................................... 96-7 96.8 C901900007 Number of relocation failures due to MS returning to original channel (on Iur-g) ........................................................................................... 96-8 96.9 C901900008 Number of relocation failures due to other causes (on Iur-g).......... 96-9

Chapter 97 RTCP Measurement .............................................................. 97-1

97.1 Overview ....................................................................................................... 97-1 97.2 C901910001 local jitter (CS) ........................................................................... 97-1 97.3 C901910002 distant jitter (CS) ........................................................................ 97-2 97.4 C901910003 average one-way delay (CS) ....................................................... 97-3 97.5 C901910004 maximal one-way delay (CS)....................................................... 97-5 97.6 C901910005 local cumulative fraction lost (CS)................................................ 97-6 97.7 C901910006 distant cumulative fraction lost (CS)............................................. 97-7 97.8 C901910007 local jitter (PS)............................................................................ 97-9 97.9 C901910008 distant jitter (PS)........................................................................97-10 97.10 C901910009 average one-way delay (PS) .................................................... 97-11 97.11 C901910010 maximal one-way delay (PS) ....................................................97-13 97.12 C901910011 local cumulative fraction lost (PS) .............................................97-14 97.13 C901910012 distant cumulative fraction lost (PS) ..........................................97-15
CLXXI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 98 DSP Measurement ................................................................ 98-1

98.1 Overview ....................................................................................................... 98-1 98.2 C901920001 the times of loss of TRAU frame synchronization in BIPB .............. 98-1

Chapter 99 Access Control Measurement ............................................. 99-1

99.1 Overview ....................................................................................................... 99-2 99.2 C901930001 Number of CS Call Denied for Lack of IPAbis BandWidth UpLink ........................................................................................................... 99-2 99.3 C901930002 Number of CS Call Denied for Lack of IPAbis BandWidth DownLink....................................................................................................... 99-3 99.4 C901930003 Number of PS Call Denied for Lack of IPAbis BandWidth UpLink ........................................................................................................... 99-3 99.5 C901930004 Number of PS Call Denied for Lack of IPAbis BandWidth DownLink....................................................................................................... 99-4 99.6 C901930005 Number of Pushing Down Uplink BandWidth ................................ 99-5 99.7 C901930006 Number of Pushing Down Downlink BandWidth ........................... 99-5 99.8 C901930007 Number of Pushing Up Uplink BandWidth ................................... 99-6 99.9 C901930008 Number of Pushing Up Downlink BandWidth ................................ 99-7 99.10 C901930009 Peak value of allocated bandwidth uplink ................................... 99-8 99.11 C901930010 Value of allocated bandwidth uplink............................................ 99-8 99.12 C901930011 Number of allocated bandwidth uplink samples........................... 99-9 99.13 C901930012 Peak value of allocated bandwidth downlink ............................... 99-9 99.14 C901930013 Value of allocated bandwidth downlink ......................................99-10 99.15 C901930014 Number of allocated bandwidth downlink samples .....................99-10 99.16 C901930015 Value of available bandwidth uplink........................................... 99-11 99.17 C901930016 Value of available bandwidth downlink ...................................... 99-11 99.18 C901930017 Number of CS preempt PS because of Abis resource ................99-12 99.19 C901930018 Number of CS allocate Abis resource........................................99-12 99.20 C901930019 Number of PS allocate Abis resource........................................99-13 99.21 C901930020 Number of PS restricted because of Abis resource ....................99-13 99.22 C901930021 Number of PDCH allocation restricted because of Abis resource .......................................................................................................99-14 99.23 C901930022 Peak value of cell CS Abis bandwidth uplink..............................99-14 99.24 C901930023 Peak value of PS Abis bandwidth uplink....................................99-15 99.25 C901930024 Value of CS Abis Bandwidth Uplink...........................................99-15 99.26 C901930025 Number of CS Abis Bandwidth Uplink Samples .........................99-15 99.27 C901930026 Value of PS Abis Bandwidth Uplink ...........................................99-16 99.28 C901930027 Number of PS Abis Bandwidth Uplink Samples .........................99-16 99.29 C901930028 Peak Value of CS Abis Bandwidth Downlink ..............................99-17
CLXXII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

99.30 C901930029 Peak value of PS Abis bandwidth downlink ...............................99-17 99.31 C901930030 Value of CS Abis Bandwidth Downlink.......................................99-18 99.32 C901930031 Number of CS Abis Bandwidth Downlink Samples .....................99-18 99.33 C901930032 Value of PS Abis Bandwidth Downlink.......................................99-19 99.34 C901930033 Number of PS Abis Bandwidth Downlink Samples .....................99-19 99.35 C901930034 Number of CS Call Denied for Lack of IPAbis BandWidth UpLink But Preempt PS IPAbis Successfully...............................................................99-20 99.36 C901930035 Number of CS Call Denied for Lack of IPAbis BandWidth DownLink But Preempt PS IPAbis Successfully ...............................................99-20

Chapter 100 Power Control Measurement ........................................... 100-1

100.1 Overview.....................................................................................................100-1 100.2 C901940001 The count of iBSC receiving power control indication from BTS ..............................................................................................................100-2 100.3 C901940002 The count of channel downlink power exceeding TRX mean downlink power, when iBSC receives power control indication from BTS ...........100-3 100.4 C901940003 The count of CS service channel allocation failure caused by power shortage .............................................................................................100-4 100.5 C901940004 The count of CS timeslot allocation failure caused by power shortage .......................................................................................................100-5 100.6 C901940005 The count of PS service channel allocation failure caused by power shortage .............................................................................................100-7 100.7 C901940006 The count of PS timeslot allocation failure caused by power shortage .......................................................................................................100-7 100.8 C901940007 The Count of CS Service Channel Allocation Failure Caused by PLMN Power Shortage ..................................................................................100-8 100.9 C901940008 The Count of CS Timeslot Allocation Failure Caused by PLMN Power Shortage.............................................................................................100-8 100.10 C901940009 The Count of PS Service Channel Allocation Failure Caused by PLMN Power Shortage ..............................................................................100-8 100.11 C901940010 The Count of PS Timeslot Allocation Failure Caused by PLMN Power Shortage.............................................................................................100-9 100.12 C901940011 The Count of Power Congestion Due to RRU Power Limit ........100-9 100.13 C901940012 Time of Power Congestion Due to RRU Power Limit ..............100-10 100.14 C901940013 The Count of Power Congestion Due to PLMN Power Limit ...........................................................................................................100-10 100.15 C901940014 Time of Power Congestion Due to PLMN Power Limit ............100-10 100.16 C901940015 The Count of PDTCH Power Decrease Due to Power Congestion.................................................................................................. 100-11 100.17 C901940016 Time of PDTCH Power Decrease Due to Power Congestion.................................................................................................. 100-11
CLXXIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

100.18 C901940017 The Count of 8PSK Power Increase Due to Power Enough ......100-12 100.19 C901940018 Time of 8PSK Power Increase Due to Power Enough ............100-12

Chapter 101 PS Adjacent Cell Handover Measurement...................... 101-1

101.1 Overview.....................................................................................................101-2 101.2 C901950001 Number of handover attempts on the adjacent cell.....................101-2 101.3 C901950002 Number of successful handovers from selected cell to the adjacent cell ..................................................................................................101-3 101.4 C901950003 Number of handover attempts from adjacent cell to the selected cell ...............................................................................................................101-4 101.5 C901950004 Number of successful handovers from adjacent cell to the selected cell ..................................................................................................101-5 101.6 C901950005 Number of handover attempts from selected cell to the adjacent cell due to better uplink quality........................................................................101-6 101.7 C901950006 Number of handover attempts from selected cell to the adjacent cell due to better downlink quality ...................................................................101-7 101.8 C901950007 Number of successful handovers from selected cell to the adjacent cell due to better uplink quality ..........................................................101-9 101.9 C901950008 Number of successful handovers from selected cell to the adjacent cell due to better downlink quality ....................................................101-10 101.10 C901950009 Number of handover attempts from selected cell to the adjacent cell due to better uplink strength...................................................... 101-11 101.11 C901950010 Number of handover attempts from selected cell to the adjacent cell due to better downlink strength .................................................101-12 101.12 C901950011 Number of successful handovers from selected cell to the adjacent cell due to better uplink strength......................................................101-13 101.13 C901950012 Number of successful handovers from selected cell to the adjacent cell due to better downlink strength .................................................101-14 101.14 C901950013 Number of handover attempts from selected cell to the adjacent cell due to PBGT............................................................................101-16 101.15 C901950014 Number of successful handovers from selected cell to the adjacent cell due to PBGT............................................................................101-17 101.16 C901950015 Number of handover attempts from selected cell to the adjacent cell due to large TA ........................................................................101-18 101.17 C901950016 Number of successful handover from selected cell to the adjacent cell due to large TA ........................................................................101-19 101.18 C901950017 Number of handover attempts from selected cell to the adjacent cell due to high traffic .....................................................................101-20 101.19 C901950018 Number of successful handover from selected cell to the adjacent cell due to high traffic .....................................................................101-21

Chapter 102 ACL Flow Statistic ............................................................ 102-1

CLXXIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

102.1 C901970001 ID of Application Type (0: ACCESS, 1: IPSEC, 2: PBR).............102-2 102.2 C901970002 Action (NOT IPSEC, PASS=0, DISCARD=other; IPSEC, PASS=0 Or 3, DISCARD=1, ipsec=2;) ............................................................102-2 102.3 C901970003 Min Value of Protocol ...............................................................102-3 102.4 C901970004 Max Value of Protocol ..............................................................102-3 102.5 C901970005 Min Value of Source IP (Fragment 1) ........................................102-3 102.6 C901970006 Min Value of Source IP (Fragment 2) ........................................102-4 102.7 C901970007 Min Value of Source IP (Fragment 3) ........................................102-4 102.8 C901970008 Min Value of Source IP (Fragment 4) ........................................102-4 102.9 C901970009 Max Value of Source IP (Fragment 1) .......................................102-5 102.10 C901970010 Max Value of Source IP (Fragment 2)......................................102-5 102.11 C901970011 Max Value of Source IP (Fragment 3) ......................................102-6 102.12 C901970012 Max Value of Source IP (Fragment 4)......................................102-6 102.13 C901970013 Min Value of Dest IP (Fragment 1) ..........................................102-6 102.14 C901970014 Min Value of Dest IP (Fragment 2) ..........................................102-7 102.15 C901970015 Min Value of Dest IP (Fragment 3) ..........................................102-7 102.16 C901970016 Min Value of Dest IP (Fragment 4) ..........................................102-7 102.17 C901970017 Max Value of Dest IP (Fragment 1) .........................................102-8 102.18 C901970018 Max Value of Dest IP (Fragment 2) .........................................102-8 102.19 C901970019 Max Value of Dest IP (Fragment 3) .........................................102-9 102.20 C901970020 Max Value of Dest IP (Fragment 4) .........................................102-9 102.21 C901970021 Min Value of Source Port........................................................102-9 102.22 C901970022 Max Value of Source Port. ....................................................102-10 102.23 C901970023 Min Value of Dest Port..........................................................102-10 102.24 C901970024 Max Value of Dest Port.........................................................102-10 102.25 C901970025 Direction (1: IN; 2: OUT) ...................................................... 102-11 102.26 C901970026 Number of Packets Filtered (Low 32 bits) .............................. 102-11 102.27 C901970027 Number of Packets Filtered (High 32 bits) .............................102-12 102.28 C901970028 Number of Bytes Filtered (Low 32 bits)..................................102-12 102.29 C901970029 Number of Bytes Filtered (High 32 bits) .................................102-12

Chapter 103 LAPDm Measurement....................................................... 103-1

103.1 Overview.....................................................................................................103-2 103.2 C902000001 Number of Error Indications due to T200 expired on SDCCH ......103-3 103.3 C902000002 Number of Error Indications due to unsolicited message on SDCCH.........................................................................................................103-3 103.4 C902000003 Number of Error Indications due to unsolicited DM response on SDCCH.........................................................................................................103-4

CLXXV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

103.5 C902000004 Number of Error Indications due to sequence error on SDCCH.........................................................................................................103-5 103.6 C902000005 Number of Error Indications due to frame content error on SDCCH.........................................................................................................103-6 103.7 C902000006 Number of Error Indications due to SABM command on SDCCH.........................................................................................................103-6 103.8 C902000007 Number of Error Indications due to T200 expired on TCH/F........103-7 103.9 C902000008 Number of Error Indications due to unsolicited message on TCH/F...........................................................................................................103-8 103.10 C902000009 Number of Error Indications due to unsolicited DM response on TCH/F ......................................................................................................103-8 103.11 C902000010 Number of Error Indications due to sequence error on TCH/F...........................................................................................................103-9 103.12 C902000011 Number of Error Indications due to frame content error on TCH/F.........................................................................................................103-10 103.13 C902000012 Number of Error Indications due to SABM command on TCH/F......................................................................................................... 103-11 103.14 C902000013 Number of Error Indications due to T200 expired on TCH/H ........................................................................................................ 103-11 103.15 C902000014 Number of Error Indications due to unsolicited message on TCH/H ........................................................................................................103-12 103.16 C902000015 Number of Error Indications due to unsolicited DM response on TCH/H....................................................................................................103-13 103.17 C902000016 Number of Error Indications due to sequence error on TCH/H ........................................................................................................103-13 103.18 C902000017 Number of Error Indications due to frame content error on TCH/H ........................................................................................................103-14 103.19 C902000018 Number of Error Indications due to SABM command on TCH/H ........................................................................................................103-15 103.20 C902000019 Number of Release Indications due to T200 expired on SDCCH.......................................................................................................103-16 103.21 C902000020 Number of Release Indications due to unsolicited DM response on SDCCH ...................................................................................103-16 103.22 C902000021 Number of Release Indications due to sequence error on SDCCH.......................................................................................................103-17 103.23 C902000022 Number of Release Indications due to T200 expired on TCH/F (signaling) ...................................................................................................103-18 103.24 C902000023 Number of Release Indications due to unsolicited DM response on TCH/F (signaling) .....................................................................103-19 103.25 C902000024 Number of Release Indications due to sequence error on TCH/F (signaling) ........................................................................................103-20
CLXXVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

103.26 C902000025 Number of Release Indications due to T200 expired on TCH/F (speech) .....................................................................................................103-21 103.27 C902000026 Number of Release Indications due to unsolicited DM response on TCH/F (speech) .......................................................................103-21 103.28 C902000027 Number of Release Indications due to sequence error on TCH/F (speech)...........................................................................................103-22 103.29 C902000028 Number of Release Indications due to T200 expired on TCH/F (data)..........................................................................................................103-23 103.30 C902000029 Number of Release Indications due to unsolicited DM response on TCH/F (data)............................................................................103-24 103.31 C902000030 Number of Release Indications due to sequence error on TCH/F (data) ...............................................................................................103-25 103.32 C902000031 Number of Release Indications due to T200 expired on TCH/H (signaling) ...................................................................................................103-26 103.33 C902000032 Number of Release Indications due to unsolicited DM response on TCH/H (signaling).....................................................................103-26 103.34 C902000033 Number of Release Indications due to sequence error on TCH/H (signaling) ........................................................................................103-27 103.35 C902000034 Number of Release Indications due to T200 expired on TCH/H (speech) .....................................................................................................103-28 103.36 C902000035 Number of Release Indications due to unsolicited DM response on TCH/H (speech) .......................................................................103-29 103.37 C902000036 Number of Error Indications due to sequence error on TCH/H (speech) .....................................................................................................103-30 103.38 C902000037 Number of Release Indications due to T200 expired on TCH/H (data)..........................................................................................................103-31 103.39 C902000038 Number of Release Indications due to unsolicited DM response on TCH/H (data) ...........................................................................103-31 103.40 C902000039 Number of Release Indications due to sequence error on TCH/H (data)...............................................................................................103-32 103.41 C902000040 Number of Release Indications without Error Ind on SDCCH.......................................................................................................103-33 103.42 C902000041 Number of Release Indications without Error Ind on TCH/F (signaling) ...................................................................................................103-33 103.43 C902000042 Number of Release Indications without Error Ind on TCH/F (speech) .....................................................................................................103-34 103.44 C902000043 Number of Release Indications without Error Ind on TCH/F (data)..........................................................................................................103-34 103.45 C902000044 Number of Release Indications without Error Ind on TCH/H (signaling) ...................................................................................................103-35

CLXXVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

103.46 C902000045 Number of Release Indications without Error Ind on TCH/H (speech) .....................................................................................................103-35 103.47 C902000046 Number of Release Indications without Error Ind on TCH/H (data)..........................................................................................................103-36 103.48 C902000047 Number of Error Indications Due to Handover Access Level Low ............................................................................................................103-36

Chapter 104 Access Control Detailed Cause Measurement............... 104-1

104.1 Overview.....................................................................................................104-1 104.2 C902010001 Number of PS Uplink BandWidth Allocated More than Overbooking..................................................................................................104-2 104.3 C902010002 Number of PS Uplink BandWidth Measured More than C2 ........104-3 104.4 C902010003 Number of that Sum of PS Uplink BandWidth Measured and Current BandWidth Allocated More than C1 ....................................................104-4 104.5 C902010004 Number of PS Downlink BandWidth Allocated More than Overbooking..................................................................................................104-5 104.6 C902010005 Number of PS Downlink BandWidth Measured More than C2 ......104-6 104.7 C902010006 Number of that Sum of PS Downlink BandWidth Measured and Current BandWidth Allocated More than C1 ....................................................104-7 104.8 C902010007 Number of CS Uplink BandWidth Allocated More than Overbooking .................................................................................................104-8 104.9 C902010008 Number of CS Uplink BandWidth Measured More than C2 .........104-9 104.10 C902010009 Number of that Sum of CS Uplink BandWidth Measured and Current BandWidth Allocated More than C1 ..................................................104-10 104.11 C902010010 Number of CS Downlink BandWidth Allocated More than Overbooking................................................................................................ 104-11 104.12 C902010011 Number of CS Downlink BandWidth Measured More than C2 ..............................................................................................................104-12 104.13 C902010012 Number of that Sum of CS Downlink BandWidth Measured and Current BandWidth Allocated More than C1 ............................................104-13

Chapter 105 BSC Group Call Setup Measurement.............................. 105-1

105.1 Overview.....................................................................................................105-1 105.2 C902020001 Number of VGCS setup attempts..............................................105-1 105.3 C902020002 Number of VGCS setup success ..............................................105-2 105.4 C902020003 Number of VGCS setup failure .................................................105-3 105.5 C902020004 Number of VBS setup attempts ................................................105-3 105.6 C902020005 Number of VBS setup success .................................................105-4 105.7 C902020006 Number of VBS setup failure ....................................................105-5

Chapter 106 VGCS Measurement.......................................................... 106-1

106.1 Overview.....................................................................................................106-2
CLXXVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

106.2 C902030001 Number of VGCS assignment attempts.....................................106-2 106.3 C902030002 Number of VGCS assignment success......................................106-3 106.4 C902030003 Number of VGCS assignment failure ........................................106-3 106.5 C902030004 Number of VGCS Inter-BSC outgoing handover attempts of Talker............................................................................................................106-4 106.6 C902030005 Number of VGCS Inter-BSC outgoing handover execution of Talker............................................................................................................106-5 106.7 C902030006 Number of VGCS Inter-BSC outgoing handover success of Talker............................................................................................................106-6 106.8 C902030007 Number of VGCS Inter-BSC outgoing handover failure of Talker............................................................................................................106-7 106.9 C902030008 Number of VGCS Inter-BSC incoming handover attempts of Talker............................................................................................................106-8 106.10 C902030009 Number of VGCS Inter-BSC incoming handover execution of Talker............................................................................................................106-9 106.11 C902030010 Number of VGCS Inter-BSC incoming handover success of Talker..........................................................................................................106-10 106.12 C902030011 Number of VGCS channel request attempts for NOTIFICATION RESPONSE of Listener ...............................................................................106-10 106.13 C902030012 Number of VGCS channel request success for NOTIFICATION RESPONSE of Listener ............................................................................... 106-11 106.14 C902030013 Number of VGCS channel request failure for NOTIFICATION RESPONSE of Listener ...............................................................................106-12 106.15 C902030014 Number of VGCS channel release for Listener detection ........106-13 106.16 C902030015 Number of Talker drops due to radio link failure .....................106-14 106.17 C902030016 Number of Talker quit ...........................................................106-15 106.18 C902030017 Number of attempts for Listener uplink request ......................106-15 106.19 C902030018 Number of VGCS Intra-BSC Inter-cell outgoing handover attempts of Talker ........................................................................................106-16 106.20 C902030019 Number of VGCS Intra-BSC Inter-cell outgoing handover execution of Talker.......................................................................................106-17 106.21 C902030020 Number of VGCS Intra-BSC Inter-cell outgoing handover success of Talker .........................................................................................106-18 106.22 C902030021 Number of VGCS Intra-BSC Inter-cell outgoing handover failure of Talker ............................................................................................106-19 106.23 C902030022 Number of VGCS Intra-BSC Inter-cell incoming handover attempts of Talker ........................................................................................106-20 106.24 C902030023 Number of VGCS Intra-BSC Inter-cell incoming handover execution of Talker.......................................................................................106-21

CLXXIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

106.25 C902030024 Number of VGCS Intra-BSC Inter-cell incoming handover success of Talker .........................................................................................106-21 106.26 C902030025 Number of NCH overflow of VGCS .......................................106-22 106.27 C902030026 Number of successes for Listener uplink request ...................106-23 106.28 C902030027 Number of failures for Listener uplink request ........................106-23

Chapter 107 VBS Measurement ............................................................ 107-1

107.1 Overview.....................................................................................................107-2 107.2 C902040001 Number of VBS assignment attempts........................................107-2 107.3 C902040002 Number of VBS assignment success ........................................107-3 107.4 C902040003 Number of VBS assignment failure ...........................................107-3 107.5 C902040004 Number of VBS Inter-BSC outgoing handover attempts of Talker............................................................................................................107-4 107.6 C902040005 Number of VBS Inter-BSC outgoing handover execution of Talker............................................................................................................107-5 107.7 C902040006 Number of VBS Inter-BSC outgoing handover success of Talker............................................................................................................107-6 107.8 C902040007 Number of VBS Inter-BSC outgoing handover failure of Talker............................................................................................................107-7 107.9 C902040008 Number of VBS Inter-BSC incoming handover attempts of Talker............................................................................................................107-8 107.10 C902040009 Number of VBS Inter-BSC incoming handover execution of Talker............................................................................................................107-9 107.11 C902040010 Number of VBS Inter-BSC incoming handover success of Talker..........................................................................................................107-10 107.12 C902040011 Number of VBS channel request attempts for NOTIFICATION RESPONSE of Listener ...............................................................................107-10 107.13 C902040012 Number of VBS channel request success for NOTIFICATION RESPONSE of Listener ............................................................................... 107-11 107.14 C902040013 Number of VBS channel request failure for NOTIFICATION RESPONSE of Listener ...............................................................................107-12 107.15 C902040014 Number of VBS channel release for Listener detection ...........107-13 107.16 C902040015 Number of VBS Intra-BSC Inter-cell outgoing handover attempts of Talker ........................................................................................107-14 107.17 C902040016 Number of VBS Intra-BSC Inter-cell outgoing handover execution of Talker.......................................................................................107-15 107.18 C902040017 Number of VBS Intra-BSC Inter-cell outgoing handover success of Talker .........................................................................................107-16 107.19 C902040018 Number of VBS Intra-BSC Inter-cell outgoing handover failure of Talker ......................................................................................................107-17

CLXXX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

107.20 C902040019 Number of VBS Intra-BSC Inter-cell incoming handover attempts of Talker ........................................................................................107-18 107.21 C902040020 Number of VBS Intra-BSC Inter-cell incoming handover execution of Talker.......................................................................................107-19 107.22 C902040021 Number of VBS Intra-BSC Inter-cell incoming handover success of Talker .........................................................................................107-19 107.23 C902040022 Number of NCH overflow of VBS ..........................................107-20 107.24 C902040023 Number of Talker drops due to radio link failure .....................107-21

Chapter 108 eMLPP Measurement........................................................ 108-1

108.1 Overview.....................................................................................................108-2 108.2 C902050001 Number of Talker is preempted.................................................108-2 108.3 C902050002 Number of Listener is preempted ..............................................108-2 108.4 C902050003 Number of preempt attempts due to VGCS setup ......................108-3 108.5 C902050004 Number of preempt attempts due to VBS setup .........................108-4 108.6 C902050005 Number of preempt execution due to VGCS setup .....................108-5 108.7 C902050006 Number of preempt execution due to VBS setup........................108-6 108.8 C902050007 Number of preempt attempts due to NOTIFICATION RESPONSE of Listener .................................................................................108-7 108.9 C902050008 Number of preempt execution due to NOTIFICATION RESPONSE of Listener .................................................................................108-8 108.10 C902050009 Number of preempt attempts due to Inter-BSC handover of Talker............................................................................................................108-9 108.11 C902050010 Number of preempt execution due to Inter-BSC handover of Talker..........................................................................................................108-10 108.12 C902050011 Number of preempt attempts due to Intra-BSC Inter-cell handover of Talker ....................................................................................... 108-11 108.13 C902050012 Number of preempt execution due to Intra-BSC Inter-cell handover of Talker .......................................................................................108-12 108.14 C902050013 Number of queuing attempts due to VGCS setup ...................108-13 108.15 C902050014 Number of queuing execution due to VGCS setup .................108-14 108.16 C902050015 Number of queuing attempts due to VBS setup......................108-15 108.17 C902050016 Number of queuing execution due to VBS setup ....................108-16 108.18 C902050017 Number of queuing attempts due to NOTIFICATION RESPONSE of Listener ...............................................................................108-17 108.19 C902050018 Number of queuing execution due to NOTIFICATION RESPONSE of Listener ...............................................................................108-18 108.20 C902050019 Number of queuing attempts due to inter-BSC incoming handover of Talker .......................................................................................108-19

CLXXXI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

108.21 C902050020 Number of queuing execution due to inter-BSC incoming handover of Talker .......................................................................................108-20 108.22 C902050021 Number of queuing attempts due to Intra-BSC Inter-cell handover of Talker .......................................................................................108-21 108.23 C902050022 Number of queuing execution due to Intra-BSC Inter-cell handover of Talker .......................................................................................108-22

Chapter 109 SDTB E1 Performance Statistic....................................... 109-1

109.1 C902100014 Slip Second.............................................................................109-1 109.2 C902100015 FAS Bit Error ...........................................................................109-1 109.3 C902100016 Near End Available Second......................................................109-2 109.4 C902100017 Near End Background Block Error ............................................109-2 109.5 C902100018 Far End Available Second ........................................................109-2 109.6 C902100019 Far End Background Block Error ..............................................109-3

Chapter 110 Flow Control Measurement .............................................. 110-1

110.1 Overview..................................................................................................... 110-1 110.2 C902110001 Times of channel request messages larger than the threshold ...... 110-1 110.3 C902110002 Times of paging messages larger than the threshold .................. 110-2 110.4 C902110003 Number of channel request message larger than the threshold....................................................................................................... 110-2 110.5 C902110004 The max number of channel request message larger than the threshold....................................................................................................... 110-3

Chapter 111 SDCCH General Handover Measurement ....................... 111-1

111.1 Overview ..................................................................................................... 111-2 111.2 C902120001 Number of BSC-controlled inter-cell outgoing handover attempts (On SDCCH) ................................................................................................. 111-3 111.3 C902120002 Number of BSC-controlled inter-cell outgoing handover (On SDCCH) ....................................................................................................... 111-4 111.4 C902120003 Number of BSC-controlled inter-cell outgoing handover success (On SDCCH) ................................................................................................. 111-5 111.5 C902120004 Number of MSC-controlled outgoing handover attempts (On SDCCH) ....................................................................................................... 111-6 111.6 C902120005 Number of MSC-controlled outgoing handover request failures due to unclear factors (On SDCCH) ................................................................ 111-7 111.7 C902120006 Number of MSC-controlled outgoing handover request failures due to unavailable radio resource (On SDCCH)............................................... 111-8 111.8 C902120007 Number of MSC-controlled outgoing handover request failures due to other factors (On SDCCH) ................................................................... 111-9 111.9 C902120008 Number of MSC-controlled outgoing handover (On SDCCH)...... 111-10

CLXXXII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

111.10 C902120009 Number of MSC-controlled outgoing handover success (On SDCCH) ..................................................................................................... 111-10 111.11 C902120010 Number of BSC-controlled inter-cell incoming handover attempts (On SDCCH) ................................................................................. 111-11 111.12 C902120011 Number of BSC-controlled inter-cell incoming handover (On SDCCH) ..................................................................................................... 111-12 111.13 C902120012 Number of BSC-controlled incoming handover attempts due to forced release (On SDCCH) ......................................................................... 111-13 111.14 C902120013 Number of BSC-controlled incoming handover due to forced release (On SDCCH) ................................................................................... 111-14 111.15 C902120014 Number of BSC-controlled incoming handover attempts due to queue (On SDCCH)..................................................................................... 111-15 111.16 C902120015 Number of BSC-controlled incoming handover due to queue (On SDCCH) ............................................................................................... 111-16 111.17 C902120016 Number of BSC-controlled incoming handover attempts due to forced handover (On SDCCH) ...................................................................... 111-17 111.18 C902120017 Number of BSC-controlled incoming handover due to forced handover (On SDCCH) ................................................................................ 111-18 111.19 C902120018 Number of BSC-controlled inter-cell incoming handover success (On SDCCH) .................................................................................. 111-19 111.20 C902120019 BSC-controlled incoming handover time due to queue (On SDCCH) ..................................................................................................... 111-19 111.21 C902120020 Number of BSC-controlled incoming handover queue (On SDCCH) ..................................................................................................... 111-21 111.22 C902120021 BSC-controlled incoming handover success time due to queue (On SDCCH) ............................................................................................... 111-22 111.23 C902120022 Number of BSC-controlled incoming handover success due to queue (On SDCCH)..................................................................................... 111-23 111.24 C902120023 Number of MSC-controlled incoming handover attempts (On SDCCH) ..................................................................................................... 111-24 111.25 C902120024 Number of incoming handover failure due to unavailable radio resource (On SDCCH) ................................................................................. 111-25 111.26 C902120025 Number of incoming handover failure due to other factors (On SDCCH) ..................................................................................................... 111-26 111.27 C902120026 Number of MSC-controlled incoming handover (On SDCCH) ..................................................................................................... 111-26 111.28 C902120027 Number of MSC-controlled incoming handover attempts due to forced release (On SDCCH) ......................................................................... 111-27 111.29 C902120028 Number of MSC-controlled incoming handover due to forced release (On SDCCH) ................................................................................... 111-28

CLXXXIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

111.30 C902120029 Number of MSC-controlled incoming handover attempts due to queue (On SDCCH)..................................................................................... 111-29 111.31 C902120030 Number of MSC-controlled incoming handover due to queue (On SDCCH) ............................................................................................... 111-30 111.32 C902120031 Number of MSC-controlled incoming handover attempts due to forced handover (On SDCCH) ...................................................................... 111-31 111.33 C902120032 Number of MSC-controlled incoming handover due to forced handover (On SDCCH) ................................................................................ 111-32 111.34 C902120033 Number of MSC-controlled incoming handover success (On SDCCH) ..................................................................................................... 111-33 111.35 C902120034 MSC-controlled incoming handover time due to queue (On SDCCH) ..................................................................................................... 111-34 111.36 C902120035 Number of MSC-controlled incoming handover queue (On SDCCH) ..................................................................................................... 111-35 111.37 C902120036 MSC-controlled incoming handover success time due to queue (On SDCCH) ............................................................................................... 111-37 111.38 C902120037 Number of MSC-controlled incoming handover success due to queue (On SDCCH)..................................................................................... 111-38

Chapter 112 Local Switch Measurement .............................................. 112-1

112.1 Overview..................................................................................................... 112-1 112.2 C902130001 The Request Number of Local Switch Establish (Inside BSC) ...... 112-2 112.3 C902130002 The Request Number of Local Switch Establish (Inside Site) ...... 112-2 112.4 C902130003 The Request Number of Local Switch Establish (Inside Site Group) .......................................................................................................... 112-3 112.5 C902130004 The Request Number of Local Switch Release (Return Normal Call).............................................................................................................. 112-3 112.6 C902130005 The Failure Number of Establishing Local Switch (Inside BSC/Connect Fail) ......................................................................................... 112-4 112.7 C902130006 The Failure Number of Establishing Local Switch (Inside BSC/Other Reason Fail)................................................................................. 112-5 112.8 C902130007 The Failure Number of Establishing Local Switch (Inside Site/Fail Returned by Site).............................................................................. 112-5 112.9 C902130008 The Failure Number of Establishing Local Switch (Inside Site Group/Fail Returned by Site) .......................................................................... 112-6 112.10 C902130009 The Failure Number of Establishing Local Switch (Inside Site/No answer from Site) .............................................................................. 112-7 112.11 C902130010 The Failure Number of Establishing Local Switch (Inside Site Group/No answer from Site) ........................................................................... 112-8 112.12 C902130011 The Failure Number of Establishing Local Switch (Inside Site/Other Reason Fail).................................................................................. 112-8
CLXXXIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

112.13 C902130012 The Failure Number of Establishing Local Switch (Inside Site Group/Other Reason Fail) .............................................................................. 112-9 112.14 C902130013 The Failure Number of Returning Normal Call (Abis unavailable) .................................................................................................. 112-9 112.15 C902130014 The Failure Number of Returning Normal Call (Connect Fail) ............................................................................................................ 112-10 112.16 C902130015 The Failure Number of Returning Normal Call (Ater unavailable) ................................................................................................ 112-11

Chapter 113 CIR Statistic ....................................................................... 113-1

113.1 C902140001 Uplink Level Grade0 (Above -57 dBm) CIR Normal Grade0 (Below -2 dB) Sample .................................................................................. 113-10 113.2 C902140002 Uplink Level Grade0 (Above -57 dBm) CIR Normal Grade1 (-2 to 0.5 dB) Sample........................................................................................ 113-10 113.3 C902140003 Uplink Level Grade0 (Above -57 dBm) CIR Normal Grade2 (1 to 3.5 dB) Sample ........................................................................................... 113-11 113.4 C902140004 Uplink Level Grade0 (Above -57 dBm) CIR Normal Grade3 (4 to 6.5 dB) Sample ........................................................................................... 113-11 113.5 C902140005 Uplink Level Grade0 (Above -57 dBm) CIR Normal Grade4 (7 to 9.5 dB) Sample ........................................................................................... 113-12 113.6 C902140006 Uplink Level Grade0 (Above -57 dBm) CIR Normal Grade5 (10 to 12.5 dB) Sample ...................................................................................... 113-12 113.7 C902140007 Uplink Level Grade0 (Above -57 dBm) CIR Normal Grade6 (13 to 15.5 dB) Sample ...................................................................................... 113-13 113.8 C902140008 Uplink Level Grade0 (Above -57 dBm) CIR Normal Grade7 (16 to 18.5 dB) Sample ...................................................................................... 113-13 113.9 C902140009 Uplink Level Grade0 (Above -57 dBm) CIR Normal Grade8 (19 to 21.5 dB) Sample ...................................................................................... 113-14 113.10 C902140010 Uplink Level Grade0 (Above -57 dBm) CIR Normal Grade9 (Above 21.5 dB) Sample .............................................................................. 113-14 113.11 C902140011 Uplink Level Grade1 (-57 to -62 dBm) CIR Normal Grade0 (Below -2 dB) Sample .................................................................................. 113-15 113.12 C902140012 Uplink Level Grade1 (-57 to -62 dBm) CIR Normal Grade1 (-2 to 0.5 dB) Sample........................................................................................ 113-15 113.13 C902140013 Uplink Level Grade1 (-57 to -62 dBm) CIR Normal Grade2 (1 to 3.5 dB) Sample........................................................................................ 113-16 113.14 C902140014 Uplink Level Grade1 (-57 to -62 dBm) CIR Normal Grade3 (4 to 6.5 dB) Sample........................................................................................ 113-16 113.15 C902140015 Uplink Level Grade1 (-57 to -62 dBm) CIR Normal Grade4 (7 to 9.5 dB) Sample........................................................................................ 113-17 113.16 C902140016 Uplink Level Grade1 (-57 to -62 dBm) CIR Normal Grade5 (10 to 12.5 dB) Sample ...................................................................................... 113-17
CLXXXV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

113.17 C902140017 Uplink Level Grade1 (-57 to -62 dBm) CIR Normal Grade6 (13 to 15.5 dB) Sample ...................................................................................... 113-18 113.18 C902140018 Uplink Level Grade1 (-57 to -62 dBm) CIR Normal Grade7 (16 to 18.5 dB) Sample ...................................................................................... 113-18 113.19 C902140019 Uplink Level Grade1 (-57 to -62 dBm) CIR Normal Grade8 (19 to 21.5 dB) Sample ...................................................................................... 113-19 113.20 C902140020 Uplink Level Grade1 (-57 to -62 dBm) CIR Normal Grade9 (Above 21.5 dB) Sample .............................................................................. 113-19 113.21 C902140021 Uplink Level Grade2 (-63 to -68 dBm) CIR Normal Grade0 (Below -2 dB) Sample .................................................................................. 113-20 113.22 C902140022 Uplink Level Grade2 (-63 to -68 dBm) CIR Normal Grade1 (-2 to 0.5 dB) Sample........................................................................................ 113-20 113.23 C902140023 Uplink Level Grade2 (-63 to -68 dBm) CIR Normal Grade2 (1 to 3.5 dB) Sample........................................................................................ 113-21 113.24 C902140024 Uplink Level Grade2 (-63 to -68 dBm) CIR Normal Grade3 (4 to 6.5 dB) Sample........................................................................................ 113-21 113.25 C902140025 Uplink Level Grade2 (-63 to -68 dBm) CIR Normal Grade4 (7 to 9.5 dB) Sample........................................................................................ 113-22 113.26 C902140026 Uplink Level Grade2 (-63 to -68 dBm) CIR Normal Grade5 (10 to 12.5 dB) Sample ...................................................................................... 113-22 113.27 C902140027 Uplink Level Grade2 (-63 to -68 dBm) CIR Normal Grade6 (13 to 15.5 dB) Sample ...................................................................................... 113-23 113.28 C902140028 Uplink Level Grade2 (-63 to -68 dBm) CIR Normal Grade7 (16 to 18.5 dB) Sample ...................................................................................... 113-23 113.29 C902140029 Uplink Level Grade2 (-63 to -68 dBm) CIR Normal Grade8 (19 to 21.5 dB) Sample ...................................................................................... 113-24 113.30 C902140030 Uplink Level Grade2 (-63 to -68 dBm) CIR Normal Grade9 (Above 21.5 dB) Sample .............................................................................. 113-24 113.31 C902140031 Uplink Level Grade3 (-69 to -74 dBm) CIR Normal Grade0 (Below -2 dB) Sample .................................................................................. 113-25 113.32 C902140032 Uplink Level Grade3 (-69 to -74 dBm) CIR Normal Grade1 (-2 to 0.5 dB) Sample........................................................................................ 113-25 113.33 C902140033 Uplink Level Grade3 (-69 to -74 dBm) CIR Normal Grade2 (1 to 3.5 dB) Sample........................................................................................ 113-26 113.34 C902140034 Uplink Level Grade3 (-69 to -74 dBm) CIR Normal Grade3 (4 to 6.5 dB) Sample........................................................................................ 113-26 113.35 C902140035 Uplink Level Grade3 (-69 to -74 dBm) CIR Normal Grade4 (7 to 9.5 dB) Sample........................................................................................ 113-27 113.36 C902140036 Uplink Level Grade3 (-69 to -74 dBm) CIR Normal Grade5 (10 to 12.5 dB) Sample ...................................................................................... 113-27

CLXXXVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

113.37 C902140037 Uplink Level Grade3 (-69 to -74 dBm) CIR Normal Grade6 (13 to 15.5 dB) Sample ...................................................................................... 113-28 113.38 C902140038 Uplink Level Grade3 (-69 to -74 dBm) CIR Normal Grade7 (16 to 18.5 dB) Sample ...................................................................................... 113-28 113.39 C902140039 Uplink Level Grade3 (-69 to -74 dBm) CIR Normal Grade8 (19 to 21.5 dB) Sample ...................................................................................... 113-29 113.40 C902140040 Uplink Level Grade3 (-69 to -74 dBm) CIR Normal Grade9 (Above 21.5 dB) Sample .............................................................................. 113-29 113.41 C902140041 Uplink Level Grade4 (-75 to -80 dBm) CIR Normal Grade0 (Below -2 dB) Sample .................................................................................. 113-30 113.42 C902140042 Uplink Level Grade4 (-75 to -80 dBm) CIR Normal Grade1 (-2 to 0.5 dB) Sample........................................................................................ 113-30 113.43 C902140043 Uplink Level Grade4 (-75 to -80 dBm) CIR Normal Grade2 (1 to 3.5 dB) Sample........................................................................................ 113-31 113.44 C902140044 Uplink Level Grade4 (-75 to -80 dBm) CIR Normal Grade3 (4 to 6.5 dB) Sample........................................................................................ 113-31 113.45 C902140045 Uplink Level Grade4 (-75 to -80 dBm) CIR Normal Grade4 (7 to 9.5 dB) Sample........................................................................................ 113-32 113.46 C902140046 Uplink Level Grade4 (-75 to -80 dBm) CIR Normal Grade5 (10 to 12.5 dB) Sample ...................................................................................... 113-32 113.47 C902140047 Uplink Level Grade4 (-75 to -80 dBm) CIR Normal Grade6 (13 to 15.5 dB) Sample ...................................................................................... 113-33 113.48 C902140048 Uplink Level Grade4 (-75 to -80 dBm) CIR Normal Grade7 (16 to 18.5 dB) Sample ...................................................................................... 113-33 113.49 C902140049 Uplink Level Grade4 (-75 to -80 dBm) CIR Normal Grade8 (19 to 21.5 dB) Sample ...................................................................................... 113-34 113.50 C902140050 Uplink Level Grade4 (-75 to -80 dBm) CIR Normal Grade9 (Above 21.5 dB) Sample .............................................................................. 113-34 113.51 C902140051 Uplink Level Grade5 (-81 to -86 dBm) CIR Normal Grade0 (Below -2 dB) Sample .................................................................................. 113-35 113.52 C902140052 Uplink Level Grade5 (-81 to -86 dBm) CIR Normal Grade1 (-2 to 0.5 dB) Sample........................................................................................ 113-35 113.53 C902140053 Uplink Level Grade5 (-81 to -86 dBm) CIR Normal Grade2 (1 to 3.5 dB) Sample........................................................................................ 113-36 113.54 C902140054 Uplink Level Grade5 (-81 to -86 dBm) CIR Normal Grade3 (4 to 6.5 dB) Sample........................................................................................ 113-36 113.55 C902140055 Uplink Level Grade5 (-81 to -86 dBm) CIR Normal Grade4 (7 to 9.5 dB) Sample........................................................................................ 113-37 113.56 C902140056 Uplink Level Grade5 (-81 to -86 dBm) CIR Normal Grade5 (10 to 12.5 dB) Sample ...................................................................................... 113-37

CLXXXVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

113.57 C902140057 Uplink Level Grade5 (-81 to -86 dBm) CIR Normal Grade6 (13 to 15.5 dB) Sample ...................................................................................... 113-38 113.58 C902140058 Uplink Level Grade5 (-81 to -86 dBm) CIR Normal Grade7 (16 to 18.5 dB) Sample ...................................................................................... 113-38 113.59 C902140059 Uplink Level Grade5 (-81 to -86 dBm) CIR Normal Grade8 (19 to 21.5 dB) Sample ...................................................................................... 113-39 113.60 C902140060 Uplink Level Grade5 (-81 to -86 dBm) CIR Normal Grade9 (Above 21.5 dB) Sample .............................................................................. 113-39 113.61 C902140061 Uplink Level Grade6 (-87 to -92 dBm) CIR Normal Grade0 (Below -2 dB) Sample .................................................................................. 113-40 113.62 C902140063 Uplink Level Grade6 (-87 to -92 dBm) CIR Normal Grade2 (1 to 3.5 dB) Sample........................................................................................ 113-40 113.63 C902140064 Uplink Level Grade6 (-87 to -92 dBm) CIR Normal Grade3 (4 to 6.5 dB) Sample........................................................................................ 113-41 113.64 C902140065 Uplink Level Grade6 (-87 to -92 dBm) CIR Normal Grade4 (7 to 9.5 dB) Sample........................................................................................ 113-41 113.65 C902140066 Uplink Level Grade6 (-87 to -92 dBm) CIR Normal Grade5 (10 to 12.5 dB) Sample ...................................................................................... 113-42 113.66 C902140067 Uplink Level Grade6 (-87 to -92 dBm) CIR Normal Grade6 (13 to 15.5 dB) Sample ...................................................................................... 113-42 113.67 C902140068 Uplink Level Grade6 (-87 to -92 dBm) CIR Normal Grade7 (16 to 18.5 dB) Sample ...................................................................................... 113-43 113.68 C902140069 Uplink Level Grade6 (-87 to -92 dBm) CIR Normal Grade8 (19 to 21.5 dB) Sample ...................................................................................... 113-43 113.69 C902140070 Uplink Level Grade6 (-87 to -92 dBm) CIR Normal Grade9 (Above 21.5 dB) Sample .............................................................................. 113-44 113.70 C902140071 Uplink Level Grade7 (-93 to -98 dBm) CIR Normal Grade0 (Below -2 dB) Sample .................................................................................. 113-44 113.71 C902140072 Uplink Level Grade7 (-93 to -98 dBm) CIR Normal Grade1 (-2 to 0.5 dB) Sample........................................................................................ 113-45 113.72 C902140073 Uplink Level Grade7 (-93 to -98 dBm) CIR Normal Grade2 (1 to 3.5 dB) Sample........................................................................................ 113-45 113.73 C902140074 Uplink Level Grade7 (-93 to -98 dBm) CIR Normal Grade3 (4 to 6.5 dB) Sample........................................................................................ 113-46 113.74 C902140075 Uplink Level Grade7 (-93 to -98 dBm) CIR Normal Grade4 (7 to 9.5 dB) Sample........................................................................................ 113-46 113.75 C902140076 Uplink Level Grade7 (-93 to -98 dBm) CIR Normal Grade5 (10 to 12.5 dB) Sample ...................................................................................... 113-47 113.76 C902140077 Uplink Level Grade7 (-93 to -98 dBm) CIR Normal Grade6 (13 to 15.5 dB) Sample ...................................................................................... 113-47

CLXXXVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

113.77 C902140078 Uplink Level Grade7 (-93 to -98 dBm) CIR Normal Grade7 (16 to 18.5 dB) Sample ...................................................................................... 113-48 113.78 C902140079 Uplink Level Grade7 (-93 to -98 dBm) CIR Normal Grade8 (19 to 21.5 dB) Sample ...................................................................................... 113-48 113.79 C902140080 Uplink Level Grade7 (-93 to -98 dBm) CIR Normal Grade9 (Above 21.5 dB) Sample .............................................................................. 113-49 113.80 C902140081 Uplink Level Grade8 (-99 to -104 dBm) CIR Normal Grade0 (Below -2 dB) Sample .................................................................................. 113-49 113.81 C902140082 Uplink Level Grade8 (-99 to -104 dBm) CIR Normal Grade1 (-2 to 0.5 dB) Sample................................................................................... 113-50 113.82 C902140083 Uplink Level Grade8 (-99 to -104 dBm) CIR Normal Grade2 (1 to 3.5 dB) Sample........................................................................................ 113-50 113.83 C902140084 Uplink Level Grade8 (-99 to -104 dBm) CIR Normal Grade3 (4 to 6.5 dB) Sample........................................................................................ 113-51 113.84 C902140085 Uplink Level Grade8 (-99 to -104 dBm) CIR Normal Grade4 (7 to 9.5 dB) Sample........................................................................................ 113-51 113.85 C902140086 Uplink Level Grade8 (-99 to -104 dBm) CIR Normal Grade5 (10 to 12.5 dB) Sample ................................................................................ 113-52 113.86 C902140087 Uplink Level Grade8 (-99 to -104 dBm) CIR Normal Grade6 (13 to 15.5 dB) Sample ................................................................................ 113-52 113.87 C902140088 Uplink Level Grade8 (-99 to -104 dBm) CIR Normal Grade7 (16 to 18.5 dB) Sample ................................................................................ 113-53 113.88 C902140089 Uplink Level Grade8 (-99 to -104 dBm) CIR Normal Grade8 (19 to 21.5 dB) Sample ................................................................................ 113-53 113.89 C902140090 Uplink Level Grade8 (-99 to -104 dBm) CIR Normal Grade9 (Above 21.5 dB) Sample .............................................................................. 113-54 113.90 C902140091 Uplink Level Grade9 (Below -104 dBm) CIR Normal Grade0 (Below -2 dB) Sample .................................................................................. 113-54 113.91 C902140092 Uplink Level Grade9 (Below -104 dBm) CIR Normal Grade1 (-2 to 0.5 dB) Sample................................................................................... 113-55 113.92 C902140093 Uplink Level Grade9 (Below -104 dBm) CIR Normal Grade2 (1 to 3.5 dB) Sample........................................................................................ 113-55 113.93 C902140094 Uplink Level Grade9 (Below -104 dBm) CIR Normal Grade3 (4 to 6.5 dB) Sample........................................................................................ 113-56 113.94 C902140095 Uplink Level Grade9 (Below -104 dBm) CIR Normal Grade4 (7 to 9.5 dB) Sample........................................................................................ 113-56 113.95 C902140096 Uplink Level Grade9 (Below -104 dBm) CIR Normal Grade5 (10 to 12.5 dB) Sample ................................................................................ 113-57 113.96 C902140097 Uplink Level Grade9 (Below -104 dBm) CIR Normal Grade6 (13 to 15.5 dB) Sample ................................................................................ 113-57

CLXXXIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

113.97 C902140098 Uplink Level Grade9 (Below -104 dBm) CIR Normal Grade7 (16 to 18.5 dB) Sample ................................................................................ 113-58 113.98 C902140099 Uplink Level Grade9 (Below -104 dBm) CIR Normal Grade8 (19 to 21.5 dB) Sample ................................................................................ 113-58 113.99 C902140100 Uplink Level Grade9 (Below -104 dBm) CIR Normal Grade9 (Above 21.5 dB) Sample .............................................................................. 113-59 113.100 C902140101 Uplink Level Grade0 (Above -57 dBm) CIR Improved Grade0 (Below -2 dB) Sample .................................................................................. 113-59 113.101 C902140102 Uplink Level Grade0 (Above -57 dBm) CIR Improved Grade1 (-2 to 0.5 dB) Sample................................................................................... 113-60 113.102 C902140103 Uplink Level Grade0 (Above -57 dBm) CIR Improved Grade2 (1 to 3.5 dB) Sample .................................................................................... 113-60 113.103 C902140104 Uplink Level Grade0 (Above -57 dBm) CIR Improved Grade3 (4 to 6.5 dB) Sample .................................................................................... 113-61 113.104 C902140105 Uplink Level Grade0 (Above -57 dBm) CIR Improved Grade4 (7 to 9.5 dB) Sample .................................................................................... 113-61 113.105 C902140106 Uplink Level Grade0 (Above -57 dBm) CIR Improved Grade5 (10 to 12.5 dB) Sample ................................................................................ 113-62 113.106 C902140107 Uplink Level Grade0 (Above -57 dBm) CIR Improved Grade6 (13 to 15.5 dB) Sample ................................................................................ 113-62 113.107 C902140108 Uplink Level Grade0 (Above -57 dBm) CIR Improved Grade7 (16 to 18.5 dB) Sample ................................................................................ 113-63 113.108 C902140109 Uplink Level Grade0 (Above -57 dBm) CIR Improved Grade8 (19 to 21.5 dB) Sample ................................................................................ 113-63 113.109 C902140110 Uplink Level Grade0 (Above -57 dBm) CIR Improved Grade9 (Above 21.5 dB) Sample .............................................................................. 113-64 113.110 C902140111 Uplink Level Grade1 (-57 to -62 dBm) CIR Improved Grade0 (Below -2 dB) Sample .................................................................................. 113-64 113.111 C902140112 Uplink Level Grade1 (-57 to -62 dBm) CIR Improved Grade1 (-2 to 0.5 dB) Sample................................................................................... 113-65 113.112 C902140113 Uplink Level Grade1 (-57 to -62 dBm) CIR Improved Grade2 (1 to 3.5 dB) Sample .................................................................................... 113-65 113.113 C902140114 Uplink Level Grade1 (-57 to -62 dBm) CIR Improved Grade3 (4 to 6.5 dB) Sample .................................................................................... 113-66 113.114 C902140115 Uplink Level Grade1 (-57 to -62 dBm) CIR Improved Grade4 (7 to 9.5 dB) Sample .................................................................................... 113-66 113.115 C902140116 Uplink Level Grade1 (-57 to -62 dBm) CIR Improved Grade5 (10 to 12.5 dB) Sample ................................................................................ 113-67 113.116 C902140117 Uplink Level Grade1 (-57 to -62 dBm) CIR Improved Grade6 (13 to 15.5 dB) Sample ................................................................................ 113-67

CXC SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

113.117 C902140118 Uplink Level Grade1 (-57 to -62 dBm) CIR Improved Grade7 (16 to 18.5 dB) Sample ................................................................................ 113-68 113.118 C902140119 Uplink Level Grade1 (-57 to -62 dBm) CIR Improved Grade8 (19 to 21.5 dB) Sample ................................................................................ 113-68 113.119 C902140120 Uplink Level Grade1 (-57 to -62 dBm) CIR Improved Grade9 (Above 21.5 dB) Sample .............................................................................. 113-69 113.120 C902140121 Uplink Level Grade2 (-63 to -68 dBm) CIR Improved Grade0 (Below -2 dB) Sample .................................................................................. 113-69 113.121 C902140122 Uplink Level Grade2 (-63 to -68 dBm) CIR Improved Grade1 (-2 to 0.5 dB) Sample................................................................................... 113-70 113.122 C902140123 Uplink Level Grade2 (-63 to -68 dBm) CIR Improved Grade2 (1 to 3.5 dB) Sample .................................................................................... 113-70 113.123 C902140124 Uplink Level Grade2 (-63 to -68 dBm) CIR Improved Grade3 (4 to 6.5 dB) Sample .................................................................................... 113-71 113.124 C902140125 Uplink Level Grade2 (-63 to -68 dBm) CIR Improved Grade4 (7 to 9.5 dB) Sample .................................................................................... 113-71 113.125 C902140126 Uplink Level Grade2 (-63 to -68 dBm) CIR Improved Grade5 (10 to 12.5 dB) Sample ................................................................................ 113-72 113.126 C902140127 Uplink Level Grade2 (-63 to -68 dBm) CIR Improved Grade6 (13 to 15.5 dB) Sample ................................................................................ 113-72 113.127 C902140128 Uplink Level Grade2 (-63 to -68 dBm) CIR Improved Grade7 (16 to 18.5 dB) Sample ................................................................................ 113-73 113.128 C902140129 Uplink Level Grade2 (-63 to -68 dBm) CIR Improved Grade8 (-19 to 21.5 dB) Sample ............................................................................... 113-73 113.129 C902140130 Uplink Level Grade2 (-63 to -68 dBm) CIR Improved Grade9 (Above 21.5 dB) Sample .............................................................................. 113-74 113.130 C902140131 Uplink Level Grade3 (-69 to -74 dBm) CIR Improved Grade0 (Below -2 dB) Sample .................................................................................. 113-74 113.131 C902140132 Uplink Level Grade3 (-69 to -74 dBm) CIR Improved Grade1 (-2 to 0.5 dB) Sample................................................................................... 113-75 113.132 C902140133 Uplink Level Grade3 (-69 to -74 dBm) CIR Improved Grade2 (1 to 3.5 dB) Sample .................................................................................... 113-75 113.133 C902140134 Uplink Level Grade3 (-69 to -74 dBm) CIR Improved Grade3 (4 to 6.5 dB) Sample .................................................................................... 113-76 113.134 C902140135 Uplink Level Grade3 (-69 to -74 dBm) CIR Improved Grade4 (7 to 9.5 dB) Sample .................................................................................... 113-76 113.135 C902140136 Uplink Level Grade3 (-69 to -74 dBm) CIR Improved Grade5 (10 to 12.5 dB) Sample ................................................................................ 113-77 113.136 C902140137 Uplink Level Grade3 (-69 to -74 dBm) CIR Improved Grade6 (13 to 15.5 dB) Sample ................................................................................ 113-77

CXCI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

113.137 C902140138 Uplink Level Grade3 (-69 to -74 dBm) CIR Improved Grade7 (16 to 18.5 dB) Sample ................................................................................ 113-78 113.138 C902140139 Uplink Level Grade3 (-69 to -74 dBm) CIR Improved Grade8 (19 to 21.5 dB) Sample ................................................................................ 113-78 113.139 C902140140 Uplink Level Grade3 (-69 to -74 dBm) CIR Improved Grade9 (Above 21.5 dB) Sample .............................................................................. 113-79 113.140 C902140141 Uplink Level Grade4 (-75 to -80 dBm) CIR Improved Grade0 (Below -2 dB) Sample .................................................................................. 113-79 113.141 C902140142 Uplink Level Grade4 (-75 to -80 dBm) CIR Improved Grade1 (-2 to 0.5 dB) Sample................................................................................... 113-80 113.142 C902140143 Uplink Level Grade4 (-75 to -80 dBm) CIR Improved Grade2 (1 to 3.5 dB) Sample .................................................................................... 113-80 113.143 C902140144 Uplink Level Grade4 (-75 to -80 dBm) CIR Improved Grade3 (4 to 6.5 dB) Sample .................................................................................... 113-81 113.144 C902140145 Uplink Level Grade4 (-75 to -80 dBm) CIR Improved Grade4 (7 to 9.5 dB) Sample .................................................................................... 113-81 113.145 C902140146 Uplink Level Grade4 (-75 to -80 dBm) CIR Improved Grade5 (10 to 12.5 dB) Sample ................................................................................ 113-82 113.146 C902140147 Uplink Level Grade4 (-75 to -80 dBm) CIR Improved Grade6 (13 to 15.5 dB) Sample ................................................................................ 113-82 113.147 C902140148 Uplink Level Grade4 (-75 to -80 dBm) CIR Improved Grade72 (16 to 18.5 dB) Sample ................................................................................ 113-83 113.148 C902140149 Uplink Level Grade4 (-75 to -80 dBm) CIR Improved Grade8 (19 to 21.5 dB) Sample ................................................................................ 113-83 113.149 C902140150 Uplink Level Grade4 (-75 to -80 dBm) CIR Improved Grade9 (Above 21.5 dB) Sample .............................................................................. 113-84 113.150 C902140151 Uplink Level Grade5 (-81 to -86 dBm) CIR Improved Grade0 (Below -2 dB) Sample .................................................................................. 113-84 113.151 C902140152 Uplink Level Grade5 (-81 to -86 dBm) CIR Improved Grade1 (-2 to 0.5 dB) Sample................................................................................... 113-85 113.152 C902140153 Uplink Level Grade5 (-81 to -86 dBm) CIR Improved Grade2 (1 to 3.5 dB) Sample .................................................................................... 113-85 113.153 C902140154 Uplink Level Grade5 (-81 to -86 dBm) CIR Improved Grade3 (4 to 6.5 dB) Sample .................................................................................... 113-86 113.154 C902140155 Uplink Level Grade5 (-81 to -86 dBm) CIR Improved Grade4 (7 to 9.5 dB) Sample .................................................................................... 113-86 113.155 C902140156 Uplink Level Grade5 (-81 to -86 dBm) CIR Improved Grade5 (10 to 12.5 dB) Sample ................................................................................ 113-87 113.156 C902140157 Uplink Level Grade5 (-81 to -86 dBm) CIR Improved Grade6 (13 to 15.5 dB) Sample ................................................................................ 113-87

CXCII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

113.157 C902140158 Uplink Level Grade5 (-81 to -86 dBm) CIR Improved Grade7 (16 to 18.5 dB) Sample ................................................................................ 113-88 113.158 C902140159 Uplink Level Grade5 (-81 to -86 dBm) CIR Improved Grade8 (19 to 21.5 dB) Sample ................................................................................ 113-88 113.159 C902140160 Uplink Level Grade5 (-81 to -86 dBm) CIR Improved Grade9 (Above 21.5 dB) Sample .............................................................................. 113-89 113.160 C902140161 Uplink Level Grade6 (-87 to -92 dBm) CIR Improved Grade0 (Below -2 dB) Sample .................................................................................. 113-89 113.161 C902140162 Uplink Level Grade6 (-87 to -92 dBm) CIR Improved Grade1 (-2 to 0.5 dB) Sample................................................................................... 113-90 113.162 C902140163 Uplink Level Grade6 (-87 to -92 dBm) CIR Improved Grade2 (1 to 3.5 dB) Sample .................................................................................... 113-90 113.163 C902140164 Uplink Level Grade6 (-87 to -92 dBm) CIR Improved Grade3 (4 to 6.5 dB) Sample .................................................................................... 113-91 113.164 C902140165 Uplink Level Grade6 (-87 to -92 dBm) CIR Improved Grade4 (7 to 9.5 dB) Sample .................................................................................... 113-91 113.165 C902140166 Uplink Level Grade6 (-87 to -92 dBm) CIR Improved Grade5 (10 to 12.5 dB) Sample ................................................................................ 113-92 113.166 C902140167 Uplink Level Grade6 (-87 to -92 dBm) CIR Improved Grade6 (13 to 15.5 dB) Sample ................................................................................ 113-92 113.167 C902140168 Uplink Level Grade6 (-87 to -92 dBm) CIR Improved Grade7 (16 to 18.5 dB) Sample ................................................................................ 113-93 113.168 C902140169 Uplink Level Grade6 (-87 to -92 dBm) CIR Improved Grade8 (19 to 21.5 dB) Sample ................................................................................ 113-93 113.169 C902140170 Uplink Level Grade6 (-87 to -92 dBm) CIR Improved Grade9 (Above 21.5 dB) Sample .............................................................................. 113-94 113.170 C902140171 Uplink Level Grade7 (-93 to -98 dBm) CIR Improved Grade0 (Below -2 dB) Sample .................................................................................. 113-94 113.171 C902140172 Uplink Level Grade7 (-93 to -98 dBm) CIR Improved Grade1 (-2 to 0.5 dB) Sample................................................................................... 113-95 113.172 C902140173 Uplink Level Grade7 (-93 to -98 dBm) CIR Improved Grade2 (1 to 3.5 dB) Sample .................................................................................... 113-95 113.173 C902140174 Uplink Level Grade7 (-93 to -98 dBm) CIR Improved Grade3 (4 to 6.5 dB) Sample .................................................................................... 113-96 113.174 C902140175 Uplink Level Grade7 (-93 to -98 dBm) CIR Improved Grade4 (7 to 9.5 dB) Sample .................................................................................... 113-96 113.175 C902140176 Uplink Level Grade7 (-93 to -98 dBm) CIR Improved Grade5 (10 to 12.5 dB) Sample ................................................................................ 113-97 113.176 C902140177 Uplink Level Grade7 (-93 to -98 dBm) CIR Improved Grade6 (13 to 15.5 dB) Sample ................................................................................ 113-97

CXCIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

113.177 C902140178 Uplink Level Grade7 (-93 to -98 dBm) CIR Improved Grade7 (16 to 18.5 dB) Sample ................................................................................ 113-98 113.178 C902140179 Uplink Level Grade7 (-93 to -98 dBm) CIR Improved Grade8 (19 to 21.5 dB) Sample ................................................................................ 113-98 113.179 C902140180 Uplink Level Grade7 (-93 to -98 dBm) CIR Improved Grade9 (Above 21.5 dB) Sample .............................................................................. 113-99 113.180 C902140181 Uplink Level Grade8 (-99 to -104 dBm) CIR Improved Grade0 (Below -2 dB) Sample .................................................................................. 113-99 113.181 C902140182 Uplink Level Grade8 (-99 to -104 dBm) CIR Improved Grade1 (-2 to 0.5 dB) Sample................................................................................. 113-100 113.182 C902140183 Uplink Level Grade8 (-99 to -104 dBm) CIR Improved Grade2 (1 to 3.5 dB) Sample .................................................................................. 113-100 113.183 C902140184 Uplink Level Grade8 (-99 to -104 dBm) CIR Improved Grade3 (4 to 6.5 dB) Sample .................................................................................. 113-101 113.184 C902140185 Uplink Level Grade8 (-99 to -104 dBm) CIR Improved Grade4 (7 to 9.5 dB) Sample .................................................................................. 113-101 113.185 C902140186 Uplink Level Grade8 (-99 to -104 dBm) CIR Improved Grade5 (10 to 12.5 dB) Sample .............................................................................. 113-102 113.186 C902140187 Uplink Level Grade8 (-99 to -104 dBm) CIR Improved Grade6 (13 to 15.5 dB) Sample .............................................................................. 113-102 113.187 C902140188 Uplink Level Grade8 (-99 to -104 dBm) CIR Improved Grade7 (16 to 18.5 dB) Sample .............................................................................. 113-103 113.188 C902140189 Uplink Level Grade8 (-99 to -104 dBm) CIR Improved Grade8 (19 to 21.5 dB) Sample .............................................................................. 113-103 113.189 C902140190 Uplink Level Grade8 (-99 to -104 dBm) CIR Improved Grade9 (Above 21.5 dB) Sample ............................................................................ 113-104 113.190 C902140191 Uplink Level Grade9 (Below -104 dBm) CIR Improved Grade0 (Below -2 dB) Sample .................................................................... 113-104 113.191 C902140192 Uplink Level Grade9 (Below -104 dBm) CIR Improved Grade1 (-2 to 0.5 dB) Sample..................................................................... 113-105 113.192 C902140193 Uplink Level Grade9 (Below -104 dBm) CIR Improved Grade2 (1 to 3.5 dB) Sample ...................................................................... 113-105 113.193 C902140194 Uplink Level Grade9 (Below -104 dBm) CIR Improved Grade3 (4 to 6.5 dB) Sample ...................................................................... 113-106 113.194 C902140195 Uplink Level Grade9 (Below -104 dBm) CIR Improved Grade4 (7 to 9.5 dB) Sample ...................................................................... 113-106 113.195 C902140196 Uplink Level Grade9 (Below -104 dBm) CIR Improved Grade5 (10 to 12.5 dB) Sample .................................................................. 113-107 113.196 C902140197 Uplink Level Grade9 (Below -104 dBm) CIR Improved Grade6 (13 to 15.5 dB) Sample .................................................................. 113-107

CXCIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

113.197 C902140198 Uplink Level Grade9 (Below -104 dBm) CIR Improved Grade7 (16 to 18.5 dB) Sample .................................................................. 113-108 113.198 C902140199 Uplink Level Grade9 (Below -104 dBm) CIR Improved Grade8 (19 to 21.5 dB) Sample .................................................................. 113-108 113.199 C902140200 Uplink Level Grade9 (Below -104 dBm) CIR Improved Grade9 (Above 21.5 dB) Sample ................................................................ 113-109

Chapter 114 BTS PS Statistic ................................................................ 114-1

114.1 C902150001 Number of Uplink PCU Block in BTS ......................................... 114-1 114.2 C902150002 Number of Downlink PCU Block in BTS..................................... 114-2 114.3 C902150003 Number of UIR Attempt Block ................................................... 114-2 114.4 C902150004 Number of UIR Success Block.................................................. 114-2 114.5 C902150005 Number of Error Downlink BN................................................... 114-3 114.6 C902150006 Number of USF Valid Block in BTS ........................................... 114-3 114.7 C902150007 RRBP Valid Number of Data Block in BTS................................. 114-4 114.8 C902150008 RRBP Valid Number of Control Block in BTS ............................. 114-4 114.9 C902150009 Number of Access Burst Indication in BTS................................. 114-5

Chapter 115 TRX Key PS Information Statistic.................................... 115-1

115.1 C902160001 The Number of Uplink PCU Frame in PCU ................................ 115-1 115.2 C902160002 The Number of Downlink PCU Frame in PCU ............................ 115-2 115.3 C902160003 The Number of USF Valid Downlink Block in PCU...................... 115-2 115.4 C902160004 The Number of RRBP Valid Downlink Data Blocks in PCU ......... 115-3 115.5 C902160005 The Number of RRBP Valid Downlink Control Blocks in PCU ...... 115-3 115.6 C902160006 The Number of Downlink Blocks Including Acess Bust Indication in PCU .......................................................................................................... 115-4

Chapter 116 PS Uplink Radio Quality Statistic Measurement ............ 116-1

116.1 C902170001 Unsuccessfully decode times of uplink block indicated with valid USF, while power level is lower than threshold .............................................. 116-6 116.2 C902170002 Unsuccessfully decode times of uplink block indicated with valid USF, whilepower level is higher than threshold and all of 4 bursts are demoded successfully................................................................................... 116-6 116.3 C902170003 Unsuccessfully decode times of uplink block indicated with valid USF, whilepower level is higher than threshold and not all of 4 burst are demoded successful ..................................................................................... 116-7 116.4 C902170004 Unsuccessfully decode times of Downlink Ack Message,while power level is lower than threshold ............................................................... 116-7 116.5 C902170005 Unsuccessfully decode times of "Downlink Ack Message" while "power level is higher than threshold and all of 4 burst are demoded successful".................................................................................................... 116-8

CXCV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

116.6 C902170006 Unsuccessfully decode times of "Downlink Ack Message", while "power level is higher than threshold and not all of 4 bursts are demoded successful".................................................................................................... 116-9 116.7 C902170007 Unsuccessfully decode times of "Downlink Ack Message", while "burst type is inconsistent".............................................................................. 116-9 116.8 C902170008 Unsuccessfully decode times of "NB Control Ack", while "power level is lower than threshold" ........................................................................ 116-10 116.9 C902170009 Unsuccessfully decode times of "NB Control Ack Message", while "power level is higher than threshold and all of 4 burst are demoded successful".................................................................................................. 116-10 116.10 C902170010 Unsuccessfully decode times of "NB Control Ack Message", while "power level is higher than threshold and not all of 4 burst are demoded successful".................................................................................................. 116-11 116.11 C902170011 Unsuccessfully decode times of "NB Control Ack Message", while "burst type is inconsistent" ................................................................... 116-12 116.12 C902170012 Unsuccessfully decode times of "AB Control Ack", while "power level is lower than threshold" ............................................................. 116-12 116.13 C902170013 Unsuccessfully decode times of "AB Control Ack Message", while "power level is higher than threshold and all of 4 bursts are demoded successful".................................................................................................. 116-13 116.14 C902170014 Unsuccessfully decode times of "AB Control Ack Message", while "power level is higher than threshold and not all of 4 bursts are demoded successful".................................................................................................. 116-13 116.15 C902170015 Unsuccessfully decode times of "AB Control Ack Message", while "burst type is inconsistent" ................................................................... 116-14 116.16 C902170016 Unsuccessfully decode times of "Single Block", while "power level is lower than threshold" ........................................................................ 116-15 116.17 C902170017 Unsuccessfully decode times of "single block", while "power level is higher than threshold and all of 4 burst are demoded successful" ........ 116-15 116.18 C902170018 Unsuccessfully decode times of "single block", while "power level is higher than threshold and not all of 4 bursts are demoded successful".................................................................................................. 116-16 116.19 C902170019 Unsuccessfully decode times of "single block", while "burst type is inconsistent" ..................................................................................... 116-16 116.20 C902170020 Number of GMSK MEAN BEP=0 Uplink Blocks...................... 116-17 116.21 C902170021 Number of GMSK MEAN BEP=1 Uplink Blocks...................... 116-17 116.22 C902170022 Number of GMSK MEAN BEP=2 Uplink Blocks...................... 116-18 116.23 C902170023 Number of GMSK MEAN BEP=3 Uplink Blocks...................... 116-19 116.24 C902170024 Number of GMSK MEAN BEP=4 Uplink Blocks...................... 116-19 116.25 C902170025 Number of GMSK MEAN BEP=5 Uplink Blocks...................... 116-20 116.26 C902170026 Number of GMSK MEAN BEP=6 Uplink Blocks...................... 116-20
CXCVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

116.27 C902170027 Number of GMSK MEAN BEP=7 Uplink Blocks...................... 116-21 116.28 C902170028 Number of GMSK MEAN BEP=8 Uplink Blocks...................... 116-21 116.29 C902170029 Number of GMSK MEAN BEP=9 Uplink Blocks...................... 116-22 116.30 C902170030 Number of GMSK MEAN BEP=10 Uplink Blocks.................... 116-22 116.31 C902170031 Number of GMSK MEAN BEP=11 Uplink Blocks .................... 116-23 116.32 C902170032 Number of GMSK MEAN BEP=12 Uplink Blocks.................... 116-23 116.33 C902170033 Number of GMSK MEAN BEP=13 Uplink Blocks.................... 116-24 116.34 C902170034 Number of GMSK MEAN BEP=14 Uplink Blocks.................... 116-25 116.35 C902170035 Number of GMSK MEAN BEP=15 Uplink Blocks.................... 116-25 116.36 C902170036 Number of GMSK MEAN BEP=16 Uplink Blocks.................... 116-26 116.37 C902170037 Number of GMSK MEAN BEP=17 Uplink Blocks.................... 116-26 116.38 C902170038 Number of GMSK MEAN BEP=18 Uplink Blocks.................... 116-27 116.39 C902170039 Number of GMSK MEAN BEP=19 Uplink Blocks.................... 116-27 116.40 C902170040 Number of GMSK MEAN BEP=20 Uplink Blocks.................... 116-28 116.41 C902170041 Number of GMSK MEAN BEP=21 Uplink Blocks.................... 116-28 116.42 C902170042 Number of GMSK MEAN BEP=22 Uplink Blocks.................... 116-29 116.43 C902170043 Number of GMSK MEAN BEP=23 Uplink Blocks.................... 116-29 116.44 C902170044 Number of GMSK MEAN BEP=24 Uplink Blocks.................... 116-30 116.45 C902170045 Number of GMSK MEAN BEP=25 Uplink Blocks.................... 116-31 116.46 C902170046 Number of GMSK MEAN BEP=26 Uplink Blocks.................... 116-31 116.47 C902170047 Number of GMSK MEAN BEP=27 Uplink Blocks.................... 116-32 116.48 C902170048 Number of GMSK MEAN BEP=28 Uplink Blocks.................... 116-32 116.49 C902170049 Number of GMSK MEAN BEP=29 Uplink Blocks.................... 116-33 116.50 C902170050 Number of GMSK MEAN BEP=30 Uplink Blocks.................... 116-33 116.51 C902170051 Number of GMSK MEAN BEP=31 Uplink Blocks.................... 116-34 116.52 C902170053 Number of GMSK CV BEP=1 Uplink Blocks........................... 116-34 116.53 C902170054 Number of GMSK CV BEP=2 Uplink Blocks........................... 116-35 116.54 C902170055 Number of GMSK CV BEP=3 Uplink Blocks........................... 116-35 116.55 C902170056 Number of GMSK CV BEP=4 Uplink Blocks........................... 116-36 116.56 C902170057 Number of GMSK CV BEP=5 Uplink Blocks........................... 116-37 116.57 C902170058 Number of GMSK CV BEP=6 Uplink Blocks........................... 116-37 116.58 C902170059 Number of GMSK CV BEP=7 Uplink Blocks........................... 116-38 116.59 C902170060 Number of 8PSK MEAN BEP=0 Uplink Blocks ....................... 116-38 116.60 C902170061 Number of 8PSK MEAN BEP=1 Uplink Blocks ....................... 116-39 116.61 C902170062 Number of 8PSK MEAN BEP=2 Uplink Blocks ....................... 116-39 116.62 C902170063 Number of 8PSK MEAN BEP=3 Uplink Blocks ....................... 116-40 116.63 C902170064 Number of 8PSK MEAN BEP=4 Uplink Blocks ....................... 116-40

CXCVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

116.64 C902170065 Number of 8PSK MEAN BEP=5 Uplink Blocks ....................... 116-41 116.65 C902170066 Number of 8PSK MEAN BEP=6 Uplink Blocks ....................... 116-41 116.66 C902170067 Number of 8PSK MEAN BEP=7 Uplink Blocks ....................... 116-42 116.67 C902170068 Number of 8PSK MEAN BEP=8 Uplink Blocks ....................... 116-43 116.68 C902170069 Number of 8PSK MEAN BEP=9 Uplink Blocks ....................... 116-43 116.69 C902170070 Number of 8PSK MEAN BEP=10 Uplink Blocks ..................... 116-44 116.70 C902170071 Number of 8PSK MEAN BEP=11 Uplink Blocks ..................... 116-44 116.71 C902170072 Number of 8PSK MEAN BEP=12 Uplink Blocks ..................... 116-45 116.72 C902170073 Number of 8PSK MEAN BEP=13 Uplink Blocks ..................... 116-45 116.73 C902170074 Number of 8PSK MEAN BEP=14 Uplink Blocks ..................... 116-46 116.74 C902170075 Number of 8PSK MEAN BEP=15 Uplink Blocks ..................... 116-46 116.75 C902170076 Number of 8PSK MEAN BEP=16 Uplink Blocks ..................... 116-47 116.76 C902170077 Number of 8PSK MEAN BEP=17 Uplink Blocks ..................... 116-47 116.77 C902170078 Number of 8PSK MEAN BEP=18 Uplink Blocks ..................... 116-48 116.78 C902170079 Number of 8PSK MEAN BEP=19 Uplink Blocks ..................... 116-49 116.79 C902170080 Number of 8PSK MEAN BEP=20 Uplink Blocks ..................... 116-49 116.80 C902170081 Number of 8PSK MEAN BEP=21 Uplink Blocks ..................... 116-50 116.81 C902170082 Number of 8PSK MEAN BEP=22 Uplink Blocks ..................... 116-50 116.82 C902170083 Number of 8PSK MEAN BEP=23 Uplink Blocks ..................... 116-51 116.83 C902170084 Number of 8PSK MEAN BEP=24 Uplink Blocks ..................... 116-51 116.84 C902170085 Number of 8PSK MEAN BEP=25 Uplink Blocks ..................... 116-52 116.85 C902170086 Number of 8PSK MEAN BEP=26 Uplink Blocks ..................... 116-52 116.86 C902170087 Number of 8PSK MEAN BEP=27 Uplink Blocks ..................... 116-53 116.87 C902170088 Number of 8PSK MEAN BEP=28 Uplink Blocks ..................... 116-53 116.88 C902170089 Number of 8PSK MEAN BEP=29 Uplink Blocks ..................... 116-54 116.89 C902170090 Number of 8PSK MEAN BEP=30 Uplink Blocks ..................... 116-55 116.90 C902170091 Number of 8PSK MEAN BEP=31 Uplink Blocks ..................... 116-55 116.91 C902170092 Number of 8PSK CV BEP=0 Uplink Blocks ............................ 116-56 116.92 C902170093 Number of 8PSK CV BEP=1 Uplink Blocks ............................ 116-56 116.93 C902170094 Number of 8PSK CV BEP=2 Uplink Blocks ............................ 116-57 116.94 C902170095 Number of 8PSK CV BEP=3 Uplink Blocks ............................ 116-57 116.95 C902170096 Number of 8PSK CV BEP=4 Uplink Blocks ............................ 116-58 116.96 C902170097 Number of 8PSK CV BEP=5 Uplink Blocks ............................ 116-58 116.97 C902170098 Number of 8PSK CV BEP=6 Uplink Blocks ............................ 116-59 116.98 C902170099 Number of 8PSK CV BEP=7 Uplink Blocks ............................ 116-59 116.99 C902170100 Summation of uplink blocks C_Value .................................... 116-60 116.100 C902170101 Number of uplink blocks' C_Value samples .......................... 116-60

CXCVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

116.101 C902170102 Average UL GMSK Mean-Bep of C-Value From 0 to 10 ........ 116-61 116.102 C902170103 Average UL 8PSK Mean-Bep of C-Value From 0 to 10 ......... 116-62 116.103 C902170104 Average UL GMSK Mean-Bep of C-Value From 11 to 15 ...... 116-62 116.104 C902170105 Average UL 8PSK Mean-Bep of C-Value From 11 to 15........ 116-63 116.105 C902170106 Average UL GMSK Mean-Bep of C-Value From 16 to 20 ...... 116-63 116.106 C902170107 Average UL 8PSK Mean-Bep of C-Value From 16 to 20........ 116-64 116.107 C902170108 Average UL GMSK Mean-Bep of C-Value From 21 to 30 ...... 116-65 116.108 C902170109 Average UL 8PSK Mean-Bep of C-Value From 21 to 30........ 116-65 116.109 C902170110 Average UL GMSK Mean-Bep of C-Value From 31 to 40 ...... 116-66 116.110 C902170111 Average UL 8PSK Mean-Bep of C-Value From 31 to 40 ........ 116-67 116.111 C902170112 Average UL GMSK Mean-Bep of C-Value From 41 to 63 ....... 116-67 116.112 C902170113 Average UL 8PSK Mean-Bep of C-Value From 41 to 63 ........ 116-68 116.113 C902170114 Average UL GMSK Mean-Bep of TA-Value 0 ........................ 116-68 116.114 C902170115 Average UL 8PSK Mean-Bep of TA-Value 0 ......................... 116-69 116.115 C902170116 Average UL GMSK Mean-Bep of TA-Value 1 ........................ 116-70 116.116 C902170117 Average UL 8PSK Mean-Bep of TA-Value 1 ......................... 116-70 116.117 C902170118 Average UL GMSK Mean-Bep of TA-Value 2 ........................ 116-71 116.118 C902170119 Average UL GMSK Mean-Bep of TA-Value 2 ........................ 116-71 116.119 C902170120 Average UL GMSK Mean-Bep of TA-Value 3........................ 116-72 116.120 C902170121 Average UL 8PSK Mean-Bep of TA-Value 3......................... 116-72 116.121 C902170122 Average UL GMSK Mean-Bep of TA-Value 4........................ 116-73 116.122 C902170123 Average UL 8PSK Mean-Bep of TA-Value 4......................... 116-74 116.123 C902170124 Average UL GMSK Mean-Bep of TA-Value 5........................ 116-74 116.124 C902170125 Average UL 8PSK Mean-Bep of TA-Value 5......................... 116-75 116.125 C902170126 Average UL GMSK Mean-Bep of TA-Value 6........................ 116-75 116.126 C902170127 Average UL 8PSK Mean-Bep of TA-Value 6......................... 116-76 116.127 C902170128 Average UL GMSK Mean-Bep of TA-Value 7........................ 116-76 116.128 C902170129 Average UL 8PSK Mean-Bep of TA-Value 7......................... 116-77 116.129 C902170130 Average UL GMSK Mean-Bep of TA-Value 8........................ 116-78 116.130 C902170131 Average UL 8PSK Mean-Bep of TA-Value 8......................... 116-78 116.131 C902170132 Average UL GMSK Mean-Bep of TA-Value 9........................ 116-79 116.132 C902170133 Average UL 8PSK Mean-Bep of TA-Value 9......................... 116-79 116.133 C902170134 Average UL GMSK Mean-Bep of TA-Value 10...................... 116-80 116.134 C902170135 Average UL 8PSK Mean-Bep of TA-Value 10 ....................... 116-80 116.135 C902170136 Average UL GMSK Mean-Bep of TA-Value 11 ...................... 116-81 116.136 C902170137 Average UL 8PSK Mean-Bep of TA-Value 11 ....................... 116-82 116.137 C902170138 Average UL GMSK Mean-Bep of TA-Value From 12 to 13...... 116-82

CXCIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

116.138 C902170139 Average UL 8PSK Mean-Bep of TA-Value From 12 to 13 ...... 116-83 116.139 C902170140 Average UL GMSK Mean-Bep of TA-Value From 14 to 15...... 116-83 116.140 C902170141 Average UL 8PSK Mean-Bep of TA-Value From 14 to 15 ...... 116-84 116.141 C902170142 Average UL GMSK Mean-Bep of TA-Value From 16 to 17...... 116-85 116.142 C902170143 Average UL 8PSK Mean-Bep of TA-Value From 16 to 17 ...... 116-85 116.143 C902170144 Average UL GMSK Mean-Bep of TA-Value From 18 to 19...... 116-86 116.144 C902170145 Average UL 8PSK Mean-Bep of TA-Value From 18 to 19 ...... 116-87 116.145 C902170146 Average UL GMSK Mean-Bep of TA-Value From 20 to 21...... 116-87 116.146 C902170147 Average UL 8PSK Mean-Bep of TA-Value From 20 to 21 ...... 116-88 116.147 C902170148 Average UL GMSK Mean-Bep of TA-Value From 22 to 23...... 116-89 116.148 C902170149 Average UL 8PSK Mean-Bep of TA-Value From 22 to 23 ...... 116-89 116.149 C902170150 Average UL GMSK Mean-Bep of TA-Value From 24 to 25...... 116-90 116.150 C902170151 Average UL 8PSK Mean-Bep of TA-Value From 24 to 25 ...... 116-91 116.151 C902170152 Average UL GMSK Mean-Bep of TA-Value From 26 to 27...... 116-91 116.152 C902170153 Average UL 8PSK Mean-Bep of TA-Value From 26 to 27 ...... 116-92 116.153 C902170154 Average UL GMSK Mean-Bep of TA-Value From 28 to 29...... 116-93 116.154 C902170155 Average UL 8PSK Mean-Bep of TA-Value From 28 to 29 ...... 116-93 116.155 C902170156 Average UL GMSK Mean-Bep of TA-Value From 30 to 31...... 116-94 116.156 C902170157 Average UL 8PSK Mean-Bep of TA-Value From 30 to 31 ...... 116-95 116.157 C902170158 Average UL GMSK Mean-Bep of TA-Value From 32 to 33...... 116-95 116.158 C902170159 Average UL 8PSK Mean-Bep of TA-Value From 32 to 33 ...... 116-96 116.159 C902170160 Average UL GMSK Mean-Bep of TA-Value From 34 to 35...... 116-97 116.160 C902170161 Average UL 8PSK Mean-Bep of TA-Value From 34 to 35 ...... 116-97 116.161 C902170162 Average UL GMSK Mean-Bep of TA-Value From 36 to 37...... 116-98 116.162 C902170163 Average UL 8PSK Mean-Bep of TA-Value From 36 to 37 ...... 116-99 116.163 C902170164 Average UL GMSK Mean-Bep of TA-Value From 38 to 39...... 116-99 116.164 C902170165 Average UL 8PSK Mean-Bep of TA-Value From 38 to 39............................................................................................................. 116-100 116.165 C902170166 Average UL GMSK Mean-Bep of TA-Value From 40 to 41............................................................................................................. 116-101 116.166 C902170167 Average UL 8PSK Mean-Bep of TA-Value From 40 to 41............................................................................................................. 116-101 116.167 C902170168 Average UL GMSK Mean-Bep of TA-Value From 42 to 43............................................................................................................. 116-102 116.168 C902170169 Average UL 8PSK Mean-Bep of TA-Value From 42 to 43............................................................................................................. 116-103 116.169 C902170170 Average UL GMSK Mean-Bep of TA-Value From 44 to 45............................................................................................................. 116-103

CC SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

116.170 C902170171 Average UL 8PSK Mean-Bep of TA-Value From 44 to 45............................................................................................................. 116-104 116.171 C902170172 Average UL GMSK Mean-Bep of TA-Value From 46 to 47............................................................................................................. 116-105 116.172 C902170173 Average UL 8PSK Mean-Bep of TA-Value From 46 to 47............................................................................................................. 116-105 116.173 C902170174 Average UL GMSK Mean-Bep of TA-Value From 48 to 49............................................................................................................. 116-106 116.174 C902170175 Average UL 8PSK Mean-Bep of TA-Value From 48 to 49............................................................................................................. 116-107 116.175 C902170176 Average UL GMSK Mean-Bep of TA-Value From 50 to 51............................................................................................................. 116-107 116.176 C902170177 Average UL 8PSK Mean-Bep of TA-Value From 50 to 51............................................................................................................. 116-108 116.177 C902170178 Average UL GMSK Mean-Bep of TA-Value From 52 to 53............................................................................................................. 116-109 116.178 C902170179 Average UL 8PSK Mean-Bep of TA-Value From 52 to 53............................................................................................................. 116-109 116.179 C902170180 Average UL GMSK Mean-Bep of TA-Value From 54 to 55............................................................................................................. 116-110 116.180 C902170181 Average UL 8PSK Mean-Bep of TA-Value From 54 to 55 ......116-111 116.181 C902170182 Average UL GMSK Mean-Bep of TA-Value From 56 to 57..............................................................................................................116-111 116.182 C902170183 Average UL 8PSK Mean-Bep of TA-Value From 56 to 57 ..... 116-112 116.183 C902170184 Average UL GMSK Mean-Bep of TA-Value From 58 to 59............................................................................................................. 116-113 116.184 C902170185 Average UL 8PSK Mean-Bep of TA-Value From 58 to 59 ..... 116-113 116.185 C902170186 Average UL GMSK Mean-Bep of TA-Value From 60 to 61............................................................................................................. 116-114 116.186 C902170187 Average UL 8PSK Mean-Bep of TA-Value From 60 to 61 ..... 116-115 116.187 C902170188 Average UL GMSK Mean-Bep of TA-Value From 62 to 63............................................................................................................. 116-115 116.188 C902170189 Average UL 8PSK Mean-Bep of TA-Value From 62 to 63 ..... 116-116

Chapter 117 PS Downlink Radio Quality Statistic Measurement ....... 117-1

117.1 C902180001 Number of MEAN BEP=0 in Downlink GMSK Blocks.................. 117-5 117.2 C902180002 Number of MEAN BEP=1 in Downlink GMSK Blocks.................. 117-6 117.3 C902180003 Number of MEAN BEP=2 in Downlink GMSK Blocks.................. 117-7 117.4 C902180004 Number of MEAN BEP=3 in Downlink GMSK Blocks.................. 117-8 117.5 C902180005 Number of MEAN BEP=4 in Downlink GMSK Blocks.................. 117-9 117.6 C902180006 Number of MEAN BEP=5 in Downlink GMSK Blocks................ 117-10
CCI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

117.7 C902180007 Number of MEAN BEP=6 in Downlink GMSK Blocks................ 117-11 117.8 C902180008 Number of MEAN BEP=7 in Downlink GMSK Blocks................ 117-12 117.9 C902180009 Number of MEAN BEP=8 in Downlink GMSK Blocks................ 117-13 117.10 C902180010 Number of MEAN BEP=9 in Downlink GMSK Blocks.............. 117-14 117.11 C902180011 Number of MEAN BEP=10 in Downlink GMSK Blocks ............ 117-15 117.12 C902180012 Number of MEAN BEP=11 in Downlink GMSK Blocks ............ 117-16 117.13 C902180013 Number of MEAN BEP=12 in Downlink GMSK Blocks ............ 117-17 117.14 C902180014 Number of MEAN BEP=13 in Downlink GMSK Blocks ............ 117-18 117.15 C902180015 Number of MEAN BEP=14 in Downlink GMSK Blocks ............ 117-19 117.16 C902180016 Number of MEAN BEP=15 in Downlink GMSK Blocks ............ 117-20 117.17 C902180017 Number of MEAN BEP=16 in Downlink GMSK Blocks ............ 117-21 117.18 C902180018 Number of MEAN BEP=17 in Downlink GMSK Blocks ............ 117-22 117.19 C902180019 Number of MEAN BEP=18 in Downlink GMSK Blocks ............ 117-23 117.20 C902180020 Number of MEAN BEP=19 in Downlink GMSK Blocks ............ 117-24 117.21 C902180021 Number of MEAN BEP=20 in Downlink GMSK Blocks ............ 117-25 117.22 C902180022 Number of MEAN BEP=21 in Downlink GMSK Blocks ............ 117-26 117.23 C902180023 Number of MEAN BEP=22 in Downlink GMSK Blocks ............ 117-27 117.24 C902180024 Number of MEAN BEP=23 in Downlink GMSK Blocks ............ 117-28 117.25 C902180025 Number of MEAN BEP=24 in Downlink GMSK Blocks ............ 117-29 117.26 C902180026 Number of MEAN BEP=25 in Downlink GMSK Blocks ............ 117-30 117.27 C902180027 Number of MEAN BEP=26 in Downlink GMSK Blocks ............ 117-31 117.28 C902180028 Number of MEAN BEP=27 in Downlink GMSK Blocks ............ 117-32 117.29 C902180029 Number of MEAN BEP=28 in Downlink GMSK Blocks ............ 117-33 117.30 C902180030 Number of MEAN BEP=29 in Downlink GMSK Blocks ............ 117-34 117.31 C902180031 Number of MEAN BEP=30 in Downlink GMSK Blocks ............ 117-35 117.32 C902180032 Number of MEAN BEP=31 in Downlink GMSK Blocks ............ 117-36 117.33 C902180033 Number of CV BEP=0 in Downlink GMSK Blocks................... 117-37 117.34 C902180034 Number of CV BEP=1 in Downlink GMSK Blocks................... 117-38 117.35 C902180035 Number of CV BEP=2 in Downlink GMSK Blocks................... 117-39 117.36 C902180036 Number of CV BEP=3 in Downlink GMSK Blocks................... 117-40 117.37 C902180037 Number of CV BEP=4 in Downlink GMSK Blocks................... 117-41 117.38 C902180038 Number of CV BEP=5 in Downlink GMSK Blocks................... 117-42 117.39 C902180039 Number of CV BEP=6 in Downlink GMSK Blocks................... 117-43 117.40 C902180040 Number of CV BEP=7 in Downlink GMSK Blocks................... 117-44 117.41 C902180041 Number of MEAN BEP=0 in Downlink 8PSK Blocks ............... 117-45 117.42 C902180042 Number of MEAN BEP=1 in Downlink 8PSK Blocks ............... 117-46 117.43 C902180043 Number of MEAN BEP=2 in Downlink 8PSK Blocks ............... 117-47

CCII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

117.44 C902180044 Number of MEAN BEP=3 in Downlink 8PSK Blocks ............... 117-48 117.45 C902180045 Number of MEAN BEP=4 in Downlink 8PSK Blocks ............... 117-49 117.46 C902180046 Number of MEAN BEP=5 in Downlink 8PSK Blocks ............... 117-50 117.47 C902180047 Number of MEAN BEP=6 in Downlink 8PSK Blocks ............... 117-51 117.48 C902180048 Number of MEAN BEP=7 in Downlink 8PSK Blocks ............... 117-52 117.49 C902180049 Number of MEAN BEP=8 in Downlink 8PSK Blocks ............... 117-53 117.50 C902180050 Number of MEAN BEP=9 in Downlink 8PSK Blocks ............... 117-54 117.51 C902180051 Number of MEAN BEP=10 in Downlink 8PSK Blocks ............. 117-55 117.52 C902180052 Number of MEAN BEP=11 in Downlink 8PSK Blocks.............. 117-56 117.53 C902180053 Number of MEAN BEP=12 in Downlink 8PSK Blocks ............. 117-57 117.54 C902180054 Number of MEAN BEP=13 in Downlink 8PSK Blocks ............. 117-58 117.55 C902180055 Number of MEAN BEP=14 in Downlink 8PSK Blocks ............. 117-59 117.56 C902180056 Number of MEAN BEP=15 in Downlink 8PSK Blocks ............. 117-60 117.57 C902180057 Number of MEAN BEP=16 in Downlink 8PSK Blocks ............. 117-61 117.58 C902180058 Number of MEAN BEP=17 in Downlink 8PSK Blocks ............. 117-62 117.59 C902180059 Number of MEAN BEP=18 in Downlink 8PSK Blocks ............. 117-63 117.60 C902180060 Number of MEAN BEP=19 in Downlink 8PSK Blocks ............. 117-64 117.61 C902180061 Number of MEAN BEP=20 in Downlink 8PSK Blocks ............. 117-65 117.62 C902180062 Number of MEAN BEP=21 in Downlink 8PSK Blocks ............. 117-66 117.63 C902180063 Number of MEAN BEP=22 in Downlink 8PSK Blocks ............. 117-67 117.64 C902180064 Number of MEAN BEP=23 in Downlink 8PSK Blocks ............. 117-68 117.65 C902180065 Number of MEAN BEP=24 in Downlink 8PSK Blocks ............. 117-69 117.66 C902180066 Number of MEAN BEP=25 in Downlink 8PSK Blocks ............. 117-70 117.67 C902180067 Number of MEAN BEP=26 in Downlink 8PSK Blocks ............. 117-71 117.68 C902180068 Number of MEAN BEP=27 in Downlink 8PSK Blocks ............. 117-72 117.69 C902180069 Number of MEAN BEP=28 in Downlink 8PSK Blocks ............. 117-73 117.70 C902180070 Number of MEAN BEP=29 in Downlink 8PSK Blocks ............. 117-74 117.71 C902180071 Number of MEAN BEP=30 in Downlink 8PSK Blocks ............. 117-75 117.72 C902180072 Number of MEAN BEP=31 in Downlink 8PSK Blocks ............. 117-76 117.73 C902180073 Number of CV BEP=0 in Downlink 8PSK Blocks .................... 117-77 117.74 C902180074 Number of CV BEP=1 in Downlink 8PSK Blocks .................... 117-78 117.75 C902180075 Number of CV BEP=2 in Downlink 8PSK Blocks .................... 117-79 117.76 C902180076 Number of CV BEP=3 in Downlink 8PSK Blocks .................... 117-80 117.77 C902180077 Number of CV BEP=4 in Downlink 8PSK Blocks .................... 117-81 117.78 C902180078 Number of CV BEP=5 in Downlink 8PSK Blocks .................... 117-82 117.79 C902180079 Number of CV BEP=6 in Downlink 8PSK Blocks .................... 117-83 117.80 C902180080 Number of CV BEP=7 in Downlink 8PSK Blocks .................... 117-84

CCIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

117.81 C902180081 Number of RQ=0 in Downlink Blocks..................................... 117-85 117.82 C902180082 Number of RQ=1 in Downlink Blocks..................................... 117-85 117.83 C902180083 Number of RQ=2 in Downlink Blocks..................................... 117-86 117.84 C902180084 Number of RQ=3 in Downlink Blocks..................................... 117-87 117.85 C902180085 Number of RQ=4 in Downlink Blocks..................................... 117-88 117.86 C902180086 Number of RQ=5 in Downlink Blocks..................................... 117-89 117.87 C902180087 Number of RQ=6 in Downlink Blocks..................................... 117-90 117.88 C902180088 Number of RQ=7 in Downlink Blocks..................................... 117-91 117.89 C902180089 Average DL GMSK Mean-Bep of C-Value From 0 to 10 .......... 117-92 117.90 C902180090 Average DL 8PSK Mean-Bep of C-Value From 0 to 10 ........... 117-93 117.91 C902180091 Average DL GMSK Mean-Bep of C-Value From 11 to 15 ........ 117-93 117.92 C902180092 Average DL 8PSK Mean-Bep of C-Value From 11 to 15.......... 117-94 117.93 C902180093 Average DL GMSK Mean-Bep of C-Value From 16 to 20 ........ 117-95 117.94 C902180094 Average DL 8PSK Mean-Bep of C-Value From 16 to 20 ......... 117-95 117.95 C902180095 Average DL GMSK Mean-Bep of C-Value From 21 to 30 ........ 117-96 117.96 C902180096 Average DL 8PSK Mean-Bep of C-Value From 21 to 30 ......... 117-97 117.97 C902180097 Average DL GMSK Mean-Bep of C-Value From 31 to 40 ........ 117-97 117.98 C902180098 Average DL 8PSK Mean-Bep of C-Value From 31 to 40 ......... 117-98 117.99 C902180099 Average DL GMSK Mean-Bep of C-Value From 41 to 63 ........ 117-99 117.100 C902180100 Average DL 8PSK Mean-Bep of C-Value From 41 to 63........ 117-99 117.101 C902180101 Average DL GMSK Mean-Bep of TA-Value 0...................... 117-100 117.102 C902180102 Average DL 8PSK Mean-Bep of TA-Value 0....................... 117-100 117.103 C902180103 Average DL GMSK Mean-Bep of TA-Value 1...................... 117-101 117.104 C902180104 Average DL 8PSK Mean-Bep of TA-Value 1....................... 117-102 117.105 C902180105 Average DL GMSK Mean-Bep of TA-Value 2...................... 117-102 117.106 C902180106 Average DL 8PSK Mean-Bep of TA-Value 2....................... 117-103 117.107 C902180107 Average DL GMSK Mean-Bep of TA-Value 3...................... 117-103 117.108 C902180108 Average DL 8PSK Mean-Bep of TA-Value 3....................... 117-104 117.109 C902180109 Average DL GMSK Mean-Bep of TA-Value 4...................... 117-105 117.110 C902180110 Average DL 8PSK Mean-Bep of TA-Value 4 ....................... 117-105 117.111 C902180111 Average DL GMSK Mean-Bep of TA-Value 5....................... 117-106 117.112 C902180112 Average DL 8PSK Mean-Bep of TA-Value 5 ....................... 117-106 117.113 C902180113 Average DL GMSK Mean-Bep of TA-Value 6 ...................... 117-107 117.114 C902180114 Average DL 8PSK Mean-Bep of TA-Value 6 ....................... 117-108 117.115 C902180115 Average DL GMSK Mean-Bep of TA-Value 7 ...................... 117-108 117.116 C902180116 Average DL 8PSK Mean-Bep of TA-Value 7 ....................... 117-109 117.117 C902180117 Average DL GMSK Mean-Bep of TA-Value 8 ...................... 117-109

CCIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

117.118 C902180118 Average DL 8PSK Mean-Bep of TA-Value 8 ....................... 117-110 117.119 C902180119 Average DL GMSK Mean-Bep of TA-Value 9 .......................117-111 117.120 C902180120 Average DL 8PSK Mean-Bep of TA-Value 9........................117-111 117.121 C902180121 Average DL GMSK Mean-Bep of TA-Value 10.................... 117-112 117.122 C902180122 Average DL 8PSK Mean-Bep of TA-Value 10 ..................... 117-112 117.123 C902180123 Average DL GMSK Mean-Bep of TA-Value 11 .................... 117-113 117.124 C902180124 Average DL 8PSK Mean-Bep of TA-Value 11 ..................... 117-114 117.125 C902180125 Average DL GMSK Mean-Bep of TA-Value From 12 to 13............................................................................................................. 117-114 117.126 C902180126 Average DL 8PSK Mean-Bep of TA-Value From 12 to 13 ..... 117-115 117.127 C902180127 Average DL GMSK Mean-Bep of TA-Value From 14 to 15............................................................................................................. 117-116 117.128 C902180128 Average DL 8PSK Mean-Bep of TA-Value From 14 to 15 ..... 117-116 117.129 C902180129 Average DL GMSK Mean-Bep of TA-Value From 16 to 17............................................................................................................. 117-117 117.130 C902180130 Average DL 8PSK Mean-Bep of TA-Value From 16 to 17 ..... 117-118 117.131 C902180131 Average DL GMSK Mean-Bep of TA-Value From 18 to 19............................................................................................................. 117-118 117.132 C902180132 Average DL 8PSK Mean-Bep of TA-Value From 18 to 19 ..... 117-119 117.133 C902180133 Average DL GMSK Mean-Bep of TA-Value From 20 to 21............................................................................................................. 117-120 117.134 C902180134 Average DL 8PSK Mean-Bep of TA-Value From 20 to 21............................................................................................................. 117-120 117.135 C902180135 Average DL GMSK Mean-Bep of TA-Value From 22 to 23............................................................................................................. 117-121 117.136 C902180136 Average DL 8PSK Mean-Bep of TA-Value From 22 to 23............................................................................................................. 117-122 117.137 C902180137 Average DL GMSK Mean-Bep of TA-Value From 24 to 25............................................................................................................. 117-122 117.138 C902180138 Average DL 8PSK Mean-Bep of TA-Value From 24 to 25............................................................................................................. 117-123 117.139 C902180139 Average DL GMSK Mean-Bep of TA-Value From 26 to 27............................................................................................................. 117-124 117.140 C902180140 Average DL 8PSK Mean-Bep of TA-Value From 26 to 27............................................................................................................. 117-124 117.141 C902180141 Average DL GMSK Mean-Bep of TA-Value From 28 to 29............................................................................................................. 117-125 117.142 C902180142 Average DL 8PSK Mean-Bep of TA-Value From 28 to 29............................................................................................................. 117-126

CCV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

117.143 C902180143 Average DL GMSK Mean-Bep of TA-Value From 30 to 31............................................................................................................. 117-126 117.144 C902180144 Average DL 8PSK Mean-Bep of TA-Value From 30 to 31............................................................................................................. 117-127 117.145 C902180145 Average DL GMSK Mean-Bep of TA-Value From 32 to 33............................................................................................................. 117-128 117.146 C902180146 Average DL 8PSK Mean-Bep of TA-Value From 32 to 33............................................................................................................. 117-128 117.147 C902180147 Average DL GMSK Mean-Bep of TA-Value From 34 to 35............................................................................................................. 117-129 117.148 C902180148 Average DL 8PSK Mean-Bep of TA-Value From 34 to 35............................................................................................................. 117-130 117.149 C902180149 Average DL GMSK Mean-Bep of TA-Value From 36 to 37............................................................................................................. 117-130 117.150 C902180150 Average DL 8PSK Mean-Bep of TA-Value From 36 to 37............................................................................................................. 117-131 117.151 C902180151 Average DL GMSK Mean-Bep of TA-Value From 38 to 39............................................................................................................. 117-132 117.152 C902180152 Average DL 8PSK Mean-Bep of TA-Value From 38 to 39............................................................................................................. 117-132 117.153 C902180153 Average DL GMSK Mean-Bep of TA-Value From 40 to 41............................................................................................................. 117-133 117.154 C902180154 Average DL 8PSK Mean-Bep of TA-Value From 40 to 41............................................................................................................. 117-134 117.155 C902180155 Average DL GMSK Mean-Bep of TA-Value From 42 to 43............................................................................................................. 117-134 117.156 C902180156 Average DL 8PSK Mean-Bep of TA-Value From 42 to 43............................................................................................................. 117-135 117.157 C902180157 Average DL GMSK Mean-Bep of TA-Value From 44 to 45............................................................................................................. 117-136 117.158 C902180158 Average DL 8PSK Mean-Bep of TA-Value From 44 to 45............................................................................................................. 117-136 117.159 C902180159 Average DL GMSK Mean-Bep of TA-Value From 46 to 47............................................................................................................. 117-137 117.160 C902180160 Average DL 8PSK Mean-Bep of TA-Value From 46 to 47............................................................................................................. 117-138 117.161 C902180161 Average DL GMSK Mean-Bep of TA-Value From 48 to 49............................................................................................................. 117-138 117.162 C902180162 Average DL 8PSK Mean-Bep of TA-Value From 48 to 49............................................................................................................. 117-139

CCVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

117.163 C902180163 Average DL GMSK Mean-Bep of TA-Value From 50 to 51............................................................................................................. 117-140 117.164 C902180164 Average DL 8PSK Mean-Bep of TA-Value From 50 to 51............................................................................................................. 117-140 117.165 C902180165 Average DL GMSK Mean-Bep of TA-Value From 52 to 53............................................................................................................. 117-141 117.166 C902180166 Average DL 8PSK Mean-Bep of TA-Value From 52 to 53............................................................................................................. 117-142 117.167 C902180167 Average DL GMSK Mean-Bep of TA-Value From 54 to 55............................................................................................................. 117-142 117.168 C902180168 Average DL 8PSK Mean-Bep of TA-Value From 54 to 55............................................................................................................. 117-143 117.169 C902180169 Average DL GMSK Mean-Bep of TA-Value From 56 to 57............................................................................................................. 117-144 117.170 C902180170 Average DL 8PSK Mean-Bep of TA-Value From 56 to 57............................................................................................................. 117-144 117.171 C902180171 Average DL GMSK Mean-Bep of TA-Value From 58 to 59............................................................................................................. 117-145 117.172 C902180172 Average DL 8PSK Mean-Bep of TA-Value From 58 to 59............................................................................................................. 117-146 117.173 C902180173 Average DL GMSK Mean-Bep of TA-Value From 60 to 61............................................................................................................. 117-146 117.174 C902180174 Average DL 8PSK Mean-Bep of TA-Value From 60 to 61............................................................................................................. 117-147 117.175 C902180175 Average DL GMSK Mean-Bep of TA-Value From 62 to 63............................................................................................................. 117-148 117.176 C902180176 Average DL 8PSK Mean-Bep of TA-Value From 62 to 63............................................................................................................. 117-148

Chapter 118 RU Measurement............................................................... 118-1

118.1 C902190001 Cell Number ............................................................................ 118-1 118.2 C902190002 Logic TRX Number .................................................................. 118-1 118.3 C902190003 Sum of Uplink Weight in Active Status....................................... 118-2 118.4 C902190004 Average Uplink Rx Level in Active Status .................................. 118-2 118.5 C902190005 Average Uplink Rx BER in Active Status (1000) ....................... 118-3 118.6 C902190006 Average Uplink Rx Level of Master Diversity in Active Status ...... 118-3 118.7 C902190007 Average Uplink Rx Level of Slave Diversity in Active Status........ 118-4 118.8 C902190008 Average Uplink Rx Level of Master Diversity in Idle Status ......... 118-4 118.9 C902190009 Average Uplink Rx Level of Slave Diversity in Idle Status ........... 118-5 118.10 C902190010 RRU traffic percent................................................................. 118-5

CCVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 119 PS Power Control Measurement...................................... 119-1

119.1 C902200001 Number of Increasing Uplink Power by C Value in GPRS ........... 119-2 119.2 C902200002 Number of Increasing Uplink Power by MEAN_BEP in GPRS ...... 119-2 119.3 C902200003 Number of Increasing Uplink Power by CV_BEP in GPRS.......... 119-2 119.4 C902200004 Number of Decreasing Uplink Power by C Value in GPRS .......... 119-3 119.5 C902200005 Number of Decreasing Uplink Power by MEAN_BEP and CV_BEP in GPRS ......................................................................................... 119-3 119.6 C902200006 Number of Uplink Power Unchanging in GPRS .......................... 119-4 119.7 C902200007 Number of Increasing Downlink Power by C Value in GPRS ....... 119-4 119.8 C902200008 Number of Increasing Downlink Power by RXQUAL in GPRS ...... 119-5 119.9 C902200009 Number of Decreasing Downlink Power by C Value in GPRS ...... 119-5 119.10 C902200010 Number of Decreasing Downlink Power by RXQUAL in GPRS ........................................................................................................... 119-5 119.11 C902200011 Number of Downlink Power Unchanging in GPRS .................... 119-6 119.12 C902200012 Number of Increasing Uplink Power by C Value in EDGE ......... 119-6 119.13 C902200013 Number of Increasing Uplink Power by MEAN_BEP in EDGE ........................................................................................................... 119-7 119.14 C902200014 Number of Increasing Uplink Power by CV_BEP in EDGE ........ 119-7 119.15 C902200015 Number of Decreasing Uplink Power by C Value in EDGE ........ 119-8 119.16 C902200016 Number of Decreasing Uplink Power by MEAN_BEP and CV_BEP in EDGE ......................................................................................... 119-8 119.17 C902200017 Number of Uplink Power Unchanging in EDGE ........................ 119-9 119.18 C902200018 Number of Increasing Downlink Power by C Value in EDGE ...... 119-9 119.19 C902200019 Number of Increasing Downlink Power by MEAN_BEP in EDGE ......................................................................................................... 119-10 119.20 C902200020 Number of Increasing Downlink Power by CV_BEP in EDGE ......................................................................................................... 119-10 119.21 C902200021 Number of Decreasing Downlink Power by C Value in EDGE ......................................................................................................... 119-10 119.22 C902200022 Number of Decreasing Downlink Power by MEAN_BEP and CV_BEP in EDGE ....................................................................................... 119-11 119.23 C902200023 Number of Downlink Power Unchanging in EDGE.................. 119-11

Chapter 120 VAMOS Measurement....................................................... 120-1

120.1 C902210001 Number of MUTE SAIC Detection.............................................120-1 120.2 C902210002 Number of SAIC AFC Detection................................................120-2 120.3 C902210003 Number of Attempt of Pairing Between Two TCH/Fs ..................120-3 120.4 C902210004 Number of Pairing Success Between Two TCH/Fs.....................120-4 120.5 C902210005 Number of Attempt of Pairing Between Two TCH/Hs..................120-4

CCVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

120.6 C902210006 Number of Pairing Success Between Two TCH/Hs ....................120-5 120.7 C902210007 Number of Attempt of Pair Releasing Between Two TCH/Fs.......120-5 120.8 C902210008 Number of Pair Releasing Success Between Two TCH/Fs .........120-6 120.9 C902210009 Number of Attempt of Pair Releasing Between Two TCH/Hs ......120-7 120.10 C902210010 Number of Pair Releasing Success Between Two TCH/Hs .......120-7 120.11 C902210011 Number of Pair Release Due to Power ....................................120-8 120.12 C902210012 Number of Pair Release Due to Uplink SCPIR .........................120-8 120.13 C902210013 Number of Pair Release Due to Downlink SCPIR.....................120-9 120.14 C902210014 Number of Connect Failure Due to No DSP Resource..............120-9 120.15 C902210015 Number of Drop Call During Pairing (TCH/F) .........................120-10 120.16 C902210016 Number of Drop Call During Pairing (TCH/H).........................120-10

Chapter 121 IP SLA PD Statistic ........................................................... 121-1

121.1 C902270001 PD Type..................................................................................121-2 121.2 C902270002 PD SubType............................................................................121-2 121.3 C902270003 ULP Pno .................................................................................121-2 121.4 C902270004 ULP TYPE ..............................................................................121-3 121.5 C902270005 ULP ID....................................................................................121-3 121.6 C902270006 Packet Type ............................................................................121-3 121.7 C902270007 Up Protocol .............................................................................121-4 121.8 C902270008 Source IP 1 .............................................................................121-4 121.9 C902270009 Source IP 2 .............................................................................121-5 121.10 C902270010 Source IP 3 ...........................................................................121-5 121.11 C902270011 Source IP 4............................................................................121-5 121.12 C902270012 Source Port ...........................................................................121-6 121.13 C902270013 Destination IP 1 .....................................................................121-6 121.14 C902270014 Destination IP 2 .....................................................................121-6 121.15 C902270015 Destination IP 3 .....................................................................121-7 121.16 C902270016 Destination IP 4 .....................................................................121-7 121.17 C902270017 Destination Port .....................................................................121-7 121.18 C902270018 Send PD Request ..................................................................121-8 121.19 C902270019 Receive PD Reply..................................................................121-8 121.20 C902270020 PD Packet Loss Rate .............................................................121-9 121.21 C902270021 PD Packet statistics by watch time..........................................121-9 121.22 C902270022 PD Packet Loss Rate by watch time........................................121-9 121.23 C902270023 PD Packet Out of Sequence .................................................121-10 121.24 C902270024 Receive PD Request............................................................121-10 121.25 C902270025 Send PD Reply....................................................................121-10

CCIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

121.26 C902270026 Max Delay........................................................................... 121-11 121.27 C902270027 Min Delay............................................................................ 121-11 121.28 C902270028 Mean Delay......................................................................... 121-11 121.29 C902270029 Max Jitter ............................................................................121-12 121.30 C902270030 Min Jitter .............................................................................121-12 121.31 C902270031 Mean Jitter ..........................................................................121-13 121.32 C902270032 Jitter Sampling Times...........................................................121-13 121.33 C902270033 Number of delay sampling ....................................................121-13

Chapter 122 Abis Usage Measurement ................................................ 122-1

122.1 C902290001 Number of CS preempt PS because of Abis resource ................122-2 122.2 C902290002 Number of CS allocate Abis resource........................................122-2 122.3 C902290003 Number of PS allocate Abis resource........................................122-2 122.4 C902290004 Number of PS restricted because of Abis resource ....................122-3 122.5 C902290005 Number of PS restricted because of Abis resource ....................122-3 122.6 C902290006 Peak Value of CS Abis Bandwidth Uplink ..................................122-4 122.7 C902290007 Peak value of PS Abis bandwidth uplink....................................122-4 122.8 C902290008 Value of CS Abis Bandwidth Uplink...........................................122-5 122.9 C902290009 Number of CS Abis Bandwidth Uplink Samples .........................122-5 122.10 C902290010 Value of PS Abis Bandwidth Uplink .........................................122-6 122.11 C902290011 Number of PS Abis Bandwidth Uplink Samples ........................122-6 122.12 C902290012 Peak Value of CS Abis Bandwidth Downlink ............................122-6 122.13 C902290013 Peak Value of PS Abis Bandwidth Downlink ............................122-7 122.14 C902290014 Value of CS Abis Bandwidth Downlink.....................................122-7 122.15 C902290015 Number of CS Abis Bandwidth Downlink Samples ...................122-8 122.16 C902290016 Value of PS Abis Bandwidth Downlink .....................................122-8 122.17 C902290017 Number of PS Abis Bandwidth Downlink Samples ...................122-9 122.18 C902290018 Peak Value of Cell CS Allocated Abis Bandwidth Uplink ...........122-9 122.19 C902290019 Peak Value of PS Allocated Abis Bandwidth Uplink ................122-10 122.20 C902290020 Value of CS Abis Bandwidth Be Allocated Uplink ...................122-10 122.21 C902290021 Number of CS Abis Bandwidth Be Allocated Uplink Samples ..................................................................................................... 122-11 122.22 C902290022 Value of PS Abis Bandwidth Be Allocated Uplink ................... 122-11 122.23 C902290023 Number of PS Abis Bandwidth Be Allocated Uplink Samples .....................................................................................................122-12 122.24 C902290024 Peak Value of CS Abis Bandwidth Be Allocated Downlink ......122-12 122.25 C902290025 Peak Value of PS Abis Bandwidth Be Allocated Downlink.......122-13 122.26 C902290026 Value of CS Abis Bandwidth Be Allocated Downlink ...............122-13

CCX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

122.27 C902290027 Number of CS Abis Bandwidth Be Allocated Downlink Samples .....................................................................................................122-14 122.28 C902290028 Value of PS Abis bandwidth be allocated downlink .................122-14 122.29 C902290029 Number of PS Abis Bandwidth Be Allocated Downlink Samples .....................................................................................................122-15

Chapter 123 DSP statistic on BIPB board HOST ................................. 123-1

123.1 C902300001 Peak value of HPI message queue usage uplink .......................123-1 123.2 C902300002 Mean value of HPI message queue usage uplink.......................123-1 123.3 C902300003 Peak value of HPI message queue usage downlink ...................123-2 123.4 C902300004 Mean value of HPI message queue usage downplink.................123-2

Chapter 124 Statistic on BIPB board DSP............................................ 124-1

124.1 C902310001 Peak value of DSP usage ........................................................124-1 124.2 C902310002 Mean value of DSP usage........................................................124-2 124.3 C902310003 Peak value of DSP received physical bandwidth........................124-2 124.4 C902310004 Peak value of DSP sent physical bandwidth ..............................124-3 124.5 C902310005 Mean value of DSP received physical bandwidth .......................124-3 124.6 C902310006 Mean value of DSP sent physical bandwidth .............................124-4 124.7 C902310007 Number of active voice channel ................................................124-4 124.8 C902310008 Number of PS channel .............................................................124-4 124.9 C902310009 Number of HR channel.............................................................124-5 124.10 C902310010 Number of FR channel ...........................................................124-5 124.11 C902310011 Number of EFR channel .........................................................124-6 124.12 C902310012 Number of AMR HR channel ..................................................124-6 124.13 C902310014 Number of AMR WB channel..................................................124-6 124.14 C902310015 Number of dropped frame ......................................................124-7 124.15 C902310016 Number of CRC check error ...................................................124-7 124.16 C902310017 Number of MAC write error.....................................................124-8

Chapter 125 IPRB DSP statistic on BIPB board HOST ....................... 125-1
125.1 C902320001 Peak value of HPI message queue usage uplink .......................125-1 125.2 C902320002 Mean value of HPI message queue usage uplink.......................125-1 125.3 C902320003 Peak value of HPI message queue usage downlink ...................125-2 125.4 C902320004 Mean value of HPI message queue usage downlink ..................125-2

Chapter 126 Statistic on BIPB board IPRB DSP .................................. 126-1

126.1 C902330001 Peak value of DSP usage ........................................................126-1 126.2 C902330002 Mean value of DSP usage........................................................126-2 126.3 C902330003 Peak value of DSP received physical bandwidth........................126-2 126.4 C902330004 Peak value of DSP sent physical bandwidth ..............................126-3
CCXI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

126.5 C902330005 Mean value of DSP received physical bandwidth .......................126-3 126.6 C902330006 Mean value of DSP sent physical bandwidth .............................126-4 126.7 C902330007 Number of active voice channel ................................................126-4 126.8 C902330008 Number of HR channel.............................................................126-4 126.9 C902330009 Number of FR channel .............................................................126-5 126.10 C902330010 Number of EFR channel.........................................................126-5 126.11 C902330011 Number of AMR HR channel...................................................126-6 126.12 C902330012 Number of AMR FR channel...................................................126-6 126.13 C902330013 Number of AMR WB channel..................................................126-7 126.14 C902330014 Number of dropped frame ......................................................126-7 126.15 C902330015 Number of CRC check error ...................................................126-7 126.16 C902330016 Number of MAC write error.....................................................126-8

Chapter 127 DSP statistic on AIPB board HOST ................................. 127-1

127.1 C902340001 Peak value of HPI message queue usage uplink .......................127-1 127.2 C902340002 Mean value of HPI message queue usage uplink.......................127-1 127.3 C902340003 Peak value of HPI message queue usage downlink ...................127-2 127.4 C902340004 Mean value of HPI message queue usage downlink ..................127-2

Chapter 128 Statistic on AIPB board DSP............................................ 128-1

128.1 C902350001 Peak value of DSP usage ........................................................128-1 128.2 C902350002 Mean value of DSP usage........................................................128-2 128.3 C902350003 Peak value of DSP received physical bandwidth........................128-2 128.4 C902350004 Peak value of DSP sent physical bandwidth ..............................128-3 128.5 C902350005 Mean value of DSP received physical bandwidth .......................128-3 128.6 C902350006 Mean value of DSP sent physical bandwidth .............................128-4 128.7 C902350007 Number of active voice channel ................................................128-4 128.8 C902350008 Number of HR channel.............................................................128-4 128.9 C902350009 Number of FR channel .............................................................128-5 128.10 C902350010 Number of EFR channel.........................................................128-5 128.11 C902350011 Number of AMR HR channel...................................................128-6 128.12 C902350012 Number of AMR FR channel...................................................128-6 128.13 C902350013 Number of AMR WB channel..................................................128-6 128.14 C902350014 Number of dropped frame ......................................................128-7 128.15 C902350015 Number of CRC check error ...................................................128-7 128.16 C902350016 Number of MAC write error.....................................................128-8

Chapter 129 DSP statistic on TIPB board HOST ................................. 129-1

129.1 C902360001 Peak value of HPI message queue usage uplink .......................129-1 129.2 C902360002 Mean value of HPI message queue usage uplink.......................129-1
CCXII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

129.3 C902360003 Peak value of HPI message queue usage downlink ...................129-2 129.4 C902360004 Mean value of HPI message queue usage downlink ..................129-2

Chapter 130 Statistic on TIPB board DSP ............................................ 130-1

130.1 C902370001 Mean value of HPI message queue usage downplink.................130-1 130.2 C902370002 Mean value of DSP usage........................................................130-2 130.3 C902370003 Peak value of DSP received physical bandwidth........................130-2 130.4 C902370004 Peak value of DSP sent physical bandwidth ..............................130-3 130.5 C902370005 Mean value of DSP received physical bandwidth .......................130-3 130.6 C902370006 Mean value of DSP sent physical bandwidth .............................130-4 130.7 C902370007 Number of active voice channel ................................................130-4 130.8 C902370008 Number of HR channel.............................................................130-4 130.9 C902370009 Number of FR channel .............................................................130-5 130.10 C902370010 Number of EFR channel.........................................................130-5 130.11 C902370011 Number of AMR HR channel...................................................130-6 130.12 C902370012 Number of AMR FR channel...................................................130-6 130.13 C902370013 Number of AMR WB channel..................................................130-6 130.14 C902370014 Number of dropped frame ......................................................130-7 130.15 C902370015 Number of CRC check error ...................................................130-7 130.16 C902370016 Number of MAC write error.....................................................130-8

Chapter 131 DSP statistic on DRTB board HOST................................ 131-1

131.1 C902380001 Peak value of HPI message queue usage uplink .......................131-1 131.2 C902380002 Mean value of HPI message queue usage uplink.......................131-1 131.3 C902380003 Peak value of HPI message queue usage downlink ...................131-2 131.4 C902380004 Mean value of HPI message queue usage downplink.................131-2

Chapter 132 Statistic on DRTB board DSP .......................................... 132-1

132.1 C902390001 Peak value of DSP usage ........................................................132-1 132.2 C902390002 Mean value of DSP usage........................................................132-2 132.3 C902390003 Peak value of DSP received physical bandwidth........................132-2 132.4 C902390004 Peak value of DSP sent physical bandwidth ..............................132-3 132.5 C902390005 Mean value of DSP received physical bandwidth .......................132-3 132.6 C902390006 Mean value of DSP sent physical bandwidth .............................132-4 132.7 C902390007 Number of active voice channel ................................................132-4 132.8 C902390008 Number of HR channel.............................................................132-4 132.9 C902390009 Number of FR channel .............................................................132-5 132.10 C902390010 Number of EFR channel.........................................................132-5 132.11 C902390011 Number of AMR HR channel...................................................132-6 132.12 C902390012 Number of AMR FR channel...................................................132-6
CCXIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

132.13 C902390013 Number of AMR WB channel..................................................132-6 132.14 C902390014 Number of TFO .....................................................................132-7 132.15 C902390015 Number of dropped frame ......................................................132-7 132.16 C902390016 Number of CRC check error ...................................................132-8 132.17 C902390017 Number of MAC write error.....................................................132-8

Chapter 133 DSP statistic on UPPB board HOST................................ 133-1

133.1 C902400001 Peak value of HPI message queue usage uplink .......................133-1 133.2 C902400002 Mean value of HPI message queue usage uplink.......................133-1 133.3 C902400003 Peak value of HPI message queue usage downlink ...................133-2 133.4 C902400004 Mean value of MAC process usage...........................................133-2

Chapter 134 Statistic on UPPB board DSP .......................................... 134-1

134.1 C902410001 Peak value of downlink LLC frame buffer usage ........................134-1 134.2 C902410002 Mean value of downlink LLC frame buffer usage........................134-2 134.3 C902410003 Peak value of MAC process usage ...........................................134-2 134.4 C902410004 Mean value of MAC process usage...........................................134-2 134.5 C902410005 Peak value of BSSGP process usage .......................................134-3 134.6 C902410006 Mean value of BSSGP process usage ......................................134-3 134.7 C902410007 Peak value of DSP usage ........................................................134-4 134.8 C902410008 Mean value of DSP usage........................................................134-4 134.9 C902410009 Peak value of memory usage ...................................................134-4 134.10 C902410010 Mean value of memory usage ................................................134-5 134.11 C902410011 Peak value of received physical bandwidth ..............................134-5 134.12 C902410012 Peak value of sent physical bandwidth ....................................134-6 134.13 C902410013 Mean value of received physical bandwidth .............................134-6 134.14 C902410014 Mean value of sent physical bandwidth ...................................134-7 134.15 C902410015 Number of SLA measurement ................................................134-7

Chapter 135 TFO Measurement............................................................. 135-1

135.1 C902420001 Number of first try to contact distant parter after TFO being enabled.........................................................................................................135-1 135.2 C902420002 Number of retrying to contact distant partner after being interrupted.....................................................................................................135-2 135.3 C902420003 Number of TFO contacting with distant parter after first try .........135-3 135.4 C902420004 Number of TFO recontacting with distant parter after TFO being interrupted.....................................................................................................135-4 135.5 C902420005 Number of TFO establishment after first try ...............................135-5 135.6 C902420006 Number of TFO reestablishment after being interrupted .............135-6

CCXIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

135.7 C902420007 Number of synchronization lost at A-Interface resulting in TFO off.................................................................................................................135-7 135.8 C902420008 Number of codec type mismatch resulting in TFO off .................135-8 135.9 C902420009 Number of rate control failure resulting in TFO off when using AMR codec type ............................................................................................135-9 135.10 C902420010 Number of mode changes for establishing TFO .....................135-10 135.11 C902420011 Number of mode changes for optimizing TFO ........................135-10 135.12 C902420012 Number of active collection changes for establishing TFO ......135-10 135.13 C902420013 Number of active collection changes for optimizing TFO.........135-10

Chapter 136 Adjacent 3G Cell Handover Measurement...................... 136-1

136.1 C902430001 Number of handover attempts from adjacent 3G cell to the selected cell ..................................................................................................136-2 136.2 C902430002 Number of successful handovers from adjacent 3G cell to the selected cell ..................................................................................................136-2 136.3 C902430003 Number of handover attempts from selected cell to the adjacent 3G cell ..........................................................................................................136-3 136.4 C902430004 Number of handovers from selected cell to the adjacent 3G cell ...............................................................................................................136-4 136.5 C902430005 Number of successful handovers from adjacent 3G cell to the selected cell ..................................................................................................136-5 136.6 C902430006 Number of handover attempts from selected cell to the adjacent 3G cell due to measurement result..................................................................136-5 136.7 C902430007 Number of handovers from selected cell to the adjacent 3G cell due to measurement result.............................................................................136-6 136.8 C902430008 Number of successful handovers from selected cell to the adjacent 3G cell due to measurement result ....................................................136-6 136.9 C902430009 Number of handover attempts from selected cell to the adjacent 3G cell due to traffic .......................................................................................136-7 136.10 C902430010 Number of handovers from selected cell to the adjacent 3G cell due to traffic ............................................................................................136-7 136.11 C902430011 Number of successful handovers from selected cell to the adjacent 3G cell due to traffic .........................................................................136-8 136.12 C902430012 Number of handover attempts from selected cell to the adjacent 3G cell due to saving call ..................................................................136-9 136.13 C902430013 Number of handovers from selected cell to the adjacent 3G cell due to saving call.....................................................................................136-9 136.14 C902430014 Number of successful handovers from selected cell to the adjacent 3G cell due to saving call ................................................................136-10 136.15 C902430015 Number of few MS MR received before connection failure after handover from adjacent 3G cell ....................................................................136-10
CCXV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

136.16 C902430016 Number of Handovers From Adjacent 3G Cell to the Selected Cell............................................................................................................. 136-11

Chapter 137 802.3ah Measurement....................................................... 137-1

137.1 C902440001 Number of the received information packet................................137-1 137.2 C902440002 Number of the transmitted information packet............................137-2 137.3 C902440003 Number of the received loopback control packet........................137-2 137.4 C902440004 Number of the transmitted loopback control packet ....................137-3 137.5 C902440005 Number of the received variable request packet ........................137-3 137.6 C902440006 Number of the transmitted variable request packet ....................137-4 137.7 C902440007 Number of the received variable response packet......................137-4 137.8 C902440008 Number of the transmitted variable response packet ..................137-5 137.9 C902440009 Number of the received event packet ........................................137-5 137.10 C902440010 Number of the transmitted event packet ..................................137-6 137.11 C902440011 Number of the received specific packet....................................137-6 137.12 C902440012 Number of the transmitted specific packet ...............................137-7 137.13 C902440013 Number of the received unsupport packet ...............................137-7 137.14 C902440014 Number of the transmitted unsupport packet............................137-8

Chapter 138 RQ Measurement (Ru) ...................................................... 138-1

138.1 C902450003 Number of Samples With UL RQ=0 on SDCCH .........................138-2 138.2 C902450004 Number of Samples With UL RQ=1 on SDCCH .........................138-2 138.3 C902450005 Number of Samples With UL RQ=2 on SDCCH .........................138-3 138.4 C902450006 Number of Samples With UL RQ=3 on SDCCH .........................138-3 138.5 C902450007 Number of Samples With UL RQ=4 on SDCCH .........................138-4 138.6 C902450008 Number of Samples With UL RQ=5 on SDCCH .........................138-4 138.7 C902450009 Number of Samples With UL RQ=6 on SDCCH .........................138-5 138.8 C902450010 Number of Samples With UL RQ=7 on SDCCH .........................138-5 138.9 C902450011 Number of Samples With DL RQ=0 on SDCCH .........................138-6 138.10 C902450012 Number of Samples With DL RQ=1 on SDCCH .......................138-6 138.11 C902450013 Number of Samples With DL RQ=2 on SDCCH .......................138-7 138.12 C902450014 Number of Samples With DL RQ=3 on SDCCH .......................138-7 138.13 C902450015 Number of Samples With DL RQ=4 on SDCCH .......................138-8 138.14 C902450016 Number of Samples With DL RQ=5 on SDCCH .......................138-8 138.15 C902450017 Number of Samples With DL RQ=6 on SDCCH .......................138-9 138.16 C902450018 Number of Samples With DL RQ=7 on SDCCH .......................138-9 138.17 C902450019 Number of Samples With UL RQ=0 on TCH ..........................138-10 138.18 C902450020 Number of Samples With UL RQ=1 on TCH ..........................138-10 138.19 C902450021 Number of Samples With UL RQ=2 on TCH .......................... 138-11
CCXVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

138.20 C902450022 Number of Samples With UL RQ=3 on TCH .......................... 138-11 138.21 C902450023 Number of Samples With UL RQ=4 on TCH ..........................138-12 138.22 C902450024 Number of Samples With UL RQ=5 on TCH ..........................138-12 138.23 C902450025 Number of Samples With UL RQ=6 on TCH ..........................138-13 138.24 C902450026 Number of Samples With UL RQ=7 on TCH ..........................138-13 138.25 C902450027 Number of Samples With DL RQ=0 on TCH ..........................138-14 138.26 C902450028 Number of Samples With DL RQ=1 on TCH ..........................138-14 138.27 C902450029 Number of Samples With DL RQ=2 on TCH ..........................138-15 138.28 C902450030 Number of Samples With DL RQ=3 on TCH ..........................138-15 138.29 C902450031 Number of Samples With DL RQ=4 on TCH ..........................138-16 138.30 C902450032 Number of Samples With DL RQ=5 on TCH ..........................138-16 138.31 C902450033 Number of Samples With DL RQ=6 on TCH ..........................138-17 138.32 C902450034 Number of Samples With DL RQ=7 on TCH ..........................138-17

Chapter 139 Directed retry Measurement ............................................ 139-1

139.1 C902460001 Number of Voice TCH/F Seizure Attempts for Directed Retry ......139-3 139.2 C902460002 Number of Voice TCH/F Seizure Success for Directed Retry ......139-3 139.3 C902460003 Number of Voice TCH/F Seizure Failure for Directed Retry.........139-4 139.4 C902460004 Number of Data TCH/F Seizure Attempts for Directed Retry.......139-4 139.5 C902460005 Number of Data TCH/F Seizure Success for Directed Retry .......139-5 139.6 C902460006 Number of Data TCH/F Seizure Failures for Directed Retry ........139-5 139.7 C902460007 Number of TCH/F Allocation Attempts for Directed Retry (Speech Version 1) ........................................................................................139-6 139.8 C902460008 Number of TCH/F Allocation Success for Directed Retry (Speech Version 1) ........................................................................................139-6 139.9 C902460009 Number of TCH/F Allocation Failure for Directed Retry (Speech Version 1) .....................................................................................................139-7 139.10 C902460010 Number of TCH/F Allocation Attempts for Directed Retry (Speech Version 2) ........................................................................................139-7 139.11 C902460011 Number of TCH/F Allocation Success for Directed Retry (Speech Version 2) ........................................................................................139-8 139.12 C902460012 Number of TCH/F Allocation Failure for Directed Retry (Speech Version 2) ........................................................................................139-8 139.13 C902460013 Number of TCH/F Allocation Attempts for Directed Retry (Speech Version 3) ........................................................................................139-9 139.14 C902460014 Number of TCH/F Allocation Success for Directed Retry (Speech Version 3) ......................................................................................139-10 139.15 C902460015 Number of TCH/F Allocation Failure for Directed Retry (Speech Version 3) ......................................................................................139-10

CCXVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

139.16 C902460016 Number of TCH/F Allocation Attempts for Directed Retry (Speech Version 4) ...................................................................................... 139-11 139.17 C902460017 Number of TCH/F Allocation Success for Directed Retry (Speech Version 4) ...................................................................................... 139-11 139.18 C902460018 Number of TCH/F Allocation Failure for Directed Retry (Speech Version 4) ......................................................................................139-12 139.19 C902460019 Number of TCH/F Allocation Attempts for Directed Retry (Speech Version 5) ......................................................................................139-12 139.20 C902460020 Number of TCH/F Allocation Success for Directed Retry (Speech Version 5) ......................................................................................139-13 139.21 C902460021 Number of TCH/F Allocation Failure for Directed Retry (Speech Version 5) ......................................................................................139-13 139.22 C902460022 Number of Data TCH/F Allocation Attempts for Directed Retry ..........................................................................................................139-14 139.23 C902460023 Number of Data TCH/F Allocation Success for Directed Retry ..........................................................................................................139-14 139.24 C902460024 Number of Data TCH/F Allocation Failure for Directed Retry ..........................................................................................................139-15 139.25 C902460025 Number of Voice TCH/F Assignment Attempts for Directed Retry ..........................................................................................................139-15 139.26 C902460026 Number of Voice TCH/F Assignment Success for Directed Retry ..........................................................................................................139-16 139.27 C902460027 Number of Voice TCH/F Assignment Failure for Directed Retry ..........................................................................................................139-16 139.28 C902460028 Number of Data TCH/F Assignment Attempts for Directed Retry ..........................................................................................................139-17 139.29 C902460029 Number of Data TCH/F Assignment Success for Directed Retry ..........................................................................................................139-17 139.30 C902460030 Number of Data TCH/F Assignment Failure for Directed Retry ..........................................................................................................139-18 139.31 C902460031 Number of Voice TCH/H Seizure Attempts for Directed Retry ..........................................................................................................139-18 139.32 C902460032 Number of Voice TCH/H Seizure Success for Directed Retry ..........................................................................................................139-19 139.33 C902460033 Number of Voice TCH/H Seizure Failure for Directed Retry ......139-19 139.34 C902460034 Number of Data TCH/H Seizure Attempts for Directed Retry ..........................................................................................................139-20 139.35 C902460035 Number of Data TCH/H Seizure Success for Directed Retry ..........................................................................................................139-20 139.36 C902460036 Number of Data TCH/H Seizure Failures for Directed Retry ..........................................................................................................139-21
CCXVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

139.37 C902460037 Number of TCH/H Allocation Attempts for Directed Retry (Speech Version 1) ......................................................................................139-21 139.38 C902460038 Number of TCH/H Allocation Success for Directed Retry (Speech Version 1) ......................................................................................139-22 139.39 C902460039 Number of TCH/H Allocation Failure for Directed Retry (Speech Version 1) ......................................................................................139-22 139.40 C902460040 Number of TCH/H Allocation Attempts for Directed Retry (Speech Version 3) ......................................................................................139-23 139.41 C902460041 Number of TCH/H Allocation Success for Directed Retry (Speech Version 3) ......................................................................................139-23 139.42 C902460042 Number of TCH/H Allocation Failure for Directed Retry (Speech Version 3) ......................................................................................139-24 139.43 C902460043 Number of TCH/H Allocation Attempts for Directed Retry (Speech Version 4) ......................................................................................139-24 139.44 C902460044 Number of TCH/H Allocation Success for Directed Retry (Speech Version 4) ......................................................................................139-25 139.45 C902460045 Number of TCH/H Allocation Failure for Directed Retry (Speech Version 4) ......................................................................................139-25 139.46 C902460046 Number of Data TCH/H Allocation Attempts for Directed Retry ..........................................................................................................139-26 139.47 C902460047 Number of Data TCH/H Allocation Success for Directed Retry ..........................................................................................................139-27 139.48 C902460048 Number of Data TCH/H Allocation Failure for Directed Retry ..........................................................................................................139-27 139.49 C902460049 Number of Voice TCH/H Assignment Attempts for Directed Retry ..........................................................................................................139-28 139.50 C902460050 Number of Voice TCH/H Assignment Success for Directed Retry ..........................................................................................................139-28 139.51 C902460051 Number of Voice TCH/H Assignment Failure for Directed Retry ..........................................................................................................139-29 139.52 C902460052 Number of Data TCH/H Assignment Attempts for Directed Retry ..........................................................................................................139-29 139.53 C902460053 Number of Data TCH/H Assignment Success for Directed Retry ..........................................................................................................139-30 139.54 C902460054 Number of Data TCH/H Assignment Failure for Directed Retry ..........................................................................................................139-30 139.55 C902460055 Number of Forced Internal Directed Retry Attempts (Voice) ........................................................................................................139-31 139.56 C902460056 Number of Forced Internal Directed Retry Attempts (Data) ......139-31 139.57 C902460057 Number of Forced External Directed Retry Attempts (Voice) ........................................................................................................139-32
CCXIX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

139.58 C902460058 Number of Forced External Directed Retry Attempts (Data) .........................................................................................................139-32 139.59 C902460059 Number of Normal Internal Directed Retry Attempts (Voice) ........................................................................................................139-33 139.60 C902460060 Number of Normal Internal Directed Retry Attempts (Data) ......139-33 139.61 C902460061 Number of Normal External Directed Retry Attempts (Voice) ........................................................................................................139-34 139.62 C902460062 Number of Normal External Directed Retry Attempts (Data) .........................................................................................................139-34 139.63 C902460063 Number of Forced Internal Directed Retry Success (Voice) ......139-35 139.64 C902460064 Number of Forced Internal Directed Retry Success (Data) ......139-35 139.65 C902460065 Number of Forced External Directed Retry Success (Voice) ........................................................................................................139-36 139.66 C902460066 Number of Forced External Directed Retry Success (Data) ......139-36 139.67 C902460067 Number of Normal Internal Directed Retry Success (Voice) ........................................................................................................139-37 139.68 C902460068 Number of Normal Internal Directed Retry Success (Data) ......139-37 139.69 C902460069 Number of Normal External Directed Retry Success (Voice) ........................................................................................................139-38 139.70 C902460070 Number of Normal External Directed Retry Success (Data) .........................................................................................................139-38

Chapter 140 General Handover Measurement 2.................................. 140-1

140.1 C902500001 Number of Handover Attempt From HR (V1) to FR Due to High Load in Subcell 2 ...........................................................................................140-1 140.2 C902500002 Number of Handover From HR (V1) to FR Due to High Load in Subcell 2.......................................................................................................140-2 140.3 C902500003 Number of Handover Success From HR (V1) to FR Due to High Load in Subcell 2 ...........................................................................................140-2 140.4 C902500004 Number of Handover Attempt From HR (V3) to FR Due to High Load in Subcell 2 ...........................................................................................140-3 140.5 C902500005 Number of Handover From HR (V3) to FR Due to High Load in Subcell 2.......................................................................................................140-3 140.6 C902500006 Number of Handover Success From HR (V3) to FR Due to High Load in Subcell 2 ...........................................................................................140-4 140.7 C902500007 Number of Back to Source Cell Successful When Handover.......140-4 140.8 C902500008 Number of Back to Source Cell Failure When Handover.............140-5 140.9 C902500009 Number of Handover Optimize When Handover Command Lost ..............................................................................................................140-5 140.10 C902500010 Number of Dual Frequence Handover Attempts .......................140-6 140.11 C902500011 Number of Dual Frequence Handover .....................................140-6
CCXX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

140.12 C902500012 Number of Dual Frequence Handover Success .......................140-7 140.13 C902500013 Number of UL_Interf Intra-Cell Handover Which Does Not Meet the Required of Interference Band ..........................................................140-7 140.14 C902500014 Number of DL_Interf Intra-Cell Handover Which Does Not Meet the Required of Interference Band ..........................................................140-8

Chapter 141 TSEC Measurement .......................................................... 141-1

141.1 C902530001 Device Type ............................................................................141-2 141.2 C902530002 Number of 64-Byte Packets Transmitted and Received ..............141-2 141.3 C902530003 Number of 65- to 127-Byte Packets Transmitted and Received.......................................................................................................141-2 141.4 C902530004 Number of 128- to 255-Byte Packets Transmitted and Received.......................................................................................................141-3 141.5 C902530005 Number of 256- to 511-Byte Packets Transmitted and Received.......................................................................................................141-3 141.6 C902530006 Number of 512- to 1023-Byte Packets Transmitted and Received.......................................................................................................141-4 141.7 C902530007 Number of 1024- to 1518-Byte Packets Transmitted and Received.......................................................................................................141-4 141.8 C902530008 Number of 1519- to 1522-Byte Packets Transmitted and Received.......................................................................................................141-4 141.9 C902530009 Number of Bytes Transmitted ...................................................141-5 141.10 C902530010 Number of Packets Transmitted..............................................141-5 141.11 C902530011 Number of Packets Transmitted That Have a Multicast Destination....................................................................................................141-5 141.12 C902530012 Number of Packets Transmitted That Have a Broadcast Destination....................................................................................................141-6 141.13 C902530013 Number of Pause Control Packets Transmitted........................141-6 141.14 C902530014 Number of Deferral Packets Transmitted .................................141-6 141.15 C902530015 Number of Excessive Deferral Packets Transmitted .................141-7 141.16 C902530016 Number of Single Collision Packets Transmitted ......................141-7 141.17 C902530017 Number of Multiple Collision Packets Transmitted ....................141-7 141.18 C902530018 Number of Late Collision Packets Transmitted .........................141-8 141.19 C902530019 Number of Excessive Collision Packets Transmitted ................141-8 141.20 C902530020 Number of Collision Packets Transmitted ................................141-8 141.21 C902530021 Number of Packets Transmitted and Dropped..........................141-9 141.22 C902530022 Number of Jabber Packets Transmitted...................................141-9 141.23 C902530023 Number of FCS Error Packets Transmitted ..............................141-9 141.24 C902530024 Number of Control Packets Transmitted ................................141-10 141.25 C902530025 Number of Oversize Packets Transmitted..............................141-10
CCXXI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

141.26 C902530026 Number of Undersize Packets Transmitted ............................141-10 141.27 C902530027 Number of Fragment Packets Transmitted............................. 141-11 141.28 C902530028 Number of Bytes Received ................................................... 141-11 141.29 C902530029 Number of Packets Received ............................................... 141-11 141.30 C902530030 Number of FCS Error Packets Received ...............................141-12 141.31 C902530031 Number of Packets Received That Have a Multicast Destination..................................................................................................141-12 141.32 C902530032 Number of Packets Received That Have a Broadcast Destination..................................................................................................141-12 141.33 C902530033 Number of Control Packets Received....................................141-13 141.34 C902530034 Number of Pause Control Packets Received .........................141-13 141.35 C902530035 Number of Unknown OP Code Packets Received ..................141-13 141.36 C902530036 Number of Alignment Error Packets Received .......................141-14 141.37 C902530037 Number of Length Error Packets Received ............................141-14 141.38 C902530038 Number of Code Error Packets Received ..............................141-14 141.39 C902530039 Number of Carrier Sense Error Packets Received..................141-15 141.40 C902530040 Number of Undersize Packets Received ...............................141-15 141.41 C902530041 Number of Oversize Packets Received .................................141-15 141.42 C902530042 Number of Fragment Packets Received ................................141-16 141.43 C902530043 Number of Jabber Packets Received ....................................141-16 141.44 C902530044 Number of Packets Received and Dropped ...........................141-16

Chapter 142 BCM56XXX Measurement ................................................ 142-1

142.1 C902540001 Number of Total Octet Received (Low 32 Bit) ............................142-2 142.2 C902540002 Number of Total Octet Received (High 32 Bit)............................142-2 142.3 C902540003 Number of Good Frames Received That Have a Unicast Destination Address.......................................................................................142-2 142.4 C902540004 Number of Good Frames Received That Have a Multicast Destination....................................................................................................142-3 142.5 C902540005 Number of Good Frames Received That Have a Broadcast Destination....................................................................................................142-3 142.6 C902540006 Number of Received Frames That is Discarded .........................142-3 142.7 C902540007 Number of Frames Received That Are Error..............................142-4 142.8 C902540008 Number of Total Octet Transmitted (Low 32 Bit) .........................142-4 142.9 C902540009 Number of Total Octet Transmitted (High 32 Bit) ........................142-4 142.10 C902540010 Number of Good Frames Transmitted That Have a Unicast Destination Address.......................................................................................142-5 142.11 C902540011 Number of Good Frames Transmitted That Have a Multicast Destination....................................................................................................142-5

CCXXII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

142.12 C902540012 Number of Good Frames Transmitted That Have a Broadcast Destination....................................................................................................142-5 142.13 C902540013 Number of Transmitted Frames That is Discarded....................142-6 142.14 C902540014 Number of Frames Transmitted That is Error ...........................142-6 142.15 C902540015 Number of Fragment Frames Received...................................142-6 142.16 C902540016 Number of Jabber Frames Received.......................................142-7 142.17 C902540017 Number of Aborted Transmitted Frames..................................142-7 142.18 C902540018 Number of Single Difer Frames Transmitted ............................142-7 142.19 C902540019 Number of Multi Difer Frames Transmitted ..............................142-8 142.20 C902540020 Number of Late Collision Frames Transmitted .........................142-8 142.21 C902540021 Number of Multi Collision Frames Transmitted .........................142-8 142.22 C902540022 Number of Collision Frames Transmitted .................................142-9 142.23 C902540023 Number of Single Collision Frames Transmitted.......................142-9 142.24 C902540024 Number of Excessive Collision Frames Transmitted .................142-9

Chapter 143 TRUNKSET Measurement ................................................ 143-1

143.1 C902550001 Number of Octets Received (Low 4B) .......................................143-1 143.2 C902550002 Number of Octets Received (High 4B) ......................................143-2 143.3 C902550003 Number of Packets Received That Are Addressed to a Unicast Address ........................................................................................................143-2 143.4 C902550004 Number of Packets Received That Are Directed to a Multicast Address ........................................................................................................143-2 143.5 C902550005 Number of Packets Received That Are Directed to the Broadcast Address ........................................................................................143-3 143.6 C902550006 Number of Packets Received That Are Discarded......................143-3 143.7 C902550007 Number of Packets Received That Are Error .............................143-3 143.8 C902550008 Number of Octets Transmitted (Low 4B)....................................143-4 143.9 C902550009 Number of Octets Transmitted (High 4B) ...................................143-4 143.10 C902550010 The Number of Packets Transmitted That Are Addressed to a Unicast Address ............................................................................................143-4 143.11 C902550011 Number of Packets Transmitted That Are Directed to a Multicast Address ..........................................................................................143-5 143.12 C902550012 Number of Packets Transmitted That Are Directed to the Broadcast Address ........................................................................................143-5 143.13 C902550013 Number of Packets Transmitted That Are Discarded ................143-5 143.14 C902550014 Number of Packets Transmitted That Are Error........................143-6

Chapter 144 HW Measurement.............................................................. 144-1

144.1 C902560001 PCM Link Connection Count ....................................................144-1 144.2 C902560002 PCM Link Disconnection Count ................................................144-1
CCXXIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

144.3 C902560003 PCM Link Connect Parameters Error Count ..............................144-2 144.4 C902560004 PCM Link Disconnect Parameters Error Count ..........................144-2 144.5 C902560005 PCM Link Duplicated Connect Count ........................................144-2 144.6 C902560006 PCM Link Duplicated Disconnect Count ....................................144-3

Chapter 145 TFS Measurement ............................................................. 145-1

145.1 C902570001 Error Count .............................................................................145-1

Chapter 146 VSC874 Measurement ...................................................... 146-1

146.1 C902580001 Number of Queue 0 HSSL 0 Received SFrames .......................146-2 146.2 C902580002 Number of Queue 0 HSSL 1 Received SFrames .......................146-2 146.3 C902580003 Number of Queue 0 HSSL 2 Received SFrames .......................146-2 146.4 C902580004 Number of Queue 0 HSSL 3 Received SFrames .......................146-3 146.5 C902580005 Number of Queue 0 HSSL 4 Received SFrames .......................146-3 146.6 C902580006 Number of Queue 0 HSSL 5 Received SFrames .......................146-3 146.7 C902580007 Number of Queue 0 HSSL 6 Received SFrames .......................146-4 146.8 C902580008 Number of Queue 0 HSSL 7 Received SFrames .......................146-4 146.9 C902580009 Number of Queue 1 HSSL 0 Received SFrames .......................146-4 146.10 C902580010 Number of Queue 1 HSSL 1 Received SFrames......................146-5 146.11 C902580011 Number of Queue 1 HSSL 2 Received SFrames ......................146-5 146.12 C902580012 Number of Queue 1 HSSL 3 Received SFrames......................146-5 146.13 C902580013 Number of Queue 1 HSSL 4 Received SFrames......................146-6 146.14 C902580014 Number of Queue 1 HSSL 5 Received SFrames......................146-6 146.15 C902580015 Number of Queue 1 HSSL 6 Received SFrames......................146-6 146.16 C902580016 Number of Queue 1 HSSL 7 Received SFrames......................146-7 146.17 C902580017 Number of Queue 0 HSSL 0 Transmitted SFrames ..................146-7 146.18 C902580018 Number of Queue 0 HSSL 1 Transmitted SFrames ..................146-7 146.19 C902580019 Number of Queue 0 HSSL 2 Transmitted SFrames ..................146-8 146.20 C902580020 Number of Queue 0 HSSL 3 Transmitted SFrames ..................146-8 146.21 C902580021 Number of Queue 0 HSSL 4 Transmitted SFrames ..................146-8 146.22 C902580022 Number of Queue 0 HSSL 5 Transmitted SFrames ..................146-9 146.23 C902580023 Number of Queue 0 HSSL 6 Transmitted SFrames ..................146-9 146.24 C902580024 Number of Queue 0 HSSL 7 Transmitted SFrames ..................146-9 146.25 C902580025 Number of Queue 1 HSSL 0 Transmitted SFrames ................146-10 146.26 C902580026 Number of Queue 1 HSSL 1 Transmitted SFrames ................146-10 146.27 C902580027 Number of Queue 1 HSSL 2 Transmitted SFrames ................146-10 146.28 C902580028 Number of Queue 1 HSSL 3 Transmitted SFrames ................ 146-11 146.29 C902580029 Number of Queue 1 HSSL 4 Transmitted SFrames ................ 146-11 146.30 C902580030 Number of Queue 1 HSSL 5 Transmitted SFrames ................ 146-11
CCXXIV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

146.31 C902580031 Number of Queue 1 HSSL 6 Transmitted SFrames ................146-12 146.32 C902580032 Number of Queue 1 HSSL 7 Transmitted SFrames ................146-12

Chapter 147 BRS Call MSC table interface Measurement .................. 147-1
147.1 C902590001 Number of MCS Table Initial Failed ...........................................147-2 147.2 C902590002 Number of L2 Item Added to MCS Failed ..................................147-3 147.3 C902590003 L2 Item Deleted From MCS Failed Times ..................................147-3 147.4 C902590004 Route Item Added to MCS Failed Times....................................147-3 147.5 C902590005 Route Item Deleted From MCS Failed Times.............................147-4 147.6 C902590006 ARP Item Added to MCS Success Times ..................................147-4 147.7 C902590007 ARP Item Added to MCS Failed Times......................................147-5 147.8 C902590008 ARP Item Deleted From MCS Success Times ...........................147-5 147.9 C902590009 ARP Item Deleted From MCS Failed Times...............................147-5 147.10 C902590010 Virtual IP Added to MCS Failed Times.....................................147-6 147.11 C902590011 Virtual IP Deleted From MCS Failed Times ..............................147-6 147.12 C902590012 Interface Table Item Deleted From MCS Failed Times ..............147-7 147.13 C902590013 Interface Status Set to MCS Failed Times ...............................147-7 147.14 C902590014 Outer Interface MAC Set to MCS Failed Times ........................147-7 147.15 C902590015 Outer Interface MTU Set to MCS Failed Times ........................147-8 147.16 C902590016 Outer Interface IP Added to MCS Failed Times........................147-8 147.17 C902590017 Outer Interface IP Delete From MCS Failed Times...................147-9 147.18 C902590018 Inner Interface IP Settled to MCS Failed Times........................147-9 147.19 C902590019 MCS Writing Single and Double Frame Information to SCRATCH Failed Times.................................................................................147-9 147.20 C902590020 Sending Packets to MCS Failed Times..................................147-10 147.21 C902590021 Adding MCS Static NAT Local Table Failed Times..................147-10 147.22 C902590022 Deleting MCS Static NAT Local Table Failed Times................147-10 147.23 C902590023 Adding MCS Static NAT Global Table Failed Times ................ 147-11 147.24 C902590024 Deleting MCS Static NAT Global Table Failed Times .............. 147-11 147.25 C902590025 Searching MCS Static NAT Table Failed Times......................147-12 147.26 C902590026 Adding MCS Dynamic NAT and NAPT Prime (Local) Table Failed Times................................................................................................147-12 147.27 C902590027 Deleting MCS Dynamic NAT and NAPT Prime (Local) Table Failed Times................................................................................................147-12 147.28 C902590028 Adding MCS Dynamic NAT and NAPT Sub (Global) Table Failed Times................................................................................................147-13 147.29 C902590029 Deleting MCS Dynamic NAT and NAPT Sub (Global) Table Failed Times................................................................................................147-13

CCXXV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

147.30 C902590030 Searching MCS Dynamic NAT and NAPT Table Failed Times..........................................................................................................147-13 147.31 C902590031 Adding MCS Decide-Table Failed Times................................147-14 147.32 C902590032 Deleting MCS Decide-Table Failed Times..............................147-14 147.33 C902590033 MCS Failed to Add VPN Attributes........................................147-15 147.34 C902590034 MCS Failed to Delete VPN Attributes ....................................147-15 147.35 C902590035 MCS Failed to Set Port Native ..............................................147-15 147.36 C902590036 MCS Failed to Add Sub_Interface VPN Attributes ..................147-16 147.37 C902590037 MCS Failed to Delete Sub_Interface VPN Attributes ..............147-16 147.38 C902590038 MCS Failed to Set vrf_id of Physic Port .................................147-16 147.39 C902590039 Adding Mapping List to MCS Prime Index Table Failed Times..........................................................................................................147-17 147.40 C902590040 Deleting Mapping List to MCS Prime Index Table Failed Times..........................................................................................................147-17 147.41 C902590041 Adding Mapping List to MCS Sub Index Table Failed Times..........................................................................................................147-17 147.42 C902590042 Deleting Mapping List to MCS Sub Index Table Failed Times..........................................................................................................147-18 147.43 C902590043 Adding MCS Prefix Failed Times...........................................147-18 147.44 C902590044 Deleting MCS Prefix Failed Times.........................................147-18 147.45 C902590045 Searching MCS Mapping List Failed Times............................147-19 147.46 C902590046 Adding MCS IPV4 Decide-Table Failed Times .......................147-19 147.47 C902590047 Deleting MCS IPV4 Decide-Table Failed Times......................147-20 147.48 C902590048 Adding MCS IPV6 Prefix Decide-Table Failed Times ..............147-20 147.49 C902590049 Deleting MCS IPV6 Prefix Decide-Table Failed Times ............147-20 147.50 C902590050 Adding MCS Sub Decide-Table Failed Times.........................147-21 147.51 C902590051 Deleting MCS Sub Decide-Table Failed Times .......................147-21 147.52 C902590052 Adding MCS NAT-PT Board List Failed Times .......................147-21 147.53 C902590053 Deleting MCS NAT-PT Board List Failed Times......................147-22 147.54 C902590054 Sending Packets to MCS Failed Times..................................147-22

Chapter 148 INGRESS/EGRESS direction of mcs op fail Measurement ...................................................................................... 148-1

148.1 C902600001 Number of Failed Operation When Configuring WRED Table to MCS .............................................................................................................148-1 148.2 C902600002 Number of Failed Operation When Configuring Flow METER Table to MCS ................................................................................................148-2 148.3 C902600003 Number of Failed Operation When Configuring Port METER Table to MCS ................................................................................................148-2

CCXXVI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

148.4 C902600004 Number of Failed Operation When Configuring L1 Table to MCS .............................................................................................................148-2 148.5 C902600005 Number of Failed Operation When Configuring Simple QOS Table to MCS ................................................................................................148-3 148.6 C902600006 Number of Failed Operation When Configuring Simple System QOS Table to MCS ........................................................................................148-3

Chapter 149 82559 Measurement.......................................................... 149-1

149.1 C902610001 Number of Transmitted Good Frames .......................................149-1 149.2 C902610002 Number of Transmitted Maximum Collisions (MAXCOL) Errors ...........................................................................................................149-2 149.3 C902610003 Number of Transmitted Late Collisions (LATECOL) Errors..........149-2 149.4 C902610004 Number of Transmitted Underrun Errors....................................149-2 149.5 C902610005 Number of Transmitted Lost Carrier Sense (CRS)......................149-3 149.6 C902610006 Number of Transmitted Deferred...............................................149-3 149.7 C902610007 Number of Transmitted Single Collision.....................................149-3 149.8 C902610008 Number of Transmitted Multiple Collisions .................................149-4 149.9 C902610009 Number of Transmitted Total Collisions .....................................149-4 149.10 C902610010 Number of Received Good Frames .........................................149-4 149.11 C902610011 Number of Received CRC Errors.............................................149-5 149.12 C902610012 Number of Received Alignment Errors ....................................149-5 149.13 C902610013 Number of Received Resource Errors .....................................149-5 149.14 C902610014 Number of Received Overrun Errors .......................................149-6 149.15 C902610015 Number of Received Collision Detect (CDT) Errors ..................149-6 149.16 C902610016 Number of Received Short Frame Errors.................................149-6

Chapter 150 CELL Paging Measurement ............................................. 150-1

150.1 C902630001 Number of PS Paging Message Discarded................................150-1 150.2 C902630002 Number of CS Paging Message Discarded................................150-1

Appendix A Corresponding Relationship between Basic Measurement Counters and General Measurement Counters ......... A-1 Figures............................................................................................................. I Tables .....................................................................................................CXXIII

CCXXVII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

CCXXVIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

About This Manual

Purpose
This manual explains the description, usage, and measurement point of each performance counter in ZXG10 iBSC Subsystem. It helps user analyze and locate faults through querying counters.

Intended Audience
l l l System Engineer Testing Engineer Planning Engineer

What Is in This Manual

This manual contains the following chapters.
Section Chapter 1, PS Basic Measurement (BSC) Chapter 2, PS Basic Measurement (Cell) Chapter 3, CPU Load Measurement Summary Introduces the detailed information about counters related to PS basic measurement (BSC). Introduces the detailed information about counters related to PS basic measurement (Cell). Introduces the detailed information about counters related to CPU load measurement. Chapter 4, CS Basic Measurement Introduces the detailed information about counters related to CS basic measurement. Chapter 5, Configuration Management Information Basic Measurement Chapter 6, Downlink Data TBF Measurement Chapter 7, Uplink Data TBF Measurement Chapter 8, Data Flow Measurement Introduces the detailed information about counters related to downlink data TBF measurement. Introduces the detailed information about counters related to uplink data TBF measurement. Introduces the detailed information about counters related to data flow. Chapter 9, Uplink-Downlink RLC Statistic Measurement Chapter 10, PS Resource Used Statistic Measurement Introduces the detailed information about counters related to uplink/downlink RLC statistic measurement. Introduces the detailed information about counters related to PS resource used statistic measurement. Introduces the detailed information about counters related to configuration management information basic measurement.

I SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Section Chapter 11, RMM Assignment Measurement Chapter 12, Handover Cause Measurement Chapter 13, RMM Call Drop Measurement Chapter 14, Radio Resource Availability Measurement Chapter 15, General Handover Measurement Chapter 16, Adjacent Cell Handover Measurement Chapter 17, Radio Access Measurement Chapter 18, Radio Measurement

Summary Introduces the detailed information about counters related to RMM assignment measurement. Introduces the detailed information about counters related to handover cause measurement. Introduces the detailed information about counters related to RMM call drop measurement. Introduces the detailed information about counters related to radio resource availability measurement. Introduces the detailed information about counters related to general handover measurement. Introduces the detailed information about counters related to adjacent cell handover measurement. Introduces the detailed information about counters related to radio access measurement. Introduces the detailed information about counters related to radio measurement.

Chapter 19, Sub Cell Statistics

Introduces the detailed information about counters related to sub cell statistics.

Chapter 20, MS TA Measurement

Introduces the detailed information about counters related to MS TA measurement.

Chapter 21, SAPI3 Measurement

Introduces the detailed information about counters related to SAPI3 measurement.

Chapter 22, Uplink and Downlink PACCH Statistics Chapter 23, Downlink GPRS data TBF Statistics Chapter 24, Downlink EGPRS data TBF Statistics Chapter 25, Uplink GPRS data TBF Statistics Chapter 26, Uplink EGPRS Data TBF Statistics Chapter 27, BSSGP Flow Statistics

Introduces the detailed information about counters related to uplink and downlink PACCH statistics. Introduces the detailed information about counters related to downlink GPRS data TBF statistics. Introduces the detailed information about counters related to downlink EGPRS data TBF statistics. Introduces the detailed information about counters related to uplink GPRS data TBF statistics. Introduces the detailed information about counters related to uplink EGPRS data TBF statistics. Introduces the detailed information about counters related to BSSGP flow statistics.

Chapter 28, TRX Measurement

Introduces the detailed information about counters related to TRX measurement.

II SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Section Chapter 29, Gb Interface Message Statistics Chapter 30, Timeslot Measurement

Summary Introduces the detailed information about counters related to Gb interface message statistics. Introduces the detailed information about counters related to timeslot measurement.

Chapter 31, SDCCH Measurement

Introduces the detailed information about counters related to SDCCH measurement.

Chapter 32, TCH/F Measurement

Introduces the detailed information about counters related to TCH/F measurement.

Chapter 33, TCH/H Measurement

Introduces the detailed information about counters related to TCH/H measurement.

Chapter 34, Abis Interface Message Counter Measurement Chapter 35, Gb Message Statistics (BVC Cell) Chapter 36, NSVC Statistic Measurement Chapter 37, NSE Statistic Measurement Chapter 38, BTS TRX Measurement

Introduces the detailed information about counters related to Abis interface message counter measurement. Introduces the detailed information about counters related to Gb interface message statistics (BVC cell). Introduces the detailed information about counters related to NSVC statistic measurement. Introduces the detailed information about counters related to NSE statistic measurement. Introduces the detailed information about counters related to BTS TRX measurement.

Chapter 39, NSVC on IPGB HOST Measurement Chapter 40, GB Message on IPGB HOST Measurement Chapter 41, NSE on IPGB HOST Measurement Chapter 42, BSSMAP Message Measurement Chapter 43, A-Interface Message Measurement Chapter 44, Terrestrial Resource Availability Measurement Chapter 45, Ater Message Measurement Chapter 46, MTP2 Signaling Link Measurement

Introduces the detailed information about counters related to NSVC on IPGB HOST measurement. Introduces the detailed information about counters related to GB message on IPGB HOST measurement. Introduces the detailed information about counters related to NSE on IPGB HOST measurement. Introduces the detailed information about counters related to BSSMAP message measurement. Introduces the detailed information about counters related to A-Interface message measurement. Introduces the detailed information about counters related to terrestrial resource availability measurement. Introduces the detailed information about counters related to Ater message measurement. Introduces the detailed information about counters related to MTP2 signaling link measurement.

III SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Section Chapter 47, CPU/MEM Measurement Chapter 48, SCTP AS Measurement

Summary Introduces the detailed information about counters related to CPU/MEM measurement. Introduces the detailed information about counters related to SCTP AS measurement.

Chapter 49, IP Port Performance Statistics Chapter 50, GTRUNK Resource Statistics Chapter 51, Other Process Statistics

Introduces the detailed information about counters related to IP port performance statistics. Introduces the detailed information about counters related to GTRUNK resource statistics. Introduces the detailed information about counters related to other process statistics.

Chapter 52, FR Carried Links Statistics Chapter 53, OMP PS Service Statistics Chapter 54, SNS on OMP Statistics

Introduces the detailed information about counters related to FR carried links statistics. Introduces the detailed information about counters related to OMP PS service statistics. Introduces the detailed information about counters related to SNS on OMP statistics.

Chapter 55, IPGB StrongARM NSVC Statistics Chapter 56, IPGB StrongARM Gb Statistics Chapter 57, Queue Measurement

Introduces the detailed information about counters related to IPGB StrongARM NSVC statistics. Introduces the detailed information about counters related to IPGB StrongARM Gb statistics. Introduces the detailed information about counters related to queue measurement.

Chapter 58, Handover Synchronization Mode Measurement Chapter 59, Paging Message Measurement Chapter 60, Reserved Channel Measurement Chapter 61, SCCP Connection Measurement Chapter 62, DTM Cell Measurement

Introduces the detailed information about counters related to handover synchronization mode measurement.

Introduces the detailed information about counters related to paging message measurement. Introduces the detailed information about counters related to reserved channel measurement. Introduces the detailed information about counters related to SCCP connection measurement. Introduces the detailed information about counters related to DTM cell measurement.

Chapter 63, LAPD Measurement

Introduces the detailed information about counters related to LAPD measurement.

Chapter 64, LCS Measurement

Introduces the detailed information about counters related to LCS measurement.

IV SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Section Chapter 65, LB Global Message Measurement Chapter 66 Ater Interface Relays Measurement Chapter 67, Ater Interface SCCP Connections Measurement Chapter 68, Measurement Report Serving Cell Measurement Chapter 69, Measurement Report Adjacent Cell Measurement Chapter 70, TRX Paging Measurement Chapter 71, TRX Temperature Power Measurement Chapter 72, Terminal Ability Statistics Chapter 73, MTP3 Signaling Link Statistics Chapter 74, M3UA Performance Statistics Chapter 75, SCCP Performance Statistics Chapter 76, MTP3 Signaling Link Set Statistics Chapter 77, M3UA Error Statistics

Summary Introduces the detailed information about counters related to LB global message measurement. Introduces the detailed information about counters related to Ater interface relays measurement. Introduces the detailed information about counters related to Ater interface SCCP connections measurement. Introduces the detailed information about counters related to measurement report serving cell measurement. Introduces the detailed information about counters related to measurement report adjacent cell measurement. Introduces the detailed information about counters related to TRX paging measurement. Introduces the detailed information about counters related to TRX temperature power measurement. Introduces the detailed information about counters related to terminal ability statistics. Introduces the detailed information about counters related to MTP3 signaling link statistics. Introduces the detailed information about counters related to M3UA performance statistics. Introduces the detailed information about counters related to SCCP performance statistics. Introduces the detailed information about counters related to MTP3 signaling link set statistics. Introduces the detailed information about counters related to M3UA error statistics.

Chapter 78, M3UA AS Performance Statistics Chapter 79, Timer Statistics

Introduces the detailed information about counters related to M3UA AS performance statistics. Introduces the detailed information about counters related to timer statistics.

Chapter 80, Scheduling Performance Statistics Chapter 81, UB Memory Performance Statistics Chapter 82, Hardware and FLASH Performance Statistics

Introduces the detailed information about counters related to scheduling performance statistics. Introduces the detailed information about counters related to UB memory performance statistics. Introduces the detailed information about counters related to hardware and FLASH performance statistics.

V SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Section Chapter 83, SCTP Protocol Stack Statistics Chapter 84, SCTP Association ULP Statistics Chapter 85, SDTB Fiber Performance Statistics Chapter 86, PEB22554 E1 Performance Statistics Chapter 87, PEB22554 T1 Performance Statistics Chapter 88, MAC Port Flow Statistics Chapter 89, AMR Rate Statistics

Summary Introduces the detailed information about counters related to SCTP protocol stack statistics. Introduces the detailed information about counters related to SCTP association ULP statistics. Introduces the detailed information about counters related to SDTB fiber performance statistics. Introduces the detailed information about counters related to PEB22554 E1 performance statistics. Introduces the detailed information about counters related to PEB22554 T1 performance statistics. Introduces the detailed information about counters related to MAC port flow statistics. Introduces the detailed information about counters related to AMR rate statistics.

Chapter 90, PPP channel measurement Chapter 91, UMAC Measurement

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

Chapter 92, Downlink EGPRS2-A TBF Statistic Chapter 93, Uplink EGPRS2-A TBF Statistic Chapter 94, PS Handover Cause Measurement Chapter 95, PS General Handover Measurement Chapter 96, IURG Measurement

Introduces the detailed information about counters related to Downlink EGPRS2-A TBF Statistic. Introduces the detailed information about counters related to Uplink EGPRS2-A TBF Statistic. Introduces the detailed information about counters related to PS handover cause measurement. Introduces the detailed information about counters related to PS general handover measurement. Introduces the detailed information about counters related to IURG measurement.

Chapter 97, RTCP Measurement

Introduces the detailed information about counters related to RTCP measurement.

Chapter 98, DSP Measurement

Introduces the detailed information about counters related to DSP measurement.

Chapter 99, Access Control Measurement Chapter 100, Power Control Measurement

Introduces the detailed information about counters related to access control measurement. Introduces the detailed information about counters related to power control measurement.

VI SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Section Chapter 101, PS Adjacent Cell Handover Measurement Chapter 102, ACL Flow Statistic

Summary Introduces the detailed information about counters related to PS adjacent cell handover measurement. Introduces the detailed information about counters related to ACL Flow Statistic.

Chapter 103, LAPDm Measurement

Introduces the detailed information about counters related to LAPDm measurement.

Chapter 104, Access Control Detailed Cause Measurement Chapter 105, BSC Group Call Setup Measurement Chapter 106, VGCS Measurement

Introduces the detailed information about counters related to access control detailed cause measurement. Introduces the detailed information about counters related to BSC group call setup measurement. Introduces the detailed information about counters related to VGCS measurement.

Chapter 107, VBS Measurement

Introduces the detailed information about counters related to VBS measurement.

Chapter 108, eMLPP Measurement

Introduces the detailed information about counters related to eMLPP measurement.

Chapter 109, IFTA Process Measurement Chapter 110, IFTA TCH/F Channel Alloc Measurement Chapter 111, IFTA TCH/H Channel Alloc Measurement Chapter 112, IFTA Message Measurement Chapter 113, SDTB E1 Performance Statistic Chapter 114, Flow Control Measurement Chapter 115, SDCCH General Handover Measurement Chapter 116, Local Switch Measurement

Introduces the detailed information about counters related to IFTA Process Measurement. Introduces the detailed information about counters related to IFTA TCH/F Channel Alloc Measurement. Introduces the detailed information about counters related to IFTA TCH/H Channel Alloc Measurement. Introduces the detailed information about counters related to IFTA Message Measurement. Introduces the detailed information about counters related to SDTB E1 Performance Statistic. Introduces the detailed information about counters related to flow control measurement. Introduces the detailed information about counters related to SDCCH general handover measurement. Introduces the detailed information about counters related to local switch measurement.

Chapter 117, CIR Statistic

Introduces the detailed information about counters related to CIR Statistic.

VII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Section Chapter 118, BTS PS Statistic

Summary Introduces the detailed information about counters related to BTS PS Statistic.

Chapter 119, TRX Key PS Information Statistic Chapter 120, PS Uplink Radio Quality Statistic Measurement Chapter 121, PS Downlink Radio Quality Statistic Measurement Chapter 122, RU Measurement

Introduces the detailed information about counters related to TRX Key PS Information Statistic. Introduces the detailed information about counters related to PS Uplink Radio Quality Statistic Measurement. Introduces the detailed information about counters related to PS Downlink Radio Quality Statistic Measurement. Introduces the detailed information about counters related to RU Measurement.

Chapter 123, PS Power Control Measurement Chapter 124, VAMOS Measurement

Introduces the detailed information about counters related to PS Power Control Measurement. Introduces the detailed information about counters related to VAMOS Measurement.

Chapter 125, IP SLA PD Statistic

Introduces the detailed information about counters related to IP SLA PD Statistic.

Chapter 126, Abis Usage Measurement Chapter 127, DSP statistic on BIPB board HOST Chapter 128, Statistic on BIPB board DSP Chapter 129, IPRB DSP statistic on BIPB board HOST Chapter 130, Statistic on BIPB board IPRB DSP Chapter 131, DSP statistic on AIPB board HOST Chapter 132, Statistic on AIPB board DSP Chapter 133, DSP statistic on TIPB board HOST Chapter 134, Statistic on TIPB board DSP Chapter 135, DSP statistic on DRTB board HOST

Introduces the detailed information about counters related to Abis Usage Measurement. Introduces the detailed information about counters related to DSP statistic on BIPB board HOST. Introduces the detailed information about counters related to Statistic on BIPB board DSP. Introduces the detailed information about counters related to IPRB DSP statistic on BIPB board HOST. Introduces the detailed information about counters related to Statistic on BIPB board IPRB DSP. Introduces the detailed information about counters related to DSP statistic on AIPB board HOST. Introduces the detailed information about counters related to Statistic on AIPB board DSP. Introduces the detailed information about counters related to DSP statistic on TIPB board HOST. Introduces the detailed information about counters related to Statistic on TIPB board DSP. Introduces the detailed information about counters related to DSP statistic on DRTB board HOST.

VIII SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Section Chapter 136, Statistic on DRTB board DSP Chapter 137, DSP statistic on UPPB board HOST Chapter 138, Statistic on UPPB board DSP Chapter 139, TFO Measurement

Summary Introduces the detailed information about counters related to Statistic on DRTB board DSP. Introduces the detailed information about counters related to DSP statistic on UPPB board HOST. Introduces the detailed information about counters related to Statistic on UPPB board DSP. Introduces the detailed information about counters related to TFO Measurement.

Chapter 140, Adjacent 3G Cell Handover Measurement Chapter 141, 802.3ah Measurement

Introduces the detailed information about counters related to Adjacent 3G Cell Handover Measurement. Introduces the detailed information about counters related to 802.3ah Measurement.

Chapter 142, RQ Measurement (Ru)

Introduces the detailed information about counters related to RQ Measurement (Ru).

Chapter 143, Directed retry Measurement Chapter 144, General Handover Measurement 2 Chapter 145, TSEC Measurement

Introduces the detailed information about counters related to Directed retry Measurement. Introduces the detailed information about counters related to General Handover Measurement 2. Introduces the detailed information about counters related to TSEC Measurement.

Chapter 146, BCM56XXX Measurement Chapter 147, TRUNKSET Measurement Chapter 148, HW Measurement

Introduces the detailed information about counters related to BCM56XXX Measurement. Introduces the detailed information about counters related to TRUNKSET Measurement. Introduces the detailed information about counters related to HW Measurement.

Chapter 149, TFS Measurement

Introduces the detailed information about counters related to TFS Measurement.

Chapter 150, VSC874 Measurement

Introduces the detailed information about counters related to VSC874 Measurement.

Chapter 151, BRS Call MSC table interface Measurement Chapter 152, INGRESS/EGRESS direction of mcs op fail Measurement Chapter 153, 82559 Measurement

Introduces the detailed information about counters related to BRS Call MSC table interface Measurement. Introduces the detailed information about counters related to INGRESS/EGRESS direction of mcs op fail Measurement. Introduces the detailed information about counters related to 82559 Measurement.

IX SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Section Chapter 154, CELL Paging Measurement Appendix A, Corresponding Relationship between Basic Measurement Counters and General Measurement Counters

Summary Introduces the detailed information about counters related to CELL Paging Measurement. Introduces the detailed information about the corresponding relationship between Basic Measurement Counters and General Measurement Counters

X SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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-20110531095035-015|2013-04-25 (R1.7) 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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-9 C900040003 Number of GPRS DL TBF release due to T3191 Timeout....................2-10 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-13 C900040008 Number of GPRS DL data TBF establishment .....................................2-13 C900040009 Number of EGPRS DL TBF establishment success on PACCH ...........2-14 C900040010 Number of EGPRS DL TBF release due to N3105 overflow ................2-15 C900040011 Number of EGPRS DL TBF release due to T3191 Timeout..................2-16 C900040012 Number of EGPRS DL TBF forcing release by control plane ...............2-17 C900040013 Number of EGPRS DL TBF release due to instance suspension .........2-18 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-20 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-23 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-25 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

C900040076 Number of discarded GPRS DL LLC frames due to life time expiration .2-62 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 C900040082 Number of DL RLC pending blocks in CS2 on PDTCH ........................2-67 C900040083 Number of DL RLC pending blocks in CS3 on PDTCH ........................2-68 C900040084 Number of DL RLC pending blocks in CS4 on PDTCH ........................2-69 C900040085 Number of DL RLC NACK blocks in CS1 on PDTCH...........................2-70 C900040086 Number of DL RLC NACK blocks in CS2 on PDTCH...........................2-71 C900040087 Number of DL RLC NACK blocks in CS3 on PDTCH...........................2-72 C900040088 Number of DL RLC NACK blocks in CS4 on PDTCH...........................2-73 C900040089 Number of DL RLC new blocks in CS1 on PDTCH ..............................2-74 C900040090 Number of DL RLC new blocks in CS2 on PDTCH ..............................2-75 C900040091 Number of DL RLC new blocks in CS3 on PDTCH ..............................2-76 C900040092 Number of DL RLC new blocks in CS4 on PDTCH ..............................2-77 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 C900040095 Number of UL RLC pending blocks in CS2 on PDTCH ........................2-79 C900040096 Number of UL RLC pending blocks in CS3 on PDTCH ........................2-80 C900040097 Number of UL RLC pending blocks in CS4 on PDTCH ........................2-81 C900040098 Number of UL RLC NACK blocks in CS1 on PDTCH...........................2-82 C900040099 Number of UL RLC NACK blocks in CS2 on PDTCH...........................2-83 C900040100 Number of UL RLC NACK blocks in CS3 on PDTCH...........................2-84 C900040101 Number of UL RLC NACK blocks in CS4 on PDTCH...........................2-85 C900040102 Number of UL RLC new blocks in CS1 on PDTCH ..............................2-86 C900040103 Number of UL RLC new blocks in CS2 on PDTCH ..............................2-87 C900040104 Number of UL RLC new blocks in CS3 on PDTCH ..............................2-88 C900040105 Number of UL RLC new blocks in CS4 on PDTCH ..............................2-89 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 of channel allocation 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 of channel allocation due to LLC transmission ..........................................................................2-95 C900040114 Number of EGPRS DL TBF establishment requests ...........................2-96

2-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C900040115 Number of EGPRS DL TBF establishment failure due to database allocation failure .......................................................................................................2-97 C900040116 Number of EGPRS DL TBF resource reallocation requests due to UL TBF establishment ..................................................................................................2-98 C900040117 Number of EGPRS DL TBF resource reallocation failure due to UL TBF establishment ..................................................................................................2-99 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-101 C900040121 Number of GPRS UL TBF establishment failure due to database allocation failure .....................................................................................................2-102 C900040122 Number of GPRS UL TBF resource reallocation requests due to DL TBF establishment .................................................................................................2-103 C900040123 Number of GPRS UL TBF resource reallocation failure of channel allocation due to DL TBF establishment .................................................................2-104 C900040124 Number of GPRS UL TBF resource reallocation requests due to LLC transmission ...........................................................................................................2-105 C900040125 Number of GPRS UL TBF resource reallocation failure of channel allocation 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-107 C900040128 Number of EGPRS UL TBF establishment requests ..........................2-108 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 TBF establishment ................................................................................................. 2-110 C900040131 Number of EGPRS UL TBF resource reallocation failure of channel allocation due to DL TBF establishment ................................................................. 2-110 C900040132 Number of EGPRS UL TBF resource reallocation requests due to LLC transmission ................................................................................................... 2-111 C900040133 Number of EGPRS UL TBF resource reallocation failure of channel allocation due to LLC transmission ......................................................................... 2-112 C900040134 Number of EGPRS UL TBF resource reallocation requests for resource request .................................................................................................... 2-113 C900040135 Number of EGPRS UL TBF resource reallocation failure due to database allocation failure for resource request...................................................... 2-114 C900040136 Average number of available PDCH .................................................. 2-114 C900040137 Number of forcing conversation dynamic from PDCH to TCH by BSC ....................................................................................................................... 2-115 C900040138 Average Number of PDCH used by TBF in each cell ......................... 2-115 C900040139 Maximum number of used PDCH ...................................................... 2-116
2-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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

ZXG10 iBSC Performance Counter Reference

C900040174 Number of DL RLC pending blocks in MCS3 on PDTCH ...................2-143 C900040175 Number of DL RLC pending blocks in MCS4 on PDTCH ...................2-144 C900040176 Number of DL RLC pending blocks in MCS5 on PDTCH ...................2-145 C900040177 Number of DL RLC pending blocks in MCS6 on PDTCH ...................2-146 C900040178 Number of DL RLC pending blocks in MCS7 on PDTCH ...................2-147 C900040179 Number of DL RLC pending blocks in MCS8 on PDTCH ...................2-148 C900040180 Number of DL RLC pending blocks in MCS9 on PDTCH ...................2-149 C900040181 Number of DL RLC NACK blocks in MCS1 on PDTCH ......................2-150 C900040182 Number of DL RLC NACK blocks in MCS2 on PDTCH ......................2-151 C900040183 Number of DL RLC NACK blocks in MCS3 on PDTCH ......................2-152 C900040184 Number of DL RLC NACK blocks in MCS4 on PDTCH ......................2-153 C900040185 Number of DL RLC NACK blocks in MCS5 on PDTCH ......................2-154 C900040186 Number of DL RLC NACK blocks in MCS6 on PDTCH ......................2-155 C900040187 Number of DL RLC NACK blocks in MCS7 on PDTCH ......................2-156 C900040188 Number of DL RLC NACK blocks in MCS8 on PDTCH ......................2-157 C900040189 Number of DL RLC NACK blocks in MCS9 on PDTCH ......................2-158 C900040190 Number of DL RLC new blocks in MCS1 on PDTCH .........................2-159 C900040191 Number of DL RLC new blocks in MCS2 on PDTCH .........................2-160 C900040192 Number of DL RLC new blocks in MCS3 on PDTCH .........................2-161 C900040193 Number of DL RLC new blocks in MCS4 on PDTCH .........................2-162 C900040194 Number of DL RLC new blocks in MCS5 on PDTCH .........................2-163 C900040195 Number of DL RLC new blocks in MCS6 on PDTCH .........................2-164 C900040196 Number of DL RLC new blocks in MCS7 on PDTCH .........................2-165 C900040197 Number of DL RLC new blocks in MCS8 on PDTCH .........................2-166 C900040198 Number of DL RLC new blocks in MCS9 on PDTCH .........................2-167 C900040199 Number of UL RLC pending blocks in MCS1 on PDTCH ...................2-168 C900040200 Number of UL RLC pending blocks in MCS2 on PDTCH ...................2-169 C900040201 Number of UL RLC pending blocks in MCS3 on PDTCH ...................2-170 C900040202 Number of UL RLC pending blocks in MCS4 on PDTCH ...................2-171 C900040203 Number of UL RLC pending blocks in MCS5 on PDTCH ...................2-172 C900040204 Number of UL RLC pending blocks in MCS6 on PDTCH ...................2-173 C900040205 Number of UL RLC pending blocks in MCS7 on PDTCH ...................2-174 C900040206 Number of UL RLC pending blocks in MCS8 on PDTCH ...................2-175 C900040207 Number of UL RLC pending blocks in MCS9 on PDTCH ...................2-176 C900040208 Number of UL RLC NACK blocks in MCS1 on PDTCH ......................2-177 C900040209 Number of UL RLC NACK blocks in MCS2 on PDTCH ......................2-178 C900040210 Number of UL RLC NACK blocks in MCS3 on PDTCH ......................2-179 C900040211 Number of UL RLC NACK blocks in MCS4 on PDTCH ......................2-180 C900040212 Number of UL RLC NACK blocks in MCS5 on PDTCH ......................2-181 C900040213 Number of UL RLC NACK blocks in MCS6 on PDTCH ......................2-182 C900040214 Number of UL RLC NACK blocks in MCS7 on PDTCH ......................2-183 C900040215 Number of UL RLC NACK blocks in MCS8 on PDTCH ......................2-184 C900040216 Number of UL RLC NACK blocks in MCS9 on PDTCH ......................2-185 C900040217 Number of UL RLC new blocks in MCS1 on PDTCH .........................2-186 C900040218 Number of UL RLC new blocks in MCS2 on PDTCH .........................2-187
2-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

C900040219 Number of UL RLC new blocks in MCS3 on PDTCH .........................2-188 C900040220 Number of UL RLC new blocks in MCS4 on PDTCH .........................2-189 C900040221 Number of UL RLC new blocks in MCS5 on PDTCH .........................2-190 C900040222 Number of UL RLC new blocks in MCS6 on PDTCH .........................2-191 C900040223 Number of UL RLC new blocks in MCS7 on PDTCH .........................2-192 C900040224 Number of UL RLC new blocks in MCS8 on PDTCH .........................2-193 C900040225 Number of UL RLC new blocks in MCS9 on PDTCH .........................2-194 C900040232 Accumulated throughput of UL GPRS TBF........................................2-194 C900040233 Accumulated throughput of DL GPRS TBF........................................2-195 C900040234 Accumulated throughput of UL EGPRS TBF .....................................2-196 C900040235 Accumulated throughput of DL EGPRS TBF .....................................2-197

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.

2-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-1 Measurement Point of Number of Requests for Establishing GPRS Downlink Data TBF Before T3193 Overtime

Figure 2-2 Measurement Point of Number of Established GPRS Downlink Data TBF Using Existing Resources

Figure 2-3 Measurement Point of Number of Requests for Establishing GPRS Downlink Data TBF on Uplink GPRS TBF PACCH

Unit
Times

2-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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.

Measurement Point
When the N3105 counter value exceeds N3105Max, this counter increments. 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

The

Unit
Times

2-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.4 C900040003 Number of GPRS DL TBF release due to T3191 Timeout

Description
When BSC is transmitting the final block of the DL TBF, FBI of this block is set to the value 1, RRBP of this block will give an uplink block in which the MS must respond with a Packet Downlink Ack/Nack message, and at the same time, activate T3191. If BSC receives Packet Downlink Ack/Nack message of the MS, T3191 will stop and the DL TBF ends normally, the TFI and other resources are released. If T3191 expires, the DL TBF ends abnormally, the TFI and other resources are released.

Measurement Point
The measurement point is A1, as shown in Figure 2-5.
Figure 2-5 Measurement point of Number of GPRS DL TBF release due to T3191 Timeout

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.

2-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Figure 2-6 Measurement Point of Number of GPRS DL TBF Forcing Release by Control Plane

Unit
Times

2.6 C900040005 Number of GPRS DL TBF release 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
When the DL block assigning timer expires, this counter increments. The measurement point is A, as shown in Figure 2-7.

2-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-7 Measurement Point of Number of GPRS DL TBF Release due to Instance Suspension

Unit
Times

2.7 C900040006 Number of GPRS DL TBF release 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-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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.9 C900040008 Number of GPRS DL data 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 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-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 2-8 Measurement Point of Number of Requests for Establishing GPRS Downlink Data TBF Before T3192 Overtime

Figure 2-9 Measurement Point of Number of Established GPRS Downlink Data TBF Using Existing Resources

2-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Figure 2-10 Measurement Point of Number of Requests for Establishing GPRS Downlink Data TBF on Uplink GPRS TBF PACCH

Unit
Times

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 fails and the DL TBF is released abnormally.

Measurement Point
When the N3105 counter value exceeds N3105Max, this counter increments. measurement point is A1, as shown in Figure 2-11. The

2-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-11 Measurement Point of Number of EGPRS DL TBF Release due to N3105 Overflow

Unit
Times

2.12 C900040011 Number of EGPRS DL TBF release due to T3191 Timeout

Description
When BSC is transmitting the final block of the DL TBF, FBI of this block is set to the value 1, RRBP of this block will give an uplink block in which the MS must respond with a Packet Downlink Ack/Nack message, and at the same time, activate T3191. If BSC receives Packet Downlink Ack/Nack message of the MS, T3191 will stop and the DL TBF ends normally, the TFI and other resources are released. If T3191 expires, the DL TBF ends abnormally, the TFI and other resources are released.

Measurement Point
The measurement point is A1, as shown in Figure 2-12.

2-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Figure 2-12 Measurement point of Number of EGPRS DL TBF release due to T3191 Timeout

Unit
Times

2.13 C900040012 Number of EGPRS 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-13.
Figure 2-13 Measurement Point of Number of EGPRS DL TBF Forcing Release by Control Plane

Unit
Times

2-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.14 C900040013 Number of EGPRS DL TBF release 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
When the DL block assigning timer expires, this counter increments. The measurement point is A1, as shown in Figure 2-14.
Figure 2-14 Measurement Point of Number of EGPRS DL TBF Release due to Instance Suspension

Unit
Times

2.15 C900040014 Number of EGPRS DL TBF release 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.
2-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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.16 C900040015 Number of EGPRS 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 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 increments. The measurement point is similar to those of C900040001 and C901000014.

Unit
Times

2.17 C900040016 Number of EGPRS DL data 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 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 increments. The measurement point is similar to those of C900040001 and C901000014.

2-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.

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 simultaneous establishment

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 establishment success on PACCH

Description
When MS has a DL TBF and the TBF is being transmitted, if the UL data need to be transmitted but there is no corresponding UL TBF, then the Packet Downlink Ack message will carry the UL TBF establishment request. Usually BSS will assign the resource to MS, and then an UL TBF is established successfully.
2-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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

2-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-16 Measurement Point of Number of GPRS UL TBF Release due to N3101 Overflow

Unit
Times

2.22 C900040021 Number of GPRS UL TBF release due 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

2-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Unit
Times

2.23 C900040022 Number of GPRS UL TBF forcing release by control plane

Description
When an UL TBF establishment is held, the control plane may forcibly release this UL TBF.

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

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

Unit
Times

2.24 C900040023 Number of GPRS UL TBF release due 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.
2-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.25 C900040024 Number of GPRS UL TBF release due 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-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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.
Figure 2-21 UL TBF Flow of 1-Step Access

2-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-22 UL TBF Flow of 2-Step Access

Unit
Times

2.27 C900040026 Number of GPRS UL data 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 data TBF link establishments.

2-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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.
Figure 2-23 UL TBF Flow of 2-Step Access

Unit
Times

2.28 C900040027 Number of EGPRS UL TBF establishment success on PACCH

Description
When MS has a DL TBF and the TBF is being transmitted, if the UL data need to be transmitted but there is no corresponding UL TBF, then the Packet Downlink Ack message

2-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The measurement point is A, as shown in Figure 2-24.
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 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 EGPRS UL TBF due to N3101 overflow.

Measurement Point
The measurement point is when N3101 overflow.

Unit
Times

2-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.30 C900040029 Number of EGPRS UL TBF release due 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 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 release by control plane

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 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.32 C900040031 Number of EGPRS UL TBF release due 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 EGPRS UL TBF due to suspension of the instance.

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

Unit
Times

2.33 C900040032 Number of EGPRS UL TBF release due to inner abnormal

Description
TBF is abnormally released due to UPPB internal error.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.34 C900040033 Number of EGPRS 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 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
For different purpose, MS may establish two types of TBF: signaling TBF and data TBF.

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 simultaneous establishment

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 simultaneous establishment

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

2.38 C900040037 Number of GPRS UL signaling 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.

2-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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

2.39 C900040038 Number of GPRS UL signaling TBF release due 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 signaling UL TBF due to N3103 overflow.

Measurement Point
The measurement point is N3103 overflow.

Unit
Times

2.40 C900040039 Number of GPRS UL signaling TBF forcing release by control plane
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 signaling UL TBF due to release request from the control plane.
2-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The measurement point is arrival of the release request.

Unit
Times

2.41 C900040040 Number of GPRS UL signaling TBF release due 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 signaling UL TBF due to suspension of the instance.

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

Unit
Times

2.42 C900040041 Number of GPRS UL signaling TBF release due to inner abnormal
Description
TBF is abnormally released due to UPPB internal error.

Usage
The counter counts the number of abnormal releases of GPRS signaling UL TBF due to internal error.

Measurement Point
The measurement point is abnormal UPPB suspension.

Unit
Times
2-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.43 C900040042 Number of EGPRS UL signaling 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 EGPRS signaling UL TBF due to N3101 overflow.

Measurement Point
The measurement point is N3101 overflow.

Unit
Times

2.44 C900040043 Number of EGPRS UL signaling TBF release due 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 EGPRS signaling UL TBF due to N3103 overflow.

Measurement Point
The measurement point is N3103 overflow.

Unit
Times

2-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.45 C900040044 Number of EGPRS UL signaling TBF forcing release by control plane
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 EGPRS signaling UL TBF due to release request from the control plane.

Measurement Point
The measurement point is arrival of the release request.

Unit
Times

2.46 C900040045 Number of EGPRS UL signaling TBF release due 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 EGPRS signaling UL TBF due to suspension of the instance.

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

Unit
Times

2-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.47 C900040046 Number of EGPRS UL signaling TBF release due to inner abnormal
Description
TBF is abnormally released due to UPPB internal error.

Usage
The counter counts the number of abnormal releases of EGPRS signaling UL TBF due to internal error.

Measurement Point
The measurement point is abnormal UPPB suspension.

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
The measurement point is A, as shown in Figure 2-25.
Figure 2-25 Measurement Point of Number of EGPRS DL LLC Frames

2-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The measurement point is A, as shown in Figure 2-26.
Figure 2-26 Measurement Point of Number of Discarded EGPRS DL LLC Frames due to Buffer Overflow

Unit
Times

2.50 C900040049 Number of discarded EGPRS DL LLC 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Measurement Point
The measurement point is A, as shown in Figure 2-27.
Figure 2-27 Measurement Point of Number of Discarded EGPRS DL LLC Frames due to Life Time Expiration

Unit
Times

2.51 C900040050 Number of discarded EGPRS DL LLC frames due to other reasons
Description
The DL GIPB sends DL UnitData to UPPB through IP packets. If UPPB fails to send them for reasons other than the above two in C900040048 and C900040049, then it will send the LLC Discard message to SGSN.

Usage
The counter counts the number of discarded EGPRS DL LLC frames due to other reasons than the above two in C900040048 and C900040049.

Measurement Point
The measurement point is A, as shown in Figure 2-28.
Figure 2-28 Measurement Point of Number of Discarded EGPRS DL LLC Frames due to Other Reasons

2-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

2.52 C900040051 Number of DL signaling 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 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
The measurement point is A, as shown in Figure 2-29.
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
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.

2-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Usage
The counter counts the number of discarded EGPRS DL signaling LLC frames due to buffer overflow.

Measurement Point
The measurement point is A, as shown in Figure 2-30.
Figure 2-30 Measurement Point of Number of Discarded EGPRS DL Signaling LLC Frames due to Buffer Overflow

Unit
Times

2.54 C900040053 Number of discarded EGPRS DL signaling LLC 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 signaling LLC frames due to life time expiration.

Measurement Point
The measurement point is A, as shown in Figure 2-31.

2-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-31 Measurement Point of Number of Discarded EGPRS DL Signaling LLC Frames due to Life Time Expiration

Unit
Times

2.55 C900040054 Number of discarded EGPRS DL signaling LLC frames due to other reasons
Description
The DL GIPB sends DL UnitData to UPPB through IP packets. If UPPB fails to send them for reasons other than the above two in C900040052 and C900040053, then it will send the LLC Discard message to SGSN.

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

Measurement Point
The measurement point is A, as shown in Figure 2-32.
Figure 2-32 Measurement Point of Number of Discarded EGPRS DL Signaling LLC Frames due to Other Reasons

Unit
Times
2-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.

Usage
The counter counts the bytes of effective upper layer protocol data sent on DL PDCH.

Measurement Point
The measurement point is A, as shown in Figure 2-33.

2-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.

Usage
The counter counts the bytes of effective upper layer protocol data received on UL PDCH.

Measurement Point
The measurement point is A, as shown in Figure 2-34.
Figure 2-34 Measurement Point of Total Bytes of Effective Upper Layer Protocol Data Received on UL PDCH

2-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Unit
Byte

Related Features
ZGB-06-01-005 BSC Supervision

2.59 C900040058 Bytes of LLC frame on GPRS UL data TBF

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. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.

Usage
The counter counts the bytes carried by GPRS UL data TBF LLC frame.

Measurement Point
The measurement point is A, as shown in Figure 2-35.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.

Usage
The counter counts the bytes of LLC frame on GPRS DL data TBF.

Measurement Point
The measurement point is A, as shown in Figure 2-38.
2-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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
The measurement point is A, as shown in Figure 2-40.

2-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
During the TBF transmission, MS divides the UL LLC frame into RLC blocks and sends them to BSS. Only when BSS correctly receives all these RLC blocks can it recompose the LLC frame. BBS informs MS of the RLC block reception through Packet Uplink Ack. For the reply mode, if any RLC block is lost, MS should transmit again. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 point is A, as shown in Figure 2-41.

2-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Figure 2-41 Measurement Point of Number of NACK Blocks Received on GPRS UL TBF

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

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. 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 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-42 Measurement Point of Number of Effective Data Blocks Sent on GPRS DL TBF

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2.66 C900040065 Number of NACK 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. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Figure 2-43 Measurement Point of Number of NACK Blocks Sent on GPRS DL TBF

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2.67 C900040066 Bytes of LLC frame on EGPRS UL data TBF

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. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.

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

Measurement Point
The measurement point is A, as shown in Figure 2-44.

2-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.

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

Measurement Point
The measurement point is A, as shown in Figure 2-47.
2-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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
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 EGPRS UL TBF.

Measurement Point
The measurement point is A, as shown in Figure 2-49.

2-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2.72 C900040071 Number of NACK blocks received on EGPRS UL TBF

Description
During the TBF transmission, MS divides the UL LLC frame into RLC blocks and sends them to BSS. Only when BSS correctly receives all these RLC blocks can it recompose the LLC frame. BBS informs MS of the RLC block reception through Packet Uplink Ack. For the reply mode, if any RLC block is lost, MS should transmit again. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 point is A, as shown in Figure 2-50.

2-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Figure 2-50 Measurement Point of Number of NACK Blocks Received on EGPRS UL TBF

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2.73 C900040072 Number of effective data blocks sent on EGPRS 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. 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 sent on EGPRS DL TBF.

Measurement Point
The counter increments when Packet DownLink Ack/EGPRS Packet Downlink Ack indicates that MS have correctly received the RLC block. The measurement point is A1, as shown in Figure 2-51.

2-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-51 Measurement Point of Number of Effective Data Blocks Sent on EGPRS DL TBF

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2.74 C900040073 Number of NACK blocks sent on EGPRS 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. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Figure 2-52 Measurement Point of Number of Nack Blocks Sent on EGPRS DL TBF

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2.75 C900040074 Number of GPRS DL LLC frames

Description
This counter counts the times that the UPPB board receives LLC frames. When the BSSGP module of the UPPB board saves LLC frames, it judges that the frames are data or signalling according to the TBit in QoSProfile of DLUnitData. If they are data LLC frames and the TBF type is GPRS, the counter increases by 1.

Usage
This counter counts the times that downlink LLC frames are sent in GPRS services.

Measurement Point
The counter is updated when the BSSGP module saves LLC frames. The measurement point is A, as shown in Figure 2-53.
Figure 2-53 Measurement Point of Downlink GPRS LLC Frames

2-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

2.76 C900040075 Number of discarded GPRS DL LLC frames due to buffer overflow
Description
This counter counts the times that the UPPB board receives LLC frames but discards them due to buffer overflow. When the BSSGP module of the UPPB board saves LLC frames, it applies for dynamic memory. If the application fails or the LLC frames saved in the BSSGP module exceed the limit set in the network management system and the TBF type is GPRS, the counter increases by 1.

Usage
This counter counts the failures to apply for dynamic memory for downlink LLC frames in GPRS services.

Measurement Point
The counter is updated when the BSSGP module saves LLC frames. The measurement point is A, as shown in Figure 2-54.
Figure 2-54 Measurement Point of Discarded Downlink GPRS LLC Frames due to Buffer Overflow

Unit
Times

2.77 C900040076 Number of discarded GPRS DL LLC frames due to life time expiration
Description
The DL GIPB sends DL UnitData to the UPPB board through IP packets. If the UPPB board fails to send DL UnitData before the LLC frame life time expires, it will send the LLC Discard message to the SGSN.
2-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Usage
The counter counts the times that the LLC Discard message is sent due to life time expiration in downlink GPRS services.

Measurement Point
The measurement point is A, as shown in Figure 2-55.
Figure 2-55 Measurement Point of Discarded Downlink GPRS LLC Frames due to Life Time Expiration

Unit
Times

2.78 C900040077 Number of discarded GPRS DL LLC frames due to other reasons
Description
This counter counts the times that the UPPB board receives LLC frames but discards them due to reasons other than buffer overflow. When the BSSGP module of the UPPB board saves LLC frames, the counter increases by 1 if the module discards an LLC frame because it fails to insert the frame into queue or transfer the frame and if the TBF type is GPRS.

Usage
This counter counts the discards of downlink LLC frames in GPRS services due to reasons other than buffer overflow.

Measurement Point
The counter is updated when the BSSGP module saves LLC frames. The measurement point is A, as shown in Figure 2-56.

2-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-56 Measurement Point of Discarded Downlink GPRS LLC Frames due 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 increments. The measurement point is A, as shown in Figure 2-57.
Figure 2-57 Measurement Point of Number of DL Dummy Control Blocks on PACCH

Unit
Times

2-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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 increments. The measurement point is A, as shown in Figure 2-58.
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. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
The counter counts the number of DL RLC blocks expect DUMMY blocks sent by BSC on PACCH.

2-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 increments. The measurement point is A, as shown in Figure 2-60.

2-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Figure 2-60 Measurement Point of Number of DL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2.83 C900040082 Number of DL RLC pending blocks in CS2 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 CS2. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of CS2.

Measurement Point
When BSC sends a pending RLC block whose coding method is CS2 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-61.
Figure 2-61 Measurement Point of Number of DL RLC Pending Blocks on PDTCH

2-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2.84 C900040083 Number of DL RLC pending blocks in CS3 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 CS3. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of CS3.

Measurement Point
When BSC sends a pending RLC block whose coding method is CS3 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-62.
Figure 2-62 Measurement Point of Number of DL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode
2-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.85 C900040084 Number of DL RLC pending blocks in CS4 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 CS4. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of CS4.

Measurement Point
When BSC sends a pending RLC block whose coding method is CS4 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-63.
Figure 2-63 Measurement Point of Number of DL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.86 C900040085 Number of DL RLC NACK 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 retransmitted RLC blocks from BSC to MS, with coding method of CS1. This counter performs statistics for RLC layer, and the statistic result is the number of data 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
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.87 C900040086 Number of DL RLC NACK blocks in CS2 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 retransmitted RLC blocks from BSC to MS, with coding method of CS2. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of CS2.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is CS2 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-65.
Figure 2-65 Measurement Point of Number of DL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.88 C900040087 Number of DL RLC NACK blocks in CS3 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 retransmitted RLC blocks from BSC to MS, with coding method of CS3. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of CS3.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is CS3 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-66.
Figure 2-66 Measurement Point of Number of DL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.89 C900040088 Number of DL RLC NACK blocks in CS4 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 retransmitted RLC blocks from BSC to MS, with coding method of CS4. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of CS4.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is CS4 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-67.
Figure 2-67 Measurement Point of Number of DL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.90 C900040089 Number of DL RLC new 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 first-transmitted RLC blocks from BSC to MS, with coding method of CS1. This counter performs statistics for RLC layer, and the statistic result is the number of data 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, the counter increments. The measurement point is A, as shown in Figure 2-68.
Figure 2-68 Measurement Point of Number of DL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.91 C900040090 Number of DL RLC new blocks in CS2 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 first-transmitted RLC blocks from BSC to MS, with coding method of CS2. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 CS2.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of CS2) to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-69.
Figure 2-69 Measurement Point of Number of DL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.92 C900040091 Number of DL RLC new blocks in CS3 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 first-transmitted RLC blocks from BSC to MS, with coding method of CS3. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 CS3.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of CS3) to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-70.
Figure 2-70 Measurement Point of Number of DL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.93 C900040092 Number of DL RLC new blocks in CS4 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 first-transmitted RLC blocks from BSC to MS, with coding method of CS4. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 CS4.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of CS4) to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-71.
Figure 2-71 Measurement Point of Number of DL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter performs statistics for RLC layer, and the statistic result is the number of data 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 increments. The measurement point is A, as shown in Figure 2-72.
Figure 2-72 Measurement Point of Number of UL RLC Blocks Excluding Dummy Blocks on PACCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

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. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL CS1-coded pending RLC blocks received by BSC on PDTCH.
2-78 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2.96 C900040095 Number of UL RLC pending blocks in CS2 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 CS2-coded pending RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL CS2-coded pending RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives CS2-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 2-74.

2-79 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-74 Measurement Point of Number of UL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2.97 C900040096 Number of UL RLC pending blocks in CS3 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 CS3-coded pending RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL CS3-coded pending RLC blocks received by BSC on PDTCH.

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

2-80 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2.98 C900040097 Number of UL RLC pending blocks in CS4 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 CS4-coded pending RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL CS4-coded pending RLC blocks received by BSC on PDTCH.

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

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode
2-81 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.99 C900040098 Number of UL RLC NACK 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 retransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 measurement point is A, as shown in Figure 2-77.
Figure 2-77 Measurement Point of Number of UL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-82 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.100 C900040099 Number of UL RLC NACK blocks in CS2 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 CS2-coded retransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL CS2-coded retransmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives CS2-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-78.
Figure 2-78 Measurement Point of Number of UL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-83 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.101 C900040100 Number of UL RLC NACK blocks in CS3 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 CS3-coded retransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL CS3-coded retransmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives CS3-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-79.
Figure 2-79 Measurement Point of Number of UL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-84 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.102 C900040101 Number of UL RLC NACK blocks in CS4 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 CS4-coded retransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL CS4-coded retransmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives CS4-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-80.
Figure 2-80 Measurement Point of Number of UL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-85 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.103 C900040102 Number of UL RLC new 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 first-transmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL CS1-coded first-transmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives CS1-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-81.
Figure 2-81 Measurement Point of Number of UL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-86 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.104 C900040103 Number of UL RLC new blocks in CS2 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 CS2-coded first-transmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL CS2-coded first-transmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives CS2-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-82.
Figure 2-82 Measurement Point of Number of UL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-87 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.105 C900040104 Number of UL RLC new blocks in CS3 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 CS3-coded first-transmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL CS3-coded first-transmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives CS3-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-83.
Figure 2-83 Measurement Point of Number of UL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-88 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.106 C900040105 Number of UL RLC new blocks in CS4 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 CS4-coded first-transmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL CS4-coded first-transmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives CS4-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-84.
Figure 2-84 Measurement Point of Number of UL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-001 Coding Scheme #1~#4 ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

2-89 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. This counter performs statistics for RLC layer, and the statistic result is the number of data 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
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

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. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode

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 l When PS control plane receives a DL TBF establishment request from PS user plane, this counter increments. When UL GPRS TBF exists and DL GPRS TBF is to be established, if PS control plane receives the DL assignment message from PS user plane, this counter increments.

Unit
Times

2.110 C900040109 Number of GPRS DL TBF establishment failure due to database allocation failure
Description
The counter counts the number of GPRS DL TBF establishment failure due to database allocation failure. It involves the number of allocation failures caused by PDCH, Abis, and PCU having no available resource or in abnormal status.

2-91 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
The counter collects information about the frequency of channel allocation failures when BSC attempts to establish GPRS DL TBFs.

Measurement Point
This counter increments in the following two cases: 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 counter increments. The measurement point is A, as shown in Figure 2-85.
Figure 2-85 Measurement Point of Allocation Failures after Receiving DL TBF Establishment Request

When MS has already established an UL GPRS TBF and DL GPRS TBF is to be established, if PS control plane receives the DL TBF assignment message from PS user plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 2-86.
Figure 2-86 Measurement Point of Allocation Failures after Receiving DL TBF Assignment Message

Unit
Times

2-92 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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 point is A, as shown in Figure 2-87.
Figure 2-87 Measurement Point of Number of GPRS DL TBF Resource Reallocation Requests due to UL TBF Establishment

Unit
Times

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

2-93 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
The counter collects information about the frequency of GPRS DL resource reallocation failures of channel allocation caused by failed UL TBF establishment allocation.

Measurement Point
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.
Figure 2-88 Measurement Point of Number of GPRS DL TBF Resource Reallocation Failure of channel allocation due to UL TBF Establishment

Unit
Times

2.113 C900040112 Number of GPRS DL TBF resource 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 shown in Figure 2-89.

2-94 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Figure 2-89 Measurement Point of Number of GPRS DL TBF Resource Reallocation Requests due to LLC Transmission

Unit
Times

2.114 C900040113 Number of GPRS DL TBF resource reallocation failure of channel allocation 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.

2-95 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-90 Measurement Point of Number of GPRS DL TBF Resource Reallocation Failure of channel allocation due to LLC Transmission

Unit
Times

2.115 C900040114 Number of EGPRS DL TBF establishment requests

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
This counter increments in the following two cases: l l When PS control plane receives a DL TBF establishment request from PS user plane, this counter increments. 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

2-96 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.116 C900040115 Number of EGPRS DL TBF establishment failure due to database allocation failure
Description
The counter counts the number of channel allocation failures when BSC attempts to establish EGPRS DL TBFs and PS control plane applies to database for resources. It involves the number of allocation failures caused by PDCH, Abis, and PCU having no available resource or in abnormal status.

Usage
The counter collects information about the frequency of channel allocation failures when BSC attempts to establish EGPRS DL TBFs and PS control plane applies to database for resources.

Measurement Point
This counter increments in the following two cases: 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 counter increments. The measurement point is A, as shown in Figure 2-91.
Figure 2-91 Measurement Point of Allocation Failures after Receiving DL TBF Establishment Request

When UL EGPRS TBF exists and DL EGPRS TBF is to be established, if PS control plane receives the DL TBF assignment message from PS user plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 2-92.

2-97 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-92 Measurement Point of Allocation Failures after Receiving DL TBF 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).

Usage
The counter collects information about the frequency of EGPRS downlink TBF resource reallocation requests.

Measurement Point
When MS has already established a DL EGPRS TBF, if PS control plane receives an UL TBF assignment message from PS user plane, this counter increments. The measurement point is A, as shown in Figure 2-93.
Figure 2-93 Measurement Point of Number of EGPRS DL TBF Resource Reallocation Requests due to UL TBF Establishment

Unit
Times
2-98 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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

Usage
The counter collects information about the frequency of EGPRS DL resource reallocation failures of channel allocation 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 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-94.
Figure 2-94 Measurement Point of Number of EGPRS DL TBF Resource Reallocation Failure of channel allocation due to UL TBF Establishment

Unit
Times

2.119 C900040118 Number of EGPRS DL TBF resource 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 EGPRS TBF transmission.
2-99 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter collects information about the frequency of resource reallocation requests received by PS control plane during the DL EGPRS TBF transmission.

Measurement Point
When PS control plane receives a resource reallocation request from PS user plane, if the current DL EGPRS TBF exists, this counter increments, as A shown in Figure 2-95.
Figure 2-95 Measurement Point of Number of EGPRS DL TBF Resource Reallocation Requests due to LLC Transmission

Unit
Times

2.120 C900040119 Number of EGPRS DL TBF resource reallocation failure due to LLC transmission
Description
During the DL EGPRS 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 EGPRS 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-96.

2-100 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Figure 2-96 Measurement Point of Number of EGPRS DL TBF Resource Reallocation Failure of channel allocation due to LLC Transmission

Unit
Times

2.121 C900040120 Number of GPRS UL TBF establishment requests

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

Usage
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 l l When BSC receives a CCCH request originated by MS, this counter increments. When BSC receives a PCCCH request originated by MS, this counter increments. When BSC receives a PACCH request originated by MS and user plane sends a resource request to control plane, this counter increments.

Unit
Times

2-101 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.122 C900040121 Number of GPRS UL TBF establishment failure due to database allocation failure
Description
The counter counts the number of GPRS UL TBF establishment channel allocation failures. It involves the number of allocation failures caused by PDCH, Abis, and PCU having no available resource or in abnormal status.

Usage
The counter collects information about the frequency of channel allocation failures when the system attempts to establish GPRS UL TBFs.

Measurement Point
This counter increments in the following three cases: 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 measurement point is A, as shown in Figure 2-97.
Figure 2-97 Measurement Point of Allocation Failures after Receiving CCCH Request

When PS control plane receives a PCCCH request from MS, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 2-98.
Figure 2-98 Measurement Point of Allocation Failures after Receiving PCCCH Request

When MS has already established a DL GPRS TBF, if PS control plane receives an UL TBF assignment message from PS user plane, it will apply to database for resources.
2-102

SJ-20110531095035-015|2013-04-25 (R1.7)

ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 2-99.
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 reallocation requests.

Measurement Point
When MS has already established an UL GPRS TBF, if PS control plane receives a DL TBF assignment message from PS user plane, this counter increments. The measurement point is A, as shown in Figure 2-100.
Figure 2-100 Measurement Point of Number of GPRS UL TBF Resource Reallocation Requests due to DL TBF Establishment

2-103 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

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

Usage
The counter collects information about the frequency of GPRS UL resource reallocation failures of channel allocation 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 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-101.
Figure 2-101 Measurement Point of Allocation Failures after Receiving DL TBF Assignment Message

Unit
Times

2-104 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.125 C900040124 Number of GPRS UL TBF resource 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 UL GPRS TBF transmission.

Usage
This counter collects information about the frequency of resource reallocation requests received by PS control plane during the UL GPRS TBF transmission.

Measurement Point
When PS control plane receives a resource reallocation request from PS user plane, if the current UL GPRS TBF exists, this counter increments. The measurement point is A, as shown in Figure 2-102.
Figure 2-102 Measurement Point of Number of GPRS DL TBF Resource Reallocation Requests due to LLC Transmission

Unit
Times

2.126 C900040125 Number of GPRS UL TBF resource reallocation failure of channel allocation due to LLC transmission
Description
During the UL 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.

2-105 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter collects information about the frequency of failed resource allocations during the UL 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-103.
Figure 2-103 Measurement Point of Number of GPRS DL TBF Resource Reallocation Failure of channel allocation due to LLC Transmission

Unit
Times

2.127 C900040126 Number of GPRS UL TBF resource 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.

2-106 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Figure 2-104 Measurement Point of Number of GPRS UL TBF Resource Reallocation Requests for Resource Request

Unit
Times

2.128 C900040127 Number of GPRS UL TBF resource 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 number of failed resource allocations.

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

Measurement Point
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 shown in Figure 2-105.
Figure 2-105 Failing to Request for Resource from Database

2-107 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

2.129 C900040128 Number of EGPRS UL TBF establishment requests

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
This counter increments in the following three cases: l l l When BSC receives an EDGE CCCH request originated by MS, this counter increments. When BSC receives an EDGE PCCCH request originated by MS, this counter increments. 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

2.130 C900040129 Number of EGPRS UL TBF establishment failure due to database allocation failure
Description
The counter counts the number of EGPRS UL TBF establishment channel allocation failures. It involves the number of allocation failures caused by PDCH, Abis, and PCU having no available resource or in abnormal status.

2-108 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Usage
The counter collects information about the frequency of channel allocation failures when the system attempts to establish EGPRS UL TBFs.

Measurement Point
This counter increments in the following two cases: 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

When MS has already established a DL EGPRS TBF, if PS control plane receives an UL TBF assignment message from PS user plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 2-107.
Figure 2-107 Measurement Point of Allocation Failures (DL GPRS TBF Exists)

Unit
Times

2-109 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

Measurement Point
When MS has already established an UL EGPRS TBF, if PS control plane receives a DL TBF assignment message from PS user plane, this counter increments. The measurement point is A, as shown in Figure 2-108.
Figure 2-108 Measurement Point of Number of GPRS UL TBF Resource Reallocation Requests due to DL TBF Establishment

Unit
Times

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

2-110 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Usage
The counter collects information about the frequency of EGPRS UL resource reallocation failures of channel allocation 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 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-109.
Figure 2-109 Measurement Point of Allocation Failures after Receiving DL TBF Assignment Message

Unit
Times

2.133 C900040132 Number of EGPRS UL TBF resource 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 UL EGPRS TBF transmission.

Usage
This counter collects information about the frequency of resource reallocation requests 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 counter increments, as A shown in Figure 2-110.

2-111 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-110 Measurement Point of Number of GPRS DL TBF Resource Reallocation Requests due to LLC Transmission

Unit
Times

2.134 C900040133 Number of EGPRS UL TBF resource reallocation failure of channel allocation due to LLC transmission
Description
During the UL EGPRS 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 UL EGPRS 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-111.

2-112 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Figure 2-111 Measurement Point of Number of GPRS DL TBF Resource Reallocation Failure of channel allocation due to LLC Transmission

Unit
Times

2.135 C900040134 Number of EGPRS UL TBF resource 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 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 counter increments, as A shown in Figure 2-112.
Figure 2-112 Measurement Point of Number of GPRS UL TBF Resource Reallocation Requests for Resource Request

Unit
Times
2-113 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.136 C900040135 Number of EGPRS UL TBF resource 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 number of failed resource allocations.

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

Measurement Point
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 shown in Figure 2-113.
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-114 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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 ZGO-03-02-003 Full dynamic channel allocation on Um interface

2.139 C900040138 Average 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-115 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
This counter increments in the following three cases: l l l Request for database Release database 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-116 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Measurement Point
This counter increments in the following three cases: l l l Request for database Release database Report periodic measurement data

Unit
Times

2.142 C900040141 Number of GPRS DL TBF 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. The measurement point is A, as shown in Figure 2-114.
Figure 2-114 Measurement Point of Number of GPRS DL TBF Establishment Requests Before T3192 Expiration

2-117 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

2.143 C900040142 Number of GPRS DL TBF establishment using existing DL TBF resource
Description
When establishing EGPRS DL TBF under UL transmission status, the user plane needs not to request control plane for DL resource if having saved DL TBF resource of last time. It uses the existing resource for DL assignment. This counter records the number of GPRS DL TBF establishment using existing DL TBF resource.

Measurement Point
During the UL GPRS TBF transmission, when BSC receives the DL LLC frame, it uses the existing resource to establish DL GPRS TBF. 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

2.144 C900040143 Number of GPRS DL TBF 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-118 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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
The measurement point is A1, as shown in Figure 2-116.
Figure 2-116 Measurement Point of Number of GPRS DL TBF Establishment Requests on PACCH

Unit
Times

2.145 C900040144 Number of GPRS DL TBF 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-119 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-117 Measurement Point of Number of GPRS DL TBF Establishment Requests on CCCH/PCCCH

Unit
Times

2.146 C900040145 Number of EGPRS DL TBF 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. The measurement point is A, as shown in Figure 2-118.

2-120 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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

Unit
Times

2.147 C900040146 Number of EGPRS DL TBF establishment using existing DL TBF resource
Description
When establishing EGPRS DL TBF under UL transmission status, the user plane needs not to request control plane for DL resource if having saved DL TBF resource of last time. It uses the existing resource for DL assignment. This counter records the number of EGPRS DL TBF establishment using existing DL TBF resource.

Measurement Point
During the UL EGPRS TBF transmission, when BSC receives the DL LLC frame, it uses the existing resource to establish DL GPRS TBF. The measurement point is A, as shown in Figure 2-119.

2-121 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

Unit
Times

2.148 C900040147 Number of EGPRS DL TBF 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. This counter counts the number of times of requesting control plane for resource to establish EGPRS DL TBF on PACCH.

Measurement Point
The measurement point is A1, as shown in Figure 2-120.
Figure 2-120 Measurement Point of Number of GPRS DL TBF Establishment Requests on PACCH

2-122 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Unit
Times

2.149 C900040148 Number of EGPRS DL TBF 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 A1, as shown in Figure 2-121.
Figure 2-121 Normal CCCH/PCCCH DL TBF Establishment Process

Unit
Times

2-123 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.150 C900040149 Number of GPRS DL signaling TBF release due to N3105 overflow
Description
During the GPRS signaling DL TBF transmission, the DL block RRBP bit is set to ask MS to respond with a Packet Downlink Ack/Nack message. If the specified block of BSC fails to receive response from MS, then the N3105 counter increments; otherwise, it has a clear. If no response comes from the MS, then the RRBP bit is set again to ask MS to respond with a Packet Downlink Ack/Nack message; 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
When the N3105 counter value exceeds N3105Max, this counter increments. measurement point is A1, as shown in Figure 2-122. The

Figure 2-122 Measurement Point of Number of GPRS DL Signaling TBF Release due to N3105 Overflow

Unit
Times

2-124 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.151 C900040150 Number of GPRS DL signaling TBF 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
The measurement point is A1, as shown in Figure 2-123.
Figure 2-123 Measurement Point of Number of GPRS DL TBF Release due to Other Reasons

Unit
Times

2.152 C900040151 Number of GPRS DL signaling TBF forcing release by control plane
Description
When the user plane is transmitting the GPRS signaling DL TBF, if a release request comes from the control plane, then the GPRS signaling DL TBF will stop and be released abnormally.

2-125 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-124.
Figure 2-124 Measurement Point of Number of GPRS DL TBF Forcing Release by Control Plane

Unit
Times

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

Measurement Point
When the DL block assigning timer expires, this counter increments. The measurement point is A, as shown in Figure 2-125.

2-126 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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

Unit
Times

2.154 C900040153 Number of GPRS DL signaling TBF release due to inner abnormal
Description
When the user plane is transmitting the GPRS signaling DL TBF, if the message fails to be sent at the radio interface, the RLC instance fails to be created, or the resource reassignment fails, the GPRS signaling DL TBF will be released abnormally.

Measurement Point
During the transmission of GPRS signaling DL TBF, if the message 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-127 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

Measurement Point
When the N3105 counter value exceeds N3105Max, this counter increments. measurement point is A1, as shown in Figure 2-126.
Figure 2-126 Measurement Point of Number of EGPRS DL Signaling TBF Release due to N3105 Overflow

The

Unit
Times

2-128 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.156 C900040155 Number of EGPRS DL signaling TBF 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
The measurement point is A1, as shown in Figure 2-127.
Figure 2-127 Measurement Point of Number of EGPRS DL TBF Release due to Other Reasons

Unit
Times

2.157 C900040156 Number of EGPRS DL signaling TBF forcing release by control plane
Description
When the user plane is transmitting the EGPRS signaling DL TBF, if a release request comes from the control plane, then the EGPRS signaling DL TBF will stop and be released abnormally.
2-129 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-128.
Figure 2-128 Measurement Point of Number of EGPRS DL TBF Forcing Release by Control Plane

Unit
Times

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

Measurement Point
When the DL block assigning timer expires, this counter increments. The measurement point is A1, as shown in Figure 2-129.

2-130 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

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

Unit
Times

2.159 C900040158 Number of EGPRS DL signaling TBF release due to inner abnormal
Description
When the user plane is transmitting the EGPRS signaling DL TBF, if the message fails to be sent at the radio interface, the RLC instance fails to be created, or the resource reassignment fails, the EGPRS signaling DL TBF will be released abnormally.

Measurement Point
During the transmission of EGPRS signaling DL TBF, if the message fails to be sent at the radio interface, the RLC instance fails to be created, or the resource reassignment fails, this counter increments.

Unit
Times

2-131 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.160 C900040159 Number of GPRS UL TBF establishments in release state

Description
If both MS and BSS support reestablishment in released state, BSS sets RRBP and sends Packet UL Ack message (FAI =1 and TBF Est = 1) to MS after receiving all RLC blocks from MS. If MS has no new data to send, MS returns Packet Ctrl Ack message to BSS. If MS has new data to send but no DL TBF is available, then TBF should be reestablished, with the following two cases to be considered: 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. If system message indicates that Packet Control Ack is of RLC/MAC mode, then MS sends Packet Resource Request message to BSS. Subsequent flow is same as that of TWO STEP access.

Usage
This counter records the number of reestablishment times of MS in released state.

Measurement Point
The measurement point is A, as shown in Figure 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-132 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Unit
Times

2.161 C900040160 Number of GPRS UL TBF establishment with existing UL resource

Description
To accelerate TBF establishment, UPPB caches MSs UL/DL resource within a period of time. When MS attempts to establish new UL TBF on PACCH, relevant resource is directly assigned to MS if there is resource as indicated by UPPB; otherwise, MS sends request for resource to CMP.

Usage
This counter records the number of reestablishing UL GPRS TBF in released state without having to request for resource.

Measurement Point
The measurement point is A, as shown in Figure 2-132.
Figure 2-132 Measurement Point of GPRS UL TBF Establishments with Existing UL Resource

Unit
Times

2.162 C900040161 Number of GPRS UL TBF establishment requests on PACCH

Description
When MS has DL TBF and the TBF is in transmission status, if MS has UL data to send but no UL TBF is available, MS sends Packet DL Ack message together with UL TBF establishment request. This counter counts the number of resource re-applications after receiving this request.
2-133 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter records the number of requests for establishing UL GPRS TBF on PACCH.

Measurement Point
The measurement point is A, as shown in Figure 2-133.
Figure 2-133 Measurement Point of Number of Requests for Establishing UL GPRS TBF on PACCH

Unit
Times

2.163 C900040162 Number of EGPRS UL data TBF establishments on PACCH

Description
When there is available DL TBF, MS sends Packet DL Ack message with UL TBF establishment request. When there is a request to establish UL TBF on PACCH and the TBF type is EGPRS, the counter increments.

Usage
This counter records the number of times of establishing EGPRS UL TBF on PACCH.

Measurement Point
When Packet DL Ack message with UL TBF establishment request is received, and the TBF type is EGPRS, the counter increments.

Unit
Times

2-134 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.164 C900040163 Number of EGPRS UL TBF establishments in release state

Description
If both MS and BSS support reestablishment in released state, BSS sets RRBP and sends Packet UL Ack message (FAI =1 and TBF Est = 1) to MS after receiving all RLC blocks from MS. If MS has no new data to send, MS returns Packet Ctrl Ack message to BSS. If MS has new data to send but no DL TBF is available, then TBF should be reestablished, with the following two cases to be considered: 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. If system message indicates that Packet Control Ack is of RLC/MAC mode, then MS sends Packet Resource Request message to BSS. Subsequent flow is same as that of TWO STEP access.

Usage
This counter records the number of reestablishment times of MS in released state.

Measurement Point
The measurement point is A, as shown in Figure 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-135 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

2.165 C900040164 Number of EGPRS UL TBF establishment with existing UL resource

Description
To accelerate TBF establishment, UPPB caches MSs UL/DL resource within a period of time. When MS attempts to establish new UL TBF on PACCH, relevant resource is directly assigned to MS if there is resource as indicated by UPPB; otherwise, MS sends request for resource to CMP.

Usage
This counter records the number of reestablishing UL EGPRS TBF in released state without having to request for resource.

Measurement Point
The measurement point is A, as shown in Figure 2-136.
Figure 2-136 Measurement Point of EGPRS UL TBF Establishments with Existing UL Resource

Unit
Times

2.166 C900040165 Number of EGPRS UL TBF establishment requests on PACCH

Description
When MS has DL TBF and the TBF is in transmission status, if MS has UL data to send but no UL TBF is available, MS sends Packet DL Ack message together with UL TBF establishment request. This counter counts the number of resource re-applications after receiving this request.
2-136 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Usage
This counter records the number of requests for establishing UL EGPRS TBF on PACCH.

Measurement Point
The measurement point is A, as shown in Figure 2-137.
Figure 2-137 Measurement Point of Number of Requests for Establishing UL EGPRS TBF on PACCH

Unit
Times

2.167 C900040166 Number of EGPRS UL TBF establishment requests on CCCH/PCCCH

Description
When MS has new data to transmit but no corresponding UL/DL TBF is available, MS initiates UL TBF establishment flow, depending on whether the cell configures PBCCH on CCCH/PCCCH.

Usage
This counter records the number of requests for establishing EGPRS UL TBF on CCCH/PCCCH.

Measurement Point
The measurement point is A, as shown in Figure 2-138.
Figure 2-138 Measurement Point of Number of EGPRS UL TBF Establishment Requests on CCCH/PCCCH

2-137 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 l When the service instance is performing CS service but fails to request for the radio channel The database initiates the dynamic PDCH collection

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-003 Full dynamic channel allocation on Um interface

2.169 C900040168 Number of GPRS UL TBF establishment requests on CCCH/PCCCH

Description
When MS has new data to transmit but no corresponding UL/DL TBF is available, MS initiates UL TBF establishment flow, depending on whether the cell configures PBCCH on CCCH/PCCCH.

2-138 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Usage
This counter records the number of requests for establishing GPRS UL TBF on CCCH/PCCCH.

Measurement Point
The measurement point is A, as shown in Figure 2-139.
Figure 2-139 Measurement Point of Number of GPRS UL TBF Establishment Requests on CCCH/PCCCH

Unit
Times

2.170 C900040169 Number of GPRS DL TBF establishment requests on PACCH

Description
When UL TBF exists, and there is DL data to be sent through SGSN, a request will be sent to establish DL TBF on PACCH. This counter increments upon the request and the TBF type is GPRS.

Usage
This counter counts the number of requests to establish GPRS DL TBF on PACCH.

Measurement Point
When a request is sent to establish DL TBF on PACCH and the TBF type is GPRS, this counter increments.

Unit
Times

2-139 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.171 C900040170 Number of EGPRS DL TBF establishment requests on PACCH

Description
When UL TBF exists, and there is DL data to be sent through SGSN, a request will be sent to establish DL TBF on PACCH. This counter increments upon the request and the TBF type is EGPRS.

Usage
This counter counts the number of requests to establish EGPRS DL TBF on PACCH.

Measurement Point
When a request is sent to establish DL TBF on PACCH and the TBF type is EGPRS, this counter increments.

Unit
Times

2.172 C900040171 Number of GPRS UL TBF establishment requests on PACCH

Description
When there is available DL TBF, MS sends Packet DL Ack message with UL TBF establishment request. When there is a request to establish UL TBF on PACCH and the TBF type is GPRS, the counter increments.

Usage
This counter records the number of requests to establish GPRS UL TBF on PACCH.

Measurement Point
When Packet DL Ack message with UL TBF establishment request is received, and the TBF type is GPRS, this counter increments.

Unit
Times

2-140 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.173 C900040172 Number of DL RLC pending blocks in MCS1 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 MCS1. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS1.

Measurement Point
When BSC sends a pending RLC block whose coding method is MCS1 to MS, the counter increments. The measurement point is A, as shown in Figure 2-140.
Figure 2-140 Measurement Point of Number of DL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-141 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.174 C900040173 Number of DL RLC pending blocks in MCS2 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 MCS2. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS2.

Measurement Point
When BSC sends a pending RLC block whose coding method is MCS2 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-141.
Figure 2-141 Measurement Point of Number of DL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-142 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.175 C900040174 Number of DL RLC pending blocks in MCS3 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 MCS3. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS3.

Measurement Point
When BSC sends a pending RLC block whose coding method is MCS3 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-142.
Figure 2-142 Measurement Point of Number of DL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-143 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.176 C900040175 Number of DL RLC pending blocks in MCS4 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 MCS4. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS4.

Measurement Point
When BSC sends a pending RLC block whose coding method is MCS4 to MS via BTS, the counter increments. The measurement point is A, as shown inFigure 2-143.
Figure 2-143 Measurement Point of Number of DL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-144 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.177 C900040176 Number of DL RLC pending blocks in MCS5 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 MCS5. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS5.

Measurement Point
When BSC sends a pending RLC block whose coding method is MCS5 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-144.
Figure 2-144 Measurement Point of Number of DL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-145 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.178 C900040177 Number of DL RLC pending blocks in MCS6 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 MCS6. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS6.

Measurement Point
When BSC sends a pending RLC block whose coding method is MCS6 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-145.
Figure 2-145 Measurement Point of Number of DL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-146 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.179 C900040178 Number of DL RLC pending blocks in MCS7 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 MCS7. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS7.

Measurement Point
When BSC sends a pending RLC block whose coding method is MCS7 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-146.
Figure 2-146 Measurement Point of Number of DL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-147 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.180 C900040179 Number of DL RLC pending blocks in MCS8 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 MCS8. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS8.

Measurement Point
When BSC sends a pending RLC block whose coding method is MCS8 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-147.
Figure 2-147 Measurement Point of Number of DL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-148 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.181 C900040180 Number of DL RLC pending blocks in MCS9 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 MCS9. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS9.

Measurement Point
When BSC sends a pending RLC block whose coding method is MCS9 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-148.
Figure 2-148 Measurement Point of Number of DL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-149 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.182 C900040181 Number of DL RLC NACK blocks in MCS1 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 retransmitted RLC blocks from BSC to MS, with coding method of MCS1. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS1.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is MCS1 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-149.
Figure 2-149 Measurement Point of Number of DL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-150 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.183 C900040182 Number of DL RLC NACK blocks in MCS2 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 retransmitted RLC blocks from BSC to MS, with coding method of MCS2. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS2.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is MCS2 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-150.
Figure 2-150 Measurement Point of Number of DL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-151 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.184 C900040183 Number of DL RLC NACK blocks in MCS3 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 retransmitted RLC blocks from BSC to MS, with coding method of MCS3. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS3.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is MCS3 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-151.
Figure 2-151 Measurement Point of Number of DL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-152 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.185 C900040184 Number of DL RLC NACK blocks in MCS4 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 retransmitted RLC blocks from BSC to MS, with coding method of MCS4. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS4.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is MCS4 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-152.
Figure 2-152 Measurement Point of Number of DL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-153 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.186 C900040185 Number of DL RLC NACK blocks in MCS5 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 retransmitted RLC blocks from BSC to MS, with coding method of MCS5. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS5.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is MCS5 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-153.
Figure 2-153 Measurement Point of Number of DL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-154 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.187 C900040186 Number of DL RLC NACK blocks in MCS6 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 retransmitted RLC blocks from BSC to MS, with coding method of MCS6. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS6.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is MCS6 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-154.
Figure 2-154 Measurement Point of Number of DL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-155 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.188 C900040187 Number of DL RLC NACK blocks in MCS7 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 retransmitted RLC blocks from BSC to MS, with coding method of MCS7. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS7.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is MCS7 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-155.
Figure 2-155 Measurement Point of Number of DL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-156 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.189 C900040188 Number of DL RLC NACK blocks in MCS8 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 retransmitted RLC blocks from BSC to MS, with coding method of MCS8. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS8.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is MCS8 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-156.
Figure 2-156 Measurement Point of Number of DL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-157 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.190 C900040189 Number of DL RLC NACK blocks in MCS9 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 retransmitted RLC blocks from BSC to MS, with coding method of MCS9. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS9.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is MCS9 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-157.
Figure 2-157 Measurement Point of Number of DL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-158 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.191 C900040190 Number of DL RLC new blocks in MCS1 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 first-transmitted RLC blocks from BSC to MS, with coding method of MCS1. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 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.
Figure 2-158 Measurement Point of Number of DL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-159 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.192 C900040191 Number of DL RLC new blocks in MCS2 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 first-transmitted RLC blocks from BSC to MS, with coding method of MCS2. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 MCS2.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of MCS2) to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-159.
Figure 2-159 Measurement Point of Number of DL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-160 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.193 C900040192 Number of DL RLC new blocks in MCS3 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 first-transmitted RLC blocks from BSC to MS, with coding method of MCS3. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 MCS3.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of MCS3) to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-160.
Figure 2-160 Measurement Point of Number of DL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-161 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.194 C900040193 Number of DL RLC new blocks in MCS4 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 first-transmitted RLC blocks from BSC to MS, with coding method of MCS4. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 MCS4.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of MCS4) to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-161.
Figure 2-161 Measurement Point of Number of DL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-162 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.195 C900040194 Number of DL RLC new blocks in MCS5 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 first-transmitted RLC blocks from BSC to MS, with coding method of MCS5. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 MCS5.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of MCS5) to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-162.
Figure 2-162 Measurement Point of Number of DL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-163 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.196 C900040195 Number of DL RLC new blocks in MCS6 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 first-transmitted RLC blocks from BSC to MS, with coding method of MCS6. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 MCS6.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of MCS6) to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-163.
Figure 2-163 Measurement Point of Number of DL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-164 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.197 C900040196 Number of DL RLC new blocks in MCS7 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 first-transmitted RLC blocks from BSC to MS, with coding method of MCS7. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 MCS7.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of MCS7) to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-164.
Figure 2-164 Measurement Point of Number of DL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-165 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.198 C900040197 Number of DL RLC new blocks in MCS8 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 first-transmitted RLC blocks from BSC to MS, with coding method of MCS8. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 MCS8.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of MCS8) to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-165.
Figure 2-165 Measurement Point of Number of DL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-166 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.199 C900040198 Number of DL RLC new blocks in MCS9 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 first-transmitted RLC blocks from BSC to MS, with coding method of MCS9. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 MCS9.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of MCS9) to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 2-166.
Figure 2-166 Measurement Point of Number of DL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-167 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.200 C900040199 Number of UL RLC pending blocks in MCS1 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 MCS1-coded pending RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data 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 measurement point is A, as shown in Figure 2-167.
Figure 2-167 Measurement Point of Number of UL RLC Pending Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-168 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.201 C900040200 Number of UL RLC pending blocks in MCS2 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 MCS2-coded pending RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS2-coded pending RLC blocks received by BSC on PDTCH.

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

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-169 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.202 C900040201 Number of UL RLC pending blocks in MCS3 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 MCS3-coded pending RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS3-coded pending RLC blocks received by BSC on PDTCH.

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

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-170 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.203 C900040202 Number of UL RLC pending blocks in MCS4 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 MCS4-coded pending RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS4-coded pending RLC blocks received by BSC on PDTCH.

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

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-171 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.204 C900040203 Number of UL RLC pending blocks in MCS5 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 MCS5-coded pending RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS5-coded pending RLC blocks received by BSC on PDTCH.

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

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-172 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.205 C900040204 Number of UL RLC pending blocks in MCS6 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 MCS6-coded pending RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS6-coded pending RLC blocks received by BSC on PDTCH.

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

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-173 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.206 C900040205 Number of UL RLC pending blocks in MCS7 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 MCS7-coded pending RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS7-coded pending RLC blocks received by BSC on PDTCH.

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

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-174 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.207 C900040206 Number of UL RLC pending blocks in MCS8 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 MCS8-coded pending RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS8-coded pending RLC blocks received by BSC on PDTCH.

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

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-175 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.208 C900040207 Number of UL RLC pending blocks in MCS9 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 MCS9-coded pending RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS9-coded pending RLC blocks received by BSC on PDTCH.

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

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-176 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.209 C900040208 Number of UL RLC NACK blocks in MCS1 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 MCS1-coded retransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS1-coded retransmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS1-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-176.
Figure 2-176 Measurement Point of Number of UL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-177 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.210 C900040209 Number of UL RLC NACK blocks in MCS2 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 MCS2-coded retransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS2-coded retransmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS2-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-177.
Figure 2-177 Measurement Point of Number of UL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-178 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.211 C900040210 Number of UL RLC NACK blocks in MCS3 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 MCS3-coded retransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS3-coded retransmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS3-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-178.
Figure 2-178 Measurement Point of Number of UL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-179 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.212 C900040211 Number of UL RLC NACK blocks in MCS4 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 MCS4-coded retransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS4-coded retransmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS4-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-179.
Figure 2-179 Measurement Point of Number of UL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-180 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.213 C900040212 Number of UL RLC NACK blocks in MCS5 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 MCS5-coded retransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS5-coded retransmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS5-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-180.
Figure 2-180 Measurement Point of Number of UL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-181 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.214 C900040213 Number of UL RLC NACK blocks in MCS6 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 MCS6-coded retransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS6-coded retransmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS6-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-181.
Figure 2-181 Measurement Point of Number of UL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-182 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.215 C900040214 Number of UL RLC NACK blocks in MCS7 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 MCS7-coded retransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS7-coded retransmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS7-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-182.
Figure 2-182 Measurement Point of Number of UL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-183 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.216 C900040215 Number of UL RLC NACK blocks in MCS8 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 MCS8-coded retransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS8-coded retransmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS8-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-183.
Figure 2-183 Measurement Point of Number of UL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-184 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.217 C900040216 Number of UL RLC NACK blocks in MCS9 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 MCS9-coded retransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS9-coded retransmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS9-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-184.
Figure 2-184 Measurement Point of Number of UL RLC NACK Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-185 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.218 C900040217 Number of UL RLC new blocks in MCS1 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 MCS1-coded first-transmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS1-coded first-transmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS1-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-185.
Figure 2-185 Measurement Point of Number of UL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-186 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.219 C900040218 Number of UL RLC new blocks in MCS2 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 MCS2-coded first-transmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS2-coded first-transmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS2-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-186.
Figure 2-186 Measurement Point of Number of UL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-187 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.220 C900040219 Number of UL RLC new blocks in MCS3 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 MCS3-coded first-transmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS3-coded first-transmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS3-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-187.
Figure 2-187 Measurement Point of Number of UL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-188 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.221 C900040220 Number of UL RLC new blocks in MCS4 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 MCS4-coded first-transmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS4-coded first-transmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS4-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-188.
Figure 2-188 Measurement Point of Number of UL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-189 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.222 C900040221 Number of UL RLC new blocks in MCS5 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 MCS5-coded first-transmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS5-coded first-transmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS5-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-189.
Figure 2-189 Measurement Point of Number of UL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-190 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.223 C900040222 Number of UL RLC new blocks in MCS6 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 MCS6-coded first-transmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS6-coded first-transmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS6-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-190.
Figure 2-190 Measurement Point of Number of UL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-191 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.224 C900040223 Number of UL RLC new blocks in MCS7 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 MCS7-coded first-transmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS7-coded first-transmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS7-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-191.
Figure 2-191 Measurement Point of Number of UL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-192 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

2.225 C900040224 Number of UL RLC new blocks in MCS8 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 MCS8-coded first-transmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS8-coded first-transmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS8-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-192.
Figure 2-192 Measurement Point of Number of UL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2-193 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

2.226 C900040225 Number of UL RLC new blocks in MCS9 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 MCS9-coded first-transmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.

Usage
This counter counts the number of useful UL MCS9-coded first-transmitted RLC blocks received by BSC on PDTCH.

Measurement Point
When BSC receives MCS9-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 2-193.
Figure 2-193 Measurement Point of Number of UL RLC New Blocks on PDTCH

Unit
Times

Related Features
ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9

2.227 C900040232 Accumulated throughput of UL GPRS TBF

Description
This counter counts the total uplink GPRS throughput after the UPPB board receives uplink data blocks. When the URLC module of the UPPB board receives data blocks in extension
2-194 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

status or transmission status changes to extension or delay status and when the TBF type is GPRS, the counter indicates the total uplink GPRS throughput in a cell.

Usage
This counter counts the throughput of uplink GPRS TBF.

Measurement Point
The counter is updated when the URLC module receives uplink data blocks. measurement point is A, as shown in Figure 2-194.
Figure 2-194 Measurement Point of Uplink GPRS TBF Throughput

The

Unit
kbps

2.228 C900040233 Accumulated throughput of DL GPRS TBF

Description
This counter counts the total downlink GPRS throughput after the UPPB board receives the Packet DownLink Ack message. After the DRLC module of the UPPB board receives the message, the counter indicates the total downlink GPRS throughput in a cell if the module changes from transmission status to delay status and the TBF type is GPRS.

Usage
This counter counts the throughput of downlink GPRS TBF.

Measurement Point
The counter is updated when the DRLC module receives the Packet DownLink Ack message. The measurement point is A, as shown in Figure 2-195.

2-195 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 2-195 Measurement Point of Downlink GPRS TBF Throughput

Unit
kbps

2.229 C900040234 Accumulated throughput of UL EGPRS TBF

Description
This counter counts the total uplink EGPRS throughput after the UPPB board receives uplink data blocks. When the URLC module of the UPPB board receives data blocks in extension status or transmission status changes to extension or delay status and when the TBF type is EGPRS, the counter multiplies indicates the total uplink EGPRS throughput in a cell.

Usage
This counter counts the throughput of uplink EGPRS TBF.

Measurement Point
The counter is updated when the URLC module receives uplink data blocks. measurement point is A, as shown in Figure 2-196.
Figure 2-196 Measurement Point of Uplink EGPRS TBF Throughput

The

2-196 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 2 PS Basic Measurement (Cell)

Unit
kbps

2.230 C900040235 Accumulated throughput of DL EGPRS TBF

Description
This counter counts the total downlink EGPRS throughput after the UPPB board receives the EGPRS Packet DownLink Ack message. After the DRLC module of the UPPB board receives the message, the counter indicates the total downlink EGPRS throughput in a cell if the module changes from transmission status to delay status and the TBF type is EGPRS.

Usage
This counter counts the throughput of downlink EGPRS TBF.

Measurement Point
The counter is updated when the DRLC module receives the EGPRS Packet DownLink Ack message. The measurement point is A, as shown in Figure 2-197.
Figure 2-197 Measurement Point of Downlink EGPRS TBF Throughput

Unit
kbps

2-197 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

2-198 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Percent

3-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 C900060025 Number of TCH/F allocation success for assignment (speech version2) ..................................................................................................................4-39 C900060026 Number of TCH/F allocation success for assignment (speech version3) ..................................................................................................................4-40 C900060027 Number of TCH/F allocation failure due to channel activation failure 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 C900060057 Average number of idle TCH/F with interference band 2......................4-84 C900060058 Average number of idle TCH/F with interference band 3......................4-85 C900060059 Average number of idle TCH/F with interference band 4......................4-85 C900060060 Average number of idle TCH/F with interference band 5......................4-86 C900060061 Average number of idle TCH/H with interference band 1 .....................4-86 C900060062 Average number of idle TCH/H with interference band 2 .....................4-87 C900060063 Average number of idle TCH/H with interference band 3 .....................4-87 C900060064 Average number of idle TCH/H with interference band 4 .....................4-88 C900060065 Average number of idle TCH/H with interference band 5 .....................4-89 C900060066 Number of samples with UL RQ = 0 ....................................................4-89 C900060067 Number of samples with UL RQ = 1 ....................................................4-90 C900060068 Number of samples with UL RQ = 2 ....................................................4-90 C900060069 Number of samples with UL RQ = 3 ....................................................4-91 C900060070 Number of samples with UL RQ = 4 ....................................................4-91 C900060071 Number of samples with UL RQ = 5 ....................................................4-92 C900060072 Number of samples with UL RQ = 6 ....................................................4-92 C900060073 Number of samples with UL RQ = 7 ....................................................4-93 C900060074 Number of samples with DL RQ = 0 ....................................................4-93 C900060075 Number of samples with DL RQ = 1 ....................................................4-94
4-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

C900060076 Number of samples with DL RQ = 2 ....................................................4-94 C900060077 Number of samples with DL RQ = 3 ....................................................4-95 C900060078 Number of samples with DL RQ = 4 ....................................................4-95 C900060079 Number of samples with DL RQ = 5 ....................................................4-96 C900060080 Number of samples with DL RQ = 6 ....................................................4-96 C900060081 Number of samples with DL RQ = 7 ....................................................4-97 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 from the upper layer ...............................................................................................4-122 C900060111 Number of incoming handover from GSM900 to GSM1800 from the lower layer..............................................................................................................4-123
4-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C900060112 Number of incoming handover success from GSM900 to GSM1800 from the lower layer................................................................................................4-124 C900060113 Number of incoming handover from GSM1800 to GSM900 from the same layer .............................................................................................................4-125 C900060114 Number of incoming handover success from GSM1800 to GSM900 from the same layer................................................................................................4-126 C900060115 Number of incoming handover from GSM1800 to GSM900 from the upper layer .............................................................................................................4-127 C900060116 Number of incoming handover success from GSM1800 to GSM900 from the upper layer ...............................................................................................4-128 C900060117 Number of incoming handover from GSM1800 to GSM900 from the lower layer..............................................................................................................4-129 C900060118 Number of incoming handover success from GSM1800 to GSM900 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 dynamic radio channel .........................4-137 C900060126 Average number of unavailable dynamic 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 assignment (speech version1)................................................................................4-150 C900060140 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version1)................................................................................4-151 C900060141 Number of TCH/F allocation failure due to channel activation failure for assignment (speech version2)...........................................................................4-152 C900060142 Number of TCH/F allocation failure due to BTS connection failure for assignment (speech version2)................................................................................4-153 C900060143 Number of TCH/F allocation failure due to BIU connection failure for assignment (speech version2)................................................................................4-154
4-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

C900060144 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version2)................................................................................4-155 C900060145 Number of TCH/F allocation failure due to BTS connection failure for assignment (speech version3)................................................................................4-156 C900060146 Number of TCH/F allocation failure due to BIU connection failure for assignment (speech version3)................................................................................4-157 C900060147 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version3)................................................................................4-158 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 C900060156 Number of TCH/F allocation failure due to channel activation failure for handover(speech version1) ...............................................................................4-167 C900060157 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version1) ...................................................................................4-169 C900060158 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version1) ...................................................................................4-170 C900060159 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version1) ...................................................................................4-171 C900060160 Number of TCH/F allocation failure due to channel activation failure for handover(speech version2) ...............................................................................4-172 C900060161 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version2) ...................................................................................4-173 C900060162 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version2) ...................................................................................4-174 C900060163 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version2) ...................................................................................4-176 C900060164 Number of TCH/F allocation failure due to channel activation failure for handover (speech version3) ..............................................................................4-177 C900060165 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version3) ...................................................................................4-178 C900060166 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version3) ...................................................................................4-179 C900060167 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version3) ...................................................................................4-180 C900060168 Number of Voice TCH/F handover success .......................................4-182

4-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 failure for handover ................................................................................................4-185 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 failure for handover ................................................................................................4-188 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 for assignment (speech version1)...........................................................................4-192 C900060176 Number of TCH/H allocation failure due to BTS connection failure for assignment (speech version1)................................................................................4-193 C900060177 Number of TCH/H allocation failure due to BIU connection failure for assignment (speech version1)................................................................................4-194 C900060178 Number of TCH/H allocation failure due to TCU connection failure for assignment (speech version1)................................................................................4-195 C900060179 Number of TCH/H allocation failure due to channel activation failure for handover (speech version1) ..............................................................................4-196 C900060180 Number of TCH/H allocation failure due to BTS connection failure for handover (speech version1) ...................................................................................4-197 C900060181 Number of TCH/H allocation failure due to BIU connection failure for handover (speech version1) ...................................................................................4-198 C900060182 Number of TCH/H allocation failure due to TCU connection failure for handover (speech version1) ...................................................................................4-200 C900060191 Number of TCH/H allocation failure due to channel activation failure for assignment (speech version3)...........................................................................4-201 C900060192 Number of TCH/H allocation failure due to BTS connection failure for assignment (speech version3)................................................................................4-202 C900060193 Number of TCH/H allocation failure due to BIU connection failure for assignment (speech version3)................................................................................4-203 C900060194 Number of TCH/H allocation failure due to TCU connection failure for assignment (speech version3)................................................................................4-204 C900060195 Number of TCH/H allocation failure due to channel activation failure for handover (speech version3) ..............................................................................4-205 C900060196 Number of TCH/H allocation failure due to BTS connection failure for handover (speech version3) ...................................................................................4-206 C900060197 Number of TCH/H allocation failure due to BIU connection failure for handover (speech version3) ...................................................................................4-207 C900060198 Number of TCH/H allocation failure due to TCU connection failure for handover (speech version3) ...................................................................................4-208 C900060199 Number of Voice TCH/H assignment success ...................................4-209 C900060200 Number of Voice TCH/H assignment failure....................................... 4-211 C900060201 Number of Voice TCH/H handover success.......................................4-212
4-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

C900060202 Number of data TCH/H allocation failure due to channel activation failure for assignment .............................................................................................4-214 C900060203 Number of data TCH/H allocation failure due to BTS connection failure for assignment .............................................................................................4-215 C900060204 Number of data TCH/H allocation failure due to BIU connection failure for assignment........................................................................................................4-216 C900060205 Number of data TCH/H allocation failure due to TCU connection failure for assignment .............................................................................................4-217 C900060206 Number of data TCH/H allocation failure due to channel activation failure for handover ................................................................................................4-218 C900060207 Number of data TCH/H allocation failure due to BTS connection failure for handover ................................................................................................4-219 C900060208 Number of data TCH/H allocation failure due to BIU connection failure for handover ...........................................................................................................4-220 C900060209 Number of data TCH/H allocation failure due to TCU connection failure for handover ................................................................................................4-222 C900060210 Number of data TCH/H assignment success .....................................4-223 C900060211 Number of data TCH/H assignment failure.........................................4-224 C900060212 Number of data TCH/H handover success.........................................4-225 C900060213 Number of BSC-controlled incoming handover due to forced release .4-228 C900060214 Number of BSC-controlled incoming handover due to queues ...........4-229 C900060215 Number of BSC-controlled incoming handover due to forced handover ................................................................................................................4-230 C900060216 Number of MSC-controlled incoming handover due to forced handover ................................................................................................................4-232 C900060217 Number of unavailable defined TCH/H ..............................................4-233 C900060218 Number of unavailable defined TCH/F...............................................4-234 C900060219 Number of signaling TCH/F drops due to handover failure.................4-235 C900060220 Number of voice TCH/F drops due to handover failure ......................4-237 C900060221 Number of data TCH/F drops due to handover failure........................4-239 C900060222 Number of signaling TCH/H drops due to handover failure ................4-241 C900060223 Number of data TCH/H drops due to handover failure .......................4-243 C900060224 Number of TCH/H handover attempts due to UL strength..................4-245 C900060225 Number of TCH/H handover attempts due to DL strength..................4-246 C900060226 Number of TCH/H handover attempts due to UL quality ....................4-247 C900060227 Number of TCH/H handover attempts due to DL quality ....................4-247 C900060228 Number of TCH/H handover attempts due to UL interference ............4-248 C900060229 Number of TCH/H handover attempts due to DL interference ............4-249 C900060230 Number of TCH/H inter-subcell handover attempts due to good C/I...4-250 C900060231 Number of TCH/H inter-subcell handover attempts due to bad C/I.....4-251 C900060232 Number of TCH/H handover attempts due to PBGT ..........................4-252 C900060233 Number of TCH/H handover attempts due to large TA .......................4-253 C900060234 Number of TCH/H handover attempts due to other reasons ..............4-254 C900060235 Number of signaling TCH/H assignment success ..............................4-255 C900060236 Number of MOC access success.......................................................4-256
4-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C900060237 Number of dual band outgoing handover...........................................4-257 C900060238 Number of dual band outgoing handover success .............................4-258 C900060239 Number of dual band incoming handover ..........................................4-259 C900060240 Number of dual band incoming handover success.............................4-260 C900060241 Number of SDCCH assignment attempts ..........................................4-260 C900060242 Number of SDCCH assignments success .........................................4-262 C900060243 Number of SDCCH assignment failure ..............................................4-263 C900060244 Number of voice TCH/F drops due to radio link failure.......................4-264 C900060245 Number of voice TCH/H drops due to radio link failure ......................4-265

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. The measurement takes cell as the statistics unit.

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.

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.

4-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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 l MS receives the IMM_ASS message from BSC and successfully accesses the channel. BSC receives the EST_IND message from MS.

Usage
This counter is used to find out the frequency of MS access success due to MTC.

Measurement Point
This counter counts when BSC receives the EST_IND message. The measurement point is A4, as shown in Figure 4-2.

4-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-2 Radio Access Flow

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 l l If allocation and occupation succeed, C900060003 and C900060004 accumulate simultaneously. If occupation fails and the failure is due to transceiver fault, C900060003, C900060004, and C900060005 do not change. For failures in other cases, C900060003 and C900060005 accumulate simultaneously.

Usage
This counter counts the number of SDCCH channel occupation attempts during assignment, including the number of occupation success (C900060004) and the number of occupation failure (C900060005).

4-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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
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. This counter accumulates when allocation and occupation succeed.

Usage
This counter counts the number of successful SDCCH channel occupations during assignment.
4-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 4-4 Immediate Assignment Flow

Unit
Times

Related Features
ZGB-03-02-003 Dynamic Configuration of SDCCH

4.6 C900060005 Number of SDCCH seizure failure 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 l l If occupation fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

Usage
This counter counts the number of SDCCH channel occupation failures during assignment.
4-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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.
Figure 4-5 Immediate Assignment Flow

Unit
Times

Related Features
ZGB-03-02-003 Dynamic Configuration of SDCCH ZGB-06-01-007 Cell Traffic Statistics

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. l l l If allocation and occupation succeed, C900060006 and C901250005 accumulate simultaneously. If occupation fails, C900060006 and C900060007 accumulate simultaneously. If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource.
4-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. other cases, C900060006 and C900060007 accumulate

For failures in 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-7 External Handover Flow

Unit
Times

Related Features
ZGB-03-02-003 Dynamic Configuration of SDCCH 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 l If occupation fails, this counter accumulates. 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 fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

l l

Usage
This counter counts the number of SDCCH occupation failure.
4-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 as shown in Figure 4-9.
Figure 4-8 Internal Handover Flow (Intra-Cell Handover)

Figure 4-9 External Handover Flow

Unit
Times

Related Features
ZGB-03-02-003 Dynamic Configuration of SDCCH ZGO-02-02-004 SDCCH/SDCCH Handover
4-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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.
Figure 4-10 Immediate Assignment Flow

Unit
Times

Related Features
ZGB-03-02-003 Dynamic Configuration of SDCCH

4-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.10 C900060009 Number of SDCCH allocation failure 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 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.
Figure 4-11 Immediate Assignment Flow

Unit
Times

4-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Related Features
ZGB-03-02-003 Dynamic Configuration of SDCCH

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. l l l If allocation and occupation succeed, C900060010 and C901260002 accumulate simultaneously. If the request returns that the transceiver is faulty, C900060010, C901260002, and C900060011 do not change. 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 measurement point is A1, as shown in Figure 4-12.
Figure 4-12 Immediate Assignment Flow

Unit
Times

4-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGB-03-01-004 Immediate TCH Assignment ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation

4.12 C900060011 Number of signaling TCH/F seizure failure for assignment

Description
This counter counts the number of TCH/F channel occupation failures during assigning signaling channels. After BSC receives the channel request, it attempts to allocate channel for the request. l l l If occupation fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

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 measurement point is A1, as shown in Figure 4-13.
Figure 4-13 Immediate Assignment Occupation Failure Flow 1

Unit
Times

Related Features
ZGB-03-01-004 Immediate TCH Assignment ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation
4-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.13 C900060012 Number of signaling TCH/F seizure 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). After BSC receives the channel request, it attempts to allocate channel for the request. l l l If allocation and occupation succeed, C900060012 and C901260005 accumulate simultaneously. If occupation fails, C900060012 and C900060013 accumulate simultaneously. 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, C900060012 and C901260005 accumulate simultaneously. If the waiting for resource fails, C900060012 and C900060013 accumulate simultaneously.

l l

If the request returns that the transceiver is faulty, C900060012, C901260005, and C900060013 do not change. For failures in other cases, C900060012 and C900060013 accumulate 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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 ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation

4-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.14 C900060013 Number of signaling TCH/F seizure failure for handover

Description
This counter counts the number of TCH/F channel occupation failures during signaling channel handover. After BSC receives the channel request, it attempts to allocate channel for the request. l l If occupation fails, this counter accumulates. 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 fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

l l

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
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
4-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

ZGO-03-02-002 Enhancement on Channel Allocation

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 measurement point is A2, as shown in Figure 4-20.
Figure 4-20 Immediate Assignment Flow

Unit
Times

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

4-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.16 C900060015 Number of signaling TCH/F allocation failure for assignment

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
ZGB-03-01-004 Immediate TCH Assignment ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.17 C900060016 Number of signaling TCH/F allocation failure for handover

Description
This counter counts the number of TCH/F channel allocation failures during signaling channel handover. 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 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 will accumulate.

Measurement Point
BSC activates TCH/F channel due to handover and uses it as signaling channel, but receives channel activation failure message, incorrect channel activation response message, T9103 being timeout, channel instance being released, or channel being forcibly released. 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

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. 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. 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.
Figure 4-24 Immediate Assignment Flow

Unit
Times

Related Features
ZGB-03-01-004 Immediate TCH Assignment
4-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.19 C900060018 Number of signaling TCH/F assignment failure for assignment

Description
This counter counts the number of failing to assign TCH/F channel as signaling channel. 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. 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
ZGB-03-01-004 Immediate TCH Assignment ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.20 C900060019 Number of voice TCH/F seizure attempts for assignment

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. l l l If allocation and occupation succeed, C900060019 and C901260021 accumulate simultaneously. If occupation fails, C900060019 and C900060020 accumulate simultaneously. 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, C900060019 and C901260021 accumulate simultaneously. If the waiting for resource fails, C900060019 and C900060020 accumulate simultaneously.

l l

If the request returns that the transceiver is faulty, C900060019, C901260021, and C900060020 do not change. For failures in other cases, C900060019 and C900060020 accumulate 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-26 Common Assignment Flow (TC Is Internal)

Figure 4-27 Common Assignment Flow (TC Is External)

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation

4-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. l l If occupation fails, this counter accumulates. 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 fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

l l

Measurement Point
BSC requests for channel (due to assignment and the channel is used as voice channel) but fails to occupy the channel, or BSC fails to wait for internal resource. The measurement point is B1, as shown in Figure 4-28.
Figure 4-28 Common Assignment Failure Flow 1 (TC Is Internal)

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation

4-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.22 C900060021 Number of voice TCH/F seizure attempts for handover

Description
This counter counts the number of TCH/F channel being attempted to be occupied during voice channel handover, including the number of occupation success (C901260024) and the number of occupation failure (C900060022). After BSC receives the channel request massage, it attempts to allocate channel for the request. l l l If allocation and occupation succeed, C900060021 and C901260024 accumulate simultaneously. If occupation fails, C900060021 and C900060022 accumulate simultaneously. 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, C900060021 and C901260024 accumulate simultaneously. If the waiting for resource fails, C900060021 and C900060022 accumulate simultaneously.

l l

If the request returns that the transceiver is faulty, C900060021, C901260024, and C900060022 do not change. For failures in other cases, C900060021 and C900060022 accumulate 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-29 Internal Handover Flow (Intra-Cell Handover, TC Is Internal)

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

4-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-31 External Handover Flow (TC Is Internal)

Figure 4-32 External Handover Flow (TC Is External)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation

4-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. After BSC receives the channel request message, it attempts to allocate channel for the request. l l If allocation or occupation fails, this counter accumulates. 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 fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

l l

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 point is C1 as shown in Figure 4-33 and D1 as shown in Figure 4-34.
Figure 4-33 Intra-BSC Handover Occupation Failure Flow

Figure 4-34 Inter-BSC Handover Occupation Failure Flow

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover
4-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation

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). 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. 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.
Figure 4-35 Common Assignment Flow (TC Is Internal)

4-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-36 Common Assignment Flow (TC Is External)

Unit
Times

Related Features
ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) 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). 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. 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-37 Common Assignment Failure Flow 1 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.26 C900060025 Number of TCH/F allocation success for assignment (speech version2)
Description
This counter counts the number of TCH/F channel being allocated successfully during voice channel assignment (speech version 2). 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. 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 2). The measurement point is B3, as shown in Figure 4-38 and Figure 4-39.

4-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-38 Common Assignment Flow (TC Is Internal)

Figure 4-39 Common Assignment Flow (TC Is External)

Unit
Times

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

4.27 C900060026 Number of TCH/F allocation success for assignment (speech version3)
Description
This counter counts the number of TCH/F channel being allocated successfully during voice channel assignment (speech version 3).
4-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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. 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 3). The measurement point is B3, as shown in Figure 4-40 and Figure 4-41.
Figure 4-40 Common Assignment Flow (TC Is Internal)

Figure 4-41 Common Assignment Flow (TC Is External)

Unit
Times

4-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

4.28 C900060027 Number of TCH/F allocation failure due to channel activation failure for assignment (speech version3)
Description
This counter counts the number of TCH/F channel allocation failure due to channel activation failure during voice channel assignment (speech version 3). 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. 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.
Figure 4-42 Common Assignment Failure Flow 1 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
4-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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

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. 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. 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.
Figure 4-43 Common Assignment Flow (TC Is Internal)

4-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-44 Common Assignment Flow (TC Is External)

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.30 C900060029 Number of voice TCH/F assignment failure for assignment

Description
This counter counts the number of failing to assign TCH/F channel as voice channel. 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. If BSC does not receive the MS access notification within a certain time, this assignment 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-45 Common Assignment Failure Flow 4 (TC Is Internal)

Unit
Times

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

4.31 C900060030 Number of data TCH/F seizure attempts for assignment

Description
This counter counts the number of TCH/F channel being attempted to be occupied during data channel assignment, including the number of occupation success (C901260070) and the number of occupation failure (C900060031). After BSC receives the channel request massage, it attempts to allocate channel for the request. l l l If allocation and occupation succeed, C900060030 and C901260070 accumulate simultaneously. If occupation fails, C900060030 and C900060031 accumulate simultaneously. 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, C900060030 and C901260070 accumulate simultaneously. If the waiting for resource fails, C900060030 and C900060031 accumulate simultaneously.

4-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

l l

If the request returns that the transceiver is faulty, C900060030, C901260070, and C900060031 do not change. For failures in other cases, C900060030 and C900060031 accumulate simultaneously.

Measurement Point
BSC completes requesting for channel (due to assignment and the channel is used as data channel), or BSC receives the internal message of waiting for resource successfully or waiting for resource failed (C901260070 + C900060031). The measurement point is B1, as shown in Figure 4-46 and Figure 4-47.
Figure 4-46 Common Assignment Flow (TC Is Internal)

Figure 4-47 Common Assignment Flow (TC Is External)

Unit
Times

4-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Related Features
ZGB-01-03-002 Data Traffic Channels ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation

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. After BSC receives the channel request message, it attempts to allocate channel for the request. l l If occupation fails, this counter accumulates. 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 fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

l l

Measurement Point
BSC requests for channel (due to assignment and the channel is used as data channel) but fails to occupy the channel, or BSC fails to wait for internal resource. The measurement point is B1, as shown in Figure 4-48.
Figure 4-48 Common Assignment Failure Flow 1 (TC Is Internal)

Unit
Times

4-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGB-01-03-002 Data Traffic Channels ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation

4.33 C900060032 Number of data TCH/F seizure attempts for handover

Description
This counter counts the number of TCH/F channel being attempted to be occupied during data channel handover, including the number of occupation success (C901260073) and the number of occupation failure (C900060033). After BSC receives the channel request massage, it attempts to allocate channel for the request. l l l If allocation and occupation succeed, C900060032 and C901260073 accumulate simultaneously. If occupation fails, C900060032 and C900060033 accumulate simultaneously. 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, C900060032 and C901260073 accumulate simultaneously. If the waiting for resource fails, C900060032 and C900060033 accumulate simultaneously.

l l

If the request returns that the transceiver is faulty, C900060032, C901260073, and C900060033 do not change. For failures in other cases, C900060032 and C900060033 accumulate simultaneously.

Measurement Point
BSC completes requesting for channel (due to handover and the channel is used as data channel), or BSC receives the internal message of waiting for resource successfully or waiting for resource failed (C901260073 + C900060033). The measurement point is C1 as shown in Figure 4-49 and Figure 4-50, and D1 as shown in Figure 4-51 and Figure 4-52.

4-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-49 Internal Handover Flow (Intra-Cell Handover, TC Is Internal)

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

4-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-51 External Handover Flow (TC Is Internal)

Figure 4-52 External Handover Flow (TC Is External)

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation

4-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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. After BSC receives the channel request message, it attempts to allocate channel for the request. l l If occupation fails, this counter accumulates. 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 fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

l l

Measurement Point
BSC requests for channel (due to handover and the channel is used as data 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-53 and D1 as shown in Figure 4-54.
Figure 4-53 Intra-BSC Handover Occupation Failure Flow

Figure 4-54 Inter-BSC Handover Occupation Failure Flow

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels
4-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation

4.35 C900060034 Number of data TCH/F allocation success for assignment

Description
This counter counts the number of TCH/F channel being allocated successfully during data 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. 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 data channel. The measurement point is B3, as shown in Figure 4-55 and Figure 4-56.
Figure 4-55 Common Assignment Flow (TC Is Internal)

4-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-56 Common Assignment Flow (TC Is External)

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.36 C900060035 Number of data TCH/F allocation failure due to channel activation failure for assignment
Description
This counter counts the number of TCH/F channel allocation failure due to channel activation failure during data channel assignment. After BSC responds the channel request message to allocate and occupy TCH/F channel successfully, if connection succeeds, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If channel activation fails due to receiving channel activation failure message, incorrect channel activation response message, T9103 being timeout, channel instance being released or channel being forcibly released, this counter accumulates.

Measurement Point
BSC activates TCH/F channel due to assignment and uses the channel as data channel, but receives channel activation failure message, incorrect channel activation response message, T9103 being timeout, channel instance being released, or channel being forcibly released. The measurement point is B3, as shown in Figure 4-57.

4-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-57 Common Assignment Failure Flow 1 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

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. 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. 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-58 and Figure 4-59.

4-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-58 Common Assignment Flow (TC Is Internal)

Figure 4-59 Common Assignment Flow (TC Is External)

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.38 C900060037 Number of data TCH/F assignment failure

Description
This counter counts the number of failing to assign TCH/F channel as data channel. 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. If BSC does not receive the MS access notification within a certain time, this assignment 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-60.
Figure 4-60 Common Assignment Failure Flow 4 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.39 C900060038 Number of signaling TCH/H seizure attempts for assignment

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). After BSC receives the channel request massage, it attempts to allocate channel for the request. l l l If allocation and occupation succeed, C900060038 and C901270002 accumulate simultaneously. If the request returns that the transceiver is faulty, C900060038, C901270002, and C900060039 do not change. 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 measurement point is A1, as shown in Figure 4-61.
Figure 4-61 Immediate Assignment Flow

Unit
Times

Related Features
ZGB-03-01-004 Immediate TCH Assignment ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate
4-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation

4.40 C900060039 Number of signaling TCH/H seizure failure for assignment

Description
This counter counts the number of TCH/H channel occupation failure during signaling channel assignment. After BSC receives the channel request message, it attempts to allocate channel for the request. l l l If occupation fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

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 measurement point is A1, as shown in Figure 4-62.
Figure 4-62 Immediate Assignment Occupation Failure Flow 1

Unit
Times

Related Features
ZGB-03-01-004 Immediate TCH Assignment ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation

4-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.41 C900060040 Number of signaling TCH/H seizure attempts for handover

Description
This counter counts the number of TCH/H channel being attempted to be occupied during signaling channel handover, including the number of occupation success (C901270005) and the number of occupation failure (C900060041). After BSC receives the channel request, it attempts to allocate channel for the request. l l l If allocation and occupation succeed, C900060040 and C901270005 accumulate simultaneously. If occupation fails, C900060040 and C900060041 accumulate simultaneously. 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, C900060040 and C901270005 accumulate simultaneously. If the waiting for resource fails, C900060040 and C900060041 accumulate simultaneously.

l l

If the request returns that the transceiver is faulty, C900060040, C901270005, and C900060041 do not change. For failures in other cases, C900060040 and C900060041 accumulate 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 Figure 4-65 and Figure 4-66.

4-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-63 Internal Handover Flow (Intra-Cell Handover, TC Is Internal)

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

4-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-65 External Handover Flow (TC Is Internal)

Figure 4-66 External Handover Flow (TC Is External)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation

4-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.42 C900060041 Number of signaling TCH/H seizure failure for handover

Description
This counter counts the number of TCH/H channel occupation failures during signaling channel handover. After BSC receives the channel request, it attempts to allocate channel for the request. l l If occupation fails, this counter accumulates. 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 fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

l l

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-67 and D1 as shown in Figure 4-68.
Figure 4-67 Intra-BSC Handover Occupation Failure Flow

Figure 4-68 Inter-BSC Handover Occupation Failure Flow

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate
4-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation

4.43 C900060042 Number of voice TCH/H seizure attempts for assignment

Description
This counter counts the number of TCH/H channel being attempted to be occupied during voice channel assignment, including the number of occupation success (C901270021) and the number of occupation failure (C900060043). After BSC receives the channel request massage, it attempts to allocate channel for the request. l l l If allocation and occupation succeed, C900060042 and C901270021 accumulate simultaneously. If occupation fails, C900060042 and C900060043 accumulate simultaneously. 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, C900060042 and C901270021 accumulate simultaneously. If the waiting for resource fails, C900060042 and C900060043 accumulate simultaneously.

l l

If the request returns that the transceiver is faulty, C900060042, C901270021, and C900060043 do not change. For failures in other cases, C900060042 and C900060043 accumulate 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 (C901270021 + C900060043). The measurement point is B1, as shown in Figure 4-69 and Figure 4-70.

4-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-69 Common Assignment Flow (TC Is Internal)

Figure 4-70 Common Assignment Flow (TC Is External)

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation

4-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.44 C900060043 Number of voice TCH/H seizure failure for assignment

Description
This counter counts the number of TCH/H channel occupation failure during voice channel assignment. After BSC receives the channel request message, it attempts to allocate channel for the request. l l If occupation fails, this counter accumulates. 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 fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

l l

Measurement Point
BSC requests for channel (due to assignment and the channel is used as voice channel) but fails to occupy the channel, or BSC fails to wait for internal resource. The measurement point is B1, as shown in Figure 4-71.
Figure 4-71 Common Assignment Failure Flow 1 (TC Is Internal)

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation

4-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.45 C900060044 Number of voice TCH/H seizure attempts for handover

Description
This counter counts the number of TCH/H channel being attempted to be occupied during voice channel handover, including the number of occupation success (C901270024) and the number of occupation failure (C900060045). After BSC receives the channel request massage, it attempts to allocate channel for the request. l l l If allocation and occupation succeed, C900060044 and C901270024 accumulate simultaneously. If occupation fails, C900060044 and C900060045 accumulate simultaneously. 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, C900060044 and C901270024 accumulate simultaneously. If the waiting for resource fails, C900060044 and C900060045 accumulate simultaneously.

l l

If the request returns that the transceiver is faulty, C900060044, C901270024, and C900060045 do not change. For failures in other cases, C900060044 and C900060045 accumulate 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 (C901270024 + C900060045). The measurement point is C1 as shown in Figure 4-72 and Figure 4-73, and D1 as shown in Figure 4-74 and Figure 4-75.

4-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-72 Internal Handover Flow (Intra-Cell Handover, TC Is Internal)

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

4-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-74 External Handover Flow (TC Is Internal)

Figure 4-75 External Handover Flow (TC Is External)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation

4-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.46 C900060045 Number of voice TCH/H seizure failure for handover

Description
This counter counts the number of TCH/H channel occupation failure during voice channel handover. After BSC receives the channel request message, it attempts to allocate channel for the request. l l If allocation or occupation fails, this counter accumulates. 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 fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

l l

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 point is C1 as shown in Figure 4-76 and D1 as shown in Figure 4-77.
Figure 4-76 Intra-BSC Handover Occupation Failure Flow

Figure 4-77 Inter-BSC Handover Occupation Failure Flow

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover
4-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation

4.47 C900060046 Number of data TCH/H seizure attempts for assignment

Description
This counter counts the number of TCH/H channel being attempted to be occupied during data channel assignment, including the number of occupation success (C901270070) and the number of occupation failure (C900060047). After BSC receives the channel request massage, it attempts to allocate channel for the request. l l l If allocation and occupation succeed, C900060046 and C901270070 accumulate simultaneously. If occupation fails, C900060046 and C900060047 accumulate simultaneously. 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, C900060046 and C901270070 accumulate simultaneously. If the waiting for resource fails, C900060046 and C900060047 accumulate simultaneously.

l l

If the request returns that the transceiver is faulty, C900060046, C901270070, and C900060047 do not change. For failures in other cases, C900060046 and C900060047 accumulate simultaneously.

Measurement Point
BSC completes requesting for channel (due to assignment and the channel is used as data channel), or BSC receives the internal message of waiting for resource successfully or waiting for resource failed (C901270070 + C900060047). The measurement point is B1, as shown in Figure 4-78 and Figure 4-79.

4-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-78 Common Assignment Flow (TC Is Internal)

Figure 4-79 Common Assignment Flow (TC Is External)

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation

4-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. After BSC receives the channel request message, it attempts to allocate channel for the request. l l If occupation fails, this counter accumulates. 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 fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

l l

Measurement Point
BSC requests for channel (due to assignment and the channel is used as data channel) but fails to occupy the channel, or BSC fails to wait for internal resource. The measurement point is B1, as shown in Figure 4-80.
Figure 4-80 Common Assignment Failure Flow 1 (TC Is Internal)

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation

4-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.49 C900060048 Number of data TCH/H seizure attempts for handover

Description
This counter counts the number of TCH/H channel being attempted to be occupied during data channel handover, including the number of occupation success (C901270073) and the number of occupation failure (C900060049). After BSC receives the channel request massage, it attempts to allocate channel for the request. l l l If allocation and occupation succeed, C900060048 and C901270073 accumulate simultaneously. If occupation fails, C900060048 and C900060049 accumulate simultaneously. 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, C900060048 and C901270073 accumulate simultaneously. If the waiting for resource fails, C900060048 and C900060049 accumulate simultaneously.

l l

If the request returns that the transceiver is faulty, C900060048, C901270073, and C900060049 do not change. For failures in other cases, C900060048 and C900060049 accumulate simultaneously.

Measurement Point
BSC completes requesting for channel (due to handover and the channel is used as data channel), or BSC receives the internal message of waiting for resource successfully or waiting for resource failed (C901270073 + C900060049). The measurement point is C1 as shown in Figure 4-81 and Figure 4-82, and D1 as shown in Figure 4-83 and Figure 4-84.

4-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-81 Internal Handover Flow (Intra-Cell Handover, TC Is Internal)

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

4-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-83 External Handover Flow (TC Is Internal)

Figure 4-84 External Handover Flow (TC Is External)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation

4-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. After BSC receives the channel request message, it attempts to allocate channel for the request. l l If occupation fails, this counter accumulates. 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 fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.

l l

Measurement Point
BSC requests for channel (due to handover and the channel is used as data 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-85 and D1 as shown in Figure 4-86.
Figure 4-85 Intra-BSC Handover Occupation Failure Flow

Figure 4-86 Inter-BSC Handover Occupation Failure Flow

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover
4-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-87 Idle-State MO Short Message Flow

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

4-78 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.52 C900060051 Number of SAPI3 link establishment 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-88 Idle-State MT Short Message Flow

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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

If RANCS is in the status of RADIO_APPLY and sends the inter-cell handover command, then T3103 is started. If RANCS is in the status of ASSIGN and T3103 is timeout, then the counter increments. The measurement point is A, as shown in Figure 4-90.

4-81 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-90 Call Drop due to T3103 Timeout During Inter-Cell Handover

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
ZGB-02-02-001 Basic Handover ZGO-02-02-004 SDCCH/SDCCH Handover

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 SDCCH 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, handover failure, or BTS fault.

Measurement Point
This counter increments when call drop occurs on SDCCH channel due to radio link failure, LAPD link failure, handover failure, or BTS fault.

Unit
Times
4-82 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Related Features
ZGB-06-01-007 Cell Traffic Statistics

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, 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 TCH/F channel due to radio link failure, LAPD link break, or handover failure.

Measurement Point
The counter increments when call drop occurs on TCH/F channel due to radio link failure, LAPD link failure, or handover failure.

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

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, 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 TCH/H channel due to radio link failure, LAPD link break, or handover failure.

Measurement Point
The counter increments when call drop occurs on TCH/H channel due to radio link failure, LAPD link failure, or handover failure.
4-83 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

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-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-001 Idle Channel Measurement

4.58 C900060057 Average number of idle TCH/F with interference band 2

Description
This counter counts the number of idle TCH/Fs with interference band 2 in the carrier.

Usage
This counter is used to find out the number of idle TCH/Fs with interference band 2.

4-84 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Measurement Point
This counter counts when querying the database periodically.

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-001 Idle Channel Measurement

4.59 C900060058 Average number of idle TCH/F with interference band 3

Description
This counter counts the number of idle TCH/Fs with interference band 3 in the carrier.

Usage
This counter is used to find out the number of idle TCH/Fs with interference band 3.

Measurement Point
This counter counts when querying the database periodically.

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-001 Idle Channel Measurement

4.60 C900060059 Average number of idle TCH/F with interference band 4

Description
This counter counts the number of idle TCH/Fs with interference band 4 in the carrier.

Usage
This counter is used to find out the number of idle TCH/Fs with interference band 4.
4-85 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter counts when querying the database periodically.

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-001 Idle Channel Measurement

4.61 C900060060 Average number of idle TCH/F with interference band 5

Description
This counter counts the number of idle TCH/Fs with interference band 5 in the carrier.

Usage
This counter is used to find out the number of idle TCH/Fs with interference band 5.

Measurement Point
This counter counts when querying the database periodically.

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-001 Idle Channel Measurement

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Measurement Point
This counter counts when querying the database periodically.

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-001 Idle Channel Measurement ZGO-03-02-005 Dynamic Half Rate Allocation

4.63 C900060062 Average number of idle TCH/H with interference band 2

Description
This counter counts the number of idle TCH/Hs with interference band 2 in the carrier.

Usage
This counter is used to find out the number of idle TCH/Hs with interference band 2.

Measurement Point
This counter counts when querying the database periodically.

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-001 Idle Channel Measurement ZGO-03-02-005 Dynamic Half Rate Allocation

4.64 C900060063 Average number of idle TCH/H with interference band 3

Description
This counter counts the number of idle TCH/Hs with interference band 3 in the carrier.
4-87 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of idle TCH/Hs with interference band 3.

Measurement Point
This counter counts when querying the database periodically.

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-001 Idle Channel Measurement ZGO-03-02-005 Dynamic Half Rate Allocation

4.65 C900060064 Average number of idle TCH/H with interference band 4

Description
This counter counts the number of idle TCH/Hs with interference band 4 in the carrier.

Usage
This counter is used to find out the number of idle TCH/Hs with interference band 4.

Measurement Point
This counter counts when querying the database periodically.

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-001 Idle Channel Measurement ZGO-03-02-005 Dynamic Half Rate Allocation

4-88 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.66 C900060065 Average number of idle TCH/H with interference band 5

Description
This counter counts the number of idle TCH/Hs with interference band 5 in the carrier.

Usage
This counter is used to find out the number of idle TCH/Hs with interference band 5.

Measurement Point
This counter counts when querying the database periodically.

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-001 Idle Channel Measurement ZGO-03-02-005 Dynamic Half Rate Allocation

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.68 C900060067 Number of samples with UL RQ = 1

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
This counter is used to count the number of samples with UL RQ = 1.

Measurement Point
The counter increments if UL RQ = 1 in the measurement report or preprocessing measurement report that BSC receives.

Unit
Times

4.69 C900060068 Number of samples with UL RQ = 2

Description
This counter counts the number of samples with UL RQ = 2. After BSC receives the measurement report or preprocessing measurement report, if the UL RQ = 2, the counter increments.

Usage
This counter is used to count the number of samples with UL RQ = 2.

Measurement Point
The counter increments if UL RQ = 2 in the measurement report or preprocessing measurement report that BSC receives.

Unit
Times

4-90 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.70 C900060069 Number of samples with UL RQ = 3

Description
This counter counts the number of samples with UL RQ = 3. After BSC receives the measurement report or preprocessing measurement report, if the UL RQ = 3, the counter increments.

Usage
This counter is used to count the number of samples with UL RQ = 3.

Measurement Point
The counter increments if UL RQ = 3 in the measurement report or preprocessing measurement report that BSC receives.

Unit
Times

4.71 C900060070 Number of samples with UL RQ = 4

Description
This counter counts the number of samples with UL RQ = 4. After BSC receives the measurement report or preprocessing measurement report, if the UL RQ = 4, the counter increments.

Usage
This counter is used to count the number of samples with UL RQ = 4.

Measurement Point
The counter increments if UL RQ = 4 in the measurement report or preprocessing measurement report that BSC receives.

Unit
Times

4-91 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.72 C900060071 Number of samples with UL RQ = 5

Description
This counter counts the number of samples with UL RQ = 5. After BSC receives the measurement report or preprocessing measurement report, if the UL RQ = 5, the counter increments.

Usage
This counter is used to count the number of samples with UL RQ = 5.

Measurement Point
The counter increments if UL RQ = 5 in the measurement report or preprocessing measurement report that BSC receives.

Unit
Times

4.73 C900060072 Number of samples with UL RQ = 6

Description
This counter counts the number of samples with UL RQ = 6. After BSC receives the measurement report or preprocessing measurement report, if the UL RQ = 6, the counter increments.

Usage
This counter is used to count the number of samples with UL RQ = 6.

Measurement Point
The counter increments if UL RQ = 6 in the measurement report or preprocessing measurement report that BSC receives.

Unit
Times

4-92 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.74 C900060073 Number of samples with UL RQ = 7

Description
This counter counts the number of samples with UL RQ = 7. After BSC receives the measurement report or preprocessing measurement report, if the UL RQ = 7, the counter increments.

Usage
This counter is used to count the number of samples with UL RQ = 7.

Measurement Point
The counter increments if UL RQ = 7 in the measurement report or preprocessing measurement report that BSC receives.

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 measurement report that BSC receives.

Unit
Times

4-93 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.76 C900060075 Number of samples with DL RQ = 1

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
This counter is used to count the number of samples with DL RQ = 1.

Measurement Point
The counter increments if DL RQ = 1 in the measurement report or preprocessing measurement report that BSC receives.

Unit
Times

4.77 C900060076 Number of samples with DL RQ = 2

Description
This counter counts the number of samples with DL RQ = 2. After BSC receives the measurement report or preprocessing measurement report, if the DL RQ = 2, the counter increments.

Usage
This counter is used to count the number of samples with DL RQ = 2.

Measurement Point
The counter increments if DL RQ = 2 in the measurement report or preprocessing measurement report that BSC receives.

Unit
Times

4-94 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.78 C900060077 Number of samples with DL RQ = 3

Description
This counter counts the number of samples with DL RQ = 3. After BSC receives the measurement report or preprocessing measurement report, if the DL RQ = 3, the counter increments.

Usage
This counter is used to count the number of samples with DL RQ = 3.

Measurement Point
The counter increments if DL RQ = 3 in the measurement report or preprocessing measurement report that BSC receives.

Unit
Times

4.79 C900060078 Number of samples with DL RQ = 4

Description
This counter counts the number of samples with DL RQ = 4. After BSC receives the measurement report or preprocessing measurement report, if the DL RQ = 4, the counter increments.

Usage
This counter is used to count the number of samples with DL RQ = 4.

Measurement Point
The counter increments if DL RQ = 4 in the measurement report or preprocessing measurement report that BSC receives.

Unit
Times

4-95 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.80 C900060079 Number of samples with DL RQ = 5

Description
This counter counts the number of samples with DL RQ = 5. After BSC receives the measurement report or preprocessing measurement report, if the DL RQ = 5, the counter increments.

Usage
This counter is used to count the number of samples with DL RQ = 5.

Measurement Point
The counter increments if DL RQ = 5 in the measurement report or preprocessing measurement report that BSC receives.

Unit
Times

4.81 C900060080 Number of samples with DL RQ = 6

Description
This counter counts the number of samples with DL RQ = 6. After BSC receives the measurement report or preprocessing measurement report, if the DL RQ = 6, the counter increments.

Usage
This counter is used to count the number of samples with DL RQ = 6.

Measurement Point
The counter increments if DL RQ = 6 in the measurement report or preprocessing measurement report that BSC receives.

Unit
Times

4-96 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.82 C900060081 Number of samples with DL RQ = 7

Description
This counter counts the number of samples with DL RQ = 7. After BSC receives the measurement report or preprocessing measurement report, if the DL RQ = 7, the counter increments.

Usage
This counter is used to count the number of samples with DL RQ = 7.

Measurement Point
The counter increments if DL RQ = 7 in the measurement report or preprocessing measurement report that BSC receives.

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 increments. The measurement point is A, as shown in Figure 4-91.
Figure 4-91 Handover Decision

4-97 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.84 C900060083 Number of TCH/F handover attempts 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
BSC performs handover decision after receiving measurement report on TCH/F channel. If handover decision succeeds and the handover is due to DL strength, this counter increments. The measurement point is A, as shown in Figure 4-92.
Figure 4-92 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
4-98 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.85 C900060084 Number of TCH/F handover attempts 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
BSC performs handover decision after receiving measurement report on TCH/F channel. If handover decision succeeds and the handover is due to UL quality, this counter increments. The measurement point is A, as shown in Figure 4-93.
Figure 4-93 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.86 C900060085 Number of TCH/F handover attempts 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
BSC performs handover decision after receiving measurement report on TCH/F channel. If handover decision succeeds and the handover is due to DL quality, this counter increments. The measurement point is A, as shown in Figure 4-94.
Figure 4-94 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.87 C900060086 Number of TCH/F handover attempts 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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 interference, this counter increments. The measurement point is A, as shown in Figure 4-95.
Figure 4-95 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.88 C900060087 Number of TCH/F handover attempts 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
BSC performs handover decision after receiving measurement report on TCH/F channel. If handover decision succeeds and the handover is due to DL interference, this counter increments. The measurement point is A, as shown in Figure 4-96.

4-101 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-96 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.89 C900060088 Number of TCH/F 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/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
BSC performs handover decision after receiving measurement report on TCH/F channel. If handover decision succeeds and the handover is due to too large C/I ratio, this counter increments. The measurement point is A, as shown in Figure 4-97.

4-102 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-97 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.90 C900060089 Number of TCH/F 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/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
BSC performs handover decision after receiving measurement report on TCH/F channel. If handover decision succeeds and the handover is due to too low C/I ratio, this counter increments. The measurement point is A, as shown in Figure 4-98.

4-103 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-98 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.91 C900060090 Number of TCH/F handover attempts 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
BSC performs handover decision after receiving measurement report on TCH/F channel. If handover decision succeeds and the handover is due to PBGT value, this counter increments. The measurement point is A, as shown in Figure 4-99.
Figure 4-99 Handover Decision

4-104 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.92 C900060091 Number of TCH/F handover attempts 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
BSC performs handover decision after receiving measurement report on TCH/F channel. If handover decision succeeds and the handover is due to too large TA, this counter increments. The measurement point is A, as shown in Figure 4-100.
Figure 4-100 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria
4-105 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.93 C900060092 Number of TCH/F handover attempts due to other reasons

Description
This counter counts the number of handover attempts due to any other reason beyond the handover reasons mentioned previously.

Usage
This counter is used to find out the frequency of handover due to any other reason.

Measurement Point
BSC performs handover decision after receiving measurement report on TCH/F channel. 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.
Figure 4-101 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics

4.95 C900060094 Number of BSC-controlled inter-cell outgoing handover success

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

4-107 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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, as shown in Figure 4-103.
Figure 4-103 BSC-Controlled Inter-Cell Outgoing Handover Success

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics

4.97 C900060096 Number of MSC-controlled outgoing 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics

4.98 C900060097 Number of BSC-controlled inter-cell 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-106 BSC-Controlled Inter-Cell Incoming Handover Execution

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics

4.99 C900060098 Number of BSC-controlled inter-cell 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 point is A, as shown in Figure 4-107.
Figure 4-107 BSC-Controlled Inter-Cell Incoming Handover Success

4-111 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics

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 is A, as shown in Figure 4-108.
Figure 4-108 MSC-Controlled Incoming Handover Execution

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover
4-112 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

ZGB-06-01-007 Cell Traffic Statistics

4.101 C900060100 Number of MSC-controlled incoming handover due to forced release

Description
During MSC-controlled inter-BSC incoming handover process, the counter counts the number of forced release executions due to no available radio resource in the target cell.

Usage
This counter is used to find out the frequency of forced release executions during MSC-controlled inter-BSC incoming handover process. It reflects the handover situation.

Measurement Point
The target cell receives the radio channel request message. If the request is due to MSC-controlled inter-BSC incoming handover and the target cell has no available radio channels, forced release is attempted. If the target cell receives the message of resource available returned by the forced release instance, the counter increments. The measurement point is A, as shown in Figure 4-109.
Figure 4-109 Forced Release Execution

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-03-001 eMLPP

4-113 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.102 C900060101 Number of MSC-controlled incoming handover due to queue

Description
During MSC-controlled inter-BSC incoming handover process, the counter counts the number of queuing executions due to no available radio resource in the target cell.

Usage
This counter is used to find out the frequency of queuing executions during MSC-controlled inter-BSC incoming handover process, and it reflects the handover situation.

Measurement Point
The target cell receives the radio channel request message. If the request is due to MSC-controlled inter-BSC incoming handover and the target cell has no available radio channels, the target instance is added to the waiting queue. When the target cell receives the message of resource available, the counter increments. The measurement point is A, as shown in Figure 4-110.
Figure 4-110 Queuing Execution

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-03-001 eMLPP

4-114 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.103 C900060102 Number of MSC-controlled incoming handover success

Description
This counter counts the number of successful MSC-controlled inter-BSC incoming handovers.

Usage
This counter is used to find out the frequency of successful MSC-controlled inter-BSC incoming handover, and it reflects the handover situation.

Measurement Point
When the target cell receives the handover completion message, if the request is due to MSC-controlled inter-BSC incoming handover, the counter increments. The measurement point is A, as shown in Figure 4-111.
Figure 4-111 MSC-Controlled Incoming Handover Success

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 A, as shown in Figure 4-112.
Figure 4-112 BSC-Controlled Inter-Cell Incoming Handover Execution

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

4.105 C900060104 Number of incoming handover success from undefined layer(GSM900) to current layer (GSM1800)
Description
This counter counts the number of successful incoming handover from the undefined layer cell (GSM900) to the target cell (GSM1800) during BSC-controlled inter-cell handover.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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.
Figure 4-113 BSC-Controlled Inter-Cell Incoming Handover Success

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

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

Usage
This counter is used to find out the frequency of incoming handover executions from the undefined layer cell (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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

(GSM1800) is the undefined layer cell, the counter increments. The measurement point is A, as shown in Figure 4-114.
Figure 4-114 BSC-Controlled Inter-Cell Incoming Handover Execution

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

4.107 C900060106 Number of incoming handover success from undefined layer(GSM1800) to current layer(GSM900)
Description
This counter counts the number of successful incoming handover from the undefined layer cell (GSM1800) to the target cell (GSM900) during BSC-controlled inter-cell handover.

Usage
This counter is used to find out the frequency of successful incoming handover from the undefined layer cell (GSM1800) to the target cell (GSM900). It reflects the handover situation.

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

4-118 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-115 BSC-Controlled Inter-Cell Incoming Handover Success

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

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
This counter is used to find out the frequency of incoming handover executions from the cell (GSM900) to the target cell (GSM1800) in the same layer. It reflects the handover situation.

Measurement Point
When the target cell (GSM1800) receives the channel activation response message, if the request is due to BSC-controlled 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-116 BSC-Controlled Inter-Cell Incoming Handover Execution

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

4.109 C900060108 Number of incoming handover success from the same layer GSM900 to GSM1800
Description
This counter counts the number of successful incoming handovers from the cell (GSM900) to the target cell (GSM1800) in the same layer during BSC-controlled inter-cell handover.

Usage
This counter is used to find out the frequency of successful incoming handover from the cell (GSM900) to the target cell (GSM1800) in the same layer. It reflects the handover situation.

Measurement Point
When the target cell (GSM1800) receives the 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-117 BSC-Controlled Inter-Cell Incoming Handover Success

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

4.110 C900060109 Number of incoming handover from 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
This counter is used to find out the frequency of incoming handover executions from the upper layer cell (GSM900) to the target cell (GSM1800). 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 upper layer, the counter increments. The measurement point is A, as shown in Figure 4-118.

4-121 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-118 BSC-Controlled Inter-Cell Incoming Handover Execution

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

4.111 C900060110 Number of incoming handover success from GSM900 to GSM1800 from the upper layer
Description
This counter counts the number of successful incoming handovers from the upper layer cell (GSM900) to the target cell (GSM1800) during BSC-controlled inter-cell handover.

Usage
This counter is used to find out the frequency of successful incoming handover from the upper layer cell (GSM900) to the target cell (GSM1800). It reflects the handover 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 upper layer, the counter increments. The measurement point is A, as shown in Figure 4-119.

4-122 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-119 BSC-Controlled Inter-Cell Incoming Handover Success

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

4.112 C900060111 Number of incoming handover from GSM900 to GSM1800 from the lower layer
Description
This counter counts the number of incoming handover executions from the lower layer cell (GSM900) to the target cell (GSM1800) during BSC-controlled inter-cell handover.

Usage
This counter is used to find out the frequency of incoming handover executions from the lower layer cell (GSM900) to the target cell (GSM1800). 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 lower layer, the counter increments. The measurement point is A, as shown in Figure 4-120.

4-123 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-120 BSC-Controlled Inter-Cell Incoming Handover Execution

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

4.113 C900060112 Number of incoming handover success from GSM900 to GSM1800 from the lower layer
Description
This counter counts the number of successful incoming handovers from the lower layer cell (GSM900) to the target cell (GSM1800) during BSC-controlled inter-cell handover.

Usage
This counter is used to find out the frequency of successful incoming handover from the lower layer cell (GSM900) to the target cell (GSM1800). It reflects the handover 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 lower layer, the counter increments. The measurement point is A, as shown in Figure 4-121.

4-124 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-121 BSC-Controlled Inter-Cell Incoming Handover Success

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

4.114 C900060113 Number of incoming handover from GSM1800 to GSM900 from the same layer
Description
This counter counts the number of incoming handover executions from the cell (GSM1800) to the target cell (GSM900) in the same layer during BSC-controlled inter-cell handover.

Usage
This counter is used to find out the frequency of incoming handover executions from the cell (GSM1800) to the target cell (GSM900) in the same layer. It reflects the handover situation.

Measurement Point
When the target cell (GSM900) receives the channel activation response message, if the request is due to BSC-controlled inter-cell handover and the source cell (GSM1800) is in the same layer, the counter increments. The measurement point is A, as shown in Figure 4-122.

4-125 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-122 BSC-Controlled Inter-Cell Incoming Handover Execution

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

4.115 C900060114 Number of incoming handover 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
This counter is used to find out the frequency of successful incoming handover from the cell (GSM1800) to the target cell (GSM900) in the same layer. It reflects the handover situation.

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

4-126 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-123 BSC-Controlled Inter-Cell Incoming Handover Success

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

4.116 C900060115 Number of incoming handover from GSM1800 to GSM900 from the upper layer
Description
This counter counts the number of incoming handover executions from the upper layer cell (GSM1800) to the target cell (GSM900) during BSC-controlled inter-cell handover.

Usage
This counter is used to find out the frequency of incoming handover executions from the upper layer cell (GSM1800) to the target cell (GSM900). It reflects the handover situation.

Measurement Point
When the target cell (GSM900) receives the channel activation response message, if the request is due to BSC-controlled inter-cell handover and the source cell (GSM1800) is in the upper layer, the counter increments. The measurement point is A, as shown in Figure 4-124.

4-127 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-124 BSC-Controlled Inter-Cell Incoming Handover Execution

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

4.117 C900060116 Number of incoming handover success from GSM1800 to GSM900 from the upper layer
Description
This counter counts the number of successful incoming handovers from the upper layer cell (GSM1800) to the target cell (GSM900) during BSC-controlled inter-cell handover.

Usage
This counter is used to find out the frequency of successful incoming handover from the upper layer cell (GSM1800) to the target cell (GSM900). It reflects the handover situation.

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

4-128 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-125 BSC-Controlled Inter-Cell Incoming Handover Success

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

4.118 C900060117 Number of incoming handover from GSM1800 to GSM900 from the lower layer
Description
This counter counts the number of incoming handover executions from the lower layer cell (GSM1800) to the target cell (GSM1800) during BSC-controlled inter-cell handover.

Usage
This counter is used to find out the frequency of incoming handover executions from the lower layer cell (GSM1800) to the target cell (GSM1800). It reflects the handover situation.

Measurement Point
When the target cell (GSM900) receives the channel activation response message, if the request is due to BSC-controlled inter-cell handover and the source cell (GSM1800) is in the lower layer, the counter increments. The measurement point is A, as shown in Figure 4-126.

4-129 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-126 BSC-Controlled Inter-Cell Incoming Handover Execution

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

4.119 C900060118 Number of incoming handover success from GSM1800 to GSM900 from the lower layer
Description
This counter counts the number of successful incoming handovers from the lower layer cell (GSM1800) to the target cell (GSM900) during BSC-controlled inter-cell handover.

Usage
This counter is used to find out the frequency of successful incoming handover from the lower layer cell (GSM1800) to the target cell (GSM900). It reflects the handover situation.

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

4-130 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-127 BSC-Controlled Inter-Cell Incoming Handover Success

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure

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 measurement point is A, as shown in Figure 4-128.

4-131 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-128 Intra-Cell Handover Execution

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics

4.121 C900060120 Number of Intra-cell handover success

Description
This counter counts the number of successful intra-cell handovers which are initiated by MS in the source cell.

Usage
This counter is used to find out the frequency of successful intra-cell handover. It is one of the parameters that evaluate handover.

Measurement 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 point is A, as shown in Figure 4-129.
Figure 4-129 Intra-Cell Handover Success

4-132 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics

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 l l After the TCH/H is occupied successfully, if the maximum number of busy TCH/Hs exceeds the counter's recorded value; Before the TCH/H is released, if the maximum number of busy TCH/Hs exceeds the counter's recorded value; When the system reports the periodical measurement data, if the maximum number of busy TCH/Hs exceeds the counter's recorded value.

The measurement point is A, as shown in Figure 4-130.

4-133 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-130 Reporting Measurement Data

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

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.
Figure 4-131 Reporting Measurement Data

4-134 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics

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
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-132.
Figure 4-132 Reporting Measurement Data

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics

4-135 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The counter counts at the following three time points: l l l When an SDCCH is acquired successfully, this counter calculates time and accumulates. When an SDCCH is released, this counter calculates time and accumulates. When the system reports the periodical measurement data, this counter calculates time and accumulates.

The measurement point is A, as shown in Figure 4-133.

Figure 4-133 Reporting Measurement Data

The measurement formula is as follows: l l Measurement value = (Current time Last measurement time point) Number of MSs that are occupying the channels 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.126 C900060125 Average number of available dynamic radio channel

Description
This counter counts the number of FR radio channel which can be assigned normally. The radio channels that can be assigned normally include idle radio channels and occupied radio channels.

Usage
This counter is used to find out the number of available FR radio channels in the current cell. It helps understand the current resource usage situation of the cell.

Measurement Point
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-134.
Figure 4-134 Reporting Measurement Data

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-04-04-002 Intelligent TRX Shutdown

4.127 C900060126 Average number of unavailable dynamic 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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-135.
Figure 4-135 Reporting Measurement Data

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics

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
The counter counts at the following three time points: l l l When a TCH/H is acquired successfully, this counter calculates time and accumulates. When a TCH/H is released, this counter calculates time and accumulates. When the system reports the periodical measurement data, this counter calculates time and accumulates.

The measurement point is A, as shown in Figure 4-136.

4-138 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-136 Reporting Measurement Data

The measurement formula is as follows: l l Measurement value = (Current time Last measurement time point) Number of MSs that are occupying the channels The reported measurement value is accumulated by each measurement value. After each accumulation, the last measurement time point is updated to the current time. If a TCH/H is acquired successfully, Number of MSs that are occupying the channels increases by 1; if a TCH/H is released, Number of MSs that are occupying the channels decreases by 1.

Unit
Second

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-04-04-002 Intelligent TRX Shutdown

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The counter counts at the following three time points: l l l After the TCH/F is occupied successfully, if the maximum number of busy TCH/Fs exceeds the counters recorded value; Before the TCH/F is released, if the maximum number of busy TCH/Hs exceeds the counters recorded value; When the system reports the periodical measurement data, if the maximum number of busy TCH/Fs exceeds the counter's recorded value.

The measurement point is A, as shown in Figure 4-137.

Figure 4-137 Reporting Measurement Data

Unit
Times

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

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Measurement Point
The counter counts at the following three time points: l l l When a TCH/F is acquired successfully, this counter calculates time and accumulates. When a TCH/F is released, this counter calculates time and accumulates. When the system reports the periodical measurement data, this counter calculates time and accumulates.

The measurement point is A, as shown in Figure 4-138.

Figure 4-138 Reporting Measurement Data

The measurement formula is as follows: l l Measurement value = (Current time Last measurement time point) Number of MSs that are occupying the channels The reported measurement value is accumulated by each measurement value. After each accumulation, the last measurement time point is updated to the current time. If a TCH/F is acquired successfully, Number of MSs that are occupying the channels increases by 1; if a TCH/F is released, Number of MSs that are occupying the channels decreases by 1.

Unit
Second

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-04-04-002 Intelligent TRX Shutdown

4.131 C900060130 Number of healthy TRXs

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

4-141 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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-139.
Figure 4-139 Reporting Measurement Data

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
This counter counts when BSC receives the EST_IND message. The measurement point is A4, as shown in Figure 4-140.

4-142 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-140 Radio Access Flow

Unit
Times

4.133 C900060132 Number of SAPI3 link establishment 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-141 Idle-State MT Short Message Flow

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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
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-142.
Figure 4-142 Reporting Measurement Data

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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

4-145 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-143 Reporting Measurement Data

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-04-04-002 Intelligent TRX Shutdown

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-144 Immediate Assignment Flow

Unit
Times

Related Features
ZGB-03-01-004 Immediate TCH Assignment ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-145 Radio Access Flow

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
This counter counts when BSC receives the EST_IND message. The measurement point is A4, as shown in Figure 4-146.

4-148 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-146 Radio Access Flow

Unit
Times

Related Features
ZGB-02-01-001 Paging

4.139 C900060138 Number of TCH/F allocation failure 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). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CMM connection request to BTS. If BTS connection fails due to receiving CMM connection failure message, incorrect CMM connection response message, or timer timeout, this counter accumulates.

Measurement Point
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-147 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.140 C900060139 Number of TCH/F allocation failure 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 failure when assigning voice channel (using speech version 1). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the 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
BSC uses TCH/F for assignment, but the problem such as receiving connection failure message, incorrect connection response message, or timer timeout occurs during BIU connection process. The measurement point is B2, as shown in Figure 4-148.

4-150 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-148 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.141 C900060140 Number of TCH/F allocation failure 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 failure when assigning voice channel (using speech version 1). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for assignment, but the problem such as receiving connection failure message, incorrect connection response message, or timer timeout occurs during TCU connection process. The measurement point is B2, as shown in Figure 4-149.

4-151 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-149 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.142 C900060141 Number of TCH/F allocation failure due to channel activation failure for assignment (speech version2)
Description
This counter counts the number of TCH/F channel allocation failure due to channel activation failure when assigning speech channel (using speech version 2). 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. 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-150 Common Assignment Failure Flow 1 (TC Is Internal)

Unit
Times

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

4.143 C900060142 Number of TCH/F allocation failure due to BTS connection failure for assignment (speech version2)
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 2). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CMM connection request to BTS. If BTS connection fails due to receiving CMM connection failure message, incorrect CMM connection response message, or timer timeout, this counter accumulates.

Measurement Point
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-151.

4-153 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-151 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

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

4.144 C900060143 Number of TCH/F allocation failure due to BIU connection failure for assignment (speech version2)
Description
This counter counts the number of failing to allocate TCH/F channel due to BIU connection failure when assigning voice channel (using speech version 2). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the BIU connection request to BIPB. If BIU connection fails due to receiving BIU connection failure message, incorrect BIU connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for assignment, but the problem such as receiving connection failure message, incorrect connection response message, or timer timeout occurs during BIU connection process. The measurement point is B2, as shown in Figure 4-152.

4-154 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-152 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

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

4.145 C900060144 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version2)
Description
This counter counts the number of failing to allocate TCH/F channel due to TCU connection failure when assigning voice channel (using speech version 2). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for assignment, but the problem such as receiving connection failure message, incorrect connection response message, or timer timeout occurs during TCU connection process. The measurement point is B2, as shown in Figure 4-153.

4-155 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-153 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

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

4.146 C900060145 Number of TCH/F allocation failure due to BTS connection failure for assignment (speech version3)
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 3). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CMM connection request to BTS. If BTS connection fails due to receiving CMM connection failure message, incorrect CMM connection response message, or timer timeout, this counter accumulates.

Measurement Point
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-154.

4-156 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-154 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

4.147 C900060146 Number of TCH/F allocation failure due to BIU connection failure for assignment (speech version3)
Description
This counter counts the number of failing to allocate TCH/F channel due to BIU connection failure when assigning voice channel (using speech version 3). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the BIU connection request to BIPB. If BIU connection fails due to receiving BIU connection failure message, incorrect BIU connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for assignment, but the problem such as receiving connection failure message, incorrect connection response message, or timer timeout occurs during BIU connection process. The measurement point is B2, as shown in Figure 4-155.

4-157 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-155 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

4.148 C900060147 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version3)
Description
This counter counts the number of failing to allocate TCH/F channel due to TCU connection failure when assigning voice channel (using speech version 3). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for assignment, but the problem such as receiving connection failure message, incorrect connection response message, or timer timeout occurs during TCU connection process. The measurement point is B2, as shown in Figure 4-156.

4-158 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-156 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

4.149 C900060148 Number of data TCH/F allocation failure due to BTS connection failure for assignment)
Description
This counter counts the number of failing to allocate TCH/F channel due to BTS connection failure when assigning data channel. After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CMM connection request to BTS. If BTS connection fails due to receiving CMM connection failure message, incorrect CMM connection response message or timer timeout, this counter accumulates.

Measurement Point
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-157.

4-159 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-157 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.150 C900060149 Number of data TCH/F allocation failure due to BIU connection failure for assignment
Description
This counter counts the number of failing to allocate TCH/F channel due to BIU connection failure when assigning data channel. After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the BIU connection request to BIPB. If BIU connection fails due to receiving BIU connection failure message, incorrect BIU connection response message or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for assignment, but receives connection failure message, incorrect connection response message or timer timeout during BIU connection process. The measurement point is B2, as shown in Figure 4-158.

4-160 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-158 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.151 C900060150 Number of data TCH/F allocation failure due to TCU connection failure for assignment
Description
This counter counts the number of failing to allocate TCH/F channel due to TCU connection failure when assigning data channel. After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for assignment, but receiving connection failure message, incorrect connection response message or timer timeout during TCU connection process. The measurement point is B2, as shown in Figure 4-159.

4-161 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-159 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

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. Presently, reasons for handover failure include T3107 timeout, T3103 timeout and external handover timer timeout under the status of ASSIGNING.

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

4-162 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-160 Call Drop due to T3107 Timeout During Intra-Cell Handover

If RANCS is in the status of RADIO_APPLY and sends the inter-cell handover command, then T3103 is started. If RANCS is in the status of ASSIGN and T3103 is timeout, then the counter increments. The measurement point is A, as shown in Figure 4-161.
Figure 4-161 Call Drop due to T3103 Timeout During Inter-Cell Handover

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. The measurement point is A1, as shown in Figure 4-162.

4-163 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-162 Call Drop due to Inter-BSC Handover Failure

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

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. The measurement point is A, as shown in Figure 4-163.

4-164 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-163 Measurement Point of Number of Abis Interface Messages Sent to BTS from BSC

Unit
Times

Related Features
ZGB-02-01-001 Paging

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 increments. The measurement point is A, as shown in Figure 4-164.
Figure 4-164 Measurement Point of Number of Abis Interface Messages Sent to BTS from BSC

Unit
Times
4-165 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGB-02-01-001 Paging

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 increments. The measurement point is A, as shown in Figure 4-165.
Figure 4-165 Measurement Point of Number of Abis Interface Messages Sent to BTS from BSC

Unit
Times

Related Features
ZGB-02-01-001 Paging

4.156 C900060155 Number of available defined TCH/H

Description
iBSC supports the function of full dynamic radio channel. This counter counts the number of available TCH/H channel configured by OMCR in the current cell.

4-166 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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
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-166.
Figure 4-166 Reporting Measurement Data

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-04-04-002 Intelligent TRX Shutdown

4.157 C900060156 Number of TCH/F allocation failure due to channel activation failure for 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). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, if the connection succeeds, BSC sends the channel activation message CHL_ACT to BTS to activate this TCH/F. If channel activation fails due to receiving channel activation failure message, incorrect channel activation response
4-167 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 4-167 Internal Handover Failure Flow 1 (Intra-Cell Handover, TC Is Internal)

Figure 4-168 External Handover Failure Flow 2 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-01-001 Full Rate (FR) Speech Codec ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4-168 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.158 C900060157 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version1)
Description
This counter counts the number of failing to allocate TCH/F channel due to BTS connection failure during voice channel handover (using speech version 1). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CMM connection request to BTS. If BTS connection fails due to receiving CMM connection failure message, incorrect CMM connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F channel for handover, but receives connection failure message, incorrect connection response message, or timer timeout during CMM connection process. The measurement point is C2 as shown in Figure 4-169 and D2 as shown in Figure 4-170.
Figure 4-169 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-170 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

4-169 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGB-01-01-001 Full Rate (FR) Speech Codec ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.159 C900060158 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version1)
Description
This counter counts the number of failing to allocate TCH/F channel due to BIU connection failure during voice channel handover (using speech version 1). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the BIU connection request to BIPB. If BIU connection fails due to receiving BIU connection failure message, incorrect BIU connection response message or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for handover, but receives connection failure message, incorrect connection response message, or timer timeout during BIU connection process. The measurement point is C2 as shown in Figure 4-171 and D2 as shown in Figure 4-172.
Figure 4-171 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-172 External Handover Failure Flow 3 (TC Is Internal)

4-170 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Unit
Times

Related Features
ZGB-01-01-001 Full Rate (FR) Speech Codec ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.160 C900060159 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version1)
Description
This counter counts the number of failing to allocate TCH/F channel due to TCU connection failure during voice channel handover (using speech version 1). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for handover, but receives connection failure message, incorrect connection response message, or timer timeout during TCU connection process. The measurement point is C2 as shown in Figure 4-173 and D2 as shown in Figure 4-174.
Figure 4-173 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

4-171 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-174 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-01-001 Full Rate (FR) Speech Codec ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.161 C900060160 Number of TCH/F allocation failure due to channel activation failure for handover(speech version2)
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 2). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, if the connection succeeds, BSC sends the channel activation message CHL_ACT to BTS to activate this TCH/F. If channel activation fails due to receiving channel 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 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-175 and D3 as shown in Figure 4-176.

4-172 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-175 Internal Handover Failure Flow 1 (Intra-Cell Handover, TC Is Internal)

Figure 4-176 External Handover Failure Flow 2 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.162 C900060161 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version2)
Description
This counter counts the number of failing to allocate TCH/F channel due to BTS connection failure during voice channel handover (using speech version 2). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CMM connection request to BTS. If BTS connection fails due to receiving CMM connection failure message, incorrect CMM connection response message, or timer timeout, this counter accumulates.
4-173 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is C2 as shown in Figure 4-177 and D2 as shown in Figure 4-178.
Figure 4-177 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-178 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.163 C900060162 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version2)
Description
This counter counts the number of failing to allocate TCH/F channel due to BIU connection failure during voice channel handover (using speech version 2).

4-174 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the BIU connection request to BIPB. If BIU connection fails due to receiving BIU connection failure message, incorrect BIU connection response message or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for handover, but receives connection failure message, incorrect connection response message, or timer timeout during BIU connection process. The measurement point is C2 as shown in Figure 4-179 and D2 as shown in Figure 4-180.
Figure 4-179 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-180 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4-175 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.164 C900060163 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version2)
Description
This counter counts the number of failing to allocate TCH/F channel due to TCU connection failure during voice channel handover (using speech version 2). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for handover, but receives connection failure message, incorrect connection response message, or timer timeout during TCU connection process. The measurement point is C2 as shown in Figure 4-181 and D2 as shown in Figure 4-182.
Figure 4-181 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-182 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

4-176 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.165 C900060164 Number of TCH/F allocation failure due to channel activation failure for handover (speech version3)
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 3). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, if the connection succeeds, BSC sends the channel activation message CHL_ACT to BTS to activate this TCH/F. If channel activation fails due to receiving channel 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 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-183 and D3 as shown in Figure 4-184.
Figure 4-183 Internal Handover Failure Flow 1 (Intra-Cell Handover, TC Is Internal)

4-177 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-184 External Handover Failure Flow 2 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

4.166 C900060165 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version3)
Description
This counter counts the number of failing to allocate TCH/F channel due to BTS connection failure during voice channel handover (using speech version 3). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CMM connection request to BTS. If BTS connection fails due to receiving CMM connection failure message, incorrect CMM connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F channel for handover, but receives connection failure message, incorrect connection response message, or timer timeout during CMM connection process. The measurement point is C2 as shown in Figure 4-185 and D2 as shown in Figure 4-186.

4-178 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-185 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-186 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

4.167 C900060166 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version3)
Description
This counter counts the number of failing to allocate TCH/F channel due to BIU connection failure during voice channel handover (using speech version 3). After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the BIU connection request to BIPB. If BIU connection fails due to receiving BIU connection failure message, incorrect BIU connection response message or timer timeout, this counter accumulates.

4-179 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
BSC uses TCH/F for handover, but receives connection failure message, incorrect connection response message, or timer timeout during BIU connection process. The measurement point is C2 as shown in Figure 4-187 and D2 as shown in Figure 4-188.
Figure 4-187 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-188 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

4.168 C900060167 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version3)
Description
This counter counts the number of failing to allocate TCH/F channel due to TCU connection failure during voice channel handover (using speech version 3).
4-180 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for handover, but receives connection failure message, incorrect connection response message, or timer timeout during TCU connection process. The measurement point is C2 as shown in Figure 4-189 and D2 as shown in Figure 4-190.
Figure 4-189 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-190 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)

4-181 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 4-191 Internal Handover Flow (Intra-Cell Handover, TC Is Internal)

4-182 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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

Figure 4-193 External Handover Flow (TC Is Internal)

4-183 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-194 External Handover Flow (TC Is External)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.170 C900060169 Number of data TCH/F allocation failure due to channel activation failure for handover
Description
This counter counts the number of failing to allocate TCH/F channel due to channel activation failure during data channel handover. After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, if the connection succeeds, BSC sends the channel activation message CHL_ACT to BTS to activate this TCH/F. If the 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 as data channel for 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-195 and D3 as shown in Figure 4-196.
4-184 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-195 Internal Handover Failure Flow 1 (Intra-Cell Handover, TC Is Internal)

Figure 4-196 External Handover Failure Flow 2 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.171 C900060170 Number of data TCH/F allocation failure due to BTS connection failure for handover
Description
This counter counts the number of failing to allocate TCH/F channel due to BTS connection failure during data channel handover. After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CMM connection request to BTS. If BTS connection fails due to receiving CMM connection failure message, incorrect CMM connection response message, or timer timeout, this counter accumulates.

4-185 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is C2 as shown in Figure 4-197 and D2 as shown in Figure 4-198.
Figure 4-197 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-198 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.172 C900060171 Number of data TCH/F allocation failure due to BIU connection failure for handover
Description
This counter counts the number of failing to allocate TCH/F channel due to BIU connection failure during data channel handover. After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the BIU connection request to BIPB. If BIU connection
4-186 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

fails due to receiving BIU connection failure message, incorrect BIU connection response message or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for handover, but receives connection failure message, incorrect connection response message, or timer timeout during BIU connection process. The measurement point is C2 as shown in Figure 4-199 and D2 as shown in Figure 4-200.
Figure 4-199 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-200 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4-187 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.173 C900060172 Number of data TCH/F allocation failure due to TCU connection failure for handover
Description
This counter counts the number of failing to allocate TCH/F channel due to TCU connection failure during data channel handover. After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/F for handover, but receives connection failure message, incorrect connection response message, or timer timeout during TCU connection process. The measurement point is C2 as shown in Figure 4-201 and D2 as shown in Figure 4-202.
Figure 4-201 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-202 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels
4-188 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

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. 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-203 and Figure 4-204, and D4 as shown in Figure 4-205 and Figure 4-206.
Figure 4-203 Internal Handover Flow (Intra-Cell Handover, TC Is Internal)

4-189 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

Figure 4-205 External Handover Flow (TC Is Internal)

4-190 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-206 External Handover Flow (TC Is External)

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4.175 C900060174 Number of signaling TCH/H allocation failure for assignment

Description
This counter counts the number of TCH/H channel allocation failures during signaling channel assignment. After BSC responds to 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 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/H channel due to assignment and uses it as signaling channel, but receives channel activation failure message, incorrect channel activation response message, T9103 being timeout, channel instance being released, or channel being forcibly released. The measurement point is A2, as shown in Figure 4-207.
4-191 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-207 Immediate Assignment Allocation Failure Flow 2

Unit
Times

Related Features
ZGB-03-01-004 Immediate TCH Assignment ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.176 C900060175 Number of TCH/H allocation failure due to channel activation failure for assignment (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). After BSC responds to 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. 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/H as voice channel (using speech version 1) 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-208.

4-192 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-208 Common Assignment Failure Flow 1 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.177 C900060176 Number of TCH/H allocation failure due to BTS connection failure for assignment (speech version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to BTS connection failure when assigning voice channel (using speech version 1). After BSC responds to the channel request message to allocate and occupy TCH/H 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/H 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-209.

4-193 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-209 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.178 C900060177 Number of TCH/H allocation failure due to BIU connection failure for assignment (speech version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to BIU connection failure when assigning voice channel (using speech version 1). After BSC responds to the channel request message to allocate and occupy TCH/H 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
BSC uses TCH/H for assignment, but the problem such as receiving connection failure message, incorrect connection response message, or timer timeout occurs during BIU connection process. The measurement point is B2, as shown in Figure 4-210.

4-194 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-210 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.179 C900060178 Number of TCH/H allocation failure due to TCU connection failure for assignment (speech version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to TCU connection failure when assigning voice channel (using speech version 1). After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/H for assignment, but the problem such as receiving connection failure message, incorrect connection response message, or timer timeout occurs during TCU connection process. The measurement point is B2, as shown in Figure 4-211.

4-195 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-211 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.180 C900060179 Number of TCH/H allocation failure due to channel activation failure for handover (speech version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to channel activation failure during voice channel handover (using speech version 1). After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, if the connection succeeds, BSC sends the channel activation message CHL_ACT to BTS to activate this TCH/H. If channel activation fails due to receiving channel 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/H 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-212 and D3 as shown in Figure 4-213.

4-196 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-212 Internal Handover Failure Flow 1 (Intra-Cell Handover, TC Is Internal)

Figure 4-213 External Handover Failure Flow 2 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.181 C900060180 Number of TCH/H allocation failure due to BTS connection failure for handover (speech version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to BTS connection failure during voice channel handover (using speech version 1). After BSC responds to the channel request message to allocate and occupy TCH/H 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.
4-197 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
BSC uses TCH/H channel for handover, but receives connection failure message, incorrect connection response message, or timer timeout during CMM connection process. The measurement point is C2 as shown in Figure 4-214 and D2 as shown in Figure 4-215.
Figure 4-214 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-215 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.182 C900060181 Number of TCH/H allocation failure due to BIU connection failure for handover (speech version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to BIU connection failure during voice channel handover (using speech version 1).
4-198 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

After BSC responds to the channel request message to allocate and occupy TCH/H 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
BSC uses TCH/H for handover, but receives connection failure message, incorrect connection response message, or timer timeout during BIU connection process. The measurement point is C2 as shown in Figure 4-216 and D2 as shown in Figure 4-217.
Figure 4-216 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-217 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4-199 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.183 C900060182 Number of TCH/H allocation failure due to TCU connection failure for handover (speech version1)
Description
This counter counts the number of failing to allocate TCH/H channel due to TCU connection failure during voice channel handover (using speech version 1). After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/H for handover, but receives connection failure message, incorrect connection response message, or timer timeout during TCU connection process. The measurement point is C2 as shown in Figure 4-218 and D2 as shown in Figure 4-219.
Figure 4-218 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-219 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

4-200 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.184 C900060191 Number of TCH/H allocation failure due to channel activation failure for assignment (speech version3)
Description
This counter counts the number of TCH/H channel allocation failure due to channel activation failure when assigning voice channel (using speech version 3). After BSC responds to 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. 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/H as voice channel (using speech version 3) 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-220.
Figure 4-220 Common Assignment Failure Flow 1 (TC Is Internal)

Unit
Times

4-201 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation

4.185 C900060192 Number of TCH/H allocation failure due to BTS connection failure for assignment (speech version3)
Description
This counter counts the number of failing to allocate TCH/H channel due to BTS connection failure when assigning voice channel (using speech version 3). After BSC responds to the channel request message to allocate and occupy TCH/H 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/H 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-221.
Figure 4-221 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation
4-202 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.186 C900060193 Number of TCH/H allocation failure due to BIU connection failure for assignment (speech version3)
Description
This counter counts the number of failing to allocate TCH/H channel due to BIU connection failure when assigning voice channel (using speech version 3). After BSC responds to the channel request message to allocate and occupy TCH/H 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
BSC uses TCH/H for assignment, but the problem such as receiving connection failure message, incorrect connection response message, or timer timeout occurs during BIU connection process. The measurement point is B2, as shown in Figure 4-222.
Figure 4-222 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation

4-203 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.187 C900060194 Number of TCH/H allocation failure due to TCU connection failure for assignment (speech version3)
Description
This counter counts the number of failing to allocate TCH/H channel due to TCU connection failure when assigning voice channel (using speech version 3). After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/H for assignment, but the problem such as receiving connection failure message, incorrect connection response message, or timer timeout occurs during TCU connection process. The measurement point is B2, as shown in Figure 4-223.
Figure 4-223 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation

4-204 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.188 C900060195 Number of TCH/H allocation failure due to channel activation failure for handover (speech version3)
Description
This counter counts the number of failing to allocate TCH/H channel due to channel activation failure during voice channel handover (using speech version 3). After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, if the connection succeeds, BSC sends the channel activation message CHL_ACT to BTS to activate this TCH/H. If channel activation fails due to receiving channel 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/H 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-224 and D3 as shown in Figure 4-225.
Figure 4-224 Internal Handover Failure Flow 1 (Intra-Cell Handover, TC Is Internal)

Figure 4-225 External Handover Failure Flow 2 (TC Is Internal)

4-205 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation

4.189 C900060196 Number of TCH/H allocation failure due to BTS connection failure for handover (speech version3)
Description
This counter counts the number of failing to allocate TCH/H channel due to BTS connection failure during voice channel handover (using speech version 3). After BSC responds to the channel request message to allocate and occupy TCH/H 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/H channel for handover, but receives connection failure message, incorrect connection response message, or timer timeout during CMM connection process. The measurement point is C2 as shown in Figure 4-226 and D2 as shown in Figure 4-227.
Figure 4-226 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

4-206 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-227 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation

4.190 C900060197 Number of TCH/H allocation failure due to BIU connection failure for handover (speech version3)
Description
This counter counts the number of failing to allocate TCH/H channel due to BIU connection failure during voice channel handover (using speech version 3). After BSC responds to the channel request message to allocate and occupy TCH/H 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
BSC uses TCH/H for handover, but receives connection failure message, incorrect connection response message, or timer timeout during BIU connection process. The measurement point is C2 as shown in Figure 4-228 and D2 as shown in Figure 4-229.

4-207 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-228 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-229 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation

4.191 C900060198 Number of TCH/H allocation failure due to TCU connection failure for handover (speech version3)
Description
This counter counts the number of failing to allocate TCH/H channel due to TCU connection failure during voice channel handover (using speech version 3). After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message, or timer timeout, this counter accumulates.
4-208 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Measurement Point
BSC uses TCH/H for handover, but receives connection failure message, incorrect connection response message, or timer timeout during TCU connection process. The measurement point is C2 as shown in Figure 4-230 and D2 as shown in Figure 4-231.
Figure 4-230 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-231 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation

4.192 C900060199 Number of Voice TCH/H assignment success

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

4-209 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 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-232 and Figure 4-233.
Figure 4-232 Common Assignment Flow (TC Is Internal)

Figure 4-233 Common Assignment Flow (TC Is External)

Unit
Times

4-210 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.193 C900060200 Number of Voice TCH/H assignment failure

Description
This counter counts the number of failing to assign TCH/H channel as voice channel. After BSC responds to 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. If BSC does not receive the MS access notification within a certain time, this assignment 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-234.
Figure 4-234 Common Assignment Failure Flow 4 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-001 Half Rate
4-211 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ZGO-03-02-005 Dynamic Half Rate Allocation

4.194 C900060201 Number of Voice TCH/H handover success

Description
This counter counts the number of successful TCH/H 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-235 and Figure 4-236, and D4 as shown in Figure 4-237 and Figure 4-238.
Figure 4-235 Internal Handover Flow (Intra-Cell Handover, TC Is Internal)

4-212 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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

Figure 4-237 External Handover Flow (TC Is Internal)

4-213 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-238 External Handover Flow (TC Is External)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.195 C900060202 Number of data TCH/H allocation failure due to channel activation failure for assignment
Description
This counter counts the number of TCH/H channel allocation failure due to channel 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 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/H channel due to assignment and uses the channel as data channel, but receives channel activation failure message, incorrect channel activation response

4-214 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

message, T9103 being timeout, channel instance being released, or channel being forcibly released. The measurement point is B3, as shown in Figure 4-239.
Figure 4-239 Common Assignment Failure Flow 1 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.196 C900060203 Number of data TCH/H allocation failure due to BTS connection failure for assignment
Description
This counter counts the number of failing to allocate TCH/H channel due to BTS connection failure when assigning data channel. After BSC responds to the channel request message to allocate and occupy TCH/H 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/H 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-240.

4-215 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-240 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.197 C900060204 Number of data TCH/H allocation failure due to BIU connection failure for assignment
Description
This counter counts the number of failing to allocate TCH/H channel due to BIU connection failure when assigning data channel. After BSC responds to the channel request message to allocate and occupy TCH/H 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
BSC uses TCH/H for assignment, but receives connection failure message, incorrect connection response message or timer timeout during BIU connection process. The measurement point is B2, as shown in Figure 4-241.

4-216 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-241 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.198 C900060205 Number of data TCH/H allocation failure due to TCU connection failure for assignment
Description
This counter counts the number of failing to allocate TCH/H channel due to TCU connection failure when assigning data channel. After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/H for assignment, but receiving connection failure message, incorrect connection response message or timer timeout during TCU connection process. The measurement point is B2, as shown in Figure 4-242.

4-217 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-242 Common Assignment Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.199 C900060206 Number of data TCH/H allocation failure due to channel activation failure for handover
Description
This counter counts the number of failing to allocate TCH/H channel due to channel activation failure during data channel handover. After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, if the connection succeeds, BSC sends the channel activation message CHL_ACT to BTS to activate this TCH/H. If the 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/H as data channel for 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-243 and D3 as shown in Figure 4-244.

4-218 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-243 Internal Handover Failure Flow 1 (Intra-Cell Handover, TC Is Internal)

Figure 4-244 External Handover Failure Flow 2 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.200 C900060207 Number of data TCH/H allocation failure due to BTS connection failure for handover
Description
This counter counts the number of failing to allocate TCH/H channel due to BTS connection failure during data channel handover. After BSC responds to the channel request message to allocate and occupy TCH/H 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.

4-219 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
BSC uses TCH/H channel for handover, but receives connection failure message, incorrect connection response message, or timer timeout during CMM connection process. The measurement point is C2 as shown in Figure 4-245 and D2 as shown in Figure 4-246.
Figure 4-245 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-246 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.201 C900060208 Number of data TCH/H allocation failure due to BIU connection failure for handover
Description
This counter counts the number of failing to allocate TCH/H channel due to BIU connection failure during data channel handover. After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the BIU connection request to BIPB. If BIU connection
4-220 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

fails due to receiving BIU connection failure message, incorrect BIU connection response message or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/H for handover, but receives connection failure message, incorrect connection response message, or timer timeout during BIU connection process. The measurement point is C2 as shown in Figure 4-247 and D2 as shown in Figure 4-248.
Figure 4-247 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-248 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4-221 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.202 C900060209 Number of data TCH/H allocation failure due to TCU connection failure for handover
Description
This counter counts the number of failing to allocate TCH/H channel due to TCU connection failure during data channel handover. After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the TCU connection request to DRTB. If TCU connection fails due to receiving TCU connection failure message, incorrect TCU connection response message, or timer timeout, this counter accumulates.

Measurement Point
BSC uses TCH/H for handover, but receives connection failure message, incorrect connection response message, or timer timeout during TCU connection process. The measurement point is C2 as shown in Figure 4-249 and D2 as shown in Figure 4-250.
Figure 4-249 Internal Handover Failure Flow 2 (Intra-Cell Handover, TC Is Internal)

Figure 4-250 External Handover Failure Flow 3 (TC Is Internal)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover
4-222 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.203 C900060210 Number of data TCH/H assignment success

Description
This counter counts the number of successful assignments of TCH/H as data channel. After BSC responds to 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 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-251 and Figure 4-252.
Figure 4-251 Common Assignment Flow (TC Is Internal)

4-223 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-252 Common Assignment Flow (TC Is External)

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.204 C900060211 Number of data TCH/H assignment failure

Description
This counter counts the number of failing to assign TCH/H channel as data channel. After BSC responds to 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. If BSC does not receive the MS access notification within a certain time, this assignment 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-253.

4-224 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-253 Common Assignment Failure Flow 4 (TC Is Internal)

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.205 C900060212 Number of data TCH/H handover success

Description
This counter counts the number of successful TCH/H channel handover during data channel handover. When BSC detects the successful handover message sent by MS on newly-allocated TCH/H 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-254 and Figure 4-255, and D4 as shown in Figure 4-256 and Figure 4-257.
4-225 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-254 Internal Handover Flow (Intra-Cell Handover, TC Is Internal)

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

4-226 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-256 External Handover Flow (TC Is Internal)

Figure 4-257 External Handover Flow (TC Is External)

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4-227 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.206 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 measurement point is A2, as shown in Figure 4-258.
Figure 4-258 Forced Release Execution

Unit
Times

4-228 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-03-001 eMLPP

4.207 C900060214 Number of BSC-controlled incoming handover due to queues

Description
During BSC-controlled inter-cell incoming handover process, the counter counts the number of queuing executions due to no available radio resource in the target cell.

Usage
This counter is used to find out the frequency of queuing execution during BSC-controlled inter-cell incoming handover process. It reflects the status of the handover flow.

Measurement Point
The target cell within BSC receives the radio channel request message. If the request is due to BSC-controlled inter-cell incoming handover and the target cell has no available radio channels, the target instance is added to the waiting queue. When the target cell receives the message of resource available, the counter increments. The measurement point is A2, as shown in Figure 4-259.

4-229 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-259 Queuing Execution

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-03-001 eMLPP

4.208 C900060215 Number of BSC-controlled incoming handover due to forced handover

Description
During BSC-controlled inter-cell incoming handover process, the counter counts the number of forced handover executions due to no available radio resource in the target cell.

4-230 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Usage
This counter is used to find out the frequency of forced handover execution during BSC-controlled inter-cell incoming handover process. It reflects the status of the handover flow.

Measurement Point
The target cell within BSC receives the radio channel request message. If the request is due to BSC-controlled inter-cell incoming handover and the target cell has no available radio channels, the forced handover message is sent to the forced handover instance and the target instance is added to the waiting queue. When the target cell receives the message of resource available, the counter increments. The measurement point is A2, as shown in Figure 4-260.
Figure 4-260 Forced Handover Execution

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-03-001 eMLPP

4-231 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.209 C900060216 Number of MSC-controlled incoming handover due to forced handover

Description
During MSC-controlled inter-BSC incoming handover process, the counter counts the number of forced handover executions due to no available radio resource in the target cell.

Usage
This counter is used to find out the frequency of forced handover executions during MSC-controlled inter-BSC incoming handover process. It reflects the status of the handover flow.

Measurement 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-261.
Figure 4-261 Forced Handover Execution

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-03-001 eMLPP

4-232 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.210 C900060217 Number of unavailable defined TCH/H

Description
iBSC supports the function of full dynamic radio channel. This counter counts the number of unavailable TCH/H channel configured by OMCR in the current cell.

Usage
This counter is used to find out the number of unavailable TCH/H channel in the current cell to facilitate eliminating the fault.

Measurement Point
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-262.
Figure 4-262 Reporting Measurement Data

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation

4-233 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.211 C900060218 Number of unavailable defined TCH/F

Description
iBSC supports the function of full dynamic wireless channel. This counter counts the number of unavailable TCH/F channel configured by OMCR in the current cell.

Usage
This counter is used to find out the number of unavailable TCH/F channel in the current cell to facilitate eliminating the fault.

Measurement Point
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-263.
Figure 4-263 Reporting Measurement Data

Unit
Times

Related Features
ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-003 Full dynamic channel allocation on Um interface

4-234 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.212 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. Presently, reasons for handover failure include T3107 timeout, T3103 timeout and external handover timer timeout under the status of ASSIGNING.

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: 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-264.
Figure 4-264 Call Drop due to T3107 Timeout During Intra-Cell Handover

If RANCS is in the status of RADIO_APPLY and sends the inter-cell handover command, then T3103 is started. If RANCS is in the status of ASSIGN and T3103 is timeout, then the counter increments. The measurement point is A, as shown in Figure 4-265.

4-235 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-265 Call Drop due to T3103 Timeout During Inter-Cell Handover

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. The measurement point is A1, as shown in Figure 4-266.
Figure 4-266 Call Drop due to Inter-BSC Handover Failure

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4-236 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.213 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. Presently, reasons for handover failure include T3107 timeout, T3103 timeout and external handover timer timeout under the status of ASSIGNING.

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: 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-267.
Figure 4-267 Call Drop due to T3107 Timeout During Intra-Cell Handover

If RANCS is in the status of RADIO_APPLY and sends the inter-cell handover command, then T3103 is started. If RANCS is in the status of ASSIGN and T3103 is timeout, then the counter increments. The measurement point is A, as shown in Figure 4-268.

4-237 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-268 Call Drop due to T3103 Timeout During Inter-Cell Handover

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. The measurement point is A1, as shown in Figure 4-269.
Figure 4-269 Call Drop due to Inter-BSC Handover Failure

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4-238 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.214 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. Presently, reasons for handover failure include T3107 timeout, T3103 timeout and external handover timer timeout under the status of ASSIGNING.

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: 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-270.
Figure 4-270 Call Drop due to T3107 Timeout During Intra-Cell Handover

If RANCS is in the status of RADIO_APPLY and sends the inter-cell handover command, then T3103 is started. If RANCS is in the status of ASSIGN and T3103 is timeout, then the counter increments. The measurement point is A, as shown in Figure 4-271.

4-239 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-271 Call Drop due to T3103 Timeout During Inter-Cell Handover

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. The measurement point is A1, as shown in Figure 4-272.
Figure 4-272 Call Drop due to Inter-BSC Handover Failure

Unit
Times

Related Features
ZGB-01-03-002 Data Traffic Channels ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

4-240 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.215 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. Presently, reasons for handover failure include T3107 timeout, T3103 timeout and external handover timer timeout under the status of ASSIGNING.

Usage
This counter is used to find out the frequency of call drop due to handover failure on TCH/H signaling channel.

Measurement Point
TCH/H signaling channel 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-273.
Figure 4-273 Call Drop due to T3107 Timeout During Intra-Cell Handover

If RANCS is in the status of RADIO_APPLY and sends the inter-cell handover command, then T3103 is started. If RANCS is in the status of ASSIGN and T3103 is timeout, then the counter increments. The measurement point is A, as shown in Figure 4-274.

4-241 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-274 Call Drop due to T3103 Timeout During Inter-Cell Handover

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. The measurement point is A1, as shown in Figure 4-275.
Figure 4-275 Call Drop due to Inter-BSC Handover Failure

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4-242 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.216 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. Presently, reasons for handover failure include T3107 timeout, T3103 timeout and external handover timer timeout under the status of ASSIGNING.

Usage
This counter is used to find out the frequency of call drop due to handover failure on TCH/H data channel.

Measurement Point
TCH/H data channel 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-276.
Figure 4-276 Call Drop due to T3107 Timeout During Intra-Cell Handover

If RANCS is in the status of RADIO_APPLY and sends the inter-cell handover command, then T3103 is started. If RANCS is in the status of ASSIGN and T3103 is timeout, then the counter increments. The measurement point is A, as shown in Figure 4-277.

4-243 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-277 Call Drop due to T3103 Timeout During Inter-Cell Handover

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. The measurement point is A1, as shown in Figure 4-278.
Figure 4-278 Call Drop due to Inter-BSC Handover Failure

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4-244 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.217 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 increments. The measurement point is A, as shown in Figure 4-279.
Figure 4-279 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4-245 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.218 C900060225 Number of TCH/H handover attempts 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
BSC performs handover decision after receiving measurement report on TCH/H channel. If handover decision succeeds and the handover is due to DL strength, this counter increments. The measurement point is A, as shown in Figure 4-280.
Figure 4-280 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4-246 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.219 C900060226 Number of TCH/H handover attempts 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
BSC performs handover decision after receiving measurement report on TCH/H channel. If handover decision succeeds and the handover is due to UL quality, this counter increments. The measurement point is A, as shown in Figure 4-281.
Figure 4-281 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.220 C900060227 Number of TCH/H handover attempts due to DL quality

Description
This counter counts the number of handover attempts due to DL quality too poor on TCH/H channel.
4-247 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
BSC performs handover decision after receiving measurement report on TCH/H channel. If handover decision succeeds and the handover is due to DL quality, this counter increments. The measurement point is A, as shown in Figure 4-282.
Figure 4-282 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.221 C900060228 Number of TCH/H handover attempts due to UL interference

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-248 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

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 interference, this counter increments. The measurement point is A, as shown in Figure 4-283.
Figure 4-283 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.222 C900060229 Number of TCH/H handover attempts due to DL interference

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
BSC performs handover decision after receiving measurement report on TCH/H channel. If handover decision succeeds and the handover is due to DL interference, this counter increments. The measurement point is A, as shown in Figure 4-284.

4-249 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-284 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.223 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
BSC performs handover decision after receiving measurement report on TCH/H channel. If handover decision succeeds and the handover is due to too large C/I ratio, this counter increments. The measurement point is A, as shown in Figure 4-285.

4-250 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-285 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.224 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
BSC performs handover decision after receiving measurement report on TCH/H channel. If handover decision succeeds and the handover is due to too low C/I ratio, this counter increments. The measurement point is A, as shown in Figure 4-286.

4-251 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-286 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.225 C900060232 Number of TCH/H handover attempts 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
BSC performs handover decision after receiving measurement report on TCH/H channel. If handover decision succeeds and the handover is due to PBGT value, this counter increments. The measurement point is A, as shown in Figure 4-287.

4-252 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-287 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.226 C900060233 Number of TCH/H handover attempts 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
BSC performs handover decision after receiving measurement report on TCH/H channel. If handover decision succeeds and the handover is due to too large TA, this counter increments. The measurement point is A, as shown in Figure 4-288.

4-253 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 4-288 Handover Decision

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.227 C900060234 Number of TCH/H handover attempts due to other reasons

Description
This counter counts the number of handover attempts due to any other reason beyond the handover reasons mentioned previously.

Usage
This counter is used to find out the frequency of handover due to any other reason.

Measurement Point
BSC performs handover decision after receiving measurement report on TCH/H channel. 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-289.
Figure 4-289 Handover Decision

4-254 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.228 C900060235 Number of signaling TCH/H 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-290.
Figure 4-290 Immediate Assignment Flow

Unit
Times
4-255 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGB-03-01-004 Immediate TCH Assignment ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

4.229 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 point is A4, as shown in Figure 4-291.
Figure 4-291 Radio Access Flow

Unit
Times
4-256 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.230 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
This counter is used to find out the frequency of MSC-controlled inter-BSC outgoing handover that is initiated by MS. The source cell and the target cell are of different frequency bands.

Measurement Point
BSC performs handover decision after receiving the measurement report sent by MS. If the decision indicates that inter-cell handover is necessary and if the current cell to which the handover is attempted is a cell under different BSC, then BSC sends the handover request A_HO_RQD to MSC to trigger inter-BSC handover. If BSC receives the handover command returned from MSC and if the source cell and the target cell are of different frequency bands, then this counter increments. The measurement point is A, as shown in Figure 4-292.
Figure 4-292 MSC-Controlled Outgoing Handover Execution

Unit
Times

Related Features
ZGO-05-02-010 Multi-band Networking

4-257 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.231 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
This counter is used to find out the frequency of successful MSC-controlled inter-BSC outgoing handover that is initiated by MS. The source cell and the target cell are of different frequency bands.

Measurement Point
BSC performs handover decision after receiving the measurement report sent by MS. If the decision indicates that inter-cell handover is necessary and if the current cell to which the handover is attempted is a cell under different BSC, then BSC sends the handover request A_HO_RQD to MSC to trigger inter-BSC handover. If MS accesses the target cell successfully, the source cell receives the release command issued by MSC, if the source cell and the target cell are of different frequency bands, then this counter increments. The measurement point is A, as shown in Figure 4-293.
Figure 4-293 MSC-Controlled Outgoing Handover Success

Unit
Times

Related Features
ZGO-05-02-010 Multi-band Networking

4-258 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

4.232 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 shown in Figure 4-294.
Figure 4-294 MSC-Controlled Incoming Handover Execution

Unit
Times

Related Features
ZGO-05-02-010 Multi-band Networking

4-259 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.233 C900060240 Number of dual band incoming 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, as shown in Figure 4-295.
Figure 4-295 MSC-Controlled Incoming Handover Success

Unit
Times

Related Features
ZGO-05-02-010 Multi-band Networking

4.234 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-260 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

If BSC receives the correct EST_IND message within specified time, it indicates that the SDCCH channel assignment succeeds, C900060241 and C900060242 accumulate simultaneously. If BSC receives the incorrect EST_IND message or T3101 is timeout, it indicates that the SDCCH channel assignment fails, C900060241 and C900060243 accumulate simultaneously.

Usage
This counter counts the number of SDCCH channel assignment attempts when BSC sends the IMM_ASS message to notify MS to use the allocated SDCCH channel. The counter's value includes the number of assignment success (C900060242) and the number of assignment failure (C900060243).

Measurement Point
This counter counts when BSC receives the EST_IND message or the assignment completion message, or when T3101 is timeout (C900060242 + C900060243). The measurement point is A2, as shown in Figure 4-296.
Figure 4-296 Immediate Assignment Flow

Unit
Times

Related Features
ZGB-03-02-003 Dynamic Configuration of SDCCH

4-261 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

4.235 C900060242 Number of SDCCH assignments success

Description
After BSC responds to the channel request to allocate and activate SDCCH channel successfully, BSC sends the IMM_ASS message to notify MS to use this channel. After MS receives this message, it sends SABM frame to BTS on SDCCH. BTS then sends the EST_IND message to BSC after receiving SABM frame. If BSC receives the correct EST_IND message within 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-297.
Figure 4-297 Immediate Assignment Flow

Unit
Times

4-262 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Related Features
ZGB-03-02-003 Dynamic Configuration of SDCCH

4.236 C900060243 Number of SDCCH assignment failure

Description
After BSC responds to the channel request to allocate and activate SDCCH channel successfully, BSC sends the IMM_ASS message to notify MS to use this channel. After MS receives this message, it sends SABM frame to BTS on SDCCH. BTS then sends the EST_IND message to BSC after receiving SABM frame. If BSC receives the 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-298.
Figure 4-298 Immediate Assignment Flow

4-263 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGB-03-02-003 Dynamic Configuration of SDCCH

4.237 C900060244 Number of voice TCH/F drops due 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-299.

4-264 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 4 CS Basic Measurement

Figure 4-299 Call Drops Caused by Radio Link Failure During Assignment

Unit
Times

Related Features
ZGB-03-02-003 Dynamic Configuration of SDCCH ZGB-06-01-001 Monitoring Um Interface

4.238 C900060245 Number of voice TCH/H drops due to radio link failure
Description
This counter counts the number of voice TCH/H drops due to radio link failure. After MS applies for TCH/H voice channel, call drops. If this problem is caused by radio link failure, then this counter increments.
4-265 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-300.
Figure 4-300 Call Drops Caused by Radio Link Failure During Assignment

Unit
Times

Related Features
ZGB-06-01-001 Monitoring Um Interface ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
4-266 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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
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.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
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-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6

Downlink Data TBF Measurement

Table of Contents
Overview ....................................................................................................................6-3 C901000001 Number of GPRS DL TBF resumption in delay state .............................6-3 C901000005 Number of GPRS DL TBF establishment failure on PACCH due to time out ......................................................................................................................6-4 C901000006 Number of GPRS DL TBF establishment failure on PACCH due to other reasons .............................................................................................................6-5 C901000009 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to time out ...........................................................................................................6-6 C901000010 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to other reasons ..................................................................................................6-7 C901000011 Number of GPRS DL TBF establishment execution on CCCH/PCCCH..6-8 C901000012 Number of GPRS DL TBF establishment execution failure on CCCH/PCCCH due to polling failed............................................................................6-9 C901000013 Number of GPRS DL TBF establishment execution success on CCCH/PCCCH due to polling succeeded .................................................................6-11 C901000014 Number of GPRS DL TBF establishment success on CCCH/PCCCH..6-13 C901000015 Number of GPRS DL TBF normal release ...........................................6-15 C901000023 Number of EGPRS DL TBF resumption in delay state .........................6-16 C901000027 Number of EGPRS DL TBF establishment failure on PACCH due to time out ....................................................................................................................6-18 C901000028 Number of EGPRS DL TBF establishment failure on PACCH due to other reasons ...........................................................................................................6-18 C901000031 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to time out .........................................................................................................6-19 C901000032 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to other reasons ................................................................................................6-20 C901000033 Number of EGPRS DL TBF establishment execution on CCCH/PCCCH .........................................................................................................6-21 C901000034 Number of EGPRS DL TBF establishment execution failure on CCCH/PCCCH due to polling failed..........................................................................6-23 C901000035 Number of EGPRS DL TBF establishment execution success on CCCH/PCCCH due to polling succeeded .................................................................6-25 C901000036 Number of EGPRS DL TBF establishment success on CCCH/PCCCH .........................................................................................................6-27
6-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901000037 Number of EGPRS DL TBF normal release.........................................6-29 C901000045 Time of GPRS DL TBF connection ......................................................6-30 C901000046 Time of EGPRS DL TBF connection....................................................6-31 C901000047 Time of DL signaling TBF connection ..................................................6-32 C901000048 Max number of GPRS DL TBF simultaneous establishment ................6-32 C901000050 Max number of EGPRS DL TBF simultaneous establishment..............6-33 C901000052 Number of GPRS DL signaling TBF normal release ............................6-33 C901000058 Number of EGPRS DL signaling TBF normal release ..........................6-35 C901000066 Number of EGPRS2-A TBF restarting in downlink delay state .............6-36 C901000067 Number of downlink EGPRS2-A TBF establishment requests before T3192 expires ..........................................................................................................6-36 C901000068 Number of establishing downlink EGPRS2-A TBF without requesting downlink channel resource .......................................................................................6-37 C901000069 Number of requests for establishing downlink EGPRS2-A TBF on PACCH.....................................................................................................................6-38 C901000070 Number of Failures in Establishing Downlink EGPRS2-A TBF on PACCH Due to Timeout in Resource Assignment.....................................................6-39 C901000071 Number of Failures in Establishing Downlink EGPRS2-A TBF on PACCH Due to Other Causes...................................................................................6-40 C901000072 Number of Successfully Establishing Downlink EGPRS2-A TBF on PACCH.....................................................................................................................6-40 C901000073 Number of Requests for Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH .........................................................................................................6-42 C901000074 Number of Failures in Establishing Downlink EGPRS2-A TBF on CCCH/PCCCH Due to Timeout in Resource Assignment .........................................6-43 C901000075 Number of Failures in Establishing Downlink EGPRS2-A TBF on CCCH/PCCCH Due to Other Causes .......................................................................6-44 C901000076 Number of Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH .6-44 C901000077 Number of Failures in Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH Due to Polling Failure.......................................................................6-46 C901000078 Number of Successfully Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH Due to Polling Success ....................................................................6-48 C901000079 Number of Successfully Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH .........................................................................................................6-50 C901000080 Times of Normal Releasing EGPRS2-A Downlink TBF ........................6-52 C901000081 Number of Releases of EGPRS2-A Downlink TBF Due to N3105 Overflow...................................................................................................................6-53 C901000082 Number of Abnormal Releases of EGPRS2-A Downlink TBF ..............6-54 C901000083 Number of Abnormal Releases of EGPRS2-A Downlink TBF by Control Plane ...........................................................................................................6-54 C901000084 Number of Abnormal Releases of EGPRS2-A Downlink TBF Due to Instance Suspension ................................................................................................6-55 C901000085 Number of Abnormal Releases of EGPRS2-A Downlink TBF Due to Internal Error ............................................................................................................6-56 C901000086 Number of EGPRS2-A Downlink Signaling TBF Establishments..........6-57
6-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

C901000087 Number of EGPRS2-A Downlink Data TBF Establishments.................6-57 C901000088 Total Time of EGPRS2-A Downlink TBF Connection ...........................6-58 C901000089 Maximum Number of EGPRS2-A Downlink TBF Established Simultaneously.........................................................................................................6-59 C901000090 Average Number of EGPRS2-A Downlink TBF Established Simultaneously.........................................................................................................6-59 C901000091 Number of Normal Releases of EGPRS2-A Signaling Downlink TBF...6-59 C901000092 Number of Releases of EGPRS2-A Signaling Downlink TBF Due to N3105 Overflow .......................................................................................................6-61 C901000093 Number of Abnormal Releases of EGPRS2-A Signaling Downlink TBF ..........................................................................................................................6-62 C901000094 Number of Abnormal Releases of EGPRS2-A Signaling Downlink TBF by Control Plane ...............................................................................................6-63 C901000095 Number of Abnormal Releases of EGPRS2-A Signaling Downlink TBF Due to Instance Suspension .............................................................................6-63 C901000096 Number of Abnormal Releases of EGPRS2-A Signaling Downlink TBF Due to Internal Error .........................................................................................6-64 C901000097 Number of EGPRS2-A Data Downlink TBF Establishment on PACCH .6-65 C901000098 Peak Downlink GPRS Throughput.......................................................6-65 C901000099 Peak Downlink EGPRS Throughput ....................................................6-65

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.

6-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 is A, as shown in Figure 6-1.
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

6.3 C901000005 Number of GPRS DL TBF establishment failure on PACCH due to time out
Definition
Number of GPRS DL TBF establishment failure on PACCH due to time out

6-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Description
In the UL transmission state, when SGSN DL LLC frame arrives, the DL TBF transmission should be established. If there is no reserved DL resource, the user plane will ask the control plane to allocate resource. This counter counts the number of non-responses from the control plane in this case.

Measurement Point
When the BSC sends DL 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

6.4 C901000006 Number of GPRS DL TBF establishment 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.
6-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

6.5 C901000009 Number of GPRS DL TBF establishment 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)

6-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Figure 6-4 Failures For Establishing DL GPRS TBF On CCCH/PCCCH (2)

Unit
Times

6.6 C901000010 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to other reasons
Definition
Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to other reasons

Description
When MS is in the idle state, after BSC receives DL LLC frames from SGSN, BSC should originate DL TBF establishment assigned on CCCH/PCCCH. The user plane sends a DL establishment request to the control plane. If it receives the instance release message from the control plane or fails to create DL RLC instance after receiving the resource assignment message, it indicates that the DL TBF establishment fails.

Measurement 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, this counter increments.

Unit
Times

6-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

6.7 C901000011 Number of GPRS DL TBF establishment execution on CCCH/PCCCH

Definition
Number of GPRS DL TBF establishment execution on CCCH/PCCCH

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

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

6-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

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 shown in Figure 6-6.
Figure 6-6 LLC Frame Transmits GTTP Message In DTM Mode

In the DTM mode, this counter increments when the user plane receives the DTM assignment message. The measurement point is A, as shown in Figure 6-7.
Figure 6-7 DTM Assignment In DTM Mode

Unit
Times

6.8 C901000012 Number of GPRS DL TBF establishment 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

6-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. 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. While waiting for MSs responding with the AB form of packet control ack message, if the release request is received from control plane, this counter increments. The measurement point is A, as shown in Figure 6-9.

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

6-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

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

Unit
Times

6.9 C901000013 Number of GPRS DL TBF establishment execution success on CCCH/PCCCH due to polling succeeded
Definition
Number of Number of GPRS DL TBF establishment execution on CCCH/PCCCH 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
6-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

l l

the BSC receives the packet control ack message and sends the message of timing advance setting, it indicates that the operation is successful. In the DTM mode, if the user plane receives the DTM assignment message from the control plane, the operation is considered to be successful. Besides, in the DTM mode, if the user plane receives the DTM sent message from the control plane, to keep the consistency of DL TBF establishment attempts and successful establishments, the DL TBF establishment is also considered to be successful.

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 as shown in Figure 6-12.
Figure 6-10 Normal Establishment Of DL GPRS TBF On CCCH/PCCCH

6-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Figure 6-11 LLC Frame Transmits GTTP Message In DTM Mode

Figure 6-12 DTM Assignment In DTM Mode

Unit
Times

6.10 C901000014 Number of GPRS DL TBF establishment success on CCCH/PCCCH

Definition
Number of Number of GPRS DL TBF establishment execution on CCCH/PCCCH DL TBF establishment success on CCCH/PCCCH

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. 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
6-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

l l

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

l l

Figure 6-13 Normal Establishment Of DL GPRS TBF On CCCH/PCCCH

6-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Figure 6-14 LLC Frame Transmits GTTP Message In DTM Mode

Figure 6-15 DTM Assignment In DTM Mode

Unit
Times

6.11 C901000015 Number of GPRS DL TBF normal release

Definition
Number of Number of GPRS DL TBF establishment execution on CCCH/PCCCH DL TBF normal release

Description
When the DL GPRS TBF sends the last data block, it sets FBI to 1 and sets the RRBP bit to let MS send the DL response message. After BSC receives the last response message (FAI=1), it is considered that the DL transmission is executed normally. In the DTM mode, if the user plane receives the data sent message from the control plane, to keep measurement consistency, it is considered that the DL TBF is released normally.

6-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

Figure 6-17 LLC Frame Transmits GTTP Message In DTM Mode

Unit
Times

6.12 C901000023 Number of EGPRS DL TBF resumption in delay state

Definition
Number of EGPRS DL TBF resumption in delay state

6-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Description
This counter counts the number of retransmissions after the DL EGPRS TBF finishes LLC frame transmission and receives new LLC frames.

Measurement Point
After the DL EGPRS TBF transmits all LLC frames and before the DL RLC block with FBI = 1 is transmitted, if the DL TBF receives new LLC frames, this counter increments. The measurement point is A, as shown in Figure 6-18.
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

6-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

6.13 C901000027 Number of EGPRS DL TBF 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.

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

6.14 C901000028 Number of EGPRS DL TBF establishment failure on PACCH due to other reasons
Definition
Number of EGPRS DL TBF establishment failure on PACCH due to other reasons

6-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Description
This counter counts the number of TBF establishment failures caused by other reasons than non-responses from the control plane when PACCH of EGPRS TBF tries to establish DL TBF. The other reasons here include failed transmission of assignment messages and failed creation of DL RLC instances.

Measurement Point
When PACCH fails to send the assignment messages or fails to create DL RLC instances, the counter increments.

Unit
Times

6.15 C901000031 Number of EGPRS DL TBF 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
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 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-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 6-20 Failures For Establishing DL GPRS TBF On CCCH/PCCCH (1)

Figure 6-21 Failures For Establishing DL GPRS TBF On CCCH/PCCCH (2)

Unit
Times

6.16 C901000032 Number of EGPRS DL TBF 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
When MS is in the idle state, after BSC receives DL LLC frames from SGSN, BSC should originate DL TBF establishment assigned on CCCH/PCCCH. The user plane sends a DL establishment request to the control plane. If it receives the instance release message from the control plane or fails to create DL RLC instance after receiving the resource assignment message, it indicates that the DL TBF establishment fails.

6-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Measurement Point
During the DL EGRPS TBF establishment on CCCH/PCCCH, after the user plane sends the request to the control plane, if it receives the instance release message from the control plane or fails to create DL RLC instance after receiving the resource assignment message, this counter increments.

Unit
Times

6.17 C901000033 Number of EGPRS DL TBF establishment execution on CCCH/PCCCH

Definition
Number of EGPRS DL TBF establishment execution on CCCH/PCCCH

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

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.

6-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 6-22 Normal Establishment Of DL GPRS TBF On CCCH/PCCCH

In the DTM mode, this counter increments when the user plane receives the DTM sent message (the LLC frame has been sent). The measurement point is A, as shown in Figure 6-23.
Figure 6-23 LLC Frame Transmits GTTP Message In DTM Mode

In the DTM mode, this counter increments when the user plane receives the DTM assignment message. The measurement point is A, as shown in Figure 6-24.

6-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Figure 6-24 DTM Assignment In DTM Mode

Unit
Times

6.18 C901000034 Number of EGPRS DL TBF 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
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 MS does not respond, it indicates the DL establishment fails.

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-25. While waiting for MSs responding with the AB form of packet control ack message, if the release request is received from control plane, this counter increments. The measurement point is A, as shown in Figure 6-26.

6-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

6.19 C901000035 Number of EGPRS DL TBF 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
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. In the DTM mode, if the user plane receives the DTM assignment message from the control plane, the operation is considered to be successful. Besides, in the DTM mode, if the user plane receives the DTM sent message from the control plane, to keep the consistency of DL TBF establishment attempts and successful establishments, the DL TBF establishment is also considered to be successful.

l l

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 as shown in Figure 6-29.

6-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 6-27 Normal Establishment Of DL GPRS TBF On CCCH/PCCCH

Figure 6-28 LLC Frame Transmits GTTP Message In DTM Mode

Figure 6-29 DTM Assignment In DTM Mode

Unit
Times
6-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

6.20 C901000036 Number of EGPRS DL TBF establishment success on CCCH/PCCCH

Definition
Number of EGPRS DL TBF establishment success on CCCH/PCCCH

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. 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. In the DTM mode, if the user plane receives the DTM assignment message from the control plane, the operation is considered to be successful. Besides, in the DTM mode, if the user plane receives the DTM sent message from the control plane, to keep the consistency of DL TBF establishment attempts and successful establishments, the EGPRS DL TBF establishment is also considered to be successful.

l l

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. If the assignment is on CCCH, after the user plane receives the packet control ack message from MS and successfully sends the DL assignment message, the counter increments. In the DTM mode, when the user plane receives the DTM sent/assignment message from the control plane, the counter increments. The measurement points are A3 (PCCCH) and A4 (CCCH), as shown in Figure 6-30, A as shown in Figure 6-31, and A as shown in Figure 6-32.

l l

6-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 6-30 Normal Establishment Of DL GPRS TBF On CCCH/PCCCH

Figure 6-31 LLC Frame Transmits GTTP Message In DTM Mode

Figure 6-32 DTM Assignment In DTM Mode

Unit
Times
6-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

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 message (FAI=1), it is considered that the DL transmission is executed normally. In the DTM mode, if the user plane receives the data sent message from the control plane, to keep measurement consistency, it is considered that the DL TBF is released normally.

Measurement Point
After the DL EGPRS TBF transmits the last data block (FBI=1) and when BSC receives the last DL response message (FAI=1), this counter increments. The measurement points are A, as shown in Figure 6-33andFigure 6-34.
Figure 6-33 Normal Release Of DL TBF

6-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 6-34 LLC Frame Transmits GTTP Message In DTM Mode

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 l (1) When GPRS TBF RLC transmission starts, this counter accumulates. (2) When GPRS TBF RLC transmission is released normally (in the acknowledged mode, BSC receives the response with FAI=1; or in the non-acknowledged mode, BSC receives the Packet Control Ack message), this counter accumulates. (3) When GPRS TBF RLC transmission is released abnormally (including N3105 overflow and T3191 timeout), this counter accumulates. (4) When the measurement value is acquired regularly, this counter accumulates. 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.

l l l

6-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

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.
Figure 6-36 Measurement Of Cumulated Overall DL Connecting Time

Unit
Second

6-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 6-37 Measurement Of Cumulated Overall DL Connecting Time

Unit
Seconds

6.25 C901000048 Max number of GPRS DL TBF simultaneous establishment

Definition
Max number of GPRS DL TBF simultaneous establishment

Description
The counter counts the maximum number of DL GPRS TBFs that are established simultaneously within a cell.

Measurement 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-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

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 simultaneous establishment

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 l When EGPRS TBF RLC transmission starts, the EGPRS TBFs in the cell increments by 1 and compares with the saved maximum value. When the measurement value is acquired regularly, compare the number of EGPRS TBF in the cell with the saved maximum value.

For the measurement of number of EGPRS TBFs in a cell, refer to Measurement Point of C901000045.

Unit
Times

6.27 C901000052 Number of GPRS DL signaling TBF normal release

Definition
Number of GPRS DL signaling TBF normal release

Description
When the DL GPRS signaling TBF sends the last data block, it sets FBI to 1 and sets the RRBP bit to let MS send the DL response message. After BSC receives the last response message (FAI=1), it is considered that the DL transmission is executed normally. In the
6-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

DTM mode, if the user plane receives the data sent message from the control plane, to keep measurement consistency, it is considered that the DL TBF is released normally.

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

Figure 6-39 LLC Frame Transmits GTTP Message In DTM Mode

Unit
Times

6-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

6.28 C901000058 Number of EGPRS DL signaling TBF 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.
Figure 6-40 Normal Release Of DL TBF

6-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 6-41 LLC Frame Transmits GTTP Message In DTM Mode

Unit
Times

6.29 C901000066 Number of EGPRS2-A TBF restarting in downlink delay state

Description
This counter counts the number of times that a downlink EGPRS2-A TBF is restarted in a cell.

Measurement Point
This counter is incremented if the TBF is operated in EGPRS2-A mode when the downlink RLC instance, after receiving an EV_BSSGP_DATA_IND message in Delay state, calls the Ranu_DRlc_DelayBssgpHaveBlock function.

Unit
Times

6.30 C901000067 Number of downlink EGPRS2-A TBF establishment requests before T3192 expires
Description
During the running of T3193 of DL EGPRS2-A 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.

6-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Measurement Point
After the DL EGPRS2-A 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. The measurement point is A, as shown in Figure 6-42.
Figure 6-42 Updated of Number of EGPRS2-A DL TBF Establishment Requests Before T3192 Expiration

Unit
Times

6.31 C901000068 Number of establishing downlink EGPRS2-A TBF without requesting downlink channel resource
Description
When establishing EGPRS2-A 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 EGPRS2-A DL TBF establishment using existing DL TBF resource.

Measurement Point
During the UL EGPRS2-A TBF transmission, when BSC receives the DL LLC frame, it uses the existing resource to establish DL EGPRS2-A TBF. The measurement point is A, as shown in Figure 6-43.

6-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 6-43 Updated of EGPRS2-A DL TBF Establishment Using Existing DL TBF Resource

Unit
Times

6.32 C901000069 Number of requests for establishing downlink EGPRS2-A TBF on PACCH
Description
Under UL transmission status, it is necessary to establish DL TBF transmission when user plane receives DL LLC Frame from SGSN. If user plane has not saved DL TBF resource, then user plane requests control plane for resource. This counter counts the number of times of requesting control plane for resource to establish EGPRS2-A DL TBF on PACCH.

Measurement Point
The measurement point is A1, as shown in Figure 6-44.
Figure 6-44 Updated of Number of EGPRS2-A DL TBF Establishment Requests on PACCH

6-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Unit
Times

6.33 C901000070 Number of Failures in Establishing Downlink EGPRS2-A TBF on PACCH Due to Timeout in Resource Assignment
Description
In the UL transmission state, when SGSN DL LLC frame arrives, the DL TBF transmission should be established. If there is no reserved DL resource, the user plane will ask the control plane to allocate resource. This counter counts the number of non-responses from the control plane in this case.

Measurement Point
When the BSC sends DL 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-45.
Figure 6-45 Number Of Request Failures For Establishing EGPRS2-A On PACCH (No Response From Control Plane)

Unit
Times

6-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

6.34 C901000071 Number of Failures in Establishing Downlink EGPRS2-A TBF on PACCH Due to Other Causes
Description
This counter counts the number of TBF establishment failures caused by other reasons than non-responses from the control plane when PACCH of EGPRS2-A 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.35 C901000072 Number of Successfully Establishing Downlink EGPRS2-A TBF on PACCH

Description
This counter counts the number of successful DL EGPRS2-A TBF establishments on the UL/DL EGPRS2-A TBF PACCH.

Measurement Point
When the DL EGPRS2-A TBF is established on the UL/DL EGPRS2-A TBF PACCH and a message indicating assignment success is sent, this counter increments. The measurement points are A as shown in Figure 6-46 and Figure 6-47, and A2 as shown in Figure 6-48.

6-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Figure 6-46 Updated of Number of Requests for Establishing EGPRS2-A Downlink Data TBF Before T3192 Overtime

Figure 6-47 Updated of Number of Established EGPRS2-A Downlink Data TBF Using Existing Resources

Figure 6-48 Updated of Number of Requests for Establishing EGPRS2-A Downlink Data TBF on Uplink EGPRS2-A TBF PACCH

Unit
Times

6-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

6.36 C901000073 Number of Requests for Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH
Description
When MS is in packet idle status, after BSC receives DL LLC frame from SGSN, BSC initiates the process of establishing DL TBF which is assigned on CCCH or PCCCH. BSC user plane first sends the request for DL establishment to BSC control plane.

Measurement Point
Under MSs packet idle status, when BSC sends the request for DL resource to BSC control plane after receiving LLC frame from SGSN, the counter increments. The measurement point is as A1, as shown in Figure 6-49.
Figure 6-49 Updated of Number of EGPRS2-A DL TBF Establishment Requests on CCCH/PCCCH

Unit
Times

6-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

6.37 C901000074 Number of Failures in Establishing Downlink EGPRS2-A TBF on CCCH/PCCCH Due to Timeout in Resource Assignment
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 EGPRS2-A 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-50 and Figure 6-51.
Figure 6-50 Failures For Establishing DL EGPRS2-A TBF On CCCH/PCCCH (1)

Figure 6-51 Failures For Establishing DL EGPRS2-A TBF On CCCH/PCCCH (2)

Unit
Times

6-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

6.38 C901000075 Number of Failures in Establishing Downlink EGPRS2-A TBF on CCCH/PCCCH Due to Other Causes
Description
When MS is in the idle state, after BSC receives DL LLC frames from SGSN, BSC should originate DL TBF establishment assigned on CCCH/PCCCH. The user plane sends a DL establishment request to the control plane. If it receives the instance release message from the control plane or fails to create DL RLC instance after receiving the resource assignment message, it indicates that the DL TBF establishment fails.

Measurement Point
During the DL EGPRS2-A TBF establishment on CCCH/PCCCH, after the user plane sends the request to the control plane, if it receives the instance release message from the control plane or fails to create DL RLC instance after receiving the resource assignment message, this counter increments.

Unit
Times

6.39 C901000076 Number of Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH

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

Measurement Point
During the DL EGPRS2-A 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-52 .

6-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Figure 6-52 Normal Establishment Of DL EGPRS2-A TBF On CCCH/PCCCH

In the DTM mode, this counter increments when the user plane receives the DTM sent message (the LLC frame has been sent). The measurement point is A, as shown in Figure 6-53.
Figure 6-53 LLC Frame Transmits GTTP Message In DTM Mode

In the DTM mode, this counter increments when the user plane receives the DTM assignment message. The measurement point is A, as shown in Figure 6-54.

6-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 6-54 DTM Assignment In DTM Mode

Unit
Times

6.40 C901000077 Number of Failures in Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH Due to Polling Failure
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. 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-55. While waiting for MSs responding with the AB form of packet control ack message, if the release request is received from control plane, this counter increments. The measurement point is A, as shown in Figure 6-56.

6-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Figure 6-55 Updated Of Number Of Times For Establishing EGPRS2-A DL TBF With Polling Failed On CCCH/PCCCH

Figure 6-56 Updated Of Number Of Times For Establishing EGPRS2-A DL TBF With Polling Failed On CCCH/PCCCH

Unit
Times

6-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

6.41 C901000078 Number of Successfully Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH Due to Polling Success
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. In the DTM mode, if the user plane receives the DTM assignment message from the control plane, the operation is considered to be successful. Besides, in the DTM mode, if the user plane receives the DTM sent message from the control plane, to keep the consistency of DL TBF establishment attempts and successful establishments, the DL TBF establishment is also considered to be successful.

l l

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-57, A as shown in Figure 6-58, and A as shown in Figure 6-59.

6-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Figure 6-57 Normal Establishment Of DL EGPRS2-A TBF On CCCH/PCCCH

Figure 6-58 LLC Frame Transmits GTTP Message In DTM Mode

Figure 6-59 DTM Assignment In DTM Mode

Unit
Times
6-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

6.42 C901000079 Number of Successfully Establishing EGPRS2-A Downlink TBF on CCCH/PCCCH

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. 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. In the DTM mode, if the user plane receives the DTM assignment message from the control plane, the operation is considered to be successful. Besides, in the DTM mode, if the user plane receives the DTM sent message from the control plane, to keep the consistency of DL TBF establishment attempts and successful establishments, the EGPRS2-A DL TBF establishment is also considered to be successful.

l l

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. If the assignment is on CCCH, after the user plane receives the packet control ack message from MS and successfully sends the DL assignment message, the counter increments. In the DTM mode, when the user plane receives the DTM sent/assignment message from the control plane, the counter increments. The measurement points are A3 (PCCCH) and A4 (CCCH), as shown in Figure 6-60, A as shown in Figure 6-61, and A as shown in Figure 6-62.

l l

6-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Figure 6-60 Normal Establishment Of DL EGPRS2-A TBF On CCCH/PCCCH

Figure 6-61 LLC Frame Transmits GTTP Message In DTM Mode

Figure 6-62 DTM Assignment In DTM Mode

Unit
Times
6-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

6.43 C901000080 Times of Normal Releasing EGPRS2-A Downlink TBF

Description
When the DL EGPRS2-A 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 EGPRS2-A 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-63and Figure 6-64.
Figure 6-63 Normal Release Of DL TBF

Figure 6-64 LLC Frame Transmits GTTP Message In DTM Mode

6-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Unit
Times

6.44 C901000081 Number of Releases of EGPRS2-A Downlink TBF Due to N3105 Overflow
Description
During the DL TBF transmission, the DL block RRBP bit is set to ask MS to respond with a Packet Downlink Ack/Nack message. If the specified block of BSC fails to receive response from MS, then the N3105 counter increments; otherwise, it has a clear. If no response comes from the MS, then the RRBP bit is set again to ask MS to respond with a Packet Downlink Ack/Nack message; if the N3105 counter reaches its maximum value, it is considered that the radio transmission fails and the DL TBF is released abnormally.

Measurement Point
When the N3105 counter value exceeds N3105Max, this counter increments. measurement point is A1, as shown in Figure 6-65. The

Figure 6-65 Updated of Number of EGPRS2-A DL TBF Release due to N3105 Overflow

Unit
Times

6-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

6.45 C901000082 Number of Abnormal Releases of EGPRS2-A Downlink TBF

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 6-66.
Figure 6-66 Updated of Number of EGPRS2-A DL TBF Release due to Other Reasons

Unit
Times

6.46 C901000083 Number of Abnormal Releases of EGPRS2-A Downlink TBF 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.

6-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

Measurement Point
When the user plane receives the release request from the control plane, this counter increments. The measurement point is A, as shown in Figure 6-67.
Figure 6-67 Updated of Number of EGPRS2-A DL TBF Forcing Release by Control Plane

Unit
Times

6.47 C901000084 Number of Abnormal Releases of EGPRS2-A Downlink TBF 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
When the DL block assigning timer expires, this counter increments. The measurement point is A, as shown in Figure 6-68.

6-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 6-68 Updated of Number of EGPRS2-A DL TBF Release due to Instance Suspension

Unit
Times

6.48 C901000085 Number of Abnormal Releases of EGPRS2-A Downlink TBF Due to Internal Error
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

6-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

6.49 C901000086 Number of EGPRS2-A Downlink Signaling TBF Establishments

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 EGPRS2-A 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 C901000066 and C901000079.

Unit
Times

6.50 C901000087 Number of EGPRS2-A Downlink Data TBF Establishments

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 EGPRS2-A DL TBF for user data (no-UL-signaling) transmission.

Measurement Point
When the DL TBF is created successfully and the TBF type is EGPRS2-A data TBF, the counter increments. The measurement point is similar to those of C901000066 and C901000079.

Unit
Times

6-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

6.51 C901000088 Total Time of EGPRS2-A Downlink TBF Connection

Description
This counter counts the cumulated overall DL connecting time of EGPRS2-A TBF within a cell.

Measurement Point
l l When EGPRS2-A TBF RLC transmission starts, this counter accumulates. When EGPRS2-A 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. When EGPRS2-A TBF RLC transmission is released abnormally (including N3105 overflow and T3191 timeout), this counter accumulates. When the measurement value is acquired regularly, this counter accumulates. The measurement value is a cumulated overall measurement value. After each accumulation, the measurement time point is updated with the current time. For Updated (1), after each accumulation, the number of DL EGPRS2-A TBFs that are being transmitted increments by 1; for Updated (2) and Updated (3), after each accumulation, the number of DL EGPRS2-A TBFs that are being transmitted decreases by 1. The measurement method is shown in Figure 6-69.
Figure 6-69 Measurement Of Cumulated Overall DL Connecting Time

l l l

Unit
ms

6-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

6.52 C901000089 Maximum Number of EGPRS2-A Downlink TBF Established Simultaneously

Description
The counter counts the maximum number of DL EGPRS2-A TBFs that are established simultaneously within a cell.

Measurement Point
l l When EGPRS2-A TBF RLC transmission starts, the EGPRS2-A TBFs in the cell increments by 1 and compares with the saved maximum value. When the measurement value is acquired regularly, compare the number of EGPRS2-A TBF in the cell with the saved maximum value.

For the measurement of number of EGPRS2-A TBFs in a cell, refer to Updated of C901000088.

Unit
None

6.53 C901000090 Average Number of EGPRS2-A Downlink TBF Established Simultaneously

Description
This counter counts the average number of DL EGPRS2-A TBF establishments in a cell.

Measurement Point
The counter acquires the measurement value regularly. The number of EGPRS2-A TBFs existing in the cell is considered the average number.

Unit
None

6.54 C901000091 Number of Normal Releases of EGPRS2-A Signaling Downlink TBF

Description
When the DL EGPRS2-A 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.
6-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 EGPRS2-A 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-70and Figure 6-71.
Figure 6-70 Normal Release Of DL TBF

Figure 6-71 LLC Frame Transmits GTTP Message In DTM Mode

Unit
Times

6-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

6.55 C901000092 Number of Releases of EGPRS2-A Signaling Downlink TBF Due to N3105 Overflow
Description
During the EGPRS2-A 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 EGPRS2-A signaling DL TBF is released abnormally.

Measurement Point
When the N3105 counter value exceeds N3105Max, this counter increments. measurement point is A1, as shown in Figure 6-72. The

Figure 6-72 Updated of Number of EGPRS2-A DL Signaling TBF Release due to N3105 Overflow

Unit
Times

6-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

6.56 C901000093 Number of Abnormal Releases of EGPRS2-A Signaling Downlink TBF

Description
When BSC is transmitting the last RLC block of EGPRS2-A 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 EGPRS2-A signaling DL TBF is released abnormally.

Measurement Point
The measurement point is A1, as shown in Figure 6-73.
Figure 6-73 Updated of Number of EGPRS2-A DL TBF Release due to Other Reasons

Unit
Times

6-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

6.57 C901000094 Number of Abnormal Releases of EGPRS2-A Signaling Downlink TBF by Control Plane
Description
When the user plane is transmitting the EGPRS2-A signaling DL TBF, if a release request comes from the control plane, then the EGPRS2-A signaling DL TBF will stop and be released abnormally.

Measurement Point
When the user plane receives the release request from the control plane, this counter increments. The measurement point is A, as shown in Figure 6-74.
Figure 6-74 Updated of Number of EGPRS2-A DL TBF Forcing Release by Control Plane

Unit
Times

6.58 C901000095 Number of Abnormal Releases of EGPRS2-A Signaling Downlink TBF Due to Instance Suspension
Description
When the user plane is transmitting the EGPRS2-A 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 EGPRS2-A signaling DL TBF is released abnormally.

6-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When the DL block assigning timer expires, this counter increments. The measurement point is A, as shown in Figure 6-75.
Figure 6-75 Updated of Number of EGPRS2-A DL TBF Release due to Instance Suspension

Unit
Times

6.59 C901000096 Number of Abnormal Releases of EGPRS2-A Signaling Downlink TBF Due to Internal Error
Description
When the user plane is transmitting the EGPRS2-A 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 EGPRS2-A signaling DL TBF will be released abnormally.

Measurement Point
During the transmission of EGPRS2-A 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
6-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 6 Downlink Data TBF Measurement

6.60 C901000097 Number of EGPRS2-A Data Downlink TBF Establishment on PACCH

Description
When UL TBF exists, and there is DL data to be sent through SGSN, a request will be sent to establish DL TBF on PACCH. This counter increments upon the request and the TBF type is EGPRS2-A. This counter counts the number of requests to establish EGPRS2-A DL TBF on PACCH.

Measurement Point
When a request is sent to establish DL TBF on PACCH and the TBF type is EGPRS2-A, this counter increments.

Unit
Times

6.61 C901000098 Peak Downlink GPRS Throughput

Description
This counter indicates the peak value of downlink GPRS throughput in a cell.

Measurement Point
The Ranu_Spmu_PSThroughput function is called during periodic event processing of a cell to count the peak traffic through the PS Gb interface and calculate the peak downlink GPRS throughput. This counter is updated with the greater one between the current counter value and the result of downlink GPRS PS traffic during a specific time granularity divided by PS traffic duration.

Unit
bps

6.62 C901000099 Peak Downlink EGPRS Throughput

Description
This counter indicates the peak value of downlink EGPRS throughput in a cell.

Measurement Point
The Ranu_Spmu_PSThroughput function is called during periodic event processing of a cell to count the peak traffic through the PS Gb interface and calculate the peak downlink
6-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

EGPRS throughput. This counter is updated with the greater one between the current counter value and the result of downlink EGPRS PS traffic during a specific time granularity divided by PS traffic duration.

Unit
bps

6-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7

Uplink Data TBF Measurement

Table of Contents
Overview ....................................................................................................................7-3 C901010001 Number of GPRS UL TBF resumption in extend uplink state .................7-3 C901010002 Number of GPRS UL TBF resource reassign in delay uplink state.........7-4 C901010006 Number of GPRS establishment failure on PACCH due to time out .......7-5 C901010007 Number of GPRS establishment failure on PACCH due to other reasons ......................................................................................................................7-6 C901010010 Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to competition solving failed.................................................................................7-7 C901010011 Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to not receive resource request ...........................................................................7-8 C901010012 Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons ..................................................................................................7-9 C901010013 Number of GPRS UL TBF establishment success on CCCH/PCCCH..7-10 C901010014 Number of GPRS UL TBF normal release ...........................................7-12 C901010022 Number of EGPRS UL TBF resumption in extend uplink state.............7-13 C901010023 Number of EGPRS UL TBF resource reassign in delay uplink state ....7-14 C901010027 Number of EGPRS establishment failure on PACCH due to time out ...7-14 C901010028 Number of EGPRS establishment failure on PACCH due to other reasons ....................................................................................................................7-15 C901010031 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to competition solving failed...............................................................................7-16 C901010032 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to not receive resource request .........................................................................7-17 C901010033 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons ................................................................................................7-18 C901010034 Number of EGPRS UL TBF establishment success on CCCH/PCCCH .........................................................................................................7-19 C901010035 Number of EGPRS UL TBF normal release.........................................7-21 C901010043 Time of GPRS UL TBF connection ......................................................7-22 C901010044 Time of EGPRS UL TBF connection....................................................7-23 C901010045 Time of UL signaling TBF connection ..................................................7-23 C901010046 Max number of GPRS UL TBF simultaneous establishment ................7-24 C901010048 Max number of EGPRS UL TBF simultaneous establishment..............7-24 C901010050 Number of GPRS UL signaling TBF normal release ............................7-25
7-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901010056 Number of EGPRS UL signaling TBF normal release ..........................7-26 C901010064 Number of EGPRS2-A uplink TBF reestablishment in extended uplink state .........................................................................................................................7-27 C901010065 Number of EGPRS2-A uplink TBF resource assignments in uplink delay state................................................................................................................7-27 C901010066 Number of EGPRS2-A uplink TBF reestablishments in released state .7-27 C901010067 Number of EGPRS2-A uplink TBF establishments with available uplink resource.........................................................................................................7-28 C901010068 Number of requests for establishing EGPRS2-A uplink TBF on PACCH.....................................................................................................................7-29 C901010069 Number of failures in establishing EGPRS2-A uplink TBF on PACCH due to timeout ..........................................................................................................7-30 C901010070 Number of failures in establishing EGPRS2-A uplink TBF on PACCH due to other causes..................................................................................................7-31 C901010071 Number of Successfully Establishing EGPRS2-A Uplink TBF on PACCH.....................................................................................................................7-31 C901010072 Number of Failures in Establishing EGPRS2-A Uplink TBF on CCCH/PCCCH Due to Other Causes .......................................................................7-32 C901010073 Number of Successfully Establishing EGPRS2-A Uplink TBF on CCCH/PCCCH .........................................................................................................7-33 C901010074 Times of Normal Releasing EGPRS2-A Uplink TBF ............................7-33 C901010075 Number of Abnormal Releases of EGPRS2-A Uplink TBF Due to N3101 Overflow .......................................................................................................7-34 C901010076 Number of Abnormal Releases of EGPRS2-A Uplink TBF Due to N3103 Overflow .......................................................................................................7-35 C901010077 Number of Forced Releases of EGPRS2-A Uplink TBF .......................7-35 C901010078 Number of Abnormal Releases of EGPRS2-A Uplink TBF Due to Instance Suspension ................................................................................................7-35 C901010079 Number of Abnormal Releases of EGPRS2-A Uplink TBF Due to Internal Error ............................................................................................................7-36 C901010080 Number of EGPRS2-A Uplink Signaling TBF Establishments ..............7-36 C901010081 Number of EGPRS2-A Uplink Data TBF Establishments .....................7-37 C901010082 Total Time of EGPRS2-A Uplink TBF Connection ................................7-37 C901010083 Maximum Number of EGPRS2-A Uplink TBF Established Simultaneously.........................................................................................................7-37 C901010084 Average Number of EGPRS2-A Uplink TBF Established Simultaneously.........................................................................................................7-38 C901010085 Number of Normal Releases of EGPRS2-A Signaling Uplink TBF .......7-38 C901010086 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due to N3101 Overflow ............................................................................................7-39 C901010087 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due to N3103 Overflow ............................................................................................7-40 C901010088 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due to Forced Release.............................................................................................7-40

7-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

C901010089 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due to Instance Suspension.....................................................................................7-41 C901010090 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due to Internal Error.................................................................................................7-41 C901010091 Number of Successfully Establishing EGPRS2-A Uplink Data TBF on PACCH.....................................................................................................................7-42 C901010092 Peak Uplink GPRS Throughput ...........................................................7-42 C901010093 Peak Uplink EGPRS Throughput.........................................................7-42

7.1 Overview
Uplink (UL) data TBF measurement mainly involves processes of establishing TBF, keeping TBF and releasing TBF on cells. The measurement takes cell as the statistics unit.

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. The measurement point is A, as shown in Figure 7-1.

7-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 7-1 Measurement Point On Receiving New Data Block In GPRS Extended UL State

Unit
Times

7.3 C901010002 Number of GPRS UL TBF resource 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-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

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
The measurement point is A, as shown in Figure 7-3.

7-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

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
The measurement point is A, as shown in Figure 7-4.
Figure 7-4 Measurement Point On Number Of Establishment Failures Of GPRS UL TBF Caused By Competition Solution Failure

7-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

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

7.7 C901010011 Number of GPRS UL TBF 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
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 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
This counter is used to record number of failed GPRS UL TBF establishment on CCCH/PCCCH caused by not receiving resource request.

Measurement Point
The measurement point is A, as shown in Figure 7-5.

7-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

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

7.8 C901010012 Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons
Definition
Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons

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 competion can be completed. Meanwhile, network sends Packet UL Ack with TLLI as well. 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 wireless radio access capability.

7-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to record number of failed GPRS UL TBF establishment on CCCH/PCCCH caused by any other reasons.

Measurement Point
This counter increments when GPRS UL TBF establishment fails because of other reasons, except that one-step access competition solution fails or two-step access does not receive resource request.

Unit
Times

7.9 C901010013 Number of GPRS UL TBF establishment success on CCCH/PCCCH

Definition
Number of GPRS UL TBF establishment success on CCCH/PCCCH

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 competion can be completed. Meanwhile, network sends Packet UL Ack with TLLI as well. 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 wireless radio access capability.

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-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

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-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The measurement point is A, as shown in Figure 7-8.
Figure 7-8 Measurement Point On Number Of Normal GPRS UL TBF Release

Unit
Times

7-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

7.11 C901010022 Number of EGPRS UL TBF resumption in extend uplink state

Definition
Number of EGPRS UL TBF resumption in extend uplink state

Description
MS notifies BSS whether extended GPRS UL TBF is supported by reporting its radio access capability. If extended GPRS UL TBF is supported, BSS will not stop allocating resources within a certain period of time after receiving RLC block (CV = 0) from MS. During this period, if MS has new data to transmit, the data is transmitted directly by the block allocated, and after the network receives a new block, TBF will be resumed to be in normal transmission state. If MS has no new data to transmit, the message Packet UL Dummy Control Block is transmitted by the block allocated.

Usage
This counter is used to record number of resumptions for EGPRS UL TBF in extended UL state.

Measurement Point
The measurement point is A, as shown in Figure 7-9.
Figure 7-9 Measurement Point On Number Of Resumptions For EGPRS UL TBF In Extended UL State

Unit
Times

7-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

7.12 C901010023 Number of EGPRS UL TBF resource 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
The measurement point is A, as shown in Figure 7-10.
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-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

Description
During TBF transmission of an MS with downlink TBF, if MS has UL data to transmit but no corresponding UL TBF is available, UL TBF establishment request will be sent out by Packet Downlink Ack. UPPB will request CMP for resources if having no UL resource records, and meanwhile, UPPB starts the timer. The request fails if the timer gets no response till timeout.

Usage
This counter is used to record number of request failures caused by timeout for establishing EGPRS on PACCH.

Measurement Point
The measurement point is A, as shown in Figure 7-11.
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
During TBF transmission of an MS with downlink TBF, if MS has UL data to transmit but no corresponding UL TBF is available, UL TBF establishment request will be sent out by Packet Downlink Ack. Generally, network will assign resources to MS; However, UL TBF establishment request fails if there is any condition abnormal.

7-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

7.15 C901010031 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to competition solving failed
Definition
Number of EGPRS 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 competion 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 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
The measurement point is A, as shown in Figure 7-12.

7-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

Figure 7-12 Measurement Point On Number Of Establishment Failures Of EGPRS UL TBF Caused By Competition Solving Failed

Unit
Times

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

7.16 C901010032 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to not receive resource request
Definition
Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to not receive resource request

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 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
This counter is used to record number of failed EGPRS UL TBF establishment on CCCH/PCCCH caused by not receiving resource request.
7-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

7.17 C901010033 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons
Definition
Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons

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. 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
7-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

Resource Request. After that, network assigns new resource for MS by Packet UL Assignment according to MSs wireless radio access capability.

Usage
This counter is used to record number of failed EGPRS UL TBF establishment on CCCH/PCCCH caused by any other reasons.

Measurement Point
This counter increments when EGPRS UL TBF establishment fails because of other reasons except that one-step access competition solution fails or two-step access does not receive resource request.

Unit
Times

7.18 C901010034 Number of EGPRS UL TBF establishment success on CCCH/PCCCH

Definition
Number of EGPRS UL TBF establishment success on CCCH/PCCCH

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 competion can be completed. Meanwhile, network sends Packet UL Ack with TLLI as well. 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 wireless radio access capability.

Usage
This counter is used to record number of successful EGPRS UL TBF establishment on CCCH/PCCCH.

7-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

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
If having received all data blocks, BSS sends Packet UL Ack with FAI to MS and sets RRBP when receiving RLC block (CV = 0). MS then reports Packet Control Ack on corresponding UL block, notifying BSS to release TBF normally.

Usage
This counter is used to record number of normal EGPRS UL TBF releases.

Measurement Point
The measurement point is A, as shown in Figure 7-16.
7-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

7.21 C901010044 Time of EGPRS UL TBF connection

Definition
Time of EGPRS 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 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
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 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-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

7.23 C901010046 Max number of GPRS UL TBF simultaneous establishment

Definition
Max number of GPRS UL TBF simultaneous establishment

Description
During the measurement period, there might be several TBFs existing simultaneously. This counter is used to find out the maximum number of UL GPRS TBF established simultaneously within the measurement period.

Usage
This counter is used to find out the maximum number of UL GPRS TBF established simultaneously within the measurement period.

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

Unit
Times

7.24 C901010048 Max number of EGPRS UL TBF simultaneous establishment

Definition
Max number of EGPRS UL TBF simultaneous establishment

Description
During the measurement period, there might be several TBFs existing simultaneously. This counter is used to find out the maximum number of UL EGPRS TBF established simultaneously within the measurement period

Usage
This counter is used to find out the maximum number of UL EGPRS TBF established simultaneously within the measurement period.

7-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

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

Unit
Times

7.25 C901010050 Number of GPRS UL signaling TBF normal release

Definition
Number of GPRS UL signaling 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 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-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

7.26 C901010056 Number of EGPRS UL signaling TBF normal release

Definition
Number of EGPRS UL signaling TBF normal release

Description
If having received all data blocks, BSS sends Packet UL Ack with FAI to MS and sets RRBP when receiving RLC block (CV = 0). MS then reports Packet Control Ack on corresponding UL block, notifying BSS to release TBF normally.

Usage
This counter is used to record number of normal EGPRS signaling UL TBF releases.

Measurement Point
The measurement point is A, as shown in Figure 7-18.
Figure 7-18 Measurement Point On Number Of Normal GPRS Signaling UL TBF Release

Unit
Times

7-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

7.27 C901010064 Number of EGPRS2-A uplink TBF reestablishment in extended uplink state
Description
This counter counts uplink TBF reestablishments in the case of uplink EGPRS2-A TBF in extended state in a cell.

Measurement Point
This counter is incremented if the current uplink TBF mode is EGPRS2-A when the uplink RLC instance in extended state receives an RLC data block.

Unit
Times

7.28 C901010065 Number of EGPRS2-A uplink TBF resource assignments in uplink delay state
Description
This counter counts uplink TBF assignments in the case of uplink EGRPS2-A TBF in delay state in a cell.

Measurement Point
This counter is incremented if the current uplink TBF mode is EGPRS2-A when the uplink RLC instance in Delay state receives an uplink TBF assignment message.

Unit
Times

7.29 C901010066 Number of EGPRS2-A uplink TBF reestablishments in released state

Description
This counter counts uplink TBF reestablishments in the case of uplink EGPRS2-A TBF in released state in a cell.

Measurement Point
The MAC instance in PreUlRelease state, upon receiving a control acknowledgement message, attempts to reestablish an uplink TBF if the TBF reestablishment in released
7-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

state is supported and no control acknowledgement is sent. This counter is incremented if the current TBF mode is EGPRS2-A in the case of TBF reestabishment. The MAC instance in PreUlRelease state, upon receiving a TBF request message, attempts to reestablish an uplink TBF if the TBF reestablishment in released state is supported. This counter is incremented if the current TBF mode is EGPRS2-A in the case of TBF reestabishment.

Unit
Times

7.30 C901010067 Number of EGPRS2-A uplink TBF establishments with available uplink resource
Description
This counter counts uplink TBF establishments with available uplink resources in the case of uplink EGPRS2-A TBF in a cell.

Measurement Point
This counter is incremented if the current uplink TBF mode is EGPRS2-A when the MAC instance in DlRelease state, upon receiving a downlink acknowledgement message from a mobile station, successfully reestablishes an uplink RLC instance in Dual Transfer Mode (DTM) in the case of invalid uplink instance number, which indicates that no downlink has been established before and necessary resources need to be requested from the CMP. This counter is incremented if the current uplink TBF mode is EGPRS2-A when the MAC instance in DlRelease state, upon receiving a downlink acknowledgement from a mobile station, successfully assigns uplink resources in the case of valid uplink instance number. This counter is incremented if the current uplink TBF mode is EGPRS2-A when the MAC instance in DlRelease state, upon receiving an EPDLAck2 message, successfully reestablishes an uplink RLC instance in Dual Transfer Mode (DTM) in the case of invalid uplink instance number, which indicates that no downlink has been established before and necessary resources need to be requested from the CMP. This counter is incremented if the current uplink TBF mode is EGPRS2-A when the MAC instance in DlRelease state, upon receiving an EPDLAck2 message, successfully assigns uplink resources in the case of valid uplink instance number. This counter is incremented if the current uplink TBF mode is EGPRS2-A when the MAC instance in DlRelPreUlRelease state, upon receiving an EGPRS downlink acknowledgement, requsts for uplink TBF establishment and the uplink assignment succeeds in the case of valid uplink RLC instance number. This counter is incremented if the current uplink TBF mode is EGPRS2-A when the MAC instance in DlRelPreUlRelease state, upon receiving an EPDLAck2 message, requsts for
7-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

uplink TBF establishment and the uplink assignment succeeds in the case of valid uplink RLC instance number. This counter is incremented if the current uplink TBF mode is EGPRS2-A when the MAC instance in DLTransfer state, upon receiving a downlink acknowledgement message, requsts for uplink TBF establishment without resource adjustment and uplink assignment in the case of valid uplink RLC instance number. This counter is incremented if the current uplink TBF mode is EGPRS2-A when the MAC instance in DlRelease state, upon receiving an EPDLAck2 message, successfully reestablishes an uplink RLC instance in DTM in the case of valid uplink instance number. This counter is incremented if the current uplink TBF mode is EGPRS2-A when the MAC instance in DLTransfer state, upon receiving an EPDLAck2 message, requsts for uplink TBF establishment without resource adjustment and uplink assignment in the case of valid uplink RLC instance number. This counter is incremented if the current TBF mode is EGPRS2-A when the MAC instance in DTPreUlRelease state, upon receiving a downlink acknowledgement message, requests for uplink TBF establishment. This counter is incremented if the current TBF mode is EGPRS2-A when the MAC instance in DTPreUlRelease state, upon receiving an EPDLAck2 message, requests for uplink TBF establishment. This counter is incremented if the current TBF mode is EGPRS2-A when the MAC instance in DTUlRelease state, upon receiving a downlink acknowledgement message, requests for uplink TBF establishment. This counter is incremented if the current TBF mode is EGPRS2-A when the MAC instance in DTUlRelease state, upon receiving an EPDLAck2 message, requests for uplink TBF establishment.

Unit
Times

7.31 C901010068 Number of requests for establishing EGPRS2-A uplink TBF on PACCH
Description
When MS has DL TBF and the TBF is in transmission status, if MS has UL data to send but no UL TBF is available, MS sends Packet DL Ack message together with UL TBF establishment request. This counter counts the number of resource re-applications after receiving this request. This counter records the number of requests for establishing UL EGPRS2-A TBF on PACCH.
7-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The measurement point is A, as shown in Figure 7-19.
Figure 7-19 Updated of Number of Requests for Establishing UL EGPRS2-A TBF on PACCH

Unit
Times

7.32 C901010069 Number of failures in establishing EGPRS2-A uplink TBF on PACCH due to timeout
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. UPU will request CMP for resources if it does not have UL resource records, and meanwhile, UPU starts the timer. The request fails if the timer gets no response till timeout. This counter is used to record number of request failures caused by timeout for establishing EGPRS2-A on PACCH.

Measurement Point
The measurement point is A, as shown in Figure 7-20.
Figure 7-20 Updated On Number Of Request Failures Caused By Timeout For Establishing EGPRS2-A On PACCH

7-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

Unit
Times

7.33 C901010070 Number of failures in establishing EGPRS2-A uplink TBF on PACCH due to other causes
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. This counter is used to record number of request failures caused by other reasons for establishing EGPRS2-A on PACCH.

Measurement Point
This counter increments when the request for establishing EGPRS2-A on PACCH fails because of other reasons except timer is timeout.

Unit
Times

7.34 C901010071 Number of Successfully Establishing EGPRS2-A Uplink TBF on PACCH

Description
When MS has a DL TBF and the TBF is being transmitted, if the UL data need to be transmitted but there is no corresponding UL TBF, then the Packet Downlink Ack message will carry the UL TBF establishment request. Usually BSS will assign the resource to MS, and then an UL TBF is established successfully. The counter counts the number of successful EGPRS2-A UL TBF establishments on PACCH

Measurement Point
The measurement point is A, as shown in Figure 7-21.

7-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 7-21 Updated of Number of EGPRS2-A UL Data TBF Establishment Success on PACCH

Unit
Times

7.35 C901010072 Number of Failures in Establishing EGPRS2-A Uplink TBF on CCCH/PCCCH Due to Other Causes
Description
This counter counts uplink EGPRS2-A TBF establishment failures on the CCCH/PCCCH due to other causes in a cell.

Measurement Point
This counter is incremented if the TBF is operated in EGPRS2-A data TBF mode when the MAC instance fails to locate a cell during downlink preestablishment before expiry of the timer used to wait for resource assignment by the control plane. This counter is incremented if the TBF is operated in EGPRS2-A data TBF mode when the MAC instance in WaitULAssign state, upon receiving a resource assignment message from the RANPS, fails to locate a cell. This counter is incremented if the TBF is operated in EGPRS2-A data TBF mode when the MAC instance in WaitULAssign state, upon receiving a resource assignment message from the RANPS, fails to create an uplink RLC instance. This counter is incremented if the TBF is operated in EGPRS2-A data TBF mode when the MAC instance in WaitULAssign state, upon receiving a resource assignment message from the RANPS, fails to send an uplink assignment message. This counter is incremented if the TBF is operated in EGPRS2- A data TBF mode when the MAC instance in WaitULAssign state releases the RANPS instance upon expiry of the timer used to wait for resource request. This counter is incremented if the TBF is operated in EGPRS2-A data TBF mode when N3101 exceeds its limit in the case of uplink data block loss.

Unit
Times

7-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

7.36 C901010073 Number of Successfully Establishing EGPRS2-A Uplink TBF on CCCH/PCCCH

Description
This counter counts successful uplink EGPRS2-A TBF establishments on the CCCH/PCCCH in a cell.

Measurement Point
This counter is incremented if the TBF is operated in EGPRS2-A data TBF mode when the MAC instance in WaitULAssign state, upon receiving a resource assignment message from the RANPS, sccessfully establishes an uplink TBF.

Unit
Times

7.37 C901010074 Times of Normal Releasing EGPRS2-A Uplink TBF

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. This counter is used to record number of normal EGPRS2-A UL TBF releases.

Measurement Point
The measurement point is A, as shown in Figure 7-22.

7-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 7-22 Updated On Number Of Normal EGPRS2-A UL TBF Release

Unit
Times

7.38 C901010075 Number of Abnormal Releases of EGPRS2-A Uplink TBF 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. The counter counts the number of abnormal releases of EGPRS2-A UL TBF due to N3101 overflow.

Measurement Point
The measurement point is when N3101 overflow.

Unit
Times

7-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

7.39 C901010076 Number of Abnormal Releases of EGPRS2-A Uplink TBF Due 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. The counter counts the number of abnormal releases of EGPRS2-A UL TBF due to N3103 overflow.

Measurement Point
The measurement point is when N3103 overflow.

Unit
Times

7.40 C901010077 Number of Forced Releases of EGPRS2-A Uplink TBF

Description
When an UL TBF establishment is held, the control plane may forcibly release this UL TBF. The counter counts the number of forced releases of EGPRS2-A UL TBF due to release request from the control plane.

Measurement Point
The measurement point is arrival of the release request.

Unit
Times

7.41 C901010078 Number of Abnormal Releases of EGPRS2-A Uplink TBF Due 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.
7-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

The counter counts the number of abnormal releases of EGPRS2-A UL TBF due to suspension of the instance.

Measurement Point
The measurement point is that UPU detects suspension of the instance.

Unit
Times

7.42 C901010079 Number of Abnormal Releases of EGPRS2-A Uplink TBF Due to Internal Error
Description
TBF is abnormally released due to UPU internal error. The counter counts the number of abnormal releases of EGPRS2-A UL TBF due to internal error.

Measurement Point
The measurement point is abnormal UPU suspension.

Unit
Times

7.43 C901010080 Number of EGPRS2-A Uplink Signaling TBF Establishments

Description
For different purpose, MS may establish two types of TBF: signaling TBF and data TBF. The counter counts the number of EGPRS2-A UL signaling TBF link establishments.

Measurement Point
The measurement point is that UPU access type is signaling TBF.

Unit
Times

7-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

7.44 C901010081 Number of EGPRS2-A Uplink Data TBF Establishments

Description
For different purpose, MS may establish two types of TBF: signaling TBF and data TBF. The counter counts the number of EGPRS2-A UL data TBF link establishments.

Measurement Point
The measurement point is that UPU access type is data TBF.

Unit
Times

7.45 C901010082 Total Time of EGPRS2-A Uplink TBF Connection

Description
MS establishes two types of TBF for different purposes. They are signaling TBF and data TBF. This counter is used to find out cumulated overall UL connecting time of EGPRS2-A TBF.

Measurement Point
The counter starts to accumulate when UPU receives the UL EGPRS2-A TBF establishment indication, and stops when UL EGPRS2-A TBF on UPU ends normally.

Unit
ms

7.46 C901010083 Maximum Number of EGPRS2-A Uplink TBF Established Simultaneously

Description
During the measurement period, there might be several TBFs existing simultaneously. This counter is used to find out the maximum number of UL EGPRS2-A TBF established simultaneously within the measurement period This counter is used to find out the maximum number of UL EGPRS2-A TBF established simultaneously within the measurement period.
7-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter increments when UPU receives UL EGPRS2-A TBF establishment indication, and decrements when the UL EGPRS2-A TBF releases.

Unit
Times

7.47 C901010084 Average Number of EGPRS2-A Uplink TBF Established Simultaneously

Description
There may be more than one TBF in the system during the sampling period. Average number of uplink EGPRS2-A TBF establishing simultaneously = Number of UL EGPRS2-A TBFs established simultaneously in the sampling period / Times of sampling This counter counts the average number of UL EGPRS2-A TBF establishing simultaneously.

Measurement Point
When UPU receives the message informing UL EGPRS2-A TBF establishment, the number of TBFs is refreshed and the times of sampling accumulates.

Unit
Times

7.48 C901010085 Number of Normal Releases of EGPRS2-A Signaling Uplink TBF

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. This counter is used to record number of normal EGPRS2-A signaling UL TBF releases.

Measurement Point
The measurement point is A, as shown in.

7-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

Figure 7-23 Updated On Number Of Normal EGPRS2-A Signaling UL TBF Release

Unit
Times

7.49 C901010086 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF 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. The counter counts the number of abnormal releases of EGPRS2-A signaling UL TBF due to N3101 overflow.

Measurement Point
The measurement point is N3101 overflow.

Unit
Times

7-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

7.50 C901010087 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due 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. The counter counts the number of abnormal releases of EGPRS2-A signaling UL TBF due to N3103 overflow.

Measurement Point
The measurement point is N3103 overflow.

Unit
Times

7.51 C901010088 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due to Forced Release
Description
When an UL TBF establishment is held, the control plane may forcibly release this UL TBF. The counter counts the number of forced releases of EGPRS2-A signaling UL TBF due to release request from the control plane.

Measurement Point
The measurement point is arrival of the release request.

Unit
Times

7-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

7.52 C901010089 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due 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. The counter counts the number of abnormal releases of EGPRS2-A signaling UL TBF due to suspension of the instance.

Measurement Point
The measurement point is that UPU detects suspension of the instance.

Unit
Times

7.53 C901010090 Number of Abnormal Releases of EGPRS2-A Uplink Signaling TBF Due to Internal Error
Description
TBF is abnormally released due to UPU internal error. The counter counts the number of abnormal releases of EGPRS2-A signaling UL TBF due to internal error.

Measurement Point
The measurement point is abnormal UPU suspension.

Unit
Times

7-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

7.54 C901010091 Number of Successfully Establishing EGPRS2-A Uplink Data TBF on PACCH
Explanation
When an existing MS's downlink TBF is in transmission state and there is no uplink TBF, if the MS needs to transmit uplink data, it will request the establishment of uplink TBF via the PACKET DOWNLINK ACK message. In ordinary cases, the network will allocate resources to the MS, and the uplink TBF is successfully established. The counter counts the successful times of EGPRS2-A TBF establishment on PACCH. According to the purpose, the MS may establish two kinds of TBF: signaling TBF and data TBF. The counter counts the successful times of EGPRS2-A data uplink TBF establishment on PACCH.

Measurement Point
None

Unit
Times

7.55 C901010092 Peak Uplink GPRS Throughput

Description
This counter indicates the peak value of uplink GPRS throughput in a cell.

Measurement Point
The Ranu_Spmu_PSThroughput function is called during periodic event processing of a cell to count the peak traffic through the PS Gb interface and calculate the peak uplink GPRS throughput. This counter is updated with the greater one between the current counter value and the result of uplink GPRS PS traffic during a specific time granularity divided by PS traffic duration.

Unit
bps

7.56 C901010093 Peak Uplink EGPRS Throughput

Description
This counter indicates the peak value of uplink EGPRS throughput in a cell.
7-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 7 Uplink Data TBF Measurement

Measurement Point
The Ranu_Spmu_PSThroughput function is called during periodic event processing of a cell to count the peak traffic through the PS Gb interface and calculate the peak uplink EGPRS throughput. This counter is updated with the greater one between the current counter value and the result of uplink EGPRS PS traffic during a specific time granularity divided by PS traffic duration.

Unit
bps

7-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

7-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8

Data Flow Measurement

Table of Contents
Overview ....................................................................................................................8-2 C901020001 Number of Bytes of IP packet sent to BIPB............................................8-2 C901020002 Number of packets sent to BIPB............................................................8-3 C901020003 Number of Bytes of IP packet received from BIPB.................................8-4 C901020004 Number of packets received from BIPB .................................................8-5 C901020005 Number of Bytes of IP packet sent to GIPB ...........................................8-6 C901020006 Number of packets sent to GIPB ...........................................................8-6 C901020007 Number of Bytes of IP packet received from GIPB ................................8-7 C901020008 Number of packets received from GIPB.................................................8-8 C901020009 Number of Bytes carried by EGPRS DL LLC frame ...............................8-9 C901020014 Number of Bytes carried by DL signaling LLC frame............................8-10 C901020019 Number of Bytes carried by UL LLC frame ..........................................8-11 C901020020 Number of UL LLC frames...................................................................8-12 C901020021 Number of Bytes of GPRS DL TBF LLC frame ....................................8-12 C901020022 Number of Bytes of EGPRS DL TBF LLC frame ..................................8-13 C901020023 Number of Bytes of DL signaling TBF LLC frame ................................8-14 C901020024 Number of Bytes of UL GPRS TBF LLC frame ....................................8-15 C901020025 Number of Bytes of EGPRS UL TBF LLC frame ..................................8-16 C901020026 Number of Bytes of UL signaling TBF LLC frame ................................8-17 C901020031 Number of GPRS UL data TBF completion..........................................8-17 C901020034 Number of GPRS DL data TBF completion..........................................8-18 C901020041 Number of EGPRS UL data TBF completion .......................................8-19 C901020044 Number of EGPRS DL data TBF completion .......................................8-20 C901020050 Number of Bytes carried by GPRS DL LLC frame ...............................8-21 C901020055 Number of DL EGPRS2-A TBF LLC Bytes ..........................................8-22 C901020056 Number of DL EGPRS2-A TBF LLC ....................................................8-22 C901020057 Number of DL EGPRS2-A TBF LLC Discarded for Buffer Overload.....8-23 C901020058 Number of DL EGPRS2-A TBF LLC Discarded for Life Time Expiration .................................................................................................................8-23 C901020059 Number of DL EGPRS2-A TBF LLC Discarded for Other Reasons......8-24 C901020060 Number of UL EGPRS2-A TBF LLC Bytes ..........................................8-24 C901020061 Number of UL EGPRS2-A TBF LLC ....................................................8-25 C901020062 Number of DL LLC Sent Correctly Bytes in EGPRS2-A Ack Mode.......8-25 C901020063 Times of UL EGPRS2-A TBF Normal Release ....................................8-26 C901020064 Alive Time of UL EGPRS2-A TBF........................................................8-26 C901020065 Number of LLC Bytes Sent by DL EGPRS2-A TBF .............................8-27 C901020066 Times of DL EGPRS2-A TBF Normal Release ....................................8-27
8-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901020067 Alive Time of DL EGPRS2-A TBF........................................................8-28 C901020068 Number of LLC Bytes Received by UL EGPRS2-A TBF ......................8-28 C901020069 Number of NACK Data Blocks Received by UL EGPRS2-A TBF .........8-29 C901020070 Number of LLC Bytes Received by DL EGPRS2-A TBF ......................8-29 C901020071 Number of NACK Data Blocks Received by DL EGPRS2-A TBF .........8-30 C901020072 Number of DL EGPRS2-A TBF Send Current Blocks ..........................8-31 C901020077 Number of Discarded UL Signaling LLC Frames .................................8-31 C901020078 Number of Discarded UL GPRS Data LLC Frames .............................8-32 C901020079 Number of Discarded UL EGPRS Data LLC Frames ...........................8-32 C901020080 Number of Discarded UL EGPRS 2A/B Data LLC Frames...................8-33 C901020081 Number of DL Signaling LLC Frames Sent Successfully in Signaling TBF Mode ................................................................................................................8-33 C901020082 Number of DL Data LLC Frames Sent Successfully in GPRS Data TBF Mode ................................................................................................................8-34 C901020083 Number of DL Data LLC Frames Sent Successfully in EGPRS Data TBF Mode ................................................................................................................8-34 C901020084 Number of DL Data LLC Frames Sent Successfully in EGPRS2A/B Data TBF Mode........................................................................................................8-35 C901020085 Maximum number of LLC Store In Bssgp ............................................8-35 C901020086 Sum of Max LLC Store In Bssgp .........................................................8-36 C901020087 Sample of BSSGP Inst ........................................................................8-36 C901020088 Sum of number due to LLC Store reach MAX......................................8-37 C901020089 Maximum number of LLC Trans In Bssgp............................................8-37 C901020090 Sum of Max LLC Trans In Bssgp .........................................................8-38 C901020091 Sample of BSSGP Trans .....................................................................8-38 C901020092 Sum of number due to LLC Trans reach MAX .....................................8-39

8.1 Overview
Data flow measurement focuses on the flow related information, including the LLC frames, RLC blocks and TBF connecting time. The measurement takes cell as the statistics unit.

8.2 C901020001 Number of Bytes 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
8-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

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

Usage
The counter counts the size of IP packets sent to BIPB. The measurement unit is Byte.

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

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.

Usage
The counter counts the number of IP packets sent to BIPB.

Measurement Point
The measurement point is A, as shown in Figure 8-2.
8-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 8-2 Measurement Point Of Number Of IP Packets Sent To BIPB

Unit
Times

8.4 C901020003 Number of Bytes of IP packet received from BIPB

Definition
Number of Kbytes of IP packet received from 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 received within iBSC.

Usage
The counter counts the size of IP packets received from BIPB. The measurement unit is Byte.

Measurement Point
The measurement point is A, as shown in Figure 8-3.

8-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

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

Usage
The counter counts the number of packets received from BIPB.

Measurement Point
The measurement point is A, as shown in Figure 8-4.
Figure 8-4 Measurement Point Of Number Of IP Packets Received From BIPB

8-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

8.6 C901020005 Number of Bytes 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
The measurement point is A, as shown in Figure 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
8-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

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.

Usage
The counter counts the number of IP packets sent to GIPB.

Measurement Point
The measurement point is A, as shown in Figure 8-6.
Figure 8-6 Measurement Point Of Number Of IP Packets Sent To GIPB

Unit
Times

8.8 C901020007 Number of Bytes of IP packet received from GIPB

Definition
Number of Kbytes of IP packet received from 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.

8-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
The counter counts the size of IP packets received from GIPB. The measurement unit is Byte.

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

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.

Usage
The counter counts the number of IP packets received from GIPB.

Measurement Point
The measurement point is A, as shown in Figure 8-8.

8-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

Figure 8-8 Measurement Point Of Number Of IP Packets Received From GIPB

Unit
Times

8.10 C901020009 Number of Bytes carried by EGPRS DL LLC frame

Definition
Number of Kbytes carried by EGPRS DL LLC frame

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 command, 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 Kbytes carried by DL EGPRS LLC frame.

Measurement Point
The measurement point is A, as shown in Figure 8-9.

8-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 8-9 Measurement Point Of Number Of Kbytes Carried By DL EGPRS LLC Frame

Unit
Byte

8.11 C901020014 Number of Bytes carried by DL signaling LLC frame

Definition
Number of Kbytes carried by DL signaling LLC frame

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 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. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.

Usage
The counter counts the number of Kbytes carried by DL signaling LLC frame.

Measurement Point
The measurement point is A, as shown in Figure 8-10.

8-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

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

Unit
Byte

8.12 C901020019 Number of Bytes 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. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.

Usage
The counter counts the number of Kbytes carried by UL LLC frame.

Measurement Point
The measurement point is A, as shown in Figure 8-11.
Figure 8-11 Measurement Point Of Number Of Kbytes Carried By UL LLC Frame

8-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The measurement point is A, as shown in Figure 8-12.
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-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

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 Packet DL Ack. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.

Usage
The counter counts the number of bytes of DL GPRS TBF LLC frame.

Measurement Point
The measurement point is A, as shown in Figure 8-13.
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
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
8-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

information about MS reception by setting RRBP to let MS report EGPRS Packet DL Ack. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.

Usage
The counter counts the number of bytes of DL EGPRS TBF LLC frame.

Measurement Point
The measurement point is A, as shown in Figure 8-14.
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
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 EGPRS Packet DL Ack. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.
8-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

Usage
The counter counts the number of bytes of DL signaling TBF LLC frame.

Measurement Point
The measurement point is A, as shown in Figure 8-15.
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
After receiving the RLC blocks reported by MS, UPPB composes them into the LLC frame and sends it to SGSN. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.

Usage
The counter counts the number of bytes of UL GPRS TBF LLC frame.

8-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The measurement point is A, as shown in Figure 8-16.
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
After receiving the RLC blocks reported by MS, UPPB composes them into the LLC frame and sends it to SGSN. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.

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

Measurement Point
The measurement point is A, as shown in Figure 8-17.
Figure 8-17 Measurement Point Of Number Of Bytes Of UL EGPRS TBF LLC Frame

8-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

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
After receiving the RLC blocks reported by MS, UPPB composes them into the LLC frame and sends it to SGSN. This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.

Usage
The counter counts the number of bytes of UL signaling TBF LLC frame.

Measurement Point
The measurement point is A, as shown in Figure 8-18.
Figure 8-18 Measurement Point Of Number Of Bytes Of UL Signaling TBF LLC Frame

Unit
Byte

8.20 C901020031 Number of GPRS UL data TBF completion

Definition
Number of GPRS UL data TBF completion
8-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The measurement point is A, as shown in Figure 8-19.
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-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

Usage
The counter counts the number of completion of GPRS DL data TBF.

Measurement Point
The measurement point is A, as shown in Figure 8-20.
Figure 8-20 Measurement Point Of Total Number Of Completion Of GPRS DL Data TBF

Unit
Times

8.22 C901020041 Number of EGPRS UL data TBF completion

Definition
Number of EGPRS UL data TBF completion

Description
After the network side receives the data blocks (CV=0) from MS and if all the other blocks have been received successfully, then it will send the Packet UL Ack message (FAI=1) to MS. By this time, the UL data transmission is completed.

Usage
The counter counts the number of completion of EGPRS UL data TBF.

Measurement Point
The measurement point is A, as shown in Figure 8-21.
8-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The measurement point is A, as shown inFigure 8-22.

8-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

Figure 8-22 Measurement Point Of Total Number Of Completion Of EGPRS DL Data TBF

Unit
Times

8.24 C901020050 Number of Bytes carried by GPRS DL LLC frame

Definition
Number of Kbytes carried by GPRS DL LLC frame

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 command, 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 Kbytes carried by DL GPRS LLC frame.

Measurement Point
The measurement point is A, as shown in Figure 8-23.

8-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 8-23 Measurement Point Of Number Of Kbytes Carried By DL GPRS LLC Frame

Unit
Byte

8.25 C901020055 Number of DL EGPRS2-A TBF LLC Bytes

Description
This counter counts downlink LLC frame bytes in EGPRS2-A TBF mode in a cell.

Usage
This counter indicates the number of downlink LLC frame bytes in EGPRS2-A TBF mode in a cell.

Measurement Point
The BSC calls the Ranu_Bssgp_StoreLLC function to store an LLC frame upon receiving downlink data. If the stored RRL frame is in EGPRS2-A TBF mode, this counter is incremented. In addition, the number of LLC frame bytes in the BSSGP instance is added to this counter if the downlink RLC instance detects that the obtained TBF data is in EGPR2-A TBF mode.

Unit
None

8.26 C901020056 Number of DL EGPRS2-A TBF LLC

Description
This counter counts downlink LLC frames in EGPRS2-A TBF mode in a cell.

8-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

Usage
This counter indicates the number of downlink LLC frames in EGPRS2-A TBF mode in a cell.

Measurement Point
The BSC calls the Ranu_Bssgp_StoreLLC function to store an LLC frame upon receiving downlink data. If the stored RRL frame is in EGPRS2-A TBF mode, this counter is incremented. In addition, the number of LLC frames in the BSSGP instance is added to this counter if the downlink RLC instance detects that the obtained TBF data is in EGPR2-A TBF mode.

Unit
None

8.27 C901020057 Number of DL EGPRS2-A TBF LLC Discarded for Buffer Overload
Description
This counter counts downlink LLC frames in EGPRS2-A TBF mode that are discarded due to buffer overload in a cell.

Usage
This counter indicates the number of downlink LLC frames in EGPRS2-A TBF mode that are discarded due to buffer overload in a cell.

Measurement Point
The BSC calls the Ranu_Bssgp_StoreLLC function to store an LLC frame upon receiving downlink data. If the LLC frame to be stored is in EGPRS2-A TBF mode and it is discarded due to buffer overload or buffer obtain failure, this counter is incremented.

Unit
None

8.28 C901020058 Number of DL EGPRS2-A TBF LLC Discarded for Life Time Expiration
Description
This counter counts the number of times that a downlink LLC frame in EGPRS2-A TBF mode is discarded due to lifetime expiration in a cell.
8-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter indicates the number of times that a downlink LLC frame in EGPRS2-A TBF mode is discarded due to lifetime expiration in a cell. This counter is not used in this version.

Measurement Point
None

Unit
Times

8.29 C901020059 Number of DL EGPRS2-A TBF LLC Discarded for Other Reasons
Description
This counter counts downlink LLC frames in EGPRS2-A TBF mode that are discarded due to the other reasons in a cell.

Usage
This counter indicates the number of downlink LLC frames in EGPRS2-A TBF mode that are discarded due to the other reasons in a cell.

Measurement Point
This counter is incremented each time the BSC, upon receiving downlink data, calls the Ranu_Bssgp_StoreLLC function to store an LLC frame in EGPRS2-A TBF mode but the BSSGP fails to insert the LLC frame, or each time the BSC calls the Ranu_Bssgp_OneLLCDelDiscardStatic function to delete an LLC frame in EGPRS2-A TBF mode during LLC buffer release.

Unit
None

8.30 C901020060 Number of UL EGPRS2-A TBF LLC Bytes

Description
This counter counts uplink LLC frame bytes in EGPRS2-A TBF mode in a cell.

8-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

Usage
This counter indicates the number of uplink LLC frame bytes in EGPRS2-A TBF mode in a cell.

Measurement Point
The BSC passes an LLC frame comprising received RLC data blocks into the Ranu_URlc_SendULUnitData function. The number of bytes in this LLC frame is added to this counter if the LLC frame is in EGPRS2-A TBF mode and the cell instance, MAC instance, and the next hop are obtained.

Unit
None

8.31 C901020061 Number of UL EGPRS2-A TBF LLC

Description
This counter counts all bytes in uplink LLC frames in EGPRS2-A TBF mode in a cell.

Usage
This counter indicates the total number of uplink LLC frame bytes in EGPRS2-A TBF mode in a cell.

Measurement Point
When the uplink RLC instance in extended uplink state or transfer state receives RLC data blocks, this counter is added with the number of LLC frame bytes in the RLC instance in the case of EGPRS2-A TBF mode. When the BSC passes an LLC frame comprising received RLC data blocks into the Ranu_URlc_SendULUnitData function, the number of bytes in this LLC frame is added to this counter if the LLC frame is in EGPRS2-A TBF mode and the cell instance, MAC instance, and the next hop are obtained.

Unit
None

8.32 C901020062 Number of DL LLC Sent Correctly Bytes in EGPRS2-A Ack Mode
Description
This counter counts LLC frame bytes that are successfully sent in a cell in the case of EGPRS2-A TBF mode.
8-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter indicates the number of successfully sent LLC frame bytes in a cell in the case of EGPRS2-A TBF mode. This counter is not used in this version.

Measurement Point
None

Unit
None

8.33 C901020063 Times of UL EGPRS2-A TBF Normal Release

Description
This counter counts the number of times that an uplink TBF is normally released in a cell in the case of EGPRS2-A TBF mode.

Usage
This counter indicates the number of times that an uplink TBF is normally released in a cell in the case of EGPRS2-A TBF mode.

Measurement Point
The BSC calls the Ranu_URlc_SendUmPUlAck function to send an uplink packet acknowledgement through the Um interface. If an acknowledgement message with FAI=1 is sent in the case of EGPRS2-A TBF mode, this counter is incremented.

Unit
Times

8.34 C901020064 Alive Time of UL EGPRS2-A TBF

Description
This counter counts the duration of uplink TBF in a cell in the case of EGPRS2-A TBF mode.

Usage
This counter indicates the duration of uplink TBF in a cell in the case of EGPRS2-A TBF mode.
8-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

Measurement Point
When the uplink RLC instance in extended uplink state receives RLC data blocks, this counter is added with 20 in the case of EGPRS2-A TBF mode. When the uplink RLC instance in transfer state receives RLC data blocks, this counter is added with the duration of the uplink TBF in the case of EGPRS2-A TBF mode. When the BSC passes an LLC frame comprising received RLC data blocks into the Ranu_URlc_SendULUnitData function, this counter is added with the duration of the uplink TBF in the case of EGPRS2-A TBF mode if the cell instance, MAC instance, and the next hop are obtained.

Unit
ms

8.35 C901020065 Number of LLC Bytes Sent by DL EGPRS2-A TBF

Description
This counter counts all bytes in downlink LLC frames in EGPRS2-A TBF mode in a cell.

Usage
This counter indicates the total number of downlink LLC frame bytes in EGPRS2-A TBF mode in a cell.

Measurement Point
The downlink RLC instance in delay state calls the Ranu_DRlc_WaitReleaseType2EgprsPacketDownlinkAck function upon receiving a downlink packet acknowledgement. If FAI=1, the downlink RLC instance retrieves all RLC data blocks and this counter is added with the number of LLC frame bytes in the downlink RLC instance.

Unit
None

8.36 C901020066 Times of DL EGPRS2-A TBF Normal Release

Description
This counter counts the number of times that a downlink TBF is normally released in a cell in the case of EGPRS2-A TBF mode.

8-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter indicates the number of times that a downlink TBF is normally released in a cell in the case of EGPRS2-A TBF mode.

Measurement Point
When the downlink RLC instance in delay state receives a packet control acknowledgement, this counter is incremented if a PCtrlAck message is received in unacknowledgement mode after the FBI is sent. The downlink RLC instance in delay state calls the Ranu_DRlc_WaitReleaseType2EgprsPacketDownlinkAck function upon receiving a downlink packet acknowledgement. If FAI=1, the downlink RLC instance retrieves all RLC data blocks and this counter is incremented.

Unit
Times

8.37 C901020067 Alive Time of DL EGPRS2-A TBF

Description
This counter counts the duration of downlink TBF in a cell in the case of EGPRS2-A TBF mode.

Usage
This counter indicates the duration of downlink TBF in a cell in the case of EGPRS2-A TBF mode.

Measurement Point
The downlink RLC instance in delay state calls the Ranu_DRlc_WaitReleaseType2EgprsPacketDownlinkAck function upon receiving a downlink packet acknowledgement. If FAI=1, the downlink RLC instance retrieves all RLC data blocks and this counter is added with the duration of the downlink TBF.

Unit
ms

8.38 C901020068 Number of LLC Bytes Received by UL EGPRS2-A TBF

Description
This counter counts valid data blocks received on uplink TBFs in a cell in the case of EGPRS2-A TBF mode.
8-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

Usage
This counter indicates the number of valid data blocks received on uplink TBFs in a cell in the case of EGPRS2-A TBF mode.

Measurement Point
This counter is added with the number of valid data blocks in the uplink RLC instance each time the uplink delay and extension timer expires in the case of EGPRS2-A TBF mode.

Unit
None

8.39 C901020069 Number of NACK Data Blocks Received by UL EGPRS2-A TBF

Description
This counter counts NACK data blocks received on uplink TBFs in a cell in the case of EGPRS2-A TBF mode.

Usage
This counter indicates the number of NACK data blocks received on uplink TBFs in a cell in the case of EGPRS2-A TBF mode.

Measurement Point
This counter is added with the number of NACK data blocks in the uplink RLC instance each time the uplink delay and extension timer expires in the case of EGPRS2-A TBF mode.

Unit
None

8.40 C901020070 Number of LLC Bytes Received by DL EGPRS2-A TBF

Description
This counter counts valid data blocks sent on downlink TBFs in a cell in the case of EGPRS2-A TBF mode.

8-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter indicates the number of valid data blocks sent on downlink TBFs in a cell in the case of EGPRS2-A TBF mode.

Measurement Point
When the downlink RLC instance in delay state receives a packet control acknowledgement, this counter is added with the number of valid data blocks in the downlink RLC instance in the case of EGPRS2-A TBF mode if a PCtrlAck message is received in unacknowledgement mode after the FBI is sent. The downlink RLC instance in delay state calls the Ranu_DRlc_WaitReleaseType2EgprsPacketDownlinkAck function upon receiving a downlink packet acknowledgement. If FAI=1, the downlink RLC instance retrieves all RLC data blocks and this counter is added with the number of valid data blocks in the downlink RLC instance in the case of EGPRS2-A TBF mode.

Unit
None

8.41 C901020071 Number of NACK Data Blocks Received by DL EGPRS2-A TBF

Description
This counter counts NACK data blocks sent on downlink TBFs in a cell in the case of EGPRS2-A TBF mode.

Usage
This counter indicates the number of NACK data blocks sent on downlink TBFs in a cell in the case of EGPRS2-A TBF mode.

Measurement Point
When the downlink RLC instance in delay state receives a packet control acknowledgement, this counter is added with the number of NACK data blocks in the downlink RLC instance in the case of EGPRS2-A TBF mode if a PCtrlAck message is received in unacknowledgement mode after the FBI is sent. The downlink RLC instance in delay state calls the Ranu_DRlc_WaitReleaseType2EgprsPacketDownlinkAck function upon receiving a downlink packet acknowledgement. If FAI=1, the downlink RLC instance retrieves all RLC data blocks and this counter is added with the number of NACK data blocks in the downlink RLC instance in the case of EGPRS2-A TBF mode.

Unit
None
8-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

8.42 C901020072 Number of DL EGPRS2-A TBF Send Current Blocks

Description
This counter counts data blocks that are successfully sent on downlink TBFs in a cell in the case of EGPRS2-A TBF mode.

Usage
This counter indicates the number of successfully sent data blocks on downlink TBFs in a cell in the case of EGPRS2-A TBF mode.

Measurement Point
When the downlink RLC in delay state receives an EGPRS Downlink Ack2 message, this counter is added with the number of RLC data blocks in the case of EGPRS2-A TBF mode if the acknowledgement is not FAI=1. When the downlink RLC in transfer state receives an EGPRS Downlink Ack2 message, this counter is added with the number of RLC data blocks in the case of EGPRS2-A TBF mode if the acknowledgement is not FAI=1. When the downlink RLC in WaitRelease state receives an EGPRS Downlink Ack2 message, this counter is added with the number of RLC data blocks in the case of EGPRS2-A TBF mode if the acknowledgement is not FAI=1.

Unit
None

8.43 C901020077 Number of Discarded UL Signaling LLC Frames

Description
This counter counts all uplink signaling LLC PDUs that are discarded in a cell.

Usage
This counter indicates the number of uplink signaling LLC PDUs discarded in a cell.

Measurement Point
The BSC passes an LLC frame comprising received RLC data blocks into the Ranu_URlc_SendULUnitData function. When the LLC frame is discarded due to an abnormal event, this counter is incremented if the LLC frame is a signaling LLC frame.

8-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
None

8.44 C901020078 Number of Discarded UL GPRS Data LLC Frames

Description
This counter counts uplink LLC PDUs in GPRS TBF mode that are discarded in a cell.

Usage
This counter indicates the number of uplink LLC PDUs in GPRS TBF mode discarded in a cell.

Measurement Point
The BSC passes an LLC frame comprising received RLC data blocks into the Ranu_URlc_SendULUnitData function. When the LLC frame is discarded due to an abnormal event, this counter is incremented if the LLC frame is in GPRS TBF mode.

Unit
None

8.45 C901020079 Number of Discarded UL EGPRS Data LLC Frames

Description
This counter counts uplink LLC PDUs in EGPRS TBF mode that are discarded in a cell.

Usage
This counter indicates the number of uplink LLC PDUs in EGPRS TBF mode discarded in a cell.

Measurement Point
The BSC passes an LLC frame comprising received RLC data blocks into the Ranu_URlc_SendULUnitData function. When the LLC frame is discarded due to an abnormal event, this counter is incremented if the LLC frame is in EGPRS TBF mode.

Unit
None
8-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

8.46 C901020080 Number of Discarded UL EGPRS 2A/B Data LLC Frames

Description
This counter counts uplink LLC PDUs in EGPRS 2A/B TBF mode that are discarded in a cell.

Usage
This counter indicates the number of uplink LLC PDUs in EGPRS 2A/B TBF mode discarded in a cell.

Measurement Point
The BSC passes an LLC frame comprising received RLC data blocks into the Ranu_URlc_SendULUnitData function. When the LLC frame is discarded due to an abnormal event, this counter is incremented if the LLC frame is in EGPRS 2A/B TBF mode.

Unit
None

8.47 C901020081 Number of DL Signaling LLC Frames Sent Successfully in Signaling TBF Mode
Description
This counter counts downlink signaling LLC PDUs that are successfully sent by the BSC in a cell during a measurement period.

Usage
This counter indicates the number of downlink signaling LLC PDUs successfully sent by the BSC in a cell during a measurement period.

Measurement Point
After successfully sending a downlink LLC PDU, the BSC receives an acknowledgement response and then deletes this LLC PDU from the PDU buffer queue. This counter is incremented if the successfully sent LLC PDU is in signaling TBF mode.

Unit
None
8-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

8.48 C901020082 Number of DL Data LLC Frames Sent Successfully in GPRS Data TBF Mode
Description
This counter counts downlink LLC PDUs in GPRS TBF mode that are successfully sent by the BSC in a cell during a measurement period.

Usage
This counter indicates the number of downlink LLC PDUs in GPRS TBF mode that are successfully sent by the BSC in a cell during a measurement period.

Measurement Point
After successfully sending a downlink LLC PDU, the BSC receives an acknowledgement response and then deletes this LLC PDU from the PDU buffer queue. This counter is incremented if the successfully sent LLC PDU is in GPRS TBF mode.

Unit
None

8.49 C901020083 Number of DL Data LLC Frames Sent Successfully in EGPRS Data TBF Mode
Description
This counter counts downlink LLC PDUs in EGPRS TBF mode that are successfully sent by the BSC in a cell during a measurement period.

Usage
This counter indicates the number of downlink LLC PDUs in EGPRS TBF mode that are successfully sent by the BSC in a cell during a measurement period.

Measurement Point
After successfully sending a downlink LLC PDU, the BSC receives an acknowledgement response and then deletes this LLC PDU from the PDU buffer queue. This counter is incremented if the successfully sent LLC PDU is in EGPRS TBF mode.

Unit
None

8-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

8.50 C901020084 Number of DL Data LLC Frames Sent Successfully in EGPRS2A/B Data TBF Mode
Description
This counter counts downlink LLC PDUs in EGPRS 2A/B TBF mode that are successfully sent by the BSC in a cell during a measurement period.

Usage
This counter indicates the number of downlink LLC PDUs in EGPRS 2A/B TBF mode that are successfully sent by the BSC in a cell during a measurement period.

Measurement Point
After successfully sending a downlink LLC PDU, the BSC receives an acknowledgement response and then deletes this LLC PDU from the PDU buffer queue. This counter is incremented if the successfully sent LLC PDU is in EGPRS 2A/B TBF mode.

Unit
None

8.51 C901020085 Maximum number of LLC Store In Bssgp

Description
This counter records the peak value of the number of LLC frames stored in the BSSGP buffer in a cell.

Usage
This counter indicates the peak value of the number of LLC frames stored in the BSSGP buffer in a cell.

Measurement Point
The BSSGP updates the number of LLC frames in the buffer upon storing an LLC frame received from the Gb interface or a DUMMY LLC inserted by the DRLC in the buffer queue. This counter records the peak value of the number of LLCs stored in the BSSGP buffer each time the BSC performs a ++ operation on the number of LLCs.

Unit
None
8-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

8.52 C901020086 Sum of Max LLC Store In Bssgp

Description
This counter calculates the average value of the number of LLC frames stored in the BSSGP buffer in a cell.

Usage
This counter indicates the average value of the number of LLC frames stored in the BSSGP buffer in a cell.

Measurement Point
This counter calculates the average value of the number of LLCs in the BSSGP buffer each time the periodically measured value is obtained.

Unit
None

8.53 C901020087 Sample of BSSGP Inst

Description
This counter records the peak value of the number of LLC frames transferred by the BSSGP in a cell.

Usage
This counter indicates the peak value of the number of LLC frames transferred by the BSSGP in a cell.

Measurement Point
The BSC considers that all LLC frames are successfully transferred when it detects the source cell and the target cell in the same DSP. After receiving a FLUSHLL message from the core network, the UMC sends an LLC transfer request to the source BSSGP instance if the UMC detects two PS instances of the mobile station and that the mobile station has got access to two different serving cells successively. If PCCO pre-transfer is supported, the BSSGP instance in BUFFER mode sends an LLC transfer request to the source BSSGP instance upon receiving a downlink establishment request from the MAC. If the PCCO pre-transfer is not supported, the BSSGP instance in BUFFER mode considers all stored LLC frames as transferred LLC frames after receiving a downlink establishment request from the MAC. This counter records the peak value of the number of LLC frames transferred by the BSSGP each time the number increases.
8-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

Unit
None

8.54 C901020088 Sum of number due to LLC Store reach MAX

Description
This counter records the peak value of the number of LLC frames transferred in the same DSP by the BSSGP in a cell.

Usage
This counter indicates the peak value of the number of LLC frames transferred in the same DSP by the BSSGP in a cell.

Measurement Point
The number of LLC frames transferred by the BSSGP are counted depending on whether the source cell and the target cell are involved in the same DSP. This counter records the peak value of the number of LLC frames transferred by the BSSGP in the DSP where the source cell and target cell are involved each time the number of transferred LLC frames increases.

Unit
None

8.55 C901020089 Maximum number of LLC Trans In Bssgp

Description
This counter records the peak value of the number of LLC frames transferred by the BSSGP between DSPs in a cell.

Usage
This counter indicates the peak value of the number of LLC frames transferred by the BSSGP between DSPs in a cell.

Measurement Point
The number of LLC frames transferred by the BSSGP are counted depending on whether the source cell and the target cell are involved in the same DSP. If the source cell and target cell are involved in two DSPs, this counter records the peak value of the number of LLC
8-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

frames transferred by the BSSGP between two DSPs each time the number of transferred LLC frames increases.

Unit
None

8.56 C901020090 Sum of Max LLC Trans In Bssgp

Description
This counter calculates the average value of the total number of LLC frames transferred by the BSSGP in a cell.

Usage
This counter indicates the average value of the total number of LLC frames transferred by the BSSGP in a cell.

Measurement Point
This counter calculates the average value of the total number of LLCs transferred by the BSSGP each time the periodically measured value is obtained.

Unit
None

8.57 C901020091 Sample of BSSGP Trans

Description
This counter calculates the average value of the number of LLC frames transferred in the same DSP by the BSSGP in a cell.

Usage
This counter indicates the average value of the number of LLC frames transferred in the same DSP by the BSSGP in a cell.

Measurement Point
This counter calculates the average value of the number of LLCs transferred by the BSSGP in the same DSP each time the periodically measured value is obtained.

Unit
None
8-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 8 Data Flow Measurement

8.58 C901020092 Sum of number due to LLC Trans reach MAX

Description
This counter calculates the average value of the number of LLC frames transferred by the BSSGP between DSPs in a cell.

Usage
This counter indicates the average value of the number of LLC frames transferred by the BSSGP between DSPs in a cell.

Measurement Point
This counter calculates the average value of the number of LLCs transferred by the BSSGP between DSPs each time the periodically measured value is obtained.

Unit
None

8-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

8-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9

Uplink-Downlink RLC Statistic Measurement

Table of Contents
Overview ....................................................................................................................9-3 C901030041 Bytes of GPRS DL RLC lost on PDTCH ................................................9-5 C901030042 Bytes of EGPRS DL RLC lost on PDTCH ..............................................9-6 C901030083 Number of UL RLC Blocks lost ..............................................................9-6 C901030084 Bytes of GPRS UL RLC lost on PDTCH ................................................9-7 C901030085 Bytes of EGPRS UL RLC lost on PDTCH ..............................................9-7 C901030086 Number of standstill of GPRS UL TBF receiving window .......................9-8 C901030087 Number of standstill of EGPRS UL TBF receiving window.....................9-9 C901030088 Number of standstill of GPRS DL TBF sending window .......................9-10 C901030089 Number of standstill of EGPRS DL TBF sending window.....................9-10 C901030090 Number of increment of DL coding mode ............................................9-11 C901030091 Number of decrement of DL coding mode ...........................................9-13 C901030092 Number of increment of UL coding mode ............................................9-14 C901030093 Number of decrement of UL coding mode ...........................................9-15 C901030094 Number of conversion from GMSK to 8PSK ........................................9-16 C901030095 Number of conversion from 8PSK to GMSK ........................................9-18 C901030098 Number of Useful Downlink RLC Pending Blocks in DAS5 Coding on PDTCH ....................................................................................................................9-19 C901030099 Number of Useful Downlink RLC Pending Blocks in DAS6 Coding on PDTCH ....................................................................................................................9-20 C901030100 Number of Useful Downlink RLC Pending Blocks in DAS7 Coding on PDTCH ....................................................................................................................9-20 C901030101 Number of Useful Downlink RLC Pending Blocks in DAS8 Coding on PDTCH ....................................................................................................................9-21 C901030102 Number of Useful Downlink RLC Pending Blocks in DAS9 Coding on PDTCH ....................................................................................................................9-21 C901030103 Number of Useful Downlink RLC Pending Blocks in DAS10 Coding on PDTCH................................................................................................................9-22 C901030104 Number of Useful Downlink RLC Pending Blocks in DAS11 Coding on PDTCH................................................................................................................9-22 C901030105 Number of Useful Downlink RLC Pending Blocks in DAS12 Coding on PDTCH................................................................................................................9-23 C901030106 Number of Useful Uplink RLC Pending Blocks in UAS7 Coding on PDTCH ....................................................................................................................9-23
9-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901030107 Number of Useful Uplink RLC Pending Blocks in UAS8 Coding on PDTCH ....................................................................................................................9-24 C901030108 Number of Useful Uplink RLC Pending Blocks in UAS9 Coding on PDTCH ....................................................................................................................9-24 C901030109 Number of Useful Uplink RLC Pending Blocks in UAS10 Coding on PDTCH ....................................................................................................................9-25 C901030110 Number of Useful Uplink RLC Pending Blocks in UAS11 Coding on PDTCH ....................................................................................................................9-25 C901030111 Number of Useful Downlink RLC NACK Blocks in DAS5 Coding on PDTCH ....................................................................................................................9-26 C901030112 Number of Useful Downlink RLC NACK Blocks in DAS6 Coding on PDTCH ....................................................................................................................9-26 C901030113 Number of Useful Downlink RLC NACK Blocks in DAS7 Coding on PDTCH ....................................................................................................................9-27 C901030114 Number of Useful Downlink RLC NACK Blocks in DAS8 Coding on PDTCH ....................................................................................................................9-27 C901030115 Number of Useful Downlink RLC NACK Blocks in DAS9 Coding on PDTCH ....................................................................................................................9-28 C901030116 Number of Useful Downlink RLC NACK Blocks in DAS10 Coding on PDTCH ....................................................................................................................9-28 C901030117 Number of Useful Downlink RLC NACK Blocks in DAS11 Coding on PDTCH ....................................................................................................................9-29 C901030118 Number of Useful Downlink RLC NACK Blocks in DAS12 Coding on PDTCH ....................................................................................................................9-29 C901030119 Number of Useful Uplink RLC NACK Blocks in UAS7 Coding on PDTCH ....................................................................................................................9-30 C901030120 Number of Useful Uplink RLC NACK Blocks in UAS8 Coding on PDTCH ....................................................................................................................9-30 C901030121 Number of Useful Uplink RLC NACK Blocks in UAS9 Coding on PDTCH ....................................................................................................................9-31 C901030122 Number of Useful Uplink RLC NACK Blocks in UAS10 Coding on PDTCH ....................................................................................................................9-31 C901030123 Number of Useful Uplink RLC NACK Blocks in UAS11 Coding on PDTCH ....................................................................................................................9-32 C901030124 Number of New Downlink RLC Blocks in DAS5 Coding on PDTCH .....9-32 C901030125 Number of New Downlink RLC Blocks in DAS6 Coding on PDTCH .....9-33 C901030126 Number of New Downlink RLC Blocks in DAS7 Coding on PDTCH .....9-33 C901030127 Number of New Downlink RLC Blocks in DAS8 Coding on PDTCH .....9-34 C901030128 Number of New Downlink RLC Blocks in DAS9 Coding on PDTCH .....9-34 C901030129 Number of New Downlink RLC Blocks in DAS10 Coding on PDTCH ...9-35 C901030130 Number of New Downlink RLC Blocks in DAS11 Coding on PDTCH ...9-35 C901030131 Number of New Downlink RLC Blocks in DAS12 Coding on PDTCH ...9-36 C901030132 Number of New Uplink RLC Blocks in UAS7 Coding on PDTCH .........9-36 C901030133 Number of New Uplink RLC Blocks in UAS8 Coding on PDTCH .........9-37 C901030134 Number of New Uplink RLC Blocks in UAS9 Coding on PDTCH .........9-37
9-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

C901030135 Number of New Uplink RLC Blocks in UAS10 Coding on PDTCH........9-38 C901030136 Number of New Uplink RLC Blocks in UAS11 Coding on PDTCH........9-38 C901030137 Times of Receive Window Stall of EGPRS2-A TBF .............................9-39 C901030138 Times of Send Window Stall of EGPRS2-A TBF..................................9-39 C901030139 Times of Changes From 8PSK to 16QAM ...........................................9-40 C901030140 Times of Changes From 8PSK to 32QAM ...........................................9-40 C901030141 Times of Changes From 16QAM to 32QAM.........................................9-41 C901030142 Times of Changes From 32QAM to 16QAM.........................................9-41 C901030143 Times of Changes From 32QAM to 8PSK ...........................................9-41 C901030144 Times of Changes From 16QAM to 8PSK ...........................................9-42 C901030145 Times of Changes From GMSK to 16QAM ..........................................9-42 C901030146 Times of Changes From GMSK to 32QAM ..........................................9-43 C901030147 Times of Changes From 32QAM to GMSK ..........................................9-43 C901030148 Times of Changes From 16QAM to GMSK ..........................................9-43 C901030149 Times of Changes From Uplink EGPRS to EGPRS2-A........................9-44 C901030150 Times of Changes From Uplink EGPRS2-A to EGPRS........................9-44 C901030151 Times of Changes From Downlink EGPRS to EGPRS2-A ...................9-45 C901030152 Times of Changes From Downlink EGPRS2-A to EGPRS ...................9-45 C901030153 Number of increment of GPRS DL coding mode..................................9-45 C901030154 Number of decrement of GPRS DL coding mode ................................9-46 C901030155 Number of increment of GPRS UL coding mode..................................9-47 C901030156 Number of decrement of GPRS UL coding mode ................................9-48 C901030157 Number of increment of EGPRS DL coding mode ...............................9-48 C901030158 Number of decrement of EGPRS DL coding mode ..............................9-49 C901030159 Number of increment of EGPRS UL coding mode ...............................9-50 C901030160 Number of decrement of EGPRS UL coding mode ..............................9-50 C901030161 Number of Bytes Lost by Uplink EGPRS2-A RLC on PDTCH ..............9-51 C901030162 Num Uplink TBF Received PAN of Using MCS....................................9-51 C901030163 Num Downlink TBF Received PAN of Using MCS ...............................9-52 C901030164 Num Uplink TBF Received PAN of Using UAS ....................................9-52 C901030165 Num Downlink TBF Received PAN of Using UAS ................................9-52

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. 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. The measurement takes cell as the statistics unit.
9-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

9.3 C901030042 Bytes of EGPRS DL RLC lost on PDTCH

Definition
Bytes of EGPRS DL RLC lost on PDTCH

Description
This counter is not used for the time being.

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 point is A, as shown in Figure 9-7.
Figure 9-7 Measurement Point Of Number Of UL RLC Blocks Lost

Unit
Times

9-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

9.5 C901030084 Bytes of GPRS UL RLC lost on PDTCH

Definition
Bytes of GPRS UL RLC lost on PDTCH

Description
MS sends UL RLC data block to BSC by BTS. The counter keeps record of the number of CS-coded RLC bytes lost on PDTCH in non-ack mode.

Usage
This counter is used to find out the number of CS-coded RLC bytes on UL PDTCH in non-ack mode.

Measurement Point
The counter increments when CS-coded UL RLC block from BTS gets lost. measurement point is A, as shown in Figure 9-8.
Figure 9-8 Measurement Point Of Number Of UL RLC Blocks 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
MS sends UL RLC data block to BSC by BTS. The counter keeps record of the number of MCS-coded RLC bytes lost on PDTCH in non-ack mode.
9-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. measurement point is A, as shown in Figure 9-9.
Figure 9-9 Measurement Point Of Number Of UL RLC Blocks 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-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

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-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

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-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

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).
Figure 9-15 Measurement Point Of Number Of Increment Of DL Coding Mode (EDGE RLC Block)

9-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 9-16 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.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. measurement point is A, as shown in Figure 9-17. The

9-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

Figure 9-17 Measurement Point Of Number Of Increment Of UL Coding Mode

Unit
Times

Related Features
ZGB-03-05-012 GPRS Link Adaptation ZGO-03-05-002 EGPRS Link Adaptation

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-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 9-18 Measurement Point Of Number Of Increment Of UL Coding Mode

Unit
Times

Related Features
ZGB-03-05-012 GPRS Link Adaptation ZGO-03-05-002 EGPRS Link Adaptation

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-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

Figure 9-19 Measurement Point Of Number Of Increment Of DL Coding Mode (EDGE RLC Block)

Figure 9-20 Measurement Point Of Number Of Increment Of DL Coding Mode (GPRS RLC Block)

Figure 9-21 Measurement Point Of Number Of Increment Of UL Coding Mode

9-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-03-05-002 EGPRS Link Adaptation

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.
Figure 9-22 Measurement Point Of Number Of Increment Of DL Coding Mode (EDGE RLC Block)

9-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

Figure 9-23 Measurement Point Of Number Of Increment Of DL Coding Mode (GPRS RLC Block)

Figure 9-24 Measurement Point Of Number Of Increment Of UL Coding Mode

Unit
Times

Related Features
ZGO-03-05-002 EGPRS Link Adaptation

9.17 C901030098 Number of Useful Downlink RLC Pending Blocks in DAS5 Coding 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 DAS5.
9-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of DAS5.

Measurement Point
When BSC sends a pending RLC block whose coding method is DAS5 to MS via BTS, the counter increments.

Unit
Block

9.18 C901030099 Number of Useful Downlink RLC Pending Blocks in DAS6 Coding 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 DAS6. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of DAS6.

Measurement Point
When BSC sends a pending RLC block whose coding method is DAS6 to MS via BTS, the counter increments.

Unit
Block

9.19 C901030100 Number of Useful Downlink RLC Pending Blocks in DAS7 Coding 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 DAS7.
9-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of DAS7.

Measurement Point
When BSC sends a pending RLC block whose coding method is DAS7 to MS via BTS, the counter increments.

Unit
Block

9.20 C901030101 Number of Useful Downlink RLC Pending Blocks in DAS8 Coding 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 DAS8. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of DAS8.

Measurement Point
When BSC sends a pending RLC block whose coding method is DAS8 to MS via BTS, the counter increments.

Unit
Block

9.21 C901030102 Number of Useful Downlink RLC Pending Blocks in DAS9 Coding 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 DAS9.
9-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of DAS9.

Measurement Point
When BSC sends a pending RLC block whose coding method is DAS9 to MS via BTS, the counter increments.

Unit
Block

9.22 C901030103 Number of Useful Downlink RLC Pending Blocks in DAS10 Coding 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 DAS10. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of DAS10.

Measurement Point
When BSC sends a pending RLC block whose coding method is DAS10 to MS via BTS, the counter increments.

Unit
Block

9.23 C901030104 Number of Useful Downlink RLC Pending Blocks in DAS11 Coding 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 DAS11.
9-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of DAS11.

Measurement Point
When BSC sends a pending RLC block whose coding method is DAS11 to MS via BTS, the counter increments.

Unit
Block

9.24 C901030105 Number of Useful Downlink RLC Pending Blocks in DAS12 Coding 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 DAS12. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of DAS12.

Measurement Point
When BSC sends a pending RLC block whose coding method is DAS12 to MS via BTS, the counter increments.

Unit
Block

9.25 C901030106 Number of Useful Uplink RLC Pending Blocks in UAS7 Coding on PDTCH
Description
This counter counts RLC pending blocks using UAS7 that are received by the BSC on the uplink PDTCH.

9-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC pending blocks using UAS7 are received on the uplink PDTCH, this counter adds the number of these received RLC pending blocks. This counter is applicable on the RLC layer and indicates the number of RLC pending blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC pending block using UAS7.

Unit
Block

9.26 C901030107 Number of Useful Uplink RLC Pending Blocks in UAS8 Coding on PDTCH
Description
This counter counts RLC pending blocks using UAS8 that are received by the BSC on the uplink PDTCH. The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC pending blocks using UAS8 are received on the uplink PDTCH, this counter adds the number of these received RLC pending blocks. This counter is applicable on the RLC layer and indicates the number of RLC pending blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC pending block using UAS8.

Unit
Block

9.27 C901030108 Number of Useful Uplink RLC Pending Blocks in UAS9 Coding on PDTCH
Description
This counter counts RLC pending blocks using UAS9 that are received by the BSC on the uplink PDTCH.
9-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC pending blocks using UAS9 are received on the uplink PDTCH, this counter adds the number of these received RLC pending blocks. This counter is applicable on the RLC layer and indicates the number of RLC pending blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC pending block using UAS9.

Unit
Block

9.28 C901030109 Number of Useful Uplink RLC Pending Blocks in UAS10 Coding on PDTCH
Description
This counter counts RLC pending blocks using UAS10 that are received by the BSC on the uplink PDTCH. The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC pending blocks using UAS10 are received on the uplink PDTCH, this counter adds the number of these received RLC pending blocks. This counter is applicable on the RLC layer and indicates the number of RLC pending blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC pending block using UAS10.

Unit
Block

9.29 C901030110 Number of Useful Uplink RLC Pending Blocks in UAS11 Coding on PDTCH
Description
This counter counts RLC pending blocks using UAS11 that are received by the BSC on the uplink PDTCH.
9-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC pending blocks using UAS11 are received on the uplink PDTCH, this counter adds the number of these received RLC pending blocks. This counter is applicable on the RLC layer and indicates the number of RLC pending blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC pending block using UAS11.

Unit
Block

9.30 C901030111 Number of Useful Downlink RLC NACK Blocks in DAS5 Coding 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 retransmitted RLC blocks from BSC to MS, with coding method of DAS5. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of DAS5.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is DAS5 to MS via BTS, the counter increments.

Unit
Block

9.31 C901030112 Number of Useful Downlink RLC NACK Blocks in DAS6 Coding 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 retransmitted RLC blocks from BSC to MS, with coding method of DAS6.
9-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of DAS6.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is DAS6 to MS via BTS, the counter increments.

Unit
Block

9.32 C901030113 Number of Useful Downlink RLC NACK Blocks in DAS7 Coding 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 retransmitted RLC blocks from BSC to MS, with coding method of DAS7. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of DAS7.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is DAS7 to MS via BTS, the counter increments.

Unit
Block

9.33 C901030114 Number of Useful Downlink RLC NACK Blocks in DAS8 Coding 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 retransmitted RLC blocks from BSC to MS, with coding method of DAS8.
9-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of DAS8.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is DAS8 to MS via BTS, the counter increments.

Unit
Block

9.34 C901030115 Number of Useful Downlink RLC NACK Blocks in DAS9 Coding 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 retransmitted RLC blocks from BSC to MS, with coding method of DAS9. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of DAS9.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is DAS9 to MS via BTS, the counter increments.

Unit
Block

9.35 C901030116 Number of Useful Downlink RLC NACK Blocks in DAS10 Coding 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 retransmitted RLC blocks from BSC to MS, with coding method of DAS10.
9-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of DAS10.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is DAS10 to MS via BTS, the counter increments.

Unit
Block

9.36 C901030117 Number of Useful Downlink RLC NACK Blocks in DAS11 Coding 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 retransmitted RLC blocks from BSC to MS, with coding method of DAS11. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of DAS11.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is DAS11 to MS via BTS, the counter increments.

Unit
Block

9.37 C901030118 Number of Useful Downlink RLC NACK Blocks in DAS12 Coding 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 retransmitted RLC blocks from BSC to MS, with coding method of DAS12.
9-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of DAS12.

Measurement Point
When BSC sends retransmitted RLC block whose coding method is DAS12 to MS via BTS, the counter increments.

Unit
Block

9.38 C901030119 Number of Useful Uplink RLC NACK Blocks in UAS7 Coding on PDTCH
Description
This counter counts RLC NACK blocks using UAS7 that are received by the BSC on the uplink PDTCH. The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC NACK blocks using UAS7 are received on the uplink PDTCH, this counter adds the number of these received RLC NACK blocks. This counter is applicable on the RLC layer and indicates the number of RLC NACK blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC NACK block using UAS7.

Unit
Block

9.39 C901030120 Number of Useful Uplink RLC NACK Blocks in UAS8 Coding on PDTCH
Description
This counter counts RLC NACK blocks using UAS8 that are received by the BSC on the uplink PDTCH.

9-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC NACK blocks using UAS8 are received on the uplink PDTCH, this counter adds the number of these received RLC NACK blocks. This counter is applicable on the RLC layer and indicates the number of RLC NACK blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC NACK block using UAS8.

Unit
Block

9.40 C901030121 Number of Useful Uplink RLC NACK Blocks in UAS9 Coding on PDTCH
Description
This counter counts RLC NACK blocks using UAS9 that are received by the BSC on the uplink PDTCH. The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC NACK blocks using UAS9 are received on the uplink PDTCH, this counter adds the number of these received RLC NACK blocks. This counter is applicable on the RLC layer and indicates the number of RLC NACK blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC NACK block using UAS9.

Unit
Block

9.41 C901030122 Number of Useful Uplink RLC NACK Blocks in UAS10 Coding on PDTCH
Description
This counter counts RLC NACK blocks using UAS10 that are received by the BSC on the uplink PDTCH.

9-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC NACK blocks using UAS10 are received on the uplink PDTCH, this counter adds the number of these received RLC NACK blocks. This counter is applicable on the RLC layer and indicates the number of RLC NACK blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC NACK block using UAS10.

Unit
Block

9.42 C901030123 Number of Useful Uplink RLC NACK Blocks in UAS11 Coding on PDTCH
Description
This counter counts RLC NACK blocks using UAS11 that are received by the BSC on the uplink PDTCH. The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC NACK blocks using UAS11 are received on the uplink PDTCH, this counter adds the number of these received RLC NACK blocks. This counter is applicable on the RLC layer and indicates the number of RLC NACK blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC NACK block using UAS11.

Unit
Block

9.43 C901030124 Number of New Downlink RLC Blocks in DAS5 Coding 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 first-transmitted RLC blocks from BSC to MS, with coding method of DAS5.

9-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of DAS5.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of DAS5) to MS via BTS, the counter increments.

Unit
Block

9.44 C901030125 Number of New Downlink RLC Blocks in DAS6 Coding 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 first-transmitted RLC blocks from BSC to MS, with coding method of DAS6. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of DAS6.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of DAS6) to MS via BTS, the counter increments.

Unit
Block

9.45 C901030126 Number of New Downlink RLC Blocks in DAS7 Coding 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 first-transmitted RLC blocks from BSC to MS, with coding method of DAS7.
9-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of DAS7.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of DAS7) to MS via BTS, the counter increments.

Unit
Block

9.46 C901030127 Number of New Downlink RLC Blocks in DAS8 Coding 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 first-transmitted RLC blocks from BSC to MS, with coding method of DAS8. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of DAS8.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of DAS8) to MS via BTS, the counter increments.

Unit
Block

9.47 C901030128 Number of New Downlink RLC Blocks in DAS9 Coding 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 first-transmitted RLC blocks from BSC to MS, with coding method of DAS9.
9-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of DAS9.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of DAS9) to MS via BTS, the counter increments.

Unit
Block

9.48 C901030129 Number of New Downlink RLC Blocks in DAS10 Coding 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 first-transmitted RLC blocks from BSC to MS, with coding method of DAS10. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of DAS10.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of DAS10) to MS via BTS, the counter increments.

Unit
Block

9.49 C901030130 Number of New Downlink RLC Blocks in DAS11 Coding 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 first-transmitted RLC blocks from BSC to MS, with coding method of DAS11.
9-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of DAS11.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of DAS11) to MS via BTS, the counter increments.

Unit
Block

9.50 C901030131 Number of New Downlink RLC Blocks in DAS12 Coding 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 first-transmitted RLC blocks from BSC to MS, with coding method of DAS12. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks. The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of DAS12.

Measurement Point
When BSC sends first-transmitted RLC block (with coding method of DAS12) to MS via BTS, the counter increments.

Unit
Block

9.51 C901030132 Number of New Uplink RLC Blocks in UAS7 Coding on PDTCH
Description
This counter counts RLC new blocks using UAS7 that are received by the BSC on the uplink PDTCH.

9-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC new blocks using UAS7 are received on the uplink PDTCH, this counter adds the number of these received RLC new blocks. This counter is applicable on the RLC layer and indicates the number of RLC new blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC new block using UAS7.

Unit
Block

9.52 C901030133 Number of New Uplink RLC Blocks in UAS8 Coding on PDTCH
Description
This counter counts RLC new blocks using UAS8 that are received by the BSC on the uplink PDTCH. The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC new blocks using UAS8 are received on the uplink PDTCH, this counter adds the number of these received RLC new blocks. This counter is applicable on the RLC layer and indicates the number of RLC new blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC new block using UAS8.

Unit
Block

9.53 C901030134 Number of New Uplink RLC Blocks in UAS9 Coding on PDTCH
Description
This counter counts RLC new blocks using UAS9 that are received by the BSC on the uplink PDTCH.

9-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC new blocks using UAS9 are received on the uplink PDTCH, this counter adds the number of these received RLC new blocks. This counter is applicable on the RLC layer and indicates the number of RLC new blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC new block using UAS9.

Unit
Block

9.54 C901030135 Number of New Uplink RLC Blocks in UAS10 Coding on PDTCH
Description
This counter counts RLC new blocks using UAS10 that are received by the BSC on the uplink PDTCH. The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC new blocks using UAS10 are received on the uplink PDTCH, this counter adds the number of these received RLC new blocks. This counter is applicable on the RLC layer and indicates the number of RLC new blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC new block using UAS10.

Unit
Block

9.55 C901030136 Number of New Uplink RLC Blocks in UAS11 Coding on PDTCH
Description
This counter counts RLC new blocks using UAS11 that are received by the BSC on the uplink PDTCH.

9-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

The BSC detects whether the received uplink data contains RLC NACK blocks, RLC new blocks, or RLC pending blocks. If RLC new blocks using UAS11 are received on the uplink PDTCH, this counter adds the number of these received RLC new blocks. This counter is applicable on the RLC layer and indicates the number of RLC new blocks.

Measurement Point
This counter is incremented each time the BSC receives an uplink RLC new block using UAS11.

Unit
Block

9.56 C901030137 Times of Receive Window Stall of EGPRS2-A TBF

Description
This counter counts the number of times that the uplink EGPRS2-A TBF receive window is stalled.

Measurement Point
This counter is incremented when the data block received by the uplink RLC instance is a new data block containing a window stall flag after uplink EGPRS2-A TBF establishment.

Unit
Times

9.57 C901030138 Times of Send Window Stall of EGPRS2-A TBF

Description
This counter counts the number of times that the downlink EGPRS2-A TBF transmit window is stalled.

Measurement Point
This counter is incremented when the PendingAck data block or new data block to be sent by the downlink RLC instance contains a window stall flag after downlink EGPRS2-A TBF establishment.

9-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

9.58 C901030139 Times of Changes From 8PSK to 16QAM

Description
This counter counts the number of times that the modulation scheme changes from 8PSK to 16QAM.

Measurement Point
The uplink RLC instance considers that the modulation scheme changes from 8PSK to 16QAM when detecting an old coding scheme of MSC_9 or lower level and a new coding scheme of UAS_7 or higher level in the measurement report being processed. This counter is incremented each time the downlink RLC instance adjusts the modulation coding mode from 8PSK to 16QAM in accordance with the measurement report.

Unit
Times

9.59 C901030140 Times of Changes From 8PSK to 32QAM

Description
This counter counts the number of times that the modulation scheme changes from 8PSK to 32QAM. This counter is not used in this version.

Measurement Point
None

Unit
Times

9-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

9.60 C901030141 Times of Changes From 16QAM to 32QAM

Description
This counter counts the number of times that the modulation scheme changes from 16QAM to 32QAM.

Measurement Point
This counter is incremented each time the downlink RLC instance adjusts the modulation coding mode from 16QAM to 32QAM in accordance with the measurement report.

Unit
Times

9.61 C901030142 Times of Changes From 32QAM to 16QAM

Description
This counter counts the number of times that the modulation scheme changes from 32QAM to 16QAM.

Measurement Point
This counter is incremented each time the downlink RLC instance adjusts the modulation coding mode from 32QAM to 16QAM in accordance with the measurement report.

Unit
Times

9.62 C901030143 Times of Changes From 32QAM to 8PSK

Description
This counter counts the number of times that the modulation scheme changes from 32QAM to 8PSK. This counter is not used in this version.

Measurement Point
None
9-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

9.63 C901030144 Times of Changes From 16QAM to 8PSK

Description
This counter counts the number of times that the modulation scheme changes from 16QAM to 8PSK.

Measurement Point
The uplink RLC instance considers that the modulation scheme changes from 16QAM to 8PSK when detecting an old coding scheme of MSC_7 or lower level and a new coding scheme of UAS_9 or higher level in the measurement report being processed. This counter is incremented each time the downlink RLC instance adjusts the modulation coding mode from 16QAM to 8PSK in accordance with the measurement report.

Unit
Times

9.64 C901030145 Times of Changes From GMSK to 16QAM

Description
This counter counts the number of times that the modulation scheme changes from GMSK to 16QAM. This counter is not used in this version.

Measurement Point
None

Unit
Times

9-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

9.65 C901030146 Times of Changes From GMSK to 32QAM

Description
This counter counts the number of times that the modulation scheme changes from GMSK to 32QAM. This counter is not used in this version.

Measurement Point
None

Unit
Times

9.66 C901030147 Times of Changes From 32QAM to GMSK

Description
This counter counts the number of times that the modulation scheme changes from 32QAM to GMSK. This counter is not used in this version.

Measurement Point
None

Unit
Times

9.67 C901030148 Times of Changes From 16QAM to GMSK

Description
This counter counts the number of times that the modulation scheme changes from 16QAM to GMSK. This counter is not used in this version.

9-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
None

Unit
Times

9.68 C901030149 Times of Changes From Uplink EGPRS to EGPRS2-A

Description
This counter counts the number of times that the uplink mode changes from EGPRS to EGPRS2-A. This counter is not used in this version.

Measurement Point
None

Unit
Times

9.69 C901030150 Times of Changes From Uplink EGPRS2-A to EGPRS

Description
This counter counts the number of times that the uplink mode changes from EGPRS2-A to EGPRS. This counter is not used in this version.

Measurement Point
None

Unit
Times

9-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

9.70 C901030151 Times of Changes From Downlink EGPRS to EGPRS2-A

Description
This counter counts the number of times that the downlink mode changes from EGPRS to EGPRS2-A. This counter is not used in this version.

Measurement Point
None

Unit
Times

9.71 C901030152 Times of Changes From Downlink EGPRS2-A to EGPRS

Description
This counter counts the number of times that the downlink mode changes from EGPRS2-A to EGPRS. This counter is not used in this version.

Measurement Point
None

Unit
Times

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

9-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the condition of downlink RLC block's coding mode being upgraded. This counter is supported in version V6.20.200a or above.

Measurement Point
When the coding mode of downlink RLC block sent to BTS from BSC is upgraded, the counter increments. The measurement point is A, as shown in Figure 9-25.
Figure 9-25 Measurement Point of Downlink GPRS RLC Block Coding Mode Adjustment

Unit
Times

9.73 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
This counter is used to find out the condition of downlink RLC block's coding mode being degraded. This counter is supported in version V6.20.200a or above.

9-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

Measurement Point
When the coding mode of downlink RLC block sent to BTS from BSC is degraded, the counter increments.

Unit
Times

9.74 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. This counter is supported in version V6.20.200a or above.

Measurement Point
When the coding mode of uplink RLC block received by BSC is upgraded, the counter increments. The measurement point is A, as shown in Figure 9-26.
Figure 9-26 Measurement Point of Uplink RLC Block Coding Mode Adjustment

Unit
Times

9-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

9.75 C901030156 Number of decrement 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 degraded.

Usage
This counter is used to find out the condition of uplink coding mode being degraded. This counter is supported in version V6.20.200a or above.

Measurement Point
When the coding mode of uplink RLC block received by BSC is degraded, the counter increments.

Unit
Times

9.76 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 according to the measurement report. This counter counts the number of times that the downlink coding mode is upgraded.

Usage
This counter is used to find out the condition of downlink RLC block's coding mode being upgraded. This counter is supported in version V6.20.200a or above.

Measurement Point
When the coding mode of downlink RLC block sent to BTS from BSC is upgraded, the counter increments. The measurement point is A, as shown in Figure 9-27.

9-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

Figure 9-27 Measurement Point of Downlink EDGE RLC Block Coding Mode Adjustment

Unit
Times

9.77 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 according to the measurement report. This counter counts the number of times that the downlink coding mode is degraded.

Usage
This counter is used to find out the condition of downlink RLC block's coding mode being degraded. 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 degraded, the counter increments.

Unit
Times

9-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

9.78 C901030159 Number of increment of EGPRS 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. This counter is supported in version V6.20.200a or above.

Measurement Point
When the coding mode of uplink RLC block received by BSC is upgraded, the counter increments. The measurement point is A, as shown in Figure 9-28.
Figure 9-28 Measurement Point of Uplink RLC Block Coding Mode Adjustment

Unit
Times

9.79 C901030160 Number of decrement of EGPRS 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 degraded.
9-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

Usage
This counter is used to find out the condition of uplink coding mode being degraded. This counter is supported in version V6.20.200a or above.

Measurement Point
When the coding mode of uplink RLC block received by BSC is degraded, the counter increments.

Unit
Times

9.80 C901030161 Number of Bytes Lost by Uplink EGPRS2-A RLC on PDTCH

Description
This counter counts lost uplink RLC bytes in EGPRS2-A mode on the PDTCH.

Measurement Point
This counter is incremented each time a received RLC block is null in uplink RLC packets.

Unit
Byte

9.81 C901030162 Num Uplink TBF Received PAN of Using MCS

Description
This counter counts the number of times that an uplink PAN using MCS is received. This counter is not used in this version.

Measurement Point
None

Unit
Times

9-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

9.82 C901030163 Num Downlink TBF Received PAN of Using MCS

Description
This counter counts the number of times that a downlink PAN using MCS is received. This counter is not used in this version.

Measurement Point
None

Unit
Times

9.83 C901030164 Num Uplink TBF Received PAN of Using UAS

Description
This counter counts the number of times that an uplink PAN using UAS is received. This counter is not used in this version.

Measurement Point
None

Unit
Times

9.84 C901030165 Num Downlink TBF Received PAN of Using UAS

Description
This counter counts the number of times that a downlink PAN using UAS is received. This counter is not used in this version.

Measurement Point
None

9-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 9 Uplink-Downlink RLC Statistic Measurement

Unit
Times

9-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

9-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10

PS Resource Used Statistic Measurement

Table of Contents
Overview ..................................................................................................................10-3 C901040001 Maximum Number of Abis TS Used.....................................................10-3 C901040002 Average Number of Abis TS Used.......................................................10-3 C901040004 Average number of unavailable PDCH ................................................10-4 C901040005 Number of available static PDCH ........................................................10-4 C901040006 Number of unavailable static PDCH ....................................................10-5 C901040009 Time of DL PDCH congestion..............................................................10-5 C901040010 Time of UL PDCH congestion..............................................................10-6 C901040011 Time of PDCH used at least one UL/DL TBF exists .............................10-7 C901040012 Time of PDCH used at least one UL/DL EGPRS TBF exists................10-8 C901040013 Time of PDCH used at least one DL TBF exists ..................................10-9 C901040014 Time of PDCH used at least one UL TBF exists ..................................10-9 C901040018 Number of immediate assignment on AGCH .....................................10-10 C901040019 Number of paging PS requests on PCH ............................................ 10-11 C901040020 Number of paging CS requests on PCH ............................................10-12 C901040021 Number of immediate assignment on PCH ........................................10-13 C901040022 Number of immediate assignment on PAGCH ...................................10-14 C901040023 Number of paging PS requests on PPCH ..........................................10-15 C901040024 Number of paging CS requests on PPCH ..........................................10-16 C901040025 Number of immediate assignment on PPCH......................................10-17 C901040026 Number of Packet Channel Request on PRACH ...............................10-18 C901040027 Sum of Abis TS Used Sampling ........................................................10-19 C901040028 Number of Abis TS used sampling ....................................................10-19 C901040029 Sum of PDCH used sampling ............................................................10-20 C901040030 Number of PDCH used sampling.......................................................10-20 C901040031 Maximum value of Abis TS used to CS..............................................10-21 C901040032 Minimum value of Abis TS used to CS...............................................10-21 C901040033 Total value of the regular sampling used to CS ..................................10-22 C901040034 Number of sampling of CS ................................................................10-22 C901040035 Maximum value of Abis TS used to PS..............................................10-23 C901040036 Minimum value of Abis TS used to PS...............................................10-23 C901040037 Total value of the regular sampling used to PS ..................................10-24 C901040038 Number of sampling of PS.................................................................10-25 C901040039 MAX CS used number of exclusive ABIS ..........................................10-25
10-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901040040 MIN CS used number of exclusive ABIS............................................10-26 C901040041 MAX PS used number of exclusive ABIS...........................................10-26 C901040042 MIN PS used number of exclusive ABIS............................................10-27 C901040043 Average Number of GPRS User ........................................................10-27 C901040044 Maximum number of GPRS User ......................................................10-28 C901040045 Average Number of EGPRS User......................................................10-28 C901040046 Maximum number of EDGE User ......................................................10-29 C901040047 Number of assigned uplink radio channels ........................................10-29 C901040048 Number of assigned downlink radio channels....................................10-30 C901040049 Number of requested uplink radio channels.......................................10-30 C901040050 Number of requested downlink radio channels ..................................10-31 C901040051 Number of PS channel expand..........................................................10-31 C901040052 Number of PS channel expand perform.............................................10-31 C901040053 Number of PS channel expand success ............................................10-32 C901040054 Total number of all TBF used uplink PDCH .......................................10-32 C901040055 Total number of all TBF used downlink PDCH ..................................10-33 C901040056 Sample number of all TBF used uplink PDCH ..................................10-34 C901040057 Sample number of all TBF used downlink PDCH ..............................10-34 C901040058 Average number used uplink PDCH ..................................................10-35 C901040059 Average number used downlink PDCH..............................................10-35 C901040060 Sum of uplink PDCH used sampling ..................................................10-36 C901040061 Sum of downlink PDCH used sampling .............................................10-36 C901040062 Number of uplink PDCH used sampling.............................................10-37 C901040063 Number of downlink PDCH used sampling ........................................10-37 C901040064 Average number of all TBF used total uplink PDCH ..........................10-38 C901040065 Average number of all TBF used total downlink PDCH .....................10-39 C901040078 Time of PDCH Used at Least One UL/DL TBF Exists ........................10-39 C901040079 Time of Configured EGPRS PDCH Used at Least One UL/DL EGPRS TBF Exists..............................................................................................................10-40 C901040080 Total number of all GPRS TBF used PDCH .......................................10-40 C901040081 Sample number of all GPRS TBF used PDCH ..................................10-41 C901040082 Average number of GPRS TBF used total PDCH ..............................10-41 C901040083 Total number of all EGPRS TBF used PDCH.....................................10-42 C901040084 Sample number of all EGPRS TBF used PDCH ................................10-42 C901040085 Average number of EGPRS TBF used total PDCH ............................10-43 C901040086 Total number of all EGPRS TBF used EGPRS only PDCH ................10-43 C901040087 Sample number of all EGPRS TBF used EGPRS only PDCH............10-44 C901040088 Average number of EGPRS TBF used total EGPRS only PDCH .......10-44 C901040089 UL Request PDCH Times..................................................................10-45 C901040090 UL Unsatisfied PDCH Times .............................................................10-45 C901040091 DL Request PDCH Times..................................................................10-46 C901040092 DL Unsatisfied PDCH Times .............................................................10-46 C901040093 Average Number of PDCH Allocated Per UL TBF .............................10-47 C901040094 Sample Number of PDCH Allocated Per UL TBF...............................10-47 C901040095 Average Number of PDCH Allocated Per DL TBF .............................10-48
10-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

C901040096 Sample Number of PDCH Allocated Per DL TBF...............................10-48

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. The measurement takes cell as the statistics unit.

10.2 C901040001 Maximum Number of Abis TS Used

Description
This counter indicates the usage of Abis resources in a cell during a measurement period. It reflects the transient occupation of Abis resources and the busy degree of the cell. l l For a site using the TDM access mode, this counter indicates the maximum number of Abis timeslots that are used during a measurement period. For a site using the IP access mode, this counter indicates the maximum Abis bandwidth that is used during a measurement period.

Usage
This counter is used to find out the Abis resource occupation in the current cell, which helps to adjust or expand Abis resources.

Measurement Point
This counter is updated with the value queried from the database when the measurement data is periodically reported.

Unit
Number of timeslots (TDM) or Kbps (IP)

10.3 C901040002 Average Number of Abis TS Used

Description
This counter indicates the average usage of Abis resources in a cell during a measurement period. l l For a site using the TDM access mode, this counter indicates the average number of Abis timeslots that are used during a measurement period. For a site using the IP access mode, this counter indicates the average Abis bandwidth that is used during a measurement period.
10-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the Abis resource occupation in the current cell, which helps to adjust or expand Abis resources.

Measurement Point
This counter is updated with the value queried from the database when the measurement data is periodically reported.

Unit
Number of timeslots (TDM) or Kbps (IP)

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
Inquire the database when periodic measurement data report to get the counter value.

Unit
Times

10.5 C901040005 Number of available static PDCH

Definition
Number of available static PDCH

Description
iBSC supports dynamic wireless channels. This counter counts the number of available PDCHs configured through OMCR in the current cell.

Usage
This counter is used to find out the number of available static PDCHs in the current cell, which helps to make troubleshooting.
10-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

Measurement Point
Inquire the database when periodic measurement data report to get the counter value.

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
Inquire the database when periodic measurement data report to get the counter value.

Unit
Times

Related Features
ZGB-03-02-005 GPRS-only (without voice) Timeslots Configurable ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-010 GPRS and EGPRS Channels Allocated Separately

10.7 C901040009 Time of DL PDCH congestion

Definition
Time of DL PDCH congestion
10-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 l l Before DL PDCH attempts to occupy, if the congestion label is set, this counter calculates the congestion time and accumulates them. Before DL PDCH is released, if the congestion label is set, this counter calculates the congestion time and accumulates them. When reporting the measurement data periodically, if the congestion label is set, this counter calculates the congestion time and accumulates them.

Unit
Second

10.8 C901040010 Time of UL PDCH congestion

Definition
Time of UL PDCH congestion

Description
This counter counts the time during which the service instance fails to apply UL PDCHs (namely the total time of UL PDCH congestion). If UL PDCH application fails, BSC records the congestion label and the time when congestion starts. If UL PDCH application succeeds, BSC clears the congestion label. When applying for UL PDCH, if the congestion label is set, the current time minus the congestion time of the previous record leaves the new congestion time.
10-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

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 reference for whether more PDCHs should be configured.

Measurement Point
The measurement is taken at three time points listed below: l l l Before UL PDCH attempts to occupy, if the congestion label is set, this counter calculates the congestion time and accumulates them. Before UL PDCH is released, if the congestion label is set, this counter calculates the congestion time and accumulates them. When reporting the measurement data periodically, if the congestion label is set, this counter calculates the congestion time and accumulates them.

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.

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
The measurement is taken at three time points listed below: l When PDCH resource is acquired successfully, this counter calculates and accumulates.
10-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

l l

When PDCH resource is released, this counter calculates and accumulates. When reporting the measurement data periodically, this counter calculates and accumulates.

Unit
Second

Related Features
ZGO-03-02-010 GPRS and EGPRS Channels Allocated Separately

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 reference for whether more PDCHs should be configured.

Measurement Point
The measurement is taken at three time points listed below: l l l When PDCH resource is acquired successfully, this counter calculates and accumulates. When PDCH resource is released, this counter calculates and accumulates. When reporting the measurement data periodically, this counter calculates and accumulates.

Unit
Second

Related Features
ZGO-03-02-010 GPRS and EGPRS Channels Allocated Separately

10-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

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
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
The measurement is taken at three time points listed below: l l l When PDCH resource is acquired successfully, this counter calculates and accumulates. When PDCH resource is released, this counter calculates and accumulates. When reporting the measurement data periodically, this counter calculates and accumulates.

Unit
Second

Related Features
ZGO-03-02-010 GPRS and EGPRS Channels Allocated Separately

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.
10-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The measurement is taken at three time points listed below: l l l When PDCH resource is acquired successfully, this counter calculates and accumulates. When PDCH resource is released, this counter calculates and accumulates. When reporting the measurement data periodically, this counter calculates and accumulates.

Unit
Second

Related Features
ZGO-03-02-010 GPRS and EGPRS Channels Allocated Separately

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.

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 and Figure 10-2.

10-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

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

10-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. measurement point is A as shown in Figure 10-3.
Figure 10-3 Sending PS Paging By PCH Channel

The

Unit
Times

Related Features
ZGB-02-01-001 Paging

10.15 C901040020 Number of paging CS requests on PCH

Definition
Number of paging CS requests on PCH

Description
This counter counts the number of Paging CS message sent on PCH by BSC.

Usage
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. measurement point is A as shown in Figure 10-4.
10-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

The

Chapter 10 PS Resource Used Statistic Measurement

Figure 10-4 SENDING CS PAGING BY PCH CHANNEL

Unit
Times

Related Features
ZGB-02-01-001 Paging

10.16 C901040021 Number of immediate assignment on PCH

Definition
Number of immediate assignment on PCH

Description
This counter counts the number of Imm Assign message sent on PCH by BSC.

Usage
This counter is used to find out the frequency of sending Imm Assign message on PCH by BSC in the current cell.

Measurement Point
If BSC starts to establish DL TBF, when DRX MS sends Imm Assign message on PCH, the counter increments. The measurement point is A2, as shown in Figure 10-5.

10-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 10-5 Sending Instant Assignment Message By AGCH Channel

Unit
Times

10.17 C901040022 Number of immediate assignment 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 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-6and Figure 10-7.

10-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

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-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of sending Paging PS message on PPCH by BSC in the current cell.

Measurement Point
When BSC sends Paging PS message on PPCH, the counter increments. measurement point is A, as shown in Figure 10-8.
Figure 10-8 Sending PS Paging By PCH ChanneL

The

Unit
Times

Related Features
ZGB-02-01-001 Paging

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 by BSC in the current cell.

Measurement Point
When BSC sends Paging CS message on PPCH, the counter increments. measurement point is A, as shown in Figure 10-9.
10-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

The

Chapter 10 PS Resource Used Statistic Measurement

Figure 10-9 Sending CS Paging By PCH Channel

Unit
Times

Related Features
ZGB-02-01-001 Paging

10.20 C901040025 Number of immediate assignment 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 by BSC in the current cell.

Measurement Point
If BSC starts to establish DL TBF, when DRX MS sends Imm Assign message on PPCH, the counter increments. The measurement point is A2, as shown in Figure 10-10.

10-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

Unit
Times

10.22 C901040027 Sum of Abis TS Used Sampling

Description
This counter counts Abis resources that are used by a cell phone for services.

Usage
This counter calculates the sum of sampled Abis resources. It is a parameter reflecting the usage of Abis resources. l l For a site using the TDM access mode, this counter calculates the sum of sampled Abis timeslots. For a site using the IP access mode, this counter calculates the sum of sampled Abis bandwidth.

Measurement Point
When the database of the BSC starts to assign Abis resource, the counter accumulates.

Unit
Number of timeslots (TDM) or Kbps (IP)

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-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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, the counter accumulates.

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, the counter increments.

10-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

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 helps adjust the usage of Abis resource.
10-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when CS user requests for the Abis resource successfully or releases the Abis resource successfully.

Unit
Number of (TDM access)/kbps (IP access)

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
Number of (TDM access)/kbps (IP access)

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-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

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
Number of (TDM access)/kbps (IP access)

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 helps adjust the usage of Abis resource.

Measurement Point
The counter counts when PS user requests for the Abis resource successfully.

Unit
Number of (TDM access)/kbps (IP access)

10.31 C901040036 Minimum value of Abis TS used to PS

Definition
Minimum value of Abis TS used to PS

10-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 helps adjust the usage of Abis resource.

Measurement Point
The counter counts when PS user requests for the Abis resource successfully or releases the Abis resource successfully.

Unit
Number of (TDM access)/kbps (IP access)

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 releases the Abis resource successfully.

Unit
Number of (TDM access)/kbps (IP access)

10-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

10.33 C901040038 Number of sampling of PS

Definition
Number of sampling of PS

Description
The counter increments at the measurement point of C901040037. This counter and 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 releases the Abis resource successfully.

Unit
Number of (TDM access)/kbps (IP access)

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-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 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.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 value, then update the value.

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-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

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 value, then update the value.

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-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 the measurement period.

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-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

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 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.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 the measurement period.

Usage
This counter counts the number of assigned uplink radio channels in the cell and site within the measurement period.

Measurement Point
The counter counts in the four following cases. 1. 2. 3. 4. Counts Counts Counts Counts in in in in single allocated resource block allocated radio resource uplink DTM assignment downlink DTM assignment

Unit
Times

10-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 within the measurement period.

Measurement Point
The counter counts in the following three cases. 1. Counts in allocated radio resource 2. Counts in uplink DTM assignment 3. Counts in downlink DTM assignment

Unit
Times

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 within the measurement period.

Usage
This counter counts the number of requested uplink radio channels in the cell and site within the measurement period.

Measurement Point
Consistent with that for C901040047.

Unit
Times

10-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

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 within the measurement period.

Usage
This counter counts the number of requested downlink radio channels in the cell and site within the measurement period.

Measurement Point
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. This counter is supported in version V6.20.210a or above.

Measurement Point
The counter counts when the RANUMC module receives the EV_DBS_PSCHANEXPAND message.

Unit
Times

10.47 C901040052 Number of PS channel expand perform

Description
This counter counts the number of channel expansions in PS service.
10-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of channel expansions executed by RANPS. This counter is supported in version V6.20.210a or above.

Measurement Point
This counter counts when the EV_RANUMC_PSCHANEXPAND message. RANPS module receives the

Unit
Times

10.48 C901040053 Number of PS channel expand success

Description
This counter counts the number of successful channel expansions in PS service.

Usage
This counter is used to find out the number of successful channel expansions executed by RANPS. This counter is supported in version V6.20.210a or above.

Measurement Point
This counter counts when the RANPS module successfully requests the resource for expansion from database.

Unit
Times

10.49 C901040054 Total number of all TBF used uplink PDCH

Measured Object
Cell

Description
Total number of uplink PDCHs occupied by TBF
10-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

The number of uplink PDCHs occupied by TBF is recorded each time an uplink PDCH request or release event occurs.

Usage
This counter calculates the sum of sampled numbers of uplink PDCHs occupied by TBF, which is sampled each time an uplink PDCH is successfully requested for TBF or an uplink PDCH occupied by TBF is successfully released, to the previous sum.

Measurement Point
None

Unit
N/A

10.50 C901040055 Total number of all TBF used downlink PDCH

Measured Object
Cell

Description
Total number of downlink PDCHs occupied by TBF The number of downlink PDCHs occupied by TBF is recorded each time a downlink PDCH request or release event occurs.

Usage
This counter adds the number of downlink PDCHs occupied by TBF, which is recorded each time a downlink PDCH is successfully requested for TBF or a downlink PDCH occupied by TBF is successfully released, to the previous sum.

Measurement Point
None

Unit
N/A

10-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

10.51 C901040056 Sample number of all TBF used uplink PDCH

Measured Object
Cell

Description
Number of times that the number of uplink PDCHs occupied by TBF is sampled when an uplink PDCH request or release event occurs

Usage
This counter is incremented each time an uplink PDCH is successfully requested for TBF, or an uplink PDCH occupied by TBF is successfully released. That is, the sampling times is incremented within 15 minutes each time an uplink PDCHs request or release event occurs.

Measurement Point
None

Unit
N/A

10.52 C901040057 Sample number of all TBF used downlink PDCH

Measured Object
Cell

Description
Number of times that the number of downlink PDCHs occupied by TBF is sampled when a downlink PDCH request or release event occurs

Usage
This counter is incremented each time a downlink PDCH is successfully requested for TBF, or a downlink PDCH occupied by TBF is successfully released. That is, the sampling times is incremented within 15 minutes each time a downlink PDCHs request or release event occurs.

10-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

Measurement Point
None

Unit
N/A

10.53 C901040058 Average number used uplink PDCH

Measured Object
Cell

Description
Average number of uplink PDCHs used within 15 minutes

Usage
This counter calculates the average number of uplink PDCHs by dividing the sum of all sampled numbers of uplink PDCHs used within 15 minutes by the number of sampling times. If the number of sampling times within 15 minutes is 0, the average number of uplink PDCHs equals the total number of uplink PDCHs used within 15 minutes.

Measurement Point
None

Unit
N/A

10.54 C901040059 Average number used downlink PDCH

Measured Object
Cell

Description
Average number of downlink PDCHs used within 15 minutes

Usage
This counter calculates the average number of downlink PDCHs by dividing the sum of all sampled numbers of downlink PDCHs used within 15 minutes by the number of sampling
10-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

times. If the number of sampling times within 15 minutes is 0, the average number of downlink PDCHs equals the total number of downlink PDCHs used within 15 minutes.

Measurement Point
None

Unit
N/A

10.55 C901040060 Sum of uplink PDCH used sampling

Measured Object
Cell

Description
Sum of uplink PDCHs used within 15 minutes

Usage
The number of uplink PDCHs used in the cell is sampled each time an uplink PDCH is successfully requested or released. This counter adds the sampled number of uplink PDCHs to the previous sum.

Measurement Point
None

Unit
N/A

10.56 C901040061 Sum of downlink PDCH used sampling

Measured Object
Cell

Description
Sum of downlink PDCHs used within 15 minutes

10-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

Usage
The number of downlink PDCHs used in the cell is sampled each time a downlink PDCH is successfully requested or released. This counter adds the sampled number of uplink PDCHs to the previous sum.

Measurement Point
None

Unit
N/A

10.57 C901040062 Number of uplink PDCH used sampling

Measured Object
Cell

Description
Number of times that the number of uplink PDCHs is sampled when an uplink PDCH request or release event occurs

Usage
This counter is incremented each time an uplink PDCH is successfully requested or released.

Measurement Point
None

Unit
N/A

10.58 C901040063 Number of downlink PDCH used sampling

Measured Object
Cell

10-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
Number of times that the number of downlink PDCHs is sampled when a downlink PDCH request or release event occurs

Usage
This counter is incremented each time a downlink PDCH is successfully requested or released.

Measurement Point
None

Unit
N/A

10.59 C901040064 Average number of all TBF used total uplink PDCH
Measured Object
Cell

Description
Average number of uplink PDCHs used by TBF within 15 minutes

Usage
This counter calculates the average number of uplink PDCHs used by TBF by dividing the sum of all sampled numbers of uplink PDCHs used by TBF within 15 minutes by the number of sampling times. If the number of sampling times within 15 minutes is 0, the average number of uplink PDCHs used by TBF equals the total number of uplink PDCHs used by TBF within 15 minutes.

Measurement Point
None

Unit
N/A

10-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

10.60 C901040065 Average number of all TBF used total downlink PDCH
Measured Object
Cell

Description
Average number of downlink PDCHs used by TBF within 15 minutes

Usage
This counter calculates the average number of downlink PDCHs used by TBF by dividing the sum of all sampled numbers of downlink PDCHs used by TBF within 15 minutes by the number of sampling times. If the number of sampling times within 15 minutes is 0, the average number of downlink PDCHs used by TBF equals the total number of downlink PDCHs used by TBF within 15 minutes.

Measurement Point
None

Unit
N/A

10.61 C901040078 Time of PDCH Used at Least One UL/DL TBF Exists
Description
This counter counts the total occupation time of PDCHs, on which at least one uplink or downlink GPRS TBF is carried. The counter value is equal to the product of the number of GPRS occupied PDCHs and occupation time of each PDCH.

Usage
This counter indicates the total occupation time of PDCHs.

Measurement Point
This counter is updated each time the PsUmMeasure function is called upon channel allocation, release and refresh. The PmAgent calls the GetMeasChalDynaRutn function to report the counter value when the measurement period (15 minutes) is reached.

10-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Second

10.62 C901040079 Time of Configured EGPRS PDCH Used at Least One UL/DL EGPRS TBF Exists
Description
This counter counts the total occupation time of EGPRS dedicated channels, on which at least one uplink or downlink EGPRS TBF is carried. The counter value is equal to the product of the number of occupied EGPRS dedicated channels and occupation time of each channel.

Usage
This counter indicates the total occupation time of EGPRS dedicated channels.

Measurement Point
This counter is updated each time the PsUmMeasure function is called upon channel allocation, release and refresh. The PmAgent calls the GetMeasChalDynaRutn function to report the counter value when the measurement period (15 minutes) is reached.

Unit
Second

10.63 C901040080 Total number of all GPRS TBF used PDCH

Description
This counter counts all GPRS TBFs on the PDCH in a cell.

Usage
This counter indicates the total number of GPRS TBFs on the PDCH in a cell.

Measurement Point
This counter is updated each time the PsUmMeasure function is called due to channel allocation, release, or refresh.

Unit
None
10-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

10.64 C901040081 Sample number of all GPRS TBF used PDCH

Description
This counter counts the number of times that the number of GPRS TBFs on the PDCH is sampled in a cell.

Usage
This counter indicates the sampling times of the number of GPRS TBFs on the PDCH in a cell.

Measurement Point
This counter is incremented each time the PsUmMeasure function is called due to channel allocation, release, or refresh.

Unit
Times

10.65 C901040082 Average number of GPRS TBF used total PDCH

Description
This counter calculates the average number of GPRS TBFs on the PDCH in a cell. This counter fulfills the relation of C901040082=C901040080/C901040081 when the number of sampling times (C901040081) is not zero. If C901040081=0, the BSC obtains the PS_GETRESOURCEUSEINFO from the database. counter value by querying

Usage
This counter indicates the average number of GPRS TBFs on the PDCH in a cell.

Measurement Point
This counter is updated each time the PmAgent calls the GetMeasChalDynaRutn function when the reporting period (15 minutes) is reached.

Unit
None

10-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

10.66 C901040083 Total number of all EGPRS TBF used PDCH

Description
This counter counts all EGPRS TBFs on the PDCH in a cell.

Usage
This counter indicates the total number of EGPRS TBFs on the PDCH in a cell.

Measurement Point
This counter is updated each time the PsUmMeasure function is called due to channel allocation, release, or refresh.

Unit
None

10.67 C901040084 Sample number of all EGPRS TBF used PDCH

Description
This counter counts the number of times that the number of EGPRS TBFs on the PDCH is sampled in a cell.

Usage
This counter indicates the sampling times of the number of EGPRS TBFs on the PDCH in a cell.

Measurement Point
This counter is incremented each time the PsUmMeasure function is called due to channel allocation, release, or refresh.

Unit
Times

10-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

10.68 C901040085 Average number of EGPRS TBF used total PDCH

Description
This counter calculates the average number of EGPRS TBFs on the PDCH in a cell. This counter fulfills the relation of C901040085=C901040083/C901040084 when the number of sampling times (C901040084) is not zero. If C901040084=0, the BSC obtains the PS_GETRESOURCEUSEINFO from the database. counter value by querying

Usage
This counter indicates the average number of EGPRS TBFs on the PDCH in a cell.

Measurement Point
This counter is updated each time the PmAgent calls the GetMeasChalDynaRutn function when the reporting period (15 minutes) is reached.

Unit
None

10.69 C901040086 Total number of all EGPRS TBF used EGPRS only PDCH
Description
This counter counts all EGPRS TBFs on the dedicated EGPRS PDCH in a cell.

Usage
This counter indicates the total number of EGPRS TBFs on the dedicated EGRPS PDCH in a cell.

Measurement Point
This counter is updated each time the PsUmMeasure function is called due to channel allocation, release, or refresh.

Unit
None

10-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

10.70 C901040087 Sample number of all EGPRS TBF used EGPRS only PDCH
Description
This counter counts the number of times that the number of EGPRS TBFs on the dedicated EGPRS PDCH is sampled in a cell.

Usage
This counter indicates the sampling times of the number of EGPRS TBFs on the dedicated EGPRS PDCH in a cell.

Measurement Point
This counter is incremented each time the PsUmMeasure function is called due to channel allocation, release, or refresh.

Unit
Times

10.71 C901040088 Average number of EGPRS TBF used total EGPRS only PDCH
Description
This counter calculates the average number of EGPRS TBFs on the dedicated EGPRS PDCH in a cell. This counter fulfills the relation of C901040088=C901040086/C901040087 when the number of sampling times (C901040087) is not zero. If C901040087=0, the BSC obtains the PS_GETRESOURCEUSEINFO from the database. counter value by querying

Usage
This counter indicates the average number of EGPRS TBFs on the dedicated EGPRS PDCH in a cell.

Measurement Point
This counter is updated each time the PmAgent calls the GetMeasChalDynaRutn function when the reporting period (15 minutes) is reached.

Unit
None
10-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

10.72 C901040089 UL Request PDCH Times

Description
This counter counts the number of times that an uplink PDCH is requested for in a cell.

Usage
This counter indicates the number of times that an uplink PDCH is requested for in a cell.

Measurement Point
This counter counts channel requests with successful channel allocation from DbsGetSBRadioResrc, GetMeasMsChanNum, RanumcMacDLAssignDealer, and RanumcCsDtmAssignDealer, indicating the number of uplink PDCH requests.

Unit
Times

10.73 C901040090 UL Unsatisfied PDCH Times

Description
This counter counts the number of times that the number of allocated timeslots in uplink does not satisfy the channel request in a cell.

Usage
This counter indicates the number of times that the number of allocated timeslots in uplink does not satisfy the channel request in a cell.

Measurement Point
The counter dwULRequestPDCHTimes counts channel requests with successful channel allocation from DbsGetSBRadioResrc, GetMeasMsChanNum, RanumcMacDLAssignDealer, and RanumcCsDtmAssignDealer. The BSC compares dwULAssignedPDCHNum and dwULRequestPDCHNum. If dwULAssignedPDCHNum < dwULReqeustPDCHNum, this counter is incremented.

Unit
Times

10-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

10.74 C901040091 DL Request PDCH Times

Description
This counter counts the number of times that a downlink PDCH is requested for in a cell.

Usage
This counter indicates the number of times that a downlink PDCH is requested for in a cell.

Measurement Point
This counter counts channel requests with successful channel allocation from GetMeasMsChanNum, RanumcMacDLAssignDealer, and RanumcCsDtmAssignDealer, indicating the number of downlink PDCH requests.

Unit
Times

10.75 C901040092 DL Unsatisfied PDCH Times

Description
This counter counts the number of times that the number of allocated downlink channels does not satisfy the channel request in a cell.

Usage
This counter indicates the number of times that the number of allocated downlink channels does not satisfy the channel request in a cell.

Measurement Point
The counter dwDLRequestPDCHTimes counts channel requests with successful channel allocation from GetMeasMsChanNum, RanumcMacDLAssignDealer, and RanumcCsDtmAssignDealer. The BSC compares dwDLAssignedPDCHNum and dwDLRequestPDCHNum. If dwDLAssignedPDCHNum < dwDLRequestPDCHNum, this counter is incremented.

Unit
Times

10-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 10 PS Resource Used Statistic Measurement

10.76 C901040093 Average Number of PDCH Allocated Per UL TBF

Description
This counter indicates the average number of PDCHs allocated per uplink TBF. Allocated PDCHs are counted by TBF, meaning that this counter calculates the average number of allocated PDCHs upon each channel request.

Usage
This counter indicates the average number of PDCHs allocated per uplink TBF.

Measurement Point
This counter is updated upon a channel request.

Unit
None

10.77 C901040094 Sample Number of PDCH Allocated Per UL TBF

Description
This counter counts the number of times that the number of PDCHs allocated to an uplink TBF is sampled.

Usage
This counter indicates the number of times that the number of PDCHs allocated to an uplink TBF is sampled.

Measurement Point
This counter is updated upon a channel request.

Unit
None

10-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

10.78 C901040095 Average Number of PDCH Allocated Per DL TBF

Description
This counter indicates the average number of PDCHs allocated per downlink TBF. Allocated PDCHs are counted by TBF, meaning that this counter calculates the average number of allocated PDCHs upon each channel request.

Usage
This counter indicates the average number of PDCHs allocated per downlink TBF.

Measurement Point
This counter is updated upon a channel request.

Unit
None

10.79 C901040096 Sample Number of PDCH Allocated Per DL TBF

Description
This counter counts the number of times that the number of PDCHs allocated to a downlink TBF is sampled.

Usage
This counter indicates the number of times that the number of PDCHs allocated to a downlink TBF is sampled.

Measurement Point
This counter is updated upon a channel request.

Unit
Times

10-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11

RMM Assignment Measurement

Table of Contents
Overview ..................................................................................................................11-4 C901050001 Number of general assignment executions for voice channel...............11-4 C901050002 Number of assignments attempts for voice due to forced release ........11-5 C901050003 Number of assignment executions for voice channel due to forced release .....................................................................................................................11-6 C901050004 Number of handover attempts for voice due to forced release .............11-7 C901050005 Number of handover executions for voice channel due to forced release .....................................................................................................................11-8 C901050006 Number of assignments for voice channel due to queuing ................. 11-10 C901050007 Number of assignments for execution for voice channel due to queuing .................................................................................................................. 11-11 C901050008 Duration of assignment success voice channel due to queuing ......... 11-12 C901050009 Number of assignments success for voice channel due to queuing ... 11-13 C901050010 Number of assignments for directed retry attempts for voice channel . 11-14 C901050011 Number of assignments for execution for voice channel due to directed retry .......................................................................................................... 11-15 C901050012 Number of general assignments for execution for data ...................... 11-16 C901050013 Number of assignments attempts for data due to forced release ....... 11-17 C901050014 Number of assignment executions for data due to forced release ...... 11-18 C901050015 Number of handover attempts for data due to forced release ............ 11-19 C901050016 Number of handover executions for data due to forced release ......... 11-20 C901050017 Number of assignments attempts for data due to queuing ................. 11-21 C901050018 Number of assignments for execution for data due to queuing........... 11-23 C901050019 Total duration of successful assignments for data due to queuing...... 11-24 C901050020 Number of assignments success for data due to queuing .................. 11-25 C901050021 Number of assignments attempts for data due to directed retry ......... 11-25 C901050022 Number of assignment executions for data due to directed retry........ 11-27 C901050023 Number of assignment for retry attempts FDD cell for voice channel . 11-28 C901050024 Number of assignment executions for data due to directed retry to FDD cell for voice channel...................................................................................... 11-29 C901050025 Number of assignment for retry attempts FDD cell for data................ 11-30 C901050026 Number of assignment executions for data due to directed retry to FDD cell for data .................................................................................................... 11-31 C901050027 Number of assignment for retry attempts TDD cell for voice channel . 11-32
11-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901050028 Number of assignment executions for data due to directed retry to TDD cell for voice channel...................................................................................... 11-34 C901050029 Number of assignment for retry attempts TDD cell for data................ 11-35 C901050030 Number of assignment executions for data due to directed retry to TDD cell for data .................................................................................................... 11-36 C901050031 Assignment unsuccessful due to circuit obstruction ........................... 11-37 C901050032 Assignment unsuccessful due to circuit obstruction unmatched......... 11-38 C901050033 Assignment unsuccessful due to no valid radio resource ................... 11-39 C901050034 Assignment unsuccessful due to other causes .................................. 11-40 C901050035 Number of assignments attempts due to forced release (emergency service) .................................................................................................................. 11-41 C901050036 Number of assignment executions channel due to forced release (emergency service)............................................................................................... 11-42 C901050037 Number of assignment attempts due to forced handover (emergency service) .................................................................................................................. 11-43 C901050038 Number of assignment executions channel due to forced handover (emergency service)............................................................................................... 11-44 C901050039 Number of assignments channel due to queuing (emergency service) .................................................................................................................. 11-45 C901050040 Number of assignments for execution channel due to queuing (emergency service)............................................................................................... 11-46 C901050041 Number of forced handover target not found (assignment forced handover)............................................................................................................... 11-47 C901050042 Number of send forced handover request to lower PRI user (assignment forced handover) ................................................................................ 11-48 C901050043 Number of received failure from lower PRI user request resource for forced handover (assignment forced handover)...................................................... 11-50 C901050044 Number of lower PRI user handover failure (assignment forced handover)............................................................................................................... 11-51 C901050045 Number of time out for wait resource (assignment forced handover) . 11-52 C901050046 Number of forced release target not found (assignment forced release) .................................................................................................................. 11-53 C901050047 Number of time out for wait resource (assignment forced release)..... 11-54 C901050048 Number of get before grab released channel (assignment forced handover)............................................................................................................... 11-55 C901050049 Number of get before grab released channel(assignment forced release) .................................................................................................................. 11-56 C901050050 The count of Assignment using FULL IP A-Interface.......................... 11-57 C901050051 The count of Assignment using PCM over IP A-Interface................... 11-58 C901050052 The count of Assignment using PCM over TDM A-Interface ............. 11-59 C901050053 The count of Assignment Failure caused by "Requested Codec Type or Codec Configuration not supported" ................................................................... 11-60 C901050054 The count of Assignment Failure caused by "Requested Codec Type or Codec Configuration unavailable"....................................................................... 11-61

11-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

C901050055 The count of Assignment Failure caused by "Requested A-Interface Type not supported" ............................................................................................... 11-62 C901050056 The count of Assignment Failure caused by "Requested A-Interface Type unavailable" ................................................................................................... 11-63 C901050057 The count of Assignment Failure caused by "Call Identifier already allocated" ............................................................................................................... 11-64 C901050058 The count of Assignment Failure caused by "Requested Redundancy Level not supported"............................................................................................... 11-65 C901050059 The count of Assignment Failure caused by "Call Access Control" .... 11-66 C901050060 Attempt Number of mode modify for assignment ............................... 11-67 C901050061 Success Number of mode modify for assignment .............................. 11-68 C901050062 Number of assignments for directed retry attempts for voice channel because of radio..................................................................................................... 11-68 C901050063 Number of assignments for execution for voice channel due to directed retry because of radio ............................................................................... 11-69 C901050064 Number of assignments for directed retry attempts for data channel because of radio..................................................................................................... 11-70 C901050065 Number of assignments for execution for data channel due to directed retry because of radio............................................................................................. 11-71 C901050066 Number of assignment success for voice channel due to directed retry........................................................................................................................ 11-72 C901050067 Number of assignment success for data due to directed retry............ 11-74 C901050068 Number of assignment success for voice channel due to directed retry to FDD cell ..................................................................................................... 11-75 C901050069 Number of assignment success for data due to directed retry to FDD cell ......................................................................................................................... 11-76 C901050070 Number of assignment success for voice channel due to directed retry to TDD cell ..................................................................................................... 11-77 C901050071 Number of assignment success for data due to directed retry to TDD cell ......................................................................................................................... 11-78 C901050072 Number of assignments success for voice channel due to directed retry because of radio............................................................................................. 11-79 C901050073 Number of assignments success for data due to directed retry because of radio..................................................................................................... 11-80 C901050074 User/MSC Release Number During Voice TCH/F Assignment........... 11-82 C901050075 User/MSC Release Number During Data TCH/F Assignment ............ 11-82 C901050076 User/MSC Release Number During Voice TCH/H Assignment .......... 11-83 C901050077 User/MSC Release Number During Data TCH/H Assignment............ 11-83 C901050078 Number of Voice TCH/F Second Assignment Attempts ..................... 11-84 C901050079 Number of Voice TCH/F Second Assignment Success ...................... 11-84 C901050080 Number of Voice TCH/F Second Assignment Failure......................... 11-85 C901050081 Number of Data TCH/F Second Assignment Attempts....................... 11-85 C901050082 Number of Data TCH/F Second Assignment Success ....................... 11-86 C901050083 Number of Data TCH/F Second Assignment Failure.......................... 11-86 C901050084 Number of Voice TCH/H Second Assignment Attempts ..................... 11-87
11-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901050085 Number of Voice TCH/H Second Assignment Success...................... 11-87 C901050086 Number of Voice TCH/H Second Assignment Failure ........................ 11-88 C901050087 Number of Data TCH/H Second Assignment Attempts ...................... 11-88 C901050088 Number of Data TCH/H Second Assignment Success....................... 11-89 C901050089 Number of Data TCH/H Second Assignment Failure ......................... 11-89 C901050090 Number of Voice Assignment Failure for Directed Retry .................... 11-90 C901050091 Number of Data Assignment Failure for Directed Retry ..................... 11-90 C901050092 The Number of Forbid Sending Assignment Command During Releasing ............................................................................................................... 11-91 C901050093 Number of Reassignment Attempts ................................................... 11-91 C901050094 Number of Reassignment Success.................................................... 11-91 C901050095 Number of Reassignment Failure ...................................................... 11-92

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
11-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

successfully sends assignment command. The measurement point is A, as shown in Figure 11-1.
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.
11-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.

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.
11-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Measurement Point
The counter increments if radio resource request fails in voice channel assignment, forced released can be carried out and instance of forcing release sends forced release message to instance of forced release, and resource available message is received and channel is obtained successfully. The measurement point is B, as 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.

11-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of handover for forced release attempts for voice channel in MS accessing process.

Measurement Point
The counter increments when BSC fails in general voice channel assignment and the system allows forced release and there is proper instance of forcing release that sends forced release message to instance of forced release. The measurement point is A, as shown in Figure 11-4.
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

11-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Description
BSC attempts to operate outgoing handover to the cell voice channel for forced release when it fails in voice channel allocation due to no available resource. The counter counts the number of handover executions for voice channel due to forced release.

Usage
This counter is used to find out the number of handover executions for voice channel due to forced release in MS accessing process.

Measurement Point
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-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

11.7 C901050006 Number of assignments for voice channel due to queuing

Definition
Number of assignments for voice channel due to queuing

Description
BSC attempts to assign voice channel after receiving Radio App 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

11-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Related Features
ZGO-01-03-001 eMLPP

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
The counter increments 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 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

11-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-01-03-001 eMLPP

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

11-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Unit
Times

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
This counter is used to check the intra-cell queuing status and represents whether queuing can relieve traffic congestion effectively.

Measurement Point
The counter increments 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 point is B, as shown in Figure 11-9.
Figure 11-9 Measurement Point Of Assignments For Execution For Voice Channel Due To Queuing

Unit
Times
11-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. The measurement point is A, as shown in Figure 11-10.
Figure 11-10 Measurement Point of Assignments for Directed Retry Attempts

Unit
Times
11-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGB-03-01-002 Directed Retry ZGO-02-03-003 GERAN/UTRAN Load Sharing

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-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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. 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-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 11-13 Measurement Point Of Assignments For Forced Release Attempts

Unit
Times

Related Features
ZGO-01-03-001 eMLPP

11.15 C901050014 Number of assignment executions 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 to forced release in MS accessing process.

Measurement Point
The counter increments if radio resource request fails in data channel assignment, forced released can be carried out and instance of forcing release sends forced release
11-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter increments when BSC fails in general data channel assignment and the system allows forced release and there is proper instance of forcing release that sends forced release message to instance of forced release. The measurement point is A, as shown in Figure 11-15.
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-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Usage
This counter is used to find out the number of handover executions for data channel due to forced release in MS accessing process.

Measurement Point
The counter increments if radio resource request fails in data channel assignment, handover for data channel due to forced release can be carried out and instance of forcing handover sends forced handover message to instance of forced handover, and resource availablemessage is received and channel is obtained successfully. The measurement point is B, as shown in Figure 11-16.
Figure 11-16 Measurement Point Of Handover Executions For Voice Channel Due To Forced Release

Unit
Times

Related Features
ZGO-01-03-001 eMLPP

11.18 C901050017 Number of assignments attempts for data due to queuing

Definition
Number of assignments attempts for data due to queuing

11-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 11-17 Measurement Point Of Assignments For Queuing Attempts

Unit
Times

Related Features
ZGO-01-03-001 eMLPP

11-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

11.19 C901050018 Number of assignments for 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.
Figure 11-18 Measurement Point Of Assignments For Execution For Voice Channel Due To Queuing

Unit
Times

Related Features
ZGO-01-03-001 eMLPP

11-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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 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.
Figure 11-19 Measurement Point Of Assignments For Execution For Voice Channel Due To Queuing

Unit
Times
11-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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
This counter is used to check the intra-cell queuing status and represents whether queuing can relieve traffic congestion effectively.

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.
Figure 11-20 Measurement Point Of Assignments For Execution For Voice Channel Due To Queuing

Unit
Times

11.22 C901050021 Number of assignments attempts for data due to directed retry
Definition
Number of assignments attempts for data due to directed retry
11-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. The measurement point is A, as shown in Figure 11-21.
Figure 11-21 Measurement Point of Assignments for Directed Retry Attempts

Unit
Times

Related Features
ZGB-03-01-002 Directed Retry ZGO-02-03-003 GERAN/UTRAN Load Sharing

11-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

11.23 C901050022 Number of assignment executions 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
ZGB-03-01-002 Directed Retry
11-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ZGO-02-03-003 GERAN/UTRAN Load Sharing

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.
Figure 11-23 Measurement Point of Assignments for Directed Retry Attempts

Unit
Times
11-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Related Features
ZGB-03-01-002 Directed Retry ZGO-02-02-014 IMSI Based Handover ZGO-02-03-002 GSM/WCDMA Interworking ZGO-02-03-003 GERAN/UTRAN Load Sharing

11.25 C901050024 Number of assignment executions 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-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 11-24 Measurement Point of Assignments for Execution for Voice Channel due to Directed Retry

Unit
Times

Related Features
ZGB-03-01-002 Directed Retry ZGO-02-02-014 IMSI Based Handover ZGO-02-03-002 GSM/WCDMA Interworking ZGO-02-03-003 GERAN/UTRAN Load Sharing

11.26 C901050025 Number of assignment for retry 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-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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.
Figure 11-25 Measurement Point of Assignments for Directed Retry Attempts

Unit
Times

Related Features
ZGB-03-01-002 Directed Retry ZGO-02-02-014 IMSI Based Handover ZGO-02-03-002 GSM/WCDMA Interworking ZGO-02-03-003 GERAN/UTRAN Load Sharing

11.27 C901050026 Number of assignment executions 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-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of assignment executions due to directed retry to FDD cell for data channel and represent FDD cell directed retry status.

Measurement Point
The counter increments in data channel assignment when target cell in directed retry is FDD cell and successfully obtains channel and source cell receives radio resource available message from target cell. The measurement point is B, as shown in Figure 11-26.
Figure 11-26 Measurement Point of Assignments for Execution for Voice Channel due to Directed Retry

Unit
Times

Related Features
ZGB-03-01-002 Directed Retry ZGO-02-02-014 IMSI Based Handover ZGO-02-03-002 GSM/WCDMA Interworking ZGO-02-03-003 GERAN/UTRAN Load Sharing

11.28 C901050027 Number of assignment for retry attempts TDD cell for voice channel
Definition
Number of assignment for retry attempts TDD cell for voice channel
11-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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.
Figure 11-27 Measurement Point of Assignments for Directed Retry Attempts

Unit
Times

Related Features
ZGB-03-01-002 Directed Retry ZGO-02-02-014 IMSI Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing

11-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

11.29 C901050028 Number of assignment executions 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
This counter is used to find out the number of assignment executions due to directed retry to TDD cell for voice channel and represent TDD cell directed retry status.

Measurement Point
The counter increments in voice channel assignment when target cell in directed retry is TDD cell and successfully obtains channel and source cell receives radio resource available message from target cell. The measurement point is B, as shown in Figure 79.
Figure 11-28 Measurement Point of Assignments for Execution for Voice Channel due to Directed Retry

Unit
Times
11-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Related Features
ZGB-03-01-002 Directed Retry ZGO-02-02-014 IMSI Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing

11.30 C901050029 Number of assignment for retry 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.
Figure 11-29 Measurement Point of Assignments for Directed Retry Attempts

11-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGB-03-01-002 Directed Retry ZGO-02-02-014 IMSI Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing

11.31 C901050030 Number of assignment executions 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
This counter is used to find out the number of assignment executions due to directed retry to TDD cell for data channel and represent TDD cell directed retry status.

Measurement Point
The counter increments in data channel assignment when target cell in directed retry is TDD cell and successfully obtains channel and source cell receives radio resource available message from target cell. The measurement point is B, as shown in Figure 11-30.

11-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Figure 11-30 Measurement Point of Assignments for Execution for Voice Channel due to Directed Retry

Unit
Times

Related Features
ZGB-03-01-002 Directed Retry ZGO-02-02-014 IMSI Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing

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-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

11.33 C901050032 Assignment unsuccessful due to circuit obstruction unmatched

Definition
Assignment unsuccessful due to circuit obstruction unmatched

Description
This counter counts the number of assignment failure due to circuit unmatched on A-interface.

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-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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.
Figure 11-32 Measurement Point of Assignment Failure due to Circuit Obstruction on A-Interface

Unit
Times

11.34 C901050033 Assignment unsuccessful due to no valid radio resource

Definition
Assignment unsuccessful due to no valid radio resource

Description
This counter counts the number assignment failure due to no valid radio resource.

Usage
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-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

Figure 11-33 Measurement Point of Assignment Failure due to Circuit Obstruction on A-Interface

Unit
Times

11.35 C901050034 Assignment unsuccessful due to other causes

Definition
Assignment unsuccessful due to other causes

Description
This counter counts the number assignment failure due to other causes on A-interface.

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-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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.
Figure 11-34 Measurement Point of Assignment Failure due to Circuit Obstruction on A-Interface

Unit
Times

11.36 C901050035 Number of assignments attempts due to forced release (emergency service)
Definition
Number of assignment attempts due to forced release (emergency service)

Description
In the assignment flow, after BSC receives the RADIO_APPLY message, it attempts to assign the voice channel. If there is no suitable channel and forced release is allowed, then it releases other channels forcibly, if this call is an emergency call, then this counter counts the number of forced release attempts.

11-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of assignment attempts due to forced release during the MS access process of an emergency call.

Measurement Point
BSC fails to assign channel due to no available resource, if forced release is allowed, BSC will forcibly release other channels. During an emergency call, BSC fails to assign voice channel. If forced release is allowed and there is suitable forced release instance, then the counter increments when the forcing release instance sends the forced release message to the forced release instance. The measurement point is A, as shown in Figure 11-35.
Figure 11-35 Measurement Point Of Number Of Assignment Attempts Due To Forced Release (Emergency Service)

Unit
Times

11.37 C901050036 Number of assignment executions channel due to forced release (emergency service)
Definition
Number of assignment executions channel due to forced release (emergency service)

Description
BSC fails to assign voice channel due to no available resource, if it obtains needed channel within specified time after the forced release is performed, then the forced release
11-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

is considered successful. If the call is an emergency call, the counter counts the number of successful forced releases (emergency service).

Usage
This counter is used to find out the number of successful assignments due to forced release during the MS access process of an emergency call.

Measurement Point
During the voice channel assignment process, if the radio resource request fails and forced release is allowed, the forcing release instance sends the forced release message to the forced release instance. If the message of resource available is received, then the resource is obtained successfully, and in this case, the counter increments. The measurement point is B, as shown in Figure 11-36.
Figure 11-36 Measurement Point Of Number Of Assignment Attempts Due To Forced Release (Emergency Service)

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-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 during the MS access process of an emergency call.

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.
Figure 11-37 Measurement Point of Handover for Forced Release Attempts

Unit
Times

11.39 C901050038 Number of assignment executions channel due to forced handover (emergency service)
Definition
Number of assignment executions channel due to forced handover(emergency service)
11-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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 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.
Figure 11-38 Measurement Point Of Handover Executions For Voice Channel Due 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-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
In the assignment flow, after BSC receives the RADIO_APPLY message, it attempts to assign the voice channel. If there is no suitable channel and queuing is allowed, then the instance enters the queuing state and waits for other resource to be released, if this call is an emergency call, then this counter counts the number of queuing attempts (emergency service).

Usage
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 is A, as shown in Figure 11-39.
Figure 11-39 Measurement Point Of Assignments For Queuing Attempts

Unit
Times

11.41 C901050040 Number of assignments for execution channel due to queuing (emergency service)
Definition
Number of assignments for execution channel due to queuing (emergency service)
11-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Description
During an emergency call, BSC fails to assign voice channel due to no available resource but obtains needed channel within specified time after the queuing is performed (no forced handover or forced release is performed). In this case, the queuing is considered successful, the counter counts the number of successful assignments due to queuing (emergency service).

Usage
This counter is used to find out the number of successful assignments due to queuing during the MS access process of an emergency call.

Measurement Point
During the voice channel assignment process, if the radio resource request fails and queuing is allowed, the counter increments when the queuing instance receives the message of resource available and obtains resource successfully. The measurement point is B, as shown in Figure 11-40.
Figure 11-40 Measurement Point Of Assignments For Execution For Voice Channel 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-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
When BSC fails to assign voice channel due to no available resource, it attempts forced handover towards external cell. If no forcing handover instance is found in the cell, the counter counts the number of times that forcing handover target instance is not found.

Usage
During forced handover for voice channel assignment, this counter is used to find out the number of times that forced handover target instance is not found.

Measurement Point
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. The measurement point is A, as shown in Figure 11-41.
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-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Description
When BSC fails to assign voice channel due to no available resource, it attempts forced handover towards external cell. If forced handover target instance is found in the cell, the counter counts the number of forced handover requests sent to low priority users during the force handover.

Usage
During the voice channel assignment of MS access process, this counter is used to find out the number of forced handover requests when the forcing handover instance is found.

Measurement Point
When BSC fails to assign voice channel, if forced handover is allowed and there is suitable forcing handover instance, then the counter increments when the forcing handover instance sends the forced handover message to the forced handover instance. The measurement point is A, as shown in Figure 11-42.
Figure 11-42 Measurement Point of Handover for Forced Release Attempts

Unit
Times

11-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
When BSC fails to assign voice channel due to no available resource, it attempts forced handover towards external cell. If forcing handover target instance is found in the cell, the forced handover is initiated. Then, if the forced handover fails due to resource request failure, the counter counts the number of receiving resource request failure message from low priority user during the forced handover.

Usage
During the forced handover for voice channel assignment in MS access process, this counter is used to find out the number of receiving the forced handover failure message due to resource request failure.

Measurement Point
When BSC fails to assign voice channel, if forced handover is allowed and there is suitable forcing handover instance, then the 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-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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
When BSC fails to assign voice channel due to no available resource, it attempts forced handover towards external cell. If forcing handover target instance is found in the cell, the forced handover is initiated. Then, if the forced handover fails due to handover execution failure, the counter counts the number of receiving handover execution failure message from low priority user during the forced handover.

Usage
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 handover execution failure.

Measurement Point
When BSC fails to assign voice channel, if forced handover is allowed and there is suitable forced handover target instance, then the counter increments in the following case: the forcing handover instance sends the forced handover message to the forced handover
11-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
When BSC fails to assign voice channel due to no available resource, it attempts forced handover towards external cell. If forced handover target instance is found in the cell, the forced handover is initiated, and when the waiting for forced handover target instance resource is timeout, the counter counts the number of timeout due to waiting for resource during the forced handover.

Usage
During the forced handover for voice channel assignment in MS access process, this counter is used to find out the number of timeout due to waiting for forced handover target instance resource.

11-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Measurement Point
When BSC fails to assign voice channel, if forced handover is allowed and there is suitable forced handover target instance, then the counter increments when the waiting for forced handover target instance resource is timeout. The measurement point is B, as 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
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 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-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A, as shown in Figure 11-46.
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
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. 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-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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
When BSC fails to assign voice channel due to no available resource, it attempts forced 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
During the forced handover for voice channel assignment in MS access process, this counter is used to find out the number of preempting the released channel.
11-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 11-48 Measurement Point Of Handover Executions For Voice Channel Due To Forced Release

Unit
Times

11.50 C901050049 Number of get before grab released 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-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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-49.
Figure 11-49 Measurement Point Of Number Of Assignment Attempts Due To Forced Release (Emergency Service)

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 measurement point is A, as shown in Figure 11-50.

11-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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 PCMoIP transmission, the counter increments. The measurement point is A, as shown in Figure 11-51.

11-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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
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 TDM transmission, the counter increments. The measurement point is A, as shown in Figure 11-52.

11-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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 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-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Figure 11-53 Measurement Point of the Count of Assignment Failure Caused by "Requested Codec Type or Codec Configuration not supported"

Unit
Times

11.55 C901050054 The count of Assignment Failure caused by "Requested Codec Type or Codec Configuration unavailable"
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 the voice version according to the field Codec List (MSC Preferred) in the assignment request. According to the voice coding type or combination in the field Codec List (MSC Preferred), if it fails to request corresponding radio channel (i.e. the radio channel type available in the current cell is not consistent with the requested channel type), then the assignment failure message is sent to MSC, and the counter increments. The measurement point is B, as shown in Figure 11-54.

11-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 11-54 Measurement Point of the Count of Assignment Failure Caused by "Requested Codec Type or Codec Configuration unavailable"

Unit
Times

11.56 C901050055 The count of Assignment Failure caused by "Requested A-Interface Type not supported"
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 voice version as well as A-interface transmission mode according to the field Codec List (MSC Preferred) in the assignment request. In the field Codec List (MSC Preferred), if the A-interface transmission mode is not consistent with that supported by BSC, then the assignment failure message is sent to MSC, and the counter increments. The measurement point is A, as shown in Figure 11-55.

11-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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
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 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-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 11-56 Measurement Point of the Count of Assignment Failure Caused by "Requested A-Interface Type unavailable"

Unit
Times

11.58 C901050057 The count of Assignment Failure caused by "Call Identifier already allocated"
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 voice version as well as A-interface transmission mode according to the field Codec List (MSC Preferred) in the assignment request. If the system uses all-IP A-interface transmission, it is necessary to check whether there are any same Call IDs of IP calls. If there are, then the assignment failure message is sent to MSC, and the counter increments. The measurement point is A, as shown in Figure 11-57.

11-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Figure 11-57 Measurement Point of the Count of Assignment Failure Caused by "Call Identifier already allocated"

Unit
Times

11.59 C901050058 The count of Assignment Failure caused by "Requested Redundancy Level not supported"
Statistics object
CELL

Description
On the premise that the 3GPP IPA function is implemented, when MSC's assignment request, which is of data type or fax service type, is received, the system selects voice version as well as transmission redundancy mode according to the field Codec List (MSC Preferred) in the assignment request. If the transmission redundancy mode is not supported by BSC, then the assignment failure message is sent to MSC, and the counter increments. The measurement point is A, as shown in Figure 11-58.

11-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 11-58 Measurement Point of the Count of Assignment Failure Caused by "Requested Redundancy Level not supported"

Unit
Times

11.60 C901050059 The count of Assignment Failure caused by "Call Access Control"
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 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-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

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-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.63 C901050062 Number of assignments for directed retry attempts for voice channel because of radio
Description
When BSC receives the voice channel assignment request from MSC, if it finds out a better cell according to the measurement report on SDCCH and directed retry due to radio cause is allowed, it attempts to assign TCH of other cells. This counter counts the number of attempts of directed retry due to radio causes. This counter counts the number of attempts of directed retry due to radio causes. It is used to study radio signal condition in the cell. During the voice channel assignment, if the source cell supports directed retry due to radio cause and if the source cell finds out a better cell according to the measurement report on SDCCH, it sends the Radio_App message to the destination cell, and the counter increments. The measurement point is A, as shown in Figure 11-60.

11-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Figure 11-60 Measurement Point of Number of Directed Retries due to Radio Causes

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

11.64 C901050063 Number of assignments for execution for voice channel due to directed retry because of radio
Description
This counter counts the number of executions of directed retry due to radio causes. This counter is used to study the process and the result of directed retry due to radio cause. During the voice channel assignment, if directed retry occurs due to radio cause and if the destination cell successfully requests the channel, then the counter increments when the source cell receives the message of radio resource available from the destination cell. The measurement point is B, as shown in Figure 11-61.

11-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 11-61 Number of Assignment Executions due to Directed Retry

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

11.65 C901050064 Number of assignments for directed retry attempts for data channel because of radio
Description
When BSC receives the data channel assignment request from MSC, if it finds out a better cell according to the measurement report on SDCCH and directed retry due to radio cause is allowed, it attempts to assign TCH of other cells. This counter counts the number of attempts of directed retry due to radio causes. This counter counts the number of attempts of directed retry due to radio causes. It is used to study radio signal condition in the cell. During the voice channel assignment, if the source cell supports directed retry due to radio cause and if the source cell finds out a better cell according to the measurement report on SDCCH, it sends the Radio_App message to the destination cell, and the counter increments. The measurement point is A, as shown in Figure 11-62.

11-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Figure 11-62 Measurement Point of Number of Directed Retries due to Radio Causes

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

11.66 C901050065 Number of assignments for execution for data channel due to directed retry because of radio
Description
This counter counts the number of executions of directed retry due to radio causes. This counter is used to study the process and the result of directed retry due to radio cause. During the data channel assignment, if directed retry occurs due to radio cause and if the destination cell successfully requests the channel, then the counter increments when the source cell receives the message of radio resource available from the destination cell. The measurement point is B, as shown in Figure 11-63.

11-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 11-63 Number of Assignment Executions due to Directed Retry

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

11.67 C901050066 Number of assignment success for voice channel due to directed retry
Measured Object
Cell

Description
Number of assignment successes (speech channel) after directed retry due to non-radio reasons

Usage
This counter reflects the results of directed retries that are initiated due to non-radio reasons.

Measurement Point
This counter is incremented each time the MS is handed over to the target cell after successful channel request of the target cell when a directed retry occurs due to non-radio
11-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

reasons during the assignment of speech channel. The measurement point is C, as shown in Figure 11-64 and Figure 11-65.
Figure 11-64 Directed Retry Procedure

Figure 11-65 External Directed Retry Procedure

Unit
Times

11-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

11.68 C901050067 Number of assignment success for data due to directed retry
Measured Object
Cell

Description
Number of assignment successes (data channel) after directed retry due to non-radio reasons

Usage
This counter reflects the results of directed retries that are initiated due to non-radio reasons.

Measurement Point
This counter is incremented each time the MS is handed over to the target cell after successful channel request of the target cell when a directed retry occurs due to non-radio reasons during the assignment of speech channel. The measurement point is C, as shown in Figure 11-66 and Figure 11-67.
Figure 11-66 Directed Retry Procedure

11-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Figure 11-67 External Directed Retry Procedure

Unit
Times

11.69 C901050068 Number of assignment success for voice channel due to directed retry to FDD cell
Measured Object
Cell

Description
Number of assignment successes (speech channel) after directed retry due to non-radio reasons

Usage
This counter reflects the results of directed retries that are initiated due to non-radio reasons.

Measurement Point
This counter is incremented each time the MS is handed over to the target cell after successful channel request of the target cell when a directed retry to an FDD cell occurs due to non-radio reasons during the assignment of speech channel. The measurement point is C, as shown in Figure 11-68.

11-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 11-68 External Directed Retry Procedure

Unit
Times

11.70 C901050069 Number of assignment success for data due to directed retry to FDD cell
Measured Object
Cell

Description
Number of assignment successes (data channel) after directed retry due to non-radio reasons

Usage
This counter reflects the results of directed retries that are initiated due to non-radio reasons.

Measurement Point
This counter is incremented each time the MS is handed over to the target cell after successful channel request of the target cell when a directed retry to an FDD cell occurs due to non-radio reasons during the assignment of speech channel. The measurement point is C, as shown in Figure 11-69.

11-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Figure 11-69 External Directed Retry Procedure

Unit
Times

11.71 C901050070 Number of assignment success for voice channel due to directed retry to TDD cell
Measured Object
Cell

Description
Number of assignment successes (speech channel) after directed retry due to non-radio reasons

Usage
This counter reflects the results of directed retries that are initiated due to non-radio reasons.

Measurement Point
This counter is incremented each time the MS is handed over to the target cell after successful channel request of the target cell when a directed retry to a TDD cell occurs due to non-radio reasons during the assignment of speech channel. The measurement point is C, as shown in Figure 11-70.

11-77 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 11-70 External Directed Retry Procedure

Unit
Times

11.72 C901050071 Number of assignment success for data due to directed retry to TDD cell
Measured Object
Cell

Description
Number of assignment successes (data channel) after directed retry due to non-radio reasons

Usage
This counter reflects the results of directed retries that are initiated due to non-radio reasons.

Measurement Point
This counter is incremented each time the MS is handed over to the target cell after successful channel request of the target cell when a directed retry to a TDD cell occurs due to non-radio reasons during the assignment of speech channel. The measurement point is C, as shown in Figure 11-71.

11-78 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Figure 11-71 External Directed Retry Procedure

Unit
Times

11.73 C901050072 Number of assignments success for voice channel due to directed retry because of radio
Measured Object
Cell

Description
Number of assignment successes (speech channel) after directed retry due to radio reasons

Usage
This counter reflects the results of directed retries that are initiated due to radio reasons.

Measurement Point
This counter is incremented each time the MS is handed over to the target cell after successful channel request of the target cell when a directed retry occurs due to radio reasons during the assignment of speech channel. The measurement point is C, as shown in Figure 11-72 and Figure 11-73.

11-79 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 11-72 Directed Retry Procedure

Figure 11-73 External Directed Retry Procedure

Unit
Times

11.74 C901050073 Number of assignments success for data due to directed retry because of radio
Measured Object
Cell

11-80 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Description
Number of assignment successes (data channel) after directed retry due to radio reasons

Usage
This counter reflects the results of directed retries that are initiated due to radio reasons.

Measurement Point
This counter is incremented each time the MS is handed over to the target cell after successful channel request of the target cell when a directed retry occurs due to radio reasons during the assignment of speech channel. The measurement point is C, as shown in Figure 11-74 and Figure 11-75.
Figure 11-74 Directed Retry Procedure

Figure 11-75 External Directed Retry Procedure

11-81 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

11.75 C901050074 User/MSC Release Number During Voice TCH/F Assignment

Description
This counter counts the number of releases due to call control by the user or the MSC during voice TCH/F assignment.

Usage
This counter indicates the number of releases due to call control by the user or the MSC during voice TCH/F assignment.

Measurement Point
This counter is incremented each time the BSC, after sending an assignment command, receives a clear command with the cause of call control instead of an assignment complete message during a voice TCH/F assignment procedure.

Unit
Times

11.76 C901050075 User/MSC Release Number During Data TCH/F Assignment

Description
This counter counts the number of releases due to call control by the user or the MSC during data TCH/F assignment.

Usage
This counter indicates the number of releases due to call control by the user or the MSC during data TCH/F assignment.

Measurement Point
This counter is incremented each time the BSC, after sending an assignment command, receives a clear command with the cause of call control instead of an assignment complete message during a data TCH/F assignment procedure.

11-82 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

Unit
Times

11.77 C901050076 User/MSC Release Number During Voice TCH/H Assignment

Description
This counter counts the number of releases due to call control by the user or the MSC during voice TCH/H assignment.

Usage
This counter indicates the number of releases due to call control by the user or the MSC during voice TCH/H assignment.

Measurement Point
This counter is incremented each time the BSC, after sending an assignment command, receives a clear command with the cause of call control instead of an assignment complete message during a voice TCH/H assignment procedure.

Unit
Times

11.78 C901050077 User/MSC Release Number During Data TCH/H Assignment

Description
This counter counts the number of releases due to call control by the user or the MSC during data TCH/H assignment.

Usage
This counter indicates the number of releases due to call control by the user or the MSC during data TCH/H assignment.

Measurement Point
This counter is incremented each time the BSC, after sending an assignment command, receives a clear command with the cause of call control instead of an assignment complete message during a data TCH/H assignment procedure.

11-83 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

11.79 C901050078 Number of Voice TCH/F Second Assignment Attempts

Description
This counter counts additional voice TCH/F assignment attempts.

Usage
This counter indicates the number of times that an attempt occurs for additional voice TCH/F assignment.

Measurement Point
The BSC increases the corresponding flag by one upon receiving an assignment success or failure message. This counter is incremented each time the BSC detects that the flag is greater than one.

Unit
Times

11.80 C901050079 Number of Voice TCH/F Second Assignment Success

Description
This counter counts successful additional voice TCH/F assignments.

Usage
This counter indicates the number of times that additional voice TCH/F assignment succeeds.

Measurement Point
The BSC increases the corresponding flag by one upon receiving an assignment success message. This counter is incremented each time the BSC detects that the flag is greater than one.

Unit
Times
11-84 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

11.81 C901050080 Number of Voice TCH/F Second Assignment Failure

Description
This counter counts failed additional voice TCH/F assignments.

Usage
This counter indicates the number of times that additional voice TCH/F assignment fails.

Measurement Point
The BSC increases the corresponding flag by one when an assignment failure message is received or the timer expires. This counter is incremented each time the BSC detects that the flag is greater than one.

Unit
Times

11.82 C901050081 Number of Data TCH/F Second Assignment Attempts

Description
This counter counts additional data TCH/F assignment attempts.

Usage
This counter indicates the number of times that an attempt occurs for additional data TCH/F assignment.

Measurement Point
The BSC increases the corresponding flag by one upon receiving an assignment success or failure message. This counter is incremented each time the BSC detects that the flag is greater than one.

Unit
Times

11-85 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

11.83 C901050082 Number of Data TCH/F Second Assignment Success

Description
This counter counts successful additional data TCH/F assignments.

Usage
This counter indicates the number of times that additional data TCH/F assignment succeeds.

Measurement Point
The BSC increases the corresponding flag by one upon receiving an assignment success message. This counter is incremented each time the BSC detects that the flag is greater than one.

Unit
Times

11.84 C901050083 Number of Data TCH/F Second Assignment Failure

Description
This counter counts failed additional data TCH/F assignments.

Usage
This counter indicates the number of times that additional data TCH/F assignment fails.

Measurement Point
The BSC increases the corresponding flag by one when an assignment failure message is received or the timer expires. This counter is incremented each time the BSC detects that the flag is greater than one.

Unit
Times

11-86 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

11.85 C901050084 Number of Voice TCH/H Second Assignment Attempts

Description
This counter counts additional voice TCH/H assignment attempts.

Usage
This counter indicates the number of times that an attempt occurs for additional voice TCH/H assignment.

Measurement Point
The BSC increases the corresponding flag by one upon receiving an assignment success or failure message. This counter is incremented each time the BSC detects that the flag is greater than one.

Unit
Times

11.86 C901050085 Number of Voice TCH/H Second Assignment Success

Description
This counter counts successful additional voice TCH/H assignments.

Usage
This counter indicates the number of times that additional voice TCH/H assignment succeeds.

Measurement Point
The BSC increases the corresponding flag by one upon receiving an assignment success message. This counter is incremented each time the BSC detects that the flag is greater than one.

Unit
Times

11-87 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

11.87 C901050086 Number of Voice TCH/H Second Assignment Failure

Description
This counter counts failed additional voice TCH/H assignments.

Usage
This counter indicates the number of times that additional voice TCH/H assignment fails.

Measurement Point
The BSC increases the corresponding flag by one when an assignment failure message is received or the timer expires. This counter is incremented each time the BSC detects that the flag is greater than one.

Unit
Times

11.88 C901050087 Number of Data TCH/H Second Assignment Attempts

Description
This counter counts additional data TCH/H assignment attempts.

Usage
This counter indicates the number of times that an attempt occurs for additional data TCH/H assignment.

Measurement Point
The BSC increases the corresponding flag by one upon receiving an assignment success or failure message. This counter is incremented each time the BSC detects that the flag is greater than one.

Unit
Times

11-88 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

11.89 C901050088 Number of Data TCH/H Second Assignment Success

Description
This counter counts successful additional data TCH/H assignments.

Usage
This counter indicates the number of times that additional data TCH/H assignment succeeds.

Measurement Point
The BSC increases the corresponding flag by one upon receiving an assignment success message. This counter is incremented each time the BSC detects that the flag is greater than one.

Unit
Times

11.90 C901050089 Number of Data TCH/H Second Assignment Failure

Description
This counter counts failed additional data TCH/H assignments.

Usage
This counter indicates the number of times that additional data TCH/H assignment fails.

Measurement Point
The BSC increases the corresponding flag by one upon receiving an assignment success message. This counter is incremented each time the BSC detects that the flag is greater than one.

Unit
Times

11-89 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

11.91 C901050090 Number of Voice Assignment Failure for Directed Retry

Description
This counter counts the number of times that an assignment for voice traffic fails due to directed retry failure. Assignment failures are counted after a directed retry failure. The original cell may attempt a directed retry to multiple cells after a directed retry fails.

Usage
This counter indicates the number of times that an assignment for voice traffic fails due to directed retry failure.

Measurement Point
This counter is incremented each time a failure occurs during a directed retry to a voice traffic channel and an additional assignment is attempted.

Unit
Times

11.92 C901050091 Number of Data Assignment Failure for Directed Retry

Description
This counter counts the number of times that an assignment for data traffic fails due to directed retry failure. Assignment failures are counted after a directed retry failure. The original cell may attempt a directed retry to multiple cells after a directed retry fails.

Usage
This counter indicates the number of times that an assignment for data traffic fails due to directed retry failure.

Measurement Point
This counter is incremented each time a failure occurs during a directed retry to a data traffic channel and an additional assignment is attempted.

Unit
Times

11-90 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 11 RMM Assignment Measurement

11.93 C901050092 The Number of Forbid Sending Assignment Command During Releasing
Description
This counter counts the number of times that the BSC is forbidden to send an assignment command during a release process.

Measurement Point
l This counter is incremented each time the BSC, after receiving an Assignment Request message from the A interface, cancels sending an assignment command when detecting an ongoing release process. This counter is incremented each time the BSC, after receiving an internal resource available message, cancels sending an assignment command to the Um interface when detecting an ongoing release process.

Unit
Number of times

11.94 C901050093 Number of Reassignment Attempts

Description
This counter counts the number of times that the BSC makes a reassignment attempt after receiving an assignment failure message.

Measurement Point
This counter is incremented each time the BSC initiates a reassignment process after receiving an assignment failure message from an MS.

Unit
Number of times

11.95 C901050094 Number of Reassignment Success

Description
This counter counts the number of times that the BSS successfully completes a reassignment process after receiving an assignment failure message.

11-91 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
l l This counter is incremented each time the BSC, after initiating a reassignment process in the serving cell, receives an assignment complete message. This counter is incremented each time the BSC, after initiating a directed retry handover due to reassignment, receives a handover complete message.

Unit
Number of times

11.96 C901050095 Number of Reassignment Failure

Description
This counter counts the number of times that the BSS fails to complete a reassignment process after receiving an assignment failure message.

Measurement Point
l l This counter is incremented each time T3107 expires after the BSC initiates a reassignment process in the serving cell. This counter is incremented each time T3103 expires after the BSC initiates a directed retry due to reassignment.

Unit
Number of times

11-92 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 C901060082 Attempts of handover on TCH/F caused by power adjustment...........12-63 C901060083 Attempts of handover on TCH/H caused by power adjustment ..........12-64 C901060084 Attempts of handover on TCH/F caused by local switch ....................12-65
12-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

C901060085 Attempts of handover on TCH/H caused by local switch ....................12-65 C901060086 Attempts of handover on TCH/F caused by reducing band resources of IPAbis.................................................................................................................12-65 C901060087 Attempts of handover on TCH/H because of MASTERPWR_ALM from TRX................................................................................................................12-66 C901060088 Attempts of handover on TCH/F because of MASTERPWR_ALM from TRX................................................................................................................12-67 C901060089 Number of handover attempts due to directed retry for PBGT............12-67 C901060090 Number of SDCCH handover attempts due to DL quality rapid drop..12-68 C901060091 Number of TCH/F handover attempts due to DL quality rapid drop ....12-69 C901060092 Number of TCH/H handover attempts due to DL quality rapid drop....12-70 C901060095 Number of TCH/F Handover Attempts Due to Dynamic Channel Move ......................................................................................................................12-70 C901060096 Number of TCH/H Handover Attempts Due to Dynamic Channel Move ......................................................................................................................12-71 C901060100 Number of MSC-Controlled Outgoing Handover Attempts Due to PBGT .....................................................................................................................12-72 C901060101 Number of MSC-Controlled Incoming Handover Attempts Due to PBGT .....................................................................................................................12-72 C901060102 Number of Inter BSC Incoming Handover Attempts Due to Large TA .12-73 C901060103 Number of Inner BSC Incoming Handover Attempts Due to Large TA ..........................................................................................................................12-73 C901060104 Number of Dual Frequency Traffic Handover Attempts on TCH/F ......12-74 C901060105 Number of Dual Frequence Traffic Handover Attempts on TCH/H .....12-74

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. The measurement takes cell as the statistics unit.

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
12-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

retry, which is a kind of handover. This counter counts the number of handover attempts due to direct retry.

Usage
This counter is used to find out MS access process and to check cell channel utilizing status. If the statistic number counted by the counter is relative high, then it means the cell does not have enough radio resource and capacity expansion shall be taken into account.

Measurement Point
In assignment process, the counter increments if source instance receives message that no available radio resource replied by target instance, then it chooses cell list successfully and try to attempt cells in the list. This counter is handover cause counter and used for finding out cell channel congestion status, so the counter only counts in the initial judgment. The measurement point is A, as shown in Figure 12-1.
Figure 12-1 Directed Retry Judgment

Unit
Times

Related Features
ZGB-03-01-002 Directed Retry ZGO-02-03-003 GERAN/UTRAN Load Sharing

12.3 C901060002 Number of SDCCH handover attempts due to UL received strength

Definition
Number of SDCCH handover attempts due to UL received strength

12-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Description
This counter counts the number of handover attempts due to too low uplink received strength (on SDCCH).

Usage
This counter is used to find out frequency of handover attempts due to uplink received strength (on SDCCH); high number means SDCCH uplink signal strength is low.

Measurement Point
BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is yes and handover cause is uplink signal strength. The measurement point is A, as shown in Figure 12-2.
Figure 12-2 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

12.4 C901060003 Number of SDCCH handover attempts 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).

12-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
BSC carries out handover judgment after receiving SDDCH measurement report; the 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.
Figure 12-3 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

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.

12-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

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 quality. The measurement point is A, as shown in Figure 12-4.
Figure 12-4 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

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
BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is yes and handover cause is downlink quality. The measurement point is A, as shown in Figure 12-5.

12-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 12-5 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

12.7 C901060006 Number of SDCCH handover attempts due to UL interference

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
BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is yes and handover cause is uplink interference. The measurement point is A, as shown in Figure 12-6.

12-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Figure 12-6 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

12.8 C901060007 Number of SDCCH handover attempts due to DL interference

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
BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is yes and handover cause is downlink interference. The measurement point is A, as shown in Figure 12-7.

12-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 12-7 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

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
BSC carries out handover judgment after receiving SDDCH measurement report; the 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Figure 12-8 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

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
BSC carries out handover judgment after receiving SDDCH measurement report; the 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 12-9 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

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
BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is yes and handover cause is PBGT (on SDCCH). The measurement point is A, as shown in Figure 12-10.

12-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Figure 12-10 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

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
BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is yes and handover cause is large TA (on SDCCH). The measurement point is A, as shown in Figure 12-11.

12-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 12-11 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

12.13 C901060012 Number of SDCCH handover 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
BSC carries out handover judgment after receiving SDDCH measurement report; the 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Figure 12-12 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover ZGO-02-02-006 Rapid Level Drop Handover ZGO-02-02-015 Enhanced Cell Reselection Procedure

12.14 C901060013 Number of SDCCH handover 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
BSC carries out handover judgment after receiving SDDCH measurement report; the 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 12-13 Handover Decision

Unit
Times

Related Features
ZGO-02-02-001 Handover between Macro- and Micro-cells ZGO-02-02-004 SDCCH/SDCCH Handover

12.15 C901060014 Number of SDCCH handover 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Figure 12-14 Ho_Enquiry Handover

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

12.16 C901060015 Number of SDCCH handover 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 12-15 Traffic Handover

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover ZGO-02-02-007 Traffic Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing

12.17 C901060016 Number of SDCCH 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Measurement Point
BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is yes and handover cause is large TA and wastage (on SDCCH). The measurement point is A, as shown in Figure 12-16.
Figure 12-16 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

12.18 C901060017 Number of SDCCH handover 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is yes and handover cause is small TA and wastage (on SDCCH). The measurement point is A, as shown in Figure 12-17.
Figure 12-17 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Measurement Point
BSC carries out handover judgment after receiving SDDCH measurement report; the 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.
Figure 12-18 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover ZGO-02-03-002 GSM/WCDMA Interworking ZGO-02-03-003 GERAN/UTRAN Load Sharing

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
BSC carries out handover judgment after receiving SDDCH measurement report; the 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.
Figure 12-19 Handover Decision

Unit
Times

Related Features
ZGO-02-02-003 Directed-Shift Handover ZGO-02-02-004 SDCCH/SDCCH 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

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 ZGO-02-02-004 SDCCH/SDCCH Handover

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 12-21 Forced Handover Judgment

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover
12-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

12.23 C901060022 Number of SDCCH handover 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
BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is yes and handover is from second cell to first cell. The measurement point is A, as shown in Figure 12-22.
Figure 12-22 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

12-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

12.24 C901060023 Number of SDCCH handover 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). 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 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
BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is yes and handover is from first cell to second cell. The measurement point is A, as shown in Figure 12-23.
Figure 12-23 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

12-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

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
BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is yes and handover cause is any other reason. The measurement point is A, as shown in Figure 12-24.
Figure 12-24 Handover Decision

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

12.26 C901060035 Number of TCH/F handover attempts due to quick break up of UL

Definition
Number of TCH/F handover attempts due to quick break up of UL.
12-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of handover attempts due to uplink break up quickly (on TCH/F). If TCH/F 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 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 counter increments if judgment result is yes and handover cause is uplink break up quickly (on TCH/F). The measurement point is A, as shown in Figure 12-25.
Figure 12-25 Handover Decision

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-02-02-006 Rapid Level Drop Handover ZGO-02-02-015 Enhanced Cell Reselection Procedure

12.27 C901060036 Number of TCH/F handover attempts due to macro-micro switch

Definition
Number of TCH/F handover attempts due to macro-micro switch.

12-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Description
This counter counts the number of handover attempts due to macro-micro switch (on TCH/F). 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 TCH/F); its value can represent the status of micro cell absorbing traffic.

Measurement Point
BSC carries out handover judgment after receiving TCH/F measurement report; the counter increments if judgment result is yes and handover cause is macro-micro switch (on TCH/F). The measurement point is A, as shown in Figure 12-26.
Figure 12-26 Handover Decision

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-02-02-001 Handover between Macro- and Micro-cells

12.28 C901060037 Number of TCH/F handover attempts 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). Handover is originated by MSC, some calls are handed over from the present cell to target cell for alleviating the present cell traffic load.
12-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out frequency of handover attempts due to MSC request (on 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 shown in Figure 12-27.
Figure 12-27 HO_Enquiry Handover

Unit
Times

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

12.29 C901060038 Number of TCH/F handover attempts due to traffic

Definition
Number of TCH/F handover attempts due to traffic.

Description
This counter counts the number of handover attempts due to traffic (on TCH/F). Handover is originated by BSC, some calls are handed over from the present cell to target cell for alleviating the present cell traffic load.

Usage
This counter is used to find out frequency of handover attempts due to traffic (on TCH/F); its value can represent the status that BSC adjusts the present cell traffic.

12-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Measurement Point
BSC carries out handover judgment after receiving TCH/F traffic alarm, the counter increments if judgment result is yes. The measurement point is A, as shown in Figure 12-28.
Figure 12-28 Traffic Handover

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-02-02-007 Traffic Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing

12.30 C901060039 Number of TCH/F handover attempts due to large TA and wastage
Definition
Number of TCH/F handover attempts due to large TA and wastage.

Description
This counter counts the number of handover attempts due to large TA and wastage (on TCH/F). 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.

12-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out frequency of handover attempts due to large TA and wastage (on TCH/F); its value can represent the mobility of subscriber among sub-cells in the cell.

Measurement Point
BSC carries out handover judgment after receiving TCH/F measurement report; the counter increments if judgment result is yes and handover cause is large TA and wastage (on TCH/F). The measurement point is A, as shown in Figure 12-29.
Figure 12-29 Handover Decision

Unit
Times

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

12.31 C901060040 Number of TCH/F handover attempts due to small TA and wastage
Definition
Number of TCH/F handover attempts due to small TA and wastage.

Description
This counter counts the number of handover attempts due to small TA and wastage (on TCH/F). 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.

12-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Usage
This counter is used to find out frequency of handover attempts due to small TA and wastage (on TCH/F); its value can represent the mobility of subscriber among sub-cells in the cell.

Measurement Point
BSC carries out handover judgment after receiving TCH/F measurement report; the counter increments if judgment result is yes and handover cause is small TA and wastage (on TCH/F). The measurement point is A, as shown in Figure 12-30.
Figure 12-30 Handover Decision

Unit
Times

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

12.32 C901060041 Number of TCH/F handover attempts 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
This counter is used to find out frequency of handover attempts due to a good standard level in 3G adjacent cell (on TCH/F); its value can represent status that 3G network absorbs traffic.
12-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
BSC carries out handover judgment after receiving TCH/F measurement report; the counter increments if judgment result is yes and handover cause is good standard level in 3G adjacent cell (on TCH/F). The measurement point is A, as shown in Figure 12-31.
Figure 12-31 Handover Decision

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-02-03-002 GSM/WCDMA Interworking ZGO-02-03-003 GERAN/UTRAN Load Sharing

12.33 C901060042 Number of TCH/F handover attempts due to forced transfer

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 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 TCH/F); its value can represent the present cells channel utilizing status and traffic sharing status.

12-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Measurement Point
BSC carries out handover judgment after receiving TCH/F measurement report; the counter increments if judgment result is yes and handover cause is forced transfer handover attempts (on TCH/F). The measurement point is A, as shown in Figure 12-32.
Figure 12-32 Handover Decision

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-02-02-003 Directed-Shift Handover

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

Usage
This counter is used to find out frequency of forced handovers during assignment (on TCH/F); its value can represent the present cells TCH utilizing status and traffic sharing status.

12-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 TCH/F. The measurement point is A, as shown in Figure 12-33.
Figure 12-33 Forced Handover Judgment

Unit
Times

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

12.35 C901060044 Number of TCH/F handover attempts during handover due to forced transfer
Definition
Number of TCH/F handover attempts during handover due to forced transfer.

12-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

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
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 TCH/F. The measurement point is A, as shown in Figure 12-34.
Figure 12-34 Forced Handover Judgment

Unit
Times

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

12-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

12.36 C901060045 Number of TCH/F handover attempts due to TA increase

Definition
Number of TCH/F handover attempts due to TA increase.

Description
This counter counts the number of handover attempts due to increased TA (on TCH/F). This handover only happens in expanding 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
BSC carries out handover judgment after receiving TCH/F measurement report; the counter increments if judgment result is yes and handover is from second cell to first cell. The measurement point is A, as shown in Figure 12-35.
Figure 12-35 Handover Decision

Unit
Times

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

12-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

12.37 C901060046 Number of TCH/F handover attempts due to TA decrease

Definition
Number of TCH/F handover attempts due to TA decrease.

Description
This counter counts the number of handover attempts due to decreased TA (on TCH/F). This handover only happens in expanding 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 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
BSC carries out handover judgment after receiving TCH/F measurement report; the counter increments if judgment result is yes and handover is from first cell to second cell. The measurement point is A, as shown in Figure 12-36.
Figure 12-36 Handover Decision

Unit
Times

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

12-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

12.38 C901060058 Number of TCH/H handover attempts due to quick break up of UL

Definition
Number of TCH/H handover attempts due to quick break up of UL.

Description
This counter counts the number of handover attempts due to uplink break up quickly (on TCH/H). If TCH/H uplink level decreases 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 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 counter increments if judgment result is yes and handover cause is uplink break up quickly (on TCH/H). The measurement point is A, as shown in Figure 12-37.
Figure 12-37 Handover Decision

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-02-02-006 Rapid Level Drop Handover ZGO-02-02-015 Enhanced Cell Reselection Procedure ZGO-03-02-005 Dynamic Half Rate Allocation

12-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

12.39 C901060059 Number of TCH/H handover attempts due to macro-micro switch

Definition
Number of TCH/H handover attempts due to macro-micro switch.

Description
This counter counts the number of handover attempts due to macro-micro switch (on TCH/H). 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 TCH/H); its value can represent the status of micro cell absorbing traffic.

Measurement Point
BSC carries out handover judgment after receiving TCH/H measurement report; the counter increments if judgment result is yes and handover cause is macro-micro switch (on TCH/H). The measurement point is A, as shown in Figure 12-38.
Figure 12-38 Handover Decision

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-02-02-001 Handover between Macro- and Micro-cells ZGO-03-02-005 Dynamic Half Rate Allocation

12-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

12.40 C901060060 Number of TCH/H handover attempts 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). 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 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
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

12-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

12.41 C901060061 Number of TCH/H handover attempts due to traffic

Definition
Number of TCH/H handover attempts due to traffic.

Description
This counter counts the number of handover attempts due to traffic (on TCH/H). Handover is originated by BSC, some calls are handed over from the present cell to target cell for alleviating the present cell traffic load.

Usage
This counter is used to find out frequency of handover attempts due to traffic (on TCH/H); its value can represent the status that BSC adjusts the present cell traffic.

Measurement Point
BSC carries out handover judgment after receiving TCH/H traffic alarm, the counter increments if judgment result is yes. The measurement point is A, as shown in Figure 12-40.
Figure 12-40 Traffic Handover

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-02-02-007 Traffic Based Handover
12-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ZGO-02-03-003 GERAN/UTRAN Load Sharing ZGO-03-02-005 Dynamic Half Rate Allocation

12.42 C901060062 Number of TCH/H handover attempts due to large TA and wastage
Definition
Number of TCH/H handover attempts due to large TA and wastage.

Description
This counter counts the number of handover attempts due to large TA and wastage (on TCH/H). 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 TCH/H); its value can represent the mobility of subscriber among sub-cells in the cell.

Measurement Point
BSC carries out handover judgment after receiving TCH/H measurement report; the counter increments if judgment result is yes and handover cause is large TA and wastage (on TCH/H). The measurement point is A, as shown in Figure 12-41.
Figure 12-41 Handover Decision

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
12-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

12.43 C901060063 Number of TCH/H handover attempts due to small TA and wastage
Definition
Number of TCH/H handover attempts due to small TA and wastage.

Description
This counter counts the number of handover attempts due to small TA and wastage (on TCH/H). 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 TCH/H); its value can represent the mobility of subscriber among sub-cells in the cell.

Measurement Point
BSC carries out handover judgment after receiving TCH/H measurement report; the counter increments if judgment result is yes and handover cause is small TA and wastage (on TCH/H). The measurement point is A, as shown in Figure 12-42.
Figure 12-42 Handover Decision

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

12-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

12.44 C901060064 Number of TCH/H handover attempts 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
This counter is used to find out frequency of handover attempts due to a good standard level in 3G adjacent cell (on TCH/H); its value can represent status that 3G network absorbs traffic.

Measurement Point
BSC carries out handover judgment after receiving TCH/H measurement report; the counter increments if judgment result is yes and handover cause is good standard level in 3G adjacent cell (on TCH/H). The measurement point is A, as shown in Figure 12-43.
Figure 12-43 Handover Decision

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-02-03-002 GSM/WCDMA Interworking ZGO-02-03-003 GERAN/UTRAN Load Sharing ZGO-03-02-005 Dynamic Half Rate Allocation
12-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

12.45 C901060065 Number of TCH/H handover attempts due to forced transfer

Definition
Number of TCH/H handover attempts due to forced transfer.

Description
This counter counts the number of forced transfer handover attempts (on TCH/H). If the TCH utilizing rate of the present cell 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 TCH/H); its value can represent the present cells channel utilizing status and traffic sharing status.

Measurement Point
BSC carries out handover judgment after receiving TCH/H measurement report; the counter increments if judgment result is yes and handover cause is forced transfer handover attempts (on TCH/H). The measurement point is A, as shown in Figure 12-44.
Figure 12-44 Handover Decision

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-02-02-003 Directed-Shift Handover ZGO-03-02-005 Dynamic Half Rate Allocation

12-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

12.46 C901060066 Number of TCH/H handover attempts 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 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.

Usage
This counter is used to find out frequency of forced handovers during assignment (on TCH/H); its value can represent the present cells TCH utilizing status and traffic sharing status.

Measurement Point
BSC has no available TCH to allocate during the assignment process and it carries out forced handover judgment; the counter increments if judgment result is yes and the channel type of forced handover instance is TCH/H. The measurement point is A, as shown in Figure 12-45.

12-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Figure 12-45 Forced Handover Judgment

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

12.47 C901060067 Number of TCH/H handover attempts 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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 TCH/H. The measurement point is A, as shown in Figure 12-46.
Figure 12-46 Forced Handover Judgment

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

12-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

12.48 C901060068 Number of TCH/H handover attempts during handover due to TA increase
Definition
Number of TCH/H handover attempts during handover due to TA increase.

Description
This counter counts the number of handover attempts due to increased TA (on TCH/H). This handover only happens in expanding 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
BSC carries out handover judgment after receiving TCH/H measurement report; the counter increments if judgment result is yes and handover is from second cell to first cell. The measurement point is A, as shown in Figure 12-47.
Figure 12-47 Handover Decision

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

12-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

12.49 C901060069 Number of TCH/H handover attempts during handover due to TA decrease
Definition
Number of TCH/H handover attempts during handover due to TA decrease.

Description
This counter counts the number of handover attempts due to decreased TA (on TCH/H). This handover only happens in expanding 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 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
BSC carries out handover judgment after receiving TCH/H measurement report; the counter increments if judgment result is yes and handover is from first cell to second cell. The measurement point is A, as shown in Figure 12-48.
Figure 12-48 Handover Decision

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

12-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

12.50 C901060070 Number of TCH/H handover attempts due to other reasons

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
BSC carries out handover judgment after receiving TCH/H measurement report; the counter increments if judgment result is yes and handover is caused by other reasons. The measurement point is A, as shown in Figure 12-49.
Figure 12-49 Handover Decision

Unit
Times

12.51 C901060071 Number of TCH/F handover attempts 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

12.52 C901060072 Number of TCH/H handover attempts due to CS channel transfer

Definition
Number of TCH/H handover attempts due to CS channel transfer

12-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

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.
Figure 12-51 CS Channel Transfer Handover

Unit
Times

Related Features
ZGO-03-02-004 HR Concentration

12-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

12.53 C901060073 Number of TCH/H handover attempts 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.
Figure 12-52 CS Channel Transfer Handover

Unit
Times
12-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Related Features
ZGO-03-02-004 HR Concentration

12.54 C901060074 Number of TCH/F handover attempts 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 shown in Figure 12-53.
Figure 12-53 CS Channel Transfer Handover

12-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-04-04-001 TCH Migration to BCCH TRX

12.55 C901060075 Number of TCH/F handover attempts 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 shown in Figure 12-54.

12-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Figure 12-54 CS Channel Transfer Handover

Unit
Times

Related Features
ZGO-04-04-001 TCH Migration to BCCH TRX

12.56 C901060076 Number of TCH/F handover attempts 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 shown in Figure 12-55.
Figure 12-55 CS Channel Transfer Handover

Unit
Times

Related Features
ZGO-03-02-004 HR Concentration

12.57 C901060077 Number of TCH/H handover attempts 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

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, as shown in Figure 12-56.
Figure 12-56 CS Channel Transfer Handover

Unit
Times

Related Features
ZGO-03-02-004 HR Concentration

12.58 C901060078 Number of TCH/F handover attempts 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

12.59 C901060079 Number of SDCCH handover 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

12.60 C901060080 Number of TCH/F handover attempts due to downlink rapid drop
Description
This counter counts the number of handover attempts due to too high downlink level on TCH/F.

12-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Usage
This counter measures the frequency of handover due to the downlink level on TCH/F. The higher value indicates the higher downlink level on TCH/F.

Measurement Point
This counter increments if the handover decision is done after receiving the measurement report on TCH/F by BSC and the handover is caused by the rapid downlink drop.

Unit
Times

12.61 C901060081 Number of TCH/H handover attempts due to downlink rapid drop
Description
This counter counts the number of handover attempts due to too high downlink level on TCH/H.

Usage
This counter measures the frequency of handover due to the downlink level on TCH/H. The higher value indicates the higher downlink level on TCH/H.

Measurement Point
This counter increments if the handover decision is done after receiving the measurement report on TCH/H by BSC and the handover is caused by the rapid downlink drop.

Unit
Times

12.62 C901060082 Attempts of handover on TCH/F caused by power adjustment

Description
After the dynamic power sharing function is enabled, iBSC performs real-time monitoring for the power usage of each RRU's timeslots. When a channel is allocated, the power it uses is registered; when the channel is released, the power it uses is also released. When the base station reports downlink dynamic power control result, the power the channel uses is refreshed.
12-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

When iBSC detects the power a RRU's timeslot currently uses reaches the threshold of power congestion control, it selects a CS service and performs outgoing handover for it towards other timeslot of the cell or towards other cell. If the service is occupying TCH/F, the counter increments. This counter is supported in version V6.20.61 or later.

Usage
This counter is used to find out the frequency of FR service handover due to RRU power congestion.

Measurement Point
When iBSC detects the power a RRU's timeslot currently uses reaches the threshold of power congestion control, it selects a CS service and performs outgoing handover for it towards other timeslot of the cell or towards other cell. If the service is occupying TCH/F, the counter increments.

12.63 C901060083 Attempts of handover on TCH/H caused by power adjustment

Description
After the dynamic power sharing function is enabled, iBSC performs real-time monitoring for the power usage of each RRU's timeslots. When a channel is allocated, the power it uses is registered; when the channel is released, the power it uses is also released. When the base station reports downlink dynamic power control result, the power the channel uses is refreshed. When iBSC detects the power a RRU's timeslot currently uses reaches the threshold of power congestion control, it selects a CS service and performs outgoing handover for it towards other timeslot of the cell or towards other cell. If the service is occupying TCH/H, the counter increments.

Usage
This counter is used to find out the frequency of HR service handover due to RRU power congestion. This counter is supported in version V6.20.61 or later.

Measurement Point
When iBSC detects the power a RRU's timeslot currently uses reaches the threshold of power congestion control, it selects a CS service and performs outgoing handover for it towards other timeslot of the cell or towards other cell. If the service is occupying TCH/H, the counter increments.
12-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

12.64 C901060084 Attempts of handover on TCH/F caused by local switch

Description
The counter counts when the local switch initiates FR service handover. This counter is supported in version V6.20.614a.

Unit
Times

Statistics Object
Cell

12.65 C901060085 Attempts of handover on TCH/H caused by local switch

Description
The counter counts when the local switch initiates HR service handover. This counter is supported in version V6.20.614a.

Unit
Times

Statistics Object
Cell

12.66 C901060086 Attempts of handover on TCH/F caused by reducing band resources of IPAbis
Description
After the service module receives the FR-to-HR handover request message from the RANUMC module, this counter counts the number of attempts of FR-to-HR handover. As shown in Figure 12-57, after the EV_FR_Ho_HR message is received, the system judges whether the handover condition is satisfied. If handover is allowed, the counter counts.

12-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 12-57 Handover Attempt due to Reducing Band Resources of IPAbis

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

12.67 C901060087 Attempts of handover on TCH/H because of MASTERPWR_ALM from TRX

Description
After the service module receives the traffic-migration handover request message from the DBS module, this counter counts the number of attempts of FR handover. As shown in Figure 12-58, after the EV_DBS_CS_MOV message is received, the system judges whether the handover condition is satisfied. If handover is allowed, the counter counts.
Figure 12-58 Traffic-Migration Handover due to MASTERPWR_ALM from TRX

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

12-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

12.68 C901060088 Attempts of handover on TCH/F because of MASTERPWR_ALM from TRX

Description
After the service module receives the traffic-migration handover request message from the DBS module, this counter counts the number of attempts of HR handover. As shown in Figure 12-59, after the EV_DBS_CS_MOV message is received, the system judges whether the handover condition is satisfied. If handover is allowed, the counter counts.
Figure 12-59 Traffic-Migration Handover due to MASTERPWR_ALM from TRX

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

12.69 C901060089 Number of handover attempts due to directed retry for PBGT
Description
After MSC assigns the channel, if the measurement report on SDCCH indicates a better cell, then the TCH channel can be assigned in the better cell. The process is called directed retry due to radio cause, which is a handover type. This counter counts the number of attempts of MS's directed retry due to radio causes. The counter is used to study the cell's coverage and the effects of cell reselection parameters. During the assignment, if the measurement report on SDCCH indicates a cell with better signal, then the better cell is selected for channel assignment attempt, and the counter increments. The measurement point is A, as shown in Figure 12-60.

12-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 12-60 Number of Assignment Executions due to Directed Retry

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

12.70 C901060090 Number of SDCCH handover attempts due to DL quality rapid drop
Description
This counter counts the number of handover attempts on SDCCH initiated by MS due to downlink quality fast fading. This counter is used to find out the frequency of MS's handover on SDCCH due to downlink quality fast fading. If the counter's value is large, it indicates that handover on SDCCH often occurs when the downlink quality becomes worse. After BSC receives the measurement report on SDCCH, it performs handover decision. If the handover decision indicates that handover is required and the handover is due to downlink quality fast fading, the counter increments. The measurement point is A, as shown in Figure 12-61.

12-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

Figure 12-61 Handover Decision

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

12.71 C901060091 Number of TCH/F handover attempts due to DL quality rapid drop
Description
This counter counts the number of handover attempts on TCH/F initiated by MS due to downlink quality fast fading. This counter is used to find out the frequency of MS's handover on TCH/F due to downlink quality fast fading. If the counter's value is large, it indicates that handover on TCH/F often occurs when the downlink quality becomes worse. After BSC receives the measurement report on TCH/F, it performs handover decision. If the handover decision indicates that handover is required and the handover is due to downlink quality fast fading, the counter increments. The measurement point is A, as shown in Figure 12-62.
Figure 12-62 Handover Decision

This counter is supported in version V6.20.614b.

Unit
Times
12-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Statistics Object
Cell

12.72 C901060092 Number of TCH/H handover attempts due to DL quality rapid drop
Description
This counter counts the number of handover attempts on TCH/H initiated by MS due to downlink quality fast fading. This counter is used to find out the frequency of MS's handover on TCH/H due to downlink quality fast fading. If the counter's value is large, it indicates that handover on TCH/H often occurs when the downlink quality becomes worse. After BSC receives the measurement report on TCH/H, it performs handover decision. If the handover decision indicates that handover is required and the handover is due to downlink quality fast fading, the counter increments. The measurement point is A, as shown in Figure 12-63.
Figure 12-63 Handover Decision

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

12.73 C901060095 Number of TCH/F Handover Attempts Due to Dynamic Channel Move
Description
This counter counts the number of TCH/F handover attempts due to dynamic channel move. In the cell that supports the dynamic channel move, the voice service over the dynamic channel in the cell is moved to the static channel via intra-cell handover when the
12-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

static TCH is released. This counter increases by 1 upon each TCH/F handover attempt in the cell due to dynamic channel move.

Usage
None

Measurement Point
The measurement point is shown in Figure 12-64.
Figure 12-64 Handover Due to CS Channel Move

Unit
Time

12.74 C901060096 Number of TCH/H Handover Attempts Due to Dynamic Channel Move
Description
This counter counts the number of TCH/H handover attempts due to dynamic channel move. In the cell that supports the dynamic channel move, the voice service over the dynamic channel in the cell is moved to the static channel via intra-cell handover when the static TCH is released. This counter increases by 1 upon each intra-cell TCH/H handover attempt due to dynamic channel move.

Usage
None

Measurement Point
The measurement point is shown in Figure Handover Due to CS Channel Move.

Unit
Time

12-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

12.75 C901060100 Number of MSC-Controlled Outgoing Handover Attempts Due to PBGT

Description
This counter counts the number of times that an outgoing handover attempt occurs upon a handover request for better cell that is sent from the MSC.

Usage
This counter indicates the number of outgoing handover attempts controlled by the MSC due to PBGT.

Measurement Point
This counter is incremented each time the BSC, after deciding an outgoing handover, sends a Handover Required message with the cause of "better cell".

Unit
Times

12.76 C901060101 Number of MSC-Controlled Incoming Handover Attempts Due to PBGT

Description
This counter counts the number of times that an incoming handover attempt occurs upon a handover request for better cell that is sent from the MSC.

Usage
This counter indicates the number of incoming handover attempts controlled by the MSC due to PBGT.

Measurement Point
This counter is incremented each time the BSC receives an external handover request with the cause of "better cell".

Unit
Times

12-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 12 Handover Cause Measurement

12.77 C901060102 Number of Inter BSC Incoming Handover Attempts Due to Large TA
Description
This counter counts the number of times that an incoming handover attempts occurs due to long distance between the MS and the BTS.

Usage
This counter indicates the number of inter-BSC incoming handover attempts due to too much TA.

Measurement Point
This counter is incremented each time the BSC receives a handover request with the cause of "Distance" from the MSC.

Unit
Times

12.78 C901060103 Number of Inner BSC Incoming Handover Attempts Due to Large TA
Description
This counter counts the number of times that an incoming handover attempts occurs due to long distance between the MS and the BTS.

Usage
This counter indicates the number of intra-BSC incoming handover attempts due to too much TA.

Measurement Point
This counter is incremented each time the BSC receives a measurement report and makes an intra-BSC handover decision due to distance reason.

Unit
Times

12-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

12.79 C901060104 Number of Dual Frequency Traffic Handover Attempts on TCH/F

Description
This counter counts inter-band handover attempts on TCH/Fs when the handover feature is enabled for dual-band networks.

Measurement Point
This counter is incremented each time the BSC determines an inter-band handover in a dual-band network based on the received measurement reports when the current channel is a TCH/F.

Unit
Number of times

12.80 C901060105 Number of Dual Frequence Traffic Handover Attempts on TCH/H

Description
This counter counts inter-band handover attempts on TCH/Hs when the handover feature is enabled for dual-band networks.

Measurement Point
This counter is incremented each time the BSC determines an inter-band handover in a dual-band network based on the received measurement reports when the current channel is a TCH/H.

Unit
Number of times

12-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13

RMM Call Drop Measurement

Table of Contents
Overview ..................................................................................................................13-6 C901070001 Number of SDCCH drops due to loss of contact with RANA ................13-7 C901070002 Number of SDCCH drops due to radio link failure................................13-8 C901070003 Number of SDCCH drops due to LAPD link failure ..............................13-9 C901070004 Number of SDCCH drops due to OMC-R forced release ...................13-10 C901070005 Number of SDCCH drops due to forced release by other calls...........13-10 C901070007 Number of SDCCH drops due to other failure .................................... 13-11 C901070008 Number of signaling TCH/F drops due to loss of contact with RANA .13-12 C901070009 Number of signaling TCH/F drops due to radio link failure .................13-13 C901070010 Number of signaling TCH/F drops due to LAPD link failure................13-14 C901070011 Number of signaling TCH/F drops due to OMC-R forced release .......13-15 C901070012 Number of signaling TCH/F drops due to forced release by other calls........................................................................................................................13-16 C901070014 Number of signaling TCH/F drops due to other failure .......................13-17 C901070015 Number of voice TCH/F drops due to loss of contact with RANA .......13-18 C901070017 Number of voice TCH/F drops due to LAPD link failure .....................13-19 C901070018 Number of voice TCH/F drops due to OMC-R forced release ............13-21 C901070019 Number of voice TCH/F drops due to forced release by other calls....13-22 C901070021 Number of voice TCH/F drops due to other failure.............................13-24 C901070022 Number of data TCH/F drops due to loss of contact with RANA ........13-24 C901070023 Number of data TCH/F drops due to radio link failure ........................13-26 C901070024 Number of data TCH/F drops due to LAPD link failure.......................13-28 C901070025 Number of data TCH/F drops due to OMC-R forced release..............13-29 C901070026 Number of data TCH/F drops due to forced release by other calls .....13-31 C901070028 Number of data TCH/F drops due to other failure ..............................13-32 C901070029 Number of signaling TCH/H drops due to loss of contact with RANA .13-33 C901070030 Number of signaling TCH/H drops due to radio link failure.................13-34 C901070031 Number of signaling TCH/H drops due to LAPD link failure ...............13-35 C901070032 Number of signaling TCH/H drops due to OMC-R forced release ......13-36 C901070033 Number of signaling TCH/H drops due to forced release by other calls........................................................................................................................13-37 C901070035 Number of signaling TCH/H drops due to other failure.......................13-38 C901070036 Number of voice TCH/H drops due to loss of contact with RANA.......13-39 C901070038 Number of voice TCH/H drops due to LAPD link failure .....................13-41 C901070039 Number of voice TCH/H drops due to OMC-R forced release ............13-42 C901070040 Number of voice TCH/H drops due to forced release by other calls ...13-44 C901070042 Number of voice TCH/H drops due to other failure ............................13-45
13-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901070043 Number of data TCH/H drops due to loss of contact with RANA ........13-46 C901070044 Number of data TCH/H drops due to radio link failure........................13-48 C901070045 Number of data TCH/H drops due to LAPD link failure ......................13-49 C901070046 Number of data TCH/H drops due to OMC-R forced release .............13-51 C901070047 Number of data TCH/H drops due to forced release by other calls.....13-52 C901070049 Number of data TCH/H drops due to other failure..............................13-54 C901070053 Number of SDCCH link failures .........................................................13-54 C901070054 Number of TCH/F link failures ...........................................................13-56 C901070055 Number of TCH/H link failures ...........................................................13-58 C901070056 Number of RANA link releases due to other cause on SDCCH..........13-59 C901070057 Number of RANA link releases due to other cause on TCH/F ............13-60 C901070058 Number of RANA link releases due to other cause on TCH/H............13-61 C901070059 Number of SDCCH short messages drops ........................................13-62 C901070060 Number of TCH/F short messages drops ..........................................13-63 C901070061 Number of TCH/H short messages drops ..........................................13-63 C901070062 Number of TCH/F drops due to CS channel is forced release by PS .13-64 C901070063 Number of TCH/H drops due to CS channel is forced release by PS .13-65 C901070064 Number of SDCCH drops due to eMLPP forced handover.................13-65 C901070065 Number of signaling TCH/F drops due to eMLPP forced handover ....13-66 C901070066 Number of voice TCH/F drops due to eMLPP forced handover..........13-67 C901070067 Number of data TCH/F drops due to eMLPP forced handover ...........13-68 C901070068 Number of sigaling TCH/H drops due to eMLPP forced handover......13-69 C901070069 Number of voice TCH/H drops due to eMLPP forced handover .........13-70 C901070070 Number of data TCH/H drops due to eMLPP forced handover...........13-71 C901070071 Bad quality of UL receiving (On SDCCH) ..........................................13-72 C901070072 Bad quality of DL receiving (On SDCCH) ..........................................13-73 C901070073 Lower electrical level of UL (On SDCCH) ..........................................13-74 C901070074 Lower electrical level of DL (On SDCCH) ..........................................13-75 C901070075 Number of signaling drops due to TA too far (On SDCCH) ................13-76 C901070076 Reasons of the other radios (On SDCCH) .........................................13-77 C901070077 Bad quality of UL receiving (On TCH/F).............................................13-78 C901070078 Bad quality of DL receiving (On TCH/F).............................................13-79 C901070079 Lower electrical level of UL (On TCH/F) ............................................13-80 C901070080 Lower electrical level of DL (On TCH/F) ............................................13-82 C901070081 Number of signaling drops due to TA too far (On TCH/F)...................13-83 C901070082 Reasons of the other radios (On TCH/F) ...........................................13-85 C901070083 Bad quality of UL receiving (On TCH/H) ............................................13-86 C901070084 Bad quality of DL receiving (On TCH/H) ............................................13-88 C901070085 Lower electrical level of UL (On TCH/H) ............................................13-89 C901070086 Lower electrical level of DL (On TCH/H) ............................................13-91 C901070087 Number of signaling drops due to TA too far (On TCH/H) ..................13-92 C901070088 Reasons of the other radios (On TCH/H) ...........................................13-94 C901070089 The Count of Drop Call caused by "IP Resource Reset" ....................13-95 C901070090 Number of FR_V1 radio link fail .........................................................13-96 C901070091 Number of FR_V2 radio link fail .........................................................13-97
13-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

C901070092 Number of FR_V3 radio link fail .........................................................13-97 C901070093 Number of HR_V1 radio link fail ........................................................13-98 C901070094 Number of HR_V3 radio link fail ........................................................13-98 C901070095 Number of signaling TCH/F drops due to BIPB Active/Standby Changeover ...........................................................................................................13-99 C901070096 Number of voice TCH/F drops due to BIPB Active/Standby Changeover ...........................................................................................................13-99 C901070097 Number of data TCH/F drops due to BIPB Active/Standby Changeover .........................................................................................................13-100 C901070098 Number of signaling TCH/H drops due to BIPB Active/Standby Changeover .........................................................................................................13-100 C901070099 Number of voice TCH/H drops due to BIPB Active/Standby Changeover .........................................................................................................13-100 C901070100 Number of data TCH/H drops due to BIPB Active/Standby Changeover .........................................................................................................13-101 C901070101 Number of SDCCH drops due to LAPD Active/Standby Changeover .........................................................................................................13-101 C901070102 Number of voice TCH/F drops due to LAPD Active/Standby Changeover .........................................................................................................13-102 C901070103 Number of data TCH/F drops due to LAPD Active/Standby Changeover .........................................................................................................13-102 C901070104 Number of signaling TCH/F drops due to LAPD Active/Standby Changeover .........................................................................................................13-102 C901070105 Number of voice TCH/H drops due to LAPD Active/Standby Changeover .........................................................................................................13-103 C901070106 Number of data TCH/H drops due to LAPD Active/Standby Changeover .........................................................................................................13-103 C901070107 Number of signaling TCH/H drops due to LAPD Active/Standby Changeover .........................................................................................................13-104 C901070108 Number of voice TCH/F drops due to handover fail for power adjustment ...........................................................................................................13-104 C901070109 Number of voice TCH/H drops due to handover fail for power adjustment ...........................................................................................................13-104 C901070110 Number of SDCCH drops due to BIPB Active/Standby Changeover .13-105 C901070111 Number of SDCCH drops due to BTS failure....................................13-105 C901070112 Number of signaling TCH/F drops due to BTS failure.......................13-106 C901070113 Number of voice TCH/F drops due to BTS failure ............................13-107 C901070114 Number of data TCH/F drops due to BTS failure..............................13-108 C901070115 Number of signaling TCH/H drops due to BTS failure ...................... 13-110 C901070116 Number of voice TCH/H drops due to BTS failure ............................ 13-111 C901070117 Number of data TCH/H drops due to BTS failure ............................. 13-112 C901070118 Call Drop by Releasing Local Switch ............................................... 13-113 C901070119 Number of FR_V4 Radio Link Fail ................................................... 13-114 C901070120 Number of FR_V5 Radio Link Fail ................................................... 13-115 C901070121 Number of HR_V4 Radio Link Fail................................................... 13-115
13-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901070122 Call Drop Due To Emergency Call Preemption on TCH/F ................ 13-116 C901070123 Call Drop Due to Emergency Call Preemption on TCH/H................. 13-117 C901070126 Number of drop call on SDCCH due to IMSI Exception ................... 13-117 C901070127 Number of drop call on sig TCH/F due to IMSI Exception ................ 13-118 C901070128 Number of drop call on voice TCH/F due to IMSI Exception ............ 13-118 C901070129 Number of drop call on data TCH/F due to IMSI Exception.............. 13-119 C901070130 Number of drop call on sig TCH/H due to IMSI Exception................ 13-119 C901070131 Number of drop call on voice TCH/H due to IMSI Exception ............13-120 C901070132 Number of drop call on data TCH/H due to IMSI Exception .............13-120 C901070133 Number of Drop Call When TCH Assign..........................................13-121 C901070134 Number of Drop Call on TCH...........................................................13-121 C901070135 Number of Drop Call on TCH(exclude sms drop after hang-off) .......13-122 C901070136 Number of SDCCH Drops Due to Intra-Cell Handover Failure .........13-122 C901070137 Number of Speech TCH/F Drops Due to Intra-Cell Handover Failure..................................................................................................................13-123 C901070138 Number of Data TCH/F Drops Due to Intra-Cell Handover Failure ...13-123 C901070139 Number of Signaling TCH/F Drops Due to Intra-Cell Handover Failure..................................................................................................................13-124 C901070140 Number of Speech TCH/H Drops Due to Intra-Cell Handover Failure..................................................................................................................13-124 C901070141 Number of Data TCH/H Drops Due to Intra-Cell Handover Failure...13-125 C901070142 Number of Signaling TCH/H Drops Due to Intra-Cell Handover Failure..................................................................................................................13-125 C901070143 Number of SDCCH Drops Due to Inter-Cell Handover Failure .........13-126 C901070144 Number of Speech TCH/F Drops Due to Inter-Cell Handover Failure..................................................................................................................13-126 C901070145 Number of Data TCH/F Drops Due to Inter-Cell Handover Failure ...13-127 C901070146 Number of Signaling TCH/F Drops Due to Inter-Cell Handover Failure..................................................................................................................13-127 C901070147 Number of Speech TCH/H Drops Due to Inter-Cell Handover Failure..................................................................................................................13-128 C901070148 Number of Data TCH/H Drops Due to Inter-Cell Handover Failure...13-128 C901070149 Number of Signaling TCH/H Drops Due to Inter-Cell Handover Failure..................................................................................................................13-129 C901070150 Number of SDCCH Drops Due to Outgoing Handover Failure .........13-129 C901070151 Number of Speech TCH/F Drops Due to Outgoing Handover Failure..................................................................................................................13-130 C901070152 Number of Data TCH/F Drops Due to Outgoing Handover Failure ...13-130 C901070153 Number of Signaling TCH/F Drops Due to Outgoing Handover Failure..................................................................................................................13-131 C901070154 Number of Speech TCH/H Drops Due to Outgoing Handover Failure..................................................................................................................13-131 C901070155 Number of Data TCH/H Drops Due to Outgoing Handover Failure...13-132 C901070156 Number of Signaling TCH/H Drops Due to Outgoing Handover Failure..................................................................................................................13-132
13-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

C901070157 Number of Speech TCH/F Drops Due to Subcell 1 to Subcell 2 Handover Failure..................................................................................................13-133 C901070158 Number of Data TCH/F Drops Due to Subcell 1 to Subcell 2 Handover Failure..................................................................................................................13-133 C901070159 Number of Signaling TCH/F Drops Due to Subcell 1 to Subcell 2 Handover Failure..................................................................................................13-134 C901070160 Number of Speech TCH/H Drops Due to Subcell 1 to Subcell 2 Handover Failure..................................................................................................13-134 C901070161 Number of Data TCH/H Drops Due to Subcell 1 to Subcell 2 Handover Failure..................................................................................................................13-135 C901070162 Number of Signaling TCH/H Drops Due to Subcell 1 to Subcell 2 Handover Failure..................................................................................................13-135 C901070163 Number of Speech TCH/F Drops Due to Subcell 2 to Subcell 1 Handover Failure..................................................................................................13-136 C901070164 Number of Data TCH/F Drops Due to Subcell 2 to Subcell 1 Handover Failure..................................................................................................................13-136 C901070165 Number of Signaling TCH/F Drops Due to Subcell 2 to Subcell 1 Handover Failure..................................................................................................13-137 C901070166 Number of Speech TCH/H Drops Due to Subcell 2 to Subcell 1 Handover Failure..................................................................................................13-137 C901070167 Number of Data TCH/H Drops Due to Subcell 2 to Subcell 1 Handover Failure..................................................................................................................13-138 C901070168 Number of Signaling TCH/H Drops Due to Subcell 2 to Subcell 1 Handover Failure..................................................................................................13-138 C901070172 Number of Data TCH/F Drops .........................................................13-139 C901070173 Number of Data TCH/H Drops.........................................................13-139 C901070175 Number of Drop Call on SDCCH Due to BCCH Exchange...............13-139 C901070176 Number of Drop Call on SDCCH Due to Block Channel or Abis Resource..............................................................................................................13-140 C901070177 Number of Drop Call on SDCCH Due to SD Change .......................13-140 C901070178 Number of Drop Call on SDCCH Due to Global Reset.....................13-140 C901070179 Number of Drop Call on SDCCH Due to Ring BTS Turn Over .........13-141 C901070180 Number of Drop Call on TCH/F Due to IPA Board Fault...................13-141 C901070181 Number of Drop Call on TCH/F Due to IPA Board Resource Fault...13-142 C901070182 Number of Drop Call on TCH/F Due to BCCH Exchange.................13-142 C901070183 Number of Drop Call on TCH/F Due to Block Channel or Abis Resource..............................................................................................................13-142 C901070184 Number of Drop Call on TCH/F Due to SD Change .........................13-143 C901070185 Number of Drop Call on TCH/F Due to Circuit Fault.........................13-143 C901070186 Number of Drop Call on TCH/F Due to IFTA Cause.........................13-144 C901070187 Number of Drop Call on TCH/F Due to TDMA Board Fault ..............13-144 C901070188 Number of Drop Call on TCH/F Due to iTC Board Fault...................13-144 C901070189 Number of Drop Call on TCH/F Due to iTC Board Resource Fault...13-145 C901070190 Number of Drop Call on TCH/F Due to TC Board Fault ...................13-145 C901070191 Number of Drop Call on TCH/F Due to TC Board Resource Fault....13-146
13-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901070192 Number of Drop Call on TCH/F Due to Global Reset .......................13-146 C901070193 Number of Drop Call on TCH/F Due to PS Preempt ........................13-146 C901070194 Number of Drop Call on TCH/F Due to Reassign Fail ......................13-147 C901070195 Number of Drop Call on TCH/F Due to Ring BTS Turn Over............13-147 C901070198 Number of Drop Call on TCH/H Due to IPA Board Fault ..................13-147 C901070199 Number of Drop Call on TCH/H Due to IPA Board Resource Fault ..13-148 C901070200 Number of Drop Call on TCH/H Due to BCCH Exchange ................13-148 C901070201 Number of Drop Call on TCH/H Due to Block Channel or Abis Resource..............................................................................................................13-149 C901070202 Number of Drop Call on TCH/H Due to SD Change.........................13-149 C901070203 Number of Drop Call on TCH/H Due to Circuit Fault ........................13-149 C901070204 Number of Drop Call on TCH/H Due to IFTA Cause ........................13-150 C901070205 Number of Drop Call on TCH/H Due to TDMA Board Fault..............13-150 C901070206 Number of Drop Call on TCH/H Due to iTC Board Fault ..................13-151 C901070207 Number of Drop Call on TCH/H Due to iTC Board Resource Fault ..13-151 C901070208 Number of Drop Call on TCH/H Due to TC Board Fault ...................13-151 C901070209 Number of Drop Call on TCH/H Due to TC Board Resource Fault ...13-152 C901070210 Number of Drop Call on TCH/H Due to Global Reset.......................13-152 C901070211 Number of Drop Call on TCH/H Due to PS Preempt ........................13-152 C901070212 Number of Drop Call on TCH/H Due to Reassign Fail......................13-153 C901070213 Number of Drop Call on TCH/H Due to Ring BTS Turn Over ...........13-153 C901070216 Number of Drops Due to Interf UL Handover ...................................13-154 C901070217 Number of Drops Due to Interf DL Handover ...................................13-154 C901070218 Number of Drops Due to QUAL UL Handover .................................13-154 C901070219 Number of Drops Due to QUAL DL Handover .................................13-155 C901070220 Number of Drops Due to LEVEL UL Handover ................................13-155 C901070221 Number of Drops Due to LEVEL DL Handover ................................13-155 C901070222 Number of Drops Due to RAPID UL Handover ................................13-156 C901070223 Number of Drops Due to PBGT Handover .......................................13-156 C901070224 Number of Drops Due to MACRO to MICRO Handover ...................13-156 C901070225 Number of Drops Due to SUB Cell 1 to SUB Cell 2 Handover .........13-157 C901070226 Number of Drops Due to SUB Cell 2 to SUB Cell 1 Handover .........13-157 C901070227 Number of Drops Due to PREEMPT Handover................................13-157 C901070228 Number of Drops Due to TRAFFIC Handover..................................13-158 C901070229 Number of Drops Due to DLRAPID Handover .................................13-158 C901070230 Number of Drops Due to HRFR Handover.......................................13-158 C901070231 Number of Drops Due to RAPIDQUAL Handover ............................13-159

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-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

The measurement takes cell as the statistics unit.

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 point is A1, as shown in Figure 13-1.
Figure 13-1 Call Drop Due To A-Interface Failure In Immediate Assignment Process

RANCS forwards EST_IND message to RANA after receiving it on SDCCH; if no link establishment message on A-interface from RANA is received, the counter increments; meanwhile, BSC release the channel and instance, the measurement point is A2, as shown in Figure 13-1.

13-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 13-2 Call Drop Due To Radio Link Failure In Immediate Assignment Process

Unit
Times

13-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Related Features
ZGB-06-01-001 Monitoring Um Interface ZGO-04-02-007 AMR Radio Link Timers

13.4 C901070003 Number of SDCCH drops due to LAPD link failure

Definition
Number of SDCCH drops due to LAPD link failure

Description
This counter counts the number of call drop due to LAPD link 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. The measurement point is A, as shown in Figure 13-3.
Figure 13-3 Call Drop Due To Lapd Link Failure In Immediate Assignment Process

Unit
Times
13-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.5 C901070004 Number of SDCCH drops due to OMC-R forced release

Definition
Number of SDCCH drops due to OMC-R forced release

Description
This counter counts the number of call drop due to OMC-R forced releases (on SDCCH). The counter increments if the phenomenon that call drops after MS has obtained SDCCH is caused by OMC-R forced releases.

Usage
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.
Figure 13-4 Call Drop Due To OMC-R Forced Release In Immediate Assignment Process

Unit
Times

13.6 C901070005 Number of SDCCH drops due to forced release by other calls
Definition
Number of SDCCH drops due to forced release by other calls
13-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

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.
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 calldrops on the SDCCH channel due to other causes. The calldrops occur after the MS successfully applies for the SDCCH channel. This counter is incremented by one if the calldrops are due to the other causes, rather than due to the disconnection from RANA, radio link failures, LAPD link failures, OMCR forced
13-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

releases, other call forced releases, handover failures, SCCP disconnected abnormally, board faults, BTS faults, eMLPP forced handovers, BCCH switchovers, SD changeovers, BTS ring network switchovers, blocked radio channels or Abis. Currently, the other causes refer to abnormal instances or waste instance recycle.

Usage
This counter is used to know the calldrop frequency on the SDCCH channel due to the other causes.

Measurement Point
This counter counts the number of calldrops when the instances on the SDCCH channel are abnormal or the waste instances on the SDCCH channel are recycled.

Unit
Times

13.8 C901070008 Number of signaling TCH/F drops 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: 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-6.
13-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

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-6.
Figure 13-6 Call Drop Due To A-Interface Failure In Immediate Assignment Process

Unit
Times

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

13.9 C901070009 Number of signaling TCH/F drops 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-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter increments when BSC receives CONNectiOn FAILure INDicatiOn message on Abis interface on TCH/F signaling channel. The measurement point is A, as shown inFigure 13-7.
Figure 13-7 Call Drop Due To Radio Link Failure In Immediate Assignment Process

Unit
Times

Related Features
ZGB-06-01-001 Monitoring Um Interface ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-04-02-007 AMR Radio Link Timers

13.10 C901070010 Number of signaling TCH/F drops 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-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

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-8.
Figure 13-8 Call Drop Due To LAPD Link Failure In Immediate Assignment Process

Unit
Times

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

13.11 C901070011 Number of signaling TCH/F drops 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-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of call drop due to OMC-R forced releases (on TCH/F signaling channel).

Measurement Point
The counter increments when BSC receives OMC-R forced release message from database on TCH/F signaling channel. The measurement point is A, as shown in Figure 13-9.
Figure 13-9 Call Drop Due To OMC-R Forced Release In Immediate Assignment Process

Unit
Times

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

13.12 C901070012 Number of signaling TCH/F drops 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 signaling channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F signaling channel is caused by forced releases by other calls.

13-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Usage
This counter is used to find out the frequency of call drop due to forced releases by other calls (on TCH/F signaling channel).

Measurement Point
The counter increments when BSC receives forced release message from other calls on TCH/F signaling channel. The measurement point is A, as shown in Figure 13-10.
Figure 13-10 Call Drop Due To Forced Release By Other Calls In Immediate Assignment Process

Unit
Times

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

13.13 C901070014 Number of signaling TCH/F drops due to other failure

Definition
Number of signaling TCH/F drops due to other failure

Description
This counter counts the number of calldrops on the TCH/F signaling channel due to other causes. The calldrops occur after the MS successfully applies for the TCH/F signaling channel. This counter is incremented by one if the calldrops are due to the other causes, rather than due to the disconnection from RANA, radio link failures, LAPD link failures, OMCR forced releases, other call forced releases, handover failures, SCCP disconnected
13-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

abnormally, the CS channel forcibly released by the PS channel, board faults, BTS faults, eMLPP forced handovers, BCCH switchovers, BTS ring network switchovers, blocked radio channels or Abis. Currently, the other causes refer to abnormal instances or waste instance recycle.

Usage
This counter is used to know the calldrop frequency on the TCH/F signaling channel due to the other causes.

Measurement Point
This counter counts the number of calldrops when the instances on the TCH/F channel are abnormal or the waste instances on the TCH/F channel are recycled.

Unit
Times

13.14 C901070015 Number of voice TCH/F drops due to loss of contact with RANA
Definition
Number of voice 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 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
This counter is used to find out the frequency of failures due to RANCS losing contact with 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.
13-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

RANCS forwards EST_IND message to RANA after receiving it on TCH/F voice channel; if no link establishment message on A-interface from RANA is received, the counter increments; meanwhile, BSC releases the channel and instance, the measurement point is A, as shown in Figure 13-11.

Figure 13-11 Call Drop Due To A-Interface Failure In Assignment Process

Unit
Times

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

13.15 C901070017 Number of voice TCH/F drops due to LAPD link failure
Definition
Number of voice TCH/F drops due to LAPD link failure

13-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of call drop due to LAPD link failures (on TCH/F voice channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F voice channel is caused by LAPD link failures.

Usage
This counter is used to find out the frequency of call drop due to LAPD link failures (on 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-12.
Figure 13-12 Call Drop Due To LAPD Link Failure In Assignment Process

Unit
Times

13-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

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

13.16 C901070018 Number of voice TCH/F drops due to OMC-R forced release
Definition
Number of voice 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 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
This counter is used to find out the frequency of call drop due to OMC-R forced releases (on TCH/F voice channel).

Measurement Point
The counter increments when BSC receives OMC-R forced release message from database on TCH/F voice channel. The measurement point is A, as shown in Figure 13-13.

13-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-13 Call Drop Due To OMC-R Forced Release In Assignment Process

Unit
Times

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

13.17 C901070019 Number of voice TCH/F drops due to forced release by other calls
Definition
Number of voice TCH/F drops due to forced release by other calls

13-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Description
This counter counts the number of call drop due to forced releases by other calls (on TCH/F voice channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F voice channel is caused by forced releases by other calls.

Usage
This counter is used to find out the frequency of call drop due to forced releases by other calls (on TCH/F voice channel).

Measurement Point
The counter increments when BSC receives forced release message from other calls on TCH/F voice channel. The measurement point is A, as shown in Figure 13-14.
Figure 13-14 Call Drop Due To Forced Release By Other Calls In Assignment Process

Unit
Times

13-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

13.18 C901070021 Number of voice TCH/F drops due to other failure

Definition
Number of voice TCH/F drops due to other failure

Description
This counter counts the number of calldrops on the TCH/F voice channel during the call establishment due to other causes. The calldrops occur after the MS successfully applies for the TCH/F voice channel. This counter is incremented by one if the calldrops are due to the other causes, rather than due to the disconnection from RANA, radio link failures, LAPD link failures, OMCR forced releases, other call forced releases, handover failures, SCCP disconnected abnormally, the CS channel forcibly released by the PS channel, board faults, BTS faults, eMLPP forced handovers, local switching function disabled, reassignment failures, ground circuit faults, BCCH switchovers, SD changeovers, BTS ring network switchovers, blocked radio channels or Abis. Currently, the other causes refer to abnormal instances or waste instance recycle.

Usage
This counter is used to know the calldrop frequency on the TCH/F voice channel due to the other causes.

Measurement Point
This counter counts the number of calldrops when the instances on the TCH/F channel are abnormal or the waste instances on the TCH/F channel are recycled.

Unit
Times

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
13-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Description
This counter counts the number of failures due to RANCS losing contact with RANA (on TCH/F data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F data channel is caused by failures due to RANCS losing contact with RANA (on TCH/F data channel).

Usage
This counter is used to find out the frequency of failures due to RANCS losing contact with 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, 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 A, as shown in Figure 13-15. 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.

13-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-15 Call Drop Due To A-Interface Failure In Assignment Process

Unit
Times

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

13.20 C901070023 Number of data TCH/F drops due to radio link failure
Definition
Number of data TCH/F drops due to radio link failure

Description
This counter counts the number of call drop due to radio link failures (on TCH/F data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F data channel is caused by radio link failures.

13-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

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
The counter increments when BSC receives CONNectiOn FAILure INDicatiOn message on Abis interface on TCH/F data channel. The measurement point is A, as shown in Figure 13-16.
Figure 13-16 Call Drop Due To Radio Link Failure In Assignment Process

Unit
Times

Related Features
ZGB-06-01-001 Monitoring Um Interface ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-04-02-007 AMR Radio Link Timers
13-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.21 C901070024 Number of data TCH/F drops due to LAPD link failure
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 channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F data channel is caused by LAPD link failures.

Usage
This counter is used to find out the frequency of call drop due to LAPD link failures (on 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-17.

13-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-17 Call Drop Due To Lapd Link Failure In Assignment Process

Unit
Times

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

13.22 C901070025 Number of data TCH/F drops due to OMC-R forced release
Definition
Number of data TCH/F drops due to OMC-R forced release

13-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of call drop due to OMC-R forced releases (on TCH/F data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F data channel is caused by OMC-R forced releases.

Usage
This counter is used to find out the frequency of call drop due to OMC-R forced releases (on TCH/F data channel).

Measurement Point
The counter increments when BSC receives OMC-R forced release message from database on TCH/F data channel. The measurement point is A, as shown in Figure 13-18.
Figure 13-18 Call Drop Due To OMC-R Forced Release In Assignment Process

Unit
Times

13-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

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

13.23 C901070026 Number of data TCH/F drops due to forced release by other calls
Definition
Number of data 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 data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F data channel is caused by forced releases by other calls.

Usage
This counter is used to find out the frequency of call drop due to forced releases by other calls (on TCH/F data channel).

Measurement Point
The counter increments when BSC receives forced release message from other calls on TCH/F data channel. The measurement point is A, as shown in Figure 13-19.

13-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-19 Call Drop Due To Forced Release By Other Calls In Assignment Process

Unit
Times

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

13.24 C901070028 Number of data TCH/F drops due to other failure

Definition
Number of data TCH/F drops due to other failure

Description
This counter counts the number of calldrops on the TCH/F data channel due to other causes.
13-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

The calldrops occur after the MS successfully applies for the TCH/F data channel. This counter is incremented by one if the calldrops are due to the other causes, rather than due to the disconnection from RANA, radio link failures, LAPD link failures, OMCR forced releases, other call forced releases, handover failures, SCCP disconnected abnormally, board faults, BTS faults, eMLPP forced handovers, ground circuit faults, BCCH switchovers, SD changeovers, BTS ring network switchovers, blocked radio channels or Abis. Currently, the other causes refer to abnormal instances or waste instance recycle.

Usage
This counter is used to know the calldrop frequency on the TCH/F data channel due to the other causes.

Measurement Point
This counter counts the number of calldrops when the instances on the TCH/F channel are abnormal or the waste instances on the TCH/F channel are recycled.

Unit
Times

13.25 C901070029 Number of signaling TCH/H drops due to loss of contact with RANA
Definition
Number of signaling TCH/H 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/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
This counter is used to find out the frequency of failures due to RANCS losing contact with RANA (on TCH/H signaling channel).

Measurement Point
The counter counts the number of failures due to loss of contact with RANA (on TCH/H signaling channel) in the following two cases:
13-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-20. 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 point is A2, as shown in Figure 13-20.

Figure 13-20 Call Drop Due To A-Interface Failure In Immediate Assignment Process

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

13.26 C901070030 Number of signaling TCH/H drops 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 channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H signaling channel is caused by radio link failures.

13-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Usage
This counter is used to find out the frequency of call drop due to radio link failures (on TCH/H signaling channel).

Measurement Point
The counter increments when BSC receives CONNectiOn FAILure INDicatiOn message on Abis interface on TCH/H signaling channel. The measurement point is A, as shown in Figure 13-21.
Figure 13-21 Call Drop Due To Radio Link Failure In Immediate Assignment Process

Unit
Times

Related Features
ZGB-06-01-001 Monitoring Um Interface ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-04-02-007 AMR Radio Link Timers

13.27 C901070031 Number of signaling TCH/H drops due to LAPD link failure
Definition
Number of signaling TCH/H drops due to LAPD link failure

13-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of call drop due to LAPD link failures (on TCH/H signaling channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H signaling channel is caused by LAPD link failures.

Usage
This counter is used to find out the frequency of call drop due to LAPD link failures (on 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-22.
Figure 13-22 Call Drop Due To LAPD Link Failure In Immediate Assignment Process

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

13.28 C901070032 Number of signaling TCH/H drops due to OMC-R forced release
Definition
Number of signaling TCH/H drops due to OMC-R forced release
13-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Description
This counter counts the number of call drop due to OMC-R forced releases (on TCH/H signaling channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H signaling channel is caused by OMC-R forced releases.

Usage
This counter is used to find out the frequency of call drop due to OMC-R forced releases (on TCH/H signaling channel).

Measurement Point
The counter increments when BSC receives OMC-R forced release message from database on TCH/H signaling channel. The measurement point is A, as shown in Figure 13-23.
Figure 13-23 Call Drop Due To OMC-R Forced Release In Immediate Assignment Process

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

13.29 C901070033 Number of signaling TCH/H drops due to forced release by other calls
Definition
Number of signaling TCH/H drops due to forced release by other calls
13-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of call drop due to forced releases by other calls (on TCH/H signaling channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H signaling channel is caused by forced releases by other calls.

Usage
This counter is used to find out the frequency of call drop due to forced releases by other calls (on TCH/H signaling channel).

Measurement Point
The counter increments when BSC receives forced release message from other calls on TCH/H signaling channel. The measurement point is A, as shown in Figure 13-24.
Figure 13-24 Call Drop Due To Forced Release By Other Calls In Immediate Assignment Process

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

13.30 C901070035 Number of signaling TCH/H drops due to other failure

Definition
Number of signaling TCH/H drops due to other failure

13-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Description
This counter counts the number of calldrops on the TCH/H signaling channel due to other causes. The calldrops occur after the MS successfully applies for the TCH/H signaling channel. This counter is incremented by one if the calldrops are due to the other causes, rather than due to the disconnection from RANA, radio link failures, LAPD link failures, OMCR forced releases, other call forced releases, handover failures, SCCP disconnected abnormally, the CS channel forcibly released by the PS channel, board faults, BTS faults, eMLPP forced handovers, BCCH switchovers, BTS ring network switchovers, blocked radio channels or Abis. Currently, the other causes refer to abnormal instances or waste instance recycle.

Usage
This counter is used to know the calldrop frequency on the TCH/H signaling channel due to the other causes.

Measurement Point
This counter counts the number of calldrops when the instances on the TCH/H channel are abnormal or the waste instances on the TCH/H channel are recycled.

Unit
Times

13.31 C901070036 Number of voice TCH/H drops due to loss of contact with RANA
Definition
Number of voice TCH/H 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/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
This counter is used to find out the frequency of failures due to RANCS losing contact with RANA (on TCH/H voice channel).

13-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts the number of failures due to loss of contact with RANA (on TCH/H voice channel) in the following two cases: l After link between RANCS and RANA has been established on TCH/H 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. RANCS forwards EST_INDmessage to RANA after receiving it on TCH/H voice channel; if no link establishment message on A-interface from RANA is received, the counter increments; meanwhile, BSC releases the channel and instance, the measurement point is A, as shown in Figure 13-25.
Figure 13-25 Call Drop Due To A-Interface Failure In Assignment Process

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
13-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.32 C901070038 Number of voice TCH/H drops due to LAPD link failure
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 channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H voice channel 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 TCH/H voice channel).

Measurement Point
The counter increments when BSC receives DLREL_IND message from LAPD on TCH/H voice channel. The measurement point is A, as shown in Figure 13-26.

13-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-26 Call Drop Due To LAPD Link Failure In Assignment Process

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

13.33 C901070039 Number of voice TCH/H drops due to OMC-R forced release
Definition
Number of voice TCH/H drops due to OMC-R forced release

13-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Description
This counter counts the number of call drop due to OMC-R forced releases (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 OMC-R forced releases.

Usage
This counter is used to find out the frequency of call drop due to OMC-R forced releases (on TCH/H voice channel).

Measurement Point
The counter increments when BSC receives OMC-R forced release message from database on TCH/H voice channel. The measurement point is A, as shown in Figure 13-27.
Figure 13-27 Call Drop Due To OMC-R Forced Release In Assignment Process

Unit
Times
13-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

13.34 C901070040 Number of voice TCH/H drops due to forced release by other calls
Definition
Number of voice 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 voice channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H voice channel is caused by forced releases by other calls.

Usage
This counter is used to find out the frequency of call drop due to forced releases by other calls (on TCH/H voice channel).

Measurement Point
The counter increments when BSC receives forced release message from other calls on TCH/H voice channel. The measurement point is A, as shown in Figure 13-28.

13-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-28 Call Drop Due To Forced Release By Other Calls In Assignment Process

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

13.35 C901070042 Number of voice TCH/H drops due to other failure

Definition
Number of voice TCH/H drops due to other failure

13-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of calldrops on the TCH/H voice channel due to other causes. The calldrops occur after the MS successfully applies for the TCH/H voice channel. This counter is incremented by one if the calldrops are due to the other causes, rather than due to the disconnection from RANA, radio link failures, LAPD link failures, OMCR forced releases, other call forced releases, handover failures, SCCP disconnected abnormally, the CS channel forcibly released by the PS channel, board faults, BTS faults, eMLPP forced handovers, local switching function disabled, reassignment failures, ground circuit faults, BCCH switchovers, SD changeovers, BTS ring network switchovers, blocked radio channels or Abis. Currently, the other causes refer to abnormal instances or waste instance recycle.

Usage
This counter is used to know the calldrop frequency on the TCH/H voice channel due to the other causes.

Measurement Point
This counter counts the number of calldrops when the instances on the TCH/H channel are abnormal or the waste instances on the TCH/H channel are recycled.

Unit
Times

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
This counter counts the number of failures due to RANCS losing contact with RANA (on TCH/H data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H data channel is caused by failures due to RANCS losing contact with RANA (on TCH/H data channel).

Usage
This counter is used to find out the frequency of failures due to RANCS losing contact with RANA (on TCH/H data channel).
13-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Measurement Point
The counter counts the number of failures due to loss of contact with RANA (on TCH/H data channel) in the following two cases: l After link between RANCS and RANA has been established on TCH/H data 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. RANCS forwards EST_IND message to RANA after receiving it on TCH/H data channel; if no link establishment message on A-interface from RANA is received, the counter increments; meanwhile, BSC releases the channel and instance, the measurement point is A, as shown in Figure 13-29.
Figure 13-29 Call Drop Due To A-Interface Failure In Assignment Process

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
13-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.37 C901070044 Number of data TCH/H drops due to radio link failure
Definition
Number of data TCH/H drops due to radio link failure

Description
This counter counts the number of call drop due to radio link failures (on TCH/H data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H data channel 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/H data channel).

Measurement Point
The counter increments when BSC receives CONNectiOn FAILure INDicatiOn message on Abis interface on TCH/H data channel. The measurement point is A, as shown in Figure 13-30.

13-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-30 Call Drop Due To Radio Link Failure In Assignment Process

Unit
Times

Related Features
ZGB-06-01-001 Monitoring Um Interface ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-04-02-007 AMR Radio Link Timers

13.38 C901070045 Number of data TCH/H drops due to LAPD link failure
Definition
Number of data TCH/H drops due to LAPD link failure
13-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of call drop due to LAPD link failures (on TCH/H data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H data channel is caused by LAPD link failures.

Usage
This counter is used to find out the frequency of call drop due to LAPD link failures (on TCH/H data channel).

Measurement Point
The counter increments when BSC receives DLREL_IND message from LAPD on TCH/H data channel. The measurement point is A, as shown in Figure 13-31.
Figure 13-31 Call Drop Due To LAPD Link Failure In Assignment Process

Unit
Times

13-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

13.39 C901070046 Number of data TCH/H drops due to OMC-R forced release
Definition
Number of data 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 data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H data channel 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 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-32.

13-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-32 Call Drop Due To Omc-R Forced Release In Assignment Process

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

13.40 C901070047 Number of data TCH/H drops due to forced release by other calls
Definition
Number of data TCH/H drops due to forced release by other calls

13-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Description
This counter counts the number of call drop due to forced releases by other calls (on TCH/H data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H data channel is caused by forced releases by other calls.

Usage
This counter is used to find out the frequency of call drop due to forced releases by other calls (on TCH/H data channel).

Measurement Point
The counter increments when BSC receives forced release message from other calls on TCH/H data channel. The measurement point is A, as shown in Figure 13-33.
Figure 13-33 Call Drop Due To Forced Release By Other Calls In Assignment Process

Unit
Times

13-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

13.41 C901070049 Number of data TCH/H drops due to other failure

Definition
Number of data TCH/H drops due to other failure

Description
This counter counts the number of calldrops on the TCH/H data channel due to other causes. The calldrops occur after the MS successfully applies for the TCH/H data channel. This counter is incremented by one if the calldrops are due to the other causes, rather than due to the disconnection from RANA, radio link failures, LAPD link failures, OMCR forced releases, other call forced releases, handover failures, SCCP disconnected abnormally, the CS channel forcibly released by the PS channel, board faults, BTS faults, eMLPP forced handovers, BCCH switchovers, SD changeovers, BTS ring network switchovers, blocked radio channels or Abis. Currently, the other causes refer to abnormal instances or waste instance recycle.

Usage
This counter is used to know the calldrop frequency on the TCH/H data channel due to the other causes.

Measurement Point
This counter counts the number of calldrops when the instances on the TCH/H channel are abnormal or the waste instances on the TCH/H channel are recycled.

Unit
Times

13.42 C901070053 Number of SDCCH link failures

Definition
Number of SDCCH link failures

13-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

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-34.
Figure 13-34 Call Drop Due To Sccp Failure In Immediate Assignment Process

l l l

T9104 is overtime and the number of maximum failure times is reached, the measurement point is A3, as shown in Figure 13-34. T9101 is overtime, the measurement point is A4, as shown in Figure 13-34. After RANA process has been established, EST_IND message sent by MS or handover request sent by MSC is not received within the set time, the measurement point is A1, as shown in Figure 13-34. BSC receives MSC reset message.
13-55

SJ-20110531095035-015|2013-04-25 (R1.7)

ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

l l

CONNECT_ID requested by RANA is failed. 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 RANA launches abnormal release flow to RANCS due to SCCP link failure after MS has obtained TCH/F.

Usage
This counter is used to find out the frequency of TCH/F link failures.

Measurement Point
The counter counts the number of abnormal release flow launched by RANA to RANCS due to SCCP link failure on TCH/F in the following cases: l T9105 is overtime, the measurement point is A2, as shown in Figure 13-35.

13-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-35 Call Drop Due To Sccp Failure In Immediate Assignment Process

l l l

l l l

T9104 is overtime and the number of maximum failure times is reached, the measurement point is A3, as shown in Figure 13-35. T9101 is overtime, the measurement point is A4, as shown inFigure 13-35. After RANA process has been established, EST_IND message sent by MS or handover request sent by MSC is not received within the set time, the measurement point is A1, as shown in Figure 13-35. BSC receives MSC reset message. CONNECT_ID requested by RANA is failed. BSC receives link release command from MSC.

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

13-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 RANA launches abnormal release flow to RANCS due to SCCP link failure after MS has obtained TCH/H.

Usage
This counter is used to find out the frequency of TCH/H link failures.

Measurement Point
The counter counts the number of abnormal release flow launched by RANA to RANCS due to SCCP link failure on TCH/H in the following cases: l T9105 is overtime, the measurement point is A2, as shown in Figure 13-36.
Figure 13-36 Call Drop Due To SCCP Failure In Immediate Assignment Process

13-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

l l l

l l l

T9104 is overtime and the number of maximum failure times is reached, the measurement point is A3, as shown in Figure 13-36. T9101 is overtime, the measurement point is A4, as shown in Figure 13-36. After RANA process has been established, EST_IND message sent by MS or handover request sent by MSC is not received within the set time, the measurement point is A1, as shown in Figure 13-36. BSC receives MSC reset message. CONNECT_ID requested by RANA is failed. BSC receives link release command from MSC.

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

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. measurement point is A2, as shown in Figure 13-37. The

13-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-37 Call Drop Due To Inter-BSC Handover Failure

Unit
Times

13.46 C901070057 Number of RANA link releases due 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 that SCCP link release command message is received). The counter increments if RANA link release occurs after MS has obtained TCH/F.

Usage
This counter is used to find out the frequency of RANA link releases by other cause on TCH/F.

Measurement Point
The counter increments when the content of HO_REQ message is incorrect. measurement point is A2, as shown in Figure 13-38. The

13-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-38 Call Drop Due To Inter-BSC Handover Failure

Unit
Times

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

13.47 C901070058 Number of RANA link releases due 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 that SCCP link release command message is received). The counter increments if RANA link release occurs after MS has obtained TCH/H.

Usage
This counter is used to find out the frequency of RANA link releases by other cause on TCH/H.

Measurement Point
The counter increments when the content of HO_REQ message is incorrect. measurement point is A2, as shown in Figure 13-39. The

13-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-39 Call Drop Due To Inter-BSC Handover Failure

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

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-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

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

Related Features
ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation

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-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

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
ZGO-03-02-004 HR Concentration

13-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

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
ZGO-03-02-004 HR Concentration

13.53 C901070064 Number of SDCCH drops due to eMLPP forced handover

Definition
Number of SDCCH drops due to eMLPP forced handover

Description
This counter counts the number of call drops on SDCCH due to eMLPP forced handover. After MS obtains SDCCH, call drop occurs. If the problem is caused by eMLPP forced handover, the counter increments.

Usage
This counter is used to find out the frequency of call drop on SDCCH due to eMLPP forced handover.
13-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on SDCCH. The measurement point is A, as shown in Figure 13-40.
Figure 13-40 Measurement Point Of Number Of SDCCH Drops Due To eMLPP Forced Handover

Unit
Times

13.54 C901070065 Number of signaling TCH/F drops 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-41.

13-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-41 Measurement Point Of Number Of SDCCH Drops Due To eMLPP Forced Handover

Unit
Times

13.55 C901070066 Number of voice TCH/F drops due 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 eMLPP forced handover, the counter increments.

Usage
This counter is used to find out the frequency of call drop on voice TCH/F due to eMLPP forced handover.

Measurement Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on voice TCH/F. The measurement point is A, as shown in Figure 13-42.

13-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-42 Measurement Point Of Number Of SDCCH Drops Due To eMLPP Forced Handover

Unit
Times

13.56 C901070067 Number of data TCH/F drops due to eMLPP forced handover
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 eMLPP forced handover, the counter increments.

Usage
This counter is used to find out the frequency of call drop on data TCH/F due to eMLPP forced handover.

Measurement Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on data TCH/F. The measurement point is A, as shown in Figure 13-43.

13-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-43 Measurement Point Of Number Of SDCCH Drops Due To eMLPP Forced 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-44.

13-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-44 Measurement Point Of Number Of SDCCH Drops Due To eMLPP Forced Handover

Unit
Times

13.58 C901070069 Number of voice TCH/H drops due to eMLPP forced handover
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 eMLPP forced handover, the counter increments.

Usage
This counter is used to find out the frequency of call drop on voice TCH/H due to eMLPP forced handover.

Measurement Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on voice TCH/H. The measurement point is A, as shown in Figure 13-45.

13-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-45 Measurement Point Of Number Of SDCCH Drops Due To eMLPP Forced Handover

Unit
Times

13.59 C901070070 Number of data TCH/H drops due to eMLPP forced handover
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 eMLPP forced handover, the counter increments.

Usage
This counter is used to find out the frequency of call drop on data TCH/H due to eMLPP forced handover.

Measurement Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on data TCH/H. The measurement point is A, as shown in Figure 13-46.

13-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-46 Measurement Point Of Number Of SDCCH Drops Due To eMLPP Forced 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, the counter increments.

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

13-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-47 Call Drop Due To Radio Link Failure In Immediate Assignment Process

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
This counter is used to find out the frequency of call drop on SDCCH due to radio link failure which is caused by bad downlink 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-48.

13-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-48 Call Drop Due To Radio Link Failure In Immediate Assignment Process

Unit
Times

13.62 C901070073 Lower electrical level of UL (On SDCCH)

Definition
Lower electrical level of UL (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 uplink receiving level, the counter increments.

Usage
This counter is used to find out the frequency of call drop on SDCCH due to radio link failure which is caused by low uplink receiving level.

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

13-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-49 Call Drop Due To Radio Link Failure In Immediate Assignment Process

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
This counter is used to find out the frequency of call drop on SDCCH due to radio link failure which is caused by low downlink receiving level.

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

13-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-50 Call Drop Due To Radio Link Failure In Immediate Assignment Process

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
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 TA being too far, the counter increments.

Usage
This counter is used to find out the frequency of call drop on SDCCH due to radio link failure which is caused by TA being too far.

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

13-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-51 Call Drop Due To Radio Link Failure In Immediate Assignment Process

Unit
Times

13.65 C901070076 Reasons of the other radios (On SDCCH)

Definition
Reasons of the other radios (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 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
This counter is used to find out the frequency of call drop on SDCCH due to radio link failure which is caused by other radio problems.

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

13-77 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-52 Call Drop Due To Radio Link Failure In Immediate Assignment Process

Unit
Times

13.66 C901070077 Bad quality of UL receiving (On TCH/F)

Definition
Bad quality of UL receiving (On TCH/F)

Description
This counter counts the number of call drops on TCH/F due to radio link failure. After MS obtains TCH/F, call drop occurs. If the problem is caused by bad uplink receiving quality, the counter increments.

Usage
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
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH/F. The measurement point is A, as shown in Figure 13-53.

13-78 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-53 Call Drop Due To Radio Link Failure In Immediate Assignment Process

Unit
Times

13.67 C901070078 Bad quality of DL receiving (On TCH/F)

Definition
Bad quality of DL 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 downlink receiving quality, the counter increments.

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 downlink receiving quality.

Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH/F. The measurement point is A, as shown in Figure 13-54.

13-79 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-54 Call Drop Due To Radio Link Failure In Assignment Process

Unit
Times

13.68 C901070079 Lower electrical level of UL (On TCH/F)

Definition
Lower electrical level of UL (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 low uplink receiving level, the counter increments.

13-80 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

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 low uplink receiving level.

Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH/F. The measurement point is A, as shown in Figure 13-55.
Figure 13-55 Call Drop Due To Radio Link Failure In Assignment Process

Unit
Times

13-81 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.69 C901070080 Lower electrical level of DL (On TCH/F)

Definition
Lower electrical level of DL (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 low downlink receiving level, the counter increments.

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 low downlink receiving level.

Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH/F. The measurement point is A, as shown in Figure 13-56.

13-82 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-56 Call Drop Due To Radio Link Failure In Assignment Process

Unit
Times

13.70 C901070081 Number of signaling drops due to TA too far (On TCH/F)
Definition
Number of signaling drops due to TA too far (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 TA being too far, the counter increments.

13-83 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 TA being too far.

Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH/F. The measurement point is A, as shown in Figure 13-57.
Figure 13-57 Call Drop Due To Radio Link Failure In Assignment Process

Unit
Times

13-84 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.71 C901070082 Reasons of the other radios (On TCH/F)

Definition
Reasons of the other radios (On TCH/F)

Description
This counter counts the number of call drops on TCH/F due to radio link failure. After MS obtains TCH/F, call drop occurs. If the 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
This counter is used to find out the frequency of call drop on TCH/F due to radio link failure which is caused by other radio problems.

Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH/F. The measurement point is A, as shown in Figure 13-58.

13-85 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-58 Call Drop Due To Radio Link Failure In Assignment Process

Unit
Times

13.72 C901070083 Bad quality of UL receiving (On TCH/H)

Definition
Bad quality of UL receiving (On TCH/H)

Description
This counter counts the number of call drops on TCH/H due to radio link failure. After MS obtains TCH/H, call drop occurs. If the problem is caused by bad uplink receiving quality, the counter increments.

13-86 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

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
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH/H. The measurement point is A, as shown in Figure 13-59.
Figure 13-59 Call Drop Due To Radio Link Failure In Assignment Process

Unit
Times

13-87 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.73 C901070084 Bad quality of DL receiving (On 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
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 downlink receiving quality.

Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH/H. The measurement point is A, as shown in Figure 13-60.

13-88 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-60 Call Drop Due To Radio Link Failure In Assignment Process

Unit
Times

13.74 C901070085 Lower electrical level of UL (On TCH/H)

Definition
Lower electrical level of UL (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 low uplink receiving level, the counter increments.

13-89 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 low uplink receiving level.

Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH/H. The measurement point is A, as shown in Figure 13-61.
Figure 13-61 Call Drop Due To Radio Link Failure In Assignment Process

Unit
Times

13-90 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.75 C901070086 Lower electrical level of DL (On TCH/H)

Definition
Lower electrical level of DL (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 low downlink receiving level, the counter increments.

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 low downlink receiving level.

Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH/H. The measurement point is A, as shown in Figure 13-62.

13-91 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-62 Call Drop Due To Radio Link Failure In Assignment Process

Unit
Times

13.76 C901070087 Number of signaling drops due to TA too far (On TCH/H)
Definition
Number of signaling drops due to TA too far (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 TA being too far, the counter increments.

13-92 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

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 TA being too far.

Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH/H. The measurement point is A, as shown in Figure 13-63.
Figure 13-63 Call Drop Due To Radio Link Failure In Assignment Process

Unit
Times

13-93 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.77 C901070088 Reasons of the other radios (On TCH/H)

Definition
Reasons of the other radios (On TCH/H)

Description
This counter counts the number of call drops on TCH/H due to radio link failure. After MS obtains TCH/H, call drop occurs. If the problem is not due to the above five causes (i.e. bad uplink receiving quality, bad downlink receiving quality, low uplink receiving level, low downlink receiving level, and TA being too far), the counter increments.

Usage
This counter is used to find out the frequency of call drop on TCH/H due to radio link failure which is caused by other radio problems.

Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH/H. The measurement point is A, as shown in Figure 13-64.

13-94 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-64 Call Drop Due To Radio Link Failure In Assignment Process

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-65.
13-95 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-65 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. This counter is supported in version V6.20.200a or above.

13-96 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

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

13.80 C901070091 Number of FR_V2 radio link fail

Description
This counter counts the number of full-rate version 2 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 2, then the counter increments.

Usage
This counter is used to find out the number of call drops due to full-rate version 2 radio link failures on TCH/F. This counter is supported in version V6.20.200a or above.

Measurement Point
When BSC receives the AbisConnectFailureIndication message from BTS, if the voice version used is full-rate voice version 2, then the counter counts.

Unit
Times

13.81 C901070092 Number of FR_V3 radio link fail

Description
This counter counts the number of full-rate version 3 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 3, then the counter increments.

Usage
This counter is used to find out the number of call drops due to full-rate version 3 radio link failures on TCH/F. This counter is supported in version V6.20.200a or above.

13-97 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC receives the AbisConnectFailureIndication message from BTS, if the voice version used is full-rate voice version 3, then the counter counts.

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 BSC receives the AbisConnectFailureIndication message from BTS, it judges the voice 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. This counter is supported in version V6.20.200a or above.

Measurement Point
When BSC receives the AbisConnectFailureIndication message from BTS, if the voice 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 BSC receives the AbisConnectFailureIndication message from BTS, it judges the voice 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. This counter is supported in version V6.20.200a or above.

13-98 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Measurement Point
When BSC receives the AbisConnectFailureIndication message from BTS, if the voice version used is half-rate voice version 3, then the counter counts.

Unit
Times

13.84 C901070095 Number of signaling TCH/F drops due to BIPB Active/Standby Changeover
Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is FORCE_REL_BIPBEXCH. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13.85 C901070096 Number of voice TCH/F drops due to BIPB Active/Standby Changeover
Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is FORCE_REL_BIPBEXCH. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13-99 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.86 C901070097 Number of data TCH/F drops due to BIPB Active/Standby Changeover
Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is FORCE_REL_BIPBEXCH. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13.87 C901070098 Number of signaling TCH/H drops due to BIPB Active/Standby Changeover
Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is FORCE_REL_BIPBEXCH. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13.88 C901070099 Number of voice TCH/H drops due to BIPB Active/Standby Changeover
Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is FORCE_REL_BIPBEXCH. This counter is supported in version V6.20.614b.

13-100 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Unit
Times

Statistics Object
Cell

13.89 C901070100 Number of data TCH/H drops due to BIPB Active/Standby Changeover
Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is FORCE_REL_BIPBEXCH. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13.90 C901070101 Number of SDCCH drops due to LAPD Active/Standby Changeover

Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is CAUSE_LAPDEXCH. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13-101 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.91 C901070102 Number of voice TCH/F drops due to LAPD Active/Standby Changeover
Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is CAUSE_LAPDEXCH. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13.92 C901070103 Number of data TCH/F drops due to LAPD Active/Standby Changeover
Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is CAUSE_LAPDEXCH. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13.93 C901070104 Number of signaling TCH/F drops due to LAPD Active/Standby Changeover
Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is CAUSE_LAPDEXCH. This counter is supported in version V6.20.614b.

13-102 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Unit
Times

Statistics Object
Cell

13.94 C901070105 Number of voice TCH/H drops due to LAPD Active/Standby Changeover
Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is CAUSE_LAPDEXCH. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13.95 C901070106 Number of data TCH/H drops due to LAPD Active/Standby Changeover
Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is CAUSE_LAPDEXCH. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13-103 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.96 C901070107 Number of signaling TCH/H drops due to LAPD Active/Standby Changeover
Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is CAUSE_LAPDEXCH. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13.97 C901070108 Number of voice TCH/F drops due to handover fail for power adjustment
Description
After the power sharing function is enabled, if power congestion occurs, the power congestion control algorithm of CS outgoing handover is executed. If the handover fails and if the current channel is FR, the counter increments. This counter is supported in version V6.20.611f.

Unit
Times

Statistics Object
Cell

13.98 C901070109 Number of voice TCH/H drops due to handover fail for power adjustment
Description
After the power sharing function is enabled, if power congestion occurs, the power congestion control algorithm of CS outgoing handover is executed. If the handover fails and if the current channel is HR, the counter increments. This counter is supported in version V6.20.611f.
13-104 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Unit
Times

Statistics Object
Cell

13.99 C901070110 Number of SDCCH drops due to BIPB Active/Standby Changeover

Description
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is FORCE_REL_BIPBEXCH. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13.100 C901070111 Number of SDCCH drops due to BTS failure

Description
This counter counts the number of call drops on SDCCH due to BTS fault. The counter has two measurement points: When BSC receives the ConnectionFailure message and the cause is "O&M intervention", if the service is on SDCCH, the counter increments. The measurement point is A, as shown in Figure 13-66.

13-105 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-66 Call Drop during Immediate Assignment due to BTS Fault

When BSC receives the O&M status report message from BTS and the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on SDCCH, the counter increments. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13.101 C901070112 Number of signaling TCH/F drops due to BTS failure

Description
This counter counts the number of call drops on signaling TCH/F due to BTS fault. The counter has two measurement points: When BSC receives the ConnectionFailure message and the cause is "O&M intervention", if the service is on signaling TCH/F, the counter increments. The measurement point is A, as shown in Figure 13-67. When BSC receives the O&M status report message from BTS and the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on signaling TCH/F, the counter increments.

13-106 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-67 Call Drop during Immediate Assignment due to BTS Fault

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13.102 C901070113 Number of voice TCH/F drops due to BTS failure

Description
This counter counts the number of call drops on voice TCH/F due to BTS fault. The counter has two measurement points: When BSC receives the ConnectionFailure message and the cause is "O&M intervention", if the service is on voice TCH/F, the counter increments. The measurement point is A, as shown in Figure 13-68.

13-107 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 13-68 Call Drop during Assignment due to BTS Fault

When BSC receives the O&M status report message from BTS and the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on voice TCH/F, the counter increments. This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13.103 C901070114 Number of data TCH/F drops due to BTS failure

Description
This counter counts the number of call drops on data TCH/F due to BTS fault. The counter has two measurement points:
13-108 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

When BSC receives the ConnectionFailure message and the cause is "O&M intervention", if the service is on data TCH/F, the counter increments. The measurement point is A, as shown in Figure 13-69. When BSC receives the O&M status report message from BTS and the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on data TCH/F, the counter increments.
Figure 13-69 Call Drop during Assignment due to BTS Fault

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13-109 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.104 C901070115 Number of signaling TCH/H drops due to BTS failure

Description
This counter counts the number of call drops on signaling TCH/H due to BTS fault. The counter has two measurement points: When BSC receives the ConnectionFailure message and the cause is "O&M intervention", if the service is on signaling TCH/H, the counter increments. The measurement point is A, as shown in Figure 13-70. When BSC receives the O&M status report message from BTS and the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on signaling TCH/H, the counter increments.
Figure 13-70 Call Drop during Assignment due to BTS Fault

This counter is supported in version V6.20.614b.

Unit
Times
13-110 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Statistics Object
Cell

13.105 C901070116 Number of voice TCH/H drops due to BTS failure

Description
This counter counts the number of call drops on voice TCH/H due to BTS fault. The counter has two measurement points: When BSC receives the ConnectionFailure message and the cause is "O&M intervention", if the service is on voice TCH/H, the counter increments. The measurement point is A, as shown in Figure 13-71. When BSC receives the O&M status report message from BTS and the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on voice TCH/H, the counter increments.
Figure 13-71 Call Drop during Assignment due to BTS Fault

This counter is supported in version V6.20.614b.

13-111 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Statistics Object
Cell

13.106 C901070117 Number of data TCH/H drops due to BTS failure

Description
This counter counts the number of call drops on data TCH/H due to BTS fault. The counter has two measurement points: When BSC receives the ConnectionFailure message and the cause is "O&M intervention", if the service is on data TCH/H, the counter increments. The measurement point is A, as shown in Figure 13-72. When BSC receives the O&M status report message from BTS and the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on data TCH/H, the counter increments.

13-112 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Figure 13-72 Call Drop during Assignment due to BTS Fault

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

13.107 C901070118 Call Drop by Releasing Local Switch

Description
This counter counts the number of call drops due to failure in releasing local switch. In normal cases, the call should return to the normal call status after the local switch is released. However, if fault occurs during the release, such as failure in requesting TC resource or connection failure when TC is external, the no-voice problem will occur. In

13-113 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

such cases, the service module will release the call and consider it as a call drop due to failure in releasing local switch. This counter is supported in version V6.20.614c.

Unit
Times

Statistics Object
Cell

13.108 C901070119 Number of FR_V4 Radio Link Fail

Description
This counter counts call drops due to radio link failure. During a call in steady state, the BSC considers the call dropped when an ABIS_CONNECT_FAIL_IND message is received. If Full Rate speech Version 4 (FR_V4) is used by the failed radio link, this counter is incremented.

Usage
This counter indicates the number of FR_V4 radio link failures.

Measurement Point
The call changes to steady state after the completion of assignment or handover. After that, if the ABIS_CONNECT_FAIL_IND message is received at the measurement point A (as shown in Figure 13-73), the BSC considers the call dropped due to radio link failure.
Figure 13-73 Radio Link (Speech Version) Failure

Unit
Times

13-114 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.109 C901070120 Number of FR_V5 Radio Link Fail

Description
This counter counts call drops due to radio link failure. During a call in steady state, the BSC considers the call dropped when an ABIS_CONNECT_FAIL_IND message is received. If Full Rate speech Version 5 (FR_V5) is used by the failed radio link, this counter is incremented.

Usage
This counter indicates the number of FR_V5 radio link failures.

Measurement Point
The call changes to steady state after the completion of assignment or handover. After that, if the ABIS_CONNECT_FAIL_IND message is received at the measurement point A (as shown in Figure 13-74), the BSC considers the call dropped due to radio link failure.
Figure 13-74 Radio Link (Speech Version) Failure

Unit
Times

13.110 C901070121 Number of HR_V4 Radio Link Fail

Description
This counter counts call drops due to radio link failure. During a call in steady state, the BSC considers the call dropped when an ABIS_CONNECT_FAIL_IND message is received. If Half Rate speech Version 4 (HR_V4) is used by the failed radio link, this counter is incremented.

Usage
This counter indicates the number of HR_V4 radio link failures.
13-115 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The call changes to steady state after the completion of assignment or handover. After that, if the ABIS_CONNECT_FAIL_IND message is received at the measurement point A (as shown in Figure 13-75), the BSC considers the call dropped due to radio link failure.
Figure 13-75 Radio Link (Speech Version) Failure

Unit
Times

13.111 C901070122 Call Drop Due To Emergency Call Preemption on TCH/F

Description
When connecting the emergency call, the system can directly select the number of call drops of other users if no radio resource is available. When the channel occupied by the forcedly dropped user is of the TCH/F type, this counter increases by 1.

Usage
None

Measurement Point
None

Unit
Time

13-116 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.112 C901070123 Call Drop Due to Emergency Call Preemption on TCH/H

Description
When connecting the emergency call, the system can directly select the number of call drops of other users if no radio resource is available. When the channel occupied by the forcedly dropped user is of the TCH/H type, this counter increases by 1.

Usage
None

Measurement Point
None

Unit
Time

13.113 C901070126 Number of drop call on SDCCH due to IMSI Exception

Measured Object
Cell

Description
This counter is incremented each time the SDCCH occupied by the MS is released due to IMSI conflict.

Usage
None

Measurement Point
None

Unit
Times

13-117 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.114 C901070127 Number of drop call on sig TCH/F due to IMSI Exception
Measured Object
Cell

Description
This counter is incremented each time the signaling TCH/F occupied by the MS is released due to IMSI conflict.

Usage
None

Measurement Point
None

Unit
Times

13.115 C901070128 Number of drop call on voice TCH/F due to IMSI Exception
Measured Object
Cell

Description
This counter is incremented each time the speech TCH/F occupied by the MS is released due to IMSI conflict.

Usage
None

Measurement Point
None

Unit
Times
13-118 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.116 C901070129 Number of drop call on data TCH/F due to IMSI Exception
Measured Object
Cell

Description
This counter is incremented each time the data TCH/F occupied by the MS is released due to IMSI conflict.

Usage
None

Measurement Point
None

Unit
Times

13.117 C901070130 Number of drop call on sig TCH/H due to IMSI Exception
Measured Object
Cell

Description
This counter is incremented each time the signaling TCH/H occupied by the MS is released due to IMSI conflict.

Usage
None

Measurement Point
None

Unit
Times
13-119 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.118 C901070131 Number of drop call on voice TCH/H due to IMSI Exception
Measured Object
Cell

Description
This counter is incremented each time the speech TCH/H occupied by the MS is released due to IMSI conflict.

Usage
None

Measurement Point
None

Unit
Times

13.119 C901070132 Number of drop call on data TCH/H due to IMSI Exception
Measured Object
Cell

Description
This counter is incremented each time the data TCH/H occupied by the MS is released due to IMSI conflict.

Usage
None

Measurement Point
None

Unit
Times
13-120 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.120 C901070133 Number of Drop Call When TCH Assign

Description
This counter counts call drops that occur due to a failure when an MS is tuned from an SDCCH to a TCH.

Usage
This counter indicates the number of call drops due to a failure during TCH assignment.

Measurement Point
This counter is incremented each time the BSC, after receiving an Assignment Request message from the A interface, sends a Clear Request message to the MSC due to a failure during the assignment procedure.

Unit
Times

13.121 C901070134 Number of Drop Call on TCH

Description
This counter counts call drops that occur due to all reasons after an MS seizes a voice TCH.

Usage
This counter indicates the number of call drops on TCH.

Measurement Point
This counter is incremented each time the BSC sends a Clear Request message to the MSC after an MS successfully seizes a voice TCH (meaning TCH assignment or TCH handover completed).

Unit
Times

13-121 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.122 C901070135 Number of Drop Call on TCH(exclude sms drop after hang-off)
Description
This counter counts call drops that occur due to all reasons except SMS and MS disconnection after an MS seizes a voice TCH.

Usage
This counter indicates the number of call drops on TCH, except those caused by SMS and MS disconnection.

Measurement Point
The counter value equals to the number of Clear Request messages sent by the BSC to the MSC after successful seizure of voice TCHs (meaning TCH assignment or TCH handover completed), except Clear Request messages sent after a CP-DATA message or Disconnect message is sent or reported.

Unit
Times

13.123 C901070136 Number of SDCCH Drops Due to Intra-Cell Handover Failure

Description
This counter counts SDCCH call drops caused by intra-cell handover failure.

Usage
This counter indicates the number of SDCCH call drops caused by intra-cell handover failure.

Measurement Point
Upon starting an intra-cell handover procedure on an SDCCH, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13-122 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.124 C901070137 Number of Speech TCH/F Drops Due to Intra-Cell Handover Failure
Description
This counter counts voice TCH/F call drops caused by intra-cell handover failure.

Usage
This counter indicates the number of voice TCH/F call drops caused by intra-cell handover failure.

Measurement Point
Upon starting an intra-cell handover procedure on a voice TCH/F, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13.125 C901070138 Number of Data TCH/F Drops Due to Intra-Cell Handover Failure
Description
This counter counts data TCH/F call drops caused by intra-cell handover failure.

Usage
This counter indicates the number of data TCH/F call drops caused by intra-cell handover failure.

Measurement Point
Upon starting an intra-cell handover procedure on a data TCH/F, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13-123 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.126 C901070139 Number of Signaling TCH/F Drops Due to Intra-Cell Handover Failure
Description
This counter counts signaling TCH/F call drops caused by intra-cell handover failure.

Usage
This counter indicates the number of signaling TCH/F call drops caused by intra-cell handover failure.

Measurement Point
Upon starting an intra-cell handover procedure on a signaling TCH/F, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13.127 C901070140 Number of Speech TCH/H Drops Due to Intra-Cell Handover Failure
Description
This counter counts voice TCH/H call drops caused by intra-cell handover failure.

Usage
This counter indicates the number of voice TCH/H call drops caused by intra-cell handover failure.

Measurement Point
Upon starting an intra-cell handover procedure on a voice TCH/H, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13-124 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.128 C901070141 Number of Data TCH/H Drops Due to Intra-Cell Handover Failure
Description
This counter counts data TCH/H call drops caused by intra-cell handover failure.

Usage
This counter indicates the number of data TCH/H call drops caused by intra-cell handover failure.

Measurement Point
Upon starting an intra-cell handover procedure on a data TCH/H, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13.129 C901070142 Number of Signaling TCH/H Drops Due to Intra-Cell Handover Failure
Description
This counter counts signaling TCH/H call drops caused by intra-cell handover failure.

Usage
This counter indicates the number of signaling TCH/H call drops caused by intra-cell handover failure.

Measurement Point
Upon starting an intra-cell handover procedure on a signaling TCH/H, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13-125 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.130 C901070143 Number of SDCCH Drops Due to Inter-Cell Handover Failure

Description
This counter counts SDCCH call drops caused by inter-cell handover failure.

Usage
This counter indicates the number of SDCCH call drops caused by inter-cell handover failure.

Measurement Point
Upon starting an inter-cell handover procedure on an SDCCH, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13.131 C901070144 Number of Speech TCH/F Drops Due to Inter-Cell Handover Failure
Description
This counter counts voice TCH/F call drops caused by inter-cell handover failure.

Usage
This counter indicates the number of voice TCH/F call drops caused by inter-cell handover failure.

Measurement Point
Upon starting an inter-cell handover procedure on a voice TCH/F, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13-126 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.132 C901070145 Number of Data TCH/F Drops Due to Inter-Cell Handover Failure
Description
This counter counts data TCH/F call drops caused by inter-cell handover failure.

Usage
This counter indicates the number of data TCH/F call drops caused by inter-cell handover failure.

Measurement Point
Upon starting an inter-cell handover procedure on a data TCH/F, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13.133 C901070146 Number of Signaling TCH/F Drops Due to Inter-Cell Handover Failure
Description
This counter counts signaling TCH/F call drops caused by inter-cell handover failure.

Usage
This counter indicates the number of signaling TCH/F call drops caused by inter-cell handover failure.

Measurement Point
Upon starting an inter-cell handover procedure on a signaling TCH/F, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13-127 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.134 C901070147 Number of Speech TCH/H Drops Due to Inter-Cell Handover Failure
Description
This counter counts voice TCH/H call drops caused by inter-cell handover failure.

Usage
This counter indicates the number of voice TCH/H call drops caused by inter-cell handover failure.

Measurement Point
Upon starting an inter-cell handover procedure on a voice TCH/H, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13.135 C901070148 Number of Data TCH/H Drops Due to Inter-Cell Handover Failure
Description
This counter counts data TCH/H call drops caused by inter-cell handover failure.

Usage
This counter indicates the number of data TCH/H call drops caused by inter-cell handover failure.

Measurement Point
Upon starting an inter-cell handover procedure on a data TCH/H, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13-128 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.136 C901070149 Number of Signaling TCH/H Drops Due to Inter-Cell Handover Failure
Description
This counter counts signaling TCH/H call drops caused by inter-cell handover failure.

Usage
This counter indicates the number of signaling TCH/H call drops caused by inter-cell handover failure.

Measurement Point
Upon starting an inter-cell handover procedure on a signaling TCH/H, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13.137 C901070150 Number of SDCCH Drops Due to Outgoing Handover Failure

Description
This counter counts SDCCH call drops caused by inter-BSC handover failure.

Usage
This counter indicates the number of SDCCH call drops caused by inter-BSC handover failure.

Measurement Point
This counter is incremented each time the BSC, after sending an inter-BSC handover command on an SDCCH, does not receive a clear command with handover complete information before the corresponding timer expires.

Unit
Times

13-129 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.138 C901070151 Number of Speech TCH/F Drops Due to Outgoing Handover Failure
Description
This counter counts voice TCH/F call drops caused by inter-BSC handover failure.

Usage
This counter indicates the number of voice TCH/F call drops caused by inter-BSC handover failure.

Measurement Point
This counter is incremented each time the BSC, after sending an inter-BSC handover command on a voice TCH/F, does not receive a clear command with handover complete information before the corresponding timer expires.

Unit
Times

13.139 C901070152 Number of Data TCH/F Drops Due to Outgoing Handover Failure
Description
This counter counts data TCH/F call drops caused by inter-BSC handover failure.

Usage
This counter indicates the number of data TCH/F call drops caused by inter-BSC handover failure.

Measurement Point
This counter is incremented each time the BSC, after sending an inter-BSC handover command on a data TCH/F, does not receive a clear command with handover complete information before the corresponding timer expires.

Unit
Times

13-130 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.140 C901070153 Number of Signaling TCH/F Drops Due to Outgoing Handover Failure
Description
This counter counts signaling TCH/F call drops caused by inter-BSC handover failure.

Usage
This counter indicates the number of signaling TCH/F call drops caused by inter-BSC handover failure.

Measurement Point
This counter is incremented each time the BSC, after sending an inter-BSC handover command on a signaling TCH/F, does not receive a clear command with handover complete information before the corresponding timer expires.

Unit
Times

13.141 C901070154 Number of Speech TCH/H Drops Due to Outgoing Handover Failure
Description
This counter counts voice TCH/H call drops caused by inter-BSC handover failure.

Usage
This counter indicates the number of voice TCH/H call drops caused by inter-BSC handover failure.

Measurement Point
This counter is incremented each time the BSC, after sending an inter-BSC handover command on a voice TCH/H, does not receive a clear command with handover complete information before the corresponding timer expires.

Unit
Times

13-131 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.142 C901070155 Number of Data TCH/H Drops Due to Outgoing Handover Failure
Description
This counter counts data TCH/H call drops caused by inter-BSC handover failure.

Usage
This counter indicates the number of data TCH/H call drops caused by inter-BSC handover failure.

Measurement Point
This counter is incremented each time the BSC, after sending an inter-BSC handover command on a data TCH/H, does not receive a clear command with handover complete information before the corresponding timer expires.

Unit
Times

13.143 C901070156 Number of Signaling TCH/H Drops Due to Outgoing Handover Failure
Description
This counter counts signaling TCH/H call drops caused by inter-BSC handover failure.

Usage
This counter indicates the number of signaling TCH/H call drops caused by inter-BSC handover failure.

Measurement Point
This counter is incremented each time the BSC, after sending an inter-BSC handover command on a signaling TCH/H, does not receive a clear command with handover complete information before the corresponding timer expires.

Unit
Times

13-132 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.144 C901070157 Number of Speech TCH/F Drops Due to Subcell 1 to Subcell 2 Handover Failure
Description
This counter counts voice TCH/F call drops caused by handover failure from subcell 1 to subcell 2.

Usage
This counter indicates the number of voice TCH/F call drops caused by handover failure from subcell 1 to subcell 2.

Measurement Point
Upon starting an intra-cell handover procedure on a TCH/F, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13.145 C901070158 Number of Data TCH/F Drops Due to Subcell 1 to Subcell 2 Handover Failure
Description
This counter counts data TCH/F call drops caused by handover failure from subcell 1 to subcell 2.

Usage
This counter indicates the number of data TCH/F call drops caused by handover failure from subcell 1 to subcell 2.

Measurement Point
Upon starting an intra-cell handover procedure on a TCH/F, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13-133 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.146 C901070159 Number of Signaling TCH/F Drops Due to Subcell 1 to Subcell 2 Handover Failure
Description
This counter counts signaling TCH/F call drops caused by handover failure from subcell 1 to subcell 2.

Usage
This counter indicates the number of signaling TCH/F call drops caused by handover failure from subcell 1 to subcell 2.

Measurement Point
Upon starting an intra-cell handover procedure on a TCH/F, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13.147 C901070160 Number of Speech TCH/H Drops Due to Subcell 1 to Subcell 2 Handover Failure
Description
This counter counts voice TCH/H call drops caused by handover failure from subcell 1 to subcell 2.

Usage
This counter indicates the number of voice TCH/H call drops caused by handover failure from subcell 1 to subcell 2.

Measurement Point
Upon starting an intra-cell handover procedure on a TCH/H, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13-134 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.148 C901070161 Number of Data TCH/H Drops Due to Subcell 1 to Subcell 2 Handover Failure
Description
This counter counts data TCH/H call drops caused by handover failure from subcell 1 to subcell 2.

Usage
This counter indicates the number of data TCH/H call drops caused by handover failure from subcell 1 to subcell 2.

Measurement Point
Upon starting an intra-cell handover procedure on a TCH/H, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13.149 C901070162 Number of Signaling TCH/H Drops Due to Subcell 1 to Subcell 2 Handover Failure
Description
This counter counts signaling TCH/H call drops caused by handover failure from subcell 1 to subcell 2.

Usage
This counter indicates the number of signaling TCH/H call drops caused by handover failure from subcell 1 to subcell 2.

Measurement Point
Upon starting an intra-cell handover procedure on a TCH/H, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13-135 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.150 C901070163 Number of Speech TCH/F Drops Due to Subcell 2 to Subcell 1 Handover Failure
Description
This counter counts voice TCH/F call drops caused by handover failure from subcell 2 to subcell 1.

Usage
This counter indicates the number of voice TCH/F call drops caused by handover failure from subcell 2 to subcell 1.

Measurement Point
Upon starting an intra-cell handover procedure on a TCH/F, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13.151 C901070164 Number of Data TCH/F Drops Due to Subcell 2 to Subcell 1 Handover Failure
Description
This counter counts data TCH/F call drops caused by handover failure from subcell 2 to subcell 1.

Usage
This counter indicates the number of data TCH/F call drops caused by handover failure from subcell 2 to subcell 1.

Measurement Point
Upon starting an intra-cell handover procedure on a TCH/F, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13-136 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.152 C901070165 Number of Signaling TCH/F Drops Due to Subcell 2 to Subcell 1 Handover Failure
Description
This counter counts signaling TCH/F call drops caused by handover failure from subcell 2 to subcell 1.

Usage
This counter indicates the number of signaling TCH/F call drops caused by handover failure from subcell 2 to subcell 1.

Measurement Point
Upon starting an intra-cell handover procedure on a TCH/F, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13.153 C901070166 Number of Speech TCH/H Drops Due to Subcell 2 to Subcell 1 Handover Failure
Description
This counter counts voice TCH/H call drops caused by handover failure from subcell 2 to subcell 1.

Usage
This counter indicates the number of voice TCH/H call drops caused by handover failure from subcell 2 to subcell 1.

Measurement Point
Upon starting an intra-cell handover procedure on a TCH/H, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13-137 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.154 C901070167 Number of Data TCH/H Drops Due to Subcell 2 to Subcell 1 Handover Failure
Description
This counter counts data TCH/H call drops caused by handover failure from subcell 2 to subcell 1.

Usage
This counter indicates the number of data TCH/H call drops caused by handover failure from subcell 2 to subcell 1.

Measurement Point
Upon starting an intra-cell handover procedure on a TCH/H, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13.155 C901070168 Number of Signaling TCH/H Drops Due to Subcell 2 to Subcell 1 Handover Failure
Description
This counter counts signaling TCH/H call drops caused by handover failure from subcell 2 to subcell 1.

Usage
This counter indicates the number of signaling TCH/H call drops caused by handover failure from subcell 2 to subcell 1.

Measurement Point
Upon starting an intra-cell handover procedure on a TCH/H, the BSC sends an assignment command and starts the corresponding timer. This counter is incremented each time the timer expires before an assignment complete message is received.

Unit
Times

13-138 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.156 C901070172 Number of Data TCH/F Drops

Description
This counter counts calls dropped on data TCH/Fs due to a radio link failure, LAPD link failure, or handover failure.

Measurement Point
This counter is incremented each time a call is dropped on a data TCH/F after an MS is assigned this channel.

Unit
Number of times

13.157 C901070173 Number of Data TCH/H Drops

Description
This counter counts calls drops on data TCH/Hs due to a radio link failure, LAPD link failure, or a handover failure.

Measurement Point
This counter is incremented each time a call is dropped on a data TCH/H after an MS is assigned this channel.

Unit
Number of times

13.158 C901070175 Number of Drop Call on SDCCH Due to BCCH Exchange

Description
This counter counts calls dropped on SDCCHs due to BCCH exchange.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command ( the release is BCCH exchange) from the RANUMC when the current channel is an SDCCH.

Unit
Number of times
13-139 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.159 C901070176 Number of Drop Call on SDCCH Due to Block Channel or Abis Resource
Description
This counter counts calls dropped on SDCCHs due to unexpected blocking of radio channels or Abis resources.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "FORCE_REL_ABISFAULT" or "FORCE_REL_UMTSFAULT") from the RANUMC when the current channel is an SDCCH.

Unit
Number of times

13.160 C901070177 Number of Drop Call on SDCCH Due to SD Change

Description
This counter counts calls dropped on SDCCHs due to SD change.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "CAUSE_SDCCHCHANGEOVER") from the RANUMC when the current channel is an SDCCH.

Unit
Number of times

13.161 C901070178 Number of Drop Call on SDCCH Due to Global Reset

Description
This counter counts calls dropped on SDCCHs due to global reset.

13-140 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "CAUSE_GLOBALRESET") from the RANUMC when the current channel is an SDCCH.

Unit
Number of times

13.162 C901070179 Number of Drop Call on SDCCH Due to Ring BTS Turn Over
Description
This counter counts calls dropped on SDCCHs due to ring BTS turnover.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "FORCE_RING_BTS_TURNOVER") from the RANUMC when the current channel is an SDCCH.

Unit
Number of times

13.163 C901070180 Number of Drop Call on TCH/F Due to IPA Board Fault
Description
This counter counts calls dropped on TCH/Fs due to an IPA board failure.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "CAUSE_AIPB_FAULT") from the RANUMC when the current channel is a TCH/F.

Unit
Number of times

13-141 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.164 C901070181 Number of Drop Call on TCH/F Due to IPA Board Resource Fault
Description
This counter counts calls dropped on TCH/Fs due to a resource failure in an IPA board.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives an EV_AIPBCONN_RESOURCE_FAIL message when the current channel is a TCH/F.

Unit
Number of times

13.165 C901070182 Number of Drop Call on TCH/F Due to BCCH Exchange

Description
This counter counts calls dropped on TCH/Fs due to BCCH exchange.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is BCCH exchange) from the RANUMC when the current channel is a TCH/F.

Unit
Number of times

13.166 C901070183 Number of Drop Call on TCH/F Due to Block Channel or Abis Resource
Description
This counter counts calls dropped on TCH/Fs due to unexpected blocking of radio channels or Abis resources.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "FORCE_REL_ABISFAULT" or "FORCE_REL_UMTSFAULT") from the RANUMC when the current channel is a TCH/F.
13-142 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Unit
Number of times

13.167 C901070184 Number of Drop Call on TCH/F Due to SD Change

Description
This counter counts calls dropped on TCH/Fs due to SD change.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "CAUSE_SDCCHCHANGEOVER") from the RANUMC when the current channel is a TCH/F.

Unit
Number of times

13.168 C901070185 Number of Drop Call on TCH/F Due to Circuit Fault

Description
This counter counts calls dropped on TCH/Fs due to a circuit failure.

Measurement Point
l In the case of an internal TC, this counter is incremented each time the RANCS instance in steady state receives an EV_DBSRELEASE_CALL message (the reason is "FORCE_REL_ATRUNKFAULT" or "FORCE_REL_ARESFAULT") when the current channel is a TCH/F. In the case of an external TC, this counter is incremented each time the RANCS instance in steady state receives an EV_DBSRELEASE_ITC_CALL message with the reason "FORCE_REL_ARESFAULT" when the current channel is a TCH/F.

Unit
Number of times

13-143 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.169 C901070186 Number of Drop Call on TCH/F Due to IFTA Cause

Description
This counter counts calls dropped on TCH/Fs due to IFTA MA change or IFTA status change.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "CAUSE_IFTAMA_CHANGE" or "CAUSE_IFTASTATUS_CHANGE") from the RANUMC when the current channel is a TCH/F.

Unit
Number of times

13.170 C901070187 Number of Drop Call on TCH/F Due to TDMA Board Fault
Description
This counter counts calls dropped on TCH/Fs due to a TDMA board failure. This counter is not used in this version.

Measurement Point
None

Unit
Number of times

13.171 C901070188 Number of Drop Call on TCH/F Due to iTC Board Fault
Description
This counter counts calls dropped on TCH/Fs due to an iTC board failure. This counter is not used in this version.

13-144 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Measurement Point
None

Unit
Number of times

13.172 C901070189 Number of Drop Call on TCH/F Due to iTC Board Resource Fault
Description
This counter counts calls dropped on TCH/Fs due to a resource failure in an iTC board. This counter is not used in this version.

Measurement Point
None

Unit
Number of times

13.173 C901070190 Number of Drop Call on TCH/F Due to TC Board Fault

Description
This counter counts calls dropped on TCH/Fs due to a TC board failure. This counter is not used in this version.

Measurement Point
None

Unit
Number of times

13-145 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.174 C901070191 Number of Drop Call on TCH/F Due to TC Board Resource Fault
Description
This counter counts calls dropped on TCH/Fs due to a resource failure in a TC board. This counter is not used in this version.

Measurement Point
None

Unit
Number of times

13.175 C901070192 Number of Drop Call on TCH/F Due to Global Reset

Description
This counter counts calls dropped on TCH/Fs due to global reset.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "CAUSE_GLOBALRESET") from the RANUMC when the current channel is a TCH/F.

Unit
Number of times

13.176 C901070193 Number of Drop Call on TCH/F Due to PS Preempt

Description
This counter counts calls dropped on TCH/Fs due to the timeout of CS traffic that is preempted by PS traffic.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "FORCE_REL_PSPREEMPT") from the RANUMC when the current channel is a TCH/F.
13-146 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Unit
Number of times

13.177 C901070194 Number of Drop Call on TCH/F Due to Reassign Fail

Description
This counter counts calls dropped on TCH/Fs due to reassignment failure.

Measurement Point
This counter is incremented each time the BSC receives a T3107 expired message during a reassignment process when the current channel is a TCH/F.

Unit
Number of times

13.178 C901070195 Number of Drop Call on TCH/F Due to Ring BTS Turn Over
Description
This counter counts calls dropped on TCH/Fs due to ring BTS turnover.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "FORCE_RING_BTS_TURNOVER") from the RANUMC when the current channel is a TCH/F.

Unit
Number of times

13.179 C901070198 Number of Drop Call on TCH/H Due to IPA Board Fault
Description
This counter counts calls dropped on TCH/Hs due to IPA board failure.

13-147 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "CAUSE_AIPB_FAULT") from the RANUMC when the current channel is a TCH/H.

Unit
Number of times

13.180 C901070199 Number of Drop Call on TCH/H Due to IPA Board Resource Fault
Description
This counter counts calls dropped on TCH/Hs due to resource failure in an IPA board.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives an EV_AIPBCONN_RESOURCE_FAIL message when the current channel is a TCH/H.

Unit
Number of times

13.181 C901070200 Number of Drop Call on TCH/H Due to BCCH Exchange

Description
This counter counts calls dropped on TCH/Hs due to BCCH exchange.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is BCCH exchange) from the RANUMC when the current channel is a TCH/H.

Unit
Number of times

13-148 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.182 C901070201 Number of Drop Call on TCH/H Due to Block Channel or Abis Resource
Description
This counter counts calls dropped on TCH/Hs due to unexpected blocking of radio channels or Abis resources.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "FORCE_REL_ABISFAULT" or "FORCE_REL_UMTSFAULT") from the RANUMC when the current channel is a TCH/H.

Unit
Number of times

13.183 C901070202 Number of Drop Call on TCH/H Due to SD Change

Description
This counter counts calls dropped on TCH/Hs due to SD change.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "CAUSE_SDCCHCHANGEOVER") from the RANUMC when the current channel is a TCH/H.

Unit
Number of times

13.184 C901070203 Number of Drop Call on TCH/H Due to Circuit Fault

Description
This counter counts calls dropped on TCH/Hs due to a circuit failure.

Measurement Point
l In the case of an internal TC, this counter is incremented each time the RANCS instance in steady state receives an EV_DBSRELEASE_CALL message (the reason
13-149 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

is "FORCE_REL_ATRUNKFAULT" or "FORCE_REL_ARESFAULT") when the current channel is a TCH/H. In the case of an external TC, this counter is incremented each time the RANCS instance in steady state receives an EV_DBSRELEASE_ITC_CALL message (the reason is "FORCE_REL_ARESFAULT") when the current channel is a TCH/H.

Unit
Number of times

13.185 C901070204 Number of Drop Call on TCH/H Due to IFTA Cause

Description
This counter counts calls dropped on TCH/Hs due to IFTA MA change or IFTA status change.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "CAUSE_IFTAMA_CHANGE" or "CAUSE_IFTASTATUS_CHANGE") from the RANUMC when the current channel is a TCH/H.

Unit
Number of times

13.186 C901070205 Number of Drop Call on TCH/H Due to TDMA Board Fault
Description
This counter counts calls dropped on TCH/Hs due to a TDMA board failure. This counter is not used in this version.

Measurement Point
None

Unit
Number of times

13-150 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

13.187 C901070206 Number of Drop Call on TCH/H Due to iTC Board Fault
Description
This counter counts calls dropped on TCH/Hs due to an iTC board failure. This counter is not used in this version.

Measurement Point
None

Unit
Number of times

13.188 C901070207 Number of Drop Call on TCH/H Due to iTC Board Resource Fault
Description
This counter counts calls dropped on TCH/Hs due to a resource failure in an iTC board. This counter is not used in this version.

Measurement Point
None

Unit
Number of times

13.189 C901070208 Number of Drop Call on TCH/H Due to TC Board Fault

Description
This counter counts calls dropped on TCH/Hs due to a TC board failure. This counter is not used in this version.

Measurement Point
None

13-151 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Number of times

13.190 C901070209 Number of Drop Call on TCH/H Due to TC Board Resource Fault
Description
This counter counts calls dropped on TCH/Hs due to a resource failure in a TC board. This counter is not used in this version.

Measurement Point
None

Unit
Number of times

13.191 C901070210 Number of Drop Call on TCH/H Due to Global Reset

Description
This counter counts calls dropped on TCH/Hs due to global reset.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "CAUSE_GLOBALRESET") from the RANUMC when the current channel is a TCH/H.

Unit
Number of times

13.192 C901070211 Number of Drop Call on TCH/H Due to PS Preempt

Description
This counter counts calls dropped on TCH/Hs due to the timeout of CS traffic that is preempted by PS traffic.
13-152 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "FORCE_REL_PSPREEMPT") from the RANUMC when the current channel is a TCH/H.

Unit
Number of times

13.193 C901070212 Number of Drop Call on TCH/H Due to Reassign Fail

Description
This counter counts calls dropped on TCH/Hs due to a reassignment failure.

Measurement Point
This counter is incremented each time the BSC receives a T3107 expired message during a reassignment process when the current channel is a TCH/H.

Unit
Number of times

13.194 C901070213 Number of Drop Call on TCH/H Due to Ring BTS Turn Over
Description
This counter counts calls dropped on TCH/Hs due to ring BTS turnover.

Measurement Point
This counter is incremented each time the RANCS instance in steady state receives a release command (the reason is "FORCE_RING_BTS_TURNOVER") from the RANUMC when the current channel is a TCH/H.

Unit
Number of times

13-153 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

13.195 C901070216 Number of Drops Due to Interf UL Handover

Description
This counter counts calls dropped due to a handover caused by uplink interference.

Measurement Point
This counter is incremented each time a call is dropped due to a handover caused by uplink interference.

Unit
Number of times

13.196 C901070217 Number of Drops Due to Interf DL Handover

Description
This counter counts calls dropped due to a handover caused by downlink interference.

Measurement Point
This counter is incremented each time a call is dropped due to a handover caused by downlink interference.

Unit
Number of times

13.197 C901070218 Number of Drops Due to QUAL UL Handover

Description
This counter counts calls dropped due to a handover caused by the uplink bit error rate.

Measurement Point
This counter is incremented each time a call is dropped due to a handover caused by the uplink bit error rate.

13-154 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Unit
Number of times

13.198 C901070219 Number of Drops Due to QUAL DL Handover

Description
This counter counts calls dropped due to a handover caused by the downlink bit error rate.

Measurement Point
This counter is incremented each time a call is dropped due to a handover caused by the downlink bit error rate.

Unit
Number of times

13.199 C901070220 Number of Drops Due to LEVEL UL Handover

Description
This counter counts calls dropped due to a handover caused by the uplink level.

Measurement Point
This counter is incremented each time a call is dropped due to a handover caused by the uplink level.

Unit
Number of times

13.200 C901070221 Number of Drops Due to LEVEL DL Handover

Description
This counter counts calls dropped due to a handover caused by the downlink level.

13-155 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time a call is dropped due to a handover caused by the downlink level.

Unit
Number of times

13.201 C901070222 Number of Drops Due to RAPID UL Handover

Description
This counter counts calls dropped due to a handover caused by an uplink rapid field drop.

Measurement Point
This counter is incremented each time a call is dropped due to a handover caused by an uplink rapid field drop.

Unit
Number of times

13.202 C901070223 Number of Drops Due to PBGT Handover

Description
This counter counts calls dropped due to a PBGT handover.

Measurement Point
This counter is incremented each time a call is dropped due to a PBGT handover.

Unit
Number of times

13.203 C901070224 Number of Drops Due to MACRO to MICRO Handover

Description
This counter counts calls dropped due to a macro-to-micro handover.
13-156 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Measurement Point
This counter is incremented each time a call is dropped due to a macro-to-micro handover.

Unit
Number of times

13.204 C901070225 Number of Drops Due to SUB Cell 1 to SUB Cell 2 Handover
Description
This counter counts calls dropped due to a handover from subcell 1 to subcell 2.

Measurement Point
This counter is incremented each time a call is dropped due to a handover from subcell 1 to subcell 2.

Unit
Number of times

13.205 C901070226 Number of Drops Due to SUB Cell 2 to SUB Cell 1 Handover
Description
This counter counts calls dropped due to a handover from subcell 2 to subcell 1.

Measurement Point
This counter is incremented each time a call is dropped due to a handover from subcell 2 to subcell 1.

Unit
Number of times

13.206 C901070227 Number of Drops Due to PREEMPT Handover

Description
This counter counts calls dropped due to a handover caused by preemption reason.
13-157 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time a call is dropped due to a handover caused by preemption reason.

Unit
Number of times

13.207 C901070228 Number of Drops Due to TRAFFIC Handover

Description
This counter counts calls dropped due to a handover caused by traffic reason.

Measurement Point
This counter is incremented each time a call is dropped due to a handover caused by traffic reason.

Unit
Number of times

13.208 C901070229 Number of Drops Due to DLRAPID Handover

Description
This counter counts calls dropped due to a downlink rapid handover.

Measurement Point
This counter is incremented each time a call is dropped due to a downlink rapid handover.

Unit
Number of times

13.209 C901070230 Number of Drops Due to HRFR Handover

Description
This counter counts calls dropped due to an HR-to-FR handover.
13-158 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 13 RMM Call Drop Measurement

Measurement Point
This counter is incremented each time a call is dropped due to an HR-to-FR handover.

Unit
Number of times

13.210 C901070231 Number of Drops Due to RAPIDQUAL Handover

Description
This counter counts calls dropped due to a rapid handover caused by the downlink bit error rate.

Measurement Point
This counter is incremented each time a call is dropped due to a rapid handover caused by the downlink bit error rate.

Unit
Number of times

13-159 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

13-160 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14

Radio Resource Availability Measurement

Table of Contents
Overview ..................................................................................................................14-2 C901080003 Maximum number of busy SDCCH......................................................14-2 C901080004 Average number of busy SDCCH ........................................................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-11 C901080018 TCH/H congestion time .....................................................................14-12 C901080022 Average number of busy TCH/F ........................................................14-13 C901080024 TCH/F busy time(SpeechVer1)..........................................................14-14 C901080025 TCH/F busy time(SpeechVer2)..........................................................14-16 C901080026 TCH/F busy time(SpeechVer3)..........................................................14-17 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 C901080045 TCH/H Busy Time (SpeechVer4) .......................................................14-23 C901080046 TCH/F Busy Time (SpeechVer4) .......................................................14-24 C901080047 TCH/F Busy Time (SpeechVer5) .......................................................14-25 C901080048 TRX Number of Configured BaseBand Resources ............................14-25 C901080049 TRX Number of Non-Configured BaseBand Resources.....................14-26 C901080050 Success Number of Configured BaseBand Resource........................14-26 C901080051 Conflict Number of Configured Baseband Resource..........................14-27 C901080052 Number of Releasing BaseBand Resource........................................14-27 C901080053 SDCCH Busy Time (Speech) ............................................................14-28 C901080054 SDCCH Busy Time (SMS).................................................................14-28 C901080055 Duration of Intelligent Cell Power Off .................................................14-28 C901080058 1800M TCH/F Busy Time ..................................................................14-29 C901080059 1800M TCH/H Busy Time..................................................................14-29

14-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. The measurement takes cell as the statistics unit.

14.2 C901080003 Maximum number of busy SDCCH

Definition
Maximum Number of Busy SDCCHs

Description
This counter counts the maximum number of busy SDCCHs in the cell within measurement period; its value represents SDDCH 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 l l The counter updates if the maximum busy number exceeds the recorded value after SDCCH has been occupied successfully; The counter updates if the maximum busy number exceeds the recorded value before SDCCH has been released; The counter updates if the maximum busy number exceeds the recorded value when measurement data are reported periodically. The measurement point is A, as shown in Figure 14-1.

14-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

Figure 14-1 Reporting Measurement Data

Unit
Times

14.3 C901080004 Average number of busy SDCCH

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
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 when measurement data are reported periodically. The measurement point is A, as shown in Figure 14-2.

14-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 14-2 Reporting Measurement Data

Unit
Times

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
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:
14-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

l l l

If congestion mark is set before SDCCH has been occupied, the counter counts congestion time and accumulates. If congestion mark is set before SDCCH has been released, the counter counts congestion time and accumulates. If congestion mark is set when measurement values are reported periodically, the counter counts congestion time and accumulates. The measurement point is A, as shown in Figure 14-3.
Figure 14-3 Reporting Measurement Data

Unit
Second

14.5 C901080008 Number of unavailable defined SDCCH

Definition
Number of unavailable defined SDCCH

Description
iBSC supports dynamic transform between SDCCH and TCH. This counter counts the number of unavailable static SDCCH configured by present cell through OMCR.

Usage
This counter is used to find out the unavailability of SDCCH in the present cell for eliminating cell failures.

14-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 14-4 Reporting Measurement Data

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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.
14-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

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-5.
Figure 14-5 Reporting Measurement Data

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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 period. The occupation number in measurement data reported periodically in the system is the mean number of busy radio channel.

Usage
This counter is used to find out the busy extent of radio channel in cells; its value can be used as the reference for whether to increase TRXs.
14-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-6.
Figure 14-6 Reporting Measurement Data

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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 period. The occupation number in measurement data reported periodically in the system 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.

14-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

Measurement Point
Occupation number updates after TCH/H has been occupied and released successfully, the counter value is reported when measurement data are reported periodically. The measurement point is A, as shown in Figure 14-7.
Figure 14-7 Reporting Measurement Data

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation

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.
14-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts in the following three cases: l l l The counter counts time and accumulates when TCH/H is obtained successfully The counter counts time and accumulates when TCH/H is released The counter counts time and accumulates when measurement data are reported periodically. The measurement point is A, as shown in Figure 14-8.
Figure 14-8 Reporting Measurement Data

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
ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation

14-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

14.10 C901080017 TCH/H busy time(SpeechVer3)

Definition
TCH/H busy time(SpeechVer3).

Description
This counter counts the total TCH/H busy time (SpeechVer3) in cells; its value represents traffic on TCH/H (SpeechVer3).

Usage
This counter is used to find out the busy extent and mean occupation time of TCH/H in cells; its value can be used as the reference for whether to increase TCH/Hs.

Measurement Point
The counter counts in the following three cases: l l l The counter counts time and accumulates when TCH/H is obtained successfully The counter counts time and accumulates when TCH/H is released The counter counts time and accumulates when measurement data are reported periodically. The measurement point is A, as shown in Figure 14-9.
Figure 14-9 Reporting Measurement Data

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
14-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

obtained successfully after accumulation. The number of MS that are occupying channels decrements when TCH/H is released after accumulation.

Unit
Second

Related Features
ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation

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 are reported periodically, the congestion time is calculated. The sum of each congestion 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
The counter counts in the following three cases: l l If congestion mark is set before TCH/H has been occupied, the counter counts congestion time and accumulates. If congestion mark is set before TCH/H has been released, the counter counts congestion time and accumulates.
14-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

If congestion mark is set when measurement values are reported periodically, the counter counts congestion time and accumulates. The measurement point is A, as shown in Figure 14-10.
Figure 14-10 Reporting Measurement Data

Unit
Second

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation

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 period. The occupation number in measurement data reported periodically in the system 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
Occupation number updates after TCH/F has been occupied and released successfully, the counter value is reported when measurement data are reported periodically. The measurement point is A, as shown in Figure 14-11.
Figure 14-11 Reporting Measurement Data

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-003 Full dynamic channel allocation on Um interface

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

Measurement Point
The counter counts in the following three cases: l l l The counter counts time and accumulates when TCH/F is obtained successfully The counter counts time and accumulates when TCH/F is released The counter counts time and accumulates when measurement data are reported periodically. The measurement point is A, as shown in Figure 14-12.
Figure 14-12 Reporting Measurement Data

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/F is obtained successfully after accumulation. The number of MS that are occupying channels decrements when TCH/F is released after accumulation.

Unit
Second

Related Features
ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-003 Full dynamic channel allocation on Um interface

14-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

14.14 C901080025 TCH/F busy time(SpeechVer2)

Definition
TCH/F busy time (SpeechVer2)

Description
This counter counts the total TCH/F busy time (SpeechVer2) in cells; its value represents traffic on TCH/F (SpeechVer2).

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

Measurement Point
The counter counts in the following three cases: l l l The counter counts time and accumulates when TCH/F is obtained successfully The counter counts time and accumulates when TCH/F is released The counter counts time and accumulates when measurement data are reported periodically. The measurement point is A, as shown in Figure 14-13.
Figure 14-13 Reporting Measurement Data

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
14-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

time. The number of MS that are occupying channels increments when TCH/F is obtained successfully after accumulation. The number of MS that are occupying channels decrements when TCH/F is released after accumulation.

Unit
Second

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-003 Full dynamic channel allocation on Um interface

14.15 C901080026 TCH/F busy time(SpeechVer3)

Definition
TCH/F busy time(SpeechVer3)

Description
This counter counts the total TCH/F busy time (SpeechVer3) in cells; its value represents traffic on TCH/F (SpeechVer3).

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

Measurement Point
The counter counts in the following three cases: l l l The counter counts time and accumulates when TCH/F is obtained successfully The counter counts time and accumulates when TCH/F is released The counter counts time and accumulates when measurement data are reported periodically. The measurement point is A, as shown in Figure 14-14.

14-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 14-14 Reporting Measurement Data

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/F is obtained successfully after accumulation. The number of MS that are occupying channels decrements when TCH/F is released after accumulation.

Unit
Second

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-003 Full dynamic channel allocation on Um interface

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

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 are reported periodically, the congestion time is calculated. The sum of each congestion 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
The counter counts in the following three cases: l l l If congestion mark is set before TCH/F has been occupied, the counter counts congestion time and accumulates. If congestion mark is set before TCH/F has been released, the counter counts congestion time and accumulates. If congestion mark is set when measurement values are reported periodically, the counter counts congestion time and accumulates. The measurement point is A, as shown in Figure 14-15.
Figure 14-15 Reporting Measurement Data

Unit
Second

14-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-003 Full dynamic channel allocation on Um interface

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
The counter value is inquired from database when periodical measurement data are reported. The measurement point is A, as shown in Figure 14-16.
Figure 14-16 Reporting Measurement Data

Unit
Times

14-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

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
The counter counts in the following three cases: l l l The counter counts when reserved TCH/F is obtained successfully The counter counts when reserved TCH/F is released; The counter counts when measurement values are reported periodically. measurement point is A, as shown in Figure 14-17.
Figure 14-17 Reporting Measurement Data

The

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
14-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

time. The number of MS that are occupying channels increments when TCH/F is obtained successfully after accumulation. The number of MS that are occupying channels decrements when TCH/F is released after accumulation.

Unit
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

Usage
This counter is used to find out the duration of cell interruption on BCCH. This counter is supported in version V6.20.210a or above.

Measurement Point
When the confirmation message (tGetCellDownTimeAck.wResult) of cell's interruption duration obtained from database is true, the counter counts.

Unit
Second

14.21 C901080045 TCH/H Busy Time (SpeechVer4)

Description
The total length of time when a half rate channel is busy needs to be calculated during a measurement period. The busy duration measurement is carried out by speech version. This counter indicates the total length of time when the channel using the half rate speech version 4 (OHR AMR-WB channels) is busy. The busy durations of channels using other speech versions are calculated by the other counters of the same measurement task. After receiving the ASSIGNMENT REQUEST from the MSC, the RANCS chooses the half rate speech version 4 for the originated call, and records the start time when the speech version is used.

Usage
This counter represents the total length of time when the half rate channel is busy during a measurement period.

Measurement Point
As shown in Figure 14-18, the RANCS chooses the speech version and records the start time at the measurement point A. It records the end time at the measurement point B when the call is completed or unexpectedly terminated. This counter calculates the busy duration of the HR channel by substracting the end time from the start time. If the call covers several measurement periods, the RANCS calculates the busy duration by measurement period according to the actual duration of the call in each measurement period.

14-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 14-18 Busy Duration Measurement of TCH/H

Unit
Second

14.22 C901080046 TCH/F Busy Time (SpeechVer4)

Description
The total length of time when a full rate channel is busy needs to be calculated during a measurement period. The busy duration measurement is carried out by speech version. This counter indicates the total length of time when the channel using the full rate speech version 4 (OFR AMR-WB) is busy. The busy durations of channels using other speech versions are calculated by the other counters of the same measurement task.

Usage
This counter represents the total length of time when the full rate channel is busy during a measurement period.

Measurement Point
Refer to C901080045 TCH/H Busy Time (SpeechVer4) for the description of measurement points.

Unit
Second

14-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

14.23 C901080047 TCH/F Busy Time (SpeechVer5)

Description
The total length of time when a full rate channel is busy needs to be calculated during a measurement period. The busy duration measurement is carried out by speech version. This counter indicates the total length of time when the channel using the full rate speech version 5 (FR AMR-WB) is busy. The busy durations of channels using other speech versions are calculated by the other counters of the same measurement task.

Usage
This counter represents the total length of time when the full rate channel is busy during a measurement period.

Measurement Point
Refer to C901080045 TCH/H Busy Time (SpeechVer4) for the description of measurement points.

Unit
Second

14.24 C901080048 TRX Number of Configured BaseBand Resources

Description
This counter counts the TRXs that are assigned baseband resources in the cell. It reflects the assignment of baseband resources for the TRXs in the cell.

Usage
This counter indicates the number of TRXs that are assigned baseband resources in the cell.

Measurement Point
The SDR counts the TRXs assigned baseband resources in the cell and reports the number every 15 minutes.

Unit
N/A

14-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

14.25 C901080049 TRX Number of Non-Configured BaseBand Resources

Description
This counter counts the TRXs that are not assigned baseband resources in the cell. It reflects the assignment of baseband resources for the TRXs in the cell.

Usage
This counter indicates the number of TRXs that are not assigned baseband resources in the cell.

Measurement Point
The SDR counts the TRXs that are not assigned baseband resources in the cell and reports the number every 15 minutes.

Unit
N/A

14.26 C901080050 Success Number of Configured BaseBand Resource

Description
This counter is incremented each time baseband resources are successfully assigned to the TRXs in the cell. It reflects the occupation of baseband resources in the cell.

Usage
This counter indicates the number of times that baseband resources are successfully assigned to the TRXs in the cell.

Measurement Point
The SDR counts the times that baseband resources are successfully assigned to TRXs in the cell within 15 minutes, and reports the number of assignment successes.

Unit
Times

14-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

14.27 C901080051 Conflict Number of Configured Baseband Resource

Description
This counter is incremented each time the assignment of baseband resources to the TRXs in the cell fails. It reflects the occupation of baseband resources in the cell.

Usage
This counter indicates the number of times that baseband resources are not successfully assigned to the TRXs in the cell.

Measurement Point
The SDR counts the times that the assignment of baseband resources fails within 15 minutes, and reports the number of assignment failures.

Unit
Times

14.28 C901080052 Number of Releasing BaseBand Resource

Description
This counter is incremented each time the baseband resources are released by the TRXs in the cell. It reflects the release of baseband resources in the cell.

Usage
This counter indicates the number of times that baseband resources are released by the TRXs in the cell.

Measurement Point
The SDR counts the times that baseband resources are released by the TRXs in the cell within 15 minutes, and reports the number of releases.

Unit
Times

14-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

14.29 C901080053 SDCCH Busy Time (Speech)

Description
This counter counts the SDCCH busy time in the speech service. When the SDCCH is released, the difference between the channel release time and channel request time is calculated and updated to the counter in the speech service.

Usage
None

Measurement Point
None

Unit
Second

14.30 C901080054 SDCCH Busy Time (SMS)

Description
This counter counts the SDCCH busy time in the SMS. When the SDCCH is released, the difference between the channel release time and channel request time is calculated and updated to the counter in the SMS.

Usage
None

Measurement Point
None

Unit
Second

14.31 C901080055 Duration of Intelligent Cell Power Off

Description
This counter counts the duration from the start to the end of intelligent cell power off.

14-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 14 Radio Resource Availability Measurement

Usage
None

Measurement Point
Timing starts at point A and ends at point B as shown in Figure 14-19. The duration from point A to point B is calculated.
Figure 14-19 Duration of Intelligent Cell Power Off

Unit
Second

14.32 C901080058 1800M TCH/F Busy Time

Description
This counter counts voice traffic on 1800M TCH/F in a cell.

Usage
This counter indicates the busy time of 1800M TCH/F.

Measurement Point
This counter calculates the busy time of 1800M TCH/F depending on the cell configuration in accordance with the counters "TCH/F Busy Time" and "TCH/F Busy Time in the Second Subcell"

Unit
Second

14.33 C901080059 1800M TCH/H Busy Time

Description
This counter counts voice traffic on 1800M TCH/H in a cell.

14-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter indicates the busy time of 1800M TCH/H.

Measurement Point
This counter calculates the busy time of 1800M TCH/F depending on the cell configuration in accordance with the counters "TCH/H Busy Time" and "TCH/H Busy Time in the Second Subcell"

Unit
Second

14-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15

General Handover Measurement

Table of Contents
Overview ..................................................................................................................15-9 C901090001 Number of BSC-controlled inter-cell outgoing handover attempts ........15-9 C901090004 Number of MSC-controlled outgoing handover attempts....................15-10 C901090005 Number of MSC-controlled outgoing handover request failures due to unclear factors........................................................................................................ 15-11 C901090006 Number of MSC-controlled outgoing handover request failures due to unavailable ground resource ..................................................................................15-12 C901090007 Number of MSC-controlled outgoing handover request failures due to unavailable radio resource .....................................................................................15-13 C901090008 Number of MSC-controlled outgoing handover request failures due to other factors ...........................................................................................................15-14 C901090011 Number of BSC-controlled inter-cell incoming handover attempts......15-15 C901090013 Number of BSC-controlled incoming handover attempts due to forced release ...................................................................................................................15-16 C901090015 Number of BSC-controlled incoming handover attempts due to queue.....................................................................................................................15-18 C901090017 Number of BSC-controlled incoming handover attempts due to forced handover ................................................................................................................15-19 C901090020 BSC-controlled incoming handover time due to queue ......................15-20 C901090021 Queue number of BSC-controlled incoming handover .......................15-22 C901090022 BSC-controlled incoming handover success time due to queue.........15-24 C901090023 Number of BSC-controlled incoming handover success due to queue.....................................................................................................................15-25 C901090024 Number of MSC-controlled incoming handover attempts ...................15-26 C901090025 Number of incoming handover failure due to circuit block ..................15-27 C901090026 Number of incoming handover failure due to circuit group mismatch .15-28 C901090027 Number of incoming handover failure due to unavailable radio resource .................................................................................................................15-29 C901090028 Number of incoming handover failure due to other factors .................15-30 C901090030 Number of MSC-controlled incoming handover attempts due to forced release ...................................................................................................................15-31 C901090032 Number of MSC-controlled incoming handover attempts due to queue.....................................................................................................................15-32

15-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901090034 Number of MSC-controlled incoming handover attempts due to forced handover ................................................................................................................15-33 C901090037 MSC-controlled incoming handover time due to queue......................15-34 C901090038 Queue number of MSC-controlled incoming handover.......................15-37 C901090039 MSC-controlled incoming handover success time due to queue ........15-39 C901090040 Number of MSC-controlled incoming handover success due to queue.....................................................................................................................15-40 C901090041 Number of incoming handover attempts from the same layer and frequency ...............................................................................................................15-41 C901090042 Number of incoming handover success from the same layer and frequency ...............................................................................................................15-42 C901090043 Number of outgoing handover attempts to the same layer and frequency ...............................................................................................................15-43 C901090044 Number of outgoing handover success to the same layer and frequency ...............................................................................................................15-44 C901090045 Number of incoming handover attempts from undefined layer to the same frequency......................................................................................................15-45 C901090046 Number of incoming handover success from undefined layer to the same frequency......................................................................................................15-46 C901090047 Number of outgoing handover attempts from undefined layer to the same frequency......................................................................................................15-47 C901090048 Number of outgoing handover success from undefined layer to the same frequency......................................................................................................15-48 C901090049 Number of incoming handover attempts from undefined layer (GSM900) to current layer (GSM1800) ...................................................................15-49 C901090052 Number of outgoing handover attempts from current layer (GSM900) to undefined layer (GSM1800)................................................................................15-50 C901090053 Number of outgoing handover from current layer (GSM900) to undefined layer (GSM1800)....................................................................................15-51 C901090054 Number of outgoing handover success from current layer (GSM900) to undefined layer (GSM1800)................................................................................15-52 C901090055 Number of incoming handover attempts from undefined layer (GSM1800) to current layer (GSM900) ...................................................................15-53 C901090058 Number of outgoing handover attempts from undefined layer (GSM1800) to current layer (GSM900) ...................................................................15-54 C901090059 Number of outgoing handover from undefined layer (GSM1800) to current layer (GSM900) ..........................................................................................15-55 C901090060 Number of outgoing handover success from undefined layer (GSM1800) to current layer (GSM900) ...................................................................15-56 C901090061 Number of incoming handover attempts from upper layer to the same frequency ...............................................................................................................15-57 C901090062 Number of incoming handover success from upper layer to the same frequency ...............................................................................................................15-58 C901090063 Number of outgoing handover attempts from the same frequency to upper layer .............................................................................................................15-59
15-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

C901090064 Number of outgoing handover success from the same frequency to upper layer .............................................................................................................15-60 C901090065 Number of incoming handover attempts from lower layer to the same frequency ...............................................................................................................15-61 C901090066 Number of incoming handover success from lower layer to the same frequency ...............................................................................................................15-62 C901090067 Number of outgoing handover attempts from the same frequency to lower layer..............................................................................................................15-63 C901090068 Number of outgoing handover success from the same frequency to lower layer..............................................................................................................15-64 C901090069 Number of incoming handover attempts from the same layer GSM900 to GSM1800 ...........................................................................................................15-65 C901090072 Number of outgoing handover attempts to the same layer GSM900 to GSM1800...............................................................................................................15-66 C901090073 Number of outgoing handover to the same layer GSM900 to GSM1800...............................................................................................................15-67 C901090074 Number of outgoing handover success to the same layer GSM900 to GSM1800...............................................................................................................15-68 C901090075 Number of incoming handover attempts from GSM900 to GSM1800 from the upper layer ...............................................................................................15-69 C901090078 Number of outgoing handover attempts from GSM900 to GSM1800 to the upper layer ...................................................................................................15-70 C901090079 Number of outgoing handover from GSM900 to GSM1800 to the upper layer .............................................................................................................15-71 C901090080 Number of outgoing handover success from GSM900 to GSM1800 to the upper layer .......................................................................................................15-72 C901090081 Number of incoming handover attempts from GSM900 to GSM1800 from the lower layer................................................................................................15-73 C901090084 Number of outgoing handover attempts from GSM900 to GSM1800 to the lower layer ....................................................................................................15-74 C901090085 Number of outgoing handover from GSM900 to GSM1800 to the lower layer..............................................................................................................15-75 C901090086 Number of outgoing handover success from GSM900 to GSM1800 to the lower layer........................................................................................................15-76 C901090087 Number of incoming handover attempts from GSM1800 to GSM900 from the same layer................................................................................................15-77 C901090090 Number of outgoing handover attempts from GSM1800 to GSM900 to the same layer....................................................................................................15-78 C901090091 Number of outgoing handover from GSM1800 to GSM900 to the same layer .............................................................................................................15-79 C901090092 Number of outgoing handover success from GSM1800 to GSM900 to the same layer........................................................................................................15-80 C901090093 Number of incoming handover attempts from GSM1800 to GSM900 from the upper layer ...............................................................................................15-81

15-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901090096 Number of outgoing handover attempts from GSM1800 to GSM900 to the upper layer ...................................................................................................15-82 C901090097 Number of outgoing handover from GSM1800 to GSM900 to the upper layer .............................................................................................................15-83 C901090098 Number of outgoing handover success from GSM1800 to GSM900 to the upper layer .......................................................................................................15-84 C901090099 Number of incoming handover attempts from GSM1800 to GSM900 from the lower layer................................................................................................15-85 C901090102 Number of outgoing handover attempts from GSM1800 to GSM900 to the lower layer ....................................................................................................15-86 C901090103 Number of outgoing handover from GSM1800 to GSM900 to the lower layer..............................................................................................................15-87 C901090104 Number of outgoing handover success from GSM1800 to GSM900 to the lower layer........................................................................................................15-88 C901090105 Number of intra-cell handover attempts .............................................15-89 C901090108 Number of intra-cell inner-circle-to-outer-circle handover attempts ....15-90 C901090109 Number of intra-cell inner-circle-to-outer-circle handover success .....15-91 C901090110 Number of intra-cell outer-circle-to-inner-circle handover attempts.....15-92 C901090111 Number of intra-cell outer-circle-to-inner-circle handover success......15-93 C901090112 Number of intra-cell inner-circle-to-inner-circle handover attempts.....15-94 C901090113 Number of intra-cell inner-circle-to-inner-circle handover success......15-95 C901090114 Number of intra-cell outer-circle-to-outer-circle handover attempts ....15-96 C901090115 Number of intra-cell outer-circle-to-outer-circle handover success .....15-97 C901090116 Number of handover attempts from 2G to 3G ....................................15-98 C901090117 Number of handover from 2G to 3G...................................................15-99 C901090118 Number of handover success from 2G to 3G ...................................15-100 C901090119 Number of handover attempts from 3G to 2G ..................................15-101 C901090120 Number of handover from 3G to 2G ................................................15-102 C901090121 Number of handover success from 3G to 2G...................................15-102 C901090122 Number of intra-cell handover attempts from TCH/F........................15-103 C901090123 Number of intra-cell TCH/F-to-TCH/F handover...............................15-104 C901090124 Number of intra-cell TCH/F-to-TCH/F handover success .................15-105 C901090125 Number of intra-cell TCH/F-to-TCH/H handover ..............................15-106 C901090126 Number of intra-cell TCH/F-to-TCH/H handover success.................15-107 C901090127 Number of intra-cell handover attempts from TCH/H .......................15-108 C901090128 Number of intra-cell TCH/H-to-TCH/F handover ..............................15-109 C901090129 Number of intra-cell TCH/H-to-TCH/F handover success................. 15-110 C901090130 Number of intra-cell TCH/H-to-TCH/H handover.............................. 15-111 C901090131 Number of intra-cell TCH/H-to-TCH/H handover success ................ 15-112 C901090132 Number of inter-cell handover attempts from TCH/F........................ 15-113 C901090133 Number of inter-cell TCH/F-to-TCH/F handover............................... 15-114 C901090134 Number of inter-cell TCH/F-to-TCH/F handover success ................. 15-115 C901090135 Number of inter-cell TCH/F-to-TCH/H handover .............................. 15-116 C901090136 Number of inter-cell TCH/F-to-TCH/H handover success................. 15-117 C901090137 Number of inter-cell handover attempts from TCH/H ....................... 15-118
15-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

C901090138 Number of inter-cell TCH/H-to-TCH/F handover .............................. 15-119 C901090139 Number of inter-cell TCH/H-to-TCH/F handover success.................15-120 C901090140 Number of inter-cell TCH/H-to-TCH/H handover..............................15-121 C901090141 Number of inter-cell TCH/H-to-TCH/H handover success ................15-122 C901090142 Total dual-band outgoing handover attempts ...................................15-123 C901090145 Number of dual band incoming handover attempts ..........................15-124 C901090148 Number of intra-cell invalid handovers.............................................15-125 C901090149 Number of BSC-controlled inter-cell incoming handover attempts due to forced release (emergency service)..................................................................15-126 C901090150 Number of BSC-controlled inter-cell incoming handover (forced release) (emergency service) ...............................................................................15-127 C901090151 Number of BSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service)...............................................................15-128 C901090152 Number of BSC-controlled inter-cell incoming handover (forced handover) (emergency service) ............................................................................15-129 C901090153 Number of BSC-controlled inter-cell incoming handover attempts due to queue (emergency service) ..............................................................................15-131 C901090154 Number of BSC-controlled inter-cell incoming handover (queue) (emergency service).............................................................................................15-132 C901090155 Number of MSC-controlled incoming handover attempts due to forced release (emergency service) ................................................................................15-133 C901090156 Number of MSC-controlled incoming handover (forced release) (emergency service).............................................................................................15-134 C901090157 Number of MSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service)...............................................................15-135 C901090158 Number of MSC-controlled incoming handover (forced release) (emergency service).............................................................................................15-136 C901090159 Number of MSC-controlled incoming handover attempts due to queue (emergency service).............................................................................................15-137 C901090160 Number of MSC-controlled incoming handover (queue) (emergency service) ................................................................................................................15-138 C901090161 Number of forced handover target not found (BSC-controlled inter-cell handover due to forced handover)........................................................................15-139 C901090162 Number of send forced handover request to lower PRI user (BSC-controlled inter-cell handover due to forced handover) ................................15-140 C901090163 Number of recv failure from lower PRI user request resource for forced handover (BSC-controlled inter-cell handover due to forced handover)......15-141 C901090164 Number of lower PRI user handover failure (BSC-controlled inter-cell handover due to forced handover)........................................................................15-143 C901090165 Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced handover)..........................................................15-144 C901090166 Number of forced release target not found (BSC-controlled inter-cell handover due to forced release) ...........................................................................15-145 C901090167 Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced release).............................................................15-147
15-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901090168 Number of HO Target not found (MSC-controlled incoming handover due to forced handover) .......................................................................................15-148 C901090169 Number of send forced handover request to lower PRI user (MSC-controlled incoming handover due to forced handover)...............................15-149 C901090170 Number of failure to lower PRI user request resource for forced handover (MSC-controlled incoming handover due to forced handover) ...............15-150 C901090171 Number of lower PRI user handover failure (MSC-controlled incoming handover due to forced handover)........................................................................15-150 C901090172 Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced handover).........................................................15-151 C901090173 Number of forced release target not found (MSC-controlled incoming handover due to forced release) ...........................................................................15-152 C901090174 Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced release) ............................................................15-152 C901090175 Number of get before grab released channel (assignment forced handover).............................................................................................................15-153 C901090176 Number of get before grab released channel (assignment forced release) ................................................................................................................15-154 C901090177 Number of handover attempts due to eMLPP forced handover........15-154 C901090178 Number of handover due to eMLPP forced handover ......................15-155 C901090179 Number of handover success due to eMLPP forced handover.........15-155 C901090180 Number of BSC-controlled inter-cell outgoing handover attempts between PLMN.....................................................................................................15-156 C901090181 Number of BSC-controlled inter-cell outgoing handover between PLMN...................................................................................................................15-156 C901090182 Number of BSC-controlled inter-cell outgoing handover success between PLMN.....................................................................................................15-156 C901090183 Number of MSC-controlled outgoing handover attempts between PLMN...................................................................................................................15-156 C901090184 Number of MSC-controlled outgoing handover request fail between PLMN due to unknown reason .............................................................................15-156 C901090185 Number of MSC-controlled outgoing handover request fail between PLMN due to unavailable ground resource ..........................................................15-157 C901090186 Number of MSC-controlled outgoing handover request fail between PLMN due to unavailable radio resource ..............................................................15-158 C901090187 Number of MSC-controlled outgoing handover request fail between PLMN due to other reasons..................................................................................15-158 C901090188 Number of MSC-controlled outgoing handover between PLMN .......15-158 C901090189 Number of MSC-controlled outgoing handover success between PLMN...................................................................................................................15-160 C901090190 Number of BSC-controlled inter-cell incoming handover attempt between PLMN.....................................................................................................15-160 C901090191 Number of BSC-controlled inter-cell incoming handover between PLMN...................................................................................................................15-160

15-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

C901090192 Number of BSC-controlled inter-cell incoming handover force-release attempt between PLMN ........................................................................................15-160 C901090193 Number of BSC-controlled inter-cell incoming handover between PLMN due to force release ...................................................................................15-161 C901090194 Number of BSC-controlled inter-cell incoming handover queue attempt between PLMN ........................................................................................15-161 C901090195 Number of BSC-controlled inter-cell incoming handover between PLMN due to queue .............................................................................................15-161 C901090196 Number of BSC-controlled inter-cell incoming handover force-handover attempt between PLMN ...............................................................15-161 C901090197 Number of BSC-controlled inter-cell incoming handover between PLMN due to force handover................................................................................15-161 C901090198 Number of BSC-controlled inter-cell incoming handover success between PLMN.....................................................................................................15-161 C901090199 Number of MSC-controlled incoming handover attempt between PLMN ..................................................................................................................15-162 C901090200 A interface incoming handover fail between PLMN due to circuit block ....................................................................................................................15-163 C901090201 A interface incoming handover fail between PLMN due to circuit unmatch ...............................................................................................................15-164 C901090202 A interface incoming handover fail between PLMN due to unavailable radio resource ......................................................................................................15-164 C901090203 A interface incoming handover fail between PLMN due to other reason..................................................................................................................15-165 C901090204 Number of MSC-controlled incoming handover between PLMN.......15-165 C901090205 Number of MSC-controlled incoming handover force-release attempt between PLMN.....................................................................................................15-165 C901090206 Number of MSC-controlled incoming handover between PLMN due to force release ....................................................................................................15-166 C901090207 Number of MSC-controlled incoming handover queue attempt between PLMN.....................................................................................................15-166 C901090208 Number of MSC-controlled incoming handover between PLMN due to queue ...............................................................................................................15-167 C901090209 Number of MSC-controlled incoming handover force-handover attempt between PLMN ........................................................................................15-168 C901090210 Number of MSC-controlled incoming handover between PLMN due to force handover .................................................................................................15-169 C901090211 Number of MSC-controlled incoming handover success between PLMN ..................................................................................................................15-169 C901090212 Number of handover due to Fragment reorganization......................15-169 C901090213 Number of handover success due to Fragment reorganization ........15-169 C901090214 Number of handover attempt from AMR FR to AMR HR due to high load ......................................................................................................................15-170 C901090215 Number of handover from AMR FR to AMR HR due to high load.....15-171

15-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901090216 Number of handover success from AMR FR to AMR HR due to high load ......................................................................................................................15-172 C901090217 Number of handover attempt from FR to HR due to high load..........15-172 C901090218 Number of handover from FR to HR due to high load ......................15-173 C901090219 Number of handover success from FR to HR due to high load.........15-174 C901090220 Number of handover attempt from AMR HR to AMR FR due to bad quality ..................................................................................................................15-174 C901090221 Number of handover from AMR HR to AMR FR due to bad quality ..15-175 C901090222 Number of handover success from AMR HR to AMR FR due to bad quality ..................................................................................................................15-176 C901090223 Number of handover attempt from HR to FR due to bad quality.......15-176 C901090224 Number of handover from HR to FR due to bad quality ...................15-177 C901090225 Number of handover success from HR to FR due to bad quality......15-178 C901090226 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM900 ....................................................................................15-178 C901090227 Number of BSC-controlled inter-cell outgoing handover, from GSM900 to GSM900 ............................................................................................15-179 C901090228 Number of BSC-controlled inter-cell outgoing handover success, from GSM900 to GSM900 ............................................................................................15-180 C901090229 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM1800 ................................................................................15-181 C901090230 Number of BSC-controlled inter-cell outgoing handover, from GSM1800 to GSM1800 ........................................................................................15-182 C901090231 Number of BSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM1800 ........................................................................................15-183 C901090232 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM1800 ..................................................................................15-184 C901090233 Number of BSC-controlled inter-cell outgoing handover, from GSM900 to GSM1800 ..........................................................................................15-185 C901090234 Number of BSC-controlled inter-cell outgoing handover success, from GSM900 to GSM1800 ..........................................................................................15-186 C901090235 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM900 ..................................................................................15-187 C901090236 Number of BSC-controlled inter-cell outgoing handover, from GSM1800 to GSM900 ..........................................................................................15-188 C901090237 Number of BSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM900 ..........................................................................................15-189 C901090238 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM900 ....................................................................................15-190 C901090239 Number of MSC-controlled inter-cell outgoing handover, from GSM900 to GSM900 ............................................................................................15-191 C901090240 Number of MSC-controlled inter-cell outgoing handover success, from GSM900 to GSM900 ....................................................................................15-192 C901090241 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM1800 ................................................................................15-193
15-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

C901090242 Number of MSC-controlled inter-cell outgoing handover, from GSM1800 to GSM1800 ........................................................................................15-194 C901090243 Number of MSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM1800 ................................................................................15-195 C901090244 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM1800 ..................................................................................15-196 C901090245 Number of MSC-controlled inter-cell outgoing handover, from GSM900 to GSM1800 ..........................................................................................15-197 C901090246 Number of MSC-controlled inter-cell outgoing handover success, from GSM900 to GSM1800 ..................................................................................15-198 C901090247 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM900 ..................................................................................15-198 C901090248 Number of MSC-controlled inter-cell outgoing handover, from GSM1800 to GSM900 ..........................................................................................15-199 C901090249 Number of MSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM900 ..................................................................................15-200 C901090250 Number of Inter-BSC Incoming Handover Failure Due to New Channel Access Failure........................................................................................15-201 C901090251 Number of Inter-BSC Incoming Handover Failure Due to MS Return to Old Channel .....................................................................................................15-201 C901090264 The Number of forbid sending hand command during releasing ......15-202 C901090265 Number of Inner BSC Direct Retry Success ....................................15-203 C901090266 Number of Inter BSC Direct Retry Success .....................................15-203 C901090267 Number of Intra-Cell Handover Failure Lead to Return ....................15-204 C901090268 User/MSC Release Number During BSC-Controlled Inter-Cell Outgoing Handover ..............................................................................................15-204 C901090269 User/MSC Release Number During MSC-Controlled Inter-Cell Outgoing Handover ..............................................................................................15-205

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. The measurement takes cell as the statistics unit.

15.2 C901090001 Number of BSC-controlled inter-cell outgoing handover attempts

Definition
Number of BSC-controlled inter-cell outgoing handover attempts
15-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 increments. The measurement point is A, as shown in Figure 15-1.
Figure 15-1 BSC-Controlled Inter-Cell Outgoing Handover Attempt

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15.3 C901090004 Number of MSC-controlled outgoing handover attempts

Definition
Number of MSC-controlled outgoing handover attempts

15-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Description
This counter counts the number of MSC-controlled inter-BSC 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 outgoing handover attempts. It is one of the parameters to measure the wireless environment.

Measurement Point
BSC starts the handover decision after it receives the measurement report from MS. If 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

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15.4 C901090005 Number of MSC-controlled outgoing handover request failures due to unclear factors
Definition
Number of MSC-controlled outgoing handover request failures due to unclear factors

15-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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 governed by different BSCs, the source BSC will send MSC the handover request A_HO_RQD to trigger inter-BSC handover. If BSC fails to receive any feedback from MSC before the protection timer expires, the counter increments. The 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

Related Features
ZGB-02-02-001 Basic Handover

15.5 C901090006 Number of MSC-controlled outgoing handover request failures due to unavailable ground resource
Definition
Number of MSC-controlled outgoing handover request failures due to unavailable ground resource

15-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Description
This counter counts the number of MSC-controlled inter-BSC outgoing handover request failures due to unavailable ground resource originated from the source cell by MS.

Usage
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
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 governed by different BSCs, the source BSC will send MSC the handover request A_HO_RQD to trigger inter-BSC handover. If the source BSC receives the feedback from MSC that the handover request is rejected due to unavailable ground resource, the counter increments. The measurement point is A, as shown in Figure 15-4.
Figure 15-4 MSC-Controlled Handover Request Failures

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15.6 C901090007 Number of MSC-controlled outgoing handover request failures due to unavailable radio resource
Definition
Number of MSC-controlled outgoing request failures due to unavailable radio resource

15-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of MSC-controlled inter-BSC outgoing handover request failures due to unavailable radio resource originated from the source cell by MS.

Usage
This counter is used to find out the frequency of MS-originated MSC-controlled outgoing handover request failures due to unavailable radio resource, and to find out the MSC-originated handover status.

Measurement Point
BSC starts the handover decision after it receives the measurement report from MS. If 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. If the source BSC receives the feedback from MSC that the handover request is rejected due to unavailable radio resource, the counter increments. The measurement point is A, as shown in Figure 15-5.
Figure 15-5 MSC-Controlled Handover Request Failures

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15.7 C901090008 Number of MSC-controlled outgoing handover request failures due to other factors
Definition
Number of MSC-controlled outgoing handover request failures due to other factors

15-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Description
This counter counts the number of MSC-controlled inter-BSC outgoing handover request failures due to other factors excluding unavailable ground resource and unavailable radio resource originated from the source cell by MS.

Usage
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
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 governed by different BSCs, the source BSC will send MSC the handover request A_HO_RQD to trigger inter-BSC handover. If the source BSC receives the feedback from MSC that the handover request is rejected due to other factors, the counter increments. The measurement point is A, as shown in Figure 15-6.
Figure 15-6 MSC-Controlled Handover Request Failures

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15.8 C901090011 Number of BSC-controlled inter-cell incoming handover attempts

Definition
Number of BSC-controlled inter-cell incoming handover attempts

15-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 shown in Figure 15-7.
Figure 15-7 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15.9 C901090013 Number of BSC-controlled incoming 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
15-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-03-001 eMLPP

15-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.10 C901090015 Number of BSC-controlled incoming 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
This counter is used to find out the frequency of MS-originated BSC-controlled inter-cell incoming handover attempts due to queue, which reflects the handover status.

Measurement Point
When intra-BSC target cell receives the wireless channel application request, if the application cause is BSC-controlled inter-cell incoming handover and wireless channel is unavailable to target cell, queuing attempt decision starts. If queuing attempt is feasible and the target cell has the target instance waiting in the queuing, the counter increments. The measurement point is A, as shown in Figure 15-9.
Figure 15-9 Queuing Attempts

Unit
Times

15-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-03-001 eMLPP

15.11 C901090017 Number of BSC-controlled incoming 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
This counter is used to find out the frequency of MS-originated BSC-controlled inter-cell incoming handover attempts due to forced handover, which reflects the handover status.

Measurement Point
When intra-BSC target cell receives the wireless channel application request, if the application cause is BSC-controlled 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-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-10 Forced-Handover Attempts

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover 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-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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

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 shown in Figure 15-12.
Figure 15-12 Incoming Handover Queuing Expires

During the process of instance queuing, when the instance is released due to some causes, if the application cause is BSC-controlled incoming handover, the queuing time accumulates. The measurement point is A, as shown in Figure 15-13.

15-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-13 Instance Release During Queuing

Unit
Second

Related Features
ZGB-02-02-001 Basic Handover

15.13 C901090021 Queue number of BSC-controlled incoming handover

Definition
Queue number of BSC-controlled incoming handover

Description
This counter counts the total queue number of calls that participate in BSC-controlled intra-cell incoming handover.

Usage
This counter is used to find out the total queue number of calls that participate in BSC-controlled intra-cell incoming handover, which helps to understand the traffic status.

Measurement Point
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. The measurement point is A, as shown in Figure 15-14.
15-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-14 Execution In Queuing

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.
Figure 15-15 Incoming Handover Queuing Expires

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 increments. The measurement point is A, as shown in Figure 15-16.

15-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-16 Instance Release During Queuing

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

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-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

application cause is BSC-controlled incoming handover, the queuing time accumulates. The measurement point is A, as shown in Figure 15-17.
Figure 15-17 Execution In Queuing

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15.15 C901090023 Number of BSC-controlled incoming handover success due to queue

Definition
Number of BSC-controlled incoming handover success due to queue

Description
This counter counts the total number of calls that participate in BSC-controlled intra-cell incoming handover due to queue and successfully acquiring resource.

Usage
This counter is used to find out the total number of calls that participate in BSC-controlled intra-cell incoming handover due to queue and successfully acquiring resource, and to find out the success ratio of queuing.

15-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
Under the condition that database acquires resource via dynamic channel conversion or MS releases resource and queuing instance receives resource usable message, if the application cause is BSC-controlled incoming handover, the counter increments. The measurement point is A, as shown in Figure 15-18.
Figure 15-18 Execution In Queuing

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15.16 C901090024 Number of MSC-controlled incoming handover attempts

Definition
Number of MSC-controlled incoming handover attempts

Description
This counter counts the number of MSC-originated inter-BSC incoming handover attempts.

Usage
This counter is used to find out the frequency of MSC-originated inter-BSC incoming handover attempts. It is one of the parameters to measure the wireless environment.
15-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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
ZGB-02-02-001 Basic Handover

15.17 C901090025 Number of incoming handover failure due to circuit block

Definition
Number of incoming handover failure due to circuit block

Description
This counter counts the number of unsuccessful MSC-originated inter-BSC incoming handover due to ground circuit block.

Usage
This counter is used to find out the frequency of unsuccessful MSC-originated inter-BSC incoming handover due to ground circuit block, and is used to observe the external handover flow.

15-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When the target cell receives the handover request from MSC, it checks the ground circuit. If the requested ground circuit is blocked, the counter increments. The measurement point is A, as shown in Figure 15-20.
Figure 15-20 Unsuccessful MSC-Controlled External Incoming Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15.18 C901090026 Number of incoming handover failure due to circuit group mismatch
Definition
Number of incoming handover failure due to circuit group mismatch

Description
This counter counts the number of unsuccessful MSC-originated inter-BSC incoming handover due to ground circuit group mismatch.

Usage
This counter is used to find out the frequency of unsuccessful MSC-originated inter-BSC incoming handover due to ground circuit group mismatch, and is used to observe the external handover flow.

Measurement Point
When the target cell receives the handover request from MSC, it checks the ground circuit. If the requested ground circuit does not match, the counter increments. The measurement point is A, as shown in Figure 15-21.
15-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-21 Unsuccessful MSC-Controlled External Incoming Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15.19 C901090027 Number of incoming handover failure due to unavailable radio resource
Definition
Number of incoming handover failure requests due to unavailable radio resource

Description
This counter counts the number of unsuccessful MSC-originated inter-BSC incoming handover due to unavailable radio resource.

Usage
This counter is used to find out the frequency of unsuccessful MSC-originated inter-BSC incoming handover due to unavailable radio resource, and is used to observe the external handover flow.

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 A, as shown in Figure 15-22.

15-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-22 Unsuccessful MSC-Controlled External Incoming Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15.20 C901090028 Number of incoming handover failure due to other factors

Definition
Number of incoming handover failure due to other factors

Description
This counter counts the number of unsuccessful MSC-originated inter-BSC incoming handover due to other factors excluding circuit block, circuit group mismatch and unavailable radio resource.

Usage
This counter is used to find out the frequency of unsuccessful MSC-originated inter-BSC incoming handover due to other factors, and is used to observe the external handover flow.

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 measurement point is A, as shown in Figure 15-23.

15-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-23 Unsuccessful MSC-Controlled External Incoming Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15.21 C901090030 Number of MSC-controlled incoming handover attempts due to forced release
Definition
Number of MSC-controlled incoming handover attempts due to forced release

Description
This counter counts the number of forced release attempts originated by target cell due to unavailable radio resource during the process of MS-originated MSC-controlled inter-BSC incoming handover. When target instance fails to allocate the channel, forced release attempts could be originated referring to the MS priority and MSC & BSC settings.

Usage
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-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-24 Forced Release Attempts

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-03-001 eMLPP

15.22 C901090032 Number of MSC-controlled incoming 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
This counter is used to find out the frequency of MS-originated MSC-controlled inter-BSC incoming handover attempts due to queue, 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
15-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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. The measurement point is A, as shown in Figure 15-25.
Figure 15-25 Queuing Attempts

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-03-001 eMLPP

15.23 C901090034 Number of MSC-controlled incoming handover attempts due to forced handover
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
This counter is used to find out the frequency of MS-originated MSC-controlled inter-BSC incoming handover attempts due to forced handover, which reflects the handover status.
15-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-handover attempt decision starts. If forced-handover attempt is feasible, the counter increments before the target cell sends forced-handover message to the instance that is to be forced handover. The measurement point is A, as shown in Figure 15-26.
Figure 15-26 Forced-Handover Attempts

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover 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-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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
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 MSC-controlled incoming handover, the queuing time accumulates. The measurement point is A, as shown in Figure 15-27.
Figure 15-27 Execution In Queuing

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 shown in Figure 15-28.

15-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-28 Incoming Handover Queuing Expires

During the process of instance queuing, when the instance is released due to some 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.
Figure 15-29 Instance Release During Queuing

Unit
Second

Related Features
ZGB-02-02-001 Basic Handover

15-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.25 C901090038 Queue number of MSC-controlled incoming handover

Definition
Queue number of MSC-controlled incoming handover

Description
This counter counts the total queue number of calls that participate in BSC-controlled intra-cell incoming handover.

Usage
This counter is used to find out the total queue number of calls that participate in MSC-controlled intra-cell incoming handover, which helps to understand the traffic status.

Measurement Point
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 MSC-controlled incoming handover, the counter increments. The measurement point is A, as shown in Figure 15-30.
Figure 15-30 Execution In Queuing

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-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-31 Incoming Handover Queuing Expires

During the process of instance queuing, when the instance is released due to some causes, if the application cause is MSC-controlled incoming handover, the counter increments. The measurement point is A, as shown in Figure 15-32.
Figure 15-32 Instance Release During Queuing

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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
Under the condition that database acquires resource via dynamic channel conversion or MS releases resource, when queuing instance receives resource usable message, if the application cause is MSC-controlled incoming handover, the queuing time accumulates. The measurement point is A, as shown in Figure 15-33.
Figure 15-33 Execution In Queuing

Unit
Second

Related Features
ZGB-02-02-001 Basic Handover
15-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.27 C901090040 Number of MSC-controlled incoming 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
Under the condition that database acquires resource via dynamic channel conversion or MS releases resource, and queuing instance receives resource usable message, if the application cause is MSC-controlled incoming handover, the counter increments. The measurement point is A, as shown in Figure 15-34.
Figure 15-34 Execution In Queuing

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover
15-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.28 C901090041 Number of incoming handover 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.
Figure 15-35 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

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

15-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.29 C901090042 Number of incoming handover 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
This counter is used to find out the frequency of BSC-controlled incoming handover success from the same layer and frequency, and is used to observe the handover flow.

Measurement Point
When intra-BSC target cell receives the handover completed message, if the application cause is BSC-controlled inter-cell handover and the source cell is at the same layer and frequency, the counter increments. The measurement point is A, as shown inFigure 15-36.
Figure 15-36 Successful BSC-Controlled Inter-Cell Incoming Handover

Unit
Times

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

15-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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
BSC starts the handover decision after it receives the measurement report from MS. If inter-cell handover is necessary, and the current attempt cells are BSC-controlled internal cells at the same layer and frequency, the counter increments. The measurement point is A, as shown in Figure 15-37.
Figure 15-37 BSC-Controlled Inter-Cell Outgoing Handover Attempt

Unit
Times

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

15-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.31 C901090044 Number of outgoing handover 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
ZGO-05-02-008 Multi-layer Cell Structure

15-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.32 C901090045 Number of incoming handover attempts from undefined layer to the same frequency
Definition
Number of incoming handover attempts from undefined layer to the same frequency

Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell receives from undefined layer to the same frequency.

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover 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 shown in Figure 15-39.
Figure 15-39 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

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

15-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.33 C901090046 Number of incoming handover success from undefined layer to the same frequency
Definition
Number of incoming handover success from undefined layer to the same frequency

Description
This counter counts the number of successful BSC-controlled inter-cell incoming handover the target cell receives from undefined layer to the same frequency.

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover success from undefined layer to the same frequency, which helps to observe the handover flow.

Measurement Point
When intra-BSC target cell receives the handover completed message, if the application cause is BSC-controlled inter-cell handover, and the source cell is at undefined layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-40.
Figure 15-40 Successful BSC-Controlled Inter-Cell Incoming Handover

Unit
Times

Related Features
ZGO-05-02-008 Multi-layer Cell Structure
15-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.34 C901090047 Number of outgoing handover attempts from undefined layer to the same frequency
Definition
Number of outgoing handover attempts from undefined layer to the same frequency

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell sends from undefined layer to the same frequency.

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover 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 measurement point is A, as shown in Figure 15-41.
Figure 15-41 BSC-Controlled Inter-Cell Outgoing Handover Attempt

Unit
Times

15-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

15.35 C901090048 Number of outgoing handover success from undefined layer to the same frequency
Definition
Number of outgoing handover success from undefined layer to the same frequency

Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell sends from undefined layer to the same frequency.

Usage
This counter is used to find out the frequency of successful BSC-controlled outgoing handover from undefined layer to the same 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 undefined layer and the same frequency, the counter increments. The measurement point is A, as shown inFigure 15-42.
Figure 15-42 Successful BSC-Controlled Inter-Cell Outgoing Handover

Unit
Times
15-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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

15.36 C901090049 Number of incoming handover attempts from undefined layer (GSM900) to current layer (GSM1800)
Definition
Number of incoming handover attempts from undefined layer (GSM900) to current layer (GSM1800)

Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM1800) receives from undefined layer (GSM900).

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover attempts from undefined layer (GSM900) to current layer (GSM1800), which helps to make the network planning.

Measurement Point
When intra-BSC target cell (GSM1800) receives the channel application request from the source cell (GSM900), if the application cause is inter-cell incoming handover and the source cell is at undefined layer, the counter increments. The measurement point is A, as shown in Figure 15-43.
Figure 15-43 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times
15-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

15.37 C901090052 Number of outgoing handover attempts from current layer (GSM900) to undefined layer (GSM1800)
Definition
Number of outgoing handover attempts from current layer (GSM900) to undefined layer (GSM1800)

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM900) sends to undefined layer (GSM1800).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts from undefined layer (GSM900) to current layer (GSM1800), 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 (GSM1800) and the current serving cell is GSM900, the counter increments. The measurement point is A, as shown in Figure 15-44.
Figure 15-44 BSC-Controlled Inter-Cell Outgoing Handover Attempt

15-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Unit
Times

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

15.38 C901090053 Number of outgoing handover 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
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts from undefined layer (GSM900) to current layer (GSM1800), which helps to make the network planning.

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 point is A, as shown in Figure 15-45.
Figure 15-45 BSC-Controlled Inter-Cell Outgoing Handover Execution Flow

Unit
Times
15-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

15.39 C901090054 Number of outgoing handover success from current layer (GSM900) to undefined layer (GSM1800)
Definition
Number of outgoing handover success from current layer (GSM900) to undefined layer (GSM1800)

Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends from undefined layer to the same frequency (GSM1800).

Usage
This counter is used to find out the frequency of successful BSC-controlled outgoing handover from undefined layer to the same frequency (GSM900) to current layer (GSM1800), which helps to make the network planning.

Measurement Point
During the process of BSC-controlled handover, if the source cell (GSM900) receives the handover completed message from the target cell (GSM1800), and the target cell is at undefined layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-46.
Figure 15-46 Successful BSC-Controlled Inter-Cell Outgoing Handover

Unit
Times
15-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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

15.40 C901090055 Number of incoming handover attempts from undefined layer (GSM1800) to current layer (GSM900)
Definition
Number of incoming handover attempts from undefined layer (GSM1800) to current layer (GSM900)

Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM900) receives from undefined layer (GSM1800).

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover attempts from undefined layer (GSM1800) to current layer (GSM900), which helps to make the network planning.

Measurement Point
When intra-BSC target cell (GSM900) receives the channel application request from the 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 shown in Figure 15-47.
Figure 15-47 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times
15-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

15.41 C901090058 Number of outgoing handover attempts from undefined layer (GSM1800) to current layer (GSM900)
Definition
Number of outgoing handover attempts from undefined layer (GSM1800) to current layer (GSM900)

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM1800) sends to undefined layer (GSM900).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts from undefined layer (GSM1800) to current layer (GSM900), 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 attempted cell is BSC-controlled internal cell at undefined layer (GSM900) or lower-layer cell at same frequency (GSM1800), the counter increments. The measurement point is A, as shown in Figure 15-48.
Figure 15-48 BSC-Controlled Inter-Cell Outgoing Handover Attempt

15-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Unit
Times

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

15.42 C901090059 Number of outgoing handover from undefined layer (GSM1800) to current layer (GSM900)
Definition
Number of outgoing handover from undefined layer (GSM1800) to current layer (GSM900)

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends to undefined layer (GSM900).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts from undefined layer (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 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 point is A, as shown in Figure 15-49.
Figure 15-49 BSC-Controlled Inter-Cell Outgoing Handover Execution Flow

Unit
Times
15-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

15.43 C901090060 Number of outgoing handover success from undefined layer (GSM1800) to current layer (GSM900)
Definition
Number of outgoing handover success from undefined layer (GSM1800) to current layer (GSM900)

Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends from undefined layer to the same frequency (GSM900).

Usage
This counter is used to find out the frequency of successful BSC-controlled outgoing 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 is A, as shown in Figure 15-50.
Figure 15-50 Successful BSC-Controlled Inter-Cell Outgoing Handover

Unit
Times
15-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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

15.44 C901090061 Number of incoming handover attempts from upper layer to the same frequency
Definition
Number of incoming handover attempts from upper layer to the same frequency

Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell receives from upper layer to the same frequency.

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover attempts from upper 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 upper layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-51.
Figure 15-51 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

Related Features
ZGO-05-02-008 Multi-layer Cell Structure
15-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.45 C901090062 Number of incoming handover success from upper layer to the same frequency
Definition
Number of incoming handover success from upper layer to the same frequency

Description
This counter counts the number of successful BSC-controlled inter-cell incoming handover the target cell receives from upper layer to the same frequency.

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover success from upper layer to the same 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-BSC handover and the source cell is at upper and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-52.
Figure 15-52 Successful BSC-Controlled Inter-Cell Incoming Handover

Unit
Times

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

15-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.46 C901090063 Number of outgoing handover attempts from the same frequency to upper layer
Definition
Number of outgoing handover attempts from the same frequency to upper layer

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell sends from upper layer to the same frequency.

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts from upper 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 upper layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-53.
Figure 15-53 BSC-Controlled Inter-Cell Outgoing Handover Attempt

Unit
Times

Related Features
ZGO-05-02-008 Multi-layer Cell Structure
15-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.47 C901090064 Number of outgoing handover success from the same frequency to upper layer
Definition
Number of outgoing handover success from the same frequency to upper layer

Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell sends from upper layer to the same frequency.

Usage
This counter is used to find out the frequency of successful BSC-controlled outgoing handover from upper layer to the same 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, 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 increments. The measurement point is A, as shown in Figure 15-54.
Figure 15-54 Successful BSC-Controlled Inter-Cell Outgoing Handover

Unit
Times

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

15-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.48 C901090065 Number of incoming handover attempts from lower layer to the same frequency
Definition
Number of incoming handover attempts from lower layer to the same frequency

Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell receives from lower layer to the same frequency.

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover attempts from lower 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 lower layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-55.
Figure 15-55 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

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

15-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.49 C901090066 Number of incoming handover success from lower layer to the same frequency
Definition
Number of incoming handover success from lower layer to the same frequency

Description
This counter counts the number of successful BSC-controlled inter-cell incoming handover the target cell receives from lower layer to the same frequency.

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover success from lower layer to the same 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-BSC handover and the source cell is at lower and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-56.
Figure 15-56 Successful BSC-Controlled Inter-Cell Incoming Handover

Unit
Times

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

15-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.50 C901090067 Number of outgoing handover attempts from the same frequency to lower layer
Definition
Number of outgoing handover attempts from the same frequency to lower layer

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell sends from the same frequency to lower layer.

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts from the same frequency to lower layer, 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 lower layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-57.
Figure 15-57 BSC-Controlled Inter-Cell Outgoing Handover Attempt

Unit
Times

Related Features
ZGO-05-02-008 Multi-layer Cell Structure
15-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.51 C901090068 Number of outgoing handover success from the same frequency to lower layer
Definition
Number of outgoing handover success from the same frequency to lower layer

Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell sends from the same frequency to lower layer.

Usage
This counter is used to find out the frequency of successful BSC-controlled outgoing handover from the same frequency to lower layer, 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 lower layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-58.
Figure 15-58 Successful BSC-Controlled Inter-Cell Outgoing Handover

Unit
Times

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

15-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.52 C901090069 Number of incoming handover attempts from the same layer GSM900 to GSM1800
Definition
Number of incoming handover attempts from the same layer GSM900 to GSM1800

Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM1800) receives from the same layer (GSM900).

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover attempts from the same layer GSM900 to 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 handover and the source cell is at the same layer, the counter increments. The measurement point is A, as shown in Figure 15-59.
Figure 15-59 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

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

15-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.53 C901090072 Number of outgoing handover attempts to the same layer GSM900 to GSM1800
Definition
Number of outgoing handover attempts to the same layer GSM900 to GSM1800

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM900) sends to the same layer (GSM1800).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts to the same layer GSM900 to GSM1800, 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 the same layer (GSM1800) and the current serving cell is GSM900, the counter increments. The measurement point is A, as shown in Figure 15-60.
Figure 15-60 BSC-Controlled Inter-Cell Outgoing Handover Attempt

Unit
Times

Related Features
ZGO-05-02-008 Multi-layer Cell Structure
15-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to the same layer (GSM1800).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts to the same layer GSM900 to GSM1800, which helps to make the network planning.

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 the same layer and frequency, the counter increments. The measurement point is A, as shown in Figure 15-61.
Figure 15-61 BSC-Controlled Inter-Cell Outgoing Handover Execution Flow

Unit
Times

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

15-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.55 C901090074 Number of outgoing handover success to the same layer GSM900 to GSM1800
Definition
Number of outgoing handover success to the same layer GSM900 to GSM1800

Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to the same layer and frequency (GSM1800).

Usage
This counter is used to find out the frequency of successful BSC-controlled outgoing handover to the same layer and frequency from GSM900 to GSM1800, which helps to make the network planning.

Measurement Point
During the process of BSC-controlled handover, if the source cell (GSM900) receives the handover completed message from the target cell (GSM1800), and the target cell is at the same layer and frequency, the counter increments. The measurement point is A, as shown in Figure 15-62.
Figure 15-62 Successful BSC-Controlled Inter-Cell Outgoing Handover

Unit
Times

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

15-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.56 C901090075 Number of incoming handover attempts from GSM900 to GSM1800 from the upper layer
Definition
Number of incoming handover attempts from GSM900 to GSM1800 from the upper layer

Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM1800) receives from upper layer (GSM900).

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover attempts at upper layer and from GSM900 to 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 handover and the source cell is at upper layer, the counter increments. The measurement point is A, as shown in Figure 15-63.
Figure 15-63 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

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

15-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.57 C901090078 Number of outgoing handover attempts from GSM900 to GSM1800 to the upper layer
Definition
Number of outgoing handover attempts from GSM900 to GSM1800 to the upper layer

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM900) sends to upper layer (GSM1800).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts from GSM900 to GSM1800 to the upper layer, 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 upper layer (GSM1800) and the current serving cell is GSM900, the counter increments. The measurement point is A, as shown in Figure 15-64.
Figure 15-64 BSC-Controlled Inter-Cell Outgoing Handover Attempt

Unit
Times

15-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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

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
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to upper layer (GSM1800).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts from GSM900 to GSM1800 to the upper layer, which helps to make the network planning.

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 upper layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-65.
Figure 15-65 BSC-Controlled Inter-Cell Outgoing Handover Execution Flow

Unit
Times

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

15-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.59 C901090080 Number of outgoing handover success from GSM900 to GSM1800 to the upper layer
Definition
Number of outgoing handover success from GSM900 to GSM1800 to the upper layer

Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends from upper layer to the same frequency (GSM1800).

Usage
This counter is used to find out the frequency of successful BSC-controlled outgoing handover from upper layer to the same frequency from GSM900 to GSM1800, which helps to make the network planning.

Measurement Point
During the process of BSC-controlled handover, if the source cell (GSM900) receives the handover completed message from the target cell (GSM1800), and the target cell is at upper layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-66.
Figure 15-66 Successful BSC-Controlled Inter-Cell Outgoing Handover

Unit
Times

Related Features
ZGO-05-02-008 Multi-layer Cell Structure
15-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.60 C901090081 Number of incoming handover attempts from GSM900 to GSM1800 from the lower layer
Definition
Number of incoming handover attempts from GSM900 to GSM1800 from the lower layer

Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM1800) receives from lower layer (GSM900).

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover attempts at lower layer and from GSM900 to 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 handover and the source cell is at lower layer, the counter increments. The measurement point is A, as shown in Figure 15-67.
Figure 15-67 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

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

15-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.61 C901090084 Number of outgoing handover attempts from GSM900 to GSM1800 to the lower layer
Definition
Number of outgoing handover attempts from GSM900 to GSM1800 from the lower layer

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM900) sends to lower layer (GSM1800).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts to lower layer and from GSM900 to GSM1800, 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 lower layer (GSM1800) and the current serving cell is GSM900, the counter increments. The measurement point is A, as shown in Figure 15-68.
Figure 15-68 BSC-Controlled Inter-Cell Outgoing Handover Attempt

Unit
Times

15-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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

15.62 C901090085 Number of outgoing handover from GSM900 to GSM1800 to the lower layer
Definition
Number of outgoing handover from GSM900 to GSM1800 in the lower layer

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to lower layer (GSM1800).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts to lower layer and from GSM900 to GSM1800, which helps to make the network planning.

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 lower layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-69.
Figure 15-69 BSC-Controlled Inter-Cell Outgoing Handover Execution Flow

Unit
Times

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

15-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.63 C901090086 Number of outgoing handover success from GSM900 to GSM1800 to the lower layer
Definition
Number of outgoing handover success from GSM900 to GSM1800 in the lower layer

Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends from the same frequency to lower layer (GSM1800).

Usage
This counter is used to find out the frequency of successful BSC-controlled outgoing handover from the same frequency to lower layer from GSM900 to GSM1800, which helps to make the network planning.

Measurement Point
During the process of BSC-controlled handover, if the source cell (GSM900) receives the handover completed message from the target cell (GSM1800), and the target cell is at lower layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-70.
Figure 15-70 Successful BSC-Controlled Inter-Cell Outgoing Handover

Unit
Times

Related Features
ZGO-05-02-008 Multi-layer Cell Structure
15-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.64 C901090087 Number of incoming handover attempts from GSM1800 to GSM900 from the same layer
Definition
Number of incoming handover attempts from GSM1800 to GSM900 from the same layer

Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM900) receives from the same layer (GSM1800).

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover attempts at the same layer and from GSM1800 to GSM900, which helps to make the network planning.

Measurement Point
When intra-BSC target cell (GSM900) receives the channel application request from the source cell (GSM1800), 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-71.
Figure 15-71 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

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

15-77 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.65 C901090090 Number of outgoing handover attempts from GSM1800 to GSM900 to the same layer
Definition
Number of outgoing handover attempts from GSM1800 to GSM900 from the same layer

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM1800) sends to the same layer (GSM900).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts to the same layer and from GSM1800 to GSM900, 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 the same layer (GSM900) and the current serving cell is GSM1800, the counter increments. The measurement point is A, as shown in Figure 15-72.
Figure 15-72 BSC-Controlled Inter-Cell Outgoing Handover Attempt

Unit
Times

15-78 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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

15.66 C901090091 Number of outgoing handover from GSM1800 to GSM900 to the same layer
Definition
Number of outgoing handover from GSM1800 to GSM900 from the same layer

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends to the same layer (GSM900).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts to the same layer and from GSM1800 to GSM900, which helps to make the network planning.

Measurement Point
During the process of BSC-controlled handover, if the source cell (GSM1800) receives the radio resource unavailable 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-73.
Figure 15-73 BSC-Controlled Inter-Cell Outgoing Handover Execution Flow

Unit
Times

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

15-79 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.67 C901090092 Number of outgoing handover success from GSM1800 to GSM900 to the same layer
Definition
Number of outgoing handover success from GSM1800 to GSM900 from the same layer

Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends to the same layer and frequency (GSM900).

Usage
This counter is used to find out the frequency of successful BSC-controlled outgoing handover to the same layer and frequency and from GSM1800 to 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 the same layer and frequency, the counter increments. The measurement point is A, as shown in Figure 15-74.
Figure 15-74 Successful BSC-Controlled Inter-Cell Outgoing Handover

Unit
Times

Related Features
ZGO-05-02-008 Multi-layer Cell Structure
15-80 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.68 C901090093 Number of incoming handover attempts from GSM1800 to GSM900 from the upper layer
Definition
Number of incoming handover attempts from GSM1800 to GSM900 from the upper layer

Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM900) receives from upper layer (GSM1800).

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover attempts at upper layer and from GSM1800 to GSM900, which helps to make the network planning.

Measurement Point
When intra-BSC target cell (GSM900) receives the channel application request from the source cell (GSM1800), 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-75.
Figure 15-75 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

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

15-81 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.69 C901090096 Number of outgoing handover attempts from GSM1800 to GSM900 to the upper layer
Definition
Number of outgoing handover attempts from GSM1800 to GSM900 to the upper layer

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM1800) sends to upper layer (GSM900).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts from GSM1800 to GSM900 to the upper layer, 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 upper layer (GSM900) and the current serving cell is GSM1800, the counter increments. The measurement point is A, as shown in Figure 15-76.
Figure 15-76 BSC-Controlled Inter-Cell Outgoing Handover Attempt

Unit
Times

15-82 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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

15.70 C901090097 Number of outgoing handover from GSM1800 to GSM900 to the upper layer
Definition
Number of outgoing handover from GSM1800 to GSM900 to the upper layer

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends to upper layer (GSM900).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts from GSM1800 to GSM900 to the upper layer, which helps to make the network planning.

Measurement Point
During the process of BSC-controlled handover, if the source cell (GSM1800) receives the radio resource unavailable 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 A, as shown in Figure 15-77.
Figure 15-77 BSC-Controlled Inter-Cell Outgoing Handover Execution Flow

Unit
Times

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

15-83 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.71 C901090098 Number of outgoing handover success from GSM1800 to GSM900 to the upper layer
Definition
Number of outgoing handover success from GSM1800 to GSM900 to the upper layer

Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends from upper layer to the same frequency (GSM900).

Usage
This counter is used to find out the frequency of successful BSC-controlled outgoing handover from upper layer to the same frequency and from GSM1800 to 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 upper layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-78.
Figure 15-78 Successful BSC-Controlled Inter-Cell Outgoing Handover

Unit
Times

Related Features
ZGO-05-02-008 Multi-layer Cell Structure
15-84 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.72 C901090099 Number of incoming handover attempts from GSM1800 to GSM900 from the lower layer
Definition
Number of incoming handover attempts from GSM1800 to GSM900 from the lower layer

Description
This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM900) receives from lower layer (GSM1800).

Usage
This counter is used to find out the frequency of BSC-controlled incoming handover attempts from GSM1800 to GSM900 from the lower layer, which helps to make the network planning.

Measurement Point
When intra-BSC target cell (GSM900) receives the channel application request from the source cell (GSM1800), 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-79.
Figure 15-79 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

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

15-85 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.73 C901090102 Number of outgoing handover attempts from GSM1800 to GSM900 to the lower layer
Definition
Number of outgoing handover attempts from GSM1800 to GSM900 to the lower layer

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM1800) sends to lower layer (GSM900).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts from GSM1800 to GSM900 to the lower layer, 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 lower layer (GSM900) and the current serving cell is GSM1800, the counter increments. The measurement point is A, as shown in Figure 15-80.
Figure 15-80 BSC-Controlled Inter-Cell Outgoing Handover Attempt

Unit
Times

15-86 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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

15.74 C901090103 Number of outgoing handover from GSM1800 to GSM900 to the lower layer
Definition
Number of outgoing handover from GSM1800 to GSM900 to the lower layer

Description
This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends to lower layer (GSM900).

Usage
This counter is used to find out the frequency of BSC-controlled outgoing handover attempts from GSM1800 to GSM900 to the lower layer, which helps to make the network planning.

Measurement Point
During the process of BSC-controlled handover, if the source cell (GSM1800) receives the radio resource unavailable 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 shown in Figure 15-81.
Figure 15-81 BSC-Controlled Inter-Cell Outgoing Handover Execution Flow

Unit
Times

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

15-87 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.75 C901090104 Number of outgoing handover success from GSM1800 to GSM900 to the lower layer
Definition
Number of outgoing handover success from GSM1800 to GSM900 to the lower layer

Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends from the same frequency to lower layer (GSM900).

Usage
This counter is used to find out the frequency of successful BSC-controlled outgoing handover from the same frequency from GSM1800 to GSM900 to the lower layer, which helps to make the network planning.

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 lower layer and the same frequency, the counter increments. The measurement point is A, as shown in Figure 15-82.
Figure 15-82 Successful BSC-Controlled Inter-Cell Outgoing Handover

Unit
Times

Related Features
ZGO-05-02-008 Multi-layer Cell Structure
15-88 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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
BSC starts the handover decision after it receives the measurement report from MS. If intra-cell handover is necessary, the counter increments. The measurement point is A, as shown in Figure 15-83.
Figure 15-83 Intra-Cell Handover Attempt

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15-89 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
BSC starts the handover decision after it receives the measurement report from MS. If inner-circle-to-outer-circle handover is necessary, the counter increments. The measurement point is A, as shown in Figure 15-84.
Figure 15-84 Intra-Cell Handover Attempt

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15-90 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.78 C901090109 Number of intra-cell 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 counter increments. The measurement point is A, as shown in Figure 15-85.
Figure 15-85 Successful Intra-Cell Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15-91 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.79 C901090110 Number of intra-cell 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 by MS when configuring the sub cell.

Usage
This counter is used to find out the frequency of inter-sub cell outer-circle-to-inner-circle handover attempts. It is one of the parameters to measure the sub cell operation status.

Measurement Point
BSC starts the handover decision after it receives the measurement report from MS. If outer-circle-to-inner-circle handover is necessary, the counter increments. The measurement point is A, as shown in Figure 15-86.
Figure 15-86 Intra-Cell Handover Attempt

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15-92 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.80 C901090111 Number of intra-cell 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 originated by MS when configuring the sub cell.

Usage
This counter is used to find out the frequency of successful inter-sub cell outer-circle-to-inner-circle handovers, and is to find out the success ratio of intra-sub cell handovers.

Measurement Point
During handover, if the source instance receives the handover completed message from the target instance, and the application cause is outer-circle-to-inner-circle handover, the counter increments. The measurement point is A, as shown in Figure 15-87.
Figure 15-87 Successful Intra-Cell Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15-93 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.81 C901090112 Number of intra-cell inner-circle-to-inner-circle handover attempts

Definition
Number of intra-cell inner-circle-to-inner-circle handover attempts

Description
This counter counts the number of inner-circle-to-inner-circle handover attempts originated by MS when configuring the sub cell.

Usage
This counter is used to find out the frequency of inter-sub cell inner-circle-to-inner-circle handover attempts. It is one of the parameters to measure the sub cell operation status.

Measurement Point
BSC starts the handover decision after it receives the measurement report from MS. If inner-circle-to-inner-circle handover is necessary, the counter increments. The measurement point is A, as shown in Figure 15-88.
Figure 15-88 Intra-Cell Handover Attempt

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15-94 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.82 C901090113 Number of intra-cell inner-circle-to-inner-circle handover success

Definition
Number of intra-cell inner-circle-to-inner-circle handover success

Description
This counter counts the number of successful inner-circle-to-inner-circle handovers originated by MS when configuring the sub cell.

Usage
This counter is used to find out the frequency of successful inter-sub cell inner-circle-to-inner-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-inner-circle handover, the counter increments. The measurement point is A, as shown in Figure 15-89.
Figure 15-89 Successful Intra-Cell Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15-95 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.83 C901090114 Number of intra-cell 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 by MS when configuring the sub cell.

Usage
This counter is used to find out the frequency of inter-sub cell outer-circle-to-outer-circle handover attempts. It is one of the parameters to measure the sub cell operation status.

Measurement Point
BSC starts the handover decision after it receives the measurement report from MS. If outer-circle-to-outer-circle handover is necessary, the counter increments. The measurement point is A, as shown in Figure 15-90.
Figure 15-90 Intra-Cell Handover Attempt

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15-96 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.84 C901090115 Number of intra-cell 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 originated by MS when configuring the sub cell.

Usage
This counter is used to find out the frequency of successful inter-sub cell outer-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 outer-circle-to-outer-circle handover, the counter increments. The measurement point is A, as shown in Figure 15-91.
Figure 15-91 Successful Intra-Cell Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

15-97 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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 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.
Figure 15-92 MSC-Controlled Outgoing Handover Attempts

Unit
Times

Related Features
ZGO-02-02-014 IMSI Based Handover ZGO-02-03-002 GSM/WCDMA Interworking

15-98 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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
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 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 measurement point is A, as shown in Figure 15-93.
Figure 15-93 MSC-Controlled Outgoing Handover

Unit
Times

Related Features
ZGO-02-02-014 IMSI Based Handover ZGO-02-03-002 GSM/WCDMA Interworking

15-99 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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 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, as shown in Figure 15-94.
Figure 15-94 Successful MSC-Controlled Outgoing Handover

Unit
Times

Related Features
ZGO-02-02-014 IMSI Based Handover ZGO-02-03-002 GSM/WCDMA Interworking
15-100 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.88 C901090119 Number of handover attempts from 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 one of the parameters to measure the wireless environment.

Measurement Point
When 2G cell receives the channel application request, if the application cause is external incoming handover and the source cell is 3G cell, the counter increments. The measurement point is A, as shown inFigure 15-95.
Figure 15-95 MSC-Controlled Incoming Handover Attempts

Unit
Times

Related Features
ZGO-02-03-002 GSM/WCDMA Interworking

15-101 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 parameters to measure the wireless environment.

Measurement Point
When 2G cell receives the channel handover request from MSC, if the channel is successfully allocated and activated, and the source cell is 3G cell, the counter increments. The measurement point is A, as shown in Figure 15-96.
Figure 15-96 MSC-Controlled Incoming Handover

Unit
Times

Related Features
ZGO-02-03-002 GSM/WCDMA Interworking

15.90 C901090121 Number of handover success from 3G to 2G

Definition
Number of handover success from 3G to 2G
15-102 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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 increments. The measurement point is A, as shown in Figure 15-97.
Figure 15-97 MSC-Controlled Incoming Handover Success

Unit
Times

Related Features
ZGO-02-03-002 GSM/WCDMA Interworking

15.91 C901090122 Number of intra-cell handover 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-103 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 point is A, as shown in Figure 15-98.
Figure 15-98 Intra-Cell Incoming Handover Attempt

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

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 handover attempts. It is one of the parameters to measure the wireless environment.

Measurement Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/F; if the new channel is successfully applied and activated, the counter increments. The measurement point is A, as shown in Figure 15-99.
15-104 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-99 Intra-Cell Incoming Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

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
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/F; if MS successfully accesses the new channel and the new channel is TCH/F, the counter increments. The measurement point is A, as shown in Figure 15-100.

15-105 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-100 Successful Intra-Cell Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

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 handover attempts. It is one of the parameters to measure the wireless environment.

Measurement Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/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-106 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-101 Intra-Cell Incoming Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation

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 handover originated by MS.

Usage
This counter is used to find out the frequency of successful intra-cell TCH/F-to-TCH/H incoming handover. It is one of the parameters to measure the wireless environment.

Measurement Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/F; if MS successfully accesses the new channel and the new channel is TCH/H, the counter increments. The measurement point is A, as shown in Figure 15-102.
15-107 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-102 Successful Intra-Cell Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation

15.96 C901090127 Number of intra-cell handover 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
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/H, the counter increments. The measurement point is A, as shown in Figure 15-103.

15-108 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-103 Intra-Cell Incoming Handover Attempt

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

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 handover attempts. It is one of the parameters to measure the wireless environment.

Measurement Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/H; if the new channel is successfully applied and activated and the new channel is TCH/F, the counter increments. The measurement point is A, as shown in Figure 15-104.

15-109 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-104 Intra-Cell Incoming Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation

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 handover originated by MS.

Usage
This counter is used to find out the frequency of successful intra-cell TCH/H-to-TCH/F incoming handover. It is one of the parameters to measure the wireless environment.

Measurement Point
When BSC receives the channel application request, if the application cause is intra-cell 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, shown in Figure 15-105.
15-110 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-105 Successful Intra-Cell Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation

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 handover attempts. It is one of the parameters to measure the wireless environment.

Measurement Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/H; if the new channel is successfully applied and activated and the new channel is TCH/H, the counter increments. The measurement point is A, as shown in Figure 15-106.
15-111 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-106 Intra-Cell Incoming Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

15.100 C901090131 Number of intra-cell TCH/H-to-TCH/H handover success

Definition
Number of intra-cell TCH/H-to-TCH/H handover success

Description
This counter counts the number of successful intra-cell TCH/H-to-TCH/H incoming handover originated by MS.

Usage
This counter is used to find out the frequency of successful intra-cell TCH/H-to-TCH/H incoming handover. It is one of the parameters to measure the wireless environment.

Measurement Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/H; if MS successfully accesses the new channel and the new channel is TCH/H, the counter increments. The measurement point is A, as shown in Figure 15-107.

15-112 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-107 Successful Intra-Cell Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

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 point is A, as shown in Figure 15-108.

15-113 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-108 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

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 handover attempts. 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; if the new channel is successfully applied and activated, the counter increments. The measurement point is A, as shown in Figure 15-109.

15-114 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-109 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

15.103 C901090134 Number of inter-cell TCH/F-to-TCH/F handover success

Definition
Number of inter-cell TCH/F-to-TCH/F handover success

Description
This counter counts the number of successful inter-cell TCH/F-to-TCH/F incoming handover originated by MS.

Usage
This counter is used to find out the frequency of successful inter-cell TCH/F-to-TCH/F incoming handover. It is one of the parameters to measure the wireless environment.

Measurement Point
When BSC receives the channel application request, if the application cause is inter-cell handover, and the source channel is TCH/F; if MS successfully accesses the new channel and the new channel is TCH/F, the counter increments. The measurement point is A, as shown in Figure 15-110.

15-115 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-110 BSC-Controlled Inter-Cell Incoming Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

15.104 C901090135 Number of inter-cell TCH/F-to-TCH/H handover

Definition
Number of inter-cell TCH/F-to-TCH/H handover

Description
This counter counts the number of inter-cell TCH/F-to-TCH/H incoming handover originated by MS.

Usage
This counter is used to find out the frequency of inter-cell TCH/F-to-TCH/H incoming handover attempts. 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; if the new channel is successfully applied and activated and the new channel is TCH/H, the counter increments. The measurement point is A, as shown in Figure 15-111.

15-116 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-111 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation

15.105 C901090136 Number of inter-cell TCH/F-to-TCH/H handover success

Definition
Number of inter-cell TCH/F-to-TCH/H handover success

Description
This counter counts the number of successful inter-cell TCH/F-to-TCH/H incoming handover originated by MS.

Usage
This counter is used to find out the frequency of successful inter-cell TCH/F-to-TCH/H incoming handover. It is one of the parameters to measure the wireless environment.

Measurement Point
When BSC receives the channel application request, if the application cause is inter-cell handover, and the source channel is TCH/F; if MS successfully accesses the new channel and the new channel is TCH/H, the counter increments. The measurement point is A, as shown in Figure 15-112.
15-117 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-112 BSC-Controlled Inter-Cell Incoming Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation

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
When BSC receives the channel application request, if the application cause is inter-cell handover, and the source channel is TCH/H, the counter increments. The measurement point is A, as shown in Figure 15-113.
15-118 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-113 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

15.107 C901090138 Number of inter-cell TCH/H-to-TCH/F handover

Definition
Number of inter-cell TCH/H-to-TCH/F handover

Description
This counter counts the number of inter-cell TCH/H-to-TCH/F incoming handover originated by MS.

Usage
This counter is used to find out the frequency of inter-cell TCH/H-to-TCH/F incoming handover attempts. 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/H; if the new channel is successfully applied and activated and the new channel is TCH/F, the counter increments. The measurement point is A, as shown in Figure 15-114.
15-119 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-114 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation

15.108 C901090139 Number of inter-cell TCH/H-to-TCH/F handover success

Definition
Number of inter-cell TCH/H-to-TCH/F handover success

Description
This counter counts the number of successful inter-cell TCH/H-to-TCH/F incoming handover originated by MS.

Usage
This counter is used to find out the frequency of successful inter-cell TCH/H-to-TCH/F incoming handover. It is one of the parameters to measure the wireless environment.

Measurement Point
When BSC receives the channel application request, if the application cause is inter-cell 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, as shown in Figure 15-115.
15-120 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-115 BSC-Controlled Inter-Cell Incoming Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation

15.109 C901090140 Number of inter-cell TCH/H-to-TCH/H handover

Definition
Number of inter-cell TCH/H-to-TCH/H handover

Description
This counter counts the number of inter-cell TCH/H-to-TCH/H incoming handover originated by MS.

Usage
This counter is used to find out the frequency of inter-cell TCH/H-to-TCH/H incoming handover attempts. 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/H; if the new channel is successfully applied and activated and the new channel is TCH/H, the counter increments. The measurement point is A, as shown in Figure 15-116.
15-121 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-116 BSC-Controlled Inter-Cell Incoming Handover Attempts

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

15.110 C901090141 Number of inter-cell TCH/H-to-TCH/H handover success

Definition
Number of inter-cell TCH/H-to-TCH/H handover success

Description
This counter counts the number of successful inter-cell TCH/H-to-TCH/H incoming handover originated by MS.

Usage
This counter is used to find out the frequency of successful inter-cell TCH/H-to-TCH/H incoming handover. It is one of the parameters to measure the wireless environment.

Measurement Point
When BSC receives the channel application request, if the application cause is inter-cell handover, and the source channel is TCH/H; if MS successfully accesses the new channel and the new channel is TCH/H, the counter increments. The measurement point is A, as shown in Figure 15-117.
15-122 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-117 BSC-Controlled Inter-Cell Incoming Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

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 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 governed by different BSCs, BSC will send MSC the handover request A_HO_RQD to trigger inter-BSC
15-123 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

handover. If 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-118.
Figure 15-118 MSC-Controlled Outgoing Handover Attempts

Unit
Times

15.112 C901090145 Number of dual band incoming 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-124 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-119 MSC-Controlled Incoming Handover Attempts

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 one of the parameters to measure the wireless environment.

Measurement Point
When BSC receives the channel application request, if the application cause is intra-cell 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 shown in Figure 15-120.

15-125 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-120 Intra-Cell Incoming Handover Attempt

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover 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-126 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

the target cell has not available radio channel. This counter increments before target cell sends forced release message to forced release instance. The measurement point is A shown in Figure 15-121.
Figure 15-121 Forced Release Attempts

Unit
Times

15.115 C901090150 Number of BSC-controlled 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-127 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

15.116 C901090151 Number of BSC-controlled inter-cell incoming handover attempts due to 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-128 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Usage
This counter counts the frequency of forced handover attempts occurred during BSC-controlled inter-cell incoming handover initiated by a MS. It can reflect the handover process.

Measurement Point
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 A, as shown in Figure 15-123.
Figure 15-123 Forced-Handover Attempts

Unit
Times

15.117 C901090152 Number of BSC-controlled inter-cell incoming handover (forced handover) (emergency service)
Definition
Number of BSC-controlled inter-cell incoming handover (forced handover) (emergency service)

15-129 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of forced handover 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 handover occurred during BSC-controlled inter-cell incoming handover initiated by a MS. It can reflect the handover process.

Measurement Point
Intra-BSC target cell receives radio channel request and adds it into a queue after sending forced handover message to forced handover instance if the request reason is BSC-controlled inter-cell incoming handover and the target cell has not available radio channel. This counter increments if target cell receives available resource message. The measurement point is A2, as shown in Figure 15-124.
Figure 15-124 BSC-Controlled Forced Handover On Incoming Handover

Unit
Times

15-130 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.118 C901090153 Number of BSC-controlled inter-cell incoming handover attempts due to 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 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 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 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.
Figure 15-125 Queuing Attempts

Unit
Times
15-131 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.119 C901090154 Number of BSC-controlled 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.
Figure 15-126 BSC-Controlled Queue On Incoming Handover

15-132 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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.

Usage
This counter counts the frequency of forced release attempts occurred during BSC-controlled inter-BSC incoming handover initiated by a MS. It can reflect the handover process.

Measurement Point
Target cell receives radio channel request to determine whether to do forced release attempt if the request reason is MSC-controlled inter-BSC incoming handover and the target cell has not available radio channel. This counter increments before target cell sends forced release message to forced release instance. The measurement point is A shown in Figure 15-127.
Figure 15-127 MSC-Controlled Forced Release Attempt On Incoming Handover

15-133 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

15.121 C901090156 Number of MSC-controlled incoming handover (forced release) (emergency service)
Definition
Number of MSC-controlled incoming handover (forced release) (emergency service)

Description
This counter counts the number of forced handover due to unavailable radio resource in target cell in the process of MSC-controlled inter-BSC incoming handover initiated by a MS on emergency service.

Usage
This counter counts the frequency of forced handover occurred during BSC-controlled inter-BSC incoming handover initiated by a MS. It can reflect the handover process.

Measurement Point
Intra-BSC target cell receives radio channel request and adds it into a queue after sending forced handover message to forced handover instance if the request reason is MSC-controlled inter-BSC incoming handover and the target cell has not available radio channel. This counter increments if target cell receives available resource message. The measurement point is A, as shown in Figure 15-128.
Figure 15-128 MSC-Controlled Forced Release On Incoming Handover

Unit
Times

15-134 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.122 C901090157 Number of MSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service)
Definition
Number of MSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service)

Description
This counter counts the number of forced handover attempts due to unavailable radio resource in target cell in the process of MSC-controlled inter-BSC incoming handover initiated by a MS on emergency service.

Usage
This counter counts the frequency of forced handover attempt occurred during MSC-controlled inter-BSC incoming handover initiated by a emergent MS. It can reflect the handover process.

Measurement Point
Target cell receives radio channel request to determine whether to do forced handover attempt if the request reason is MSC-controlled inter-BSC incoming handover and the target cell has not available radio channel. This counter increments before target cell sends forced handover message to forced handover instance. The measurement point is A, as shown in Figure 15-129.
Figure 15-129 MSC-Controlled Forced Handover Attempt On Incoming Handover

Unit
Times

15-135 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.123 C901090158 Number of MSC-controlled incoming handover (forced release) (emergency service)
Definition
Number of MSC-controlled incoming handover (forced release) (emergency service)

Description
This counter counts the number of forced handover due to unavailable radio resource in target cell in the process of MSC-controlled inter-BSC incoming handover initiated by a MS on emergency service.

Usage
This counter counts the frequency of forced handover occurred during BSC-controlled inter-BSC incoming handover initiated by a MS. It can reflect the handover process.

Measurement Point
Intra-BSC target cell receives radio channel request and adds it into a queue after sending forced handover message to forced handover instance if the request reason is MSC-controlled inter-BSC incoming handover and the target cell has not available radio channel. This counter increments if target cell receives available resource message. The measurement point is A, as shown in Figure 15-130.
Figure 15-130 MSC-Controlled Forced Handover On Incoming Handover

Unit
Times

15-136 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.124 C901090159 Number of MSC-controlled 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 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 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 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

15-137 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.125 C901090160 Number of MSC-controlled incoming handover (queue) (emergency service)

Definition
Number of MSC-controlled incoming handover (queue) (emergency service)

Description
This counter counts the number of queue due to unavailable radio resource in target cell in the process of MSC-controlled inter-BSC incoming handover initiated by a MS on emergency service.

Usage
This counter counts the frequency of queue occurred during 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.
Figure 15-132 MSC-Controlled Queue On Incoming Handover

Unit
Times

15-138 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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 BSC-controlled inter-cell incoming handover initiated by a MS. It can reflect the handover process.

Measurement Point
Intra-BSC target cell receives radio channel request if the request reason is BSC-controlled inter-cell incoming handover and the target cell has not available radio channel. This counter increments if the forced handover target is not found after initiating forced handover attempt. The measurement point is A, as shown inFigure 15-133.
Figure 15-133 Forced Handover Target Not Found (BSC-Controlled Inter-Cell Handover Due To Forced Handover)

15-139 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

15.127 C901090162 Number of send forced handover 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 handover due to forced handover)

Description
This counter counts the number of sending forced handover request to lower priority user on forced handover attempt due to unavailable radio resource in target cell in the process of BSC-controlled inter-cell incoming handover initiated by a MS.

Usage
This counter counts the frequency of sending forced handover request to a lower priority user during BSC-controlled inter-cell incoming handover initiated by a MS. It can reflect the handover process.

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

15-140 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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-141 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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 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-142 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.129 C901090164 Number of lower PRI user handover 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
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 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-143 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 handover due to forced handover)
Definition
Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced handover)

Description
This counter counts the number of timeout for waiting resource while initiating forced handover due to unavailable radio resource in target cell in the process of BSC-controlled inter-cell incoming handover initiated by a MS.

Usage
This counter counts the frequency of timeout for waiting resource while initiating forced handover during BSC-controlled inter-cell incoming handover initiated by a MS. It can reflect the handover process.
15-144 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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 timeout for waiting resource occurs after initiating forced handover. The measurement point is A, as shown in Figure 15-137.
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-145 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of forced release target not found due to unavailable radio resource in target cell in the process of BSC-controlled inter-cell incoming handover initiated by a MS.

Usage
This counter counts the frequency of forced release target not found during BSC-controlled inter-cell incoming handover initiated by a MS. It can reflect the handover process.

Measurement Point
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 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-146 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.132 C901090167 Number of high PRI user time 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 the handover process.

Measurement Point
Intra-BSC target cell receives radio channel request if the request reason is BSC-controlled inter-cell incoming handover and the target cell has not available radio channel. This counter increments if timeout for waiting resource occurs after initiating forced release. The measurement point is A, as shown in Figure 15-139.

15-147 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 handover due to forced handover)

Usage
This counter counts the frequency of handover target not found on MSC-controlled incoming handover due to forced handover. It is one of parameters to measure radio environment.

15-148 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Measurement Point
l l l l This counter increments after BSC receives incoming handover message and does forced handover attempt due to unavailable resource. This counter increments if the interval timer to search for handover target is timeout on handover. This counter increments if waiting for handover resource and handover attempt fails. This counter increments if the timer of waiting for resource is timeout after initiating forced handover.

Unit
Times

15.134 C901090169 Number of send forced handover 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 handover due to forced handover)

Description
This counter counts the number of sending forced handover request to lower PRI user (MSC-controlled incoming handover due to forced handover).

Usage
This counter counts the frequency of sending handover request to a lower priority user on MSC-controlled incoming handover due to forced handover. It is one of parameters to measure radio environment.

Measurement Point
l l l l This counter increments after BSC receives incoming handover message and does forced handover attempt due to unavailable resource. This counter increments if the interval timer to search for handover target is timeout on handover. This counter increments if waiting for handover resource and handover attempt fails. This counter increments if the timer of waiting for resource is timeout after initiating forced handover.

Unit
Times
15-149 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measure radio environment.

Measurement Point
This counter increments if BSC receives forced handover failure and incoming handover fails due to failure of resource request.

Unit
Times

15.136 C901090171 Number of lower PRI user handover 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-150 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Usage
This counter counts the frequency of handover failure for lower priority user on MSC-controlled incoming handover due to forced handover. It is one of parameters to measure radio environment.

Measurement Point
This counter increments if BSC receives forced handover failure and incoming handover fails due to failure of forced handover.

Unit
Times

15.137 C901090172 Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced handover)
Definition
Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced handover)

Description
This counter counts the number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced handover).

Usage
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 measure radio environment.

Measurement Point
This counter increments if the timer of waiting for resource after initiating forced handover.

Unit
Times

15-151 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 l l l l l This counter increments after BSC receives incoming forced release message and does forced release due to unavailable resource. This counter increments if the interval timer to search for forced release target is timeout on handover. This counter increments if waiting for handover resource and forced release fails. This counter increments if the timer of waiting for resource is timeout after initiating forced handover. This counter increments if the timer to initiate forced release is timeout on handover. This counter increments if the timer of waiting for resource is timeout after initiating forced release.

Unit
Times

15.139 C901090174 Number of high PRI user time 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-152 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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 measure radio environment.

Measurement Point
This counter increments if the timer of waiting for resource is timeout after initiating forced release.

Unit
Times

15.140 C901090175 Number of get before grab released 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-153 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.141 C901090176 Number of get before grab released 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 to eMLPP forced handover

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-154 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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. This counter increments if it is forced handover based on hierarchy and frequency relationship on BSC-controlled inter-cell or MSC-controlled outgoing handover.

Unit
Times

15.144 C901090179 Number of handover success due to eMLPP forced handover

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-155 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter increments if it is intra-cell forced handover on handover success. This counter increments if it is forced handover based on hierarchy and frequency relationship on BSC-controlled inter-cell or MSC-controlled outgoing handover success.

Unit
Times

15.145 C901090180 Number of BSC-controlled inter-cell outgoing handover attempts between PLMN
This counter is not used for the time being.

15.146 C901090181 Number of BSC-controlled inter-cell outgoing handover between PLMN

This counter is not used for the time being.

15.147 C901090182 Number of BSC-controlled inter-cell outgoing handover success between PLMN
This counter is not used for the time being.

15.148 C901090183 Number of MSC-controlled outgoing handover attempts between PLMN

This counter is not used for the time being.

15.149 C901090184 Number of MSC-controlled outgoing handover request fail between PLMN due to unknown reason
This counter is not used for the time being.

15-156 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.150 C901090185 Number of MSC-controlled outgoing handover request fail between PLMN due to unavailable ground resource
Description
This counter counts the number of failures of MSC-controlled inter-PLMN outgoing handover requests due to no available ground resource. When MSC receives the handover request rejection message from BSC on TCH, it queries the rejection cause. If the rejection cause is CAUSE_REQ_CIC_UNAVAIL, then the counter increments.

Usage
This counter is used to find out the frequency of failure of MSC-controlled inter-PLMN outgoing handover request initiated by MS due to no available ground resource. It also helps study the condition of handover initiated by MSC. This counter is supported in version V6.20.200a or above.

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-157 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.151 C901090186 Number of MSC-controlled outgoing handover request fail between PLMN due to unavailable radio resource
This counter is not used for the time being.

15.152 C901090187 Number of MSC-controlled outgoing handover request fail between PLMN due to other reasons
Description
This counter counts the number of failures of MSC-controlled inter-PLMN outgoing handover requests due to other reasons. When MSC receives the handover request rejection message from BSC on TCH, it queries the rejection cause. If the rejection cause is not CAUSE_REQ_CIC_UNAVAIL or CAUSE_NO_RR_AVAIL, then 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. This counter is supported in version V6.20.200a or above.

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

15.153 C901090188 Number of MSC-controlled 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-158 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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. This counter is supported in version V6.20.200a or above.

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-159 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.154 C901090189 Number of MSC-controlled 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. This counter is supported in version V6.20.200a or above.

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

15.155 C901090190 Number of BSC-controlled inter-cell incoming handover attempt between PLMN
This counter is not used for the time being.

15.156 C901090191 Number of BSC-controlled inter-cell incoming handover between PLMN

This counter is not used for the time being.

15.157 C901090192 Number of BSC-controlled inter-cell incoming handover force-release attempt between PLMN
This counter is not used for the time being.

15-160 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.158 C901090193 Number of BSC-controlled inter-cell incoming handover between PLMN due to force release
This counter is not used for the time being.

15.159 C901090194 Number of BSC-controlled inter-cell incoming handover queue attempt between PLMN
This counter is not used for the time being.

15.160 C901090195 Number of BSC-controlled inter-cell incoming handover between PLMN due to queue
This counter is not used for the time being.

15.161 C901090196 Number of BSC-controlled inter-cell incoming handover force-handover attempt between PLMN
This counter is not used for the time being.

15.162 C901090197 Number of BSC-controlled inter-cell incoming handover between PLMN due to force handover
This counter is not used for the time being.

15.163 C901090198 Number of BSC-controlled inter-cell incoming handover success between PLMN
This counter is not used for the time being.

15-161 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.164 C901090199 Number of MSC-controlled 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. This counter is supported in version V6.20.200a or above.

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 shown in Figure 15-143.
Figure 15-143 MSC-Controlled Inter-PLMN Incoming Handover Flow

Unit
Times

15-162 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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. This counter is supported in version V6.20.200a or above.

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-163 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.166 C901090201 A interface incoming handover fail between PLMN due to circuit unmatch
Description
This counter counts the number of A-interface inter-PLMN incoming handover failures due to circuit mismatching. When MSC receives the Handover Failure message, if the handover fails due to CAUSE_CIRCUIT_POOL_MISMATCH and the handover is inter-PLMN handover, then the counter increments.

Usage
This counter is used to find out the number of A-interface inter-PLMN incoming handover failures due to circuit mismatching. It also helps study the handover initiated by MSC. This counter is supported in version V6.20.200a or above.

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

15.167 C901090202 A interface incoming handover fail between PLMN due to unavailable radio resource
Description
This counter counts the number of A-interface inter-PLMN incoming handover failures due to no available radio resource. When MSC receives the Handover Failure message or RanA receives the Handover Failure message, if the handover failure cause is CAUSE_NO_RR_AVAI and the handover is inter-PLMN handover, the counter increments.

Usage
This counter is used to find out the number of A-interface inter-PLMN incoming handover failures due to no available radio resource. It also helps study the handover initiated by MSC. This counter is supported in version V6.20.200a or above.

15-164 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

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, then the counter counts.

Unit
Times

15.168 C901090203 A interface incoming handover fail between PLMN due to other reason
This counter is not used for the time being.

15.169 C901090204 Number of MSC-controlled incoming handover between PLMN

This counter is not used for the time being.

15.170 C901090205 Number of MSC-controlled 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. This counter is supported in version V6.20.200a or above.

15-165 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

15.171 C901090206 Number of MSC-controlled 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
This counter is used to find out the number of MSC-controlled inter-PLMN incoming handover due to forced release. It also helps study the inter-PLMN incoming handover initiated by MSC due to forced release. This counter is supported in version V6.20.200a or above.

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

15.172 C901090207 Number of MSC-controlled incoming handover queue attempt between PLMN
Description
This counter counts the number of attempts of MSC-controlled inter-PLMN incoming handover queuing. When BSC receives the command Ho Req from MSC, it sends the

15-166 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

command Chan Act to BTS. If channel requests fails but queuing is allowed, the counter increments.

Usage
This counter is used to find out the number of attempts of MSC-controlled inter-PLMN incoming handover queuing. It also helps study the inter-PLMN incoming handover, which is initiated by MSC, in case of no channel resource. This counter is supported in version V6.20.200a or above.

Measurement Point
When BSC receives the command Ho Req from MSC, it sends the command Chan Act to BTS. If no channel request fails but queuing is allowed, then the counter counts. The measurement point is A1, as shown in Figure 15-145.
Figure 15-145 Inter-MSC Handover

Unit
Times

15.173 C901090208 Number of MSC-controlled 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-167 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of MSC-controlled inter-PLMN incoming handover due to queuing. It also helps study the inter-PLMN incoming handover, which is initiated by MSC, in case of no channel resource. This counter is supported in version V6.20.200a or above.

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

15.174 C901090209 Number of MSC-controlled incoming handover force-handover attempt between PLMN
Description
This counter counts the number of attempts of MSC-controlled inter-PLMN incoming handover force-handover. When BSC receives the command Ho Req from MSC, it sends the command Chan Act to BTS. If channel requests fails but forced handover is allowed, the counter increments.

Usage
This counter is used to find out the number of attempts of MSC-controlled inter-PLMN incoming handover force-handover. It also helps study the inter-PLMN incoming handover, which is initiated by MSC, in case of no channel resource. This counter is supported in version V6.20.200a or above.

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-168 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.175 C901090210 Number of MSC-controlled incoming handover between PLMN due to force handover
This counter is not used for the time being.

15.176 C901090211 Number of MSC-controlled incoming handover success between PLMN

This counter is not used for the time being.

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. This counter is supported in version V6.20.210a or above.

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-169 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. This counter is supported in version V6.20.210a or above.

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 measurement point is A1, as shown in Figure 15-146.
Figure 15-146 Handover Success due to CS Service Migration

Unit
Times

15.179 C901090214 Number of handover attempt from AMR FR to AMR HR due to high load
Description
When the cell's traffic load increases and reaches the threshold of handover from AMR FR to AMR HR, it will trigger the process of finding an existed AMR FR call in the cell. If the appropriate call is found, the intra-cell handover attempt from AMR FR to AMR HR will be initiated, and the counter increments. The measurement point is A1, as shown in Figure 15-147.
15-170 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-147 Intra-cell Handover Flow

This counter is supported in version V6.20.614a.

Unit
Times

Statistics Object
Cell

15.180 C901090215 Number of handover from AMR FR to AMR HR due to high load
Description
When the cell's traffic load increases and reaches the threshold of handover from AMR FR to AMR HR,if the radio resource is available and the channel activation succeeds, the counter increments. The measurement point is A2, as shown in Figure 15-148.
Figure 15-148 Intra-cell Handover Flow

This counter is supported in version V6.20.614a.

Unit
Times

15-171 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Statistics Object
Cell

15.181 C901090216 Number of handover success from AMR FR to AMR HR due to high load
Description
When the cell's traffic load increases and reaches the threshold of handover from AMR FR to AMR HR,if the MS successfully performs handover to the new channel and the handover completion message is sent, the counter increments. The measurement point is A3, as shown in Figure 15-149.
Figure 15-149 Intra-cell Handover Flow

This counter is supported in version V6.20.614a.

Unit
Times

Statistics Object
Cell

15.182 C901090217 Number of handover attempt from FR to HR due to high load

Description
When the cell's traffic load increases and reaches the threshold of handover from FR to HR, it will trigger the process of finding an existed AMR FR call or FR call in the cell. It finds the AMR FR call first, and then finds the FR call if no appropriate AMR FR call is found. If an appropriate FR call is found, the intra-cell handover attempt from FR to HR will be initiated, and the counter increments. The measurement point is A1, as shown in Figure 15-150.
15-172 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-150 Intra-cell Handover Flow

This counter is supported in version V6.20.614a.

Unit
Times

Statistics Object
Cell

15.183 C901090218 Number of handover from FR to HR due to high load

Description
When the cell's traffic load increases and reaches the threshold of handover from FR to HR,if the radio resource is available and the channel activation succeeds, the counter increments. The measurement point is A2, as shown in Figure 15-151.
Figure 15-151 Intra-cell Handover Flow

This counter is supported in version V6.20.614a.

Unit
Times

15-173 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Statistics Object
Cell

15.184 C901090219 Number of handover success from FR to HR due to high load

Description
When the cell's traffic load increases and reaches the threshold of handover from FR to HR,if the MS successfully performs handover to the new channel and the handover completion message is sent, the counter increments. The measurement point is A3, as shown in Figure 15-152.
Figure 15-152 Intra-cell Handover Flow

This counter is supported in version V6.20.614a.

Unit
Times

Statistics Object
Cell

15.185 C901090220 Number of handover attempt from AMR HR to AMR FR due to bad quality
Description
Suppose the voice quality of an AMR HR call is poor. If all other handover conditions are not satisfied but the threshold of intra-cell handover from AMR HR to AMR FR is reached, the intra-cell handover attempt from AMR HR to AMR FR is initiated, and the counter increments. The measurement point is A1, as shown in Figure 15-153.

15-174 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-153 Intra-cell Handover Flow

This counter is supported in version V6.20.614a.

Unit
Times

Statistics Object
Cell

15.186 C901090221 Number of handover from AMR HR to AMR FR due to bad quality
Description
When the intra-cell handover from AMR HR to AMR FR is caused due to bad quality, if the radio resource is available and the channel activation succeeds, the counter increments. The measurement point is A2, as shown in Figure 15-154.
Figure 15-154 Intra-cell Handover Flow

This counter is supported in version V6.20.614a.

Unit
Times

15-175 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Statistics Object
Cell

15.187 C901090222 Number of handover success from AMR HR to AMR FR due to bad quality
Description
When the intra-cell handover from AMR HR to AMR FR is caused due to bad quality, if the MS successfully performs handover to the new channel and the handover completion message is sent, the counter increments. The measurement point is A3, as shown in Figure 15-155.
Figure 15-155 Intra-cell Handover Flow

This counter is supported in version V6.20.614a.

Unit
Times

Statistics Object
Cell

15.188 C901090223 Number of handover attempt from HR to FR due to bad quality

Description
Suppose the voice quality of an HR call is poor. If all other handover conditions are not satisfied but the threshold of intra-cell handover from HR to FR is reached, the intra-cell handover attempt from HR to FR is initiated, and the counter increments. The measurement point is A1, as shown in Figure 15-156.

15-176 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-156 Intra-cell Handover Flow

This counter is supported in version V6.20.614a.

Unit
Times

Statistics Object
Cell

15.189 C901090224 Number of handover from HR to FR due to bad quality

Description
When the intra-cell handover from HR to FR is caused due to bad quality, if the radio resource is available and the channel activation succeeds, the counter increments. The measurement point is A2, as shown in Figure 15-157.
Figure 15-157 Intra-cell Handover Flow

This counter is supported in version V6.20.614a.

Unit
Times

15-177 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Statistics Object
Cell

15.190 C901090225 Number of handover success from HR to FR due to bad quality

Description
When the intra-cell handover from HR to FR is caused due to bad quality, if the MS successfully performs handover to the new channel and the handover completion message is sent, the counter increments. The measurement point is A3, as shown in Figure 15-158.
Figure 15-158 Intra-cell Handover Flow

This counter is supported in version V6.20.614a.

Unit
Times

Statistics Object
Cell

15.191 C901090226 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM900
Description
During the process of intra-BSC inter-cell handover, after BSC receives the measurement report from MS, it performs handover decision. If it decides intra-BSC inter-cell handover is required and if the source cell's frequency band is 900 MHz and the destination cell's frequency band is 900 MHz, the counter increments. The measurement point is A1, as shown in Figure 15-159.
15-178 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-159 Intra-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.192 C901090227 Number of BSC-controlled inter-cell outgoing handover, from GSM900 to GSM900
Description
During the process of intra-BSC inter-cell handover, after BSC successfully activates channel for BTS in the destination cell, it sends the HANDOVER COMMAND message to MS in the source cell. If the source cell's frequency band is 900 MHz and the destination cell's frequency band is 900 MHz, the counter increments. The measurement point is A2, as shown in Figure 15-160.

15-179 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-160 Intra-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.193 C901090228 Number of BSC-controlled inter-cell outgoing handover success, from GSM900 to GSM900
Description
During the process of intra-BSC inter-cell handover, after BSC sends the HANDOVER COMMAND message to MS in the source cell, MS successfully accesses the destination channel, and BSC receives the HANDOVER COMPLETE message from the destination cell. If the source cell's frequency band is 900 MHz and the destination cell's frequency band is 900 MHz, the counter increments. The measurement point is A3, as shown in Figure 15-161.

15-180 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-161 Intra-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.194 C901090229 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM1800
Description
During the process of intra-BSC inter-cell handover, after BSC receives the measurement report from MS, it performs handover decision. If it decides intra-BSC inter-cell handover is required and if the source cell's frequency band is 1800 MHz and the destination cell's frequency band is 1800 MHz, the counter increments. The measurement point is A1, as shown in Figure 15-162.

15-181 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-162 Intra-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.195 C901090230 Number of BSC-controlled inter-cell outgoing handover, from GSM1800 to GSM1800
Description
During the process of intra-BSC inter-cell handover, after BSC successfully activates channel for BTS in the destination cell, it sends the HANDOVER COMMAND message to MS in the source cell. If the source cell's frequency band is 1800 MHz and the destination cell's frequency band is 1800 MHz, the counter increments. The measurement point is A2, as shown in Figure 15-163.

15-182 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-163 Intra-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.196 C901090231 Number of BSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM1800
Description
During the process of intra-BSC inter-cell handover, after BSC sends the HANDOVER COMMAND message to MS in the source cell, MS successfully accesses the destination channel, and BSC receives the HANDOVER COMPLETE message from the destination cell. If the source cell's frequency band is 1800 MHz and the destination cell's frequency band is 1800 MHz, the counter increments. The measurement point is A3, as shown in Figure 15-164.

15-183 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-164 Intra-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.197 C901090232 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM1800
Description
During the process of intra-BSC inter-cell handover, after BSC receives the measurement report from MS, it performs handover decision. If it decides intra-BSC inter-cell handover is required and if the source cell's frequency band is 900 MHz and the destination cell's frequency band is 1800 MHz, the counter increments. The measurement point is A1, as shown in Figure 15-165.

15-184 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-165 Intra-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.198 C901090233 Number of BSC-controlled inter-cell outgoing handover, from GSM900 to GSM1800
Description
During the process of intra-BSC inter-cell handover, after BSC successfully activates channel for BTS in the destination cell, it sends the HANDOVER COMMAND message to MS in the source cell. If the source cell's frequency band is 900 MHz and the destination cell's frequency band is 1800 MHz, the counter increments. The measurement point is A2, as shown in Figure 15-166.

15-185 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-166 Intra-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.199 C901090234 Number of BSC-controlled inter-cell outgoing handover success, from GSM900 to GSM1800
Description
During the process of intra-BSC inter-cell handover, after BSC sends the HANDOVER COMMAND message to MS in the source cell, MS successfully accesses the destination channel, and BSC receives the HANDOVER COMPLETE message from the destination cell. If the source cell's frequency band is 900 MHz and the destination cell's frequency band is 1800 MHz, the counter increments. The measurement point is A3, as shown in Figure 15-167.

15-186 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-167 Intra-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.200 C901090235 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM900
Description
During the process of intra-BSC inter-cell handover, after BSC receives the measurement report from MS, it performs handover decision. If it decides intra-BSC inter-cell handover is required and if the source cell's frequency band is 1800 MHz and the destination cell's frequency band is 900 MHz, the counter increments. The measurement point is A1, as shown in Figure 15-168.

15-187 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-168 Intra-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.201 C901090236 Number of BSC-controlled inter-cell outgoing handover, from GSM1800 to GSM900
Description
During the process of intra-BSC inter-cell handover, after BSC successfully activates channel for BTS in the destination cell, it sends the HANDOVER COMMAND message to MS in the source cell. If the source cell's frequency band is 1800 MHz and the destination cell's frequency band is 900 MHz, the counter increments. The measurement point is A2, as shown in Figure 15-169.

15-188 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-169 Intra-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.202 C901090237 Number of BSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM900
Description
During the process of intra-BSC inter-cell handover, after BSC sends the HANDOVER COMMAND message to MS in the source cell, MS successfully accesses the destination channel, and BSC receives the HANDOVER COMPLETE message from the destination cell. If the source cell's frequency band is 1800 MHz and the destination cell's frequency band is 900 MHz, the counter increments. The measurement point is A3, as shown in Figure 15-170.

15-189 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-170 Intra-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.203 C901090238 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM900
Description
During the process of inter-BSC inter-cell handover, the source BSC sends the HANDOVER REQUIRED message to MSC. If the source cell's frequency band is 900 MHz and the destination cell's frequency band is 900 MHz, the counter increments. The measurement point is A4, as shown in Figure 15-171.

15-190 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-171 Inter-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.204 C901090239 Number of MSC-controlled inter-cell outgoing handover, from GSM900 to GSM900
Description
During the process of inter-BSC inter-cell handover, the source BSC receives the HANDOVER COMMAND message from MSC. If the source cell's frequency band is 900 MHz and the destination cell's frequency band is 900 MHz, the counter increments. The measurement point is A5, as shown in Figure 15-172.

15-191 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-172 Inter-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.205 C901090240 Number of MSC-controlled inter-cell outgoing handover success, from GSM900 to GSM900
Description
During the process of inter-BSC inter-cell handover, MS successfully performs handover to the destination BSC, and the source BSC receives the CLEAR COMMAND message from MSC and the cause is handover success. If the source cell's frequency band is 900 MHz and the destination cell's frequency band is 900 MHz, the counter increments. The measurement point is A6, as shown in Figure 15-173.

15-192 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-173 Inter-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.206 C901090241 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM1800
Description
During the process of inter-BSC inter-cell handover, the source BSC sends the HANDOVER REQUIRED message to MSC. If the source cell's frequency band is 1800 MHz and the destination cell's frequency band is 1800 MHz, the counter increments. The measurement point is A4, as shown in Figure 15-174.

15-193 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-174 Inter-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.207 C901090242 Number of MSC-controlled inter-cell outgoing handover, from GSM1800 to GSM1800
Description
During the process of inter-BSC inter-cell handover, the source BSC receives the HANDOVER COMMAND message from MSC. If the source cell's frequency band is 1800 MHz and the destination cell's frequency band is 1800 MHz, the counter increments. The measurement point is A5, as shown in Figure 15-175.

15-194 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-175 Inter-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.208 C901090243 Number of MSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM1800
Description
During the process of inter-BSC inter-cell handover, MS successfully performs handover to the destination BSC, and the source BSC receives the CLEAR COMMAND message from MSC and the cause is handover success. If the source cell's frequency band is 1800 MHz and the destination cell's frequency band is 1800 MHz, the counter increments. The measurement point is A6, as shown in Figure 15-176.

15-195 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 15-176 Inter-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.209 C901090244 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM1800
Description
During the process of inter-BSC inter-cell handover, the source BSC sends the HANDOVER REQUIRED message to MSC. If the source cell's frequency band is 900 MHz and the destination cell's frequency band is 1800 MHz, the counter increments. The measurement point is A4, as shown in Figure 15-177.
Figure 15-177 Inter-BSC Inter-cell Handover Flow

15-196 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.210 C901090245 Number of MSC-controlled inter-cell outgoing handover, from GSM900 to GSM1800
Description
During the process of inter-BSC inter-cell handover, the source BSC receives the HANDOVER COMMAND message from MSC. If the source cell's frequency band is 900 MHz and the destination cell's frequency band is 1800 MHz, the counter increments. The measurement point is A5, as shown in Figure 15-178.
Figure 15-178 Inter-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15-197 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

15.211 C901090246 Number of MSC-controlled inter-cell outgoing handover success, from GSM900 to GSM1800
Description
During the process of inter-BSC inter-cell handover, MS successfully performs handover to the destination BSC, and the source BSC receives the CLEAR COMMAND message from MSC and the cause is handover success. If the source cell's frequency band is 900 MHz and the destination cell's frequency band is 1800 MHz, the counter increments. The measurement point is A6, as shown in Figure 15-179.
Figure 15-179 Inter-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.212 C901090247 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM900
Description
During the process of inter-BSC inter-cell handover, the source BSC sends the HANDOVER REQUIRED message to MSC. If the source cell's frequency band is 1800 MHz and the destination cell's frequency band is 900 MHz, the counter increments. The measurement point is A4, as shown in Figure 15-180.
15-198 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-180 Inter-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.213 C901090248 Number of MSC-controlled inter-cell outgoing handover, from GSM1800 to GSM900
Description
During the process of inter-BSC inter-cell handover, the source BSC receives the HANDOVER COMMAND message from MSC. If the source cell's frequency band is 1800 MHz and the destination cell's frequency band is 900 MHz, the counter increments. The measurement point is A5, as shown in Figure 15-181.
Figure 15-181 Inter-BSC Inter-cell Handover Flow

15-199 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15.214 C901090249 Number of MSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM900
Description
During the process of inter-BSC inter-cell handover, MS successfully performs handover to the destination BSC, and the source BSC receives the CLEAR COMMAND message from MSC and the cause is handover success. If the source cell's frequency band is 1800 MHz and the destination cell's frequency band is 900 MHz, the counter increments. The measurement point is A6, as shown in Figure 15-182.
Figure 15-182 Inter-BSC Inter-cell Handover Flow

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

15-200 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

15.215 C901090250 Number of Inter-BSC Incoming Handover Failure Due to New Channel Access Failure
Description
This counter counts the number of the inter-BSC incoming handover failures due to new channel access failure. The counter is updated in the following two cases: 1. When the BSC waits for mobile station (MS) access after the new channel is activated, no MS access is discovered until the protection timer times out. 2. When waiting for the MS access after the new channel is activated, the BSC receives the ClearCommand message sent by the MSC due to the radio interface fault or radio interface message failure.

Usage
None

Measurement Point
None

Unit
Time

15.216 C901090251 Number of Inter-BSC Incoming Handover Failure Due to MS Return to Old Channel
Description
This counter counts the number of the inter-BSC incoming handover failures due to MS return to the old channel. When waiting for the MS access after the new channel is activated, the BSC receives the ClearCommand message sent by the MSC due to the radio interface fault and MS return to the old channel. In this case, the counter is updated.

Usage
None

Measurement Point
None
15-201 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Time

15.217 C901090264 The Number of forbid sending hand command during releasing
Measured Object
Cell

Description
This counter is incremented each time the BSC does not send a handover command after receiving a layer3 DISCONNECT or RELEASE message because a handover already occurs, to prevent release exception during the handover of the MS.

Usage
None

Measurement Point
The measurement point, A1, varies with intra-BSC handover and inter-BSC handover, as shown in Figure 15-183 and Figure 15-184.
Figure 15-183 Measurement Point in the Intra-BSC Handover Process

15-202 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Figure 15-184 Measurement Point in the Inter-BSC Handover Process

Unit
Times

15.218 C901090265 Number of Inner BSC Direct Retry Success

Description
This counter counts the number of times that a directed retry, which is decided by the BSC, is successfully completed in the source cell during TCH assignment.

Usage
This counter indicates the number of successful intra-BSC directed retries.

Measurement Point
This counter is incremented each time the BSC, after starting an intra-BSC directed retry, receives a handover complete message from the MS.

Unit
Times

15.219 C901090266 Number of Inter BSC Direct Retry Success

Description
This counter counts the number of times that a directed retry, which is decided by the BSC, is successfully completed in the source cell during TCH assignment.
15-203 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter indicates the number of successful inter-BSC directed retries.

Measurement Point
This counter is incremented each time the BSC, after starting an inter-BSC directed retry, receives a handover complete message from the MS.

Unit
Times

15.220 C901090267 Number of Intra-Cell Handover Failure Lead to Return

Description
This counter counts the number of times that an MS returns to the original channel due to handover failure during an intra-cell handover.

Usage
This counter indicates the number of times that an MS returns to the original channel due to intra-cell handover failure.

Measurement Point
This counter is incremented each time the BSC, after sending an assignment command during intra-cell handover, receives an assignment failure message.

Unit
Times

15.221 C901090268 User/MSC Release Number During BSC-Controlled Inter-Cell Outgoing Handover
Description
This counter counts the number of times that an MS or the core network initiates a channel release during an inter-cell handover controlled by the BSC.

Usage
This counter indicates the number of times that an MS or the core network initiates a channel release during an inter-cell handover controlled by the BSC.
15-204 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 15 General Handover Measurement

Measurement Point
This counter is incremented each time the BSC, after sending a handover command during inter-cell handover, does not receive a handover complete message but only receives a clear command with the cause of call control.

Unit
Times

15.222 C901090269 User/MSC Release Number During MSC-Controlled Inter-Cell Outgoing Handover
Description
This counter counts the number of times that an MS or the core network initiates a channel release during an inter-cell handover controlled by the MSC.

Usage
This counter indicates the number of times that an MS or the core network initiates a channel release during an inter-cell handover controlled by the MSC.

Measurement Point
This counter is incremented each time the BSC receives a clear command with the cause of call control during an inter-cell outgoing handover.

Unit
Times

15-205 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

15-206 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16

Adjacent Cell Handover Measurement

Table of Contents
Overview ..................................................................................................................16-3 C901100001 Number of handover attempts on the adjacent cell. .............................16-3 C901100002 Number of handover success from selected cell to the adjacent cell. ...16-4 C901100003 Number of handover attempts from adjacent cell to the selected cell. ..16-5 C901100004 Number of handover success from adjacent cell to the selected cell. ...16-7 C901100005 Number of handover attempts from selected cell to the adjacent cell due to better UL quality.............................................................................................16-8 C901100006 Number of handover attempts from selected cell to the adjacent cell due to better DL quality.............................................................................................16-9 C901100007 Number of handover success from selected cell to the adjacent cell due to better UL quality........................................................................................... 16-11 C901100008 Number of handover success from selected cell to the adjacent cell due to better DL quality...........................................................................................16-12 C901100009 Number of handover attempts from selected cell to the adjacent cell due to better UL strength........................................................................................16-13 C901100010 Number of handover attempts from selected cell to the adjacent cell due to better DL strength........................................................................................16-15 C901100011 Number of handover success from selected cell to the adjacent cell due to better UL strength........................................................................................16-16 C901100012 Number of handover success from selected cell to the adjacent cell due to better DL strength........................................................................................16-17 C901100013 Number of handover attempts from selected cell to the adjacent cell due to PBGT ..........................................................................................................16-19 C901100014 Number of handover success from selected cell to the adjacent cell due to PBGT ..........................................................................................................16-20 C901100015 Number of handover attempts from selected cell to the adjacent cell due to other factors. ...............................................................................................16-21 C901100016 Number of successful handover from selected cell to the adjacent cell due to other factors. ...............................................................................................16-23 C901100017 Number of pingpong handover (handover to source cell) ...................16-24 C901100018 The max of RTD ................................................................................16-25 C901100019 The sum of RTD ................................................................................16-26 C901100021 Number of Receive Downlink Level of This Adjacent Cell ..................16-27 C901100022 Sum of Receive Downlink Level of This Adjacent Cell .......................16-27
16-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901100023 Number of Update History Record of This Adjacent Cell ....................16-28 C901100024 Sum of Downlink Level to Update History Record of This Adjacent Cell ........................................................................................................................16-28 C901100025 Sum of Used History Record Downlink Level of This Adjacent Cell....16-28 C901100020 The number of RTD ...........................................................................16-28 C901100026 Number of handover attempts from selected cell to the adjacent cell due to DL quality rapid drop....................................................................................16-29 C901100027 Number of handover success from selected cell to the adjacent cell due to DL quality rapid drop....................................................................................16-30 C901100028 Number of Handover From Selected Cell to the Adjacent Cell ...........16-31 C901100029 Number of Handover From the Adjacent Cell to Selected Cell ...........16-32 C901100030 Number of Handover From Selected Cell to the Adjacent Cell Due to UL Quality ..............................................................................................................16-33 C901100031 Number of Handover From Selected Cell to the Adjacent Cell Due to DL Quality ..............................................................................................................16-34 C901100032 Number of Handover From Selected Cell to the Adjacent Cell Due to UL Strength............................................................................................................16-35 C901100033 Number of Handover From Selected Cell to the Adjacent Cell Due to DL Strength............................................................................................................16-35 C901100034 Number of Handover From Selected Cell to the Adjacent Cell Due to PBGT .....................................................................................................................16-36 C901100035 Number of Handover From Selected Cell to the Adjacent Cell Due to DL Quality Rapid Drop ...........................................................................................16-36 C901100036 Number of Handover From Selected Cell to the Adjacent Cell Due to Other Reason.........................................................................................................16-37 C901100037 Number of Handover Attempts From Selected Cell to the Adjacent Cell Due to Traffic...................................................................................................16-37 C901100038 Number of Handover From Selected Cell to the Adjacent Cell Due to Traffic .....................................................................................................................16-38 C901100039 Number of successful handovers from selected cell to the adjacent cell due to Traffic ....................................................................................................16-38 C901100043 Number of few MS MR received before connection failure after handover from adjacent 3G cell ..............................................................................16-39 C901100044 Number of Handover Failure to the Adjacent Cell Lead to Return ......16-39 C901100045 Number of Attempts in Target Cell for Directed Retry.........................16-40 C901100046 Number of Perform in Target Cell for Directed Retry ..........................16-40 C901100047 Number of Success in Target Cell for Directed Retry .........................16-41 C901100048 Number of SDCCH Drops Due to Handover Failure to This Cell ........16-41 C901100049 Number of Speech TCH Drops Due to Handover Failure to This Cell .16-42 C901100050 Number of Data TCH Drops Due to Handover Failure to This Cell .....16-42 C901100051 Number of Signal TCH Drops Due to Handover Failure to This Cell...16-43

16-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

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. The measurement takes cell as the statistics unit.

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 point is A, as shown in Figure 16-1.
Figure 16-1 BSC-Controlled Inter-Cell Outgoing Handover Attempt

16-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

When external handover happens inside one MSC, and source cell sends handover request message to MSC, the counter increments. The measurement point is A, as shown in Figure 16-2.
Figure 16-2 MSC-Controlled Outgoing Handover Attempts

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

16.3 C901100002 Number of handover success from selected cell to the adjacent cell.
Definition
This counter counts the number of success of handover from the selected cell to the adjacent cell.

Usage
This counter is used to find out the number of success of handover from the selected cell to the adjacent cell so as to know the handover situation.

Measurement Point
l When handover happens between cells inside one BSC, and source cell receives handover completion message from target cell, the counter increments. The measurement point is A, as shown in Figure 16-3.

16-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Figure 16-3 Successful BSC-Controlled Inter-Cell Outgoing Handover

When external handover happens inside one MSC, source cell receives release command from MSC and the release is due to handover success, the counter increments. The measurement point is A, as shown in Figure 16-4.
Figure 16-4 Successful MSC-Controlled Outgoing Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

16.4 C901100003 Number of handover attempts from adjacent cell to the selected cell.
Definition
Number of handover attempts from adjacent cell to the selected cell.

16-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A, as shown in Figure 16-5.
Figure 16-5 BSC-Controlled Inter-Cell Incoming Handover Attempts

When external handover happens inside one MSC, and target cell receives handover request message from MSC, the counter increments. The measurement point is A, as shown in Figure 16-6.
Figure 16-6 MSC-Controlled Incoming Handover Attempts

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover
16-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

16.5 C901100004 Number of handover success from 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 point is A, as shown in Figure 16-7.
Figure 16-7 Successful BSC-Controlled Inter-Cell Incoming Handover

When external handover happens inside one MSC, and target cell receives handover completion message from MS, the counter increments. The measurement point is A, as shown in Figure 16-8.
Figure 16-8 MSC-Controlled Incoming Handover Success

Unit
Times
16-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGB-02-02-001 Basic Handover

16.6 C901100005 Number of handover attempts from 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
l When handover happens between cells inside one BSC, and target cell receives radio channel request message from source cell due to better UL quality, the counter increments. The measurement point is A, as shown inFigure 16-9.
Figure 16-9 BSC-Controlled Inter-Cell Incoming Handover Attempts

When external handover happens inside one MSC, target cell receives handover request message from MSC due to better UL quality, the counter increments. The measurement point is A, as shown in Figure 16-10.

16-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Figure 16-10 MSC-Controlled Incoming Handover Attempts

Unit
Times

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

16.7 C901100006 Number of handover attempts from 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
l When handover happens between cells inside one BSC, and target cell receives radio channel request message from source cell due to better DL quality, the counter increments. The measurement point is A, as shown in Figure 16-11.

16-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 16-11 BSC-Controlled Inter-Cell Incoming Handover Attempts

When external handover happens inside one MSC, and target cell receives handover request message from MSC due to better DL quality, the counter increments. The measurement point is A, as shown in Figure 16-12.
Figure 16-12 MSC-Controlled Incoming Handover Attempts

Unit
Times

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

16-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

16.8 C901100007 Number of handover success from selected cell to the adjacent cell due to better UL 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
l When handover happens between cells inside one BSC, and source cell receives handover completion message from target cell due to better UL quality, the counter increments. The measurement point is A, as shown in Figure 16-13.
Figure 16-13 Successful BSC-Controlled Inter-Cell Outgoing Handover

When external handover happens inside one MSC, and source cell receives release command from MSC due to better UL quality, the counter increments. The measurement point is A, as shown in Figure 16-14.

16-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 16-14 Successful MSC-Controlled Outgoing Handover

Unit
Times

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

16.9 C901100008 Number of handover success from selected cell to the adjacent cell due to better DL quality.
Definition
Number of handover success from selected cell to the adjacent cell due to better DL 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 DL quality 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 due to better DL quality, the counter increments. The measurement point is A, as shown in Figure 16-15.

16-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Figure 16-15 Successful BSC-Controlled Inter-Cell Outgoing Handover

When external handover happens inside one MSC, source cell receives release command from MSC due to better DL quality, the counter increments. The measurement point is A, as shown in Figure 16-16.
Figure 16-16 Successful MSC-Controlled Outgoing Handover

Unit
Times

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

16.10 C901100009 Number of handover attempts from selected cell to the adjacent cell due to better UL strength.
Definition
Number of handover attempts from selected cell to the adjacent cell due to better UL strength.
16-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of attempts of handover from a selected cell to the adjacent cell due to better UL strength so as to know the handover situation.

Measurement Point
l When handover happens between cells inside one BSC, and target cell receives radio channel request message from source cell due to better UL strength, the counter increments. The measurement point is A, as shown in Figure 16-17.
Figure 16-17 BSC-Controlled Inter-Cell Incoming Handover Attempts

When external handover happens inside one MSC, and target cell receives handover request message from MSC due to better UL strength, the counter increments. The measurement point is A, as shown in Figure 16-18
Figure 16-18 MSC-Controlled Incoming Handover Attempts

Unit
Times

Related Features
ZGB-02-02-002 Basic Handover Decision Criteria
16-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

16.11 C901100010 Number of handover attempts from selected cell to the adjacent cell due to better DL strength.
Definition
Number of handover attempts from selected cell to the adjacent cell due to better DL strength.

Usage
This counter is used to find out the number of attempts of handover from a selected cell to the adjacent cell due to better DL strength so as to know the handover situation.

Measurement Point
l When handover happens between cells inside one BSC, and target cell receives radio channel request message from source cell due to better DL strength, the counter increments. The measurement point is A, as shown in Figure 16-19.
Figure 16-19 BSC-Controlled Inter-Cell Incoming Handover Attempts

When external handover happens inside one MSC, and target cell receives handover request message from MSC due to better DL strength, the counter increments. The measurement point is A, as shown in Figure 16-20.

16-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 16-20 MSC-Controlled Incoming Handover Attempts

Unit
Times

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

16.12 C901100011 Number of handover success from selected cell to the adjacent cell due to better UL strength.
Definition
Number of successful handover from selected cell to the adjacent cell due to better UL strength

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 strength 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 due to better UL strength, the counter increments. The measurement point is A, as shown in Figure 16-21.

16-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Figure 16-21 Successful BSC-Controlled Inter-Cell Outgoing Handover

When external handover happens inside one MSC, and source cell receives release command from MSC due to better UL strength, the counter increments. The measurement point is A, as shown in Figure 16-22.
Figure 16-22 Successful MSC-Controlled Outgoing Handover

Unit
Times

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

16.13 C901100012 Number of handover success from selected cell to the adjacent cell due to better DL strength.
Definition
Number of successful handover from the selected cell to the adjacent cell due to better DL strength
16-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of successful handover from a selected cell to the adjacent cell due to better DL strength 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 due to better DL strength, the counter increments. The measurement point is A, as shown in Figure 16-23.
Figure 16-23 Successful BSC-Controlled Inter-Cell Outgoing Handover

When external handover happens inside one MSC, and source cell receives release command from MSC due to better UL strength, the counter increments, as shown in Figure 16-24.
Figure 16-24 Successful MSC-Controlled Outgoing Handover

Unit
Times

Related Features
ZGB-02-02-002 Basic Handover Decision Criteria
16-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

16.14 C901100013 Number of handover attempts from 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
This counter is used to find out the number of attempts of handover from a selected cell to the adjacent cell due to PBGT, so as to know the handover situation.

Measurement Point
l When handover happens between cells inside one BSC, and target cell receives radio channel request message from source cell due to better PBGT, the counter increments. The measurement point is A, as shown inFigure 16-25.
Figure 16-25 BSC-Controlled Inter-Cell Incoming Handover Attempts

When external handover happens inside one MSC, and target cell receives handover request message from MSC due to better PBGT, the counter increments. The measurement point is A, as shown in Figure 16-26.

16-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 16-26 MSC-Controlled Incoming Handover Attempts

Unit
Times

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

16.15 C901100014 Number of handover success from selected cell to the adjacent cell due to PBGT
Definition
Number of handover success from selected cell to the adjacent cell due to better PBGT

Usage
This counter is used to find out the number of handover success from a selected cell to the adjacent cell due to better PBGT, so as 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 due to better PBGT, the counter increments. The measurement point is A, as shown in Figure 16-27.

16-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Figure 16-27 Successful BSC-Controlled Inter-Cell Outgoing Handover

When external handover happens inside one MSC, and source cell receives release command from MSC due to better PBGT, the counter increments. The measurement point is A, as shown in Figure 16-28.
Figure 16-28 Successful MSC-Controlled Outgoing Handover

Unit
Times

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

16.16 C901100015 Number of handover attempts from 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.
16-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of attempts of handover from a selected cell to the adjacent cell due to other factors, so as to know the handover situation.

Measurement Point
l When handover happens between cells inside one BSC, and target cell receives radio channel request message from source cell due to other factors, the counter increments, as shown in Figure 16-29.
Figure 16-29 BSC-Controlled Inter-Cell Incoming Handover Attempts

When external handover happens inside one MSC, and target cell receives handover request message from MSC due to other factors, the counter increments, as shown in Figure 16-30.
Figure 16-30 MSC-Controlled Incoming Handover Attempts

Unit
Times

16-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

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

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
l When handover happens between cells inside one BSC, and source cell receives handover completion message from target cell due to other factors, the counter increments, as shown in Figure 16-31.
Figure 16-31 Successful BSC-Controlled Inter-Cell Outgoing Handover

When external handover happens inside one MSC, and source cell receives release command from MSC due to other factors, the counter increments, as shown in Figure 16-32.

16-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 16-32 Successful MSC-Controlled Outgoing Handover

Unit
Times

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 point is A, as shown in Figure 16-33.

16-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Figure 16-33 BSC-Controlled Inter-Cell Outgoing Handover Attempt

For MSC-controlled external handover, the counter increments when the souce cell sends the handover request message to MSC. The measurement point is A, as shown in Figure 16-34.
Figure 16-34 MSC-Controlled Outgoing Handover Attempts

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.
16-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter is supported in version V6.20.210a or above.

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.
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. This counter is supported in version V6.20.210a or above.
16-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Measurement Point
When BSC receives the Assign Complete message from MS, if it contains the mobile time difference, then the counter counts.

Unit
Times

16.21 C901100021 Number of Receive Downlink Level of This Adjacent Cell

Description
This counter counts the number of times that the Mobile Station (MS) receives a downlink level of the adjacent cell.

Usage
This counter reflects the rate that the local cell detects the adjacent cell.

Measurement Point
This counter is incremented each time the BSC detects a measured level of the adjacent cell in the measurement report received from the BTS.

Unit
Times

16.22 C901100022 Sum of Receive Downlink Level of This Adjacent Cell

Description
This counter calculates the sum of the adjacent cell's downlink level that is received by the MS.

Usage
This counter reflects the adjacent cell's level intensity that is measured by the local cell.

Measurement Point
This counter is updated each time the BSC detects a measured level of the adjacent cell in the measurement report received from the BTS.

16-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
None

16.23 C901100023 Number of Update History Record of This Adjacent Cell

Description
This counter is not used in this version.

16.24 C901100024 Sum of Downlink Level to Update History Record of This Adjacent Cell
Description
This counter is not used in this version.

16.25 C901100025 Sum of Used History Record Downlink Level of This Adjacent Cell
Description
This counter is not used in this version.

16.26 C901100020 The number of RTD

Description
This counter counts the number of sampled reference time differences between two cells. When BSC receives the Assign Complete message from MS, if it contains the mobile time difference, then the counter increments.

Usage
This counter is used to find out the number of sampled reference time differences between two cells. This counter is supported in version V6.20.210a or above.

Measurement Point
When BSC receives the Assign Complete message from MS, if it contains the mobile time difference, then the counter counts.
16-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Unit
Times

16.27 C901100026 Number of handover attempts from selected cell to the adjacent cell due to DL quality rapid drop
Description
This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to fast fading of downlink quality. This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell. It helps check the direction of handover between cells. 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 point is A, as shown in Figure 16-36. For MSC-controlled external handover, the counter increments when the source cell sends the handover request message to MSC. The measurement point is A, as shown in Figure 16-37.

Figure 16-36 BSC-Controlled Inter-Cell Outgoing Handover Attempt

16-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 16-37 MSC-Controlled Inter-Cell Outgoing Handover Attempt

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

16.28 C901100027 Number of handover success from selected cell to the adjacent cell due to DL quality rapid drop
Description
This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to fast fading of downlink quality. This counter is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell. It helps check the direction of handover between cells. l For BSC-controlled inter-cell handover, the counter increments when the source cell receives the handover completion message from the destination cell. The measurement point is A, as shown in Figure 16-38. For MSC-controlled external handover, when the source cell receives the release command issued by MSC and if the release is due to handover success, then the counter increments. The measurement point is A, as shown in Figure 16-39.

16-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Figure 16-38 Number of BSC-Controlled Outgoing Handover Successes

Figure 16-39 Number of MSC-Controlled Outgoing Handover Successes

This counter is supported in version V6.20.614b.

Unit
Times

Statistics Object
Cell

16.29 C901100028 Number of Handover From Selected Cell to the Adjacent Cell
Description
The handover from the selected cell to the adjacent cell can be classified into the handover process controlled by the BSC and the handover process controlled by the MSC, as described in the following section. In the case of intra-BSC cell handover, when the source cell is going to send the handover command to the MS after the destination cell requests a channel and activates the channel successfully, the counter increases by 1. In the case of inter-BSC handover, the source BSC sends the handover request message A_HO_RQD to the MSC to trigger the inter-BSC cell handover. When the source BSC receives a handover command replied by the MSC and is going to send the command to the MS, the counter increases by 1.

Usage
None
16-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The measurement point for intra-BSC cell handover is shown in Figure 16-40.
Figure 16-40 BSC-Controlled Cell Handover

The measurement point for inter-BSC cell handover is shown in Figure 16-41.
Figure 16-41 MSC-Controlled Cell Handover

Unit
Time

16.30 C901100029 Number of Handover From the Adjacent Cell to Selected Cell
Description
During the process of cell handover, this counter increases by 1 when the destination cell requests a channel and activates the channel successfully. In the case of intra-BSC cell handover, when the source cell is going to send the handover command to the MS after the destination cell requests a channel and activates the channel successfully, the counter increases by 1. In the case of inter-BSC handover, the source BSC sends the handover request message A_HO_RQD to the MSC to trigger the inter-BSC cell handover. When the source BSC receives a handover command replied by the MSC and is going to send the command to the MS, the counter increases by 1.
16-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Usage
None

Measurement Point
The measurement point for intra-BSC cell handover is shown in Figure 16-42.
Figure 16-42 BSC-Controlled Cell Handover

The measurement point for MSC-controlled cell handover is shown in Figure 16-43.
Figure 16-43 MSC-Controlled Cell Handover

Unit
Time

16.31 C901100030 Number of Handover From Selected Cell to the Adjacent Cell Due to UL Quality
Description
During the process of cell handover, this counter increases by 1 when the destination cell requests a channel and activates the channel successfully. In the case of MSC-controlled cell handover, this counter increases by 1 when the destination cell requests a channel and activates the channel successfully after receiving the handover request delivered by the MSC.

16-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
The measurement point for intra-BSC cell handover is shown in Figure 16-44.
Figure 16-44 BSC-Controlled Cell Handover

The measurement point for MSC-controlled cell handover is shown in Figure 16-45.
Figure 16-45 MSC-Controlled Cell Handover

Unit
Time

16.32 C901100031 Number of Handover From Selected Cell to the Adjacent Cell Due to DL Quality
Description
This counter increases by 1 when the source cell is going to send the handover command to the MS to initiate the intra-BSC/inter-BSC cell handover process due to the DL quality.

Usage
None

16-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Measurement Point
The measurement point for intra-BSC cell handover is as A1 shown in BSC-Controlled Cell Handover. The measurement point for inter-BSC cell handover is as A2 shown in MSC-Controlled Cell Handover.

Unit
Time

16.33 C901100032 Number of Handover From Selected Cell to the Adjacent Cell Due to UL Strength
Description
This counter increases by 1 when the source cell is going to send the handover command to the MS to initiate the intra-BSC/inter-BSC cell handover process due to the UL strength.

Usage
None

Measurement Point
The measurement point of the intra-BSC cell handover process is as A1 shown in BSC-Controlled Cell Handover. The measurement point of the inter-BSC cell handover process is as A2 shown in MSC-Controlled Cell Handover.

Unit
Time

16.34 C901100033 Number of Handover From Selected Cell to the Adjacent Cell Due to DL Strength
Description
This counter increases by 1 when the source cell is going to send the handover command to the MS to initiate the intra-BSC/inter-BSC cell handover process due to the DL strength.

Usage
None
16-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The measurement point of the intra-BSC cell handover process is as A1 shown in BSC-Controlled Cell Handover. The measurement point of the inter-BSC cell handover process is as A2 shown in MSC-Controlled Cell Handover.

Unit
Time

16.35 C901100034 Number of Handover From Selected Cell to the Adjacent Cell Due to PBGT
Description
This counter increases by 1 when the source cell is going to send the handover command to the MS to initiate the intra-BSC/inter-BSC cell handover process due to PBGT.

Usage
None

Measurement Point
The measurement point of the intra-BSC cell handover process is as A1 shown in BSC-Controlled Cell Handover. The measurement point of the inter-BSC cell handover process is as A2 shown in MSC-Controlled Cell Handover.

Unit
Time

16.36 C901100035 Number of Handover From Selected Cell to the Adjacent Cell Due to DL Quality Rapid Drop
Description
This counter increases by 1 when the source cell is going to send the handover command to the MS to initiate the intra-BSC/inter-BSC cell handover process due to the DL quality rapid drop.

16-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Usage
None

Measurement Point
The measurement point of the intra-BSC cell handover process is as A1 shown in BSC-Controlled Cell Handover. The measurement point of the inter-BSC cell handover process is as A2 shown in MSC-Controlled Cell Handover.

Unit
Time

16.37 C901100036 Number of Handover From Selected Cell to the Adjacent Cell Due to Other Reason
Description
This counter increases by 1 when the source cell is going to send the handover command to the MS to initiate the intra-BSC/inter-BSC cell handover process due to other reasons.

Usage
None

Measurement Point
The measurement point of the intra-BSC cell handover process is as A1 shown in BSC-Controlled Cell Handover. The measurement point of the inter-BSC cell handover process is as A2 shown in MSC-Controlled Cell Handover.

Unit
Time

16.38 C901100037 Number of Handover Attempts From Selected Cell to the Adjacent Cell Due to Traffic
Description
This counter counts the number of handover attempts from selected cell to the adjacent cell due to the traffic.
16-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Time

16.39 C901100038 Number of Handover From Selected Cell to the Adjacent Cell Due to Traffic
Description
This counter counts the number of handover process from selected cell to the adjacent cell due to the traffic.

Usage
None

Measurement Point
None

Unit
Time

16.40 C901100039 Number of successful handovers from selected cell to the adjacent cell due to Traffic
Description
This counter counts the number of successful handover from selected cell to the adjacent cell due to the traffic.

Usage
None

Measurement Point
None
16-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Unit
Time

16.41 C901100043 Number of few MS MR received before connection failure after handover from adjacent 3G cell
Measured Object
Cell

Description
This counter is incremented each time a connection failure occurs after the MS is handed over from the adjacent 3G cell to the local cell, and the number of measurement reports, which are received from the MS during the period from the handover completion and the connection failure, is less than the number specified by the system parameter "MrCountForRlt".

Usage
None

Measurement Point
None

Unit
Times

16.42 C901100044 Number of Handover Failure to the Adjacent Cell Lead to Return
Description
This counter counts the number of times that an MS returns to the original channel due to handover failure to the adjacent cell.

Usage
This counter indicates the number of times that an MS returns to the original channel due to handover failure to the adjacent cell.

16-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the BSC, after sending a handover command for handover to the adjacent cell, receives a handover failure message.

Unit
Times

16.43 C901100045 Number of Attempts in Target Cell for Directed Retry

Description
This counter counts the number of times that an MS attempts a directed retry to a target cell. During a directed retry, the MS will be handed over from the original cell to the target cell. This counter indicates the number of times that the MS attempts a handover to the target cell.

Usage
This counter indicates the number of directed retry attempts to a target cell.

Measurement Point
This counter is incremented each time a channel request with the cause of directed retry is successful in the target cell.

Unit
Times

16.44 C901100046 Number of Perform in Target Cell for Directed Retry

Description
This counter counts the number of times that a directed retry is performed in a cell. During a directed retry, the MS will be handed over from the original cell to the target cell. This counter indicates the number of times that a handover to the target cell is performed.

Usage
This counter indicates the number of performed directed retries to a target cell.

16-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Measurement Point
This counter is incremented each time the target cell receives a channel activation acknowledgement with the cause of directed retry.

Unit
Times

16.45 C901100047 Number of Success in Target Cell for Directed Retry

Description
This counter counts the number of times that a directed retry to a cell is successful. During a directed retry, the MS will be handed over from the original cell to the target cell. This counter indicates the number of times that a handover to the target cell is successful.

Usage
This counter indicates the number of successful directed retries to a target cell.

Measurement Point
This counter is incremented each time the target cell receives a handover complete message with the cause of directed retry.

Unit
Times

16.46 C901100048 Number of SDCCH Drops Due to Handover Failure to This Cell
Description
This counter counts SDCCH call drops caused by handover failure to the adjacent cell.

Usage
This counter indicates the number of SDCCH call drops caused by handover failure to the adjacent cell.

16-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Points
l Upon starting an inter-cell handover procedure on an SDCCH, the BSC sends a handover command and starts the corresponding timer. This counter is incremented each time the timer expires before a handover complete message is received. Upon starting an inter-cell handover procedure on an SDCCH, the BSC sends a handover command and starts the corresponding timer. This counter is incremented each time the timer expires before a clear command with the cause of Handover Success is received.

Unit
Times

16.47 C901100049 Number of Speech TCH Drops Due to Handover Failure to This Cell
Description
This counter counts voice TCH call drops caused by handover failure to the adjacent cell.

Usage
This counter indicates the number of voice TCH call drops caused by handover failure to the adjacent cell.

Measurement Points
l Upon starting an inter-cell handover procedure on a voice TCH, the BSC sends a handover command and starts the corresponding timer. This counter is incremented each time the timer expires before a handover complete message is received. Upon starting an inter-cell handover procedure on a voice TCH, the BSC sends a handover command and starts the corresponding timer. This counter is incremented each time the timer expires before a clear command with the cause of Handover Success is received.

Unit
Times

16.48 C901100050 Number of Data TCH Drops Due to Handover Failure to This Cell
Description
This counter counts data TCH call drops caused by handover failure to the adjacent cell.
16-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 16 Adjacent Cell Handover Measurement

Usage
This counter indicates the number of data TCH call drops caused by handover failure to the adjacent cell.

Measurement Points
l Upon starting an inter-cell handover procedure on a data TCH, the BSC sends a handover command and starts the corresponding timer. This counter is incremented each time the timer expires before a handover complete message is received. Upon starting an inter-cell handover procedure on a data TCH, the BSC sends a handover command and starts the corresponding timer. This counter is incremented each time the timer expires before a clear command with the cause of Handover Success is received.

Unit
Times

16.49 C901100051 Number of Signal TCH Drops Due to Handover Failure to This Cell
Description
This counter counts signaling TCH call drops caused by handover failure to the adjacent cell.

Usage
This counter indicates the number of signaling TCH call drops caused by handover failure to the adjacent cell.

Measurement Points
l Upon starting an inter-cell handover procedure on a signaling TCH, the BSC sends a handover command and starts the corresponding timer. This counter is incremented each time the timer expires before a handover complete message is received. Upon starting an inter-cell handover procedure on a signaling TCH, the BSC sends a handover command and starts the corresponding timer. This counter is incremented each time the timer expires before a clear command with the cause of Handover Success is received.

Unit
Times

16-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

16-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17

Radio Access Measurement

Table of Contents
Overview ..................................................................................................................17-3 C901110001 Number of invalid access requests.......................................................17-4 C901110003 Number of MOC access success for processes ...................................17-5 C901110006 Number of MTC access success for processes....................................17-5 C901110008 Number of call re-establishment access attempts ................................17-6 C901110009 Number of call re-establishment access success for processes ...........17-6 C901110010 Number of call re-establishment access success .................................17-7 C901110011 Number of emergency calls access attempts .......................................17-8 C901110012 Number of emergency calls access success for processes ..................17-8 C901110013 Number of emergency calls access success ........................................17-9 C901110014 Number of LOC access attempts .......................................................17-10 C901110015 Number of LOC access success for processes ..................................17-10 C901110016 Number of LOC access success ........................................................ 17-11 C901110017 Number of other causes access attempts .......................................... 17-11 C901110018 Number of successful random access processes for other causes.....17-12 C901110019 Number of other causes access success ...........................................17-12 C901110020 Number of LMU Establishment Access attempts................................17-13 C901110021 Number of LMU Establishment access success for processes ...........17-14 C901110022 Number of LMU Establishment access success .................................17-14 C901110023 Number of accesses due to location update.......................................17-15 C901110024 Number of Access due to CM SERVICE REQ ...................................17-15 C901110026 Number of CM service requests of Emergency Call ...........................17-16 C901110027 Number of CM service requests of SMS ............................................17-17 C901110028 Number of CM service requests of Supplement .................................17-17 C901110029 Number of CM service requests of LCS .............................................17-18 C901110031 Number of wireless access due to call re-establishments...................17-18 C901110032 Number of wireless accesses due to IMSI detachment ......................17-19 C901110033 Number of wireless accesses due to other causes.............................17-19 C901110034 Number of access due to Notification response .................................17-20 C901110035 Number of access due to Immediate setup ........................................17-21 C901110036 Number of access due to Talker indication .........................................17-22 C901110037 Number of access due to DATA Indication .........................................17-23 C901110038 Number of access due to priority uplink request .................................17-24 C901110039 Number of access of CM service request of VGCS ............................17-25 C901110040 Number of access of CM service request of VBS ...............................17-26 C901110041 Number of CS Precise Paging ...........................................................17-27 C901110042 Number of CS Precise Paging Response...........................................17-28
17-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901110043 Number of CS First Paging ................................................................17-28 C901110044 Number of CS First Paging Response ...............................................17-28 C901110045 Number of CS Second Paging ...........................................................17-29 C901110046 Number of CS Second Paging Response ..........................................17-29 C901110047 Number of CS Third Paging ...............................................................17-30 C901110048 Number of CS Third Paging Response ..............................................17-30 C901110049 Number of PS Precise Paging............................................................17-30 C901110050 Number of PS Precise Paging Response...........................................17-31 C901110051 Number of PS First Paging ................................................................17-31 C901110052 Number of PS First Paging Response................................................17-32 C901110053 Number of PS Second Paging ...........................................................17-32 C901110054 Number of PS Second Paging Response...........................................17-32 C901110055 Number of PS Third Paging ...............................................................17-33 C901110056 Number of PS Third Paging Response ..............................................17-33 C901110057 Number of CS Precise Paging for Last Service in This Cell................17-34 C901110058 Number of CS Precise Paging No Response for Last Service in This Cell ........................................................................................................................17-34 C901110059 Number of CS First Paging for Last Service in This Cell.....................17-35 C901110060 Number of CS First Paging No Response for Last Service in This Cell ........................................................................................................................17-35 C901110061 Number of CS Second Paging for Last Service in This Cell................17-36 C901110062 Number of CS Second Paging No Response for Last Service in This Cell ........................................................................................................................17-36 C901110063 Number of CS Third Paging for Last Service in This Cell ...................17-37 C901110064 Number of CS Third Paging No Response for Last Service in This Cell ........................................................................................................................17-37 C901110065 Number of PS Precise Paging for Last Service in This Cell ................17-38 C901110066 Number of PS Precise Paging No Response for Last Service in This Cell ........................................................................................................................17-38 C901110067 Number of PS First Paging for Last Service in This Cell.....................17-39 C901110068 Number of PS First Paging No Response for Last Service in This Cell ........................................................................................................................17-39 C901110069 Number of PS Second Paging for Last Service in This Cell................17-40 C901110070 Number of PS Second Paging No Response for Last Service in This Cell ........................................................................................................................17-40 C901110071 Number of PS Third Paging for Last Service in This Cell....................17-41 C901110072 Number of PS Third Paging No Response for Last Service in This Cell ........................................................................................................................17-41 C901110073 Number of CS Precise Paging (Paging Hole Search) .........................17-42 C901110074 Number of CS Precise Paging No Response (Paging Hole Search)...17-42 C901110075 Number of CS First Paging (Paging Hole Search)..............................17-43 C901110076 Number of CS First Paging No Response (Paging Hole Search)........17-43 C901110077 Number of CS Second Paging (Paging Hole Search).........................17-44 C901110078 Number of CS Second Paging No Response (Paging Hole Search)...17-44 C901110079 Number of CS Third Paging (Paging Hole Search).............................17-45
17-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

C901110080 Number of CS Third Paging No Response (Paging Hole Search) ......17-45 C901110081 Number of PS Precise Paging (Paging Hole Search) .........................17-46 C901110082 Number of PS Precise Paging No Response (Paging Hole Search) ...17-46 C901110083 Number of PS First Paging (Paging Hole Search) ..............................17-47 C901110084 Number of PS First Paging No Response (Paging Hole Search)........17-47 C901110085 Number of PS Second Paging (Paging Hole Search) .........................17-48 C901110086 Number of PS Second Paging No Response (Paging Hole Search)...17-48 C901110087 Number of PS Third Paging (Paging Hole Search).............................17-49 C901110088 Number of PS Third Paging No Response (Paging Hole Search).......17-49

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. 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. The measurement takes cell as the statistics unit. Radio access flow and related counters locations are shown in Figure 17-1.

17-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.

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-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

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

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.
17-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.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.6 C901110009 Number of call re-establishment 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
17-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

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
The counter increments when channel is activated successfully. The measurement point is A3, as shown in Figure Radio Access Process.

Unit
Times

17.7 C901110010 Number of call re-establishment 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.

Measurement Point
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

Unit
Times

17-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 increments when MS sends CHL_REQ message through BTS to BSC for requiring radio channel, if TA does not exceed cell scope and the access cause is emergency calls.

Usage
This counter is used to find out the frequency of random access attempts due to emergency calls.

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

Related Features
ZGB-01-03-001 Emergency Call Handling

17.9 C901110012 Number of emergency calls access success for processes

Definition
Number of emergency calls access success for processes

Description
This counter counts the Number of emergency calls access success for processes. The counter increments when BSC allows MS to be accessed into the network due to emergency calls and accepts channel request sent by MS and allocates and activates channel successfully. Meanwhile, BSC sends IMM_ASS message to MS.

17-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

Usage
This counter is used to find out the frequency of random access processes due to emergency calls.

Measurement Point
The counter increments when channel is activated successfully. The measurement point is A3, as shown in Figure Radio Access Process.

Unit
Times

Related Features
ZGB-01-03-001 Emergency Call Handling

17.10 C901110013 Number of emergency calls access 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
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

Unit
Times

Related Features
ZGB-01-03-001 Emergency Call Handling

17-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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.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. The counter increments when BSC allows MS to be accessed into the network due to emergency calls and accepts channel request sent by MS and allocates and activates channel successfully. Meanwhile, BSC sends IMM_ASS message to MS.

Usage
This counter is used to find out the frequency of random access processes due to LOC.

Measurement Point
The counter increments when channel is activated successfully. The measurement point is A3, as shown in Figure Radio Access Process.
17-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

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
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

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.

Usage
This counter is used to find out the frequency of random access attempts due to other causes.
17-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.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. The counter increments when BSC allows MS to be accessed into the network due to other causes and accepts channel request sent by MS and allocates and activates channel successfully. Meanwhile, BSC sends IMM_ASS message to MS.

Usage
This counter is used to find out the frequency of random access processes due to other causes.

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.16 C901110019 Number of other causes access success

Definition
Number of other causes access success

17-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

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
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

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 increments when MS sends CHL_REQ message through BTS to BSC for requiring radio channel, if TA does not exceed cell scope and the access cause is LMU establishment.

Usage
This counter is used to find out the frequency of LMU establishment access request.

Measurement Point
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-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

17.18 C901110021 Number of LMU Establishment 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
The counter increments when channel is activated successfully. The measurement point is A3, as shown in Figure Radio Access Process.

Unit
Times

17.19 C901110022 Number of LMU Establishment access success

Definition
Number of LMU Establishment access success

Description
This counter counts the Number of LMU Establishment access success. The counter increments when MS sends CHL_REQ message through BTS to BSC for requiring radio channel, if TA does not exceed cell scope and the access cause is LMU establishment.

Usage
This counter is used to find out the frequency of LMU establishment access successfully.

17-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

Measurement Point
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

Unit
Times

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
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

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-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of access caused by CM SERVICE REQ.

Measurement Point
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

Unit
Times

17.22 C901110026 Number of CM service requests of Emergency Call

Definition
Number of access of CM SERVICE REQ's emergency call

Description
This counter counts the number of access of CM SERVICE REQ's emergency call. The counter increments when it is emergency call and the access cause in Layer3 information carried in EST_IND message received by BSC is CM SERVICE REQ.

Usage
This counter is used to find out the frequency of access of CM SERVICE REQ's emergency call.

Measurement Point
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

Unit
Times

Related Features
ZGB-01-03-001 Emergency Call Handling

17-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

17.23 C901110027 Number of CM service requests of SMS

Definition
Number of access of SMS's CM SERVICE REQ

Description
This counter counts the number of access of SMS's CM SERVICE REQ. The counter increments when it is SMS access among other accesses and the access cause in Layer3 information carried in EST_IND message received by BSC is CM SERVICE REQ.

Usage
This counter is used to find out the frequency of access of SMS's CM SERVICE REQ.

Measurement Point
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

Unit
Times

17.24 C901110028 Number of CM service requests of Supplement

Definition
Number of access of supplement's CM SERVICE REQ

Description
This counter counts the number of access of supplement's CM SERVICE REQ. The counter increments when it is supplement access among other accesses and the access cause in Layer3 information carried in EST_IND message received by BSC is CM SERVICE REQ.

Usage
This counter is used to find out the frequency of access of supplement's CM SERVICE REQ.

17-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

Unit
Times

17.25 C901110029 Number of CM service requests of LCS

Definition
Number of access of LCS's CM SERVICE REQ

Description
This counter counts the number of access of supplement's CM SERVICE REQ. The counter increments when it is LCS access among other accesses and the access cause in Layer3 information carried in EST_IND. message received by BSC is CM SERVICE REQ.

Usage
This counter is used to find out the frequency of access of LCS's CM SERVICE REQ.

Measurement Point
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

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-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

Usage
This counter is used to find out the frequency of radio channel accesses due to call re-establishments.

Measurement Point
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

Unit
Times

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
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

Unit
Times

17.28 C901110033 Number of wireless accesses due to other causes

Definition
Number of wireless accesses due to other causes
17-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process.

Unit
Times

17.29 C901110034 Number of access due to Notification response

Description
This counter counts the number of accesses due to notification response in the group call service. After BSC receives the EST_IND message, if the layer-3 information carried in this message indicates that the access is due to MS's response to notification, then the counter increments. The measurement point is A4, as shown in Figure 17-2.

17-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

Figure 17-2 Radio Access Process

This counter is supported in version V8.00.00 or later.

Unit
Times

Statistics Object
Cell

17.30 C901110035 Number of access due to Immediate setup

Description
This counter counts the number of accesses due to immediate setup in the group call service. After BSC receives the EST_IND message, if the layer-3 information carried in this message indicates that the access is due to immediate setup, then the counter increments. The measurement point is A4, as shown in Figure 17-3.

17-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 17-3 Radio Access Process

This counter is supported in version V8.00.00 or later.

Unit
Times

Statistics Object
Cell

17.31 C901110036 Number of access due to Talker indication

Description
This counter counts the number of accesses due to Talker indication in the group call service. After BSC receives the EST_IND message, if the layer-3 information carried in this message indicates that the access is due to Talker indication, then the counter increments. The measurement point is A4, as shown in Figure 17-4.

17-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

Figure 17-4 Radio Access Process

This counter is supported in version V8.00.00 or later.

Unit
Times

Statistics Object
Cell

17.32 C901110037 Number of access due to DATA Indication

Description
This counter counts the number of accesses due to DATA indication in the group call service. After BSC receives the EST_IND message, if the layer-3 information carried in this message indicates that the access is due to DATA indication, then the counter increments. The measurement point is A4, as shown in Figure 17-5.

17-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 17-5 Radio Access Process

This counter is supported in version V8.00.00 or later.

Unit
Times

Statistics Object
Cell

17.33 C901110038 Number of access due to priority uplink request

Description
This counter counts the number of accesses due to priority uplink request in the group call service. After BSC receives the EST_IND message, if the layer-3 information carried in this message indicates that the access is due to priority uplink request, then the counter increments. The measurement point is A4, as shown in Figure 17-6.

17-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

Figure 17-6 Radio Access Process

This counter is supported in version V8.00.00 or later.

Unit
Times

Statistics Object
Cell

17.34 C901110039 Number of access of CM service request of VGCS

Description
This counter counts the number of accesses of CM service request of VGCS. After BSC receives the EST_IND message, if the layer-3 information carried in this message indicates that the access is due to CM service request and the service type is VGCS, then the counter increments. The measurement point is A4, as shown in Figure 17-7.

17-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 17-7 Radio Access Process

This counter is supported in version V8.00.00 or later.

Unit
Times

Statistics Object
Cell

17.35 C901110040 Number of access of CM service request of VBS

Description
This counter counts the number of accesses of CM service request of VBS. After BSC receives the EST_IND message, if the layer-3 information carried in this message indicates that the access is due to CM service request and the service type is VBS, then the counter increments. The measurement point is A4, as shown in Figure 17-8.

17-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

Figure 17-8 Radio Access Process

This counter is supported in version V8.00.00 or later.

Unit
Times

Statistics Object
Cell

17.36 C901110041 Number of CS Precise Paging

Description
This counter counts the number of CS precise pagings in the local cell.

Usage
This counter indicates the number of CS precise pagings in the local cell.

Measurement Point
When the BSC sends a paging message for the CS service to the BTS, the counter is updated if the current paging is the precise paging.

Unit
Time
17-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

17.37 C901110042 Number of CS Precise Paging Response

Description
This counter counts the number of CS precise paging responses in the local cell.

Usage
This counter indicates the number of CS precise paging responses in the local cell.

Measurement Point
When the BSC receives the ESTABLISH INDICATION message as paging response from the BTS, the counter is updated if the corresponding paging is detected as the first paging.

Unit
Time

17.38 C901110043 Number of CS First Paging

Description
This counter counts the number of CS first pagings in the local cell.

Usage
This counter indicates the number of CS first pagings in the local cell.

Measurement Point
When the BSC sends a paging message for the CS service to the BTS, the counter is updated if the current paging is the first paging.

Unit
Time

17.39 C901110044 Number of CS First Paging Response

Description
This counter counts the number of CS first paging responses in the local cell.

Usage
This counter indicates the number of CS first paging responses in the local cell.
17-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

Measurement Point
When the BSC receives the ESTABLISH INDICATION message as the paging response from the BTS, the counter is updated if the corresponding paging is detected as the first paging.

Unit
Time

17.40 C901110045 Number of CS Second Paging

Description
This counter counts the number of CS second pagings in the local cell.

Usage
This counter indicates the number of CS second pagings in the local cell.

Measurement Point
When the BSC sends a paging message for the CS service to the BTS, the counter is updated if the current paging is the second paging.

Unit
Time

17.41 C901110046 Number of CS Second Paging Response

Description
This counter counts the number of CS second paging responses in the local cell.

Usage
This counter indicates the number of CS second paging responses in the local cell.

Measurement Point
When the BSC receives the ESTABLISH INDICATION message as the paging response from the BTS, the counter is updated if the corresponding paging is detected as the second paging.

Unit
Time
17-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

17.42 C901110047 Number of CS Third Paging

Description
This counter counts the number of CS third pagings in the local cell.

Usage
This counter indicates the number of CS third pagings in the local cell.

Measurement Point
When the BSC sends a paging message for the CS service to the BTS, the counter is updated if the current paging is the third paging.

Unit
Time

17.43 C901110048 Number of CS Third Paging Response

Description
This counter counts the number of CS third paging responses in the local cell.

Usage
This counter indicates the number of CS third paging responses in the local cell.

Measurement Point
When the BSC receives the ESTABLISH INDICATION message as the paging response from the BTS, the counter is updated if the corresponding paging is detected as the third paging.

Unit
Time

17.44 C901110049 Number of PS Precise Paging

Description
This counter counts the number of PS precise paging in the local cell.

17-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

Usage
This counter indicates the number of PS precise paging in the local cell.

Measurement Point
When the BSC sends a paging message for the PS service to the BTS, the counter is updated if the current paging is the precise paging.

Unit
Time

17.45 C901110050 Number of PS Precise Paging Response

Description
This counter counts the number of PS precise paging responses in the local cell.

Usage
This counter indicates the number of PS precise paging responses in the local cell.

Measurement Point
When the PS service is an uplink access for paging response, the counter is updated if the corresponding paging is detected as the precise paging.

Unit
Time

17.46 C901110051 Number of PS First Paging

Description
This counter counts the number of PS first pagings in the local cell.

Usage
This counter indicates the number of PS first pagings in the local cell.

Measurement Point
When the BSC sends a paging message for the PS service to the BTS, the counter is updated if the current paging is the first paging.

17-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Time

17.47 C901110052 Number of PS First Paging Response

Description
This counter counts the number of PS first paging responses in the local cell.

Usage
This counter indicates the number of PS first paging responses in the local cell.

Measurement Point
When the PS service is an uplink access for paging response, the counter is updated if the corresponding paging is detected as the first paging.

Unit
Time

17.48 C901110053 Number of PS Second Paging

Description
This counter counts the number of PS second pagings in the local cell.

Usage
This counter indicates the number of PS second pagings in the local cell.

Measurement Point
When the BSC sends a paging message for the PS service to the BTS, the counter is updated if the current paging is the second paging.

Unit
Time

17.49 C901110054 Number of PS Second Paging Response

Description
This counter counts the number of PS second paging responses in the local cell.
17-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

Usage
This counter indicates the number of PS second paging responses in the local cell.

Measurement Point
When the PS service is is an uplink access for paging response, the counter is updated if the corresponding paging is detected as the second paging.

Unit
Time

17.50 C901110055 Number of PS Third Paging

Description
This counter counts the number of PS third pagings in the local cell.

Usage
This counter indicates the number of PS third pagings in the local cell.

Measurement Point
When the BSC sends a paging message for the PS service to the BTS, the counter is updated if the current paging is the third paging.

Unit
Time

17.51 C901110056 Number of PS Third Paging Response

Description
This counter counts the number of PS third paging responses in the local cell.

Usage
This counter indicates the number of PS third paging responses in the local cell.

Measurement Point
When the PS service is an uplink access for paging response, the counter is updated if the corresponding paging is detected as the third paging.

17-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Time

17.52 C901110057 Number of CS Precise Paging for Last Service in This Cell
Description
This counter counts the number of CS precise pagings for the last service in the local cell.

Usage
This counter indicates the number of CS precise pagings for the last service in the local cell.

Measurement Point
When the BSC sends the CS precise paging, the counter is updated if the last service of the user is in the local cell.

Unit
Time

17.53 C901110058 Number of CS Precise Paging No Response for Last Service in This Cell
Description
This counter counts the number of CS precise pagings with no response for the last service in the local cell.

Usage
This counter indicates the number of CS precise pagings with no response for the last service in the local cell.

Measurement Point
When the BSC does not receive a user response after sending the CS precise paging, the counter is updated for the cell of the last service if the paging waiting timer times out.

Unit
Time

17-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

17.54 C901110059 Number of CS First Paging for Last Service in This Cell
Description
This counter counts the number of CS first pagings for the last service in the local cell.

Usage
This counter indicates the number of CS first pagings for the last service in the local cell.

Measurement Point
When the BSC sends the CS first paging, the counter is updated if the last service of the user is in the local cell.

Unit
Time

17.55 C901110060 Number of CS First Paging No Response for Last Service in This Cell
Description
This counter counts the number of CS first pagings with no response for the last service in the local cell.

Usage
This counter indicates the number of CS first pagings with no response for the last service in the local cell.

Measurement Point
When the BSC does not receive a user response after sending the CS first paging, the counter is updated for the cell of the last service if the paging waiting timer times out.

Unit
Time

17-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

17.56 C901110061 Number of CS Second Paging for Last Service in This Cell
Description
This counter counts the number of CS second pagings for the last service in the local cell.

Usage
This counter indicates the number of CS second pagings for the last service in the local cell.

Measurement Point
When the BSC sends the CS second paging, the counter is updated if the last service of the user is in the local cell.

Unit
Time

17.57 C901110062 Number of CS Second Paging No Response for Last Service in This Cell
Description
This counter counts the number of CS second pagings with no response for the last service in the local cell.

Usage
This counter indicates the number of CS second pagings with no response for the last service in the local cell.

Measurement Point
When the BSC does not receive a user response after sending the CS second paging, the counter is updated for the cell of the last service if the paging waiting timer times out.

Unit
Time

17-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

17.58 C901110063 Number of CS Third Paging for Last Service in This Cell
Description
This counter counts the number of CS third pagings for the last service in the local cell.

Usage
This counter indicates the number of CS third pagings for the last service in the local cell.

Measurement Point
When the BSC sends the CS third paging, the counter is updated if the last service of the user is in the local cell.

Unit
Time

17.59 C901110064 Number of CS Third Paging No Response for Last Service in This Cell
Description
This counter counts the number of CS third pagings with no response for the last service in the local cell.

Usage
This counter indicates the number of CS third pagings with no response for the last service in the local cell.

Measurement Point
When the BSC does not receive a user response after sending the CS third paging, the counter is updated for the cell of the last service if the paging waiting timer times out.

Unit
Time

17-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

17.60 C901110065 Number of PS Precise Paging for Last Service in This Cell
Description
This counter counts the number of PS precise pagings for the last service in the local cell.

Usage
This counter indicates the number of PS precise pagings for the last service in the local cell.

Measurement Point
When the BSC sends the PS precise paging, the counter is updated if the last service of the user is in the local cell.

Unit
Time

17.61 C901110066 Number of PS Precise Paging No Response for Last Service in This Cell
Description
This counter counts the number of PS precise pagings with no response for the last service in the local cell.

Usage
This counter indicates the number of PS precise pagings with no response for the last service in the local cell.

Measurement Point
When the BSC does not receive a user response after sending the PS precise paging, the counter is updated for the cell of the last service if the paging waiting timer times out.

Unit
Time

17-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

17.62 C901110067 Number of PS First Paging for Last Service in This Cell
Description
This counter counts the number of PS first pagings for the last service in the local cell.

Usage
This counter indicates the number of PS first pagings for the last service in the local cell.

Measurement Point
When the BSC sends the PS first paging, the counter is updated if the last service of the user is in the local cell.

Unit
Time

17.63 C901110068 Number of PS First Paging No Response for Last Service in This Cell
Description
This counter counts the number of PS first pagings with no response for the last service in the local cell.

Usage
This counter indicates the number of PS first pagings with no response for the last service in the local cell.

Measurement Point
When the BSC does not receive a user response after sending the PS first paging, the counter is updated for the cell of the last service if the paging waiting timer times out.

Unit
Time

17-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

17.64 C901110069 Number of PS Second Paging for Last Service in This Cell
Description
This counter counts the number of PS second pagings for the last service in the local cell.

Usage
This counter indicates the number of PS second pagings for the last service in the local cell.

Measurement Point
When the BSC sends the PS second paging, the counter is updated if the last service of the user is in the local cell.

Unit
Time

17.65 C901110070 Number of PS Second Paging No Response for Last Service in This Cell
Description
This counter counts the number of PS second pagings with no response for the last service in the local cell.

Usage
This counter indicates the number of PS second pagings with no response for the last service in the local cell.

Measurement Point
When the BSC does not receive a user response after sending the PS second paging, the counter is updated for the cell of the last service if the paging waiting timer times out.

Unit
Time

17-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

17.66 C901110071 Number of PS Third Paging for Last Service in This Cell
Description
This counter counts the number of PS third pagings for the last service in the local cell.

Usage
This counter indicates the number of PS third pagings for the last service in the local cell.

Measurement Point
When the BSC sends the PS third paging, the counter is updated if the last service of the user is in the local cell.

Unit
Time

17.67 C901110072 Number of PS Third Paging No Response for Last Service in This Cell
Description
This counter counts the number of PS third pagings with no response for the last service in the local cell.

Usage
This counter indicates the number of PS third pagings with no response for the last service in the local cell.

Measurement Point
When the BSC does not receive a user response after sending the PS third paging, the counter is updated for the cell of the last service if the paging waiting timer times out.

Unit
Time

17-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

17.68 C901110073 Number of CS Precise Paging (Paging Hole Search)

Description
This counter counts the number of CS precise pagings before the paging hole timer times out.

Usage
This counter indicates the number of CS precise pagings before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the CS precise paging, the counter is updated for the cell that receives a response if the BSC receives a response. Otherwise, the counter is updated for the cell of the last user service.

Unit
Time

17.69 C901110074 Number of CS Precise Paging No Response (Paging Hole Search)

Description
This counter counts the number of CS precise pagings with no response before the paging hole timer times out.

Usage
This counter indicates the number of CS precise pagings with no response before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the CS precise paging, the counter is updated for the cell where the last service of the user occurs, if the BSC does not receive a response.

Unit
Time

17-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

17.70 C901110075 Number of CS First Paging (Paging Hole Search)

Description
This counter counts the number of CS first pagings before the paging hole timer times out.

Usage
This counter indicates the number of CS first pagings before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the CS first paging, the counter is updated for the cell that receives a response if the BSC receives a response. Otherwise, the counter is updated for the cell of the last user service.

Unit
Time

17.71 C901110076 Number of CS First Paging No Response (Paging Hole Search)

Description
This counter counts the number of CS first pagings with no response before the paging hole timer times out.

Usage
This counter indicates the number of CS first pagings with no response before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the CS first paging, the counter is updated for the cell of the last user service if the BSC does not receive a response.

Unit
Time

17-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

17.72 C901110077 Number of CS Second Paging (Paging Hole Search)

Description
This counter counts the number of CS second pagings before the paging hole timer times out.

Usage
This counter indicates the number of CS second pagings before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the CS second paging, the counter is updated for the cell that receives a response if the BSC receives a response. Otherwise, the counter is updated for the cell of the last user service.

Unit
Time

17.73 C901110078 Number of CS Second Paging No Response (Paging Hole Search)

Description
This counter counts the number of CS second pagings with no response before the paging hole timer times out.

Usage
This counter indicates the number of CS second pagings with no response before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the CS second paging, the counter is updated for the cell of the last user service if the BSC does not receive a response.

Unit
Time

17-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

17.74 C901110079 Number of CS Third Paging (Paging Hole Search)

Description
This counter counts the number of CS third pagings before the paging hole timer times out.

Usage
This counter indicates the number of CS third pagings before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the CS third paging, the counter is updated for the cell that receives a response if the BSC receives a response. Otherwise, the counter is updated for the cell of the last user service.

Unit
Time

17.75 C901110080 Number of CS Third Paging No Response (Paging Hole Search)

Description
This counter counts the number of CS third pagings with no response before the paging hole timer times out.

Usage
This counter indicates the number of CS third pagings with no response before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the CS third paging, the counter is updated for the cell of the last user service if the BSC does not receive a response.

Unit
Time

17-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

17.76 C901110081 Number of PS Precise Paging (Paging Hole Search)

Description
This counter counts the number of PS precise pagings before the paging hole timer times out.

Usage
This counter indicates the number of PS precise pagings before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the PS precise paging, the counter is updated for the cell that receives a response if the BSC receives a response. Otherwise, the counter is updated for the cell of the last user service.

Unit
Time

17.77 C901110082 Number of PS Precise Paging No Response (Paging Hole Search)

Description
This counter counts the number of PS precise pagings with no response before the paging hole timer times out.

Usage
This counter indicates the number of PS precise pagings with no response before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the PS precise paging, the counter is updated for the cell of the last user service if the BSC does not receive a response.

Unit
Time

17-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

17.78 C901110083 Number of PS First Paging (Paging Hole Search)

Description
This counter counts the number of PS first pagings before the paging hole timer times out.

Usage
This counter indicates the number of PS first pagings before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the PS first paging, the counter is updated for the cell that receives a response if the BSC receives a response. Otherwise, the counter is updated for the cell of the last user service.

Unit
Time

17.79 C901110084 Number of PS First Paging No Response (Paging Hole Search)

Description
This counter counts the number of PS first pagings with no response before the paging hole timer times out.

Usage
This counter indicates the number of PS first pagings with no response before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the PS first paging, the counter is updated for the cell of the last user service if the BSC does not receive a response.

Unit
Time

17-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

17.80 C901110085 Number of PS Second Paging (Paging Hole Search)

Description
This counter counts the number of PS second pagings before the paging hole timer times out.

Usage
This counter indicates the number of PS second pagings before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the PS second paging, the counter is updated for the cell that receives a response if the BSC receives a response. Otherwise, the counter is updated for the cell of the last user service.

Unit
Time

17.81 C901110086 Number of PS Second Paging No Response (Paging Hole Search)

Description
This counter counts the number of PS second pagings with no response before the paging hole timer times out.

Usage
This counter indicates the number of PS second pagings with no response before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the PS second paging, the counter is updated for the cell of the last user service if the BSC does not receive a response.

Unit
Time

17-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 17 Radio Access Measurement

17.82 C901110087 Number of PS Third Paging (Paging Hole Search)

Description
This counter counts the number of PS third pagings before the paging hole timer times out.

Usage
This counter indicates the number of PS third pagings before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the CS third paging, the counter is updated for the cell that receives a response if the BSC receives a response. Otherwise, the counter is updated for the cell of the last user service.

Unit
Time

17.83 C901110088 Number of PS Third Paging No Response (Paging Hole Search)

Description
This counter counts the number of PS third pagings with no response before the paging hole timer times out.

Usage
This counter indicates the number of PS third pagings with no response before the paging hole timer times out.

Measurement Point
When the BSC detects that the paging hole timer does not time out when sending the PS third paging, the counter is updated for the cell of the last user service if the BSC does not receive a response.

Unit
Time

17-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

17-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18

Radio Measurement
Table of Contents
Overview ..................................................................................................................18-4 C901120001 Number of UL signal quality samples in wireless channels ..................18-4 C901120002 Level of worst UL signal quality in wireless channels ...........................18-5 C901120003 Total value of UL quality level values in wireless channels ...................18-5 C901120004 Number of DL signal quality samples in wireless channels ..................18-6 C901120005 Level of worst DL signal quality in wireless channels ...........................18-6 C901120006 Total value of DL quality strength values in wireless channels..............18-7 C901120007 Number of received UL signal strength samples in wireless channels..18-8 C901120008 Maximum received UL signal strength in wireless channels .................18-8 C901120009 Minimum received UL signal strength in wireless channels ..................18-9 C901120010 Total value of UL signal strength in wireless channels..........................18-9 C901120011 Number of received DL signal strength samples in wireless channels .18-10 C901120012 Maximum received DL signal strength in wireless channels ............... 18-11 C901120013 Minimum DL received signal strength in radio channels..................... 18-11 C901120014 Total value of DL signal strength in wireless channels........................18-12 C901120015 Number of TA samples in wireless channels ......................................18-12 C901120016 Maximum TA in wireless channels .....................................................18-13 C901120017 Total number of TAs in wireless channels ..........................................18-13 C901120018 Mean number of idle TCH/Fs with interference band 0 ......................18-14 C901120024 Mean number of idle TCH/Hs with interference band 0 ......................18-15 C901120030 Mean number of idle SDCCHs with interference band 0 ....................18-15 C901120031 Mean number of idle SDCCHs with interference band 1 ....................18-16 C901120032 Mean number of idle SDCCHs with interference band 2 ....................18-16 C901120033 Mean number of idle SDCCHs with interference band 3 ....................18-17 C901120034 Mean number of idle SDCCHs with interference band 4 ....................18-17 C901120035 Mean number of idle SDCCHs with interference band 5 ....................18-18 C901120053 Number of using noise suppression ...................................................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 C901120063 Number of uplink error frame on FR_V1 ............................................18-22 C901120064 Total Number of uplink frame on FR_V1 ............................................18-22 C901120065 Number of uplink error frame on FR_V2 ............................................18-22 C901120066 Total Number of uplink frame on FR_V2 ............................................18-23 C901120067 Number of uplink error frame on FR_V3 ............................................18-23
18-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901120068 Total Number of uplink frame on FR_V3 ............................................18-23 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 C901120073 Number of UL signal quality samples in radio channels on SDCCH ...18-25 C901120074 Level of worst UL signal quality in radio channels on SDCCH............18-26 C901120075 Total value of UL quality level values in radio channels on SDCCH....18-27 C901120076 Number of DL signal quality samples in radio channels on SDCCH ...18-27 C901120077 Level of worst DL signal quality in radio channels on SDCCH............18-28 C901120078 Total value of DL quality strength values in radio channels on SDCCH ..................................................................................................................18-28 C901120079 Number of received UL signal strength samples in radio channels on SDCCH ..................................................................................................................18-29 C901120080 Maximum received UL signal strength in radio channels on SDCCH .18-30 C901120081 Minimum received UL signal strength in radio channels on SDCCH ..18-30 C901120082 Total value of UL signal strength in radio channels on SDCCH ..........18-31 C901120083 Number of received DL signal strength samples in radio channels on SDCCH ..................................................................................................................18-31 C901120084 Maximum received DL signal strength in radio channels on SDCCH .18-32 C901120085 Minimum DL received signal strength in radio channels on SDCCH ..18-33 C901120086 Total value of DL signal strength in radio channels on SDCCH ..........18-33 C901120087 Number of UL signal quality samples in radio channels on TCH ........18-34 C901120088 Level of worst UL signal quality in radio channels on TCH .................18-34 C901120089 Total value of UL quality level values in radio channels on TCH .........18-35 C901120090 Number of DL signal quality samples in radio channels on TCH ........18-36 C901120091 Level of worst DL signal quality in radio channels on TCH .................18-36 C901120092 Total value of DL quality strength values in radio channels on TCH ...18-37 C901120093 Number of received UL signal strength samples in radio channels on TCH .......................................................................................................................18-37 C901120094 Maximum received UL signal strength in radio channels on TCH.......18-38 C901120095 Minimum received UL signal strength in radio channels on TCH........18-39 C901120096 Total value of UL signal strength in radio channels on TCH ...............18-39 C901120097 Number of received DL signal strength samples in radio channels on TCH .......................................................................................................................18-40 C901120098 Maximum received DL signal strength in radio channels on TCH.......18-40 C901120099 Minimum DL received signal strength in radio channels on TCH........18-41 C901120100 Total value of DL signal strength in radio channels on TCH ...............18-42 C901120101 Number of samples with UL RQ = 0 on SDCCH ................................18-42 C901120102 Number of samples with UL RQ = 1 on SDCCH ................................18-43 C901120103 Number of samples with UL RQ = 2 on SDCCH ................................18-44 C901120104 Number of samples with UL RQ = 3 on SDCCH ................................18-44 C901120105 Number of samples with UL RQ = 4 on SDCCH ................................18-45 C901120106 Number of samples with UL RQ = 5 on SDCCH ................................18-46 C901120107 Number of samples with UL RQ = 6 on SDCCH ................................18-46
18-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

C901120108 Number of samples with UL RQ = 7 on SDCCH ................................18-47 C901120109 Number of samples with DL RQ = 0 on SDCCH ................................18-47 C901120110 Number of samples with DL RQ = 1 on SDCCH.................................18-48 C901120111 Number of samples with DL RQ = 2 on SDCCH.................................18-49 C901120112 Number of samples with DL RQ = 3 on SDCCH.................................18-49 C901120113 Number of samples with DL RQ = 4 on SDCCH.................................18-50 C901120114 Number of samples with DL RQ = 5 on SDCCH.................................18-51 C901120115 Number of samples with DL RQ = 6 on SDCCH.................................18-51 C901120116 Number of samples with DL RQ = 7 on SDCCH.................................18-52 C901120117 Number of samples with UL RQ = 0 on TCH......................................18-53 C901120118 Number of samples with UL RQ = 1 on TCH......................................18-53 C901120119 Number of samples with UL RQ = 2 on TCH......................................18-54 C901120120 Number of samples with UL RQ = 3 on TCH......................................18-55 C901120121 Number of samples with UL RQ = 4 on TCH......................................18-55 C901120122 Number of samples with UL RQ = 5 on TCH......................................18-56 C901120123 Number of samples with UL RQ = 6 on TCH......................................18-57 C901120124 Number of samples with UL RQ = 7 on TCH......................................18-57 C901120125 Number of samples with DL RQ = 0 on TCH......................................18-58 C901120126 Number of samples with DL RQ = 1 on TCH......................................18-59 C901120127 Number of samples with DL RQ = 2 on TCH......................................18-59 C901120128 Number of samples with DL RQ = 3 on TCH......................................18-60 C901120129 Number of samples with DL RQ = 4 on TCH......................................18-61 C901120130 Number of samples with DL RQ = 5 on TCH......................................18-61 C901120131 Number of samples with DL RQ = 6 on TCH......................................18-62 C901120132 Number of samples with DL RQ = 7 on TCH......................................18-63 C901120133 Rach Level Grade0 (Above -57 dBm) Sample ...................................18-63 C901120134 Rach Level Grade1 (-57 to -62 dBm) Sample ....................................18-64 C901120135 Rach Level Grade2 (-63 to -68 dBm) Sample ....................................18-64 C901120136 Rach Level Grade3 (-69 to -74 dBm) Sample ....................................18-65 C901120137 Rach Level Grade4 (-75 to -80 dBm) Sample ....................................18-65 C901120138 Rach Level Grade5 (-81 to -86 dBm) Sample ....................................18-66 C901120139 Rach Level Grade6 (-87 to -92 dBm) Sample ....................................18-66 C901120140 Rach Level Grade7 (-93 to -98 dBm) Sample ....................................18-67 C901120141 Rach Level Grade8 (-99 to -104 dBm) Sample ..................................18-67 C901120142 Rach Level Grade9 (Below -104 dBm) Sample..................................18-68 C901120143 Number of Sample With Interference Band........................................18-68 C901120144 Number of Idle TCH/F With Interference Band 0................................18-69 C901120145 Number of Idle TCH/F With Interference Band 1................................18-69 C901120146 Number of Idle TCH/F With Interference Band 2................................18-70 C901120147 Number of Idle TCH/F With Interference Band 3................................18-70 C901120148 Number of Idle TCH/F With Interference Band 4................................18-71 C901120149 Number of Idle TCH/F With Interference Band 5................................18-71 C901120150 Number of Idle TCH/H With Interference Band 0 ...............................18-72 C901120151 Number of Idle TCH/H With Interference Band 1 ...............................18-72 C901120152 Number of Idle TCH/H With Interference Band 2 ...............................18-73
18-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901120153 Number of Idle TCH/H With Interference Band 3 ...............................18-73 C901120154 Number of Idle TCH/H With Interference Band 4 ...............................18-74 C901120155 Number of Idle TCH/H With Interference Band 5 ...............................18-74 C901120156 Number of Idle SDCCH With Interference Band 0..............................18-75 C901120157 Number of Idle SDCCH With Interference Band 1..............................18-75 C901120158 Number of Idle SDCCH With Interference Band 2..............................18-76 C901120159 Number of Idle SDCCH With Interference Band 3..............................18-76 C901120160 Number of Idle SDCCH With Interference Band 4..............................18-77 C901120161 Number of Idle SDCCH With Interference Band 5..............................18-77

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. The measurement takes cell as the statistics unit.

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.

Unit
Times
18-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

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 in wireless channels

Definition
Total value of UL quality level values in radio channels

Description
This counter counts the number of total value of UL quality level values in radio channels in radio measurement reports. The counter accumulates UL quality level values in radio channels in UL measurement report or pre-processing measurement report received by BSC.

Usage
This counter is used to find out status of total value of UL quality level values in radio channels.
18-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when BSC receives UL measurement report or pre-processing measurement report.

Unit
None

18.5 C901120004 Number of DL signal quality samples in wireless channels

Definition
Number of DL signal quality samples in radio channels

Description
This counter counts the number of received DL radio measurement report or pre-processing measurement report. The counter increments when BSC receives DL radio measurement report or 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

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
18-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

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
The counter counts when BSC receives DL measurement report or pre-processing measurement report.

Unit
None

18-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 in wireless channels

Definition
Maximum received UL signal strength in radio channels

Description
This counter counts the maximum received UL signal strength in radio channels in UL measurement report. If the UL signal strength in radio channel in UL measurement report or pre-processing measurement report received by BSC is higher than the recorded highest UL signal strength, then the new highest UL signal strength will be recorded.

Usage
This counter is used to find out status of maximum received UL signal strength in radio channels.

18-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

Measurement Point
The counter counts when BSC receives UL measurement report or pre-processing 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
The counter counts when BSC receives UL measurement report or pre-processing 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-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The counter counts when BSC receives UL measurement report or pre-processing 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-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

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
The counter counts when BSC receives DL measurement report or pre-processing 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-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when BSC receives DL measurement report or pre-processing 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
The counter counts when BSC receives DL measurement report or pre-processing 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-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

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-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-001 Idle Channel Measurement

18-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

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
The counter increments when timed database inquiry is carried out.

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-001 Idle Channel Measurement ZGO-03-02-005 Dynamic Half Rate Allocation

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
The counter increments when timed database inquiry is carried out.
18-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-03-02-001 Idle Channel Measurement

18.22 C901120031 Mean number of idle SDCCHs with interference band 1

Definition
Mean number of idle SDCCHs with interference band 1

Description
This counter counts the mean number of idle SDCCHs with interference band 1.

Usage
This counter is used to find out number of idle SDCCHs with interference band 1.

Measurement Point
The counter increments when timed database inquiry is carried out.

Unit
Times

Related Features
ZGO-03-02-001 Idle Channel Measurement

18.23 C901120032 Mean number of idle SDCCHs with interference band 2

Definition
Mean number of idle SDCCHs with interference band 2

Description
This counter counts the mean number of idle SDCCHs with interference band 2.

Usage
This counter is used to find out number of idle SDCCHs with interference band 2.
18-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

Measurement Point
The counter increments when timed database inquiry is carried out.

Unit
Times

Related Features
ZGO-03-02-001 Idle Channel Measurement

18.24 C901120033 Mean number of idle SDCCHs with interference band 3

Definition
Mean number of idle SDCCHs with interference band 3

Description
This counter counts the mean number of idle SDCCHs with interference band 3.

Usage
This counter is used to find out number of idle SDCCHs with interference band 3.

Measurement Point
The counter increments when timed database inquiry is carried out.

Unit
Times

Related Features
ZGO-03-02-001 Idle Channel Measurement

18.25 C901120034 Mean number of idle SDCCHs with interference band 4

Definition
Mean number of idle SDCCHs with interference band 4.

Description
This counter counts the mean number of idle SDCCHs with interference band 4.
18-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out number of idle SDCCHs with interference band 4.

Measurement Point
The counter increments when timed database inquiry is carried out.

Unit
Times

Related Features
ZGO-03-02-001 Idle Channel Measurement

18.26 C901120035 Mean number of idle SDCCHs with interference band 5

Definition
Mean number of idle SDCCHs with interference band 5

Description
This counter counts the mean number of idle SDCCHs with interference band 5.

Usage
This counter is used to find out number of idle SDCCHs with interference band 5.

Measurement Point
The counter increments when timed database inquiry is carried out.

Unit
Times

Related Features
ZGO-03-02-001 Idle Channel Measurement

18.27 C901120053 Number of using noise suppression

Definition
Number of using noise suppression
18-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

Description
This counter does not count for the time being.

18.28 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

18.29 C901120059 Number of samples with voice 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
This counter is used to find out the UL voice quality on the radio channel.
18-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

18.30 C901120060 Number of samples with voice 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
This counter is used to find out the UL voice quality on the radio channel.

Measurement Point
When BSC receives the UL measurement report, preprocessing measurement report, or enhanced preprocessing measurement report, if the voice quality is medium, the counter increments.

Unit
Times

18.31 C901120061 Number of samples with voice quality is bad

Definition
Number of samples with voice quality is bad

18-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

Description
This counter counts the number of voice quality being bad. When the UL measurement report, preprocessing measurement report, or enhanced preprocessing measurement report is received, if the voice quality is bad, the counter increments.

Usage
This counter is used to find out the UL voice quality on the radio channel.

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

18.32 C901120062 Number of samples with voice 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, preprocessing measurement report, or enhanced preprocessing measurement report is received, if the voice quality is awful, the counter increments.

Usage
This counter is used to find out the UL voice quality on the radio channel.

Measurement Point
When BSC receives the UL measurement report, preprocessing measurement report, or enhanced preprocessing measurement report, if the voice quality is awful, the counter increments.

Unit
Times

18-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

18.33 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.34 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
The counter's value is obtained from the periodic measurement report.

18.35 C901120065 Number of uplink error frame on FR_V2

Description
This counter counts the number of uplink error frames of full-rate version 2.

Usage
This counter is used to find out the number of incorrect uplink voice frames of full-rate version 2. The counter increments when uplink decoding error occurs.

18-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

Measurement Point
The counter's value is obtained from the periodic measurement report.

18.36 C901120066 Total Number of uplink frame on FR_V2

Description
This counter counts the number of uplink voice frames of full-rate version 2.

Usage
This counter is used to find out the number of uplink voice frames of full-rate version 2. The counter increments every 20 ms.

Measurement Point
The counter's value is obtained from the periodic measurement report.

18.37 C901120067 Number of uplink error frame on FR_V3

Description
This counter counts the number of uplink error frames of full-rate version 3.

Usage
This counter is used to find out the number of incorrect uplink voice frames of full-rate version 3. The counter increments when uplink decoding error occurs.

Measurement Point
The counter's value is obtained from the periodic measurement report.

18.38 C901120068 Total Number of uplink frame on FR_V3

Description
This counter counts the number of uplink voice frames of full-rate version 3.

18-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of uplink voice frames of full-rate version 3. The counter increments every 20 ms.

Measurement Point
The counter's value is obtained from the periodic measurement report.

18.39 C901120069 Number of uplink error frame on HR_V1

Description
This counter counts the number of uplink error frames of half-rate version 1.

Usage
This counter is used to find out the number of incorrect uplink voice frames of half-rate version 1. The counter increments when uplink decoding error occurs.

Measurement Point
The counter's value is obtained from the periodic measurement report.

18.40 C901120070 Total Number of uplink frame on 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. The counter increments every 20 ms.

Measurement Point
The counter's value is obtained from the periodic measurement report.

18-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.41 C901120071 Number of uplink error frame on 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 version 3. The counter increments when uplink decoding error occurs.

Measurement Point
The counter's value is obtained from the periodic measurement report.

18.42 C901120072 Total Number of uplink frame on 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. The counter increments every 20 ms.

Measurement Point
The counter's value is obtained from the periodic measurement report.

18.43 C901120073 Number of UL signal quality samples in radio channels on SDCCH

Definition
Number of UL signal quality samples in radio channels on SDCCH

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.

18-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of UL signal quality samples in radio channels on SDCCH.

Measurement Point
The counter increments when BSC receives UL measurement report or pre-processing measurement report.

Unit
Times

18.44 C901120074 Level of worst UL signal quality in radio channels on SDCCH

Definition
Level of worst UL signal quality in radio channels on SDCCH

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

Measurement Point
The counter counts when BSC receives UL measurement report or pre-processing measurement report.

Unit
None

18-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.45 C901120075 Total value of UL quality level values in radio channels on SDCCH
Definition
Total value of UL quality level values in radio channels on SDCCH

Description
This counter counts the number of total value of UL quality level values in radio channels on SDCCH in radio measurement reports. The counter accumulates UL quality level values in radio channels on SDCCH in UL measurement report or pre-processing measurement report received by BSC.

Usage
This counter is used to find out status of total value of UL quality level values in radio channels on SDCCH.

Measurement Point
The counter counts when BSC receives UL measurement report or pre-processing measurement report.

Unit
None

18.46 C901120076 Number of DL signal quality samples in radio channels on SDCCH

Definition
Number of DL signal quality samples in radio channels on SDCCH

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

18-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter increments when BSC receives DL measurement report or pre-processing measurement report.

Unit
Times

18.47 C901120077 Level of worst DL signal quality in radio channels on SDCCH

Definition
Level of worst DL signal quality in radio channels on SDCCH

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

Measurement Point
The counter counts when BSC receives DL measurement report or pre-processing measurement report.

Unit
None

18.48 C901120078 Total value of DL quality strength values in radio channels on SDCCH
Definition
Total value of DL quality level values in radio channels on SDCCH

18-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

Description
This counter counts the number of total value of DL quality level values in radio channels on SDCCH in radio measurement reports. The counter accumulates DL quality level values in radio channels on SDCCH in DL measurement report or pre-processing measurement report received by BSC.

Usage
This counter is used to find out status of total value of DL quality level values in radio channels on SDCCH.

Measurement Point
The counter counts when BSC receives DL measurement report or pre-processing measurement report.

Unit
None

18.49 C901120079 Number of received UL signal strength samples in radio channels on SDCCH
Definition
Number of received UL signal strength samples in radio channels on SDCCH

Description
This counter counts the number of received UL signal strength samples in radio channels on SDCCH 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 on SDCCH.

Measurement Point
The counter increments when BSC receives UL measurement report or pre-processing measurement report.

Unit
Times

18-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

18.50 C901120080 Maximum received UL signal strength in radio channels on SDCCH

Definition
Maximum received UL signal strength in radio channels on SDCCH

Description
This counter counts the maximum received UL signal strength in radio channels on SDCCH in UL measurement report. If the UL signal strength in radio channel in UL measurement report or pre-processing measurement report received by BSC is higher than the recorded highest UL signal strength, then the new highest UL signal strength will be recorded.

Usage
This counter is used to find out status of maximum received UL signal strength in radio channels on SDCCH.

Measurement Point
The counter counts when BSC receives UL measurement report or pre-processing measurement report.

Unit
None

18.51 C901120081 Minimum received UL signal strength in radio channels on SDCCH

Definition
Minimum received UL signal strength in radio channels on SDCCH

Description
This counter counts the minimum received UL signal strength in radio channels on SDCCH in UL measurement report. If the UL signal strength in radio channel in UL measurement report or pre-processing measurement report received by BSC is lower than the recorded lowest UL signal strength, then the new lowest UL signal strength will be recorded.

Usage
This counter is used to find out status of minimum received UL signal strength in radio channels on SDCCH.
18-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

Measurement Point
The counter counts when BSC receives UL measurement report or pre-processing measurement report.

Unit
None

18.52 C901120082 Total value of UL signal strength in radio channels on SDCCH

Definition
Total value of UL signal strength in radio channels on SDCCH

Description
This counter counts the number of total value of UL signal strength in radio channels on SDCCH in radio measurement reports. The counter accumulates values of UL signal strength in radio channels on SDCCH in UL measurement report or pre-processing measurement report received by BSC.

Usage
This counter is used to find out status of total value of UL signal strength in radio channels on SDCCH.

Measurement Point
The counter counts when BSC receives UL measurement report or pre-processing measurement report.

Unit
None

18.53 C901120083 Number of received DL signal strength samples in radio channels on SDCCH
Definition
Number of received DL signal strength samples in radio channels on SDCCH

18-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of received DL signal strength samples in radio channels on SDCCH 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 on SDCCH.

Measurement Point
The counter increments when BSC receives DL measurement report or pre-processing measurement report.

Unit
Times

18.54 C901120084 Maximum received DL signal strength in radio channels on SDCCH

Definition
Maximum received DL signal strength in radio channels on SDCCH

Description
This counter counts the maximum received DL signal strength in radio channels on SDCCH in DL measurement report. If the DL signal strength in radio channel in DL measurement report or pre-processing measurement report received by BSC is higher than the recorded highest DL signal strength, then the new highest DL signal strength will be recorded.

Usage
This counter is used to find out status of maximum received DL signal strength in radio channels on SDCCH.

Measurement Point
The counter counts when BSC receives DL measurement report or pre-processing measurement report.

Unit
None

18-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.55 C901120085 Minimum DL received signal strength in radio channels on SDCCH

Definition
Minimum DL received signal strength in radio channels on SDCCH

Description
This counter counts the minimum received DL signal strength in radio channels on SDCCH in DL measurement report. If the DL signal strength in radio channel in DL measurement report or pre-processing measurement report received by BSC is lower than the recorded lowest DL signal strength, then the new lowest DL signal strength will be recorded.

Usage
This counter is used to find out status of minimum received DL signal strength in radio channels on SDCCH.

Measurement Point
The counter counts when BSC receives DL measurement report or pre-processing measurement report.

Unit
None

18.56 C901120086 Total value of DL signal strength in radio channels on SDCCH

Definition
Total value of DL signal strength in radio channels on SDCCH

Description
This counter counts the number of total value of DL signal strength in radio channels on SDCCH in radio measurement reports. The counter accumulates values of DL signal strength in radio channels on SDCCH in DL measurement report or pre-processing measurement report received by BSC.

Usage
This counter is used to find out status of total value of DL signal strength in radio channels on SDCCH.
18-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when BSC receives DL measurement report or pre-processing measurement report.

Unit
None

18.57 C901120087 Number of UL signal quality samples in radio channels on TCH

Definition
Number of UL signal quality samples in radio channels on TCH

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

Measurement Point
The counter increments when BSC receives UL measurement report or pre-processing measurement report.

Unit
Times

18.58 C901120088 Level of worst UL signal quality in radio channels on TCH

Definition
Level of worst UL signal quality in radio channels on TCH

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
18-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

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

Measurement Point
The counter counts when BSC receives UL measurement report or pre-processing measurement report.

Unit
None

18.59 C901120089 Total value of UL quality level values in radio channels on TCH
Definition
Total value of UL quality level values in radio channels on TCH

Description
This counter counts the number of total value of UL quality level values in radio channels on TCH in radio measurement reports. The counter accumulates UL quality level values in radio channels on TCH in UL measurement report or pre-processing measurement report received by BSC.

Usage
This counter is used to find out status of total value of UL quality level values in radio channels on TCH.

Measurement Point
The counter counts when BSC receives UL measurement report or pre-processing measurement report.

Unit
None

18-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

18.60 C901120090 Number of DL signal quality samples in radio channels on TCH

Definition
Number of DL signal quality samples in radio channels on TCH

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

Measurement Point
The counter increments when BSC receives DL measurement report or pre-processing measurement report.

Unit
Times

18.61 C901120091 Level of worst DL signal quality in radio channels on TCH

Definition
Level of worst DL signal quality in radio channels on TCH

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 on TCH.
18-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

Measurement Point
The counter counts when BSC receives DL measurement report or pre-processing measurement report.

Unit
None

18.62 C901120092 Total value of DL quality strength values in radio channels on TCH
Definition
Total value of DL quality level values in radio channels on TCH

Description
This counter counts the number of total value of DL quality level values in radio channels on TCH in radio measurement reports. The counter accumulates DL quality level values in radio channels on TCH in DL measurement report or pre-processing measurement report received by BSC.

Usage
This counter is used to find out status of total value of DL quality level values in radio channels on TCH.

Measurement Point
The counter counts when BSC receives DL measurement report or pre-processing measurement report.

Unit
None

18.63 C901120093 Number of received UL signal strength samples in radio channels on TCH
Definition
Number of received UL signal strength samples in radio channels on TCH

18-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of received UL signal strength samples in radio channels on TCH 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 on TCH.

Measurement Point
The counter increments when BSC receives UL measurement report or pre-processing measurement report.

Unit
Times

18.64 C901120094 Maximum received UL signal strength in radio channels on TCH

Definition
Maximum received UL signal strength in radio channels on TCH

Description
This counter counts the maximum received UL signal strength in radio channels on TCH in UL measurement report. If the UL signal strength in radio channel in UL measurement report or pre-processing measurement report received by BSC is higher than the recorded highest UL signal strength, then the new highest UL signal strength will be recorded.

Usage
This counter is used to find out status of maximum received UL signal strength in radio channels on TCH.

Measurement Point
The counter counts when BSC receives UL measurement report or pre-processing measurement report.

Unit
None

18-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.65 C901120095 Minimum received UL signal strength in radio channels on TCH

Definition
Minimum received UL signal strength in radio channels on TCH

Description
This counter counts the minimum received UL signal strength in radio channels on TCH in UL measurement report. If the UL signal strength in radio channel in UL measurement report or pre-processing measurement report received by BSC is lower than the recorded lowest UL signal strength, then the new lowest UL signal strength will be recorded.

Usage
This counter is used to find out status of minimum received UL signal strength in radio channels on TCH.

Measurement Point
The counter counts when BSC receives UL measurement report or pre-processing measurement report.

Unit
None

18.66 C901120096 Total value of UL signal strength in radio channels on TCH

Definition
Total value of UL signal strength in radio channels on TCH

Description
This counter counts the number of total value of UL signal strength in radio channels on TCH in radio measurement reports. The counter accumulates values of UL signal strength in radio channels on TCH in UL measurement report or pre-processing measurement report received by BSC.

Usage
This counter is used to find out status of total value of UL signal strength in radio channels on TCH.
18-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when BSC receives UL measurement report or pre-processing measurement report.

Unit
None

18.67 C901120097 Number of received DL signal strength samples in radio channels on TCH
Definition
Number of received DL signal strength samples in radio channels on TCH

Description
This counter counts the number of received DL signal strength samples in radio channels on TCH 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 on TCH.

Measurement Point
The counter increments when BSC receives DL measurement report or pre-processing measurement report.

Unit
Times

18.68 C901120098 Maximum received DL signal strength in radio channels on TCH

Definition
Maximum received DL signal strength in radio channels on TCH

Description
This counter counts the maximum received DL signal strength in radio channels on TCH in DL measurement report. If the DL signal strength in radio channel in DL measurement
18-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio 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 on TCH.

Measurement Point
The counter counts when BSC receives DL measurement report or pre-processing measurement report.

Unit
None

18.69 C901120099 Minimum DL received signal strength in radio channels on TCH

Definition
Minimum DL received signal strength in radio channels on TCH

Description
This counter counts the minimum received DL signal strength in radio channels on TCH in DL measurement report. If the DL signal strength in radio channel in DL measurement report or pre-processing measurement report received by BSC is lower than the recorded lowest DL signal strength, then the new lowest DL signal strength will be recorded.

Usage
This counter is used to find out status of minimum received DL signal strength in radio channels on TCH.

Measurement Point
The counter counts when BSC receives DL measurement report or pre-processing measurement report.

Unit
None

18-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

18.70 C901120100 Total value of DL signal strength in radio channels on TCH

Definition
Total value of DL signal strength in radio channels on TCH

Description
This counter counts the number of total value of DL signal strength in radio channels on TCH in radio measurement reports. The counter accumulates values of DL signal strength in radio channels on TCH in DL measurement report or pre-processing measurement report received by BSC.

Usage
This counter is used to find out status of total value of DL signal strength in radio channels on TCH.

Measurement Point
The counter counts when BSC receives DL measurement report or pre-processing measurement report.

Unit
None

18.71 C901120101 Number of samples with UL RQ = 0 on SDCCH

Definition
Number of samples with UL RQ = 0 on SDCCH

Description
BTS measures the level, quality, and interference of UL signal received in channel, and reports it to BSC, in combination with measurement report of DL signal reported by MS. Interval between BTS measurement and report is consistent with that of MS, that is, one measurement report is reported to BSC per 480 ms. Measurement mechanism of following counter C901120101 ~ C901120116 is same as that of this measurement value. This measurement value is the sample number with UL RQ = 0 in measurement report.

18-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

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 18-1.
Figure 18-1 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.72 C901120102 Number of samples with UL RQ = 1 on SDCCH

Definition
Number of samples with UL RQ = 1 on SDCCH

Description
This measurement value is the sample number with UL RQ=1 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=1 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-2.
Figure 18-2 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times
18-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

18.73 C901120103 Number of samples with UL RQ = 2 on SDCCH

Definition
Number of samples with UL RQ = 2 on SDCCH

Description
This measurement value is the sample number with UL RQ=2 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=2 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-3.
Figure 18-3 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.74 C901120104 Number of samples with UL RQ = 3 on SDCCH

Definition
Number of samples with UL RQ = 3 on SDCCH

Description
This measurement value is the sample number with UL RQ=3 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=3 in measurement report, this counter increments. The measurement point is A, as shown inFigure 18-4.

18-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

Figure 18-4 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.75 C901120105 Number of samples with UL RQ = 4 on SDCCH

Definition
Number of samples with UL RQ = 4 on SDCCH

Description
This measurement value is the sample number with UL RQ=4 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=4 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-5.
Figure 18-5 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

18.76 C901120106 Number of samples with UL RQ = 5 on SDCCH

Definition
Number of samples with UL RQ = 5 on SDCCH

Description
This measurement value is the sample number with UL RQ=5 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=5 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-6.
Figure 18-6 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.77 C901120107 Number of samples with UL RQ = 6 on SDCCH

Definition
Number of samples with UL RQ = 6 on SDCCH

Description
This measurement value is the sample number with UL RQ=6 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=6 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-7.

18-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

Figure 18-7 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.78 C901120108 Number of samples with UL RQ = 7 on SDCCH

Description
This measurement value is the sample number with UL RQ=7 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=7 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-8.
Figure 18-8 BSC Receives the Measurement Report Submitted by BTS

Unit
Times

18.79 C901120109 Number of samples with DL RQ = 0 on SDCCH

Definition
Number of samples with DL RQ = 0 on SDCCH

18-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 report, this counter increments. The measurement point is A, as shown in Figure 18-9.
Figure 18-9 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.80 C901120110 Number of samples with DL RQ = 1 on SDCCH

Definition
Number of samples with DL RQ = 1 on SDCCH

Description
This measurement value is the sample number with DL RQ=1 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=1 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-10.
Figure 18-10 - BSC Receives the Measurement Report Submitted BY BTS

18-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

Unit
Times

18.81 C901120111 Number of samples with DL RQ = 2 on SDCCH

Definition
Number of samples with DL RQ = 2 on SDCCH

Description
This measurement value is the sample number with DL RQ=2 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=2 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-11.
Figure 18-11 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.82 C901120112 Number of samples with DL RQ = 3 on SDCCH

Definition
Number of samples with DL RQ = 3 on SDCCH

Description
This measurement value is the sample number with DL RQ=3 in measurement report.

18-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=3 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-12.
Figure 18-12 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.83 C901120113 Number of samples with DL RQ = 4 on SDCCH

Definition
Number of samples with DL RQ = 4 on SDCCH

Description
This measurement value is the sample number with DL RQ=4 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=4 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-13.
Figure 18-13 - BSC Receives the Measurement Report Submitted By BTS

Unit
Times
18-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.84 C901120114 Number of samples with DL RQ = 5 on SDCCH

Definition
Number of samples with DL RQ = 5 on SDCCH

Description
This measurement value is the sample number with DL RQ=5 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=5 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-14.
Figure 18-14 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.85 C901120115 Number of samples with DL RQ = 6 on SDCCH

Definition
Number of samples with DL RQ = 6 on SDCCH

Description
This measurement value is the sample number with DL RQ=6 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=6 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-15.

18-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 18-15 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.86 C901120116 Number of samples with DL RQ = 7 on SDCCH

Definition
Number of samples with DL RQ = 7 on SDCCH

Description
This measurement value is the sample number with DL RQ=7 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ = 7 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-16.
Figure 18-16 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.87 C901120117 Number of samples with UL RQ = 0 on TCH

Definition
Number of samples with UL RQ = 0 on TCH

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 C901120117 ~ C901120132 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 18-17.
Figure 18-17 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.88 C901120118 Number of samples with UL RQ = 1 on TCH

Definition
Number of samples with UL RQ = 1 on TCH

Description
This measurement value is the sample number with UL RQ=1 in measurement report.
18-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=1 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-18.
Figure 18-18 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.89 C901120119 Number of samples with UL RQ = 2 on TCH

Definition
Number of samples with UL RQ = 2 on TCH

Description
This measurement value is the sample number with UL RQ=2 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=2 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-19.
Figure 18-19 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times
18-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.90 C901120120 Number of samples with UL RQ = 3 on TCH

Definition
Number of samples with UL RQ = 3 on TCH

Description
This measurement value is the sample number with UL RQ=3 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=3 in measurement report, this counter increments. The measurement point is A, as shown inFigure 18-20.
Figure 18-20 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.91 C901120121 Number of samples with UL RQ = 4 on TCH

Definition
Number of samples with UL RQ = 4 on TCH

Description
This measurement value is the sample number with UL RQ=4 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=4 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-21.

18-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 18-21 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.92 C901120122 Number of samples with UL RQ = 5 on TCH

Definition
Number of samples with UL RQ = 5 on TCH

Description
This measurement value is the sample number with UL RQ=5 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=5 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-22.
Figure 18-22 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.93 C901120123 Number of samples with UL RQ = 6 on TCH

Definition
Number of samples with UL RQ = 6 on TCH

Description
This measurement value is the sample number with UL RQ=6 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=6 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-23.
Figure 18-23 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.94 C901120124 Number of samples with UL RQ = 7 on TCH

Description
This measurement value is the sample number with UL RQ=7 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=7 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-24.

18-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 18-24 BSC Receives the Measurement Report Submitted by BTS

Unit
Times

18.95 C901120125 Number of samples with DL RQ = 0 on TCH

Definition
Number of samples with DL RQ = 0 on TCH

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 report, this counter increments. The measurement point is A, as shown in Figure 18-25.
Figure 18-25 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.96 C901120126 Number of samples with DL RQ = 1 on TCH

Definition
Number of samples with DL RQ = 1 on TCH

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=1 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-26.
Figure 18-26 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.97 C901120127 Number of samples with DL RQ = 2 on TCH

Definition
Number of samples with DL RQ = 2 on TCH

Description
This measurement value is the sample number with DL RQ=2 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=2 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-27.

18-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 18-27 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.98 C901120128 Number of samples with DL RQ = 3 on TCH

Definition
Number of samples with DL RQ = 3 on TCH

Description
This measurement value is the sample number with DL RQ=3 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=3 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-28.
Figure 18-28 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.99 C901120129 Number of samples with DL RQ = 4 on TCH

Definition
Number of samples with DL RQ = 4 on TCH

Description
This measurement value is the sample number with DL RQ=4 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=4 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-29.
Figure 18-29 - BSC Receives the Measurement Report Submitted By BTS

Unit
Times

18.100 C901120130 Number of samples with DL RQ = 5 on TCH

Definition
Number of samples with DL RQ = 5 on TCH

Description
This measurement value is the sample number with DL RQ=5 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=5 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-30.

18-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 18-30 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.101 C901120131 Number of samples with DL RQ = 6 on TCH

Definition
Number of samples with DL RQ = 6 on TCH

Description
This measurement value is the sample number with DL RQ=6 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=6 in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-31.
Figure 18-31 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.102 C901120132 Number of samples with DL RQ = 7 on TCH

Definition
Number of samples with DL RQ = 7 on TCH

Description
This measurement value is the sample number with DL RQ=7 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ = 7 on TCH in measurement report, this counter increments. The measurement point is A, as shown in Figure 18-32.
Figure 18-32 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

18.103 C901120133 Rach Level Grade0 (Above -57 dBm) Sample

Description
This counter counts the number of signal request samples with the level grade as 0 (above -57 dBm) received from the RACH/EGPRS channel by the BTS.

Usage
None

Measurement Point
None
18-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Time

18.104 C901120134 Rach Level Grade1 (-57 to -62 dBm) Sample

Description
This counter counts the number of signal request samples with the level grade as 1 (-57 to -62 dBm) received from the RACH/EGPRS channel by the BTS.

Usage
None

Measurement Point
None

Unit
Time

18.105 C901120135 Rach Level Grade2 (-63 to -68 dBm) Sample

Description
This counter counts the number of signal request samples with the level grade as 2 (-63 to -68 dBm) received from the RACH/EGPRS channel by the BTS.

Usage
None

Measurement Point
None

Unit
Time

18-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.106 C901120136 Rach Level Grade3 (-69 to -74 dBm) Sample

Description
This counter counts the number of signal request samples with the level grade as 3 (-69 to -74 dBm) received from the RACH/EGPRS channel by the BTS.

Usage
None

Measurement Point
None

Unit
Time

18.107 C901120137 Rach Level Grade4 (-75 to -80 dBm) Sample

Description
This counter counts the number of signal request samples with the level grade as 4 (-75 to -80 dBm) received from the RACH/EGPRS channel by the BTS.

Usage
None

Measurement Point
None

Unit
Time

18-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

18.108 C901120138 Rach Level Grade5 (-81 to -86 dBm) Sample

Description
This counter counts the number of signal request samples with the level grade as 5 (-81 to -86 dBm) received from the RACH/EGPRS channel by the BTS.

Usage
None

Measurement Point
None

Unit
Time

18.109 C901120139 Rach Level Grade6 (-87 to -92 dBm) Sample

Description
This counter counts the number of signal request samples with the level grade as 6 (-87 to -92 dBm) received from the RACH/EGPRS channel by the BTS.

Usage
None

Measurement Point
None

Unit
Time

18-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.110 C901120140 Rach Level Grade7 (-93 to -98 dBm) Sample

Description
This counter counts the number of signal request samples with the level grade as 7 (-93 to -98 dBm) received from the RACH/EGPRS channel by the BTS.

Usage
None

Measurement Point
None

Unit
Time

18.111 C901120141 Rach Level Grade8 (-99 to -104 dBm) Sample

Description
This counter counts the number of signal request samples with the level grade as 8 (-99 to -104 dBm) received from the RACH/EGPRS channel by the BTS.

Usage
None

Measurement Point
None

Unit
Time

18-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

18.112 C901120142 Rach Level Grade9 (Below -104 dBm) Sample

Description
This counter counts the number of signal request samples with the level grade as 9 (below -104 dBm) received from the RACH/EGPRS channel by the BTS.

Usage
None

Measurement Point
None

Unit
Time

18.113 C901120143 Number of Sample With Interference Band

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database, and counts and accumulates the numbers of the TCH/F, TCH/H, and SDCCH channels in each interference band in the cell. In this case, this counter increases by 1.

Usage
None

Measurement Point
The measurement point is shown in Figure 18-33.

18-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

Figure 18-33 Flowchart of Interference Band Update

Unit
None

18.114 C901120144 Number of Idle TCH/F With Interference Band 0

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/F channel with the interference band as 0.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18.115 C901120145 Number of Idle TCH/F With Interference Band 1

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/F channel with the interference band as 1.
18-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18.116 C901120146 Number of Idle TCH/F With Interference Band 2

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/F channel with the interference band as 2.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18.117 C901120147 Number of Idle TCH/F With Interference Band 3

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/F channel with the interference band as 3.

Usage
None

18-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18.118 C901120148 Number of Idle TCH/F With Interference Band 4

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/F channel with the interference band as 4.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18.119 C901120149 Number of Idle TCH/F With Interference Band 5

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/F channel with the interference band as 5.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

18-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
None

18.120 C901120150 Number of Idle TCH/H With Interference Band 0

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 0.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18.121 C901120151 Number of Idle TCH/H With Interference Band 1

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 1.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.122 C901120152 Number of Idle TCH/H With Interference Band 2

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 2.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18.123 C901120153 Number of Idle TCH/H With Interference Band 3

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 3.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

18.124 C901120154 Number of Idle TCH/H With Interference Band 4

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 4.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18.125 C901120155 Number of Idle TCH/H With Interference Band 5

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 5.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.126 C901120156 Number of Idle SDCCH With Interference Band 0

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle SDCCH channel with the interference band as 0.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18.127 C901120157 Number of Idle SDCCH With Interference Band 1

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle SDCCH channel with the interference band as 1.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

18.128 C901120158 Number of Idle SDCCH With Interference Band 2

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle SDCCH channel with the interference band as 2.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18.129 C901120159 Number of Idle SDCCH With Interference Band 3

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle SDCCH channel with the interference band as 3.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 18 Radio Measurement

18.130 C901120160 Number of Idle SDCCH With Interference Band 4

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle SDCCH channel with the interference band as 4.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18.131 C901120161 Number of Idle SDCCH With Interference Band 5

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle SDCCH channel with the interference band as 5.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

18-77 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

18-78 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19

Sub Cell Statistics

Table of Contents
Overview ..................................................................................................................19-6 C901130001 Number of available TCH/Fs in the second sub cell .............................19-6 C901130002 Number of unavailable TCH/Fs in the second sub cell .........................19-7 C901130003 Number of available TCH/Hs in the second sub cell.............................19-7 C901130004 Number of unavailable TCH/Hs in the second sub cell.........................19-8 C901130005 Number of handover attempts from the first sub cell to the second sub cell.....................................................................................................................19-9 C901130006 Number of handover execution from the first sub cell to the second sub cell...................................................................................................................19-10 C901130007 Number of handover success from the first sub cell to the second sub cell ......................................................................................................................... 19-11 C901130008 Number of handover attempts from the second sub cell to the first sub cell...................................................................................................................19-12 C901130009 Number of handover execution from the second sub cell to the first sub cell...................................................................................................................19-13 C901130010 Number of handover success from the second sub cell to the first sub cell .........................................................................................................................19-14 C901130011 Number of handover attempts in the second sub cell .........................19-15 C901130012 Number of handover execution in the second sub cell .......................19-16 C901130013 Number of handover success in the second sub cell..........................19-17 C901130014 Number of outgoing inter-cell handover attempts of the second sub cell .........................................................................................................................19-18 C901130015 Number of outgoing inter-cell handover execution of the second sub cell .........................................................................................................................19-19 C901130016 Number of outgoing inter-cell handover success of the second sub cell .........................................................................................................................19-20 C901130017 Handover attempts due to UL receiving strength of the full rate second sub cell ......................................................................................................19-21 C901130018 Handover attempts due to DL receiving strength of the full rate second sub cell ......................................................................................................19-22 C901130019 Handover attempts due to UL quality of the full rate second sub cell..19-23 C901130020 Handover attempts due to DL quality of the full rate second sub cell..19-24 C901130021 Handover attempts due to PBGT of the full rate second sub cell........19-25 C901130022 Handover attempts due to traffic of the full rate second sub cell.........19-26 C901130023 Handover attempts due to UL interference of the full rate second sub cell (on TCH/F).......................................................................................................19-27

19-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901130024 Handover attempts due to DL interference of the full rate second sub cell (on TCH/F).......................................................................................................19-28 C901130025 Handover attempts due to good CI of the full rate second sub cell (on TCH/F) ...................................................................................................................19-29 C901130026 Handover attempts due to bad CI of the full rate second sub cell (on TCH/F) ...................................................................................................................19-30 C901130027 Handover attempts due to path loss and too large TA of the full rate second sub cell (on TCH/F) ....................................................................................19-31 C901130028 Handover attempts due to path loss and too small TA of the full rate second sub cell (on TCH/F) ....................................................................................19-32 C901130029 Number of forced transfer handover attempts of the full rate second sub cell (on TCH/F) ................................................................................................19-33 C901130030 Handover attempts due to other causes of the full rate second sub cell .........................................................................................................................19-34 C901130031 Handover attempts due to UL receiving strength of the half rate second sub cell ......................................................................................................19-35 C901130032 Handover attempts due to DL receiving strength of the half rate second sub cell ......................................................................................................19-36 C901130033 Handover attempts due to UL quality of the half rate second sub cell .19-37 C901130034 Handover attempts due to DL quality of the half rate second sub cell .19-38 C901130035 Handover attempts due to PBGT of the half rate second sub cell.......19-39 C901130036 Handover attempts due to traffic of the half rate second sub cell........19-40 C901130037 Handover attempts due to UL interference of the half rate second sub cell .........................................................................................................................19-41 C901130038 Handover attempts due to DL interference of the half rate second sub cell .........................................................................................................................19-42 C901130039 Handover attempts due to C/I of the half rate second sub cell............19-43 C901130040 Handover attempts due to C/I of the half rate second sub cell............19-44 C901130041 Handover attempts due to path loss and too large TA of the half rate second sub cell ......................................................................................................19-45 C901130042 Handover attempts due to path loss and too small TA of the half rate second sub cell ......................................................................................................19-46 C901130043 Number of forced transfer handover attempts of the half rate second sub cell...................................................................................................................19-47 C901130044 Handover attempts due to other causes of the half rate second sub cell .........................................................................................................................19-48 C901130045 Number of attempts of TCH/F seizure of the second sub cell (used for assignment) ...........................................................................................................19-49 C901130046 Number of TCH/F seizure success of the second sub cell (used for assignment) ...........................................................................................................19-50 C901130047 Number of TCH/F seizure failure of the second sub cell (used for assignment) ...........................................................................................................19-51 C901130048 Number of attempts of TCH/F seizure of the second sub cell (used for handover)...............................................................................................................19-52

19-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

C901130049 Number of TCH/F seizure success of the second sub cell (used for handover)...............................................................................................................19-53 C901130050 Number of TCH/F seizure failure of the second sub cell (used for handover)...............................................................................................................19-54 C901130051 Number of TCH/H seizure attempts of the second sub cell (used for assignment) ...........................................................................................................19-55 C901130052 Number of TCH/H seizure success of the second sub cell (used for assignment) ...........................................................................................................19-56 C901130053 Number of TCH/H seizure failure of the second sub cell (used for assignment) ...........................................................................................................19-56 C901130054 Number of TCH/H seizure attempts of the second sub cell (used for handover)...............................................................................................................19-57 C901130055 Number of TCH/H seizure success of the second sub cell (used for handover)...............................................................................................................19-58 C901130056 Number of TCH/H seizure failure of the second sub cell (used for handover)...............................................................................................................19-59 C901130057 Number of TCH/F call drops in the second sub cell............................19-60 C901130058 Number of TCH/H call drops in the second sub cell ...........................19-61 C901130059 TCH/F busy time in the second sub cell .............................................19-61 C901130060 TCH/H busy time in the second sub cell ............................................19-62 C901130061 Number of TCH/F assignment attempts of the second sub cell ..........19-63 C901130062 Number of TCH/F assignment success of the second sub cell...........19-64 C901130063 Number of TCH/F handover attempts of the second sub cell .............19-64 C901130064 Number of TCH/F handover success of the second sub cell ..............19-65 C901130065 Number of TCH/H assignment attempts of the second sub cell..........19-66 C901130066 Number of TCH/H assignment success of the second sub cell ..........19-67 C901130067 Number of TCH/H handover attempts of the second sub cell .............19-68 C901130068 Number of TCH/H handover success of the second sub cell..............19-69 C901130069 TCH/F of the first sub cell seizure success when prefer the second sub cell (used for assignment)................................................................................19-69 C901130070 TCH/F of the first sub cell seizure success when prefer the second sub cell (used for handover) ...................................................................................19-70 C901130071 TCH/H of the first sub cell seizure success when prefer the second sub cell (used for assignment)................................................................................19-71 C901130072 TCH/H of the first sub cell seizure success when prefer the second sub cell (used for handover) ...................................................................................19-71 C901130073 Number of Inter-Cell Handover Attempts to the Second Sub Cell Directly From the Cell in the Same Site ..................................................................19-72 C901130074 Number of Inter-Cell Handover Execution to the Second Sub Cell Directly From the Cell in the Same Site ..................................................................19-73 C901130075 Number of Inter-Cell Handover Success to the Second Sub Cell Directly From the Cell in the Same Site ..................................................................19-73 C901130076 Number of Inter-Cell Handover Attempts to the Second Sub Cell Directly From Another Site .....................................................................................19-74

19-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901130077 Number of Inter-Cell Handover Execution to the Second Sub Cell Directly From Another Site .....................................................................................19-74 C901130078 Number of Inter-Cell Handover Success to the Second Sub Cell Directly From Another Site .....................................................................................19-75 C901130079 Number of Handover Attempts to the Second Sub Cell Directly From Another BSC ..........................................................................................................19-75 C901130080 Number of Handover Execution to the Second Sub Cell Directly From Another BSC ..........................................................................................................19-76 C901130081 Number of Handover Success to the Second Sub Cell Directly From Another BSC ..........................................................................................................19-76 C901130082 Number of Handover to the First Sub Cell Too Fast After Handover From Another Cell in the Same Site .......................................................................19-77 C901130083 Number of Handover to the Second Sub Cell Too Fast After Handover From Another Cell in the Same Site .......................................................................19-77 C901130084 Number of Handover to the First Sub Cell Too Fast After Handover From Another Site ..................................................................................................19-78 C901130085 Number of Handover to the Second Sub Cell Too Fast After Handover From Another Site ..................................................................................................19-78 C901130086 Sample of Subcell 2 Level Low 30dB or Below Than BCCH ..............19-79 C901130087 Sample of Subcell 2 Level Low 29 dB Than BCCH ............................19-79 C901130088 Sample of Subcell 2 Level Low 28 dB Than BCCH ............................19-80 C901130089 Sample of Subcell 2 Level Low 27 dB Than BCCH ............................19-80 C901130090 Sample of Subcell 2 Level Low 26 dB Than BCCH ............................19-81 C901130091 Sample of Subcell 2 Level Low 25 dB Than BCCH ............................19-81 C901130092 Sample of Subcell 2 Level Low 24 dB Than BCCH ............................19-82 C901130093 Sample of Subcell 2 Level Low 23 dB Than BCCH ............................19-82 C901130094 Sample of Subcell 2 Level Low 22 dB Than BCCH ............................19-83 C901130095 Sample of Subcell 2 Level Low 21 dB Than BCCH ............................19-83 C901130096 Sample of Subcell 2 Level Low 20 dB Than BCCH ............................19-84 C901130097 Sample of Subcell 2 Level Low 19 dB Than BCCH ............................19-84 C901130098 Sample of Subcell 2 Level Low 18 dB Than BCCH ............................19-85 C901130099 Sample of Subcell 2 Level Low 17 dB Than BCCH ............................19-85 C901130100 Sample of Subcell 2 Level Low 16 dB Than BCCH ............................19-86 C901130101 Sample of Subcell 2 Level Low 15 dB Than BCCH ............................19-86 C901130102 Sample of Subcell 2 Level Low 14 dB Than BCCH ............................19-87 C901130103 Sample of Subcell 2 Level Low 13 dB Than BCCH ............................19-87 C901130104 Sample of Subcell 2 Level Low 12 dB Than BCCH ............................19-88 C901130105 Sample of Subcell 2 Level Low 11 dB Than BCCH ............................19-88 C901130106 Sample of Subcell 2 Level Low 10 dB Than BCCH ............................19-89 C901130107 Sample of Subcell 2 Level Low 9 dB Than BCCH ..............................19-89 C901130108 Sample of Subcell 2 Level Low 8 dB Than BCCH ..............................19-90 C901130109 Sample of Subcell 2 Level Low 7 dB Than BCCH ..............................19-90 C901130110 Sample of Subcell 2 Level Low 6 dB Than BCCH ..............................19-91 C901130111 Sample of Subcell 2 Level Low 5 dB Than BCCH ..............................19-91 C901130112 Sample of Subcell 2 Level Low 4 dB Than BCCH ..............................19-92
19-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

C901130113 Sample of Subcell 2 Level Low 3 dB Than BCCH ..............................19-92 C901130114 Sample of Subcell 2 Level Low 2 dB Than BCCH ..............................19-93 C901130115 Sample of Subcell 2 Level Low 1 dB Than BCCH ..............................19-93 C901130116 Sample of Subcell 2 Level Equal BCCH.............................................19-94 C901130117 Sample of Subcell 2 Level High 1 dB Than BCCH .............................19-94 C901130118 Sample of Subcell 2 Level High 2 dB Than BCCH .............................19-95 C901130119 Sample of Subcell 2 Level High 3 dB Than BCCH .............................19-95 C901130120 Sample of Subcell 2 Level High 4 dB Than BCCH .............................19-96 C901130121 Sample of Subcell 2 Level High 5 dB Than BCCH .............................19-96 C901130122 Sample of Subcell 2 Level High 6 dB Than BCCH .............................19-97 C901130123 Sample of Subcell 2 Level High 7 dB Than BCCH .............................19-97 C901130124 Sample of Subcell 2 Level High 8 dB Than BCCH .............................19-98 C901130125 Sample of Subcell 2 Level High 9 dB Than BCCH .............................19-98 C901130126 Sample of Subcell 2 Level High 10 dB Than BCCH ...........................19-99 C901130127 Sample of Subcell 2 Level High 11 dB Than BCCH ...........................19-99 C901130128 Sample of Subcell 2 Level High 12 dB Than BCCH .........................19-100 C901130129 Sample of Subcell 2 Level High 13 dB Than BCCH .........................19-100 C901130130 Sample of Subcell 2 Level High 14 dB Than BCCH .........................19-101 C901130131 Sample of Subcell 2 Level High 15 dB Than BCCH .........................19-101 C901130132 Sample of Level Difference Between Subcell 2 and BCCH ..............19-102 C901130133 Sum of Level Difference Between Subcell 2 and BCCH...................19-102 C901130134 Lowest of Level Difference Between Subcell 2 and BCCH ...............19-103 C901130135 Highest of Level Difference Between Subcell 2 and BCCH ..............19-103 C901130136 Number of handover attempt from FR to HR(V3) due to high load in Subcell2 ...............................................................................................................19-104 C901130137 Number of handover from FR to HR(V3) due to high load in Subcell2 ...............................................................................................................19-105 C901130138 Number of handover success from FR to HR(V3) due to high load in Subcell2 ...............................................................................................................19-105 C901130139 Number of handover attempt from FR to HR(V1) due to high load in Subcell2 ...............................................................................................................19-106 C901130140 Number of handover from FR to HR(V1) due to high load in Subcell2 ...............................................................................................................19-106 C901130141 Number of handover success from FR to HR(V1) due to high load in Subcell2 ...............................................................................................................19-107 C901130142 Number of handover attempt from HR(V3) to FR due to bad quality in Subcell2 ...............................................................................................................19-107 C901130143 Number of handover from HR(V3) to FR due to bad quality in Subcell2 ...............................................................................................................19-108 C901130144 Number of handover success from HR(V3) to FR due to bad quality in Subcell2 ...............................................................................................................19-108 C901130145 Number of handover attempt from HR(V1) to FR due to bad quality in Subcell2 ...............................................................................................................19-109 C901130146 Number of handover from HR(V1) to FR due to bad quality in Subcell2 ............................................................................................................... 19-110
19-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901130147 Number of handover success from HR(V1) to FR due to bad quality in Subcell2 ............................................................................................................... 19-110 C901130150 Number of Handover Attempt From FR to HR (V1) Due to High Load in Subcell 2 .......................................................................................................... 19-111 C901130151 Number of Handover From FR to HR (V1) Due to High Load in Subcell 2 .............................................................................................................. 19-111 C901130152 Number of Handover Success From FR to HR (V1) Due to High Load in Subcell 2 .......................................................................................................... 19-112 C901130153 Number of Handover Attempt From FR to HR (V3) Due to High Load in Subcell 2 .......................................................................................................... 19-112 C901130154 Number of Handover From FR to HR (V3) Due to High Load in Subcell 2 .............................................................................................................. 19-113 C901130155 Number of Handover Success From FR to HR (V3) Due to High Load in Subcell 2 .......................................................................................................... 19-113

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.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
19-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec 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 cell, to learn the traffic of the second sub cell.

Measurement Point
Call database interface to count promptly.

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-05-02-009 Concentric Circle Technology

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.

19-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of available TCH/H 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-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-05-02-009 Concentric Circle Technology

19.5 C901130004 Number of unavailable TCH/Hs in the second sub cell

Definition
Number of unavailable TCH/Hs in the second sub cell

Description
This counter counts the number of unavailable TCH/H channels in the second sub cell.

Usage
This counter is used to find out the number of available TCH/H 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-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-05-02-009 Concentric Circle Technology
19-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.6 C901130005 Number of handover attempts from the first sub cell to the second sub cell
Definition
Number of handover attempts from the first sub cell to the second sub cell

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 .
Figure 19-1 - Intra-Cell Handover Attempt

Unit
Times

Related Features
ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.7 C901130006 Number of handover execution from the first sub cell to the second sub cell
Definition
Number of handover execution from the first sub cell to the second sub cell

Description
This counter counts the number of intra-cell handover execution 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 sub cell to the second sub cell, as one of the parameters to measure radio environment.

Measurement Point
During inter-sub-cell handover within a cell, this counter increments when following conditions are met: l l l The channel of target sub cell is successfully activated Current channel is in the second sub cell Source channel is in the first sub cell

The measurement point is A, as shown in Figure 19-2.

Figure 19-2 - Intra-Cell Incoming Handover

Unit
Times

Related Features
ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.8 C901130007 Number of handover success from the first sub cell to the second sub cell
Definition
Number of handover success from the first sub cell to the second sub cell

Description
This counter counts the number of intra-cell handover success 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 sub cell to the second sub cell, as one of the parameters to measure radio environment.

Measurement Point
During inter-sub-cell handover within a cell, target sub cell will receive handover completion message, indicating that MS successfully accesses to new channel. If target channel is in the second sub cell, and source channel is in the first sub cell, this counter increments. The measurement point is A, as shownFigure 19-3 .
Figure 19-3 - Successful Intra-Cell Handover

Unit
Times

Related Features
ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.9 C901130008 Number of handover attempts from the second sub cell to the first sub cell
Definition
Number of handover attempts from the second sub cell to the first sub cell

Description
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. The measurement point is A, as shown in Figure 19-4.
Figure 19-4 - Intra-Cell Handover Attempt

Unit
Times

Related Features
ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.10 C901130009 Number of handover execution from the second sub cell to the first sub cell
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 to the first sub cell.

Usage
This counter is used to find out the frequency of intra-cell handover execution from the second sub cell to the first sub cell, as one of the parameters to measure radio environment.

Measurement Point
During inter-sub-cell handover within a cell, this counter increments when following conditions are met: l l l The channel of target sub cell is successfully activated Current channel is in the second sub cell Source channel is in the first sub cell

The measurement point is A, as shown in Figure 19-5.

Figure 19-5 - Intra-Cell Incoming Handover

Unit
Times

Related Features
ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.11 C901130010 Number of handover success from the second sub cell to the first sub cell
Definition
Number of handover success from the second sub cell to the first sub cell

Description
This counter counts the number of intra-cell successful handover from the second sub cell to the first sub cell.

Usage
This counter is used to find out the frequency of intra-cell handover ins success from the second sub cell to the first sub cell, as one of the parameters to measure radio environment.

Measurement Point
During inter-sub-cell handover within a cell, this counter increments when following conditions are met: l l l Target sub cell receives handover completion message Target channel is in the first sub cell Source channel is in the second sub cell

The measurement point is A, as shown in Figure 19-6.

Figure 19-6 - Successful Intra-Cell Handover

Unit
Times

Related Features
ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology
19-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

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
When BSC receives measurement reports from MS, it makes handover decision. If it is decided to do intra-cell handover, and current sub cell is the second sub cell, and if handover reason is interference handover, this counter increments. The measurement point is A, as shown inFigure 19-7.
Figure 19-7 - Intra-Cell Handover Attempt

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

19-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
During inter-sub-cell handover within a cell, this counter increments when following conditions are met: l l l l The channel of target sub cell is successfully activated The channel of target sub cell is successfully activated Current channel is in the first sub cell Source channel is in the second sub cell

The measurement point is A, as shown in Figure 19-8.

Figure 19-8 - Intra-Cell Incoming Handover

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

19-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

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
During inter-sub-cell handover within a cell, this counter increments when following conditions are met: l l l Target sub cell receives handover completion message Target channel is in the second sub cell Source channel is in the first sub cells

The measurement point is A, as shown in Figure 19-9.

Figure 19-9 - Successful Intra-Cell Handover

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

19-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
When BSC receives measurement reports from MS, it makes handover decision. If it is decided to do inter-cell handover, and source cell is the second sub cell, this counter increments. The measurement point is A, as shown in Figure 19-10.
Figure 19-10 - Intra-Cell Handover Attempt

Unit
Times

Related Features
ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.16 C901130015 Number of outgoing inter-cell 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 from the second sub cell, as one of the parameters to measure radio environment.

Measurement Point
During inter-sub-cell handover within a cell, source instance receives the handover completion message returned from target instance, indicating the MS has accessed to target channel. If source sub cell is the second sub cell, this counter increments. The measurement point is A, as shown in Figure 19-11.
Figure 19-11 - Inter-Cell Handover Execution

Unit
Times

Related Features
ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.17 C901130016 Number of outgoing inter-cell 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 from the second sub cell, as one of the parameters to measure radio environment.

Measurement Point
During inter-sub-cell handover within a cell, source instance receives the handover completion message returned from target instance, indicating the MS has accessed to target channel. If source sub cell is the second sub cell, this counter increments. The measurement point is A, as shown in Figure 19-12.
Figure 19-12 - Successful Intra-Cell Handover

Usage
Times

Related Features
ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

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. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by UL strength Current channel is full rate one This counter

The measurement point is A, as shown in .

Figure 19-13 - Handover Decision

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

19-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 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. increments when following conditions are met: l l l l Decision is made Handover is caused by DL strength Source sub cell is the second sub cell Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-14.

Figure 19-14 - Handover Decision

Usage
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

19-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

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
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Handover is caused by UL quality Source sub cell is the second sub cell Current channel is full rate one This counter

The measurement point is A, as shown inFigure 19-15 .

Figure 19-15 - Handover Decision

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

19-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 originated from full rate channel in the second sub cell.

Usage
This counter is used to find out the frequency of handover attempts, caused by DL quality and originated from full rate channel 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. increments when following conditions are met: l l l l Decision is made Handover is caused by DL quality Source sub cell is the second sub cell Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-16.

Figure 19-16 - Handover Decision

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

19-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

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
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Handover is caused by PBGT Source sub cell is the second sub cell Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-17.

Figure 19-17 - Handover Decision

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

19-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Handover is caused by traffic Source sub cell is the second sub cell Current channel is full rate one, this counter increments This counter

The measurement point is A, as shown in Figure 19-18.

Figure 19-18 - Handover Decision

Units
Times

Related Features
ZGO-02-02-007 Traffic Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing ZGO-05-02-009 Concentric Circle Technology
19-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.24 C901130023 Handover attempts due to UL interference of the full rate second sub cell (on TCH/F)
Definition
Handover attempts due to UL interference of the full rate second sub cell (on TCH/F)

Description
This counter counts the number of handover attempts, caused by UL interference and originated from full rate channel in the second sub cell.

Usage
This counter is used to find out the frequency of handover attempts, caused by UL interference and originated from full rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Handover is caused by traffic Source sub cell is the second sub cell Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-19.

Figure 19-19 - Handover Decision

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
19-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ZGO-05-02-009 Concentric Circle Technology

19.25 C901130024 Handover attempts due to DL 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 originated from full rate channel in the second sub cell.

Usage
This counter is used to find out the frequency of handover attempts, caused by DL interference and originated from full rate 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. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by DL interference Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-20.

Figure 19-20 - Handover Decision

Unit
Times

19-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-05-02-009 Concentric Circle Technology

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 originated from full rate channel in the second sub cell.

Usage
This counter is used to find out the frequency of handover attempts, caused by too good C/I and originated from full rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by too good C/I Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-21.

Figure 19-21 - Handover Decision

Unit
Times
19-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-05-02-009 Concentric Circle Technology

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 originated from full rate channel in the second sub cell.

Usage
This counter is used to find out the frequency of handover attempts, caused by too bad C/I and originated from full rate channel 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. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by too bad C/I Current channel is full rate one This counter

The measurement point is A, as shown inFigure 19-22.

Figure 19-22 - Handover Decision

Unit
Times
19-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-05-02-009 Concentric Circle Technology

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 references for radio environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Handover is caused by too large path loss and TA Source sub cell is the second sub cell Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-23.

Figure 19-23 - Handover Decision

19-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19.29 C901130028 Handover attempts due to path loss 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.

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 references for radio environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by too small path loss and TA Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-24.

19-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Figure 19-24 - Handover Decision

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

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)

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 the references for radio environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by forced transfer Current channel is full rate one
19-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

This counter

ZXG10 iBSC Performance Counter Reference

The measurement point is A, as shown inFigure 19-25.

Figure 19-25 - Handover Decision

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-02-02-003 Directed-Shift Handover ZGO-05-02-009 Concentric Circle Technology

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 for radio environment 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. increments when following conditions are met: l l Decision is made Source sub cell is the second sub cell
19-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

This counter

Chapter 19 Sub Cell Statistics

l l

Handover is caused by other reasons Current channel is full rate one

The measurement point is A, as shown inFigure 19-26.

Figure 19-26 - Handover Decision

Unit
Times

Related Features
ZGO-02-02-001 Handover between Macro- and Micro-cells ZGO-02-02-006 Rapid Level Drop Handover ZGO-02-02-015 Enhanced Cell Reselection Procedure ZGO-05-02-009 Concentric Circle Technology

19.32 C901130031 Handover attempts due to UL receiving strength of the half rate second sub cell
Definition
Handover attempts due to UL receiving strength of the half rate second sub cell

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

19-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by UL strength Current channel is half rate one This counter

The measurement point is A, as shown inFigure 19-27 .

Figure 19-27 - Handover Decision

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

19.33 C901130032 Handover attempts due to DL receiving strength of the half rate second sub cell
Definition
Handover attempts due to DL receiving strength of the half rate second sub cell

Description
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
This counter is used to find out the frequency of handover attempts, caused by DL receiving strength and originated from half rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.

19-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by DL strength Current channel is half rate one This counter

The measurement point is A, as shown in Figure 19-28.

Figure 19-28 - Handover Decision

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

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 radio environment in the second sub cell.

19-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by UL quality Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-29.

Figure 19-29 - Handover Decision

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

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 and originated from full rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.

19-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by DL quality Current channel is half rate one This counter

The measurement point is A, as shown in Figure 19-30.

Figure 19-30 - Handover Decision

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

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 environment in the second sub cell.

19-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by PBGT Current channel is half rate one This counter

The measurement point is A, as shown in Figure 19-31.

Figure 19-31 - Handover Decision

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

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 environment in the second sub cell.

19-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by traffic Current channel is half rate one This counter

The measurement point is A, as shown in Figure 19-32.

Figure 19-32 - Handover Decision

Unit
Times

Related Features
ZGO-02-02-007 Traffic Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing ZGO-05-02-009 Concentric Circle Technology

19.38 C901130037 Handover attempts due to UL interference of the half rate second sub cell
Definition
Handover attempts due to UL interference of the half rate second sub cell

Description
This counter counts the number of handover attempts, caused by UL interference and originated from half rate channel in the second sub cell.

19-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of handover attempts, caused by UL interference and originated from half rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by UL interference Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-33.

Figure 19-33 - Handover Decision

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

19.39 C901130038 Handover attempts due to DL 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 originated from half rate channel in the second sub cell.

19-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Usage
This counter is used to find out the frequency of handover attempts, caused by DL interference and originated from half rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by DL interference Current channel is half rate one This counter

The measurement point is A, as shown in Figure 19-34.

Figure 19-34 - Handover Decision

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

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 originated from half rate channel in the second sub cell.

19-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of handover attempts, caused by too good C/I and originated from half rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by too good C/I Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-35

Figure 19-35 - Handover Decision

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

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 originated from half rate channel in the second sub cell.

19-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Usage
This counter is used to find out the frequency of handover attempts, caused by too bad C/I and originated from half rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by too bad C/I Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-36.

Figure 19-36 - Handover Decision

Unit
Times

Related Features
ZGO-05-02-009 Concentric Circle Technology

19.42 C901130041 Handover attempts due to path loss 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.
19-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of handover attempts, caused by too large path loss and TA and originated from half rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by too large path loss and TA Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-37.

Figure 19-37 - Handover Decision

Unit
Times

Related Features
ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19.43 C901130042 Handover attempts due to path loss 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.
19-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

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 the references for radio environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by too small path loss and TA Current channel is full rate one This counter

The measurement point is A, as shown in Figure 19-38.

Figure 19-38 - Handover Decision

Unit
Times

Related Features
ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

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.
19-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 the references for radio environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by forced transfer Current channel is half rate one This counter

The measurement point is A, as shown in Figure 19-39.

Figure 19-39 - Handover Decision

Unit
Times

Related Features
ZGO-02-02-003 Directed-Shift Handover ZGO-05-02-009 Concentric Circle Technology

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 originated from half rate channel in the second sub cell.
19-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Usage
This counter is used to find out the frequency of handover attempts, caused by other causes and originated from half rate channel in the second sub cell, as one of the references for radio environment in the second sub cell.

Measurement Point
Make handover decision after BSC receives measurement reports. increments when following conditions are met: l l l l Decision is made Source sub cell is the second sub cell Handover is caused by other reasons Current channel is half rate one This counter

The measurement point is A, as shown in Figure 19-40.

Figure 19-40 - Handover Decision

Unit
Times

Related Features
ZGO-02-02-001 Handover between Macro- and Micro-cells ZGO-02-02-006 Rapid Level Drop Handover ZGO-02-02-015 Enhanced Cell Reselection Procedure ZGO-05-02-009 Concentric Circle Technology

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

19-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

When channel application is failed, if channel type is TCH/F, and application reason is assignment, this counter increments. Failure reasons of application channel include:

Receive release command while waiting for resource state Failed to configure instance number while seizing channel Timeout while queuing or seizure, or waiting for resource timer No available radio resource

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation ZGO-05-02-009 Concentric Circle Technology

19.47 C901130046 Number of TCH/F seizure success of the second sub cell (used for assignment)
Definition
Number of TCH/F seizure success of the second sub cell (used for assignment)

19-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

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 l l Successfully applying for channel Channel type is TCH/F Application reason is assignment

Successful application includes: successful resource application; resource acquisition by queuing, seizure, or dynamic channel conversion.

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation ZGO-05-02-009 Concentric Circle Technology

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 second sub cell, as one of the references for radio environment in the second sub cell.

19-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
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: l l l l 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
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation ZGO-05-02-009 Concentric Circle Technology

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.

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 channel is successfully applied, if channel type is TCH/F, and application reason is handover, this counter increments. Successful application includes: successful resource application; resource acquisition by queuing, seizure, or dynamic channel conversion. When channel application is failed, if channel type is TCH/F, 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;
19-52

SJ-20110531095035-015|2013-04-25 (R1.7)

ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

No available radio resource.

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

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.

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 l l Channel is successfully applied Channel type is TCH/F Application reason is handover

Successful application includes: successful resource application; resource acquisition by queuing, seizure, or dynamic channel conversion.

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
19-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ZGO-03-02-002 Enhancement on Channel Allocation ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

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
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 second sub cell, as one of the references for radio environment in the second sub cell.

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: l l l l 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

Successful application includes: successful resource application; resource acquisition by queuing, seizure, or dynamic channel conversion.

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.52 C901130051 Number of TCH/H seizure attempts of the second sub cell (used for assignment)
Definition
Number of TCH/H seizure attempts of the second sub cell (used for assignment)

Description
This counter counts the number of seizure attempts in TCH/H 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 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 channel is successfully applied, 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. 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:

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
ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-05-02-009 Concentric Circle Technology

19-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.53 C901130052 Number of TCH/H seizure success of the second sub cell (used for assignment)
Definition
Number of TCH/H seizure success of the second sub cell (used for assignment)

Description
This counter counts the number of successful seizure in TCH/H channel in the second sub cell.

Usage
This counter is used to find out the frequency of successful seizure in TCH/H channel in the second sub cell, as one of the references for radio environment in the second sub cell.

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
ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-05-02-009 Concentric Circle Technology

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
This counter counts the number of seizure failure in TCH/F channel in the second sub cell.
19-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Usage
This counter is used to find out the frequency of seizure failure in TCH/H channel in the second sub cell, as one of the references for radio environment in the second sub cell.

Measurement Point
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: l l l l 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
ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-05-02-009 Concentric Circle Technology

19.55 C901130054 Number of TCH/H seizure attempts of the second sub cell (used for handover)
Definition
Number of TCH/H seizure attempts of the second sub cell (used for handover)

Description
This counter counts the number of seizure attempts in TCH/H 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 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 channel is successfully applied, if channel type is TCH/H, and application reason is handover, this counter increments. Successful application includes:
19-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

successful resource application; resource acquisition by queuing, seizure, or dynamic channel conversion. 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:

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
ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19.56 C901130055 Number of TCH/H seizure success of the second sub cell (used for handover)
Definition
Number of TCH/H seizure success of the second sub cell (used for handover)

Description
This counter counts the number of successful seizure in TCH/H channel in the second sub cell.

Usage
This counter is used to find out the frequency of successful seizure in TCH/H channel in the second sub cell, as one of the references for radio environment in the second sub cell.

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.
19-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

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.

Usage
This counter is used to find out the frequency of seizure failure in TCH/H channel in the second sub cell, as one of the references for radio environment in the second sub cell.

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: l l l l 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
ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation
19-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

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: l l l l After handover and deliver assignment command in cell, call drops occur due to 3107 timer timeout After inter-cell handover delivers handover command, call drops occur due to 3103 timer timeout After handover and deliver external handover command, call drops occur due to outgoing protection timer timeout BSC receives radio link failure message

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

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 l l l After handover and deliver assignment command in cell, call drops occur due to 3107 timer timeout After inter-cell handover delivers handover command, call drops occur due to 3103 timer timeout After handover and deliver external handover command, call drops occur due to outgoing protection timer timeout BSC receives radio link failure message

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

19.60 C901130059 TCH/F busy time in the second sub cell

Definition
TCH/F busy time in the second sub cell
19-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. When promptly report measurement data.

Unit
Times

Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

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:
19-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

When seize or release TCH/F channel within a cell. Seizure channel means successful application of radio resource for database. Channel release means two cases: instance release caused by different reasons and release while waiting resource timer timeout. When promptly report measurement data.

Unit
Times

Related Features
ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology

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 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, then the counter counts. 2. When BSC receives the Um interface assignment completion message in the WaitAccess status, if the sub cell ID is 2, the channel is full-rate channel, and the channel request is due to assignment, then the counter counts. 3. When BSC receives the handover completion message in the WaitAccess status, if the sub cell ID is 2, the channel is full-rate channel, and the channel request is due to assignment, then the counter counts.
19-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 assignment, then the counter counts.

Unit
Times

19.63 C901130062 Number of TCH/F assignment success of the second sub cell
Description
This counter counts the number of successful TCH/F assignments for the second sub cell. When BSC receives the release command, the Um interface assignment completion message or handover completion message, or the message of waiting for MS access being timeout, if the sub cell ID is 2, the channel is full-rate channel, and the channel request is due to assignment, then the counter increments.

Usage
This counter is used to find out the number of successful TCH/F assignments 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 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. 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 assignment, then the counter counts.

Unit
Times

19.64 C901130063 Number of TCH/F handover attempts of the second sub cell
Description
This counter counts the number of attempts of TCH/F handover of the second sub cell. In the WaitAccess status, when BSC receives the release command, the Um interface
19-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

assignment completion message or handover completion message, or the message of waiting for MS access being timeout, if the sub cell ID is 2, the channel is full-rate channel, and the channel request is due to intra-cell handover, inter-cell handover, external incoming handover, or internal directed retry, then the counter increments.

Usage
This counter is used to find out the number of attempts of TCH/F handover of the second sub cell. It helps study the access condition of the second sub cell. 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 intra-cell handover, inter-cell handover, external incoming handover, or internal directed retry, then the counter counts. 2. When BSC receives the Um interface assignment completion message in the WaitAccess status, if the sub cell ID is 2, the channel is full-rate channel, and the channel request is due to 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. 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 directed retry, then the counter counts.

Unit
Times

19.65 C901130064 Number of TCH/F handover success of the second sub cell
Description
This counter counts the number of successful TCH/F handovers of the second sub cell. When BSC receives the release command, the Um interface assignment completion message or handover completion message, or the message of waiting for MS access being timeout, if the sub cell ID is 2, the channel is full-rate channel, and the channel request is due to intra-cell handover, inter-cell handover, external incoming handover, or internal directed retry, then the counter increments.
19-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of successful TCH/F handovers of the second sub cell. It helps study the access condition of the second sub cell. This counter is supported in version V6.20.200f or above.

Measurement Point
1. 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 intra-cell handover, inter-cell handover, external incoming handover, or internal directed retry, then the counter counts. 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 intra-cell handover, inter-cell handover, external incoming handover, or internal directed retry, then the counter counts.

Unit
Times

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 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 assignment, then the counter increments.

Usage
This counter is used to find out the number of attempts of TCH/H assignment for the second sub cell. It helps study the access condition of the second sub cell. 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 half-rate channel, and the channel request is due to assignment, then the counter counts. 2. When BSC receives the Um interface assignment completion message in the WaitAccess status, if the sub cell ID is 2, the channel is half-rate channel, and the channel request is due to assignment, then the counter counts.
19-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

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 assignment, then the counter counts.

Unit
Times

19.67 C901130066 Number of TCH/H assignment success of the second sub cell
Description
This counter counts the number of successful TCH/H assignments for the second sub cell. When BSC receives the release command, the Um interface assignment completion message or handover completion message, or the message of waiting for MS access being timeout, if the sub cell ID is 2, the channel is half-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 successful TCH/H assignments 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 Um interface assignment 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. 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 assignment, then the counter counts.

Unit
Times

19-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.68 C901130067 Number of TCH/H handover attempts of the second sub cell
Description
This counter counts the number of attempts of TCH/H handover of the second sub cell. In the WaitAccess status, when BSC receives the release command, the Um interface assignment completion message or handover completion message, or the message of waiting for MS access being timeout, if the sub cell ID is 2, the channel is half-rate channel, and the channel request is due to intra-cell handover, inter-cell handover, external incoming handover, or internal directed retry, then the counter increments.

Usage
This counter is used to find out the number of attempts of TCH/H handover of the second sub cell. It helps study the access condition of the second sub cell. 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 half-rate channel, and the channel request is due to intra-cell handover, inter-cell handover, external incoming handover, or internal directed retry, then the counter counts. 2. When BSC receives the Um interface assignment 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 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 half-rate channel, and the channel request is due to intra-cell handover, inter-cell handover, external incoming handover, or internal directed retry, then the counter counts. 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 intra-cell handover, inter-cell handover, external incoming handover, or internal directed retry, then the counter counts.

Unit
Times

19-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.69 C901130068 Number of TCH/H handover success of the second sub cell
Description
This counter counts the number of successful TCH/H handovers of the second sub cell. When BSC receives the release command, the Um interface assignment completion message or handover completion message, or the message of waiting for MS access being timeout, if the sub cell ID is 2, the channel is half-rate channel, and the channel request is due to intra-cell handover, inter-cell handover, external incoming handover, or internal directed retry, then the counter increments.

Usage
This counter is used to find out the number of successful TCH/H handovers of the second sub cell. It helps study the access condition of the second sub cell. This counter is supported in version V6.20.200f or above.

Measurement Point
1. When BSC receives the Um interface assignment 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 directed retry, then the counter counts. 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 intra-cell handover, inter-cell handover, external incoming handover, or internal directed retry, then the counter counts.

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.
19-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. This counter is supported in version V6.20.200f or above.

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.71 C901130070 TCH/F of the first sub cell seizure success when prefer the second sub cell (used for handover)
Description
This counter counts the number of assigning TCH/F to the first sub cell when the second sub cell has higher priority (used for handover). When BSC requests radio resource from DBS, if the 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 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. This counter is supported in version V6.20.200f or above.

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

19-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Unit
Times

19.72 C901130071 TCH/H 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/H to the first sub cell when the second sub cell has higher priority (used for assignment). When BSC requests radio resource from DBS, if the 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 half-rate channel, and the channel request is due to assignment.

Usage
This counter is used to find out the number of assigning TCH/H to the first sub cell when the second sub cell has higher priority (used for assignment). It helps study the access condition of the first sub cell when the second sub cell has higher priority. This counter is supported in version V6.20.200f or above.

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 half-rate channel, and the channel request is due to assignment.

Unit
Times

19.73 C901130072 TCH/H of the first sub cell seizure success when prefer the second sub cell (used for handover)
Description
This counter counts the number of assigning TCH/H to the first sub cell when the second sub cell has higher priority (used for handover). When BSC requests radio resource from DBS, if the request succeeds and the following conditions are satisfied, the counter
19-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

increments: the sub cell selection mode is the second cell being preferred, the sub cell ID is 1, the channel is half-rate channel, and the channel request is due to handover.

Usage
This counter is used to find out the number of assigning TCH/H to the first sub cell when the second sub cell has higher priority (used for handover). It helps study the access condition of the first sub cell when the second sub cell has higher priority. This counter is supported in version V6.20.200f or above.

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 half-rate channel, and the channel request is due to handover.

Unit
Times

19.74 C901130073 Number of Inter-Cell Handover Attempts to the Second Sub Cell Directly From the Cell in the Same Site
Description
This counter counts the inter-cell handover attempts that occur to hand over an MS to subcell 2 of the cell from another cell in the same site.

Usage
This counter indicates the number of inter-cell handover attempts that occur to hand over an MS to subcell 2 of the cell from another cell in the same site.

Measurement Point
This counter is incremented when channel assignment in subcell 2 of the cell is determined.

Unit
Times

19-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.75 C901130074 Number of Inter-Cell Handover Execution to the Second Sub Cell Directly From the Cell in the Same Site
Description
This counter counts the times that an inter-cell handover is performed to hand over an MS to subcell 2 of the cell from another cell in the same site.

Usage
This counter indicates the number of times that an inter-cell handover is performed to hand over an MS to subcell 2 of the cell from another cell in the same site.

Measurement Point
This counter is incremented when the assigned channel in subcell 2 of the cell is activated.

Unit
Times

19.76 C901130075 Number of Inter-Cell Handover Success to the Second Sub Cell Directly From the Cell in the Same Site
Description
This counter counts successful inter-cell handovers from a cell in the same site to subcell 2 of the cell.

Usage
This counter indicates the number of successful inter-cell handovers from a cell in the same site to subcell 2 of the cell.

Measurement Point
This counter is incremented when a HANDOVER COMPLETE message is received through the assigned channel in subcell 2 of the cell.

Unit
Times

19-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.77 C901130076 Number of Inter-Cell Handover Attempts to the Second Sub Cell Directly From Another Site
Description
This counter counts the inter-cell handover attempts that occur to hand over an MS to subcell 2 of the cell from a cell in another site controlled by the same BSC.

Usage
This counter indicates the number of inter-cell handover attempts that occur to hand over an MS to subcell 2 of the cell from a cell in another site controlled by the same BSC.

Measurement Point
This counter is incremented when channel assignment in subcell 2 of the cell is determined.

Unit
Times

19.78 C901130077 Number of Inter-Cell Handover Execution to the Second Sub Cell Directly From Another Site
Description
This counter counts the times that an inter-cell handover is performed to hand over an MS from a cell in another site (controlled by the same BSC) to subcell 2 of the cell.

Usage
This counter indicates the number of inter-cell handovers that hand over an MS to subcell 2 of the cell from a cell in another site controlled by the same BSC.

Measurement Point
This counter is incremented when the assigned channel in subcell 2 of the cell is activated.

Unit
Times

19-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.79 C901130078 Number of Inter-Cell Handover Success to the Second Sub Cell Directly From Another Site
Description
This counter counts successful inter-cell handovers that hand over an MS to subcell 2 of the cell from a cell in another site controlled by the same BSC.

Usage
This counter indicates the number of successful inter-cell handovers that hand over an MS to subcell 2 of the cell from a cell in another site controlled by the same BSC.

Measurement Point
This counter is incremented when a HANDOVER COMPLETE message is received through the assigned channel in subcell 2 of the cell.

Unit
Times

19.80 C901130079 Number of Handover Attempts to the Second Sub Cell Directly From Another BSC
Description
This counter counts the inter-cell handover attempts that occur to hand over an MS to subcell 2 of the cell from a cell controlled by another BSC.

Usage
This counter indicates the number of inter-cell handover attempts that occur to hand over an MS to subcell 2 of the cell from a cell controlled by another BSC.

Measurement Point
This counter is incremented when channel assignment in subcell 2 of the cell is determined.

Unit
Times

19-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.81 C901130080 Number of Handover Execution to the Second Sub Cell Directly From Another BSC
Description
This counter counts the times that an inter-cell handover is performed to hand over an MS from a cell controlled by another BSC to subcell 2 of the cell.

Usage
This counter indicates the number of inter-cell handovers that hand over an MS to subcell 2 of the cell from a cell controlled by another BSC.

Measurement Point
This counter is incremented when the assigned channel in subcell 2 of the cell is activated.

Unit
Times

19.82 C901130081 Number of Handover Success to the Second Sub Cell Directly From Another BSC
Description
This counter counts successful inter-cell handovers that hand over an MS to subcell 2 of the cell from a cell controlled by another BSC.

Usage
This counter indicates the number of successful inter-cell handovers that hand over an MS to subcell 2 of the cell from a cell controlled by another BSC.

Measurement Point
This counter is incremented when a HANDOVER COMPLETE message is received through the assigned channel in subcell 2 of the cell.

Unit
Times

19-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.83 C901130082 Number of Handover to the First Sub Cell Too Fast After Handover From Another Cell in the Same Site
Description
This counter indicates the number of times that an MS is handed over to subcell 1 soon after being handed over to subcell 2 of the cell from another cell in the same site.

Usage
This counter indicates the number of inter-subcell handovers that are carried out to hand over an MS from subcell 2 to subcell 1 soon after the MS is handed over to subcell 2 of the cell from another cell in the same site. It is a reference for revising handover parameters.

Measurement Point
This counter is incremented when an inter-subcell handover is decided.

Unit
Times

19.84 C901130083 Number of Handover to the Second Sub Cell Too Fast After Handover From Another Cell in the Same Site
Description
This counter indicates the number of times that an MS is handed over to subcell 2 soon after being handed over to subcell 1 of the cell from another cell in the same site.

Usage
This counter indicates the number of inter-subcell handovers that are carried out to hand over an MS from subcell 1 to subcell 2 soon after the MS is handed over to subcell 1 of the cell from another cell in the same site. It is a reference for revising handover parameters.

Measurement Point
This counter is incremented when an inter-subcell handover is decided.

Unit
Times
19-77 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.85 C901130084 Number of Handover to the First Sub Cell Too Fast After Handover From Another Site
Description
This counter indicates the number of times that an MS is handed over to subcell 1 soon after being handed over to subcell 2 of the cell from a cell in another site.

Usage
This counter indicates the number of inter-subcell handovers that are carried out to hand over an MS from subcell 2 to subcell 1 soon after the MS is handed over to subcell 2 of the cell from a cell in another site controlled by the same BSC. It is a reference for revising handover parameters.

Measurement Point
This counter is incremented when an inter-subcell handover is decided.

Unit
Times

19.86 C901130085 Number of Handover to the Second Sub Cell Too Fast After Handover From Another Site
Description
This counter indicates the number of times that an MS is handed over to subcell 2 soon after being handed over to subcell 1 of the cell from a cell in another site.

Usage
This counter indicates the number of inter-subcell handovers that are carried out to hand over an MS from subcell 1 to subcell 2 soon after the MS is handed over to subcell 1 of the cell from a cell in another site controlled by the same BSC. It is a reference for revising handover parameters.

Measurement Point
This counter is incremented when an inter-subcell handover is decided.

Unit
Times
19-78 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.87 C901130086 Sample of Subcell 2 Level Low 30dB or Below Than BCCH
Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 30 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.88 C901130087 Sample of Subcell 2 Level Low 29 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 29 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-79 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.89 C901130088 Sample of Subcell 2 Level Low 28 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 28 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.90 C901130089 Sample of Subcell 2 Level Low 27 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 27 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-80 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.91 C901130090 Sample of Subcell 2 Level Low 26 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 26 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.92 C901130091 Sample of Subcell 2 Level Low 25 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 25 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-81 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.93 C901130092 Sample of Subcell 2 Level Low 24 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 24 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.94 C901130093 Sample of Subcell 2 Level Low 23 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 23 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-82 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.95 C901130094 Sample of Subcell 2 Level Low 22 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 22 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.96 C901130095 Sample of Subcell 2 Level Low 21 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 21 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-83 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.97 C901130096 Sample of Subcell 2 Level Low 20 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 20 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.98 C901130097 Sample of Subcell 2 Level Low 19 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 19 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-84 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.99 C901130098 Sample of Subcell 2 Level Low 18 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 18 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.100 C901130099 Sample of Subcell 2 Level Low 17 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 17 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-85 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.101 C901130100 Sample of Subcell 2 Level Low 16 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 16 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.102 C901130101 Sample of Subcell 2 Level Low 15 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 15 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-86 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.103 C901130102 Sample of Subcell 2 Level Low 14 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 14 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.104 C901130103 Sample of Subcell 2 Level Low 13 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 13 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-87 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.105 C901130104 Sample of Subcell 2 Level Low 12 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 12 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.106 C901130105 Sample of Subcell 2 Level Low 11 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 11 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-88 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.107 C901130106 Sample of Subcell 2 Level Low 10 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 10 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.108 C901130107 Sample of Subcell 2 Level Low 9 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 9 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-89 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.109 C901130108 Sample of Subcell 2 Level Low 8 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 8 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.110 C901130109 Sample of Subcell 2 Level Low 7 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 7 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-90 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.111 C901130110 Sample of Subcell 2 Level Low 6 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 6 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.112 C901130111 Sample of Subcell 2 Level Low 5 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 5 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-91 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.113 C901130112 Sample of Subcell 2 Level Low 4 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 4 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.114 C901130113 Sample of Subcell 2 Level Low 3 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 3 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-92 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.115 C901130114 Sample of Subcell 2 Level Low 2 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 2 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.116 C901130115 Sample of Subcell 2 Level Low 1 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 1 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-93 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.117 C901130116 Sample of Subcell 2 Level Equal BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is equal to the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.118 C901130117 Sample of Subcell 2 Level High 1 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 1 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-94 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.119 C901130118 Sample of Subcell 2 Level High 2 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 2. This counter indicates the number of samples that the TCH level is 2 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.120 C901130119 Sample of Subcell 2 Level High 3 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 3. This counter indicates the number of samples that the TCH level is 3 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-95 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.121 C901130120 Sample of Subcell 2 Level High 4 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 4. This counter indicates the number of samples that the TCH level is 4 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.122 C901130121 Sample of Subcell 2 Level High 5 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 5. This counter indicates the number of samples that the TCH level is 5 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-96 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.123 C901130122 Sample of Subcell 2 Level High 6 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 6. This counter indicates the number of samples that the TCH level is 6 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.124 C901130123 Sample of Subcell 2 Level High 7 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 7. This counter indicates the number of samples that the TCH level is 7 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-97 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.125 C901130124 Sample of Subcell 2 Level High 8 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 8. This counter indicates the number of samples that the TCH level is 8 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.126 C901130125 Sample of Subcell 2 Level High 9 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 9. This counter indicates the number of samples that the TCH level is 9 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-98 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.127 C901130126 Sample of Subcell 2 Level High 10 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 10. This counter indicates the number of samples that the TCH level is 10 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.128 C901130127 Sample of Subcell 2 Level High 11 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 11. This counter indicates the number of samples that the TCH level is 11 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-99 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.129 C901130128 Sample of Subcell 2 Level High 12 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 12. This counter indicates the number of samples that the TCH level is 12 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.130 C901130129 Sample of Subcell 2 Level High 13 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 13. This counter indicates the number of samples that the TCH level is 13 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-100 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.131 C901130130 Sample of Subcell 2 Level High 14 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 14. This counter indicates the number of samples that the TCH level is 14 dB higher than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.132 C901130131 Sample of Subcell 2 Level High 15 dB Than BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the TCH level is 15 dB lower than the BCCH level.

Usage
This counter reflects the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-101 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.133 C901130132 Sample of Level Difference Between Subcell 2 and BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the number of samples that the difference between the TCH level and the BCCH level is calculated.

Usage
This counter reflects the number of samples of the level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.134 C901130133 Sum of Level Difference Between Subcell 2 and BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the sum of level difference between the TCH in subcell 2 and the BCCH in subcell 1.

Usage
This counter reflects the sum of level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-102 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.135 C901130134 Lowest of Level Difference Between Subcell 2 and BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the minimal level difference between the TCH in subcell 2 and the BCCH in subcell 1.

Usage
This counter reflects the minimal level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19.136 C901130135 Highest of Level Difference Between Subcell 2 and BCCH

Description
When camping in subcell 2 of a COBCCH cell, the MS measures the TCH level in subcell 2 and the BCCH level in subcell 1. This counter indicates the maximal level difference between the TCH in subcell 2 and the BCCH in subcell 1.

Usage
This counter reflects the maximal level difference between subcell 2 and subcell 1.

Measurement Point
This counter counts the samples when the BSC receives a measurement report from the Abis interface.

Unit
Times

19-103 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.137 C901130136 Number of handover attempt from FR to HR(V3) due to high load in Subcell2
Measured Object
Cell

Description
This counter is incremented each time the BSC attempts to initiate an intra-cell FR-to-HR (V3) handover in subcell 2 due to heavy load. When the load in subcell 2 increases and reaches the threshold for FR-to-HR (V3) handover, a process is initiated to find an existing FR call. If the MS of this call supports AMR HR, and the speech quality reaches the threshold for FR-to-HR handover, the BSC attempts to initiate an intra-cell FR-to-HR (V3) handover.

Usage
None

Measurement Point
The measurement point is A1, as shown in Figure 19-41.
Figure 19-41 Intra-Cell Handover Flow Chart

Unit
Times

19-104 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.138 C901130137 Number of handover from FR to HR(V3) due to high load in Subcell2
Measured Object
Cell

Description
This counter is incremented each time the target resource (AMR HR resource) is ready and the new channel is successfully activated during an FR-to-HR (V3) handover in subcell 2, which is initiated due to heavy load.

Usage
None

Measurement Point
The measurement point is A2, as shown in the intra-cell handover flow chart.

Unit
Times

19.139 C901130138 Number of handover success from FR to HR(V3) due to high load in Subcell2
Measured Object
Cell

Description
This counter is incremented each time the MS sends a handover complete message after successful handover to the new channel in subcell 2 in the case of an intra-cell FR-to-HR (V3) handover initiated due to heavy load.

Usage
None

Measurement Point
The measurement point is A3, as shown in the intra-cell handover flow chart.

Unit
Times
19-105 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.140 C901130139 Number of handover attempt from FR to HR(V1) due to high load in Subcell2
Measured Object
Cell

Description
This counter is incremented each time the BSC attempts to initiate an intra-cell FR->HR (V1) handover due to heavy load in subcell 2. When the load in subcell 2 increases and reaches the threshold for FR-to-HR (V1) handover, a process is initiated to find an existing FR call. The BSC searches for MSs that support AMR HR in subcell 2. If no MS supporting AMR HR is found, the BSC searches for MSs that support HR. If an MS supports AMR HR or HR, and the speech quality reaches the threshold for FR-to-HR handover, the BSC attempts to initiate an intra-cell FR-to-HR (V1) handover.

Usage
None

Measurement Point
The measurement point is A1, as shown in the intra-cell handover flow chart.

Unit
Times

19.141 C901130140 Number of handover from FR to HR(V1) due to high load in Subcell2
Measured Object
Cell

Description
This counter is incremented each time the target resource (common HR resource) is ready and the new channel is successfully activated during an FR-to-HR (V1) handover in subcell 2, which is initiated due to heavy load.

Usage
None
19-106 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Measurement Point
The measurement point is A2, as shown in the intra-cell handover flow chart.

Unit
Times

19.142 C901130141 Number of handover success from FR to HR(V1) due to high load in Subcell2
Measured Object
Cell

Description
This counter is incremented each time a handover complete message is sent after the MS is successfully handed over to the new channel during an FR-to-HR (V1) handover in subcell 2, which is initiated due to heavy load.

Usage
None

Measurement Point
The measurement point is A3, as shown in the intra-cell handover flow chart.

Unit
Times

19.143 C901130142 Number of handover attempt from HR(V3) to FR due to bad quality in Subcell2
Measured Object
Cell

Description
This counter is incremented each time the BSC attempts to initiate an HR (V3)-to-FR handover in subcell 2. When the speech quality of an AMR HR call in subcell 2 is poor, the BSC attempts to initiate an intra-cell HR (V3)-to-FR handover in the case that the intra-cell HR (V3)-to-AMR handover criteria is satisfied but the other handover criterion are not fulfilled.
19-107 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
The measurement point is A1, as shown in the intra-cell handover flow chart.

Unit
Times

19.144 C901130143 Number of handover from HR(V3) to FR due to bad quality in Subcell2
Measured Object
Cell

Description
This counter is incremented each time the radio resource is ready and the new channel is successfully activated during an HR (V3)-to-FR handover in subcell 2, which is initiated due to poor speech quality.

Usage
None

Measurement Point
The measurement point is A2, as shown in the intra-cell handover flow chart.

Unit
Times

19.145 C901130144 Number of handover success from HR(V3) to FR due to bad quality in Subcell2
Measured Object
Cell

19-108 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

Description
This counter is incremented each time a handover complete message is sent after the MS is successfully handed over to the new channel during an HR (V3)-to-FR handover in subcell 2, which is initiated due to poor speech quality.

Usage
None

Measurement Point
The measurement point is A3, as shown in the intra-cell handover flow chart.

Unit
Times

19.146 C901130145 Number of handover attempt from HR(V1) to FR due to bad quality in Subcell2
Measured Object
Cell

Description
This counter is incremented each time the BSC attempts to initiate an intra-cell HR (V1)-to-FR handover. When the speech quality of an HR call in subcell 2 is poor, the BSC attempts to initiate an intra-cell HR (V1)-to-FR handover 2 in the case that the intra-cell HR (V1)-to-FR handover criteria is satisfied but the other handover criterion are not fulfilled.

Usage
None

Measurement Point
The measurement point is A1, as shown in the intra-cell handover flow chart.

Unit
Times

19-109 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.147 C901130146 Number of handover from HR(V1) to FR due to bad quality in Subcell2
Measured Object
Cell

Description
This counter is incremented each time the radio resource is ready and the new channel is successfully activated during an HR (V1)-to-FR handover in subcell 2, which is initiated due to poor speech quality.

Usage
None

Measurement Point
The measurement point is A2, as shown in the intra-cell handover flow chart.

Unit
Times

19.148 C901130147 Number of handover success from HR(V1) to FR due to bad quality in Subcell2
Measured Object
Cell

Description
This counter is incremented each time a handover complete message is sent after the MS is successfully handed over to the new channel during an HR (V1)-to-FR handover in subcell 2, which is initiated due to poor speech quality.

Usage
None

Measurement Point
The measurement point is A3, as shown in the intra-cell handover flow chart.

Unit
Times
19-110 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.149 C901130150 Number of Handover Attempt From FR to HR (V1) Due to High Load in Subcell 2
Description
This counter counts handover attempts from an HR channel (speech version 1) to an FR channel in subcell 2 due to heavy load.

Usage
This counter indicates the number of handover attempts from an HR channel (speech version 1) to an FR channel in subcell 2 due to heavy load.

Measurement Point
This counter is incremented each time the RANCS instance starts a handover procedure after receiving an EV_HRTOFRHOENABLE or EV_AMRHRTOFRHOENABLE message and the current channel in use is an HR channel (speech version 1).

Unit
Times

19.150 C901130151 Number of Handover From FR to HR (V1) Due to High Load in Subcell 2
Description
This counter counts the number of times that a handover from an HR channel (speech version 1) to an FR channel is performed in subcell 2 due to heavy load.

Usage
This counter indicates the number of times that a handover from an HR channel (speech version 1) to an FR channel is performed in subcell 2 due to heavy load.

Measurement Point
This counter is incremented each time the RANCS instance receives an EV_RANCS_RADIO_AVAIL message with the handover cause of HO_HRTOFR_LOAD or HO_AHRTOFR_LOAD and the current channel in use is an HR channel (speech version 1).

Unit
Times
19-111 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

19.151 C901130152 Number of Handover Success From FR to HR (V1) Due to High Load in Subcell 2
Description
This counter counts the number of successful handovers from an HR channel (speech version 1) to an FR channel in subcell 2 due to heavy load.

Usage
This counter indicates the number of successful handovers from an HR channel (speech version 1) to an FR channel in subcell 2 due to heavy load.

Measurement Point
This counter is incremented each time the RANCS instance receives an EV_RANCS_ASS_COM message with the handover cause of HO_HRTOFR_LOAD or HO_AHRTOFR_LOAD and the current channel in use is an HR channel (speech version 1).

Unit
Times

19.152 C901130153 Number of Handover Attempt From FR to HR (V3) Due to High Load in Subcell 2
Description
This counter counts handover attempts from an HR channel (speech version 3) to an FR channel in subcell 2 due to heavy load.

Usage
This counter indicates the number of handover attempts from an HR channel (speech version 3) to an FR channel in subcell 2 due to heavy load.

Measurement Point
This counter is incremented each time the RANCS instance starts a handover procedure after receiving an EV_AMRHRTOFRHOENABLE message and the current channel in use is an HR channel (speech version 3).

Unit
Times
19-112 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 19 Sub Cell Statistics

19.153 C901130154 Number of Handover From FR to HR (V3) Due to High Load in Subcell 2
Description
This counter counts the number of times that a handover from an HR channel (speech version 3) to an FR channel is performed in subcell 2 due to heavy load.

Usage
This counter indicates the number of times that a handover from an HR channel (speech version 3) to an FR channel is performed in subcell 2 due to heavy load.

Measurement Point
This counter is incremented each time the RANCS instance receives an EV_RANCS_RADIO_AVAIL message with the handover cause of HO_AHRTOFR_LOAD and the current channel in use is an HR channel (speech version 3).

Unit
Times

19.154 C901130155 Number of Handover Success From FR to HR (V3) Due to High Load in Subcell 2
Description
This counter counts successful handovers from an HR channel (speech version 3) to an FR channel in subcell 2 due to heavy load.

Usage
This counter indicates the number of successful handovers from an HR channel (speech version 3) to an FR channel in subcell 2 due to heavy load.

Measurement Point
This counter is incremented each time the RANCS instance receives an EV_RANCS_ASS_COM message with the handover cause of HO_AHRTOFR_LOAD and the current channel in use is an HR channel (speech version 3).

Unit
Times

19-113 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

19-114 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20

MS TA Measurement
Table of Contents
Overview ..................................................................................................................20-2 C901140001 Number of TA=0 ..................................................................................20-2 C901140033 Number of TA>63 ................................................................................20-3 C901140034 Number of TA=1 ..................................................................................20-4 C901140035 Number of TA=2 ..................................................................................20-4 C901140036 Number of TA=3 ..................................................................................20-5 C901140037 Number of TA=4 ..................................................................................20-5 C901140038 Number of TA=5 ..................................................................................20-6 C901140039 Number of TA=6 ..................................................................................20-6 C901140040 Number of TA=7 ..................................................................................20-7 C901140041 Number of TA=8 ..................................................................................20-7 C901140042 Number of TA=9 ..................................................................................20-8 C901140043 Number of TA=10 ................................................................................20-8 C901140044 Number of TA=11.................................................................................20-9 C901140045 Number of TA=12 ................................................................................20-9 C901140046 Number of TA=13 ..............................................................................20-10 C901140047 Number of TA=14 ..............................................................................20-10 C901140048 Number of TA=15 .............................................................................. 20-11 C901140049 Number of TA=16 .............................................................................. 20-11 C901140050 Number of TA=17 ..............................................................................20-12 C901140051 Number of TA=18 ..............................................................................20-12 C901140052 Number of TA=19 ..............................................................................20-13 C901140053 Number of TA=20 ..............................................................................20-13 C901140054 Number of TA=21 ..............................................................................20-14 C901140055 Number of TA=22 ..............................................................................20-14 C901140056 Number of TA=23 ..............................................................................20-15 C901140057 Number of TA=24 ..............................................................................20-15 C901140058 Number of TA=25 ..............................................................................20-16 C901140059 Number of TA=26 ..............................................................................20-16 C901140060 Number of TA=27 ..............................................................................20-17 C901140061 Number of TA=28 ..............................................................................20-17 C901140062 Number of TA=29 ..............................................................................20-18 C901140063 Number of TA=30 ..............................................................................20-18 C901140064 Number of TA=31 ..............................................................................20-19 C901140065 Number of TA=32 ..............................................................................20-19 C901140066 Number of TA=33 ..............................................................................20-20 C901140067 Number of TA=34 ..............................................................................20-20
20-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901140068 Number of TA=35 ..............................................................................20-21 C901140069 Number of TA=36 ..............................................................................20-21 C901140070 Number of TA=37 ..............................................................................20-22 C901140071 Number of TA=38 ..............................................................................20-22 C901140072 Number of TA=39 ..............................................................................20-23 C901140073 Number of TA=40 ..............................................................................20-23 C901140074 Number of TA=41 ..............................................................................20-24 C901140075 Number of TA=42 ..............................................................................20-24 C901140076 Number of TA=43 ..............................................................................20-25 C901140077 Number of TA=44 ..............................................................................20-25 C901140078 Number of TA=45 ..............................................................................20-26 C901140079 Number of TA=46 ..............................................................................20-26 C901140080 Number of TA=47 ..............................................................................20-27 C901140081 Number of TA=48 ..............................................................................20-27 C901140082 Number of TA=49 ..............................................................................20-28 C901140083 Number of TA=50 ..............................................................................20-28 C901140084 Number of TA=51 ..............................................................................20-29 C901140085 Number of TA=52 ..............................................................................20-29 C901140086 Number of TA=53 ..............................................................................20-30 C901140087 Number of TA=54 ..............................................................................20-30 C901140088 Number of TA=55 ..............................................................................20-31 C901140089 Number of TA=56 ..............................................................................20-31 C901140090 Number of TA=57 ..............................................................................20-32 C901140091 Number of TA=58 ..............................................................................20-32 C901140092 Number of TA=59 ..............................................................................20-33 C901140093 Number of TA=60 ..............................................................................20-33 C901140094 Number of TA=61 ..............................................................................20-34 C901140095 Number of TA=62 ..............................................................................20-34 C901140096 Number of TA=63 ..............................................................................20-35

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. The measurement takes cell as the statistics unit.

20.2 C901140001 Number of TA=0

Description
This counter counts the number of times of TA=0 in the MS measurement reports.

20-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
This counter is used to find out the frequency of TA=0 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment.

Measurement Point
This counter increments when BSC receives the MS measurement report with TA=0. The measurement point is A, as shown in Figure 20-1.
Figure 20-1 MS Measurement Report

Unit
Times

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

Usage
This counter is used to find out the frequency of TA>63 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment.

Measurement Point
This counter increments when BSC receives the MS measurement report with TA>63. The measurement point is A, as shown in Figure 20-2.

20-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 20-2 MS Measurement Report

Unit
Times

20.4 C901140034 Number of TA=1

Measured Object
Cell

Description
Number of TA=1 received This counter is incremented each time TA=1 is detected in a channel request or measurement report received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.5 C901140035 Number of TA=2

Measured Object
Cell

Description
Number of TA=2 received This counter is incremented each time TA=2 is detected in a channel request or measurement report that is received from the MS.
20-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.6 C901140036 Number of TA=3

Measured Object
Cell

Description
Number of TA=3 received This counter is incremented each time TA=3 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.7 C901140037 Number of TA=4

Measured Object
Cell

Description
Number of TA=4 received This counter is incremented each time TA=4 is detected in a channel request or measurement report that is received from the MS.
20-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.8 C901140038 Number of TA=5

Measured Object
Cell

Description
Number of TA=5 received This counter is incremented each time TA=5 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.9 C901140039 Number of TA=6

Measured Object
Cell

Description
Number of TA=6 received This counter is incremented each time TA=6 is detected in a channel request or measurement report that is received from the MS.
20-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.10 C901140040 Number of TA=7

Measured Object
Cell

Description
Number of TA=7 received This counter is incremented each time TA=7 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.11 C901140041 Number of TA=8

Measured Object
Cell

Description
Number of TA=8 received This counter is incremented each time TA=8 is detected in a channel request or measurement report that is received from the MS.
20-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.12 C901140042 Number of TA=9

Measured Object
Cell

Description
Number of TA=9 received This counter is incremented each time TA=9 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.13 C901140043 Number of TA=10

Measured Object
Cell

Description
Number of TA=10 received This counter is incremented each time TA=10 is detected in a channel request or measurement report that is received from the MS.
20-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.14 C901140044 Number of TA=11

Measured Object
Cell

Description
Number of TA=11 received This counter is incremented each time TA=11 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.15 C901140045 Number of TA=12

Measured Object
Cell

Description
Number of TA=12 received This counter is incremented each time TA=12 is detected in a channel request or measurement report that is received from the MS.
20-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.16 C901140046 Number of TA=13

Measured Object
Cell

Description
Number of TA=13 received This counter is incremented each time TA=13 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.17 C901140047 Number of TA=14

Measured Object
Cell

Description
Number of TA=14 received This counter is incremented each time TA=14 is detected in a channel request or measurement report that is received from the MS.
20-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.18 C901140048 Number of TA=15

Measured Object
Cell

Description
Number of TA=15 received This counter is incremented each time TA=15 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.19 C901140049 Number of TA=16

Measured Object
Cell

Description
Number of TA=16 received This counter is incremented each time TA=16 is detected in a channel request or measurement report that is received from the MS.
20-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.20 C901140050 Number of TA=17

Measured Object
Cell

Description
Number of TA=17 received This counter is incremented each time TA=17 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.21 C901140051 Number of TA=18

Measured Object
Cell

Description
Number of TA=18 received This counter is incremented each time TA=18 is detected in a channel request or measurement report that is received from the MS.
20-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.22 C901140052 Number of TA=19

Measured Object
Cell

Description
Number of TA=19 received This counter is incremented each time TA=19 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.23 C901140053 Number of TA=20

Measured Object
Cell

Description
Number of TA=20 received This counter is incremented each time TA=20 is detected in a channel request or measurement report that is received from the MS.
20-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.24 C901140054 Number of TA=21

Measured Object
Cell

Description
Number of TA=21 received This counter is incremented each time TA=21 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.25 C901140055 Number of TA=22

Measured Object
Cell

Description
Number of TA=22 received This counter is incremented each time TA=22 is detected in a channel request or measurement report that is received from the MS.
20-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.26 C901140056 Number of TA=23

Measured Object
Cell

Description
Number of TA=23 received This counter is incremented each time TA=23 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.27 C901140057 Number of TA=24

Measured Object
Cell

Description
Number of TA=24 received This counter is incremented each time TA=24 is detected in a channel request or measurement report that is received from the MS.
20-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.28 C901140058 Number of TA=25

Measured Object
Cell

Description
Number of TA=25 received This counter is incremented each time TA=25 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.29 C901140059 Number of TA=26

Measured Object
Cell

Description
Number of TA=26 received This counter is incremented each time TA=26 is detected in a channel request or measurement report that is received from the MS.
20-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.30 C901140060 Number of TA=27

Measured Object
Cell

Description
Number of TA=27 received This counter is incremented each time TA=27 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.31 C901140061 Number of TA=28

Measured Object
Cell

Description
Number of TA=28 received This counter is incremented each time TA=28 is detected in a channel request or measurement report that is received from the MS.
20-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.32 C901140062 Number of TA=29

Measured Object
Cell

Description
Number of TA=29 received This counter is incremented each time TA=29 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.33 C901140063 Number of TA=30

Measured Object
Cell

Description
Number of TA=30 received This counter is incremented each time TA=30 is detected in a channel request or measurement report that is received from the MS.
20-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.34 C901140064 Number of TA=31

Measured Object
Cell

Description
Number of TA=31 received This counter is incremented each time TA=31 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.35 C901140065 Number of TA=32

Measured Object
Cell

Description
Number of TA=32 received This counter is incremented each time TA=32 is detected in a channel request or measurement report that is received from the MS.
20-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.36 C901140066 Number of TA=33

Measured Object
Cell

Description
Number of TA=33 received This counter is incremented each time TA=33 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.37 C901140067 Number of TA=34

Measured Object
Cell

Description
Number of TA=34 received This counter is incremented each time TA=34 is detected in a channel request or measurement report that is received from the MS.
20-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.38 C901140068 Number of TA=35

Measured Object
Cell

Description
Number of TA=35 received This counter is incremented each time TA=35 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.39 C901140069 Number of TA=36

Measured Object
Cell

Description
Number of TA=36 received This counter is incremented each time TA=36 is detected in a channel request or measurement report that is received from the MS.
20-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.40 C901140070 Number of TA=37

Measured Object
Cell

Description
Number of TA=37 received This counter is incremented each time TA=37 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.41 C901140071 Number of TA=38

Measured Object
Cell

Description
Number of TA=38 received This counter is incremented each time TA=38 is detected in a channel request or measurement report that is received from the MS.
20-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.42 C901140072 Number of TA=39

Measured Object
Cell

Description
Number of TA=39 received This counter is incremented each time TA=39 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.43 C901140073 Number of TA=40

Measured Object
Cell

Description
Number of TA=40 received This counter is incremented each time TA=40 is detected in a channel request or measurement report that is received from the MS.
20-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.44 C901140074 Number of TA=41

Measured Object
Cell

Description
Number of TA=41 received This counter is incremented each time TA=41 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.45 C901140075 Number of TA=42

Measured Object
Cell

Description
Number of TA=42 received This counter is incremented each time TA=42 is detected in a channel request or measurement report that is received from the MS.
20-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.46 C901140076 Number of TA=43

Measured Object
Cell

Description
Number of TA=43 received This counter is incremented each time TA=43 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.47 C901140077 Number of TA=44

Measured Object
Cell

Description
Number of TA=44 received This counter is incremented each time TA=44 is detected in a channel request or measurement report that is received from the MS.
20-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.48 C901140078 Number of TA=45

Measured Object
Cell

Description
Number of TA=45 received This counter is incremented each time TA=45 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.49 C901140079 Number of TA=46

Measured Object
Cell

Description
Number of TA=46 received This counter is incremented each time TA=46 is detected in a channel request or measurement report that is received from the MS.
20-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.50 C901140080 Number of TA=47

Measured Object
Cell

Description
Number of TA=47 received This counter is incremented each time TA=47 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.51 C901140081 Number of TA=48

Measured Object
Cell

Description
Number of TA=48 received This counter is incremented each time TA=48 is detected in a channel request or measurement report that is received from the MS.
20-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.52 C901140082 Number of TA=49

Measured Object
Cell

Description
Number of TA=49 received This counter is incremented each time TA=49 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.53 C901140083 Number of TA=50

Measured Object
Cell

Description
Number of TA=50 received This counter is incremented each time TA=50 is detected in a channel request or measurement report that is received from the MS.
20-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.54 C901140084 Number of TA=51

Measured Object
Cell

Description
Number of TA=51 received This counter is incremented each time TA=51 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.55 C901140085 Number of TA=52

Measured Object
Cell

Description
Number of TA=52 received This counter is incremented each time TA=52 is detected in a channel request or measurement report that is received from the MS.
20-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.56 C901140086 Number of TA=53

Measured Object
Cell

Description
Number of TA=53 received This counter is incremented each time TA=53 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.57 C901140087 Number of TA=54

Measured Object
Cell

Description
Number of TA=54 received This counter is incremented each time TA=54 is detected in a channel request or measurement report that is received from the MS.
20-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.58 C901140088 Number of TA=55

Measured Object
Cell

Description
Number of TA=55 received This counter is incremented each time TA=55 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.59 C901140089 Number of TA=56

Measured Object
Cell

Description
Number of TA=56 received This counter is incremented each time TA=56 is detected in a channel request or measurement report that is received from the MS.
20-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.60 C901140090 Number of TA=57

Measured Object
Cell

Description
Number of TA=57 received This counter is incremented each time TA=57 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.61 C901140091 Number of TA=58

Measured Object
Cell

Description
Number of TA=58 received This counter is incremented each time TA=58 is detected in a channel request or measurement report that is received from the MS.
20-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.62 C901140092 Number of TA=59

Measured Object
Cell

Description
Number of TA=59 received This counter is incremented each time TA=59 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.63 C901140093 Number of TA=60

Measured Object
Cell

Description
Number of TA=60 received This counter is incremented each time TA=60 is detected in a channel request or measurement report that is received from the MS.
20-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

20.64 C901140094 Number of TA=61

Measured Object
Cell

Description
Number of TA=61 received This counter is incremented each time TA=61 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20.65 C901140095 Number of TA=62

Measured Object
Cell

Description
Number of TA=62 received This counter is incremented each time TA=62 is detected in a channel request or measurement report that is received from the MS.
20-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 20 MS TA Measurement

Usage
None

Measurement Point
None

Unit
Times

20.66 C901140096 Number of TA=63

Measured Object
Cell

Description
Number of TA=63 received This counter is incremented each time TA=63 is detected in a channel request or measurement report that is received from the MS.

Usage
None

Measurement Point
None

Unit
Times

20-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

20-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901150026 Number of Release for Intercept Mobile Originated Short Message ...21-26 C901150027 Number of Release for Intercept Mobile Terminated Short Message ..21-27 C901150028 Number of Discard CM SERVICE REQUEST for Mobile Terminated Short Message .......................................................................................................21-28 C901150029 Number of Discard RP-DATA for Mobile Terminated Short Message..21-29

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. The measurement takes cell as the statistics unit.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

Figure 21-1 - Flow of MO Short Messages during Conversation

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.3 C901150002 Number of SAPI3 link establishments on SACCH/H (MO-SM)

Definition
Number of SAPI3 link establishments on SACCH/H (MO-SM)

Description
This counter counts the number of short message link establishment of mobile originating call through SACCH/H. On SDCCH/H, BSC receives EST_IND message sent by BTS. If the layer 3 information in this message is SAPI=3, the counter increments.

21-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 21-2 - Flow of MO Short Messages during Conversation

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.4 C901150004 Number of SAPI3 link establishments on FACCH/F (MO-SM)

Definition
Number of SAPI3 link establishments on FACCH/F (MO-SM)
21-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

Description
This counter counts the number of short message link establishment of mobile originating call through FACCH/F. On FACCH/F, BSC receives EST_IND message sent by BTS. If the layer 3 information in this message is SAPI=3, the counter increments.

Usage
This counter is used to find out the frequency of SAPI3 link establishments on FACCH/F.

Measurement Point
This counter is not realized at present in the system.

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.5 C901150005 Number of SAPI3 link establishments on FACCH/H (MO-SM)

Definition
Number of SAPI3 link establishments on FACCH/H (MO-SM)

Description
This counter counts the number of short message link establishment of mobile originating call through FACCH/H. On FACCH/H, 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/H.

Measurement Point
This counter is not realized at present in the system.

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)
21-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

21.6 C901150006 Number of SAPI3 link establishment requests on SACCH/F (MT-SM)

Definition
Number of SAPI3 link establishments on SACCH/F (MT-SM)

Description
This counter counts the number of short message link establishment of mobile originating call through SACCH/F. On SDCCH/F, if BSC receives DTAP_IND message sent by MSC with SAPI=3 while the 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.7 C901150007 Number of SAPI3 link establishment requests on SACCH/H (MT-SM)

Definition
Number of SAPI3 link establishments on SACCH/H (MT-SM)

Description
This counter counts the number of short message link establishment of mobile originating call through SACCH/H. On SACCH/H, 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/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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 21-4 - Flow of MT Short Message during Conversation

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.8 C901150009 Number of SAPI3 link establishment requests on FACCH/F (MT-SM)

Definition
Number of SAPI3 link establishments on FACCH/F (MT-SM)

Description
This counter counts the number of short message link establishment of mobile terminating call through FACCH/F. On FACCH/F, BSC receives DTAP_IND message sent by MSC with SAPI=3 while the short message link between BSC and MS is not established, BSC initiates link establishment flow and the counter increments.

Usage
This counter is used to find out the frequency of SAPI3 link establishments on FACCH/F.
21-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

Measurement Point
This counter is not realized at present in the system.

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.9 C901150010 Number of SAPI3 link establishment requests on FACCH/H (MT-SM)

Definition
Number of SAPI3 link establishments on FACCH/H (MT-SM)

Description
This counter counts the number of short message link establishment of mobile terminating call through FACCH/H. On FACCH/H, BSC receives DTAP_IND message sent by MSC with SAPI=3 while the short message link between BSC and MS is not established, BSC initiates link establishment flow and the counter increments.

Usage
This counter is used to find out the frequency of SAPI3 link establishments on FACCH/H.

Measurement Point
This counter is not realized at present in the system.

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of successful short message link establishment of mobile terminating call through SACCH/F. On SACCH/F, if BSC receives EST_CONF message sent by BTS after it initiates short message link establishment flow, this link establishment succeeds, and the counter increments.

Usage
This counter is used to find out the frequency of successful SAPI3 link establishments on SACCH/F.

Measurement Point
This counter counts the number of BSC receiving EST_IND message send by BTS with SAPI=3. The measurement point is C2, as shown in Figure 21-5.
Figure 21-5 - Flow of MT Short Message during Conversation

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

21.11 C901150012 Number of successful SAPI3 link establishments on SACCH/H (MT-SM)

Definition
Number of SAPI3 link establishments on SACCH/H (MT-SM)

Description
This counter counts the number of short message link establishment of mobile terminating call through SACCH/H. On SDCCH/H, if BSC receives EST_CONF message sent by BTS after it initiates short message link establishment flow, this link establishment succeeds, and the counter increments.

Usage
This counter is used to find out the frequency of SAPI3 link establishment requests on SACCH/H.

Measurement Point
This counter counts the number of BSC sending EST_CONF message send by BTS with SAPI=3 while the short message link between BSC and MS is not established. The measurement point is C2, as shown inFigure 21-6 .
Figure 21-6 - Flow of MT Short Message during Conversation

21-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.12 C901150014 Number of successful SAPI3 link establishments on FACCH/F (MT-SM)

Definition
Number of successful SAPI3 link establishments on FACCH/F (MT-SM)

Description
This counter counts the number of successful short message link establishment of mobile terminating call through FACCH/F. On FACCH/F, if BSC receives EST_CONF message sent by BTS after it initiates short message link establishment flow, this link establishment succeeds, and the counter increments.

Usage
This counter is used to find out the frequency of SAPI3 link establishment requests on SACCH/F.

Measurement Point
This counter is not realized at present in the system.

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.13 C901150015 Number of successful SAPI3 link establishments on FACCH/H (MT-SM)

Definition
Number of successful SAPI3 link establishments on FACCH/H (MT-SM)

21-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

Description
This counter counts the number of successful short message link establishment of mobile terminating call through FACCH/H. On FACCH/H, if BSC receives EST_CONF message sent by BTS after it initiates short message link establishment flow, this link establishment succeeds, and the counter increments.

Usage
This counter is used to find out the frequency of successful SAPI3 link establishments on FACCH/H.

Measurement Point
This counter is not realized at present in the system.

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 21-7 - Flow of MT Short Message in Idle Status

21-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

Figure 21-8 - Flow of MO Short Message in Idle Status

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

Figure 21-10 - Flow of MO Short Message in Idle Status

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
This counter is not realized at present in the system.

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.17 C901150019 Number of DTAP messages on 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
This counter is used to find out the frequency of DTAP message of point-to-point short messages on FACCH/F UL.

Measurement Point
This counter is not realized at present in the system.

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

21.18 C901150020 Number of DTAP messages on 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
This counter is used to find out the frequency of DTAP message of point-to-point short messages on FACCH/H UL.

Measurement Point
This counter is not realized at present in the system.

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.19 C901150021 Number of DTAP messages on 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
This counter counts the number of DTAP packet of short messages sent by network side to MS through FACCH/H.

Usage
This counter is used to find out the frequency of DTAP message of point-to-point short messages on FACCH/H DL.

Measurement Point
This counter is not realized at present in the system.
21-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.20 C901150022 Number of DTAP messages on 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
This counter counts the number of DTAP packet of short messages sent by network side to MS through SACCH/F.

Usage
This counter is used to find out the frequency of point-to-point DTAP message of point-to-point short messages on SACCH/F UL.

Measurement Point
This counter counts the number of BSC receiving DTAP packet sent by BTS on SDCCH 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

Figure 21-11 - Flow of MT Short Message during Conversation

Figure 21-12 - Flow of MO Short Messages during Conversation

21-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.21 C901150023 Number of DTAP messages on 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
This counter counts the number of DTAP packet of short messages sent by network side to MS through SACCH/F.

Usage
This counter is used to find out the frequency of DTAP message of point-to-point short messages on SACCH/F DL.

Measurement Point
This counter is not realized at present in the system.

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.22 C901150024 Number of DTAP messages on 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

Usage
This counter is used to find out the frequency of DTAP message of point-to-point short messages on SACCH/H 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 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 21-14 - Flow Of MO Short Messages During Conversation

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.23 C901150025 Number of DTAP messages on 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
This counter counts the number of DTAP packet of short messages sent by network side to MS through SACCH/H.

21-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

Usage
This counter is used to find out the frequency of DTAP message of point-to-point short messages on SACCH/H DL.

Measurement Point
This counter counts the number of BSC sending DTAP packet to BTS on SACCH/H withSAPI=3. The measurement points are C3 and C6 as shown in Figure 21-15, and A3 and A4 as shown inFigure 21-16.
Figure 21-15 - Flow of MT Short Message during Conversation

21-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 21-16 - Flow of MO Short Messages during Conversation

Unit
Times

Related Features
ZGB-01-03-003 Short Message Service (SMS)

21.24 C901150026 Number of Release for Intercept Mobile Originated Short Message
Description
This counter is incremented each time a release is initiated for intercepting Mobile Originated (MO) short messages. Upon receiving an initial link setup indication message from Abis interface, the BSC checks the parameter configuration if the indication contains the layer 3 message "CM SERVICE REQUEST" and the service type of MO short message. If the parameter configuration requires the interception of MO short messages, the BSC initiates a release process.

21-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

Usage
This counter reflects the frequency of releases that are initiated for intercepting MO short messages.

Measurement Point
This counter is incremented each time the BSC initiates a release process for intercepting MO short messages after an initial link setup indication is received from Abis interface. The measurement point is A, as shown in Figure 21-17.
Figure 21-17 Flow Chart of Release Initiation Due to MO Short Message Interception

Unit
Times

21.25 C901150027 Number of Release for Intercept Mobile Terminated Short Message
Description
This counter is incremented each time a release is initiated for intercepting Mobile Terminated (MT) short messages. Upon receiving an SAPI3 DTAP message containing RP-DATA from A interface, the BSC, which is not processing other services, checks its parameter configuration. If the parameter configuration requires intercepting Mobile Terminated (MT) short messages, the BSC initiates a release process.

Usage
This counter reflects the frequency of releases that are initiated for intercepting MT short messages.
21-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremetned each time the BSC initiates a release process for intercepting MT short messages after a RP-DATA message is received from A interface. The measurement point is A, as shown in Figure 21-18.
Figure 21-18 Flow Chart of Release Initiation Due to MT Short Message Interception

Unit
Times

21.26 C901150028 Number of Discard CM SERVICE REQUEST for Mobile Terminated Short Message
Description
This counter is incremented each time the BSC discards a DTAP message due to the requirement for intercepting MO short messages. Upon receiving a DTAP message from Abis interface, the BSC checks the parameter configuration if the DTAP message contains CM SERVICE REQUEST and the service type of MO short message. If the parameter configuration requires the interception of MO short messages, the BSC discards the DTAP message.

21-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 21 SAPI3 Measurement

Usage
This counter reflects the frequency of discarding uplink CM SERVICE REQUEST for intercepting MO short messages.

Measurement Point
This counter is incremented each time the BSC discards a DTAP message received from Abis interface for the interception of MO short messages. The measurement point is A, as shown in Figure 21-19.
Figure 21-19 Flow Chart of CM SERVICE REQUEST Discard for MO Short Message Interception

Unit
Times

21.27 C901150029 Number of Discard RP-DATA for Mobile Terminated Short Message
Description
This counter is incremented each time an RP-DATA message is discarded for intercepting MT short messages. Upon receiving an SAPI3 DTAP message containing RP-DATA from A interface, the BSC, which is processing another service, checks its parameter configuration. If the parameter configuration requires the interception of MT short messages, the BSC discards the RP-DATA message.

Usage
This counter reflects the frequency of discarding downlink DTAP messages that contain RP-DATA due to the requirement for intercepting MT short messages.

21-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the BSC discards an SAPI3 DTAP message that contains RP-DATA for intercepting MT short messages. The measurement point is A, as shown in Figure 21-20.
Figure 21-20 Flow Chart of RP-DATA Discard

Unit
Times

21-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22

Uplink and Downlink PACCH Statistics

Table of Contents
Overview ..................................................................................................................22-2 C901160001 Number of Packet access reject message ...........................................22-2 C901160002 Number of Packet resource request message .....................................22-3 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 C901160029 Number of Packet Measurement Order Message ..............................22-25 C901160030 Number of Packet Measurement Order Message Owing to 2G/3G Inter-Operation .......................................................................................................22-26 C901160031 Number of Packet Measurement Report Message.............................22-27 C901160032 Number of Packet Measurement Report Message Owing to 2G/3G Inter-Operation .......................................................................................................22-28 C901160033 Number of Packet Cell Change Order Message to 3G .......................22-29

22-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.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-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

22.3 C901160002 Number of Packet resource request message

Definition
Number of Packet access reject message

Description
When MS sends packet resource request to BSC through BTS, BSC will return packet UL assignment to MS or packet access reject on PACCH. This counter counts the number of BSC sending the packet access reject messages on PACCH.

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 receives packet resource request messages, the counter increments. The measurement point is A1, as shown inFigure 22-2 .
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
22-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. This counter counts the number of packet UL assignment messages sent by BSC on PACCH.

Measurement Point
When the type of DL control block sent by BSC is packet UL assignment, the counter increments. The measurement point is A, as shown inFigure 22-3.
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.
22-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

Usage
This counter is used to check the packet access reject messages sent by BSC in packet transmission mode.

Measurement Point
When the type of UL control block received by BSC is additional MS access capabilities, the counter increments. The measurement point is A, as shown inFigure 22-4.
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.
22-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 .
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 increments. The measurement point is A, as shown inFigure 22-6.

22-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

Figure 22-6 - DL Sent on PACCH in Packet Transmission Mode

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 PACCH in packet transmission mode.

22-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

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.
Figure 22-8 - DL Sent on PACCH in Packet Transmission Mode

Unit
Times

22.10 C901160009 Number of Packet UL Ack/Nack message

Definition
Number of Packet UL Ack/Nack message

22-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of packet UL Ack/Nack messages sent by BSC on PACCH in packet transmission mode.

Measurement Point
When the type of DL control block sent by BSC is packet UL Ack/Nack, the counter increments. The measurement point is A, as shown inFigure 22-9 .
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

22.13 C901160012 Number of Packet Cell Change Failure message

Definition
Number of Packet Cell Change Failure message
22-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

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 increments. The measurement point is A3, as shown inFigure 22-13 .
Figure 22-13 - Measurement Point of Packet Cell Change Order and Packet Cell Change Failure

Unit
Times

22.14 C901160013 Number of Packet Cell Change Notification message

Definition
Number of Packet Cell Change Notification messages.

Description
If MS intends to handoff from service cell to destination cell, it will initiate packet cell change notification to BSC to request the system message of destination under the condition that the network and MS support NACC.
22-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

22.15 C901160014 Number of Packet Cell Change Order message

Definition
Number of Packet Cell Change Order message

Description
When the MS initiates the packet cell change notification, this counter counts the number of packet cell change order messages 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

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 increments. The measurement point is A, as shown inFigure 22-16.

22-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 PACCH in packet transmission mode.

Measurement Point
When the type of DL control block sent by BSC is packet polling request, counter increments. The measurement point is A, as shown inFigure 22-18 .
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When the type of UL control block sent by BSC is packet PSI Status message, counter increments. The measurement point is A1, as shown inFigure 22-20.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

Figure 22-21 - Measurement Point of Packet-Service-Cell-Data-Related Counter

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 increments. The measurement point is A1, as shown inFigure 22-22.

22-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 22-22 - Measurement Point of Packet-Service-Cell-Data-Related Counter

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGB-02-01-001 Paging

22.26 C901160027 Number of PSI message

Definition
Number of packet PSI message.

22-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

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.27 C901160029 Number of Packet Measurement Order Message

Description
This counter counts the times that the BSC sends the Packet Measurement Order message in the network control mode. This counter increases by 1 when the BSC sends the Packet Measurement Order message in the network control mode.

Usage
None

22-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The measurement point is as shown in Figure 22-27.
Figure 22-27 Number of Packet Measurement Order Messages

Unit
Time

22.28 C901160030 Number of Packet Measurement Order Message Owing to 2G/3G Inter-Operation
Description
This counter counts the times that the Packet Measurement Order message is sent to the dual-mode terminal in the 2G/3G network control mode. This counter increases by 1 when the Packet Measurement Order message is sent to the dual-mode terminal in the 2G/3G network control mode.

Usage
None

Measurement Point
The measurement point is as shown in Figure 22-28.

22-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

Figure 22-28 Number of Packet Measurement Order Messages Owing to 2G/3G Inter-Operation

Unit
Time

22.29 C901160031 Number of Packet Measurement Report Message

Description
This counter counts the times that the RANU FP module receives Packet Measurement Report message. This counter increases by 1 when the RANU FP module receives the Packet Measurement Report message.

Usage
None

Measurement Point
The measurement point is as shown in Figure 22-29.
Figure 22-29 Number of Packet Measurement Report Messages

22-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Time

22.30 C901160032 Number of Packet Measurement Report Message Owing to 2G/3G Inter-Operation
Description
This counter counts the times that the RANU MAC module receives the Packet Measurement Report message containing the measurement report of the adjacent 3G cell. This counter increases by 1 when the RANU MAC module receives the Packet Measurement Report message containing the measurement report of the adjacent 3G cell.

Usage
None

Measurement Point
The measurement point is as shown in Figure 22-30.
Figure 22-30 Number of Packet Measurement Report Messages Owing to 2G/3G Inter-Operation

Unit
Time

22-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 22 Uplink and Downlink PACCH Statistics

22.31 C901160033 Number of Packet Cell Change Order Message to 3G

Description
This counter counts the times that the Packet Cell Change Order message is sent to the 3G target cell. This counter increases by 1 when the RANU MAC module sends the Packet Cell Change Order message to the 3G target cell.

Usage
None

Measurement Point
The measurement point is as shown in Figure 22-31.
Figure 22-31 Number of Packet Cell Change Order Messages to 3G

Unit
Time

22-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

22-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 C901170016 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to not receive PIA ............................................................................................23-15 C901170017 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to UPPB-DSP congestion ................................................................................23-16 C901170018 Number of GPRS DL TBF establishment failure on PACCH due to 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 congestion for UL TBF establishment .....................................................................23-19 C901170025 Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment.....................................23-20
23-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901170026 Number of GPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment .................................................................23-21 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 connection failure for UL TBF establishment ..........................................................23-25 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 TBF establishment .................................................................................................23-27 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 congestion for LLC transmission.............................................................................23-29 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 of channel allocation 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 connection failure for LLC transmission ..................................................................23-35 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 index exception .................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. The measurement takes cell as the statistics unit.

23.2 C901170002 Number of GPRS DL TBF establishment requests on CCCH/PCCCH

Definition
Number of GPRS DL TBF establishment requests on CCCH/PCCCH.

Description
This counter counts the number of DL establishment requests received by control plane when BSC initially attempts to establish GPRS DL TBF.

Usage
This counter is used to find out the frequency of DL establishment requests sent from CCCH/PCCCH and received by control plane when BSC establishes GPRS DL TBF.

Measurement Point
When RANPS module receives the DL request (EV_RANUMC_DLASS_REQ) sent from RANUMC module, the counter increments. The measurement point is A, as shown in Figure 23-1.
Figure 23-1 - DL Request

23-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

23.3 C901170003 Number of GPRS DL TBF establishment requests on PACCH

Definition
Number of GPRS DL TBF establishment requests on PACCH.

Description
This counter counts the number of establishing GPRS DL TBF on PACCH by MS.

Usage
This counter is used to find out the frequency of establishing DL TBF in PACCH after MS has established GPRS UL TBF.

Measurement Point
After MS has established GPRS UL TBF, RANPS module receives EV_MAC_DL_ASSIGN_REQ message sent from RANU module, the counter increments. The measurement point is A, as shown inFigure 23-2.
Figure 23-2 - DL Assignment Request

Unit
Times

23-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

23.4 C901170004 Number of GPRS DL TBF establishment failure due to CPU

Description
No statistics temporarily.

23.5 C901170005 Number of GPRS DL TBF establishment failure due to not support DTM
Description
No statistics temporarily.

23.6 C901170007 Number of GPRS DL TBF 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 23-3 - Database Application Failure due to Abis Congestion (I)

After MS establishes GPRS UL TBF, RANPS module receives EV_MAC_DL_ASSIGN_REQ message sent from RANU module, if resource application fails and the cause of failure is Abis congestion, the counter increments. The measurement point is A, as shown inFigure 23-4 .
Figure 23-4 - Database Application Failure due to Abis Congestion (II)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

23.7 C901170008 Number of GPRS DL TBF establishment failure due to RR congestion

Definition
Number of GPRS DL TBF establishment failure due to RR congestion.

Description
This counter counts the number of failures that RANPS applies to database for resource and the cause of failures is RR congestion when BSC attempts to establish GPRS DL TBF.
23-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

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
This counter is used to find out the frequency of failures that RANPS applies to database for resource and the cause of failures is RR 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 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)

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 RR congestion, the counter increments. The measurement point is A, as shown inFigure 23-6.
Figure 23-6 - Database Application Failure Due To RR Congestion (II)

Unit
Times
23-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

23.8 C901170009 Number of GPRS DL TBF establishment failure due to UPPB-DSP channel congestion
Definition
Number of GPRS DL TBF establishment failure due to UPPB-DSP channel congestion.

Description
This counter counts the number 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.

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

After MS establishes GPRS UL TBF, RANPS module receives EV_MAC_DL_ASSIGN_REQ message sent from RANU module, if resource
23-8

SJ-20110531095035-015|2013-04-25 (R1.7)

ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

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.
Figure 23-8 - Database Application Failure due to UPPB-DSP Channel Congestion (II)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

23.9 C901170010 Number of GPRS DL TBF establishment channel allocate success

Definition
Number of GPRS DL TBF establishment channel allocate success

Description
This counter counts the number of channel allocate success applied by RANPS when BSC attempts to establish GPRS DL TBF.

Usage
This counter is used to find out the frequency of successful resource application that RANPS sends when BSC attempts to establish GPRS DL TBF.

Measurement Point
After RANPS module receives DL request message (EV_RANUMC_DLASS_REQ) sent from RANUMC module, when resource application succeeds, the counter increments. The measurement point is A, as shown inFigure 23-9.

23-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 23-9 - Successful Resource Application

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Figure 23-10 - Successful Resource Application

Unit
Times

23.11 C901170012 Number of GPRS DL TBF 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
The measurement is taken at two time points listed below: l When BSC receives PDCH activation failure message reported by BTS, the counter increments. The measurement point is A, as shown inFigure 23-11.

23-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 23-11 - PDCH Activation Failure

If 'wait for PDCH activate & connection response' timer expires, and BSC has not received PDCH activate response message reported by BTS, the counter increments.

Unit
Times

23.12 C901170013 Number of GPRS DL TBF 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
The measurement is taken at two time points listed below: l If RANPS module receives connection failed message reported by connection module, and the cause of failure is BTS connection failed, the counter increments. The measurement point is A, as shown inFigure 23-12.

23-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Figure 23-12 - Connection Failed due to BTS Connection Failure

If 'wait for PDCH activate & connection response' timer expires, and BSC has not received connection success response message reported by connection module, the counter increments.

Unit
Times

23.13 C901170014 Number of GPRS DL TBF 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 establishing DL TBF while UL TBF already exists).

Measurement Point
If RANPS module receives connection failed message reported by connection module, and the cause of failure is BIU connection failed, the counter increments. The measurement point is A, as shown inFigure 23-13.

23-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Figure 23-14 - DL GPRS TBF Establishes Channel Activation And Access Success

Unit
Times

23.15 C901170016 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to not 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 when BSC establishes GPRS DL TBF.

Usage
This counter is used to find out the frequency of DL immediate assignment message sending failures when BSC establishes GPRS DL TBF.

Measurement Point
The measurement is taken at two time points listed below: l When RANPS module receives immediate assignment sending failure message (EV_PACKET_PIA_DEL_IND) reported by BTS, the counter increments. The measurement point is A, as shown inFigure 23-15.

23-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 23-15 - Immediate Assignment Sending Failure

If 'wait for immediate assignment sending indication' timer expires, and BSC has not received immediate assignment sending message, the counter increments.

Unit
Times

23.16 C901170017 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to 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
ZGO-03-02-002 Enhancement on Channel Allocation

23.17 C901170018 Number of GPRS DL TBF 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
No statistics for this counter is meaningless to GPRS DL TBF.
23-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

23.18 C901170019 Number of GPRS DL TBF 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 when BSC establishes GPRS DL TBF.

Usage
This counter is used to find out the frequency of GPRS DL TBF establishment success.

Measurement Point
When RANPS module receives successful immediate assignment sending message (SPS_ABIS_PACKET_SEND_PIA_IND) reported by BTS, the counter increments. The measurement point is A, as shown in Figure 23-16.
Figure 23-16 - Successful Immediate Assignment Sending

Unit
Times

23.19 C901170020 Number of GPRS DL TBF establishment success on PACCH

Definition
Number of GPRS DL TBF establishment success on PACCH.
23-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
No statistics temporarily.

23.20 C901170023 Number of GPRS DL TBF resource 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

23.21 C901170024 Number of GPRS DL TBF resource 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 application failure leads to DL resource reallocation failure. This counter counts the number of DL resource reallocation failure due to RR congestion. There are three causes for RR congestion: MS per channel (number of MS reaches the peak in each channel), TAI/TFI (no TAI or TFI) and no PDCH (no PS channel).

Usage
This counter is used to find out the frequency of GPRS DL TBF resource reallocation failure due to RR 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 RR congestion, the counter increments. The measurement point is A, as shown in Figure 23-18.

23-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 23-18 - Resource Application Failure Due To RR Congestion (Assigned By UL)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

23.22 C901170025 Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment
Definition
Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment

Description
After MS establishes GPRS DL TBF, it shall establish UL TBF in PACCH. But resource application failure leads to DL resource reallocation failure. This counter counts the number of DL resource reallocation failures due to UPPB-DSP channel congestion.

Usage
This counter is used to find out the frequency of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel 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

23-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

fails due to UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown in Figure 23-19.
Figure 23-19 - Resource Application Failure Due To UPPB-DSP Channel Congestion (Assigned By UL)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

23.23 C901170026 Number of GPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment
Definition
Number of GPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment.

Description
After MS establishes GPRS DL TBF, it shall establish UL TBF in PACCH. This counter counts the number of DL resource application success.

Usage
This counter is used to find out the frequency of GPRS DL TBF resource reallocation success.

23-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 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
ZGO-03-02-002 Enhancement on Channel Allocation

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.
23-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Measurement Point
MS has established GPRS DL TBF, and after RANPS module receives EV_MAC_UL_ASSIGN_REQ message sent from RANU module, when resource application succeeds, the counter accumulates the PDTCH number. The measurement point is A, as shown inFigure 23-21.
Figure 23-21 - Successful Resource Application (Assigned By UL)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

23.25 C901170028 Number of GPRS DL TBF resource 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.
23-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The measurement is taken at two time points listed below: l When BSC receives PDCH activate failure message reported by BTS, the counter increments. The measurement point is A, as shown in Figure 23-22.
Figure 23-22 - PDCH Activation Failure

If 'wait for PDCH activate & connection response' timer expires, and BSC has not received PDCH activate response message reported by BTS, the counter increments.

Unit
Times

23.26 C901170029 Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment
Definition
Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment

Description
This counter counts the number of connection failure due to BTS connection failure during the process of GPRS DL TBF resource reallocation.

Usage
This counter is used to find out the frequency of connection failure due to BTS connection failure during the process of GPRS DL TBF resource reallocation.

Measurement Point
The measurement is taken at two time points listed below:

23-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

If RANPS module receives connection failure message reported by connection module, and the cause of failure is BTS connection failure, the counter increments. The measurement point is A, as shown in Figure 23-23.
Figure 23-23 - Connection Failure Due To BTS Connection Failure

If 'wait for PDCH activation & connection response' timer expires, and BSC has not received connection success response message reported by connection module, the counter increments.

Unit
Times

23.27 C901170030 Number of GPRS DL TBF resource reallocation failure due to BIU connection failure for UL TBF establishment
Definition
Number of GPRS 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 GPRS DL TBF resource reallocation.

Usage
This counter is used to find out the frequency of connection failure due to BIU connection 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 measurement point is A, as shown inFigure 23-24.
23-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 23-24 - Connection Failed Due To BIU Connection Failure

Unit
Times

23.28 C901170031 Number of GPRS DL TBF resource reallocation success of channel activate and connection for UL TBF establishment
Definition
Number of GPRS DL TBF resource reallocation success of channel activate and connection for UL TBF establishment

Description
This counter counts the number of channel activate success during the process of GPRS DL TBF resource reallocation.

Usage
This counter is used to find out the frequency of channel activate success during the process of GPRS DL TBF resource reallocation.

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

23-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Figure 23-25 - Successful Activation And Connection

Unit
Times

23.29 C901170032 Number of GPRS DL TBF resource reallocation failure due to UL TBF establishment
Definition
Number of GPRS DL TBF resource reallocation failure due to UL TBF establishment.

Description
No statistics for this counter is meaningless to GPRS DL TBF.

23.30 C901170033 Number of GPRS DL TBF resource reallocation success due to UL TBF establishment
Definition
Number of GPRS DL TBF resource reallocation success due to UL TBF establishment.

Description
No statistics for this counter is meaningless to GPRS DL TBF.

23.31 C901170036 Number of GPRS DL TBF resource 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A, as shown inFigure 23-26.
Figure 23-26 - Resource Application Failure Due To Abis Congestion (Resource Adjustment)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

23-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

23.32 C901170037 Number of GPRS DL TBF resource 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
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 RR congestion). There are three causes for RR congestion: MS per channel (number of MS reaches the peak in each channel), TAI/TFI (no TAI or TFI) and no PDCH (no PS channel).

Usage Measurement Point

After RANPS module receives EV_MAC_RESOURCE_ADJU_REQ message sent from MAC, if resource application fails due to RR congestion, the counter increments. The measurement point is A, as shown in Figure 23-27.
Figure 23-27 - Resource Application Failure Due To RR Congestion (Resource Adjustment)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation
23-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

23.33 C901170038 Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission
Definition
Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission.

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 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. The measurement point is A, as shown in Figure 23-28.
Figure 23-28 - Resource Application Failure Due To UPPB-DSP Channel Congestion (Resource Adjustment)

Unit
Times

23-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

23.34 C901170039 Number of GPRS DL TBF resource reallocation success of channel allocation due to LLC transmission
Definition
Number of GPRS DL TBF resource reallocation success of channel allocation due to LLC transmission.

Description
During GPRS DL TBF transmission, MAC sends resource adjustment message (EV_MAC_RESOURCE_ADJU_REQ) to RANPS due to UL/DL LLC changes. RANPS applies for resource after it receives the message. This counter counts the number of resource 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
After RANPS module receives EV_MAC_RESOURCE_ADJU_REQ message sent from MAC, if resource application succeeds, the counter increments. The measurement point is A, as shown in Figure 23-29.
Figure 23-29 Successful Resource Application (Resource Adjustment)

Unit
Times
23-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

23.35 C901170040 Number of allocated PDCH for 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
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 successfully allocated PDCH after RANPS receives resource adjustment request during GPRS DL TBF transmission.

Usage
This counter is used to find out the number of successfully allocated PDCH after RANPS receives resource adjustment request during GPRS DL TBF transmission.

Measurement Point
After RANPS module receives EV_MAC_RESOURCE_ADJU_REQ message sent from MAC, if resource application succeeds, the counter accumulates the PDTCH number. The measurement point is A, as shown in Figure 23-30.
Figure 23-30 - Successful Resource Application (Resource Adjustment)

Unit
Times
23-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

23.36 C901170041 Number of GPRS DL TBF resource reallocation failure due to channel activate failure 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
The measurement is taken at two time points listed below: l When BSC receives PDCH activate failure message reported by BTS, the counter increments. The measurement point is A, as shown in Figure 23-31.
Figure 23-31 - PDCH Activation Failure

If 'wait for PDCH activate & connection response' timer expires, and BSC has not received PDCH activate response message reported by BTS, the counter increments.

Unit
Times

23-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

23.37 C901170042 Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission
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: l If RANPS module receives connection failure message reported by connection module, and the cause of failure is BTS connection failure, the counter increments. The measurement point is A, as shown inFigure 23-32.
Figure 23-32 - Connection Failed Due To BTS Connection Failure

If 'wait for PDCH activate & connection response' timer expires, and BSC has not received connection success response message reported by connection module, the counter increments.

Unit
Times

23-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

23.38 C901170043 Number of GPRS DL TBF resource reallocation failure due to BIU connection failure for LLC transmission
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
If RANPS module receives connection failure message reported by connection module, and the cause of failure is BIU connection failure, the counter increments. The measurement point is A, as shown in Figure 23-33.
Figure 23-33 - Connection Failed Due To BIU Connection Failure

Unit
Times

23-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

23.39 C901170044 Number of GPRS DL TBF resource reallocation success of channel activate and connection for LLC transmission
Definition
Number of GPRS DL TBF resource reallocation success of channel activate and connection for LLC transmission

Description
This counter counts the number of channel activate success after BSC receives resource adjustment request during GPRS DL TBF transmission.

Usage
This counter is used to find out the frequency of channel activate success after BSC receives resource adjustment request during GPRS DL TBF transmission.

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 in Figure 23-34.
Figure 23-34 - Successful Activation And Connection

Unit
Times

23.40 C901170045 Number of GPRS DL TBF resource reallocation failure due to LLC transmission
Definition
Number of GPRS DL TBF resource reallocation failure due to LLC transmission.

23-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Description
No statistics for this counter is meaningless to GPRS DL TBF.

23.41 C901170046 Number of GPRS DL TBF resource reallocation success due to LLC transmission
Definition
Number of GPRS DL TBF resource reallocation success due to LLC transmission.

Description
No statistics for this counter is meaningless to GPRS DL TBF.

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 counter increments. The measurement point is A, as shown in Figure 23-35.
Figure 23-35 - Release Request Due To Flush LL

23-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

23.43 C901170048 Number of GPRS DL TBF release 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
This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests due to suspend requests received by RANPS.

Measurement Point
When RANPS module receives Release Request message (EV_RANUMC_REL_CMD) reported by RANUMC, if the cause of release is SUSPEND, and GPRS DL TBF exists, the counter increments. The measurement point is A, as shown in Figure 23-36.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Description
This counter counts the number of GPRS DL TBF forcing release by CS due to PDCH REL.

Usage
This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests (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 measurement point is A, as shown in Figure 23-37.
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
This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests due to normal Release Request by MAC received by RANPS.

23-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 release due to user plane requests
Definition
Number of GPRS DL TBF abnormal release due to user plane requests.

Description
This counter counts the number of GPRS DL TBF abnormal release due to abnormal Release Request by MAC.

Usage
This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests due to abnormal Release Request by MAC received by RANPS.

Measurement Point
When RANPS module receives Release Request message (EV_MAC_REL_IND) reported 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Figure 23-39 - Release Request Due To Abnormal Release Request By MAC

Unit
Times

23.47 C901170052 Number of GPRS DL TBF release 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
This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests due to NSVC unavailability 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 NSVC unavailability, and GPRS DL TBF exists, the counter increments. The measurement point is A, as shown in Figure 23-40.
Figure 23-40 - Release Request Due To NSVC Unavailability

Unit
Times

23-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

23.48 C901170053 Number of GPRS DL TBF release 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
This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests due to BVC unavailability received by RANPS.

Measurement Point
When RANPS module receives Release Request message (EV_RANUMC_REL_CMD) 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

23.49 C901170054 Number of GPRS DL TBF release due to index exception

Definition
Number of GPRS DL TBF release due to index exception.

23-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Description
This counter counts the number of GPRS DL TBF release due to index exception. If TLLI conflict is detected by control plane When the MS try to access a new cell, this counter will be added 1, then the old instance is released too.

Usage
This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests due to index exception in control plane.

Measurement Point
When MS accesses a new cell, TLLI conflict will be detected by control plane. At the same time, the old instance will be released. The release reason is index exception. If current TBF is GPRS DL TBF, the counter will be added 1. The measurement point is A, as shown inFigure 23-42.
Figure 23-42 - RELEASE REQUEST due to index exception

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.

23-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 23-43 - DL GPRS Resource Request Success

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS 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.

23-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

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 inFigure 23-44.
Figure 23-44 - DL GPRS Resource Request Success

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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
This counter increments while DL GPRS TBF is established during resource adjustment, 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 23-45 - DL GPRS Resource Request Success

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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
This counter increments while DL GPRS TBF is established during resource adjustment, the instance to be queued successfully assigns resource for user plane, and database is successfully registered. Measurement point is A as shown in Figure 23-46.

23-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 23 Downlink GPRS Data TBF Statistics

Figure 23-46 - Resource Assignment Success

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 23-47 - Release DL GPRS TBF

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

23-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 connection failed ....................................................................................................24-12 C901180014 Number of EGPRS DL TBF establishment failure due to BIU connection failed ....................................................................................................24-13 C901180015 Number of EGPRS DL TBF channel activate establishment success .24-14 C901180016 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to not receive PIA ............................................................................................24-15 C901180017 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to UPPB-DSP congestion ................................................................................24-16 C901180018 Number of EGPRS DL TBF establishment failure on PACCH due to UPPB-DSP congestion...........................................................................................24-16 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 congestion for UL TBF establishment .....................................................................24-18

24-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901180024 Number of EGPRS DL TBF resource reallocation failure due to RR congestion for UL TBF establishment .....................................................................24-19 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 of channel allocation due to UL TBF establishment .................................................................24-21 C901180027 Number of allocated PDCH for EGPRS DL TBF resource reallocation due to UL TBF establishment .................................................................................24-22 C901180028 Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment ..................................................24-23 C901180029 Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment ..........................................................24-24 C901180030 Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for UL TBF establishment ..........................................................24-25 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 TBF establishment .................................................................................................24-27 C901180033 Number of EGPRS DL TBF resource reallocation success due to UL TBF establishment .................................................................................................24-27 C901180036 Number of EGPRS DL TBF resource reallocation failure due to Abis congestion for LLC transmission.............................................................................24-28 C901180037 Number of EGPRS DL TBF resource reallocation failure due to RR congestion for LLC transmission.............................................................................24-29 C901180038 Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission ............................................24-30 C901180039 Number of EGPRS DL TBF resource reallocation success of channel allocation due to LLC transmission .........................................................................24-31 C901180040 Number of allocated PDCH for EGPRS DL TBF resource reallocation due to LLC transmission.........................................................................................24-32 C901180041 Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission..........................................................24-33 C901180042 Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission ..................................................................24-34 C901180043 Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for LLC transmission ..................................................................24-35 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 Index exception...............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 C901180060 Times of Downlink EGPRS TBF Requesting DLDC Resources..........24-48 C901180061 Times of Allocating Downlink DLDC Resources for EGPRS TBF .......24-48

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.

24.2 C901180002 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 PS control plane receives the DL request (EV_RANUMC_DLASS_REQ) sent from PS user plane, the counter increments. This measurement point is A, as shown in Figure 24-1.

24-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 24-1 - DL Request

Unit
Times

24.3 C901180003 Number of EGPRS DL TBF establishment requests on PACCH

Definition
Number of EGPRS DL TBF establishment requests on PACCH.

Description
This counter counts the number of establishing EGPRS DL TBF on PACCH by MS.

Usage
This counter is used to find out the frequency of establishing DL TBF in PACCH after MS has established EGPRS UL TBF.

Measurement Point
After MS has established EGPRS UL TBF, PS control plane receives EV_MAC_DL_ASSIGN_REQ message sent from PS user plane, the counter increments. This measurement point is A, as shown inFigure 24-2.
Figure 24-2 - DL Assignment Request

24-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Unit
Times

24.4 C901180004 Number of EGPRS DL TBF establishment failure due to CPU

Definition
Number of EGPRS DL TBF establishment failure due to CPU.

Description
No statistics temporarily.

24.5 C901180005 Number of EGPRS DL TBF establishment failure due to not support DTM
Definition
Number of EGPRS DL TBF establishment failure due to not support DTM.

Description
No statistics temporarily.

24.6 C901180007 Number of EGPRS DL TBF establishment failure due to Abis congestion
Definition
Number of EGPRS DL TBF establishment failure due to Abis congestion.

Description
This counter counts the number of failures that PS control plane applies to database for resource and the cause of failures is Abis congestion when BSC attempts to establish EGPRS DL TBF.

Usage
This counter is used to find out the frequency of failures that PS control plane applies to database for resource and the cause of failures is Abis congestion when BSC attempts to establish EGPRS DL TBF.

24-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The measurement is taken at two time points listed below: l After PS control plane module receives DL request message (EV_RANUMC_DLASS_REQ) sent from PS user plane, 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)

After MS establishes EGPRS UL TBF, PS control plane module receives EV_MAC_DL_ASSIGN_REQ message sent from PS user plane, 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-4.
Figure 24-4 - Database Application Failure Due To Abis Congestion (II)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

24.7 C901180008 Number of EGPRS DL TBF establishment failure due to RR congestion

Definition
Number of EGPRS DL TBF establishment failure due to RR congestion.

Description
This counter counts the number of failures that PS control plane applies to database for resource and the cause of failures is RR congestion when BSC attempts to establish GPRS DL TBF. There are three causes for RR congestion: MS per channel (number of MS reaches the peak in each channel), TAI/TFI (no TAI or TFI) and no PDCH (no PS channel). This counter is used to find out the frequency of failures that PS control plane applies to database for resource and the cause of failures is RR congestion when BSC attempts to establish GPRS DL TBF.

Usage
This counter is used to find out the frequency of failures that PS control plane applies to database for resource and the cause of failures is RR congestion when BSC attempts to establish GPRS DL TBF.

Measurement Point
The measurement is taken at two time points listed below: l After PS control plane module receives DL request message (EV_RANUMC_DLASS_REQ) sent from PS user plane, if resource application fails and the cause of failure is 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)

After MS establishes GPRS UL TBF, PS control plane module receives EV_MAC_DL_ASSIGN_REQ message sent from PS user plane, if resource application fails and the cause of failure is RR congestion, the counter increments. The measurement point is A, as shown inFigure 24-6.
24-7

SJ-20110531095035-015|2013-04-25 (R1.7)

ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 24-6 - Database Application Failure Due To RR Congestion (II)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.8 C901180009 Number of EGPRS DL TBF establishment failure due to UPPB-DSP channel congestion
Definition
Number of EGPRS DL TBF establishment failure due to UPPB-DSP channel congestion.

Description
This counter counts the number of failures that PS control plane applies to database for resource 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 PS control plane 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
The measurement is taken at two time points listed below: l After PS control plane receives DL request message (EV_RANUMC_DLASS_REQ) sent from PS user plane, 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 24-7.
24-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Figure 24-7 - Database Application Failure due to UPPB-DSP Channel Congestion (I)

After MS establishes EGPRS UL TBF, PS control plane receives EV_MAC_DL_ASSIGN_REQ message sent from PS user plane, 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 24-8.
Figure 24-8 - Database Application Failure due to UPPB-DSP Channel Congestion (II)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.9 C901180010 Number of EGPRS DL TBF establishment channel allocate success

Definition
Number of EGPRS DL TBF establishment channel allocate success.

Description
This counter counts the number of channel allocate success applied by PS control plane when BSC attempts to establish EGPRS DL TBF.
24-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of successful resource application that PS control plane sends when BSC attempts to establish EGPRS DL TBF.

Measurement Point
After PS control plane receives DL request message (EV_RANUMC_DLASS_REQ) sent from PS user plane, when resource application succeeds, the counter increments. The measurement point is A, as shown inFigure 24-9.
Figure 24-9 - Successful Resource Application

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.10 C901180011 Number of allocated PDCH for 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Measurement Point
After PS control plane receives DL request message EV_RANUMC_DLASS_REQ sent from PS user plane, when resource application succeeds, the counter accumulates the PDCH number. The measurement point is A, as shown inFigure 24-10.
Figure 24-10 - Successful Resource Application

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.11 C901180012 Number of EGPRS DL TBF establishment failure due to channel activate failed
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
The measurement is taken at two time points listed below: l When BSC receives PDCH activation failure message reported by BTS, the counter increments. The measurement point is A, as shown inFigure 24-11.
24-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 24-11 - PDCH Activation Failure

If 'wait for PDCH activate & connection response' timer expires, and BSC has not received PDCH activate response message reported by BTS, the counter increments.

Unit
Times

24.12 C901180013 Number of EGPRS DL TBF establishment failure due to BTS connection failed
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
This counter is used to find out the frequency of connection failure due to BTS connection failed when BSC establishes EGPRS DL TBF (including establishing DL TBF initially and establishing DL TBF while UL TBF already exists).

Measurement Point
The measurement is taken at two time points listed below: l If PS control plane receives connection failure message reported by connection module, and the cause of failure is BTS connection failure, the counter increments. The measurement point is A, as shown inFigure 24-12.

24-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Figure 24-12 - Connection Failed Due To BTS Connection Failure

If 'wait for PDCH activation & connection response' timer expires, and BSC has not received connection success response message reported by connection module, the counter increments.

Unit
Times

24.13 C901180014 Number of EGPRS DL TBF establishment failure due to BIU connection failed
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
This counter is used to find out the frequency of connection failure due to BIU connection failed when BSC establishes EGPRS DL TBF (including establishing DL TBF initially and establishing DL TBF while UL TBF already exists).

Measurement Point
If PS control plane receives connection failed message reported by connection module, and the cause of failure is BIU connection failed, the counter increments. The measurement point is A, as shown inFigure 24-13.

24-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 24-13 - Connection Failed Due To BIU Connection Failure

Unit
Times

24.14 C901180015 Number of EGPRS DL TBF channel activate establishment success

Definition
Number of EGPRS DL TBF channel activate establishment success.

Description
This counter counts the number of channel activate establishment success when BSC establishes EGPRS DL TBF.

Usage
This counter is used to find out the frequency of channel activate establishment success when BSC establishes EGPRS DL TBF.

Measurement Point
When PS control plane 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 24-14.

24-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Figure 24-14 - Immediate Assignment Sending Failure

Unit
Times

24.15 C901180016 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to not 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
The measurement is taken at two time points listed below: l When PS control plane receives immediate assignment sending failure message EV_PACKET_PIA_DEL_IND reported by BTS, the counter increments. The measurement point is A, as shown inFigure 24-15.

24-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 24-15 - Successful Immediate Assignment Sending

If 'wait for immediate assignment sending indication' timer expires, and BSC has not received immediate assignment sending message, the counter increments.

Unit
Times

24.16 C901180017 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to 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.

24.17 C901180018 Number of EGPRS DL TBF establishment failure on PACCH due to UPPB-DSP congestion
Definition
Number of EGPRS DL TBF establishment failure on PACCH due to UPPB-DSP congestion.

Description
No statistics for this counter is meaningless to EGPRS DL TBF.

24-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

24.18 C901180019 Number of EGPRS DL TBF establishment success on PCCCH/CCCH

Definition
Number of EGPRS DL TBF establishment success on PCCCH/CCCH.

Description
This counter counts the number of successful DL immediate assignment message sendings when BSC establishes EGPRS DL TBF.

Usage
This counter is used to find out the frequency of EGPRS DL TBF establishment success.

Measurement Point
When PS control plane receives successful immediate assignment sending message (SPS_ABIS_PACKET_SEND_PIA_IND) reported by BTS, the counter increments. The measurement point is A, as shown inFigure 24-16.
Figure 24-16 - Resource Application Failure Due To Abis Congestion (Assigned By UL)

Unit
Times

24.19 C901180020 Number of EGPRS DL TBF establishment success on PACCH

Definition
Number of EGPRS DL TBF establishment success on PACCH.
24-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
No statistics temporarily.

24.20 C901180023 Number of EGPRS DL TBF resource 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 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 EGPRS DL TBF establishment success.

Measurement Point
MS has established EGPRS DL TBF, and after PS control plane receives EV_MAC_UL_ASSIGN_REQ message sent from PS user plane, if resource application fails due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 24-17.
Figure 24-17 - Resource Application Failure Due To Abis Congestion (Assigned by UL)

Unit
Times

24-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.21 C901180024 Number of EGPRS DL TBF resource 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 application failure leads to DL resource reallocation failure. This counter counts the number of DL resource reallocation failure due to RR congestion. There are three causes for RR congestion: MS per channel (number of MS reaches the peak in each channel), TAI/TFI (no TAI or TFI) and no PDCH (no PS channel).

Usage
This counter is used to find out the frequency of EGPRS DL TBF resource reallocation failure due to RR congestion.

Measurement Point
MS has established EGPRS DL TBF, and after PS control plane receives EV_MAC_UL_ASSIGN_REQ message sent from PS user plane, if resource application fails due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 24-18.
Figure 24-18 - Resource Application Failure Due To RR Congestion (Assigned By UL)

24-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.22 C901180025 Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment
Definition
Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment

Description
After MS establishes EGPRS DL TBF, it shall establish UL TBF in PACCH. But resource application failure leads to DL resource reallocation failure. This counter counts the number of DL resource reallocation failures due to UPPB-DSP channel congestion.

Usage
This counter is used to find out the frequency of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion.

Measurement Point
MS has established EGPRS DL TBF, and after PS control plane receives EV_MAC_UL_ASSIGN_REQ message sent from PS user plane, if resource application fails due to UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown inFigure 24-19.

24-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Figure 24-19 - Resource Application Failure Due To UPPB-DSP Congestion (Assigned By UL)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.23 C901180026 Number of EGPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment
Definition
Number of EGPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment

Description
After MS establishes EGPRS DL TBF, it shall establish UL TBF in PACCH. This counter counts the number of DL resource application success.

Usage
This counter is used to find out the frequency of EGPRS DL TBF resource reallocation success.

Measurement Point
MS has established EGPRS DL TBF, and after PS control plane receives EV_MAC_UL_ASSIGN_REQ message sent from PS user plane, if resource application succeeds, the counter increments. The measurement point is A, as shown in Figure 24-20.
24-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 24-20 Successful Resource Application (Assigned By UL)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.24 C901180027 Number of allocated PDCH for 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
MS has established EGPRS DL TBF, and after PS control plane receives EV_MAC_UL_ASSIGN_REQ message sent from PS user plane, when resource application succeeds, the counter accumulates the PDTCH number. The measurement point is A, as shown inFigure 24-21.
24-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Figure 24-21 - Successful Resource Application (Assigned By UL)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.25 C901180028 Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment
Definition
Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment

Description
This counter counts the number of PDCH activate failure during the process of EGPRS DL TBF resource reallocation.

Usage
This counter is used to find out the frequency of PDCH activate failure during the process of EGPRS DL TBF resource reallocation.

Measurement Point
The measurement is taken at two time points listed below: l l When BSC receives PDCH activate failure message reported by BTS, the counter increments. The measurement point is A, as shown in If 'wait for PDCH activate & connection response' timer expires, and BSC has not received PDCH activate response message reported by BTS, the counter increments.
24-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 24-22 - PDCH Activation Failure

Unit
Times

24.26 C901180029 Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment
Definition
Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment

Description
This counter counts the number of connection failure due to BTS connection failure during the process of EGPRS DL TBF resource reallocation.

Usage
This counter is used to find out the frequency of connection failure due to BTS connection failure during the process of EGPRS DL TBF resource reallocation.

Measurement Point
The measurement is taken at two time points listed below: l If PS control plane receives connection failure message reported by connection module, and the cause of failure is BTS connection failure, the counter increments. The measurement point is A, as shown inFigure 24-23.

24-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Figure 24-23 - Connection Failed Due To BTS Connection Failure

If 'wait for PDCH activation & connection response' timer expires, and BSC has not received connection success response message reported by connection module, the counter increments.

Unit
Times

24.27 C901180030 Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for UL TBF establishment
Definition
Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for UL TBF establishment.

Description
This counter counts the number of connection failure due to BIU connection failure during the process of EGPRS DL TBF resource reallocation.

Usage
This counter is used to find out the frequency of connection failure due to BIU connection failure during the process of EGPRS DL TBF resource reallocation.

Measurement Point
If PS control plane receives connection failure message reported by connection module, and the cause of failure is BIU connection failure, the counter increments. The measurement point is A, as shown in Figure 24-24.

24-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 24-24 - Connection Failed Due To BIU Connection Failure

Unit
Times

24.28 C901180031 Number of EGPRS DL TBF resource reallocation success of channel activate and connection for UL TBF establishment
Definition
Number of EGPRS DL TBF resource reallocation success of channel activate and connection for UL TBF establishment

Description
This counter counts the number of channel activate success during the process of EGPRS DL TBF resource reallocation.

Usage
This counter is used to find out the frequency of channel activate success during the process of EGPRS DL TBF resource reallocation.

Measurement Point
When PS control plane 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 24-25.

24-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Figure 24-25 - Successful Activation And Connection

Unit
Times

24.29 C901180032 Number of EGPRS DL TBF resource reallocation failure due to UL TBF establishment
Definition
Number of EGPRS DL TBF resource reallocation failure due to UL TBF establishment.

Description
No statistics for this counter is meaningless to EGPRS DL TBF.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.30 C901180033 Number of EGPRS DL TBF resource reallocation success due to UL TBF establishment
Definition
Number of EGPRS DL TBF resource reallocation success due to UL TBF establishment.

Description
No statistics for this counter is meaningless to EGPRS DL TBF.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

24.31 C901180036 Number of EGPRS DL TBF resource reallocation failure due to Abis congestion for LLC transmission
Definition
Number of EGPRS DL TBF resource reallocation failure due to Abis congestion for LLC transmission.

Description
During EGPRS DL TBF transmission, PS user plane sends resource adjustment message (EV_MAC_RESOURCE_ADJU_REQ) to PS control plane due to UL/DL LLC changes. PS control plane applies for resource after it receives the message. This counter counts the number of resource application failures after PS control plane receives resource adjustment request during EGPRS 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 PS control plane receives resource adjustment request during EGPRS DL TBF transmission (the cause of database application failure is Abis congestion).

Measurement Point
After PS control plane receives EV_MAC_RESOURCE_ADJU_REQ message sent from PS user plane, if resource application fails due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 24-26 .
Figure 24-26 - Resource Application Failure Due To Abis Congestion (Resource Adjustment)

Unit
Times

24-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.32 C901180037 Number of EGPRS DL TBF resource reallocation failure due to RR congestion for LLC transmission
Definition
Number of EGPRS DL TBF resource reallocation failure due to RR congestion for LLC transmission.

Description
During EGPRS DL TBF transmission, PS user plane sends resource adjustment message (EV_MAC_RESOURCE_ADJU_REQ) to PS control plane due to UL/DL LLC changes. PS control plane applies for resource after it receives the message. This counter counts the number of resource application failures after PS control plane receives resource adjustment request during EGPRS DL TBF transmission (the cause of database application failure is RR congestion). There are three causes for RR congestion: MS per channel (number of MS reaches the peak in each channel), TAI/TFI (no TAI or TFI) and no PDCH (no PS channel).

Usage
This counter is used to find out the frequency of resource application failures after PS control plane receives resource adjustment request during EGPRS DL TBF transmission (the cause of database application failure is RR congestion).

Measurement Point
After PS control plane receives EV_MAC_RESOURCE_ADJU_REQ message sent from PS user plane, if resource application fails due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 24-27 .

24-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 24-27 - Resource Application Failure Due To RR Congestion (Resource Adjustment)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.33 C901180038 Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission
Definition
Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission.

Description
During EGPRS DL TBF transmission, PS user plane sends resource adjustment message (EV_MAC_RESOURCE_ADJU_REQ) to PS control plane due to UL/DL LLC changes. PS control plane applies for resource after it receives the message. This counter counts the number of resource reallocation failure after PS control plane 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 PS control plane receives resource adjustment request during EGPRS DL TBF transmission (the cause of database application failure is UPPB-DSP channel congestion).

24-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Measurement Point
After PS control plane receives EV_MAC_RESOURCE_ADJU_REQ message sent from PS user plane, if resource application fails due to UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown inFigure 24-28.
Figure 24-28 - Resource Application Failure Due To UPPB-DSP Channel Congestion (Resource Adjustment)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.34 C901180039 Number of EGPRS DL TBF resource reallocation success of channel allocation due to LLC transmission
Definition
Number of EGPRS DL TBF resource reallocation success of channel allocation due to LLC transmission.

Description
During EGPRS DL TBF transmission, PS user plane sends resource adjustment message (EV_MAC_RESOURCE_ADJU_REQ) to PS control plane due to UL/DL LLC changes. PS control plane applies for resource after receiving the message. This counter counts the number of resource reallocation success after PS control plane receives resource adjustment request during EGPRS DL TBF transmission.

Usage
This counter is used to find out the frequency of resource reallocation success after PS control plane receives resource adjustment request during EGPRS DL TBF transmission.
24-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
After PS control plane receives EV_MAC_RESOURCE_ADJU_REQ message sent from PS user plane, if resource application succeeds, the counter increments. The measurement point is A, as shown in Figure 24-29.
Figure 24-29 Successful Resource Application (Resource Adjustment)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.35 C901180040 Number of allocated PDCH for 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
During EGPRS DL TBF transmission, PS user plane sends resource adjustment message (EV_MAC_RESOURCE_ADJU_REQ) to PS control plane due to UL/DL LLC changes. PS control plane applies for resource after it receives the message. This counter counts the number of successfully allocated PDCH after PS control plane receives resource adjustment request during EGPRS DL TBF transmission.

Usage
This counter is used to find out the number of successfully allocated PDCH after PS control plane receives resource adjustment request during EGPRS DL TBF transmission.
24-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Measurement Point
After PS control plane receives EV_MAC_RESOURCE_ADJU_REQ message sent from PS user plane, if resource application succeeds, the counter accumulates the PDTCH number. The measurement point is A, as shown inFigure 24-30.
Figure 24-30 - Successful Resource Application (Resource Adjustment)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.36 C901180041 Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission
Definition
Number of Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission.

Description
This counter counts the number of PDCH activate failure after BSC receives resource adjustment request during EGPRS DL TBF transmission.

Usage
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
The measurement is taken at two time points listed below:
24-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

When BSC receives PDCH activate failure message reported by BTS, the counter increments. The measurement point is A, as shown inFigure 24-31.
Figure 24-31 - Connection Failed due to BTS Connection Failure

If 'wait for PDCH activate & connection response' timer expires, and BSC has not received PDCH activate response message reported by BTS, the counter increments.

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.37 C901180042 Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission
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
The measurement is taken at two time points listed below:
24-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

If PS control plane receives connection failure message reported by connection module, and the cause of failure is BTS connection failure, the counter increments. The measurement point is A, as shown in Figure 24-32.
Figure 24-32 - Connection Failed Due To BTS Connection Failure

If 'wait for PDCH activate & connection response' timer expires, and BSC has not received connection success response message reported by connection module, the counter increments.

Unit
Times

24.38 C901180043 Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for LLC transmission
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
This counter is used to find out the frequency of connection failure due to BIU connection failure after BSC receives resource adjustment request during EGPRS DL TBF transmission.

Measurement Point
If PS control plane receives connection failure message reported by connection module, and the cause of failure is BIU connection failure, the counter increments. The measurement point is A, as shown inFigure 24-33.
24-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 24-33 - Connection Failed Due To BIU Connection Failure

Unit
Times

24.39 C901180044 Number of EGPRS DL TBF resource reallocation success of channel activate and connection for LLC transmission
Definition
Number of EGPRS DL TBF resource reallocation success of channel activate and connection for LLC transmission

Description
This counter counts the number of channel activate success after BSC receives resource adjustment request during EGPRS DL TBF transmission.

Usage
This counter is used to find out the frequency of channel activate success after BSC receives resource adjustment request during EGPRS DL TBF transmission.

Measurement Point
When PS control plane 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 in Figure 24-34.

24-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Figure 24-34 - Successful Activation And Connection

Unit
Times

24.40 C901180045 Number of EGPRS DL TBF resource reallocation failure due to LLC transmission
Definition
Number of EGPRS DL TBF resource reallocation failure due to LLC transmission.

Description
No statistics for this counter is meaningless to EGPRS DL TBF.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24.41 C901180046 Number of EGPRS DL TBF resource reallocation success due to LLC transmission
Definition
Number of EGPRS DL TBF resource reallocation success due to LLC transmission.

Description
No statistics for this counter is meaningless to EGPRS DL TBF.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

24-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

24.42 C901180047 Number of EGPRS DL TBF release 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 PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_RANUMC_REL_CMD) reported by PS user plane, if the cause of release is flush LL, and EGPRS DL TBF exists, the counter increments. The measurement point is A, as shown in Figure 24-35.
Figure 24-35 - Release Request Due To Flush LL

Unit
Times

24.43 C901180048 Number of EGPRS DL TBF release 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Usage
This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests due to suspend requests received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_RANUMC_REL_CMD) reported by PS user plane, if the cause of release is SUSPEND, and EGPRS DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 24-36.
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
This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests (EV_RANCCM_PDCH_REL) received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_RANCCM_PDCH_REL) reported by CS control plane, if EGPRS DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 24-37.

24-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 24-37 - Release Request Due To PDCH REL

Unit
Times

24.45 C901180050 Number of EGPRS DL TBF normal release due to user plane requests
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 Release Request by CS control plane.

Usage
This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests due to abnormal Release Request by CS control plane received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_MAC_REL_IND) reported by CS control plane, if the cause of release is abnormal Release Request by CS control plane, 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

24.46 C901180051 Number of EGPRS DL TBF abnormal release due to user plane requests
Definition
Number of EGPRS DL TBF abnormal release due to user plane requests

Description
This counter counts the number of EGPRS DL TBF abnormal release due to abnormal Release Request by MAC.

Usage
This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests due to abnormal Release Request by MAC received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_MAC_REL_IND) reported 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-39.
Figure 24-39 - Release Request due to Abnormal Release Request by MAC

Unit
Times

24.47 C901180052 Number of EGPRS DL TBF release due to NSVC unavailability

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests due to NSVC unavailability received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_RANUMC_REL_CMD) reported by PS user plane, 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

24.48 C901180053 Number of EGPRS DL TBF release due to BVC unavailability

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
This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests due to BVC unavailability received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_RANUMC_REL_CMD) reported by PS user plane, if the cause of release is BVC unavailability, and EGPRS DL TBF exists, the counter increments. The measurement point is A, as shown in Figure 24-41.

24-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Figure 24-41 - Release Request Due To BVC Unavailability

Unit
Times

24.49 C901180054 Number of EGPRS DL TBF release due to Index exception

Definition
Number of EGPRS DL TBF release due to index exception.

Description
This counter counts the number of EGPRS DL TBF release due to index exception. If TLLI conflict is detected by control plane When the MS try to access a new cell, this counter will be added 1, then the old instance is released too.

Usage
This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests due to index exception in control plane.

Measurement Point
When MS accesses a new cell, TLLI conflict will be detected by control plane. At the same time, the old instance will be released. The release reason is index exception. If current TBF is EGPRS DL TBF, the counter will be added one. The measurement point is A, as shown inFigure 24-42 .
Figure 24-42 - RELEASE REQUEST due to index exception

24-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

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 increments. The measurement point is A, as shown in Figure 24-43.
Figure 24-43 Downlink EGPRS Requesting Resource Successfully

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

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.
Figure 24-44 Downlink EGPRS Requesting Resource Successfully

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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 increments. The measurement point is A, as shown in Figure 24-45.

24-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 24-45 Downlink EGPRS Requesting Resource Successfully

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 24 Downlink EGPRS Data TBF Statistics

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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 counter increments. The measurement point is A, as shown in Figure 24-47.
Figure 24-47 Releasing Downlink EGPRS TBF

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

24-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

24.55 C901180060 Times of Downlink EGPRS TBF Requesting DLDC Resources 24.56 C901180061 Times of Allocating Downlink DLDC Resources for EGPRS TBF

24-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 connection failed ....................................................................................................25-30 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 establishhment failure on PCCCH/CCCH .25-33 C901190033 Number of GPRS UL TBF establishment failure on PACCH...............25-34 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 congestion for DL TBF establishment .....................................................................25-37 C901190040 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for DL TBF establishment.....................................25-38 C901190041 Number of GPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment .................................................................25-39 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 connection failure for DL TBF establishment ..........................................................25-43 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 TBF establishment .................................................................................................25-45 C901190051 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission.............................................................................25-46 C901190052 Number of GPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission.............................................................................25-47

25-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

C901190053 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission ............................................25-48 C901190054 Number of GPRS UL TBF resource reallocation success of channel allocation due to LLC transmission .........................................................................25-49 C901190055 Number of allocated PDCH for GPRS UL TBF resource reallocation due to LLC transmission.........................................................................................25-50 C901190056 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for LLC transmission .......................................................................25-51 C901190057 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for LLC transmission ..................................................................25-52 C901190058 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for LLC transmission ..................................................................25-53 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 C901190064 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for resource request .............................................................................25-55 C901190065 Number of GPRS UL TBF resource reallocation failure due to RR congestion for resource request .............................................................................25-56 C901190066 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for resource request .............................................25-58 C901190067 Number of GPRS UL TBF resource reallocation success due to resource request ....................................................................................................25-59 C901190068 Number of allocated PDCH for GPRS UL TBF resource reallocation due to resource request..........................................................................................25-60 C901190069 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for resource request........................................................................25-61 C901190070 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for resource request...................................................................25-62 C901190071 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for resource request...................................................................25-63 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 resource request ....................................................................................................25-65 C901190074 Number of GPRS UL TBF resourse reallocation success due to resource request ....................................................................................................25-65 C901190075 Number of GPRS UL TBF release due to flush LL .............................25-65 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
25-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.

25.2 C901190002 Number of GPRS UL TBF 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 measurement point is A, as shown inFigure 25-1.

25-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Figure 25-1 - Channel Request

Usage
Times

25.3 C901190003 Number of EGPRS UL TBF establishment requests on CCCH

Definition
Number of EGPRS UL TBF establishment requests on CCCH.

Description
This counter is not meaningful in UL GPRS TBF and is not used.

25.4 C901190004 Number of GPRS UL TBF 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC receives channel requests on PCCCH from MS, the counter increments. The measurement point is A, as shown inFigure 25-2.
Figure 25-2 - Packet Channel Request

Unit
Times

25.5 C901190005 Number of EGPRS UL TBF establishment requests on PCCCH

Definition
Number of EGPRS UL TBF establishment requests on PCCCH.

Description
This counter is not meaningful in UL GPRS TBF statistic, and is not used.

25.6 C901190006 Number of GPRS UL TBF establishment requests on PACCH

Definition
Number of GPRS UL TBF establishment requests on PACCH.

Description
The counter counts the number of UL GPRS TBF establishment attempts on PACCH.

25-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Usage
This counter is used to find out the number of UL GPRS TBF establishment attempts on PACCH under the situation when DL GPRS TBF is already established.

Measurement Point
In the situation when DL GPRS TBF is established, PS control plane receives UL assignment request message from PS user plane, the counter increments. The measurement point is A, as shown inFigure 25-3 .
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 counter increments. The measurement point is A, as shown inFigure 25-4.
Figure 25-4 - Channel Requests on CCCH due to One Phase Access

If BSC receives channel requests from MS on CCCH due to one phase access, the counter increments. The measurement point is A, as shown inFigure 25-5.
Figure 25-5 - Packet Channel Requests on CCCH due to One Phase Access

Unit
Times

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

25-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

25.8 C901190008 Number of cell attempts for UL assignment due to single block packet access
Definition
Number of cell attempts for UL assignment due to single block packet access.

Description
This counter counts the number of packet channel requests on PCCCH when MS attempts UL GPRS TBF establishment due to single block packet access.

Usage
This counter is used to find out the number of packet channel requests when MS attempting UL GPRS TBF establishment due to single block packet access.

Measurement Point
If BSC receives channel requests on PCCCH from MS due to single block packet access. The measurement point is A, as shown inFigure 25-6.
Figure 25-6 - Channel Request due to Single Block Packet Access

Unit
Times

25.9 C901190009 Number of cell attempts for UL assignment due to response paging
Definition
Number of cell attempts for UL assignment due to response paging.

25-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of packet channel requests when MS attempting UL GPRS TBF establishment due to response paging.

Usage
This counter is used to find out the number of packet channel requests when MS attempting UL GPRS TBF establishment due to response paging.

Measurement Point
When BSC receives channel requests on PCCCH from MS due to response paging, the counter increments. The measurement point is A, as shown inFigure 25-7.
Figure 25-7 - Channel Request Due To Response Paging

Unit
Times

25.10 C901190010 Number of cell attempts for UL 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
This counter is used to find out the number of packet channel requests when MS attempting UL GPRS TBF establishment due to cell update.
25-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Measurement Point
When BSC receives channel requests on PCCCH from MS duet to cell update, the counter increments. The measurement point is A, as shown inFigure 25-8 .
Figure 25-8 - Channel Requests due to Cell Update

Unit
Times

25.11 C901190011 Number of cell attempts for UL 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
This counter is used to find out the number of packet channel requests when MS attempting UL GPRS TBF establishment due to mobile management.

Measurement Point
If BSC receives channel requests on PCCCH from MS due to mobile management, the counter increments. The measurement point is A, as shown in Figure 25-9.

25-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 25-9 - Channel Request Due To Mobile Management

Unit

25.12 C901190012 Number of cell attempts for UL assignment due to TWO PHASE access
Definition
Number of cell attempts for UL assignment due to TWO PHASE access

Description
This counter counts the number of channel requests on CCCH when MS attempting UL GPRS TBF establishment or the number of packet channel requests on PCCCH due to two phase access.

Usage
This counter is used to find out the number of UL GPRS TBF establishment attempts due to two phase access.

Measurement Point
The counter accumulates at the following two time points: l If BSC receives channel requests from MS on CCCH due to two phase access, the counter increments. The measurement point is A, as shown inFigure 25-10.

25-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Figure 25-10 - Channel Requests On PCCCH Due To Two Phase Access

If BSC receives channel requests from MS on CCCH due to one phase access, the counter increments. The measurement point is A, as shown inFigure 25-11.
Figure 25-11 - Packet Channel Requests On PCCCH Due To Two Phase Access

Unit
Times

Related Features
GB-03-05-008 Two Phase Access

25.13 C901190013 Number of cell attempts for UL 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of UL GPRS TBF establishment attempts due to short access.

Measurement Point
If BSC receives packet channel requests on PCCCH from MS on PCCCH due to short access, the counter increments. The measurement point is A, as shown inFigure 25-12.
Figure 25-12 - Packet Channel Requests On PCCCH Due To Short Access

Unit
Times

25.14 C901190015 Number of GPRS UL TBF establishment failure due to Abis congestion
Definition
Number of GPRS UL TBF establishment failure due to Abis congestion.

Description
The counter records the number of DB resource application failure when attempting UL GPRS TBF establishment due to Abis congestion.

Usage
This counter is used to find out the number of DB resource application failure when attempting UL GPRS TBF establishment due to Abis congestion.

Measurement Point
The counter accumulates at the following three time points:
25-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

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 point is A, as shown inFigure 25-13.
Figure 25-13 - DB Resource Requests Failure Due To Abis Congestion (CCCH)

If PS control panel receives channel requests from MS on CCCH and fails to apply for DB resource due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 25-14.
Figure 25-14 - DB Resource Requests Failure Due To Abis Congestion (PCCCH)

If PS control panel receives UL assignment request messages from PS user plane on CCCH and fails to apply for DB resource due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 25-15.
Figure 25-15 - DB Resource Requests Failure Due To Abis Congestion (DL GPRS TBF Already Established)

Unit
Times

25-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.15 C901190016 Number of GPRS UL TBF establishment failure due to RR congestion

Definition
Number of GPRS UL TBF establishment failure due to RR congestion.

Description
The counter records the number of DB resource request failure when attempting UL GPRS TBF establishment due to radio resource congestion. There are three causes that lead to radio resource congestion: MS per channel (MS number on each channel reaches its maximum), no TAI/TFI, and no PDCH.

Usage
This counter is used to find out the number of DB resource application failure when attempting UL GPRS TBF establishment due to RR congestion.

Measurement Point
The counter accumulates at the following three time points: l If PS control plane receives channel requests from MS on CCCH and fails to apply for DB resource due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 25-16.
Figure 25-16 - DB Resource Requests Failure Due To RR Congestion (CCCH)

If PS control panel receives channel requests from MS on CCCH and fails to apply for DB resource due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 25-17.

25-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Figure 25-17 - DB Resource Requests Failure Due To RR Congestion (PCCCH)

If PS control panel receives UL assignment request messages from PS user plane on CCCH and fails to apply for DB resource due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 25-18.
Figure 25-18 - DB Resource Requests Failure Due To Abis Congestion (DL GPRS TBF Already Established)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.16 C901190017 Number of GPRS UL TBF establishment failure due to UPPB-DSP channel congestion
Definition
Number of GPRS UL TBF establishment failure due to UPPB-DSP channel congestion.

Description
The counter records the number of DB resource application failure when attempting UL GPRS TBF establishment due to UPPB-DSP channel congestion.
25-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of DB resource application failure when attempting UL GPRS TBF establishment due to UPPB-DSP channel congestion.

Measurement Point
The counter accumulates at the following three time points: l If PS control plane receives channel requests from MS on CCCH and fails to apply for DB resource due to UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown in Figure 25-19.
Figure 25-19 DB Resource Requests Failure Due To UPPB-DSP Channel Congestion (CCCH)

If PS control panel receives channel requests from MS on PCCCH and fails to apply for DB resource due to UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown inFigure 25-20.
Figure 25-20 - DB Resource Requests Failure Due To Abis Congestion (PCCCH)

If PS control panel receives UL assignment request messages from PS user plane 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 is A, as shown inFigure 25-21.

25-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Figure 25-21 - DB Resource Requests Failure Due To DPPB-DSP Congestion (DL GPRS TBF Already Established)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.17 C901190018 Number of GPRS UL TBF establishment channel allocate success

Definition
Number of GPRS UL TBF establishment channel allocate success.

Description
This counter counts the number of DB resource request successes when attempting UL GPRS TBF establishment.

Usage
This counter is used to find out the number of DB resource request successes when attempting UL GPRS TBF establishment.

Measurement Point
The counter accumulates at the following three time points: 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 shown inFigure 25-22.

25-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 25-22 - DB Resource Request Successes (CCCH)

If PS control panel receives channel requests from MS on PCCCH and succeed in applying for DB resource, the counter increments. The measurement point is A, as shown inFigure 25-23.
Figure 25-23 - DB Resource Request Successes (PCCCH)

If only GPRS is supported in the network, PS control plane receives EGPRS channel request on CCCH or on PCCCH from MS, and DB resource request succeeds, the counter increments.

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

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
The counter accumulates at the following three time points: 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 measurement point is A, as shown in Figure 25-24.
Figure 25-24 - Channel Request Successes On CCCH Due To One Phase Access

If BSC receives channel requests from MS on CCCH due to one phase access, the counter increments. The measurement point is A, as shown inFigure 25-25.
Figure 25-25 - Packet Channel Request Successes On CCCH Due To One Phase Access

If only GPRS is supported in the network, PS control plane receives EGPRS channel request on CCCH or on PCCCH from MS, and DB resource request succeeds, the counter increments.

25-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

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

25.19 C901190020 Number of cell success for GPRS 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 measurement point is A, as shown inFigure 25-26.
Figure 25-26 - Channel Requests Successes Due To Single Block Packet Access

Unit
Times

25-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

25.20 C901190021 Number of cell success for GPRS 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
This counter is used to find out the number of successful UL GPRS TBF establishment due to response paging.

Measurement Point
When PS control plane receives channel requests on PCCCH from MS due to response paging and DB resource request succeeds, the counter increments. The measurement point is A, as shown inFigure 25-27.
Figure 25-27 - DB Resource Request Successes Due To Response Paging

Unit
Times

25.21 C901190022 Number of cell success for GPRS UL assignment due to cell updating
Definition
Number of cell success for GPRS UL assignment due to cell updation.

25-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
The counter counts the number of successful UL GPRS TBF establishment due to cell update

Usage
This counter is used to find out the number of successful UL GPRS TBF establishment due to cell update.

Measurement Point
When PS control plane receives channel requests on PCCCH from MS due to cell update and DB resource request succeeds, the 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

25.22 C901190023 Number of cell success for GPRS 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
This counter is used to find out the number of successful UL GPRS TBF establishment due to mobile management.
25-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

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 measurement point is A, as shown inFigure 25-29.
Figure 25-29 - DB Resource Request Successes Due To Mobile Management (PCCCH)

Unit
Times

25.23 C901190024 Number of cell success for GPRS 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
This counter is used to find out the number of successful UL GPRS TBF establishment due to two phase access.

Measurement Point
The counter accumulates at the following two time points: 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 is A, as shown inFigure 25-30.

25-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 25-30 - DB Resource Request Successes Due To Two Phase Access (CCCH)

If BSC receives channel requests from MS on PCCCH due to two phase access and DB resource request succeeds, the counter increments. The measurement point is A, as shown inFigure 25-31.
Figure 25-31 - DB Resource Request Successes On PCCCH Due To Two Phase Access

Unit
Times

Related Features
ZGB-03-05-008Two Phase Access

25.24 C901190025 Number of cell success for GPRS UL assignment due to short access
Definition
Number of cell success for GPRS UL assignment due to short access.

25-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Description
This counter counts the number of successful UL GPRS TBF establishment due to short access.

Usage
This counter is used to find out the number of successful UL GPRS TBF establishment due to short access.

Measurement Point
The counter accumulates at the following two time points: 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, as shown inFigure 25-32.
Figure 25-32 - DB Resource Request Successes Due To Short Access (PCCCH)

If only GPRS is supported in the network, PS control plane receives GPRS channel request on CCCH or on PCCCH from MS, and DB resource request succeeds, the counter increments.

Unit
Times

25.25 C901190026 Number of allocated PDCH for GPRS UL TBF establishment

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of successfully assigned PDTCH when UL GPRS TBF successfully established.

Measurement Point
The counter accumulates at the following three time points: 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, as shown inFigure 25-33.
Figure 25-33 - DB Resource Request Successes Due To Short Access (PCCCH)

When PS control plane receives packet channel requests on PCCCH from MS, the counter increments. The measurement point is A, as shown inFigure 25-34.
Figure 25-34 - UL GPRS TBF Establishment On PCCCH/CCCH

If only GPRS is supported in the network, PS control plane receives EGPRS channel request on CCCH or on PCCCH from MS, and DB resource request succeeds, the counter increments.

25-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.26 C901190027 Number of GPRS UL TBF establishment failure due to channel activate failed
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
The counter accumulates at the following two time points: l When BSC receives PDTCH channel activate failure message reported by BTS, the counter increments. The measurement point is A, as shown inFigure 25-35.
Figure 25-35 - PDCH Activation Failure

When 'wait for PDTCH channel activation and connection response' counter times out and BSC fails to receive PDTCH activate response message reported by BTS, this counter increments.

25-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

25.27 C901190028 Number of GPRS UL TBF establishment failure due to BTS connection failed
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
The counter accumulates at the following two time points: l When PS control plane receives connection failure message reported by connection module due to BTS connection failure, the counter increments. The measurement point is A, as shown in Figure 25-36.
Figure 25-36 - Connection Failed due to BTS Connection Failure

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

25.28 C901190029 Number of GPRS UL TBF establishment failure due to BIU connection failed
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 (including initially establish UL TBF and establish UL TBF when DL TBF exists) due to BIU connection failure.

Measurement Point
When PS control plane receives connection failure message reported by connection modules due to BIU connection failure, the counter increments. The measurement point is A, as shown inFigure 25-37.
Figure 25-37 - Connection Failed Due To BIU Connection Failure

Usage
Times

25-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

25.29 C901190030 Number of GPRS UL TBF channel activate establishment success

Definition
Number of GPRS UL TBF channel activate establishment success.

Description
This counter counts the number of channel activate and connection successes when establishing UL GPRS TBF.

Usage
This counter is used to find out the number of channel activate and connection successes when establishing UL GPRS TBF.

Measurement Point
When PS control plane receives channel activate response message reported by BTS and connection successes acknowledgement message reported by connection module, the counter increments. The measurement point is A, as shown inFigure 25-38.
Figure 25-38 - Resource Application Failure Due To Abis Congestion (Resource Adjustment)

Unit
Times

25.30 C901190031 Number of GPRS UL TBF establishment failure due to not receive PIA
Definition
Number of GPRS UL TBF establishment failure due to not receive PIA.
25-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

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
The counter accumulates at the following two time points: l l When PS control plane receives immediate assignment failure message reported by BTS, the counter increments. When 'wait for immediate assignment and sending indication' counter times out and BSC fails to receive immediate assignment and sending indication message, the counter increments.

Usage
Times

25.31 C901190032 Number of GPRS UL TBF establishhment failure on PCCCH/CCCH

Definition
Number of GPRS UL TBF establishment failure on PCCCH/CCCH.

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 measurement point is A, as shown inFigure 25-39 .

25-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 25-39 - UL GPRS TBF Establishment On PCCCH/CCCH

Unit
Times

25.32 C901190033 Number of GPRS UL TBF establishment failure on PACCH

Definition
Number of GPRS UL TBF establishment failure on PACCH.

Description
This counter is not used currently.

25.33 C901190034 Number of GPRS UL TBF establishment success on PCCCH/CCCH

Definition
Number of GPRS UL TBF establishment success on PCCCH/CCCH

Description
This counter counts the number of successful UL GPRS TBF establishment and receiving MS TLL1.

25-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Usage
This counter is used to find out the number of successful UL GPRS TBF establishment and receiving MS TLL1.

Measurement Point
The counter accumulates at the following two time points: 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 increments. The measurement point is A, as shown inFigure 25-40.
Figure 25-40 - UL One-Phase-Access Resource Assignment Successes

PS control plane receives resource request message from PS user plane in the premise of two phase access, the counter 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

25.34 C901190035 Number of GPRS UL TBF establishment success on PACCH

Definition
Number of GPRS UL TBF establishment success on PACCH.

Description
This counter is not used currently.

25.35 C901190038 Number of GPRS UL TBF resource 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Figure 25-42 - Database Application Failure Due To Abis Congestion

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.36 C901190039 Number of GPRS UL TBF resource 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
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. 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 GPRS TBF reallocation failure due to RR congestion.

25-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 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
ZGO-03-02-002 Enhancement on Channel Allocation

25.37 C901190040 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for DL TBF establishment
Definition
Number of GPRS UL TBF resource reallocation failure due to UPPB -DSP channel congestion for DL TBF establishment.

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 UPPB-DSP channel resource congestion.

Usage
This counter is used to find out the number of UL GPRS TBF reallocation failure due to UPPB-DSP channel congestion.
25-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

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 UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown inFigure 25-44.
Figure 25-44 - Database Application Failure due to UPPB-DSP Channel Congestion

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.38 C901190041 Number of GPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment
Definition
Number of GPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment.

Description
The counter records the number of successful DL TBF establishment on PACCH when UL GPRS TBF is already established.

Usage
This counter is used to find out the number of DL GPRS TBF reallocation successes.

25-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 succeeds, the counter increments. The measurement point is A, as shown inFigure 25-45.
Figure 25-45 Successful Resource Application

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.39 C901190042 Number of allocated PDCH for 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.

25-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

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 succeeds, the counter increments. The measurement point is A, as shown inFigure 25-46.
Figure 25-46 - Successful Resource Application

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.40 C901190043 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for DL TBF establishment
Definition
Number of GPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment.

Description
The counter records the number of PDTCH activate failure during UL GPRS TBF resource reallocation.

Usage
This counter is used to find out the number of PDTCH activate failure during UL GPRS TBF resource reallocation.

Measurement Point
The measurement is taken at two time points listed below:
25-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

When BSC receives PDTCH channel activate failure message from BTS, the counter increments. The measurement point is A, as shown inFigure 25-47 .
Figure 25-47 - PDTCH Activation Failure

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive PDTCH channel activate response message from BTS, the counter increments.

Unit
Times

25.41 C901190044 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for DL TBF establishment
Definition
Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for DL TBF establishment.

Description
The counter records the number of BTS connection failure during UL GPRS TBF resource reallocation.

Usage
This counter is used to find out the number of BTS connection failure during UL GPRS TBF resource reallocation.

Measurement Point
The measurement is taken at two time points listed below: l When PS control plane receives connection failure message from connection module due to BTS connection failure, the counter increments. The measurement point is A, as shown inFigure 25-48 .
25-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Figure 25-48 - Connection Failed due to BTS Connection Failure

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive connection success message from connection module, the counter increments.

Unit
Times

25.42 C901190045 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for DL TBF establishment
Definition
Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for DL TBF establishment.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 25-49 - Connection Failed Due To BIU Connection Failure

Unit
Times

25.43 C901190046 Number of GPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment
Definition
Number of GPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment

Description
The counter records the number of channel activate and connection successes during UL GPRS TBF resource reallocation.

Usage
This counter is used to find out the number of channel activate and connection successes during UL GPRS TBF resource reallocation.

Measurement Point
When PS control plane receives channel activate ack message and connection success ack message from connection module due to BIU connection failure, the counter increments. The measurement point is A, as shown inFigure 25-50.

25-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Figure 25-50 - Resource Application Failure Due To Abis Congestion (Resource Adjustment)

Unit
Times

25.44 C901190047 Number of GPRS UL TBF resourse reallocation failure due to DL TBF establishment
Definition
Number of GPRS UL TBF resource reallocation failure due to DL TBF establishment.

Description
This counter is not used currently.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.45 C901190048 Number of GPRS UL TBF resourse reallocation success due to DL TBF establishment
Definition
Number of GPRS UL TBF resource reallocation success due to DL TBF establishment.

Description
This counter is not used currently.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation
25-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

25.46 C901190051 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for LLC 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 measurement point is A, as shown inFigure 25-51.
Figure 25-51 - Resource Application Failure Due To Abis Congestion

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation
25-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

25.47 C901190052 Number of GPRS UL TBF resource reallocation failure due to RR congestion for LLC 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 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 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
When PS control plane receives resource reallocation message from PS user plane, and DB resource request fails due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 25-52 .
Figure 25-52 - Resource Application Failure Due To RR Congestion (Resource Adjustment)

Unit
Times
25-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.48 C901190053 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission
Definition
Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission.

Description
During UL EGPRS TBF transmission process, PS user plane sends resource reallocation message to PS control plane due to LLC frame change; PS control plane requests DBresource after receiving the 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. The measurement point is A, as shown in Figure 25-53.
Figure 25-53 - Resource Application Failure Due To UPPPB-DSP Channel Congestion (Resource Adjustment)

25-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.49 C901190054 Number of GPRS UL TBF resource reallocation success of channel allocation due to LLC transmission
Definition
Number of GPRS UL TBF resource reallocation success of channel allocation due to LLC transmission

Description
During UL EGPRS TBF transmission process, PS user plane sends resource reallocation message to PS control plane due to LLC frame change; PS control plane requests DB resource after receiving the message. The counter records the number of DB resource 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
When PS control plane receives resource reallocation message from PS user plane, and DB resource request succeeds, the counter increments. The measurement point is A, as shown inFigure 25-54.
Figure 25-54 Release Request Due To Flush LL

Unit
Times
25-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.50 C901190055 Number of allocated PDCH for 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
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 DB 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
When PS control plane receives resource reallocation message from PS user plane, and DB resource request succeeds, the counter increments. The measurement point is A, as shown inFigure 25-55.
Figure 25-55 - Release Request Due To Flush LL

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation
25-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

25.51 C901190056 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for LLC transmission
Definition
Number of GPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment

Description
The counter records the number of PDTCH activate failure after BSC receiving resource reallocation request during UL GPRS TBF resource reallocation.

Usage
This counter is used to find out the number of PDTCH activate failure during UL GPRS TBF resource reallocation.

Measurement Point
The counter accumulates at the following two time points: l When BSC receives PDTCH channel activate failure message from BTS, the counter increments. The measurement point is A, as shown inFigure 25-56.
Figure 25-56 - PDTCH Activation Failure

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive PDTCH channel activate response message from BTS, the counter increments.

Unit
Times

25-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

25.52 C901190057 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for LLC transmission
Definition
Number of GPRS UL TBF resource reallocation failure due to BTS connection failure for LLC transmission

Description
The counter records the number of connection failure due to BTS connection failure after BSC receiving resource reallocation request during UL GPRS TBF transmission.

Usage
This counter is used to find out the number of BTS connection failure during UL GPRS TBF resource transmission.

Measurement Point
The counter accumulates at the following two time points: l When PS control plane receives connection failure message from connection module due to BTS connection failure, the counter increments. The measurement point is A, as shown inFigure 25-57.
Figure 25-57 - Connection Failed Due To BTS Connection Failure

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive connection success message from connection module, the counter increments.

Unit
Times

25-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

25.53 C901190058 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for LLC transmission
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
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-58.
Figure 25-58 - Connection Failed due to BIU Connection Failure

Unit
Times

25-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

25.54 C901190059 Number of GPRS UL TBF resourse reallocation success of channel activate for LLC transmission
Definition
Number of GPRS UL TBF resource reallocation success of channel activate for LLC transmission.

Description
The counter records the number of channel activate and connection successes during UL GPRS TBF transmission.

Usage
This counter is used to find out the number of channel activate and connection successes during UL GPRS TBF tranmission.

Measurement Point
When PS control plane receives channel activate ack message and connection success ack message from connection module due to BIU connection failure, the counter increments. The measurement point is A, as shown in Figure 25-59.
Figure 25-59 - Successful Activation And Connection

Unit
Times

25.55 C901190060 Number of GPRS UL TBF resourse reallocation failure due to LLC transmission
Definition
Number of GPRS UL TBF resource reallocation failure due to LLC transmission.

25-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Description
This counter is not used currently.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.56 C901190061 Number of GPRS UL TBF resourse reallocation success due to LLC transmission
Definition
Number of GPRS UL TBF resource reallocation success due to LLC transmission.

Description
This counter is not used currently.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.57 C901190062 Number of GPRS UL TBF resource reallocation requests for resource request
Definition
Number of GPRS UL TBF resource reallocation requests for resource request.

Description
This counter is not used currently.

25.58 C901190064 Number of GPRS UL TBF resource 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 A, as shown in Figure 25-60.
Figure 25-60 - DB Resource Requests Failure Due To Abis Congestion (Resource Request)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.59 C901190065 Number of GPRS UL TBF resource 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

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
This counter is used to find out the number of DB resource request failure after PS control 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
PS control plane receives resource request message from PS user plane, and DB resource request fails due to RR congestion, the counter increments. The measurement point is A, as shown in Figure 25-61.
Figure 25-61 - DB Resource Requests Failure Due To RR Congestion

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

25.60 C901190066 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for resource request
Description
The counter records the number of DB resource request failure after PS control plane receives resource request from MS due to UPPB-DSP channel congestion 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 due to UPPB-DSP channel congestion 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 RR congestion, the counter increments. The measurement point is A, as shown in Figure 25-62.
Figure 25-62 DB Resource Requests Failure due to UPPB-DSP Channel Congestion (Resource Request)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

25.61 C901190067 Number of GPRS UL TBF resource 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
PS control plane receives resource request message from PS user plane, and DB resource 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
ZGO-03-02-002 Enhancement on Channel Allocation

25-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

25.62 C901190068 Number of allocated PDCH for GPRS 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 two-phase access and UL TBF transmission).

Measurement Point
PS control plane receives resource request message from PS user plane, and DB resource request succeeds, the counter increments. The measurement point is A, as shown in Figure 25-64.
Figure 25-64 DB Resource Requests Successes (Resource Request)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

25.63 C901190069 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for resource request
Definition
Number of GPRS UL TBF resource reallocation failure due to channel activate failure for resource request.

Description
The counter records the number of PDTCH activate failure during UL GPRS TBF resource reallocation after PS control plane receives resource request message.

Usage
The counter records the number of PDTCH activate failure during UL GPRS TBF resource reallocation after PS control plane receives resource request message in UL GPRS TBF process (including UL two-phase access and one-phase TBF transmission).

Measurement Point
The counter accumulates at the following two time points: l When BSC receives PDTCH channel activate failure message from BTS, the counter increments. The measurement point is A, as shown inFigure 25-65.
Figure 25-65 - PDTCH Activation Failure

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive PDTCH channel activate response message from BTS, the counter increments.

Unit
Times

25-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

25.64 C901190070 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for resource request
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
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 in UL GPRS TBF process (including UL two-phase access and one-phase TBF transmission).

Measurement Point
The counter accumulates at the following two time points: l When PS control plane receives connection failure message from connection module due to BTS connection failure, the counter increments. The measurement point is A, as shown inFigure 25-66 .
Figure 25-66 - Connection Failed due to BTS Connection Failure

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive connection success message from connection module, the counter increments.

Unit
Times
25-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

25.65 C901190071 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for resource request
Definition
Number of GPRS UL TBF resource reallocation failure due to BIU connection failure for resource request

Description
The counter records the number of connection failure due to BIU connection failure during UL GPRS TBF resource reallocation after PS control plane receives resource request message.

Usage
The counter records the number of connection failure due to BIU connection failure during UL GPRS TBF resource reallocation after PS control plane receives resource request message in UL GPRS TBF process (including UL two-phase access and one-phase TBF transmission).

Measurement Point
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-67.
Figure 25-67 - Connection Failed Due To BIU Connection Failure

Unit
Times

25-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

25.66 C901190072 Number of GPRS UL TBF resource reallocation success of channel activate and connection for resource request
Definition
Number of GPRS UL TBF resource reallocation success of channel activate and connection for resource request

Description
The counter records the number of channel activate and connection successes during UL GPRS TBF resource reallocation after PS control plane receives resource request message.

Usage
The counter records the number of channel activate and connection failure during UL GPRS TBF resource reallocation after PS control plane receives resource request message in UL GPRS TBF process (including UL two-phase access and one-phase TBF transmission).

Measurement Point
When PS control plane receives channel activate ack message and connection success ack message from connection module due to BIU connection failure, the counter increments. The measurement point is A, as shown inFigure 25-68.
Figure 25-68 - Resource Application Failure Due To Abis Congestion (Resource Adjustment)

Unit
Times

25-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

25.67 C901190073 Number of GPRS UL TBF resourse reallocation failure due to resource request
Definition
Number of GPRS UL TBF resource reallocation failure due to resource request.

Description
This counter is not used currently.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

25.68 C901190074 Number of GPRS UL TBF resourse reallocation success due to resource request
Definition
Number of GPRS UL TBF resource reallocation failure due to reallocation success due to resource request.

Description
This counter is not used currently.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 point is A, as shown in Figure 25-69.
Figure 25-69 - Release Request Due To Flush LL

Unit
Times

25.70 C901190076 Number of GPRS UL TBF release due to GPRS suspend requests
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 point is A, as shown inFigure 25-70.

25-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

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, as shown inFigure 25-71.
Figure 25-71 - Release Request due to PDCH REL

Unit
Times

25-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

25.72 C901190078 Number of GPRS UL TBF normal release due to user plane requests
Definition
Number of GPRS UL TBF normal release due to user plane requests.

Description
This counter counts the number of UL GPRS TBF normal release due to user plane requests.

Usage
This counter is used to find out the number of UL GPRS TBF normal release due to user plane requests.

Measurement Point
When PS control plane of BSC receives NORMAL RELEASE REQUEST message from PS user plane when UL GPRS TBF exists, the counter increments. The measurement point is A, as shown inFigure 25-72.
Figure 25-72 - Normal Release Request

Unit
Times

25.73 C901190079 Number of GPRS UL TBF abnormal release due to user plane requests
Definition
Number of GPRS UL TBF abnormal release due to user plane requests.

Description
This counter counts the number of UL GPRS TBF abnormal release due to user plane requests.
25-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Usage
This counter is used to find out the number of UL GPRS TBF abnormal release due to user plane requests.

Measurement Point
When PS control plane receives ABNORMAL RELEASE REQUEST message from PS user plane when UL GPRS TBF exists, the counter increments. The measurement point is A, as shown inFigure 25-73.
Figure 25-73 - Release Request due to Abnormal Release Request by MAC

Unit
Times

25.74 C901190080 Number of GPRS UL TBF release due to NSVC unavailability

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 point is A, as shown inFigure 25-74.

25-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 25-74 - Release Request due to NVSC Unavailability

Unit
Times

25.75 C901190081 Number of GPRS UL TBF release due to BVC unavailability

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
This counter is used to find out the number of UL GPRS TBF release after receiving forcing release request due to BVC unavailability.

Measurement Point
When PS control plane receives BVC unavailability command to release PS control plane module from DB when UL GPRS TBF exists, the counter increments. The measurement point is A, as shown inFigure 25-75.
Figure 25-75 - Release Request Due To Other Reasons

Unit
Times
25-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

25.76 C901190082 Number of GPRS UL TBF release due to other reasons

Definition
Number of GPRS UL TBF release due to other reasons.

Description
This counter counts the number of UL GPRS TBF forcing release due to other reasons.

Usage
This counter is used to find out the number of UL GPRS TBF release after receiving forcing release request due to other reasons.

Measurement Point
When PS control plane receives release message due to other reasons when UL GPRS TBF exists, the counter increments. The measurement point is A, as shown inFigure 25-76.
Figure 25-76 - Channel Request

Unit
Times

25.77 C901190083 Number of UL GPRS TBF grab resources

Definition
Number of UL GPRS TBF grab resources.

25-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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, resource request is successful, and other TBF resource is grabbed. Measurement point is A, as shown inFigure 25-77.
Figure 25-77 - UL GPRS Resource Request Success

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Usage
This counter is used to find out the frequency for UL GPRS TBF grabbing other TBF resource.

Measurement Point
This counter increments while UL GPRS TBF is established during resource adjustment, resource request is successful, and other TBF resource is grabbed. Measurement point is A, as shown inFigure 25-78.
Figure 25-78 - UL GPRS Resource Request Success

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter increments while UL GPRS TBF is established during resource adjustment, resource request is successful but queuing is required due to incompliant to QoS rate. Measurement point is A as shown inFigure 25-79.
Figure 25-79 - UL GPRS Resource Request Success

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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
This counter increments while UL GPRS TBF is established during resource adjustment, the instance to be queued successfully assigns resource for user plane, and database is successfully registered. Measurement point is A as shown inFigure 25-80.

25-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 25 Uplink GPRS Data TBF Statistics

Figure 25-80 - Resource Assignment Success

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 25-81 - Release UL GPRS TBF

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

25-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 connection failed ....................................................................................................26-25 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 .26-28 C901200033 Number of EGPRS UL TBF establishment failure on PACCH ............26-29 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 congestion for DL TBF establishment .....................................................................26-31 C901200039 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for DL TBF establishment .....................................................................26-32 C901200040 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for DL TBF establishment.....................................26-33 C901200041 Number of EGPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment .................................................................26-34 C901200042 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to DL TBF establishment .................................................................................26-35 C901200043 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment ..................................................26-36 C901200044 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for DL TBF establishment ..........................................................26-37 C901200045 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for DL TBF establishment ..........................................................26-38 C901200046 Number of EGPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment .................................................26-39 C901200047 Number of EGPRS UL TBF resource reallocation failure due to DL TBF establishment .................................................................................................26-40 C901200048 Number of EGPRS UL TBF resource reallocation success due to DL TBF establishment .................................................................................................26-40 C901200051 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission.............................................................................26-41 C901200052 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission.............................................................................26-42
26-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

C901200053 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission ............................................26-43 C901200054 Number of EGPRS UL TBF resource reallocation success of channel allocation due to LLC transmission .........................................................................26-44 C901200055 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to LLC transmission ........................................................................................26-45 C901200056 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for LLC transmission..........................................................26-46 C901200057 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for LLC transmission ..................................................................26-47 C901200058 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for LLC transmission ..................................................................26-48 C901200059 Number of EGPRS UL TBF resource reallocation success of channel activate for LLC transmission .................................................................................26-49 C901200060 Number of EGPRS UL TBF resource reallocation failure due to LLC transmission ...........................................................................................................26-50 C901200061 Number of EGPRS UL TBF resource reallocation success due to LLC transmission ...........................................................................................................26-50 C901200062 Number of EGPRS UL TBF resource reallocation requests for resource request ....................................................................................................26-51 C901200064 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for resource request .............................................................................26-51 C901200065 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for resource request .............................................................................26-52 C901200066 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for resource request .............................................26-53 C901200067 Number of EGPRS UL TBF resource reallocation success due to database allocation for resource request ................................................................26-54 C901200068 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to resource request..........................................................................................26-55 C901200069 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for resource request ..........................................................26-56 C901200070 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for resource request...................................................................26-57 C901200071 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for resource request...................................................................26-58 C901200072 Number of EGPRS UL TBF resource reallocation success of channel activate and connection for resource request .........................................................26-59 C901200073 Number of EGPRS UL TBF resource reallocation failure due to resource request ....................................................................................................26-60 C901200074 Number of EGPRS UL TBF resource reallocation success due to resource request ....................................................................................................26-60 C901200075 Number of EGPRS UL TBF release due to flush LL...........................26-61 C901200076 Number of EGPRS UL TBF release due to GPRS suspend requests .26-61 C901200077 Number of EGPRS UL TBF forcing release by CS ............................26-62
26-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-63 C901200080 Number of EGPRS UL TBF release due to NSVC unavailability ........26-64 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-65 C901200083 Number of UL EGPRS TBF grab resources.......................................26-66 C901200084 Number of grab instance by UL EGPRS TBF ....................................26-67 C901200085 Number of UL EGPRS TBF queuing .................................................26-68 C901200086 Number of UL EGPRS TBF queuing success ....................................26-69 C901200087 Number of UL EGPRS TBF release TBF during queuing...................26-70 C901200088 Times of Uplink EGPRS TBF Requesting DLDC Resources..............26-71 C901200089 Times of Allocating Uplink DLDC Resources for EGPRS TBF ...........26-72

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.

26.2 C901200002 Number of GPRS UL TBF establishment requests on CCCH

Definition
Number of GPRS UL TBF establishment requests on CCCH

Description
This counter is not used currently.

26.3 C901200003 Number of EGPRS UL TBF establishment requests on CCCH

Definition
Number of EGPRS UL TBF establishment requests on CCCH.

Description
This counter counts the number of EGPRS channel requests on CCCH when MS using EGPRS service.

26-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

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 measurement point is A, as shown inFigure 26-1.
Figure 26-1 - EGPRS Channel Request

Unit
Times

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.4 C901200004 Number of GPRS UL TBF establishment requests on PCCCH

Definition
Number of GPRS UL TBF establishment requests on PCCCH.

Description
The counter is not used.

26.5 C901200005 Number of EGPRS UL TBF establishment requests on PCCCH

Definition
Number of EGPRS UL TBF establishment requests on PCCCH.
26-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of packet channel requests on PCCCH when MS attempts 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 measurement point is A, as shown in Figure 26-2.
Figure 26-2 - EGPRS Packet Channel Request

Unit
Times

26.6 C901200006 Number of GPRS UL TBF establishment requests on PACCH

Definition
Number of GPRS UL TBF establishment requests on PACCH.

Description
The counter counts the number of UL EGPRS TBF establishment attempts on PACCH.

Usage
This counter is used to find out the number of UL EGPRS TBF establishment attempts on PACCH under the situation when DL GPRS TBF is already established.

26-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Measurement Point
In the situation when DL EGPRS TBF is established, PS control plane receives UL assignment request message from PS user plane, the counter increments. The measurement point is A, as shown inFigure 26-3.
Figure 26-3 - UL Assignment Request (DL GPRS TBF ALREADY Established)

Unit
Times

26.7 C901200007 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 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
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 counter increments. The measurement point is A, as shown inFigure 26-4 .

26-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 26-4 - EGPRS Channel Requests On CCCH Due To One Phase Access

If BSC receives EGPRS Packet channel request from MS on PCCCH due to one phase access, the counter increments. The 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 l ZGB-03-05-007 One Phase Access ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.8 C901200008 Number of cell attempts for UL assignment due to single block packet access
Definition
Number of cell attempts for UL assignment due to single block packet access

Description
This counter is not used currently.

26-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.9 C901200009 Number of cell attempts for UL assignment due to response paging
Definition
Number of cell attempts for UL assignment due to response paging.

Description
This counter is not used currently.

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.10 C901200010 Number of cell attempts for UL assignment due to cell updating
Definition
Number of cell attempts for UL assignment due to cell updating.

Description
This counter is not used currently.

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.11 C901200011 Number of cell attempts for UL 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.12 C901200012 Number of cell attempts for UL assignment due to TWO PHASE access
Definition
Number of cell attempts for UL assignment due to TWO PHASE access.

Description
This counter counts the number of channel requests on CCCH when MS attempting UL EGPRS TBF establishment or the number of packet channel requests on PCCCH due to two phase access.

Usage
This counter is used to find out the number of UL EGPRS TBF establishment attempts due to two phase access.

Measurement Point
The counter accumulates at the following two time points: 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

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Figure 26-7 - EGPRS Packet Channel Requests On PCCCH Due To Two Phase Access

Unit
Times

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.13 C901200013 Number of cell attempts for UL 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
This counter is used to find out the number of UL EGPRS TBF establishment attempts due to short access.

Measurement Point
The counter accumulates at the following two time points: l If BSC receives EGPRS channel requests from MS on CCCH due to short access, the counter increments. The measurement point is A, as shown in Figure 26-8.

26-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 26-8 - EGPRS Channel Requests On CCCH Due To Short Access

If BSC receives EGPRS Packet channel request from MS on PCCCH due to short access, the counter increments. The measurement point is A, as shown in Figure 26-9.
Figure 26-9 - EGPRS Packet Channel Requests On PCCCH Due To Short Access

Unit
Times

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.14 C901200015 Number of EGPRS UL TBF establishment failure due to Abis congestion
Definition
Number of EGPRS UL TBF establishment failure due to Abis congestion.

Description
The counter records the number of DB resource application failure when attempting UL EGPRS TBF establishment due to Abis congestion.

26-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Usage
This counter is used to find out the number of DB resource application failure when attempting UL EGPRS TBF establishment due to Abis congestion.

Measurement Point
The counter accumulates at the following two time points: 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)

If PS control panel receives UL channel requests from PS user plane when DL EGPRS TBF exists and fails to apply for DB resource due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 26-11 .
Figure 26-11 - DB Resource Requests Failure Due To Abis Congestion (DL GPRS TBF Already Established)

Unit
Times

Related Features
l l ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

26.15 C901200016 Number of EGPRS UL TBF establishment failure due to RR congestion

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
This counter is used to find out the number of DB resource application failure when attempting UL EGPRS TBF establishment due to RR congestion.

Measurement Point
The counter accumulates at the following two time points: 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)

If PS control panel receives UL channel requests from PS user plane when DL EGPRS TBF exists and fails to apply for DB resource due to RR congestion, the counter increments. The measurement point is A, as shown in Figure 26-13.
Figure 26-13 - DB Resource Requests Failure Due To Abis Congestion (DL GPRS TBF Already Established)

26-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Unit
Times

Related Features
l l ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.16 C901200017 Number of EGPRS UL TBF establishment failure due to UPPB-DSP channel congestion
Definition
Number of EGPRS UL TBF establishment failure due to UPPB-DSP channel congestion

Description
The counter records the number of DB resource application failure when attempting UL EGPRS TBF establishment due to UPPB-DSP channel congestion.

Usage
This counter is used to find out the number of DB resource application failure when attempting UL EGPRS TBF establishment due to UPPB-DSP channel congestion.

Measurement Point
The counter accumulates at the following two time points: 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 UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown in Figure 26-14.
Figure 26-14 - DB Resource Requests Failure Due To UPPB-DSP Channel Congestion (EGPRS)

26-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

If PS control panel receives UL assignment request messages from PS user plane 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 is A, as shown in Figure 26-15.
Figure 26-15 - DB Resource Requests Failure Due To UPPB-DSP Congestion (DL GPRS TBF Already Established)

Unit
Times

Related Features
l l ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.17 C901200018 Number of EGPRS UL TBF establishment channel allocate success

Definition
Number of EGPRS UL TBF establishment channel allocate success.

Description
This counter counts the number of DB resource request successes when attempting UL EGPRS TBF establishment.

Usage
This counter is used to find out the number of DB resource request successes when attempting UL GPRS TBF establishment.

26-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Measurement Point
If PS control plane receives EGPRS channel requests from MS on CCCH or EGPRS Packet channel request on PCCCH and succeeds in applying for DB resource, the counter increments. The measurement point is A, as shown in Figure 26-16.
Figure 26-16 - DB Resource Request Successes (EGPRS)

Unit
Times

Related Features
l l ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

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
The counter records the number of DB resource application failure when attempting UL EGPRS TBF establishment due to UPPB-DSP channel congestion.

Usage
This counter is used to find out the number of DB resource application failure when attempting UL EGPRS TBF establishment due to UPPB-DSP channel congestion.

Measurement Point
The counter accumulates at the following two time points:
26-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown inFigure 26-17
Figure 26-17 - DB Resource Requests Failure Due To UPPB-DSP Channel Congestion (EGPRS)

If PS control panel receives UL assignment request messages from PS user plane 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 is A, as shown inFigure 26-18
Figure 26-18 - DB Resource Requests Failure Due To DPPB-DSP Congestion (DL GPRS TBF Already Established)

Unit
Times

Related Features
l l ZGB-03-05-007 One Phase Access ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

26.19 C901200020 Number of cell success for EGPRS UL assignment due to single block packet access
Definition
Number of cell success for EGPRS UL assignment due to single block packet access

Description
This counter is not used.

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.20 C901200021 Number of cell success for EGPRS UL assignment due to response paging
Definition
Number of cell success for EGPRS UL assignment due to response paging

Description
This counter is not used.

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.21 C901200022 Number of cell success for EGPRS UL assignment due to cell updating
Definition
Number of cell success for EGPRS UL assignment due to cell updating.

Description
This counter is not used.

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

26.22 C901200023 Number of cell success for EGPRS UL assignment due to mobility management
Definition
Number of cell success for EGPRS UL assignment due to mobility management.

Description
This counter is not used.

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.23 C901200024 Number of cell success for EGPRS 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
The counter accumulates at the following two time points: 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 measurement point is A, as shown in Figure 26-19.

26-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Figure 26-19 - EGPRS DB Resource Request Successes Due To Two Phase Access (CCCH)

If BSC receives EGPRS packet channel requests from MS on PCCCH due to two phase access and DB resource request succeeds, the counter increments. The measurement point is A, as shown inFigure 26-20.
Figure 26-20 - DB Resource Request Successes On PCCCH Due To Two Phase Access

Unit
Times

Related Features
l l ZGB-03-05-008 Two Phase Access ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.24 C901200025 Number of cell success for EGPRS UL assignment due to short access
Definition
Number of cell success for EGPRS UL assignment due to short access.

26-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of successful UL EGPRS TBF establishment due to short access.

Usage
This counter is used to find out the number of successful UL GPRS TBF establishment due to short access.

Measurement Point
The counter accumulates at the following two time points: 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 point is A, as shown in Figure 26-21.
Figure 26-21 - EGPRS DB Resource Request Successes Due To Short Access (CCCH)

If BSC receives EGPRS packet channel requests from MS on PCCCH due to short access and DB resource request succeeds, the counter increments. The measurement point is A, as shown in Figure 26-22.
Figure 26-22 - EGPRS DB Resource Request Successes Due To Short Access (PCCCH)

Unit
Times
26-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.25 C901200026 Number of allocated PDCH for 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 increments. The measurement point is A, as shown in Figure 26-23.
Figure 26-23 - DB Resource Request Successes (EGPRS)

Unit
Times

Related Features
l l ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
26-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

26.26 C901200027 Number of EGPRS UL TBF establishment failure due to channel activate failed
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
The counter accumulates at the following two time points: l When BSC receives PDTCH channel activate failure message reported by BTS, the counter increments. The measurement point is A, as shown in Figure 26-24.
Figure 26-24 - PDCH Activation Failure

When 'wait for PDTCH channel activation and connection response' counter times out and BSC fails to receive PDTCH activate response message reported by BTS, this counter increments.

Unit
Times

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

26.27 C901200028 Number of EGPRS UL TBF establishment failure due to BTS connection failed
Definition
Number of EGPRS UL TBF establishment failure due to BTS connection failed.

Description
This counter counts the number of failure to establish UL EGPRS TBF due to BTS connection failure.

Usage
This counter is used to find out the number of UL EGPRS TBF establishment failure (including initially establish UL TBF and establish UL TBF when DL TBF exists) due to BTS connection failure.

Measurement Point
The counter accumulates at the following two time points: l When PS control plane receives connection failure message reported by connection module due to BTS connection failure, the counter increments. The measurement point is A, as shown in Figure 26-25.
Figure 26-25 - Connection Failed Due To BTS Connection Failure

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
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

26.28 C901200029 Number of EGPRS UL TBF establishment failure due to BIU connection failed
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 (including initially establish UL TBF and establish UL TBF when DL TBF exists) due to BIU connection failure.

Measurement Point
When PS control plane receives connection failure message reported by connection modules due to BIU connection failure, the counter increments. The measurement point is A, as shown in Figure 26-26.
Figure 26-26 - Connection Failed Due To BIU Connection Failure

Unit
Times

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

26.29 C901200030 Number of EGPRS UL TBF channel activate establishment success

Definition
Number of EGPRS UL TBF channel activate establishment success.

Description
This counter counts the number of channel activate and connection successes when establishing UL EGPRS TBF.

Usage
This counter is used to find out the number of channel activate and connection successes when establishing UL EGPRS TBF.

Measurement Point
When PS control plane receives channel activate response message reported by BTS and connection successes acknowledgement message reported by connection module, the counter increments. The measurement point is A, as shown inFigure 26-27.
Figure 26-27 - UL EGPRS TBF Establishes Channel Activation And Access Success

Unit
Times

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.30 C901200031 Number of EGPRS UL TBF establishment failure due to not receive PIA
Definition
Number of EGPRS UL TBF establishment failure due to not receive PIA.
26-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The counter accumulates at the following two time points: l When PS control plane receives immediate assignment failure message reported by BTS, the counter increments. The measurement point is A, as shown in Figure 26-28.
Figure 26-28 - Successful Immediate Assignment Sending

When 'wait for immediate assignment and sending indication' counter times out and BSC fails to receive immediate assignment and sending indication message, the counter increments.

Unit
Times

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.31 C901200032 Number of EGPRS UL TBF establishment failure on PCCCH/CCCH

Definition
Number of EGPRS UL TBF establishment failure on PCCCH/CCCH.

Description
This counter counts the number of failure to establish UL EGPRS TBF.
26-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

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 measurement point is A, as shown in Figure 26-29.
Figure 26-29 - UL GPRS TBF Establishment On PCCCH/CCCH

Unit
Times

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.32 C901200033 Number of EGPRS UL TBF establishment failure on PACCH

Definition
Number of EGPRS UL TBF establishment failure on PACCH.

Description
This counter is not used currently.

26-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

26.33 C901200034 Number of EGPRS UL TBF establishment success on PCCCH/CCCH

Definition
Number of EGPRS UL TBF establishment success on PCCCH/CCCH.

Description
This counter counts the number of successful UL EGPRS TBF establishment and receiving MS TLL1.

Usage
This counter is used to find out the number of successful UL EGPRS TBF establishment and receiving MS TLL1.

Measurement Point
The counter accumulates at the following two time points: 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 increments. The measurement point is A, as shown in Figure 26-30.
Figure 26-30 - UL One-Phase-Access Resource Assignment Successes

PS control plane receives resource request message from PS user plane in the premise of two phase access, the counter increments. The measurement point is A, as shown in Figure 26-31.

26-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Figure 26-31 - UL Two-Phase-Access Single Block Assignment Successes

Unit
Times

Related Features
ZGO-03-05-003 EGPRS Packet Channel Request on CCCH

26.34 C901200035 Number of EGPRS UL TBF establishment success on PACCH

Definition
Number of EGPRS UL TBF establishment success on PACCH.

Description
This counter is not used currently.

26.35 C901200038 Number of EGPRS UL TBF resource 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 established on PACCH; DB resource request fails which leads to UL resource reallocation
26-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

failure. The counter records the number of UL EGPRS TBF reallocation failure due to Abis resource congestion.

Usage
This counter is used to find out the number of UL GPRS TBF reallocation failure due to Abis congestion.

Measurement Point
In the situation when UL EGPRS TBF is established, PS control plane receives DL assignment request message from PS user plane, and DB resource request fails due to Abis congestion, 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

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.36 C901200039 Number of EGPRS UL TBF resource 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
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
26-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

failure. The counter records the number of UL resource reallocation failure due to RR resource congestion. 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
In the situation when UL EGPRS TBF is established, PS control plane receives DL assignment request message from PS user plane, and DB resource request fails due to 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

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.37 C901200040 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for DL TBF establishment
Definition
Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion.
26-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
In the situation when UL EGPRS 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 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
In the situation when UL EGPRS TBF is established, PS control plane receives DL assignment request message from PS user plane, and DB resource request fails due to UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown in Figure 26-34.
Figure 26-34 - Database Application Failure due to UPPB-DSP Channel Congestion

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.38 C901200041 Number of EGPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment
Definition
Number of EGPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment.
26-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

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
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 in Figure 26-35.
Figure 26-35 Successful Resource Application

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.39 C901200042 Number of allocated PDCH for 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.
26-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of successful allocated PDTCH when UL EGPRS TBF is successfully reallocated.

Measurement Point
The counter accumulates at the following two time points: 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.

Figure 26-36 - Successful Resource Application

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.40 C901200043 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment
Definition
Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment.

Description
The counter records the number of PDTCH activate failure during UL GPRS TBF resource reallocation.

26-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Usage
This counter is used to find out the number of PDTCH activate failure during UL EGPRS TBF resource reallocation.

Measurement Point
The counter accumulates at the following two time points: l When BSC receives PDTCH channel activate failure message from BTS, the counter increments. The measurement point is A, as shown inFigure 26-37.
Figure 26-37 - PDCH Activation Failure

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive PDTCH channel activate response message from BTS, the counter increments.

Unit
Times

26.41 C901200044 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for DL TBF establishment
Definition
Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for DL TBF establishment.

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 TBF resource reallocation.
26-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter accumulates at the following two time points: l When PS control plane receives connection failure message from connection module due to BTS connection failure, the counter increments. The measurement point is A, as shown in Figure 26-38.
Figure 26-38 - Connection Failed Due To BTS Connection Failure

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive connection success message from connection module, the counter increments.

Unit
Times

26.42 C901200045 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for DL TBF establishment
Definition
Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for DL TBF establishment.

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 TBF resource reallocation.

26-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

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 in Figure 26-39.
Figure 26-39 - Connection Failed Due To BIU Connection Failure

Unit
Times

26.43 C901200046 Number of EGPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment
Definition
Number of EGPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment

Description
The counter records the number of channel activate and connection successes during UL EGPRS TBF resource reallocation.

Usage
This counter is used to find out the number of channel activate and connection successes during UL EGPRS TBF resource reallocation.

26-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When PS control plane receives channel activate ack message and connection success ack message from connection module due to BIU connection failure, the counter increments. The measurement point is A, as shown inFigure 26-40.
Figure 26-40 - Resource Application Failure Due To ABIS Congestion (Resource Adjustment)

Unit
Times

26.44 C901200047 Number of EGPRS UL TBF resource reallocation failure due to DL TBF establishment
Definition
Number of EGPRS UL TBF resource reallocation failure due to DL TBF establishment.

Description
The counter is not used currently.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.45 C901200048 Number of EGPRS UL TBF resource reallocation success due to DL TBF establishment
Definition
Number of EGPRS UL TBF resource reallocation success due to DL TBF establishment.

Description
The counter is not used currently.
26-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.46 C901200051 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission
Definition
Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission.

Description
During UL EGPRS TBF transmission process, PS user plane sends resource reallocation message to PS control plane due to LLC frame change; PS control plane requests 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 EGPRS 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 EGPRS TBF transmission process.

Measurement Point
When PS control plane receives resource reallocation message from PS user plane, and DB resource request fails due to Abis congestion, the counter increments. The measurement point is A, as shown in Figure 26-41.
Figure 26-41 - Resource Application Failure Due To Abis Congestion (Resource Adjustment)

26-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.47 C901200052 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission
Definition
Number of EGPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission.

Description
During UL EGPRS TBF transmission process, PS user plane sends resource reallocation message to PS control plane due to LLC frame change; PS control plane requests DB resource after receiving the message. The counter records the number of DB resource 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
When PS control plane receives resource reallocation message from PS user plane, and DB resource request fails due to RR congestion, the counter increments. The measurement point is A, as shown in Figure 26-42.

26-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Figure 26-42 - Resource Application Failure Due To RR Congestion (Resource Adjustment)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.48 C901200053 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission
Definition
Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission.

Description
During UL EGPRS TBF transmission process, PS user plane sends resource reallocation message to PS control plane due to LLC frame change; PS control plane requests DB resource 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 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.

26-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. The measurement point is A, as shown inFigure 26-43.
Figure 26-43 - Resource Application Failure Due To UPPB-DSP Channel Congestion (Resource Adjustment)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.49 C901200054 Number of EGPRS UL TBF resource reallocation success of channel allocation due to LLC transmission
Definition
Number of EGPRS UL TBF resource reallocation success of channel allocation due to LLC transmission.

Description
During UL EGPRS TBF transmission process, PS user plane sends resource reallocation message to PS control plane due to LLC frame change; PS control plane requests DB resource after receiving the message. The counter records the number of DB resource 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.
26-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Measurement Point
When PS control plane receives resource reallocation message from PS user plane, and DB resource request succeeds, the counter increments. The measurement point is A, as shown in Figure 26-44.
Figure 26-44 Successful Resource Application (Resource Adjustment)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.50 C901200055 Number of allocated PDCH for 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
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 DB 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.
26-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When PS control plane receives resource reallocation message from PS user plane, and DB resource request succeeds, the counter increments. The measurement point is A, as shown inFigure 26-45.
Figure 26-45 - Successful Resource Application (Resource Adjustment)

Unit
Tines

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.51 C901200056 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for LLC transmission
Definition
Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for LLC transmission.

Description
This counter counts the number of PDTCH activate failure after BSC receiving resource reallocation request during UL EGPRS TBF resource reallocation.

Usage
This counter is used to find out the number of PDTCH activate failure during UL EGPRS TBF resource reallocation.

Measurement Point
The measurement is taken at two time points listed below:
26-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

When BSC receives PDTCH channel activate failure message from BTS, the counter increments. The measurement point is A, as shown inFigure 26-46.
Figure 26-46 - PDCH Activation Failure

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive PDTCH channel activate response message from BTS, the counter increments.

Unit
Times

26.52 C901200057 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for LLC transmission
Definition
Number of EGPRS 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 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
The counter accumulates at the following two time points: l When PS control plane receives connection failure message from connection module due to BTS connection failure, the counter increments. The measurement point is A, as shown in
26-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 26-47 - Connection Failed Due To BTS Connection Failure

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive connection success message from connection module, the counter increments.

Unit
Times

26.53 C901200058 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for LLC transmission
Definition
Number of EGPRS 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 EGPRS TBF transmission.

Usage
This counter is used to find out the number of BIU connection failure during UL EGPRS TBF transmission.

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 in Figure 26-48.

26-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Figure 26-48 - Connection Failed Due To BIU Connection Failure

Unit
Times

26.54 C901200059 Number of EGPRS UL TBF resource reallocation success of channel activate for LLC transmission
Definition
Number of EGPRS UL TBF resource reallocation success of channel activate for LLC transmission

Description
The counter records the number of channel activate and connection successes during UL EGPRS TBF transmission.

Usage
This counter is used to find out the number of channel activate and connection successes during UL EGPRS TBF tranmission.

Measurement Point
When PS control plane receives channel activate ack message and connection success ack message from connection module due to BIU connection failure, the counter increments. The measurement point is A, as shown in .

26-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 26-49

Unit
Times

26.55 C901200060 Number of EGPRS UL TBF resource reallocation failure due to LLC transmission
Definition
Number of EGPRS UL TBF resource reallocation failure due to LLC transmission.

Description
The counter is not used currently.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.56 C901200061 Number of EGPRS UL TBF resource reallocation success due to LLC transmission
Definition
Number of EGPRS UL TBF resource reallocation success due to LLC transmission.

Description
The counter is not used currently.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

26.57 C901200062 Number of EGPRS UL TBF resource reallocation requests for resource request
Definition
Number of EGPRS UL TBF resource reallocation requests for resource request.

Description
The counter is not used currently.

26.58 C901200064 Number of EGPRS UL TBF resource 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
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 EGPRS 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 A, as shown in Figure 26-50.

26-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 26-50 - DB Resource Requests Failure Due To Abis Congestion (Resource Request)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.59 C901200065 Number of EGPRS UL TBF resource 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
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 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
This counter is used to find out the number of DB resource request failure after PS control plane receives resource request from MS due to RR congestion during UL EGPRS TBF process (including UL two-phase access and UL TBF transmission).

26-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

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

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.60 C901200066 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for resource request
Definition
Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for resource request.

Description
The counter records the number of DB resource request failure after PS control plane receives resource request from MS due to UPPB-DSP channel congestion during UL EGPRS 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 due to UPPB-DSP channel congestion during UL EGPRS TBF process (including UL two-phase access and UL TBF transmission).
26-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
PS control plane receives resource request message from PS user plane, and DB resource request fails due to RR congestion, the counter increments. The measurement point is A, as shown in Figure 26-52.
Figure 26-52 - DB Resource Requests Failure Due To UPPB-DSP Channel Congestion (Resource Request)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.61 C901200067 Number of EGPRS UL TBF resource reallocation success due to database allocation for resource request
Definition
Number of EGPRS UL TBF resource reallocation success due to database allocation for resource request

Description
The counter records the number of successful DB resource request after PS control plane receives resource request message from MS during UL EGPRS TBF process.

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).
26-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Measurement Point
PS control plane receives resource request message from PS user plane, and DB resource request succeeds, the counter increments. The measurement point is A, as shown in Figure 26-53.
Figure 26-53 - DB Resource Requests Successes (Resource Request)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.62 C901200068 Number of allocated PDCH for 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 two-phase access and UL TBF transmission).

26-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
PS control plane receives resource request message from PS user plane, and DB resource request succeeds, the counter increments. The measurement point is A, as shown in Figure 26-54.
Figure 26-54 - DB Resource Requests Successes (Resource Request)

Unit
Times

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.63 C901200069 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for resource request
Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for resource request. The counter records the number of PDTCH activate failure during UL EGPRS TBF resource reallocation after PS control plane receives resource request message. The counter records the number of PDTCH activate failure during UL EGPRS TBF resource reallocation after PS control plane receives resource request message in UL EGPRS TBF process (including UL two-phase access and one-phase TBF transmission). The counter accumulates at the following two time points: l When BSC receives PDTCH channel activate failure message from BTS, the counter increments. The measurement point is A, as shown in .

26-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Figure 26-55 - PDTCH Activation Failure

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive PDTCH channel activate response message from BTS, the counter increments.

Unit
Times

26.64 C901200070 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for resource request
Definition
Number of EGPRS 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 EGPRS TBF resource reallocation after PS control plane receives resource request message.

Usage
The counter records the number of connection failure due to BTS connection failure during UL EGPRS TBF resource reallocation after PS control plane receives resource request message in UL GPRS TBF process (including UL two-phase access and one-phase TBF transmission).

Measurement Point
The counter accumulates at the following two time points: l When PS control plane receives connection failure message from connection module due to BTS connection failure, the counter increments. The measurement point is A, as shown in Figure 26-56.
26-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 26-56 - Connection Failed Due To BTS Connection Failure

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive connection success message from connection module, the counter increments.

Unit
Times

26.65 C901200071 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for resource request
Definition
Number of EGPRS 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 UL EGPRS TBF resource reallocation after PS control plane receives resource request message.

Usage
The counter records the number of connection failure due to BIU 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
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 26-57.

26-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Figure 26-57 - Connection Failed Due To BIU Connection Failure

Unit
Times

26.66 C901200072 Number of EGPRS UL TBF resource reallocation success of channel activate and connection for resource request
Definition
Number of EGPRS UL TBF resource reallocation success of channel activate and connection for resource request

Description
The counter records the number of channel activate and connection successes during UL EGPRS TBF resource reallocation after PS control plane receives resource request message.

Usage
The counter records the number of channel activate and connection failure during UL EGPRS TBF resource reallocation after PS control plane receives resource request message in UL EGPRS TBF process (including UL two-phase access and one-phase TBF transmission).

Measurement Point
When PS control plane receives channel activate ack message and connection success ack message from connection module due to BIU connection failure, the counter increments. The measurement point is A, as shown in Figure 26-58.

26-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 26-58 - Resource Application Failure Due To Abis Congestion (Resource Adjustment)

Unit
Times

26.67 C901200073 Number of EGPRS UL TBF resource reallocation failure due to resource request
Description
The counter is not used currently.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26.68 C901200074 Number of EGPRS UL TBF resource reallocation success due to resource request
Description
The counter is not used currently.

Related Features
ZGO-03-02-002 Enhancement on Channel Allocation

26-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

26.69 C901200075 Number of EGPRS UL TBF release 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 point is A, as shown in Figure 26-59.
Figure 26-59 Release Request due to Suspend Request

Unit
Times

26.70 C901200076 Number of EGPRS UL TBF release due to GPRS suspend requests
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.

26-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 point is A, as shown in Figure 26-60.
Figure 26-60 Release Request due to Suspend Request

Unit
Times

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 A, as shown in Figure 26-61.
Figure 26-61 Release Request due to PDCH REL

Unit
Times

26-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

26.72 C901200078 Number of EGPRS UL TBF normal release due to user plane requests
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 point is A, as shown in Figure 26-62.
Figure 26-62 Release Request due to Normal Release Request by MAC

Unit
Times

26.73 C901200079 Number of EGPRS UL TBF abnormal release due to user plane requests
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.

26-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 is A, as shown in Figure 26-63.
Figure 26-63 Release Request due to Abnormal Release Request by MAC

Unit
Times

26.74 C901200080 Number of EGPRS UL TBF release due to NSVC unavailability

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 point is A, as shown in Figure 26-64.
Figure 26-64 - Release Request Due To NSVC Unavailability

26-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Unit
Times

26.75 C901200081 Number of EGPRS UL TBF release due to BVC unavailability

Definition
Number of EGPRS UL TBF release due to BVC unavailability.

Description
This counter counts the number of UL EGPRS TBF release due to BVC unavailability.

Usage
This counter is used to find out the number of UL EGPRS TBF release after receiving forcing release request due to BVC unavailability.

Measurement Point
When PS control plane receives BVC unavailability command to release PS control plane module from DB when UL EGPRS TBF exists, the counter increments. The measurement point is A, as shown in Figure 26-65.
Figure 26-65 - Release Request Due To BVC Unavailability

Unit
Times

26.76 C901200082 Number of EGPRS UL TBF release due to other reasons

Definition
Number of EGPRS UL TBF release due to other reasons.
26-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of UL EGPRS TBF forcing release due to other reasons.

Usage
This counter is used to find out the number of UL EGPRS TBF release after receiving forcing release request due to other reasons.

Measurement Point
When PS control plane receives release message due to other reasons when UL EGPRS TBF exists, the counter increments. The measurement point is A, as shown inFigure 26-66.
Figure 26-66 - Channel Request

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.

26-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Measurement Point
This counter increments while UL EGPRS TBF is established during resource adjustment, resource request is successful, and other TBF resource is grabbed. Measurement point is A as shown inFigure 26-67.
Figure 26-67 - UL EGPRS Resource Request Success

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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.

26-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter increments while UL EGPRS TBF is established during resource adjustment, resource request is successful, and other TBF resource is grabbed. Measurement point is A as shown in Figure 26-68.
Figure 26-68 - UL EGPRS Resource Request Success

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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
This counter increments while UL EGPRS TBF is established during resource adjustment, resource request is successful but queuing is required due to incompliant to QoS rate. Measurement point is A as shown in Figure 26-69.

26-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Figure 26-69 - UL EGPRS Resource Request Success

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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
This counter increments while UL EGPRS TBF is established during resource adjustment, the instance to be queued successfully assigns resource for user, and database is successfully registered. Measurement point is A as shown inFigure 26-70.

26-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 26-70 - UL EGPRS Resource Request Success

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

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-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 26 Uplink EGPRS Data TBF Statistics

Figure 26-71 - Release UL EGPRS TBF

Unit
Times

Related Features
l l ZGO-01-02-003 Service Based QoS ZGO-01-02-004 Streaming Service Policies

26.82 C901200088 Times of Uplink EGPRS TBF Requesting DLDC Resources

Description
This counter counts the number of times that an uplink EGPRS TBF requests DLDC resources.

Measurement Point
None

Unit
Times

26-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

26.83 C901200089 Times of Allocating Uplink DLDC Resources for EGPRS TBF
Description
This counter counts the number of times that DLDC resources are allocated to an uplink EGPRS TBF.

Measurement Point
None

Unit
Times

26-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 point is A, as shown in Figure 27-1.
Figure 27-1 PAGING PS Process

Unit
Times

Related Features
ZGB-02-01-001 Paging

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 27 BSSGP Flow Statistic

Measurement Point
When BSC receives a PAGING CS message, this counter increments. The measurement point is A, as shown inFigure 27-2.
Figure 27-2 - Paging CS Process

Unit
Times

Related Features
ZGB-02-01-001 Paging

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 point is A1, as shown in Figure 27-3.

27-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. measurement point is A2, as shown in Figure 27-4.
Figure 27-4 - FLUSH-LL Message

The

Unit
Times
27-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 27 BSSGP Flow Statistic

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 point is A1, as shown inFigure 27-5.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC receives a BVC-BLOCK-ACK message, this counter increments. measurement point is A2, as shown inFigure 27-6 .
Figure 27-6 - BVC Blocking Process

The

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 27 BSSGP Flow Statistic

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. measurement point is A2, as shown inFigure 27-8. The

27-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 27 BSSGP Flow Statistic

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. measurement point is A2, as shown in Figure 27-10. The

27-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 27-10 - BVC Reset Process

Unit
Times

27.12 C901210011 Number of BVC-RESET message received

Definition
Number of BVC-RESET message received

Description
SGSN sends BVC reset message indicates BSC resets designated BVC, and this counter will count the number of resetting BVC by SGSN actively.

Description
When BSC receives a BVC-RESET message, this counter increments. The measurement point is A3, as shown inFigure 27-11.

27-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 27 BSSGP Flow Statistic

Figure 27-11 - BVC Reset Process

Unit
Times

27.13 C901210012 Number of BVC-RESET-ACK 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. measurement point is A1, as shown inFigure 27-12. The

27-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 27-12 - BVC Reset Process

Unit
Times

27.14 C901210013 Number of PERFORM-LOCATION-REQUEST 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 27 BSSGP Flow Statistic

Figure 27-13 - Perform Location Process

Unit
Times

27.15 C901210014 Number of PERFORM-LOCATION-RESPONSE 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, increments. The measurement point is A1, as shown inFigure 27-14. this counter

27-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 27-14 - Perform Location Process

Unit
Times

27.16 C901210015 Number of PERFORM-LOCATION-ABORT 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 27 BSSGP Flow Statistic

Figure 27-15 - Perform Location Process

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 point is A2, as shown inFigure 27-16.

27-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 27-16 - Perform Location Process

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 measurement point is A3, as shown inFigure 27-17.

27-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 27 BSSGP Flow Statistic

Figure 27-17 - Perform Location Process

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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 DL data service made by MS.

Measurement Point
When BSC receives a FLUSH-LL message and MS is conducting UL data service, this counter increments. The measurement point is A, as shown in Figure 27-19.

27-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 27 BSSGP Flow Statistic

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
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 UL data service made by MS.

Measurement Point
When BSC receives a FLUSH-LL message and MS is conducting UL data service, this counter increments. The measurement point is A, as shown in Figure 27-20.

27-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 27-21 - FLUSH-LL Message

27-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 27 BSSGP Flow Statistic

Unit
Times

27.23 C901210022 Number of reroute inter NSE intra BSS cell

Definition
Number of reroute inter NSE intra BSS cell.

Description
SGSN sends FLUSH-LL message to notify of BSS MS passed inter-cell handover. This counter counts the number of receiving this message by BSC, and the number of same BSS and different NSEs for new and previous cells.

Measurement 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.
Figure 27-22 - FLUSH-LL Message

Unit
Times

27.24 C901210023 Number of reroute inter NSE inter BSS cell

Definition
Number of reroute inter NSE inter BSS cell.

27-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
SGSN sends FLUSH-LL message to notify of BSS MS passed inter-cell handover. This counter counts the number of receiving this message by BSC, and the number of different BSSs and NSEs for new and previous cells.

Measurement 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.
Figure 27-23 - FLUSH-LL Message

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. This counter is supported in version V6.20.200a or above.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 27 BSSGP Flow Statistic

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. This counter is supported in version V6.20.200a or above.

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 after LLC frame transferring is initiated. This counter is supported in version V6.20.200a or above.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. This counter is supported in version V6.20.200a or above.

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 This counter is not used. 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 after LLC frame transferring is initiated. 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 27 BSSGP Flow Statistic

d. Unit Times

27.30 C901210029 LLC transfer succeeded num

1. V6.20.200a ~ V6.20.200e This counter is not used. 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 after LLC frame transferring is initiated. c. Measurement Point 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 If LLC frame transferring is supported, then this counter counts the number of LLC frames successfully transferred within BSC when cell reselection occurs. 2. V6.20.200f 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 This counter is used to find out the number of LLC frames successfully transferred after LLC frame transferring is initiated due to cell reselection. 2. V6.20.200f
27-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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, then the counter increments.

Unit
Times

27.32 C901210031 LLC transfer not via cell reselection

Description
1. V6.20.200a ~ V6.20.200e If LLC frame transferring is supported, then this counter counts the number of LLC frames successfully transferred within BSC when 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 This counter is used to find out the number of LLC frames successfully transferred after LLC frame transferring is initiated not due to cell reselection. 2. V6.20.200f If LLC frame transferring is supported, then this counter is used to find out the number of successful self-recovered TBF link reestablishments in downlink within BSC.

Measurement Point
1. V6.20.200a ~ V6.20.200e

27-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 27 BSSGP Flow Statistic

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 If LLC frame transferring is supported, then this counter counts the number of LLC frames failed to be transferred within BSC when cell reselection occurs. b. Usage This counter is used to find out the number of LLC frames failed to be transferred after LLC frame transferring is initiated due to cell reselection. c. Measurement Point 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 the counter increments. d. Unit Times 2. V6.20.200f This counter is not used.

27.34 C901210033 LLC transfer fail Num not via cell reselection
1. V6.20.200a ~ V6.20.200e a. Description If LLC frame transferring is supported, then this counter counts the number of LLC frames failed to be transferred within BSC when no cell reselection occurs (such as when uplink and downlink TBFs are established simultaneously).
27-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

b. Usage This counter is used to find out the number of LLC frames failed to be transferred after LLC frame transferring is initiated not due to cell reselection. c. Measurement Point 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, then the counter increments. d. Unit Times 2. V6.20.200f This counter is not used.

27-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28

GB Message Statistic
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-12 C901220014 Number of FLOW-CONTROL-MS messages sent by BSC ................28-13 C901220015 Number of FLOW-CONTROL-MS-ACK messages received by BSC .28-14 C901220016 Number of FLOW-CONTROL-PFC messages sent by BSC ..............28-15 C901220017 Number of FLOW-CONTROL-PFC-ACK messages received by BSC .......................................................................................................................28-16 C901220018 Number of status messages sent by BSC .........................................28-17 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 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
28-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-35 C901220043 Number of PS-HANDOVER-COMPLETE messages sent by BSC.....28-37 C901220044 Number of PS-HANDOVER-CANCEL messages sent by BSC..........28-38 C901220045 Number of PS-HANDOVER-REQUEST messages with Service UTRAN CCO received by BSC...............................................................................28-39 C901220046 Number of CREATE-BSS-PFC messages with Service UTRAN CCO received by BSC ....................................................................................................28-40

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. measurement point is A, as shown in Figure 28-1. The

28-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

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 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
This counter increments each time BSC receives a DL-UNITDATA message. measurement point is A, as shown in Figure 28-2. The

28-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. measurement point is A, as shown in Figure 28-3. The

28-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

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
When BSC receives a PAGING PS message, this counter increments. The measurement point is A, as shown in Figure 28-4.
Figure 28-4 PTP Packet Paging Process

28-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
When BSC receives a PAGING CS message, this counter increments. The measurement point is A, as shown in Figure 28-5.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 28-7 RA-CAPABILITY-UPDATE Process

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 measurement point is A, as shown in Figure 28-8.

28-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

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
The radio interface status can be checked by counting this message.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

28.11 C901220010 Number of wireless status messages sent by BSC due to bad link quality
Description
BSC sends the wireless status message to indicate SGSN that abnormality occurs at radio interface. This counter counts the number of BSC's sending this message due to bad link quality.

Usage
The radio interface status can be checked by counting this message.

Measurement Point
When BSC sends a RADIO-STATUS message to SGSN due to bad link quality, this counter increments.

Unit
Times

28.12 C901220011 Number of wireless status messages sent by BSC due to cell reselection command
Description
BSC sends the wireless status message to indicate SGSN that abnormality occurs at radio interface. This counter counts the number of BSC's sending this message due to cell reselection command.

Usage
The radio interface status can be checked by counting this message.

Measurement Point
When BSC sends a RADIO-STATUS message to SGSN due to cell reselection command, this counter increments.

Unit
Times

28-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

28.13 C901220012 Number of FLOW-CONTROL-BVC messages sent by BSC

Description
BSC sends the FLOW-CONTROL-BVC message to notify SGSN of the current BVC flow control policy. This counter counts the number of BSC's sending this message.

Measurement Point
When BSC sends a FLOW-CONTROL-BVC message, this counter increments. The measurement point is A1, as shown in Figure 28-9.
Figure 28-9 FLOW-CONTROL-BVC Process

Unit
Times

28-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.

Measurement Point
When BSC receives a FLOW-CONTROL-BVC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 28-10.
Figure 28-10 FLOW-CONTROL-BVC Process

Unit
Times

28-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

28.15 C901220014 Number of FLOW-CONTROL-MS messages sent by BSC

Description
BSC sends the FLOW-CONTROL-MS message to notify SGSN of the current MS flow control policy. This counter counts the number of BSC's sending this message.

Measurement Point
When BSC sends the FLOW-CONTROL-MS message, this counter increments. The measurement point is A1, as shown in Figure 28-11.
Figure 28-11 FLOW-CONTROL-MS Process

Unit
Times

28-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

28.16 C901220015 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. The measurement point is A2, as shown in Figure 28-12.
Figure 28-12 FLOW-CONTROL-MS Process

Unit
Times

28-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

28.17 C901220016 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 sending this message.

Measurement Point
When BSC sends the FLOW-CONTROL-PFC message, this counter increments. The measurement point is A1, as shown in Figure 28-13.
Figure 28-13 FLOW-CONTROL-PFC Process

Unit
Times

28-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

28.18 C901220017 Number of FLOW-CONTROL-PFC-ACK messages received by BSC

Description
SGSN sends the FLOW-CONTROL-PFC-ACK message to notify BSC that the PFC flow control policy for designated MS is accepted. This counter counts the number of BSC's receiving this message.

Measurement Point
When BSC receives a FLOW-CONTROL-PFC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 28-14.
Figure 28-14 FLOW-CONTROL-PFC Process

Unit
Times

28-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

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 is A1, as shown in Figure 28-15.
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.
28-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC receives the STATUS message, this counter increments. The measurement point is A2, as shown in Figure 28-16.
Figure 28-16 STATUS Process

Unit
Times

28.21 C901220020 Number of status messages sent with BVCI Unknown

Description
BSC sends the status message to SGSN to indicate that abnormality occurs. This counter 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

28.22 C901220021 Number of Status messages sent with cell service congestion
Description
BSC sends the status message to SGSN to indicate that abnormality occurs. This counter 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

28.23 C901220022 Number of status messages sent with protocol error

Description
BSC sends the status message to SGSN to indicate that abnormality occurs. This counter 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

28.24 C901220023 Number of status messages sent 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

28.25 C901220024 Number of status messages 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

28.26 C901220025 Number of status messages received with cell service congestion
Description
SGSN sends status message to BSC, to indicate exception occurred. This counter counts 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

28.27 C901220026 Number of status messages received with protocol error

Description
SGSN sends status message to BSC, to indicate exception occurred. This counter counts the number of receiving this message by BSC due to protocol error.

28-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

Measurement Point
When BSC receives a STATUS message due to protocol error, this counter increments.

Unit
Times

28.28 C901220027 Number of status messages received with processor overload

Description
SGSN sends status message to BSC, to indicate exception occurred. This counter counts 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 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 measurement point is A1, as shown in Figure 28-17.

28-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A2, as shown in Figure 28-18.

28-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

Figure 28-18 CREATE-BSS-PFC Process

Unit
Times

28.31 C901220030 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
When BSC sends a CREATE-BSS-PFC-ACK message, this counter increments. The measurement point is A3, as shown in Figure 28-19.

28-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 28-19 CREATE-BSS-PFC Process

Unit
Times

28.32 C901220031 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 sending this message.

Measurement Point
When BSC sends a CREATE-BSS-PFC-NACK message, this counter increments. The measurement point is A4, as shown in Figure 28-20.

28-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

Figure 28-20 CREATE-BSS-PFC Process

Unit
Times

28.33 C901220032 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. measurement point is A1, as shown in Figure 28-21. The

28-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 28-21 MODIFY-BSS-PFC Process

Unit
Times

28.34 C901220033 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
When BSC receives a MODIFY-BSS-PFC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 28-22.

28-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

Figure 28-22 MODIFY-BSS-PFC Process

Unit
Times

28.35 C901220034 Number of DELETE-BSS-PFC messages received by BSC

Description
SGSN sends the DELETE-BSS-PFC message to request BSC to delete a packet flow control context. This counter counts the number of BSC's receiving this message.

Measurement Point
When BSC receives a DELETE-BSS-PFC message, this counter increments. measurement point is A1, as shown in Figure 28-23. The

28-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 28-23 DELETE-BSS-PFC Process

Unit
Times

28.36 C901220035 Number of DELETE-BSS-PFC-ACK messages sent by BSC

Description
BSC sends the DELETE-BSS-PFC-ACK message to SGSN to confirm the deletion of specified packet flow control context. This counter counts the number of BSC's sending this message.

Measurement Point
When BSC sends a DELETE-BSS-PFC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 28-24.

28-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

Figure 28-24 DELETE-BSS-PFC Process

Unit
Times

28.37 C901220036 Number of DELETE-BSS-PFC-REQ messages received by BSC

Description
This counter is not used.

28.38 C901220037 Number of PS-HANDOVER-REQUIRED 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 28-25 Measurement Point of Number of PS-HANDOVER-REQUIRED messages sent by BSC

Unit
Times

28.39 C901220038 Number of PS-HANDOVER-REQUIRED-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 measurement point is A, as shown in Figure 28-26.

28-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

Figure 28-26 Measurement Point of Number of PS-HANDOVER-REQUIRED-ACK messages received by BSC

Unit
Times

28.40 C901220039 Number of PS-HANDOVER-REQUIRED-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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 28-27 Measurement Point of Number of PS-HANDOVER-REQUIRED-NACK messages received by BSC

Unit
Times

28.41 C901220040 Number of PS-HANDOVER-REQUEST 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

Figure 28-28 Measurement Point of Number of PS-HANDOVER-REQUEST messages received by BSC

Unit
Times

28.42 C901220041 Number of PS-HANDOVER-REQUEST-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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 28-29 Measurement Point of Number of PS-HANDOVER-REQUEST-ACK messages sent by BSC

Unit
Times

28-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

28.43 C901220042 Number of PS-HANDOVER-REQUEST-NACK messages sent by BSC

Statistics object
BSC

Description
During the handover, if the channel request fails or the cell does not support PS handover, then creating MS or PS instance will fail. This counter counts the number of messages, which indicate failure of creating MS or PS instance, sent by BSC. The counter increments when BSC sends the PS-HANDOVER-REQUEST-NACK message. The measurement point is A3, as shown in Figure 28-30.

28-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 28-30 Measurement Point of Number of PS-HANDOVER-REQUEST-NACK messages sent by BSC

Unit
Times

28-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

28.44 C901220043 Number of PS-HANDOVER-COMPLETE 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. The measurement point is A, as shown in Figure 28-31.
Figure 28-31 Measurement Point of Number of PS-HANDOVER-COMPLETE messages sent by BSC

Unit
Times

28-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

28.45 C901220044 Number of PS-HANDOVER-CANCEL messages sent by BSC

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-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 28 GB Message Statistic

28.46 C901220045 Number of PS-HANDOVER-REQUEST 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.
Figure 28-33 Measurement Point of Number of PS-HANDOVER-REQUEST messages with Service UTRAN CCO received by BSC

Unit
Times

28-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 shown in Figure 28-34.
Figure 28-34 Measurement Point of Number of CREATE-BSS-PFC messages with Service UTRAN CCO received by BSC

Unit
Times

28-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29

TRX Measurement
Table of Contents
Overview ..................................................................................................................29-4 C901230001 Number of intra-cell handover in attempts ...........................................29-4 C901230002 Number of intra-cell handover ins success ..........................................29-5 C901230003 Number of Intra-BSC inter-cell handover in attempts ...........................29-6 C901230004 Number of Intra-BSC intra-cell handover ins success ..........................29-7 C901230005 Number of Intra-MSC inter-cell handover in attempts ..........................29-8 C901230006 Number of Intra-MSC inter-cell handover in success ...........................29-9 C901230007 TCH busy time ..................................................................................29-10 C901230008 Number of TCH seizures (including handover) .................................. 29-11 C901230009 Number of call drops due to TCH LAPD breakage............................. 29-11 C901230010 Number of call drops due to TCH radio link failure ............................. 29-11 C901230011 Number of TCH handover call drops..................................................29-12 C901230012 Number of TCH/F activation attempts (including handover) ...............29-13 C901230013 Number of TCH/F activation success (including handover)................29-14 C901230014 Number of TCH/F assignment attempts.............................................29-15 C901230015 Number of TCH/F assignment success .............................................29-16 C901230016 Number of TCH/H activation attempts (including handover)...............29-17 C901230017 Number of TCH/H activation success (including handover) ...............29-18 C901230018 Number of TCH/H assignment attempts ............................................29-19 C901230019 Number of TCH/H assignment success .............................................29-20 C901230020 SDCCH busy time .............................................................................29-21 C901230021 Number of attempts for SDCCH ........................................................29-22 C901230022 Number of SDCCH call drops............................................................29-22 C901230023 Number of SDCCH activation attempts (including handover) .............29-24 C901230024 Number of SDCCH activation success (including handover)..............29-24 C901230025 Number of SDCCH assignment attempts ..........................................29-25 C901230026 Number of SDCCH assignment success ...........................................29-26 C901230027 Number of samples with UL RQ = 0 ..................................................29-27 C901230028 Number of samples with UL RQ = 1 ..................................................29-28 C901230029 Number of samples with UL RQ = 2 ..................................................29-28 C901230030 Number of samples with UL RQ = 3 ..................................................29-29 C901230031 Number of samples with UL RQ = 4 ..................................................29-30 C901230032 Number of samples with UL RQ = 5 ..................................................29-30 C901230033 Number of samples with UL RQ = 6 ..................................................29-31 C901230034 Number of samples with UL RQ = 7 ..................................................29-31 C901230035 Number of samples with DL RQ = 0 ..................................................29-32 C901230036 Number of samples with DL RQ = 1 ..................................................29-33
29-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901230037 Number of samples with DL RQ = 2 ..................................................29-33 C901230038 Number of samples with DL RQ = 3 ..................................................29-34 C901230039 Number of samples with DL RQ = 4 ..................................................29-34 C901230040 Number of samples with DL RQ = 5 ..................................................29-35 C901230041 Number of samples with DL RQ = 6 ..................................................29-36 C901230042 Number of samples with DL RQ = 7 ..................................................29-36 C901230043 Mean number of idle TCH/Fs with interference band 0 ......................29-37 C901230044 Mean number of idle TCH/Fs with interference band 1 ......................29-38 C901230045 Mean number of idle TCH/Fs with interference band 2 ......................29-38 C901230046 Mean number of idle TCH/Fs with interference band 3 ......................29-39 C901230047 Mean number of idle TCH/Fs with interference band 4 ......................29-39 C901230048 Mean number of idle TCH/Fs with interference band 5 ......................29-40 C901230049 Mean number of idle TCH/Hs with interference band 0......................29-40 C901230050 Mean number of idle TCH/Hs with interference band 1......................29-41 C901230051 Mean number of idle TCH/Hs with interference band 2......................29-41 C901230052 Mean number of idle TCH/Hs with interference band 3......................29-42 C901230053 Mean number of idle TCH/Hs with interference band 4......................29-42 C901230054 Mean number of idle TCH/Hs with interference band 5......................29-43 C901230055 Mean number of idle SDCCHs with interference band 0 ....................29-43 C901230056 Mean number of idle SDCCHs with interference band 1 ....................29-44 C901230057 Mean number of idle SDCCHs with interference band 2 ....................29-44 C901230058 Mean number of idle SDCCHs with interference band 3 ....................29-44 C901230059 Mean number of idle SDCCHs with interference band 4 ....................29-45 C901230060 Mean number of idle SDCCHs with interference band 5 ....................29-45 C901230061 Number of TRX poweroff...................................................................29-46 C901230062 Duration of TRX poweroff ..................................................................29-46 C901230063 Number of uplink error frame on FR_V1 ............................................29-47 C901230064 Total Number of uplink frame on FR_V1 ............................................29-47 C901230065 Number of uplink error frame on FR_V2 ............................................29-47 C901230066 Total Number of uplink frame on FR_V2 ............................................29-48 C901230067 Number of uplink error frame on FR_V3 ............................................29-48 C901230068 Total Number of uplink frame on FR_V3 ............................................29-48 C901230069 Number of uplink error frame on HR_V1............................................29-49 C901230070 Total Number of uplink frame on HR_V1............................................29-49 C901230071 Number of uplink error frame on HR_V3............................................29-50 C901230072 Total Number of uplink frame on HR_V3............................................29-50 C901230073 Number of Samples With Uplink RQ=0 (on SDCCH) .........................29-50 C901230074 Number of Samples With Uplink RQ = 1 (on SDCCH) .......................29-51 C901230075 Number of Samples With Uplink RQ = 2 (on SDCCH) .......................29-51 C901230076 Number of Samples With Uplink RQ = 3 (on SDCCH) .......................29-51 C901230077 Number of Samples With Uplink RQ = 4 (on SDCCH) .......................29-52 C901230078 Number of Samples With Uplink RQ = 5 (on SDCCH) .......................29-52 C901230079 Number of Samples With Uplink RQ = 6 (on SDCCH) .......................29-53 C901230080 Number of Samples With Uplink RQ = 7 (on SDCCH) .......................29-53 C901230081 Number of Samples With Downlink RQ = 0 (on SDCCH)...................29-53
29-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

C901230082 Number of Samples With Downlink RQ = 1 (on SDCCH)...................29-54 C901230083 Number of Samples With Downlink RQ = 2 (on SDCCH)...................29-54 C901230084 Number of Samples With Downlink RQ = 3 (on SDCCH)...................29-54 C901230085 Number of Samples With Downlink RQ = 4 (on SDCCH)...................29-55 C901230086 Number of Samples With Downlink RQ = 5 (on SDCCH)...................29-55 C901230087 Number of Samples With Downlink RQ = 6 (on SDCCH)...................29-56 C901230088 Number of Samples With Downlink RQ = 7 (on SDCCH)...................29-56 C901230089 Number of Samples With Uplink RQ = 0 (on TCH) ............................29-56 C901230090 Number of Samples With Uplink RQ = 1 (on TCH) ............................29-57 C901230091 Number of Samples With Uplink RQ = 2 (on TCH) ............................29-57 C901230092 Number of Samples With Uplink RQ = 3 (on TCH) ............................29-57 C901230093 Number of Samples With Uplink RQ = 4 (on TCH) ............................29-58 C901230094 Number of Samples With Uplink RQ = 5 (on TCH) ............................29-58 C901230095 Number of Samples With Uplink RQ = 6 (on TCH) ............................29-59 C901230096 Number of Samples With Uplink RQ = 7 (on TCH) ............................29-59 C901230097 Number of Samples With Downlink RQ = 0 (on TCH) ........................29-59 C901230098 Number of Samples With Downlink RQ = 1 (on TCH) ........................29-60 C901230099 Number of Samples With Downlink RQ = 2 (on TCH) ........................29-60 C901230100 Number of Samples With Downlink RQ = 3 (on TCH) ........................29-60 C901230101 Number of Samples With Downlink RQ = 4 (on TCH) ........................29-61 C901230102 Number of Samples With Downlink RQ = 5 (on TCH) ........................29-61 C901230103 Number of Samples With Downlink RQ = 6 (on TCH) ........................29-62 C901230104 Number of Samples With Downlink RQ = 7 (on TCH) ........................29-62 C901230105 Number of Sample With Interference Band........................................29-62 C901230106 Number of Idle TCH/F With Interference Band 0................................29-63 C901230107 Number of Idle TCH/F With Interference Band 1................................29-63 C901230108 Number of Idle TCH/F With Interference Band 2................................29-64 C901230109 Number of Idle TCH/F With Interference Band 3................................29-64 C901230110 Number of Idle TCH/F With Interference Band 4................................29-65 C901230111 Number of Idle TCH/F With Interference Band 5 ................................29-65 C901230112 Number of Idle TCH/H With Interference Band 0 ...............................29-66 C901230113 Number of Idle TCH/H With Interference Band 1 ...............................29-66 C901230114 Number of Idle TCH/H With Interference Band 2 ...............................29-67 C901230115 Number of Idle TCH/H With Interference Band 3 ...............................29-67 C901230116 Number of Idle TCH/H With Interference Band 4 ...............................29-68 C901230117 Number of Idle TCH/H With Interference Band 5 ...............................29-68 C901230118 Number of Idle TCH/H With Interference Band 0 ...............................29-69 C901230119 Number of Idle TCH/H With Interference Band 1 ...............................29-69 C901230120 Number of Idle TCH/H With Interference Band 2 ...............................29-70 C901230121 Number of Idle TCH/H With Interference Band 3 ...............................29-70 C901230122 Number of Idle TCH/H With Interference Band 4 ...............................29-71 C901230123 Number of Idle TCH/H With Interference Band 5 ...............................29-71 C901230124 Uplink CIR Normal Grade 0 (Below -2 dB) Sample ............................29-72 C901230125 Uplink CIR Normal Grade 1 (-2 to 0.5 dB) Sample.............................29-72 C901230126 Uplink CIR Normal Grade 2 (1 to 3.5 dB) Sample..............................29-72
29-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901230127 Uplink CIR Normal Grade 3 (4 to 6.5 dB) Sample..............................29-73 C901230128 Uplink CIR Normal Grade 4 (7 to 9.5 dB) Sample..............................29-73 C901230129 Uplink CIR Normal Grade 5 (10 to 12.5 dB) Sample ..........................29-73 C901230130 Uplink CIR Normal Grade 6 (13 to 15.5 dB) Sample ..........................29-74 C901230131 Uplink CIR Normal Grade 7 (16 to 18.5 dB) Sample ..........................29-74 C901230132 Uplink CIR Normal Grade 8 (19 to 21.5 dB) Sample ..........................29-75 C901230133 Uplink CIR Normal Grade 9 (Above 21.5 dB) Sample........................29-75 C901230134 Uplink CIR Improved Grade 0 (Below -2 dB) Sample.........................29-75 C901230135 Uplink CIR Improved Grade 1 (-2 to 0.5 dB) Sample .........................29-76 C901230136 Uplink CIR Improved Grade 2 (1 to 3.5 dB) Sample...........................29-76 C901230137 Uplink CIR Improved Grade 3 (4 to 6.5 dB) Sample...........................29-76 C901230138 Uplink CIR Improved Grade 4 (7 to 9.5 dB) Sample...........................29-77 C901230139 Uplink CIR Improved Grade 5 (10 to 12.5 dB) Sample.......................29-77 C901230140 Uplink CIR Improved Grade 6 (13 to 15.5 dB) Sample.......................29-78 C901230141 Uplink CIR Improved Grade 7 (16 to 18.5 dB) Sample.......................29-78 C901230142 Uplink CIR Improved Grade 8 (19 to 21.5 dB) Sample.......................29-78 C901230143 Uplink CIR Improved Grade 9 (Above 21.5 dB) Sample ....................29-79

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

29-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Figure 29-1 - Intra-cell Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

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.

29-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 29-2 - Intra-cell Handover

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

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 shown in Figure 29-3.

29-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Figure 29-3 - Inter-Cell Handover Controlled By BSC

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

29.5 C901230004 Number of Intra-BSC intra-cell handover ins success

Definition
Number of Intra-BSC intra-cell handover ins success.

Description
During inter-cell handover controlled by BSC, after target channel is successfully activated, BSC will send handover command to MS through source channel. After BSC receives HANDOVER COMPLETE message of MS from target channel, inter-cell handover is successfully completed.

Measurement Point
During inter-cell handover controlled by BSC, measurement point will be counted after BSC receives HANDOVER COMPLETE message. The measurement point is A2, as shown in Figure 29-4.

29-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 29-4 - Inter-Cell Handover Controlled By BSC

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

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.

Measurement Point
During inter-cell handover (incoming) controlled by MSC, measurement point will be counted after BSC receives CHANNEL ACTIVATE ACK. The measurement point is A1, as shown in Figure 29-5.

29-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Figure 29-5 - Inter-Cell Handover Controlled By BSC

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

29.7 C901230006 Number of Intra-MSC inter-cell handover in success

Definition
Number of Intra-MSC inter-cell handover ins success.

Description
During inter-cell handover controlled by MSC, after target channel is successfully activated and target channel receives HANDOVER COMPLETE message sent by MS, handover is successfully done.

Measurement Point
During inter-cell handover controlled by MSC, measurement point will be counted after BSC receives HANDOVER COMPLETE message from MS. The measurement point is A2, as shown in Figure 29-6.

29-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 29-6 - Inter-Cell Handover Controlled By BSC

Unit
Times

Related Features
ZGB-02-02-001 Basic Handover

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 l l Accumulate while successfully acquire voice channel resource Accumulate while release voice channel resource Accumulate by regular measurement and acquisition

Unit
Second
29-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

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-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 shown in Figure 29-8.

29-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Figure 29-8 - Inter-Cell Handover Failure

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-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

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-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Figure 29-11 - Channel Activation Measurement Point

Unit
Times

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

29.15 C901230014 Number of TCH/F assignment 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-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 29-12 - TCH/F Channel Assignment Measurement Point

Unit
Times

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

29.16 C901230015 Number of TCH/F assignment 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. measurement point is A2, as shown inFigure 29-13. The

29-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Figure 29-13 - TCH/F Channel Assignment Measurement Point

Unit
Times

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

29.17 C901230016 Number of TCH/H activation attempts (including handover)

Definition
Number of TCH/H activation attempts (including handover).

Description
Count the number of originating channel activation from carrier TCH/H channel.

Measurement Point
Count after BSC sends CHANNEL ACTIVATE message to BTS. The measurement point is A1, as shown inFigure 29-14.

29-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 29-14 - Channel Activation Measurement Point

Unit
Times

Related Features
l l ZGO-01-01-001 Half Rate 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
Count after BSC receives CHANNEL ACTIVATE ACK message. The measurement point is A2, as shown inFigure 29-15 .

29-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Figure 29-15 - Channel Activation Measurement Point

Unit
Times

Related Features
l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

29.19 C901230018 Number of TCH/H assignment 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 is A1, as shown inFigure 29-16 .

29-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 29-16 - TCH/F Channel Assignment Measurement Point

Unit
Times

Related Features
l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

29.20 C901230019 Number of TCH/H assignment 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. measurement point is A2, as shown inFigure 29-17 . The

29-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Figure 29-17 - TCH/F Channel Assignment Measurement Point

Unit Related Features

l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

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 l l Accumulate while successfully acquire SDCCH channel resource Accumulate while release SDCCH channel resource Accumulate by regular measurement and acquisition
29-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

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 l l l l When BSC receives LAPD breakage message and channel is SDCCH. When BSC connection faults and channel is SDCCH. After THoOutGo timer times out. After T3103 timer times out. After T3107 timer times out.

Unit
Times

29-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

29.24 C901230023 Number of SDCCH activation attempts (including handover)

Definition
Number of SDCCH activation attempts (including handover)

Description
Count the number of originating CHANNEL ACTIVATE messages from carrier SDCCH channel.

Measurement Point
Count after BSC sends CHANNEL ACTIVATE message to BTS. The measurement point is A1, as shown inFigure 29-21 .
Figure 29-21 - Channel Activation 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-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Measurement Point
Count after BSC receives CHANNEL ACTIVATE ACK message. The measurement point is A2, as shown inFigure 29-22 .
Figure 29-22 - Channel Activation Measurement Point

Unit
Times

29.26 C901230025 Number of SDCCH assignment attempts

Definition
Number of SDCCH assignment attempts

Description
When assign SDCCH channel, BSC assigns SDCCH channels by sending IMMEDIATE ASSIGNMENT message or ASSIGNMENT COMMAND message. This counter counts the number of SDCCH assignment attempts.

Measurement Point
Count after BSC sends IMMEDIATE ASSIGNMENT message or ASSIGNMENT COMMAND to BTS. The measurement point is A1, as shown in Figure 29-23.

29-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 29-23 - Channel Assignment Measurement Point

Unit
Times

29.27 C901230026 Number of SDCCH assignment success

Definition
Number of SDCCH assignment success

Description
When assign SDCCH channel, BSC sends IMMEDIATE ASSIGNMENT message or ASSIGNMENT COMMAND message to assignment channel, after BSC receives EST IND (CM SERV REQ), channel assignment is successful.

Measurement Point
Count after BSC receives EST IND (CM SERV REQ) message. The measurement point is A2, as shown in Figure 29-24.

29-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Figure 29-24 - Channel Assignment Measurement Point

Unit
Times

29.28 C901230027 Number of samples with UL RQ = 0

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-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 29-25 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

29.29 C901230028 Number of samples with UL RQ = 1

Definition
Number of samples with UL RQ = 1

Description
This measurement value is the sample number with UL RQ=1 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=1 in measurement report, this counter increments. The measurement point is A, as shown in Figure 29-26.
Figure 29-26 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

29.30 C901230029 Number of samples with UL RQ = 2

Definition
Number of samples with UL RQ = 2
29-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Description
This measurement value is the sample number with UL RQ=2 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=2 in measurement report, this counter increments. The measurement point is A, as shown in Figure 29-27.
Figure 29-27 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

29.31 C901230030 Number of samples with UL RQ = 3

Definition
Number of samples with UL RQ = 3

Description
This measurement value is the sample number with UL RQ=3 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=3 in measurement report, this counter increments. The measurement point is A, as shown inFigure 29-28.
Figure 29-28 - BSC Receives the Measurement Report Submitted BY BTS

29-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

29.32 C901230031 Number of samples with UL RQ = 4

Definition
Number of samples with UL RQ = 4

Description
This measurement value is the sample number with UL RQ=4 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=4 in measurement report, this counter increments. The measurement point is A, as shown in Figure 29-29.
Figure 29-29 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

29.33 C901230032 Number of samples with UL RQ = 5

Definition
Number of samples with UL RQ = 5

Description
This measurement value is the sample number with UL RQ=5 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=5 in measurement report, this counter increments. The measurement point is A, as shown in Figure 29-30.

29-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Figure 29-30 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

29.34 C901230033 Number of samples with UL RQ = 6

Definition
Number of samples with UL RQ = 6

Description
This measurement value is the sample number with UL RQ=6 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=6 in measurement report, this counter increments. The measurement point is A, as shown in Figure 29-31.
Figure 29-31 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

29.35 C901230034 Number of samples with UL RQ = 7

Description
This measurement value is the sample number with UL RQ=7 in measurement report.
29-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=7 in measurement report, this counter increments. The measurement point is A, as shown in Figure 29-32.
Figure 29-32 BSC Receives the Measurement Report Submitted by BTS

Unit
Times

29.36 C901230035 Number of samples with DL RQ = 0

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 report, this counter increments. The measurement point is A, as shown in Figure 29-33.
Figure 29-33 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

29-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

29.37 C901230036 Number of samples with DL RQ = 1

Definition
Number of samples with DL RQ = 1

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=1 in measurement report, this counter increments. The measurement point is A, as shown in Figure 29-34.
Figure 29-34 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

29.38 C901230037 Number of samples with DL RQ = 2

Definition
Number of samples with DL RQ = 2

Description
This measurement value is the sample number with DL RQ=2 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=2 in measurement report, this counter increments. The measurement point is A, as shown in Figure 29-35.

29-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 29-35 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

29.39 C901230038 Number of samples with DL RQ = 3

Definition
Number of samples with DL RQ = 3

Description
This measurement value is the sample number with DL RQ=3 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=3 in measurement report, this counter increments. The measurement point is A, as shown in Figure 29-36.
Figure 29-36 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

29.40 C901230039 Number of samples with DL RQ = 4

Definition
Number of samples with DL RQ = 4
29-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Description
This measurement value is the sample number with DL RQ=4 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=4 in measurement report, this counter increments. The measurement point is A, as shown in Figure 29-37.
Figure 29-37 - BSC Receives the Measurement Report Submitted By BTS

Unit
Times

29.41 C901230040 Number of samples with DL RQ = 5

Definition
Number of samples with DL RQ = 5

Description
This measurement value is the sample number with DL RQ=5 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=5 in measurement report, this counter increments. The measurement point is A, as shown in Figure 29-38.
Figure 29-38 - BSC Receives the Measurement Report Submitted BY BTS

29-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

29.42 C901230041 Number of samples with DL RQ = 6

Definition
Number of samples with DL RQ = 6

Description
This measurement value is the sample number with DL RQ=6 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=6 in measurement report, this counter increments. The measurement point is A, as shown in Figure 29-39.
Figure 29-39 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

29.43 C901230042 Number of samples with DL RQ = 7

Definition
Number of samples with DL RQ = 7

Description
This measurement value is the sample number with DL RQ=7 in measurement report.

Measurement Point
BSC receives the measurement report submitted by BTS, if DL RQ=7 in measurement report, this counter increments. The measurement point is A, as shown in Figure 29-40.

29-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Figure 29-40 - BSC Receives the Measurement Report Submitted BY BTS

Unit
Times

29.44 C901230043 Mean number of idle TCH/Fs with interference band 0

Definition
Mean number of idle TCH/Fs with interference band 0

Description
Regularly query database, acquire idle TCH/F number at different interference level on carrier, to represent average with queried value. Interference level for different TCH/F channel in database will be updated after BSC receives radio resource sent by BTS. 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
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec

29-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

29.45 C901230044 Mean number of idle TCH/Fs with interference band 1

Definition
Mean number of idle TCH/Fs with interference band 1

Description
This measurement value is idle TCH/F number when interference band is 1 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

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

29.46 C901230045 Mean number of idle TCH/Fs with interference band 2

Definition
Mean number of idle TCH/Fs with interference band 2

Description
This measurement value is idle TCH/F number when interference band is 2 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

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

29-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

29.47 C901230046 Mean number of idle TCH/Fs with interference band 3

Definition
Mean number of idle TCH/Fs with interference band 3

Description
This measurement value is idle TCH/F number when interference band is 3 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

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

29.48 C901230047 Mean number of idle TCH/Fs with interference band 4

Definition
Mean number of idle TCH/Fs with interference band 4

Description
This measurement value is idle TCH/F number when interference band is 4 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

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

29-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

29.49 C901230048 Mean number of idle TCH/Fs with interference band 5

Definition
Mean number of idle TCH/Fs with interference band 5

Description
This measurement value is idle TCH/F number when interference band is 5 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

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

29.50 C901230049 Mean number of idle TCH/Hs with interference band 0

Definition
Mean number of idle TCH/Hs with interference band 0

Description
This measurement value is idle TCH/H number when interference band is 0 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

Related Features
l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

29-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

29.51 C901230050 Mean number of idle TCH/Hs with interference band 1

Definition
Mean number of idle TCH/Hs with interference band 1

Description
This measurement value is idle TCH/H number when interference band is 1 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

Related Features
l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

29.52 C901230051 Mean number of idle TCH/Hs with interference band 2

Definition
Mean number of idle TCH/Hs with interference band 2

Description
This measurement value is idle TCH/H number when interference band is 2 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

Related Features
l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
29-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

29.53 C901230052 Mean number of idle TCH/Hs with interference band 3

Definition
Mean number of idle TCH/Hs with interference band 3

Description
This measurement value is idle TCH/H number when interference band is 3 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

Related Features
l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

29.54 C901230053 Mean number of idle TCH/Hs with interference band 4

Definition
Mean number of idle TCH/Hs with interference band 4.

Description
This measurement value is idle TCH/H number when interference band is 4 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

Related Features
l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
29-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

29.55 C901230054 Mean number of idle TCH/Hs with interference band 5

Definition
Mean number of idle TCH/Hs with interference band 5.

Description
This measurement value is idle TCH/H number when interference band is 5 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

Related Features
l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

29.56 C901230055 Mean number of idle SDCCHs with interference band 0

Definition
Mean number of idle SDCCHs with interference band 0

Description
This measurement value is idle SDCCH number when interference band is 0 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

29-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

29.57 C901230056 Mean number of idle SDCCHs with interference band 1

Definition
Mean number of idle SDCCHs with interference band 1

Description
This measurement value is idle SDCCH number when interference band is 1 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

29.58 C901230057 Mean number of idle SDCCHs with interference band 2

Definition
Mean number of idle SDCCHs with interference band 2

Description
This measurement value is idle SDCCH number when interference band is 2 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

29.59 C901230058 Mean number of idle SDCCHs with interference band 3

Definition
Mean number of idle SDCCHs with interference band 3

29-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Description
This measurement value is idle SDCCH number when interference band is 3 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

29.60 C901230059 Mean number of idle SDCCHs with interference band 4

Definition
Mean number of idle SDCCHs with interference band 4

Description
This measurement value is idle SDCCH number when interference band is 4 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times

29.61 C901230060 Mean number of idle SDCCHs with interference band 5

Definition
Mean number of idle SDCCHs with interference band 5

Description
This measurement value is idle SDCCH number when interference band is 5 in carrier.

Measurement Point
Count when regularly query database.

Unit
Times
29-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-04-04-002 Intelligent TRX Shutdown

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
s

Related Features
ZGO-04-04-002 Intelligent TRX Shutdown

29-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

29.64 C901230063 Number of uplink error frame on 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

29.65 C901230064 Total Number of uplink frame on FR_V1

Description
Enable the function of reporting voice quality information, and count the number of voice 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

29.66 C901230065 Number of uplink error frame on FR_V2

Description
Enable the function of reporting voice quality information, and count the number of error frames of voice version 2 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.
29-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

29.67 C901230066 Total Number of uplink frame on FR_V2

Description
Enable the function of reporting voice quality information, and count the number of voice frames of voice version 2 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

29.68 C901230067 Number of uplink error frame on FR_V3

Description
Enable the function of reporting voice quality information, and count the number of error frames of voice version 3 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

29.69 C901230068 Total Number of uplink frame on FR_V3

Description
Enable the function of reporting voice quality information, and count the number of voice frames of voice version 3 in the measurement report received on the FR channel.
29-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Measurement Point
The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received.

Unit
Times

29.70 C901230069 Number of uplink error frame on HR_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 HR channel.

Measurement Point
The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received.

Unit
Times

29.71 C901230070 Total Number of uplink frame on HR_V1

Description
Enable the function of reporting voice quality information, and count the number of voice frames of voice version 1 in the measurement report received on the HR channel.

Measurement Point
The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received.

Unit
Times

29-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

29.72 C901230071 Number of uplink error frame on HR_V3

Description
Enable the function of reporting voice quality information, and count the number of error frames of voice version 3 in the measurement report received on the HR channel.

Measurement Point
The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received.

Unit
Times

29.73 C901230072 Total Number of uplink frame on HR_V3

Description
Enable the function of reporting voice quality information, and count the number of voice frames of voice version 3 in the measurement report received on the HR channel.

Measurement Point
The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received.

Unit
Times

29.74 C901230073 Number of Samples With Uplink RQ=0 (on SDCCH)

Description
This counter counts uplink RQ = 0 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on SDCCH is 0.
29-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Unit
Number of samples

29.75 C901230074 Number of Samples With Uplink RQ = 1 (on SDCCH)

Description
This counter counts uplink RQ = 1 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on SDCCH is 1.

Unit
Number of samples

29.76 C901230075 Number of Samples With Uplink RQ = 2 (on SDCCH)

Description
This counter counts uplink RQ = 2 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on SDCCH is 2.

Unit
Number of samples

29.77 C901230076 Number of Samples With Uplink RQ = 3 (on SDCCH)

Description
This counter counts uplink RQ = 3 samples on SDCCH.

29-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on SDCCH is 3.

Unit
Number of samples

29.78 C901230077 Number of Samples With Uplink RQ = 4 (on SDCCH)

Description
This counter counts uplink RQ = 4 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on SDCCH is 4.

Unit
Number of samples

29.79 C901230078 Number of Samples With Uplink RQ = 5 (on SDCCH)

Description
This counter counts uplink RQ = 5 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on SDCCH is 5.

Unit
Number of samples

29-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

29.80 C901230079 Number of Samples With Uplink RQ = 6 (on SDCCH)

Description
This counter counts uplink RQ = 6 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on SDCCH is 6.

Unit
Number of samples

29.81 C901230080 Number of Samples With Uplink RQ = 7 (on SDCCH)

Description
This counter counts uplink RQ = 7 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on SDCCH is 7.

Unit
Number of samples

29.82 C901230081 Number of Samples With Downlink RQ = 0 (on SDCCH)

Description
This counter counts downlink RQ = 0 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on SDCCH is 0.
29-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Number of samples

29.83 C901230082 Number of Samples With Downlink RQ = 1 (on SDCCH)

Description
This counter counts downlink RQ = 1 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on SDCCH is 1.

Unit
Number of samples

29.84 C901230083 Number of Samples With Downlink RQ = 2 (on SDCCH)

Description
This counter counts downlink RQ = 2 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on SDCCH is 2.

Unit
Number of samples

29.85 C901230084 Number of Samples With Downlink RQ = 3 (on SDCCH)

Description
This counter counts downlink RQ = 3 samples on SDCCH.

29-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on SDCCH is 3.

Unit
Number of samples

29.86 C901230085 Number of Samples With Downlink RQ = 4 (on SDCCH)

Description
This counter counts downlink RQ = 4 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on SDCCH is 4.

Unit
Number of samples

29.87 C901230086 Number of Samples With Downlink RQ = 5 (on SDCCH)

Description
This counter counts downlink RQ = 5 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on SDCCH is 5.

Unit
Number of samples

29-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

29.88 C901230087 Number of Samples With Downlink RQ = 6 (on SDCCH)

Description
This counter counts downlink RQ = 6 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on SDCCH is 6.

Unit
Number of samples

29.89 C901230088 Number of Samples With Downlink RQ = 7 (on SDCCH)

Description
This counter counts downlink RQ = 7 samples on SDCCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on SDCCH is 7.

Unit
Number of samples

29.90 C901230089 Number of Samples With Uplink RQ = 0 (on TCH)

Description
This counter counts uplink RQ = 0 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on TCH is 0.
29-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Unit
Number of samples

29.91 C901230090 Number of Samples With Uplink RQ = 1 (on TCH)

Description
This counter counts uplink RQ = 1 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on TCH is 1.

Unit
Number of samples

29.92 C901230091 Number of Samples With Uplink RQ = 2 (on TCH)

Description
This counter counts uplink RQ = 2 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on TCH is 2.

Unit
Number of samples

29.93 C901230092 Number of Samples With Uplink RQ = 3 (on TCH)

Description
This counter counts uplink RQ = 3 samples on TCH.

29-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on TCH is 3.

Unit
Number of samples

29.94 C901230093 Number of Samples With Uplink RQ = 4 (on TCH)

Description
This counter counts uplink RQ = 4 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on TCH is 4.

Unit
Number of samples

29.95 C901230094 Number of Samples With Uplink RQ = 5 (on TCH)

Description
This counter counts uplink RQ = 5 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on TCH is 5.

Unit
Number of samples

29-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

29.96 C901230095 Number of Samples With Uplink RQ = 6 (on TCH)

Description
This counter counts uplink RQ = 6 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on TCH is 6.

Unit
Number of samples

29.97 C901230096 Number of Samples With Uplink RQ = 7 (on TCH)

Description
This counter counts uplink RQ = 7 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the uplink receiving quality level on TCH is 7.

Unit
Number of samples

29.98 C901230097 Number of Samples With Downlink RQ = 0 (on TCH)

Description
This counter counts downlink RQ = 0 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on TCH is 0.
29-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Number of samples

29.99 C901230098 Number of Samples With Downlink RQ = 1 (on TCH)

Description
This counter counts downlink RQ = 1 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on TCH is 1.

Unit
Number of samples

29.100 C901230099 Number of Samples With Downlink RQ = 2 (on TCH)

Description
This counter counts downlink RQ = 2 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on TCH is 2.

Unit
Number of samples

29.101 C901230100 Number of Samples With Downlink RQ = 3 (on TCH)

Description
This counter counts downlink RQ = 3 samples on TCH.

29-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on TCH is 3.

Unit
Number of samples

29.102 C901230101 Number of Samples With Downlink RQ = 4 (on TCH)

Description
This counter counts downlink RQ = 4 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on TCH is 4.

Unit
Number of samples

29.103 C901230102 Number of Samples With Downlink RQ = 5 (on TCH)

Description
This counter counts downlink RQ = 5 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on TCH is 5.

Unit
Number of samples

29-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

29.104 C901230103 Number of Samples With Downlink RQ = 6 (on TCH)

Description
This counter counts downlink RQ = 6 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on TCH is 6.

Unit
Number of samples

29.105 C901230104 Number of Samples With Downlink RQ = 7 (on TCH)

Description
This counter counts downlink RQ = 7 samples on TCH.

Measurement Point
This counter is incremented each time the BSC, after receiving a measurement report or pre-processing a measurement report, detects that the downlink receiving quality level on TCH is 7.

Unit
Number of samples

29.106 C901230105 Number of Sample With Interference Band

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database, and counts and accumulates the numbers of the TCH/F, TCH/H, and SDCCH channels in each interference band in the current carrier frequency.

29-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Usage
None

Measurement Point
The measurement point is as A shown in Flowchart of Interference Band Update.

Unit
None

29.107 C901230106 Number of Idle TCH/F With Interference Band 0

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/F channel with the interference band as 0.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29.108 C901230107 Number of Idle TCH/F With Interference Band 1

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/F channel with the interference band as 1.

Usage
None

29-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29.109 C901230108 Number of Idle TCH/F With Interference Band 2

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/F channel with the interference band as 2.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29.110 C901230109 Number of Idle TCH/F With Interference Band 3

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/F channel with the interference band as 3.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

29-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Unit
None

29.111 C901230110 Number of Idle TCH/F With Interference Band 4

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/F channel with the interference band as 4.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29.112 C901230111 Number of Idle TCH/F With Interference Band 5

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/F channel with the interference band as 5.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

29.113 C901230112 Number of Idle TCH/H With Interference Band 0

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 0.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29.114 C901230113 Number of Idle TCH/H With Interference Band 1

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 1.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

29.115 C901230114 Number of Idle TCH/H With Interference Band 2

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 2.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29.116 C901230115 Number of Idle TCH/H With Interference Band 3

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 3.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

29.117 C901230116 Number of Idle TCH/H With Interference Band 4

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 4.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29.118 C901230117 Number of Idle TCH/H With Interference Band 5

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 5.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

29.119 C901230118 Number of Idle TCH/H With Interference Band 0

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 0.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29.120 C901230119 Number of Idle TCH/H With Interference Band 1

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 1.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

29.121 C901230120 Number of Idle TCH/H With Interference Band 2

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 2.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29.122 C901230121 Number of Idle TCH/H With Interference Band 3

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 3.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

29.123 C901230122 Number of Idle TCH/H With Interference Band 4

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 4.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29.124 C901230123 Number of Idle TCH/H With Interference Band 5

Description
When receiving the interference band update message sent by the BTS, the BSC refreshes the interference band info of each idle channel in the database. This counter increases by 1 when the BSC detects an idle TCH/H channel with the interference band as 5.

Usage
None

Measurement Point
The measurement point is shown in Flowchart of Interference Band Update.

Unit
None

29-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

29.125 C901230124 Uplink CIR Normal Grade 0 (Below -2 dB) Sample

Description
This counter counts the samples of normal uplink CIR grade 0 (CIR < -2 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29.126 C901230125 Uplink CIR Normal Grade 1 (-2 to 0.5 dB) Sample
Description
This counter counts the samples of normal uplink CIR grade 1 (CIR range: -2 dB to 0.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29.127 C901230126 Uplink CIR Normal Grade 2 (1 to 3.5 dB) Sample

Description
This counter counts the samples of normal uplink CIR grade 2 (CIR range: 1 dB to 3.5 dB) in measurement reports received from a BTS.

Measurement Point
None

29-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Unit
None

29.128 C901230127 Uplink CIR Normal Grade 3 (4 to 6.5 dB) Sample

Description
This counter counts the samples of normal uplink CIR grade 3 (CIR range: 4 dB to 6.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29.129 C901230128 Uplink CIR Normal Grade 4 (7 to 9.5 dB) Sample

Description
This counter counts the samples of normal uplink CIR grade 4 (CIR range: 7 dB to 9.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29.130 C901230129 Uplink CIR Normal Grade 5 (10 to 12.5 dB) Sample
Description
This counter counts the samples of normal uplink CIR grade 5 (CIR range: 10 dB to 12.5 dB) in measurement reports received from a BTS.

29-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
None

Unit
None

29.131 C901230130 Uplink CIR Normal Grade 6 (13 to 15.5 dB) Sample
Description
This counter counts the samples of normal uplink CIR grade 6 (CIR range: 13 dB to 15.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29.132 C901230131 Uplink CIR Normal Grade 7 (16 to 18.5 dB) Sample
Description
This counter counts the samples of normal uplink CIR grade 7 (CIR range: 16 dB to 18.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

29.133 C901230132 Uplink CIR Normal Grade 8 (19 to 21.5 dB) Sample
Description
This counter counts the samples of normal uplink CIR grade 8 (CIR range: 19 dB to 21.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29.134 C901230133 Uplink CIR Normal Grade 9 (Above 21.5 dB) Sample
Description
This counter counts the samples of normal uplink CIR grade 9 (CIR > 21.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29.135 C901230134 Uplink CIR Improved Grade 0 (Below -2 dB) Sample

Description
This counter counts the samples of improved uplink CIR grade 0 (CIR < -2 dB) in measurement reports received from a BTS.

Measurement Point
None

29-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
None

29.136 C901230135 Uplink CIR Improved Grade 1 (-2 to 0.5 dB) Sample
Description
This counter counts the samples of improved uplink CIR grade 1 (CIR range: -2 dB to 0.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29.137 C901230136 Uplink CIR Improved Grade 2 (1 to 3.5 dB) Sample

Description
This counter counts the samples of improved uplink CIR grade 2 (CIR range: 1 dB to 3.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29.138 C901230137 Uplink CIR Improved Grade 3 (4 to 6.5 dB) Sample

Description
This counter counts the samples of improved uplink CIR grade 3 (CIR range: 4 dB to 6.5 dB) in measurement reports received from a BTS.

29-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Measurement Point
None

Unit
None

29.139 C901230138 Uplink CIR Improved Grade 4 (7 to 9.5 dB) Sample

Description
This counter counts the samples of improved uplink CIR grade 4 (CIR range: 7 dB to 9.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29.140 C901230139 Uplink CIR Improved Grade 5 (10 to 12.5 dB) Sample
Description
This counter counts the samples of improved uplink CIR grade 5 (CIR range: 10 dB to 12.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29-77 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

29.141 C901230140 Uplink CIR Improved Grade 6 (13 to 15.5 dB) Sample
Description
This counter counts the samples of improved uplink CIR grade 6 (CIR range: 13 dB to 15.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29.142 C901230141 Uplink CIR Improved Grade 7 (16 to 18.5 dB) Sample
Description
This counter counts the samples of improved uplink CIR grade 7 (CIR range: 16 dB to 18.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29.143 C901230142 Uplink CIR Improved Grade 8 (19 to 21.5 dB) Sample
Description
This counter counts the samples of improved uplink CIR grade 8 (CIR range: 19 dB to 21.5 dB) in measurement reports received from a BTS.

Measurement Point
None

29-78 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 29 TRX Measurement

Unit
None

29.144 C901230143 Uplink CIR Improved Grade 9 (Above 21.5 dB) Sample
Description
This counter counts the samples of improved uplink CIR grade 9 (CIR > 21.5 dB) in measurement reports received from a BTS.

Measurement Point
None

Unit
None

29-79 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

29-80 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30

Timeslot Measurement
Table of Contents
Overview ..................................................................................................................30-3 C901240001 Maximum value of UL RQ ...................................................................30-3 C901240002 Minimum value of UL RQ ....................................................................30-3 C901240003 Value of UL RQ ...................................................................................30-4 C901240004 Number of scans of UL RQ .................................................................30-5 C901240005 Maximum value of DL RQ ...................................................................30-6 C901240006 Minimum value of DL RQ ....................................................................30-6 C901240007 Value of DL RQ ...................................................................................30-7 C901240008 Number of scans of DL RQ .................................................................30-8 C901240009 Maximum value of received UL signal strength....................................30-8 C901240010 Minimum value of received UL signal strength.....................................30-9 C901240011 Total value of received UL signal strength..........................................30-10 C901240012 Number of received UL signal strength samples................................ 30-11 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-13 C901240016 Number of received DL signal strength samples................................30-14 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-16 C901240020 Number of power scans of BTS power ..............................................30-17 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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(ms) .....................................30-41 C901240044 Number of activated voice channel....................................................30-42 C901240045 Maximum Value of Uplink RQ (on SDCCH) .......................................30-43 C901240046 Minimum Value of Uplink RQ (on SDCCH) ........................................30-43 C901240047 Sum of Uplink RQ (on SDCCH) .........................................................30-44 C901240048 Number of Samples of Uplink RQ (on SDCCH) .................................30-44 C901240049 Maximum Value of Downlink RQ (on SDCCH)...................................30-45 C901240050 Minimum Value of Downlink RQ (on SDCCH)....................................30-45 C901240051 Sum of Downlink RQ (on SDCCH) ....................................................30-45 C901240052 Number of Samples of Downlink RQ (on SDCCH).............................30-46 C901240053 Maximum Value of Received Uplink Signal Strength (on SDCCH) .....30-46 C901240054 Minimum Value of Received Uplink Signal Strength (on SDCCH) ......30-47 C901240055 Total Received Uplink Signal Strength on SDCCH.............................30-47 C901240056 Number of Received Uplink Signal Strength Samples (on SDCCH)...30-47 C901240057 Maximum Value of Received Downlink Signal Strength (on SDCCH) .30-48 C901240058 Minimum Value of Received Downlink Signal Strength (on SDCCH) .30-48 C901240059 Total Value of Received Downlink Signal Strength (on SDCCH) ........30-49 C901240060 Number of Received Downlink Signal Strength Samples (on SDCCH) .................................................................................................................30-49 C901240061 Maximum Value of Uplink RQ (on TCH) ............................................30-49 C901240062 Minimum Value of Uplink RQ (on TCH) .............................................30-50 C901240063 Sum of Uplink RQ (on TCH) ..............................................................30-50 C901240064 Number of Samples of Uplink RQ (on TCH) ......................................30-51 C901240065 Maximum Value of Downlink RQ (on TCH) ........................................30-51 C901240066 Minimum Value of Downlink RQ (on TCH) .........................................30-51 C901240067 Sum of Downlink RQ (on TCH)..........................................................30-52 C901240068 Number of samples of downlink RQ(on TCH) ....................................30-52 C901240069 Maximum Value of Received Uplink Signal Strength (on TCH) ..........30-53 C901240070 Minimum Value of Received Uplink Signal Strength (on TCH) ...........30-53 C901240071 Total Received Uplink Signal Strength on TCH ..................................30-53 C901240072 Number of Received Uplink Signal Strength Samples (on TCH) ........30-54 C901240073 Maximum Value of Received Downlink Signal Strength (on TCH)......30-54 C901240074 Minimum Value of Received Downlink Signal Strength (on TCH).......30-55 C901240075 Total Received Downlink Signal Strength on TCH .............................30-55 C901240076 Number of Received Downlink Signal Strength Samples (on TCH)....30-55

30-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

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 A, as shown in Figure 30-1.
Figure 30-1 BSC Receives the measurement report submitted by BTS

Unit
NA

30.3 C901240002 Minimum value of UL RQ

Definition
Minimum UL RQ
30-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 parameters that evaluate timeslot radio environment.

Measurement Point
After BSC receives the measurement report from BTS, if UL RQ in the report is less than the value in the counter, the UL RQ in the counter is replaced. The measurement point is A, as shown in Figure 30-2.
Figure 30-2 BSC Receives the measurement report submitted by BTS

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.

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.
30-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

Figure 30-3 BSC Receives the measurement report submitted by BTS

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 parameters that evaluate timeslot radio environment.

Measurement Point
The counter increments after BSC receives the measurement report from BTS. The measurement point is A, as shown in Figure 30-4.
Figure 30-4 BSC Receives the measurement report submitted by BTS

Unit
Times

30-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 parameters that evaluate timeslot radio environment.

Measurement Point
After BSC receives the measurement report from BTS, if DL RQ in the report is bigger than the value in the counter, the DL RQ is in the counter replaced. The measurement point is A, as shown in Figure 30-5
Figure 30-5 BSC Receives the measurement report submitted by BTS

Unit
NA

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 parameters that evaluate timeslot radio environment.
30-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

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 A, as shown in Figure 30-6.
Figure 30-6 BSC Receives the measurement report submitted by BTS

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 the parameters that evaluate timeslot radio environment.

Measurement Point
After BSC receives the measurement report from BTS, the counter accumulates DL RQ value for relevant timeslot. The measurement point is A, as shown in Figure 30-7.
Figure 30-7 BSC Receives the measurement report submitted by BTS

30-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 parameters that evaluate timeslot radio environment.

Measurement Point
The counter increments after BSC receives the measurement report from BTS. The measurement point is A, as shown in Figure 30-8.
Figure 30-8 BSC Receives the measurement report submitted by BTS

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.
30-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

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.
Figure 30-9 BSC Receives the measurement report submitted by BTS

Unit
dBm

30.11 C901240010 Minimum value of received UL signal strength

Definition
Minimum value of received UL signal strength

Description
This counter counts Minimum value of received UL signal strength in the measurement report of a timeslot in a cell.

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.

30-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 30-10 BSC Receives the measurement report submitted by BTS

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.

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.
Figure 30-11 BSC Receives the measurement report submitted by BTS

Unit
dBm
30-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

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
The counter increments after BSC receives the measurement report from BTS. The measurement point is A, as shown in Figure 30-12.
Figure 30-12 BSC Receives the measurement report submitted by BTS

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 report of a timeslot in a cell.
30-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. The measurement point is A, as shown in Figure 30-13.
Figure 30-13 BSC Receives the measurement report submitted by BTS

Unit
dBm

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 report of a timeslot in a cell.

Usage
This counter is used to find out the Minimum value of received DL signal strength in a timeslot in a cell. It is one of the parameters that evaluate timeslot radio environment.

Measurement Point
After BSC receives the measurement report from BTS, if DL reception strength in the report is less than the value in the counter, the DL reception strength in the counter is replaced. The measurement point is A, as shown in Figure 30-14.

30-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

Figure 30-14 BSC Receives the measurement report submitted by BTS

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.

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.
Figure 30-15 BSC Receives the measurement report submitted by BTS

Unit
dBm
30-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The counter increments after BSC receives the measurement report from BTS. The measurement point is A, as shown in Figure 30-16.
Figure 30-16 BSC Receives the measurement report submitted by BTS

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.
30-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

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 value for relevant timeslot. The measurement point is A, as shown in Figure 30-17.
Figure 30-17 BSC Receives the measurement report submitted by BTS

Unit
dBm

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
The counter increments after BSC receives the measurement report from BTS. The measurement point is A, as shown in Figure 30-18.

30-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 30-18 BSC Receives the measurement report submitted by BTS

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.

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.
Figure 30-19 BSC Receives the measurement report submitted by BTS

Unit
dBm

30-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

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
The counter increments after BSC receives the measurement report from BTS. The measurement point is A, as shown in Figure 30-20.
Figure 30-20 BSC Receives the measurement report submitted by BTS

Unit
dBm

30.22 C901240021 Number of immediate assignment failure

Definition
Number of immediate assignment failure

Description
This counter counts the number of times of immediate assignment failure in a timeslot in a cell.

30-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter shows the frequency of immediate assignment failure in a timeslot in a cell. It is one of the parameters that evaluate timeslot radio environment.

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 shown in Figure 30-21.
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 the parameters that evaluate timeslot radio environment.

Measurement Point
After BSC sent assignment to MS, if access Timer overtimes, the counter increments in relevant timeslot. The measurement point is A2, as shown in Figure 30-22.
30-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

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.
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 parameters that evaluate timeslot radio environment.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 of the parameters that evaluate timeslot radio environment.

Measurement Point
When BSC received resource indication from BTS updating interference band, if interference band reported is bigger than the value in the counter, the value in the counter is replaced. The measurement point is A, as shown in Figure 30-24.
Figure 30-24 Resource Indication Measurement Point

30-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

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 of the parameters that evaluate timeslot radio environment.

Measurement Point
When BSC received resource indication from BTS updating interference band, if interference band reported is 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.
Figure 30-25 Resource Indication Measurement Point

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the total value of interference band in a timeslot in a cell. It is one of the parameters that evaluate timeslot radio environment.

Measurement Point
When BSC received resource indication from BTS updating interference band, the counter accumulates interference value for relevant timeslot. The measurement point is A, as shown in Figure 30-26.
Figure 30-26 Resource Indication Measurement Point

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 timeslot in a cell. It is one of the parameters that evaluate timeslot radio environment.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

Figure 30-27 Resource Indication Measurement Point

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 timeslot in a cell. It is one of the parameters that evaluate timeslot radio environment.

Measurement Point
The counter increments in relevant timeslot after BSC receives radio link failure from BTS. The measurement point is A, as shown in Figure 30-28.
Figure 30-28 Resource Indication Measurement Point

Unit
Times
30-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 the parameters that evaluate timeslot radio environment.

Measurement Point
When BSC receives measurement report from BTS, calculate the current path loss. Then path balance is calculated according UL and DL path loss. If the path balance calculated is more than the value in the counter, then the value in the counter is replaced. The measurement point is A, as shown in Figure 30-29.
Figure 30-29 BSC Receives the measurement report submitted by BTS

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

Usage
This counter shows the Minimum value of path balance in a timeslot in a cell. It is one of the parameters that evaluate timeslot radio environment.

Measurement Point
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 less than the value in the counter, then the value in the counter is replaced. The measurement point is A, as shown in Figure 30-30.
Figure 30-30 BSC Receives the measurement report submitted by BTS

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
When BSC receives measurement report from BTS, calculate the current path loss. Then 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 30-31 BSC Receives the measurement report submitted by BTS

Unit
dBm

30.33 C901240032 Number of regular scanning and 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.
Figure 30-32 BSC Receives the measurement report submitted by BTS

Unit
Times

30-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

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 the parameters that evaluate timeslot radio environment.

Measurement Point
When BSC receives measurement report from BTS, calculate the current path loss. Then path balance is calculated according UL and DL path loss. The counter accumulates the path balance for relevant timeslot. The measurement point is A, as shown in Figure 30-33.
Figure 30-33 BSC Receives the measurement report submitted by BTS

Unit
dBm

30.35 C901240034 Number of regular scanning and 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 30-34 BSC Receives the measurement report submitted by BTS

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

Figure 30-35 BSC Receives the measurement report submitted by BTS

Unit
dB

30.37 C901240036 Number of regular scanning and 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.
Figure 30-36 BSC Receives the measurement report submitted by BTS

Unit
Times
30-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH. The measurement point is A, as shown in Figure 30-38.

30-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

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
This counter counts the number of call drops on some timeslot in the cell due to radio link failure. After MS obtains SDCCH or TCH, call drop occurs. If the problem is caused by bad downlink receiving quality, the counter increments.

30-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 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-39.
Figure 30-39 Call Drop due to Radio Link Failure during Immediate Assignment Process

The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH. The measurement point is A, as shown in Figure 30-40.

30-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

Figure 30-40 Call Drop due to Radio Link Failure during Assignment Process

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
This counter counts the number of call drops on some timeslot in the cell due to radio link failure. After MS obtains SDCCH or TCH, call drop occurs. If the problem is caused by low uplink receiving level, the counter increments.

30-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 low uplink receiving level. 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-41.
Figure 30-41 Call Drop due to Radio Link Failure during Immediate Assignment Process

The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH. The measurement point is A, as shown in Figure 30-42.

30-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

Figure 30-42 Call Drop due to Radio Link Failure during Assignment Process

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
This counter counts the number of call drops on some timeslot in the cell due to radio link failure. After MS obtains SDCCH or TCH, call drop occurs. If the problem is caused by low downlink receiving level, the counter increments.

30-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 low downlink receiving level. 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-43.
Figure 30-43 Call Drop due to Radio Link Failure during Immediate Assignment Process

The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH. The measurement point is A, as shown in Figure 30-44.

30-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

Figure 30-44 Call Drop due to Radio Link Failure during Assignment Process

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
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 TA being too far, the counter increments.

30-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 TA being too far. 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-45.
Figure 30-45 Call Drop due to Radio Link Failure during Immediate Assignment Process

The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH. The measurement point is A, as shown in Figure 30-46.

30-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

Figure 30-46 Call Drop due to Radio Link Failure during Assignment Process

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
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 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 other radio problems. 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-47.
Figure 30-47 Call Drop due to Radio Link Failure during Immediate Assignment Process

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

Figure 30-48 Call Drop due to Radio Link Failure during Assignment Process

Unit
Times

30.44 C901240043 the valid time of the used voice channel(ms)

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. The measurement point is A, as shown in Figure 30-50.

30-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

Figure 30-50 Measurement Point when Channel Is Activated

Unit
Times

30.46 C901240045 Maximum Value of Uplink RQ (on SDCCH)

Description
This counter records the maximum uplink RQ that is detected in measurement reports received from an SDCCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot and the measured uplink RQ in the report is greater than the current counter value, this counter is updated with the greater uplink RQ value.

Unit
None

30.47 C901240046 Minimum Value of Uplink RQ (on SDCCH)

Description
This counter records the minimum uplink RQ that is detected in measurement reports received from an SDCCH timeslot.

30-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot and the measured uplink RQ in the report is smaller than the current counter value, this counter is updated with the smaller uplink RQ value.

Unit
None

30.48 C901240047 Sum of Uplink RQ (on SDCCH)

Description
This counter calculates the sum of uplink RQs that are detected in measurement reports received from an SDCCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot, this counter adds the measured uplink RQ to the current counter value (the sum of previous uplink RQs).

Unit
None

30.49 C901240048 Number of Samples of Uplink RQ (on SDCCH)

Description
This counter counts the number of times that an uplink RQ is detected in a measurement report received from an SDCCH timeslot.

Measurement Point
This counter is incremented each time the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from the SDCCH timeslot and a measured uplink RQ exists in the report.

Unit
Times

30-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

30.50 C901240049 Maximum Value of Downlink RQ (on SDCCH)

Description
This counter records the maximum downlink RQ that is detected in measurement reports received from an SDCCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot and the measured downlink RQ in the report is greater than the current counter value, this counter is updated with the greater downlink RQ value.

Unit
None

30.51 C901240050 Minimum Value of Downlink RQ (on SDCCH)

Description
This counter records the minimum downlink RQ that is detected in measurement reports received from an SDCCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot and the measured downlink RQ in the report is smaller than the current counter value, this counter is updated with the smaller downlink RQ value.

Unit
None

30.52 C901240051 Sum of Downlink RQ (on SDCCH)

Description
This counter calculates the sum of downlink RQs that are detected in measurement reports received from an SDCCH timeslot.

30-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot, this counter adds the measured downlink RQ to the current counter value (the sum of previous downlink RQs).

Unit
None

30.53 C901240052 Number of Samples of Downlink RQ (on SDCCH)

Description
This counter counts the number of times that a downlink RQ is detected in a measurement report received from an SDCCH timeslot.

Measurement Point
This counter is incremented each time the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot and a measured uplink RQ exists in the report.

Unit
Times

30.54 C901240053 Maximum Value of Received Uplink Signal Strength (on SDCCH)
Description
This counter records the maximum uplink received signal strength that is detected in measurement reports received from an SDCCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot and the measured uplink received signal strength in the report is greater than the current counter value, this counter is updated with the greater value.

Unit
dBm
30-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

30.55 C901240054 Minimum Value of Received Uplink Signal Strength (on SDCCH)
Description
This counter records the minimum uplink received signal strength that is detected in measurement reports received from an SDCCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot and the measured uplink received signal strength in the report is smaller than the current counter value, this counter is updated with the smaller value.

Unit
dBm

30.56 C901240055 Total Received Uplink Signal Strength on SDCCH

Description
This counter calculates the sum of uplink received signal strength that is detected in measurement reports received from an SDCCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot, this counter adds the measured uplink received signal strength in the report to the current counter value (the sum of previous uplink received signal strength).

Unit
dBm

30.57 C901240056 Number of Received Uplink Signal Strength Samples (on SDCCH)
Description
This counter counts the number of times that uplink received signal strength is detected in a measurement report received from an SDCCH timeslot.
30-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from the SDCCH timeslot and a measured uplink received signal strength exists in the report.

Unit
Times

30.58 C901240057 Maximum Value of Received Downlink Signal Strength (on SDCCH)
Description
This counter records the maximum downlink received signal strength that is detected in measurement reports received from an SDCCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot and the measured downlink received signal strength in the report is greater than the current counter value, this counter is updated with the greater value.

Unit
dBm

30.59 C901240058 Minimum Value of Received Downlink Signal Strength (on SDCCH)
Description
This counter records the minimum downlink received signal strength that is detected in measurement reports received from an SDCCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot and the measured downlink received signal strength in the report is smaller than the current counter value, this counter is updated with the smaller value.

Unit
dBm
30-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

30.60 C901240059 Total Value of Received Downlink Signal Strength (on SDCCH)
Description
This counter calculates the sum of downlink received signal strength that is detected in measurement reports received from an SDCCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot, this counter adds the measured downlink received signal strength to the current counter value (the sum of previous downlink received signal strength).

Unit
dBm

30.61 C901240060 Number of Received Downlink Signal Strength Samples (on SDCCH)
Description
This counter counts the number of times that downlink received signal strength is detected in a measurement report received from an SDCCH timeslot.

Measurement Point
This counter is incremented each time the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from an SDCCH timeslot and a measured downlink received signal strength exists in the report.

Unit
Times

30.62 C901240061 Maximum Value of Uplink RQ (on TCH)

Description
This counter records the maximum uplink RQ that is detected in measurement reports received from a TCH timeslot.
30-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot and the measured uplink RQ in the report is greater than the current counter value, this counter is updated with the greater value.

Unit
None

30.63 C901240062 Minimum Value of Uplink RQ (on TCH)

Description
This counter records the minimum uplink RQ that is detected in measurement reports received from a TCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot and the measured uplink RQ in the report is smaller than the current counter value, this counter is updated with the smaller value.

Unit
None

30.64 C901240063 Sum of Uplink RQ (on TCH)

Description
This counter calculates the sum of uplink RQs that are detected in measurement reports received from a TCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot, this counter adds the measured uplink RQ to the current counter value (the sum of previous uplink RQs).

Unit
None

30-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

30.65 C901240064 Number of Samples of Uplink RQ (on TCH)

Description
This counter counts the number of times that uplink RQ is detected in a measurement report received from a TCH timeslot.

Measurement Point
This counter is incremented each time the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot and a measured uplink RQ exists in the report.

Unit
Times

30.66 C901240065 Maximum Value of Downlink RQ (on TCH)

Description
This counter records the maximum downlink RQ that is detected in measurement reports received from a TCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot and the measured downlink RQ in the report is greater than the current counter value, this counter is updated with the greater value.

Unit
None

30.67 C901240066 Minimum Value of Downlink RQ (on TCH)

Description
This counter records the minimum downlink RQ that is detected in measurement reports received from a TCH timeslot.
30-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot and the measured downlink RQ in the report is smaller than the current counter value, this counter is updated with the smaller value.

Unit
None

30.68 C901240067 Sum of Downlink RQ (on TCH)

Description
This counter calculates the sum of downlink RQs that are detected in measurement reports received from a TCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot, this counter adds the measured downlink RQ to the current counter value (the sum of previous downlink RQs).

Unit
None

30.69 C901240068 Number of samples of downlink RQ(on TCH)

Description
This counter counts the number of times that a downlink RQ is detected in a measurement report received from a TCH timeslot.

Measurement Point
This counter is incremented each time the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot and a measured downlink RQ exists in the report.

Unit
Times

30-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

30.70 C901240069 Maximum Value of Received Uplink Signal Strength (on TCH)
Description
This counter records the maximum uplink received signal strength that is detected in measurement reports received from a TCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot and the measured uplink received signal strength in the report is greater than the current counter value, this counter is updated with the greater value.

Unit
dBm

30.71 C901240070 Minimum Value of Received Uplink Signal Strength (on TCH)
Description
This counter records the minimum uplink received signal strength that is detected in measurement reports received from a TCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot and the measured uplink received signal strength in the report is smaller than the current counter value, this counter is updated with the smaller value.

Unit
dBm

30.72 C901240071 Total Received Uplink Signal Strength on TCH

Description
This counter calculates the sum of uplink received signal strength that is detected in measurement reports received from a TCH timeslot.
30-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot, this counter adds the measured uplink received signal strength to the current counter value (the sum of previous uplink received signal strength).

Unit
dBm

30.73 C901240072 Number of Received Uplink Signal Strength Samples (on TCH)
Description
This counter counts the number of times that uplink received signal strength is detected in a measurement report received from a TCH timeslot.

Measurement Point
This counter is incremented each time the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot and a measured uplink received signal strength exists in the report.

Unit
Times

30.74 C901240073 Maximum Value of Received Downlink Signal Strength (on TCH)
Description
This counter records the maximum downlink received signal strength that is detected in measurement reports received from a TCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot and the measured downlink received signal strength in the report is greater than the current counter value, this counter is updated with the greater value.

Unit
dBm
30-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 30 Timeslot Measurement

30.75 C901240074 Minimum Value of Received Downlink Signal Strength (on TCH)
Description
This counter records the minimum downlink received signal strength that is detected in measurement reports received from a TCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot and the measured downlink received signal strength in the report is smaller than the current counter value, this counter is updated with the smaller value.

Unit
dBm

30.76 C901240075 Total Received Downlink Signal Strength on TCH

Description
This counter calculates the sum of downlink received signal strength that is detected in measurement reports received from a TCH timeslot.

Measurement Point
If the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot, this counter adds the measured downlink received signal strength to the current counter value (the sum of previous downlink received signal strength).

Unit
dBm

30.77 C901240076 Number of Received Downlink Signal Strength Samples (on TCH)
Description
This counter counts the number of times that downlink received signal strength is detected in a measurement report received from a TCH timeslot.
30-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the BSC, upon receiving or pre-processing a measurement report, detects that the measurement report was received from a TCH timeslot and a measured downlink received signal strength exists in the report.

Unit
Times

30-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31

SDCCH Measurement
Table of Contents
Overview ..................................................................................................................31-2 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-15 C901250020 Number of SDCCH assignment attempts (MOC) ...............................31-15 C901250021 Number of successful SDCCH assignments (MOC) ..........................31-17 C901250022 Number of unsuccessful SDCCH assignments (MOC) ......................31-18 C901250023 Number of SDCCH assignment attempts (MTC)................................31-19 C901250024 Number of successful SDCCH assignments (MTC) ...........................31-20 C901250025 Number of unsuccessful SDCCH assignments (MTC) .......................31-21 C901250026 Number of SDCCH assignment attempts (call re-establishment) .......31-22 C901250027 Number of successful SDCCH assignments (call re-establishment) ..31-23 C901250028 Number of unsuccessful SDCCH assignments (call re-establishment) ...................................................................................................31-25 C901250029 Number of SDCCH assignment attempts (emergency call)................31-26 C901250030 Number of successful SDCCH assignments (emergency call) ...........31-27 C901250031 Number of unsuccessful SDCCH assignments (emergency call) .......31-28 C901250032 Number of SDCCH assignment attempts (LOC) ................................31-29 C901250033 Number of successful SDCCH assignments (LOC) ...........................31-31 C901250034 Number of unsuccessful SDCCH assignments (LOC) .......................31-32 C901250035 Number of SDCCH assignment attempts (other cause) .....................31-33 C901250036 Number of successful SDCCH assignments (other cause) ................31-34 C901250037 Number of unsuccessful SDCCH assignments (other cause) ............31-35 C901250038 Count of USSD attempts to connect ..................................................31-36 C901250039 Average dialoge time of USSD services ............................................31-37 C901250040 Dialog counts of USSD services ........................................................31-37

31-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 shown in Figure 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)

31-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

The Measurement point Of SDCCH counters in the process of external handover is shown in Figure 31-3.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 31-4 The Process Of Internal Handover (like intra-cell handover)

Figure 31-5 The Process Of External Handover

Unit
Times

Related Features
l l ZGB-03-02-003 Dynamic Configuration of SDCCH ZGO-02-02-004 SDCCH/SDCCH Handover

31-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

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
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), 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). measurement point is A2 as shown in Figure 31-6.
Figure 31-6 The Process Of Immediate Assignment

The

31-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGB-03-02-003 Dynamic Configuration of SDCCH

31.4 C901250010 Number of SDCCH allocation attempts for handover

Definition
Number of SDCCH allocation attempts 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), this counter and C901250011 increment simultaneously. Otherwise, if the channel could not be activated due to receiving channel activation failure message, incorrect channel activation response message, T9103 timeout, channel instance being released or channel being released forcibly, this counter and C901250012 increment simultaneously.

Usage
This counter records the number of SDCCH allocations attempts for handover, including successful allocations (C901250011) and unsuccessful allocations (C901250012).

Measurement Point
BSC activates SDCCH due to handover (C901250011+C901250012). The measurement point is B2 as shown in Figure 31-7and C2 as shown in Figure 31-8.

31-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

Figure 31-7 The Process Of Internal Handover (like intra-cell handover)

Figure 31-8 The Process Of External Handover

Unit
Times

Related Features
l l ZGB-03-02-003 Dynamic Configuration of SDCCH ZGO-02-02-004 SDCCH/SDCCH Handover

31-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 31-9 The Process Of Internal Handover (like intra-cell handover)

31-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

Figure 31-10 The Process Of External Handover

Unit
Times

Related Features
l l ZGB-03-02-003 Dynamic Configuration of SDCCH ZGO-02-02-004 SDCCH/SDCCH Handover

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, incorrect channel activation response message, T9103 timeout, channel instance being released or channel being released forcibly, this counter increments.

Usage
This counter records the number of SDCCH allocations failure for handover.

31-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 31-11 The Process Of Internal Handover (like intra-cell handover)

Figure 31-12 The Process Of External Handover

Unit
Times

Related Features
l ZGB-03-02-003 Dynamic Configuration of SDCCH
31-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

ZGO-02-02-004 SDCCH/SDCCH Handover

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 31-13 The Process Of Internal Handover (like intra-cell handover)

Figure 31-14 The Process Of External Handover

Unit
Times

Related Features
ZGO-02-02-004 SDCCH/SDCCH Handover

31.8 C901250017 Number of SDCCH handover success

Definition
Number of SDCCH handover success
31-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

Description
In the process of handover, when MS accesses successfully in the new channel, BSC will receive assignment complete message ASS_COM (intra-cell handover) or HO_COM (inter-cell handover). If BSC receives successfully above message within assigned time, which means handover succeeds, this counter increments.

Usage
This counter records the number of MS accesses successfully SDCCH newly allocated in the process of handover.

Measurement Point
BSC receives ASS_COM message (intra-cell handover) or HO_COM message (inter-cell handover). The measurement point is B3 as shown in Figure 31-15and C3 as shown in Figure 31-16.
Figure 31-15 The Process Of Internal Handover (like intra-cell handover)

31-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 31-16 The Process Of External Handover

Unit
Times

Related Features
l l ZGB-03-02-003 Dynamic Configuration of SDCCH ZGO-02-02-004 SDCCH/SDCCH Handover

31.9 C901250018 Number of SDCCH handover failure 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.
31-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

Unit
Times

Related Features
l l ZGB-03-02-003 Dynamic Configuration of SDCCH ZGO-02-02-004 SDCCH/SDCCH Handover

31.10 C901250019 Number of SDCCH handover failure without Reconnection

Definition
Number of SDCCH handover failure without Reconnection

Description
If handover fails and at same time BSC has not received any HO_FAILURE message, this counter increments.

Usage
This counter records the number of MS accesses unsuccessfully SDCCH newly allocated in the process of handover and BSC has not received any HO_FAILURE message.

Measurement 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
l l ZGB-03-02-003 Dynamic Configuration of SDCCH ZGO-02-02-004 SDCCH/SDCCH Handover

31.11 C901250020 Number of SDCCH assignment attempts (MOC)

Description
After BSC responds to the channel request due to MOC and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to
31-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message correctly within specified time, it indicates that SDCCH assignment succeeds, this counter and C901250021 accumulate simultaneously. Otherwise, if BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, this counter and C901250022 accumulate simultaneously.

Usage
When the channel access is due to MOC, this counter is used to find out the number of BSC's attempts of making MS use allocated SDCCH by sending the IMM_ASS message to MS, including the number of assignment successes (C901250021) and the number of assignment failures (C901250022). This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the EST_IND message or the assignment completion message, or T3101 is timeout (C901250021+C901250022). The measurement point is A3, as shown in Figure 31-17.
Figure 31-17 Immediate Assignment Flow

Unit
Times

31-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

31.12 C901250021 Number of successful SDCCH assignments (MOC)

Description
After BSC responds to the channel request due to MOC and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message correctly within specified time, it indicates that SDCCH assignment succeeds, and this counter accumulates.

Usage
When the channel access is due to MOC, this counter is used to find out the number of MS's successfully accessing the corresponding SDCCH after BSC sends the IMM_ASS message. The measurement point is A3, as shown in Figure 31-18. This counter is supported in version V6.20.61 or later.
Figure 31-18 Number of successful SDCCH assignments (MOC)

Measurement Point
The counter counts when BSC correctly receives the EST_IND message or the assignment completion message.

Unit
Times
31-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

31.13 C901250022 Number of unsuccessful SDCCH assignments (MOC)

Description
After BSC responds to the channel request due to MOC and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, and this counter accumulates.

Usage
When the channel access is due to MOC, this counter is used to find out the number of MS's failing in accessing the allocated SDCCH after BSC sends the IMM_ASS message. This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the EST_IND message incorrectly or T3101 is timeout. The measurement point is A3, as shown in Figure 31-19.
Figure 31-19 Number of unsuccessful SDCCH assignments (MOC)

Unit
Times
31-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

31.14 C901250023 Number of SDCCH assignment attempts (MTC)

Description
After BSC responds to the channel request due to MTC and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message correctly within specified time, it indicates that SDCCH assignment succeeds, this counter and C901250024 accumulate simultaneously. Otherwise, if BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, this counter and C901250025 accumulate simultaneously.

Usage
When the channel access is due to MTC, this counter is used to find out the number of BSC's attempts of making MS use allocated SDCCH by sending the IMM_ASS message to MS, including the number of assignment successes (C901250024) and the number of assignment failures (C901250025). This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the EST_IND message or the assignment completion message, or T3101 is timeout (C901250024+C901250025). The measurement point is A3, as shown in Figure 31-20.

31-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 31-20 Number of SDCCH assignment attempts (MTC)

Unit
Times

31.15 C901250024 Number of successful SDCCH assignments (MTC)

Description
After BSC responds to the channel request due to MTC and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message correctly within specified time, it indicates that SDCCH assignment succeeds, and this counter accumulates.

Usage
When the channel access is due to MTC, this counter is used to find out the number of MS's successfully accessing the corresponding SDCCH after BSC sends the IMM_ASS message. The measurement point is A3, as shown in Figure 31-21.

31-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

Figure 31-21 Number of successful SDCCH assignments (MTC)

This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC correctly receives the EST_IND message or the assignment completion message.

Unit
Times

31.16 C901250025 Number of unsuccessful SDCCH assignments (MTC)

Description
After BSC responds to the channel request due to MTC and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, and this counter accumulates.

Usage
When the channel access is due to MTC, this counter is used to find out the number of MS's failing in accessing the allocated SDCCH after BSC sends the IMM_ASS message.
31-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the EST_IND message incorrectly or T3101 is timeout. The measurement point is A3, as shown in Figure 31-22.
Figure 31-22 Number of unsuccessful SDCCH assignments (MTC)

Unit
Times

31.17 C901250026 Number of SDCCH assignment attempts (call re-establishment)

Description
After BSC responds to the channel request due to call reestablishment and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message correctly within specified time, it indicates that SDCCH assignment succeeds, this counter and C901250027 accumulate simultaneously. Otherwise, if BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, this counter and C901250028 accumulate simultaneously.
31-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

Usage
When the channel access is due to call reestablishment, this counter is used to find out the number of BSC's attempts of making MS use allocated SDCCH by sending the IMM_ASS message to MS, including the number of assignment successes (C901250027) and the number of assignment failures (C901250028). This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the EST_IND message or the assignment completion message, or T3101 is timeout (C901250027+C901250028). The measurement point is A3, as shown in Figure 31-23.
Figure 31-23 Number of SDCCH assignment attempts (call re-establishment)

Unit
Times

31.18 C901250027 Number of successful SDCCH assignments (call re-establishment)

Description
After BSC responds to the channel request due to call reestablishment and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends

31-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message correctly within specified time, it indicates that SDCCH assignment succeeds, and this counter accumulates.

Usage
When the channel access is due to call reestablishment, this counter is used to find out the number of MS's successfully accessing the corresponding SDCCH after BSC sends the IMM_ASS message. The measurement point is A3, as shown in Figure 31-24.
Figure 31-24 Number of successful SDCCH assignments (call re-establishment)

This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC correctly receives the EST_IND message or the assignment completion message.

Unit
Times

31-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

31.19 C901250028 Number of unsuccessful SDCCH assignments (call re-establishment)

Description
After BSC responds to the channel request due to call reestablishment and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, and this counter accumulates.

Usage
When the channel access is due to call reestablishment, this counter is used to find out the number of MS's failing in accessing the allocated SDCCH after BSC sends the IMM_ASS message. This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the EST_IND message incorrectly or T3101 is timeout. The measurement point is A3, as shown in Figure 31-25.
Figure 31-25 Number of unsuccessful SDCCH assignments (call re-establishment)

31-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

31.20 C901250029 Number of SDCCH assignment attempts (emergency call)

Description
After BSC responds to the channel request due to emergency call and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message correctly within specified time, it indicates that SDCCH assignment succeeds, this counter and C901250030 accumulate simultaneously. Otherwise, if BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, this counter and C901250031 accumulate simultaneously.

Usage
When the channel access is due to emergency call, this counter is used to find out the number of BSC's attempts of making MS use allocated SDCCH by sending the IMM_ASS message to MS, including the number of assignment successes (C901250030) and the number of assignment failures (C901250031). This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the EST_IND message or the assignment completion message, or T3101 is timeout (C901250030+C901250031). The measurement point is A3, as shown in Figure 31-26.

31-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

Figure 31-26 Number of SDCCH assignment attempts (emergency call)

Unit
Times

31.21 C901250030 Number of successful SDCCH assignments (emergency call)

Description
After BSC responds to the channel request due to emergency call and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message correctly within specified time, it indicates that SDCCH assignment succeeds, and this counter accumulates.

Usage
When the channel access is due to emergency call, this counter is used to find out the number of MS's successfully accessing the corresponding SDCCH after BSC sends the IMM_ASS message. The measurement point is A3, as shown in Figure 31-27.

31-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 31-27 Number of successful SDCCH assignments (emergency call)

This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC correctly receives the EST_IND message or the assignment completion message.

Unit
Times

31.22 C901250031 Number of unsuccessful SDCCH assignments (emergency call)

Description
After BSC responds to the channel request due to emergency call and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, and this counter accumulates.

31-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

Usage
When the channel access is due to emergency call, this counter is used to find out the number of MS's failing in accessing the allocated SDCCH after BSC sends the IMM_ASS message. This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the EST_IND message incorrectly or T3101 is timeout. The measurement point is A3, as shown in Figure 31-28.
Figure 31-28 Number of unsuccessful SDCCH assignments (emergency call)

Unit
Times

31.23 C901250032 Number of SDCCH assignment attempts (LOC)

Description
After BSC responds to the channel request due to LOC and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message correctly within specified time, it indicates that SDCCH assignment succeeds, this counter and C901250033 accumulate simultaneously.
31-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Otherwise, if BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, this counter and C901250034 accumulate simultaneously.

Usage
When the channel access is due to LOC, this counter is used to find out the number of BSC's attempts of making MS use allocated SDCCH by sending the IMM_ASS message to MS, including the number of assignment successes (C901250033) and the number of assignment failures (C901250034). This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the EST_IND message or the assignment completion message, or T3101 is timeout (C901250033+C901250034). The measurement point is A3, as shown in Figure 31-29.
Figure 31-29 Number of SDCCH assignment attempts (LOC)

Unit
Times

31-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

31.24 C901250033 Number of successful SDCCH assignments (LOC)

Description
After BSC responds to the channel request due to LOC and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message correctly within specified time, it indicates that SDCCH assignment succeeds, and this counter accumulates.

Usage
When the channel access is due to LOC, this counter is used to find out the number of MS's successfully accessing the corresponding SDCCH after BSC sends the IMM_ASS message. The measurement point is A3, as shown in Figure 31-30.
Figure 31-30 Number of successful SDCCH assignments (LOC)

This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC correctly receives the EST_IND message or the assignment completion message.

Unit
Times
31-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

31.25 C901250034 Number of unsuccessful SDCCH assignments (LOC)

Description
After BSC responds to the channel request due to LOC and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, and this counter accumulates.

Usage
When the channel access is due to LOC, this counter is used to find out the number of MS's failing in accessing the allocated SDCCH after BSC sends the IMM_ASS message. This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the EST_IND message incorrectly or T3101 is timeout. The measurement point is A3, as shown in Figure 31-31.
Figure 31-31 Number of unsuccessful SDCCH assignments (LOC)

Unit
Times
31-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

31.26 C901250035 Number of SDCCH assignment attempts (other cause)

Description
After BSC responds to the channel request due to causes beyond what have been mentioned previously and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message correctly within specified time, it indicates that SDCCH assignment succeeds, this counter and C901250036 accumulate simultaneously. Otherwise, if BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, this counter and C901250037 accumulate simultaneously.

Usage
When the channel access is due to causes beyond what have been mentioned previously, this counter is used to find out the number of BSC's attempts of making MS use allocated SDCCH by sending the IMM_ASS message to MS, including the number of assignment successes (C901250036) and the number of assignment failures (C901250037). This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the EST_IND message or the assignment completion message, or T3101 is timeout (C901250036+C901250037). The measurement point is A3, as shown in Figure 31-32.

31-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 31-32 Number of SDCCH assignment attempts (other cause)

Unit
Times

31.27 C901250036 Number of successful SDCCH assignments (other cause)

Description
After BSC responds to the channel request due to causes beyond what have been mentioned previously and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message correctly within specified time, it indicates that SDCCH assignment succeeds, and this counter accumulates.

Usage
When the channel access is due to causes beyond what have been mentioned previously, this counter is used to find out the number of MS's successfully accessing the corresponding SDCCH after BSC sends the IMM_ASS message. The measurement point is A3, as shown in Figure 31-33.

31-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

Figure 31-33 Number of successful SDCCH assignments (other cause)

This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC correctly receives the EST_IND message or the assignment completion message.

Unit
Times

31.28 C901250037 Number of unsuccessful SDCCH assignments (other cause)

Description
After BSC responds to the channel request due to causes beyond what have been mentioned previously and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, and this counter accumulates.

31-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
When the channel access is due to causes beyond what have been mentioned previously, this counter is used to find out the number of MS's failing in accessing the allocated SDCCH after BSC sends the IMM_ASS message. This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the EST_IND message incorrectly or T3101 is timeout. The measurement point is A3, as shown in Figure 31-34.
Figure 31-34 Number of unsuccessful SDCCH assignments (other cause)

Unit
Times

31.29 C901250038 Count of USSD attempts to connect

Description
This counter counts the number of attempts of connecting USSD service. This counter is supported in version V6.20.614c.

Unit
Times

31-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 31 SDCCH Measurement

Statistics Object
Cell

31.30 C901250039 Average dialoge time of USSD services

Description
This counter counts the average conversation time of USSD service. This counter is supported in version V6.20.614c.

Unit
Second

Statistics Object
Cell

31.31 C901250040 Dialog counts of USSD services

Description
This counter counts the number of conversations of USSD service. This counter is supported in version V6.20.614c.

Unit
Times

Statistics Object
Cell

31-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

31-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32

TCH/F Measurement
Table of Contents
Overview ..................................................................................................................32-6 C901260002 Number of signaling TCH/F seizure success for assignment ...............32-9 C901260005 Number of signaling TCH/F seizure success for handover.................32-10 C901260007 Number of signaling TCH/F allocation attempts for assignment .........32-13 C901260010 Number of signaling TCH/F allocation attempts for handover ............32-14 C901260011 Number of signaling TCH/F allocation success for handover .............32-17 C901260013 Number of signaling TCH/F assignment attempts for assignment ......32-19 C901260016 Number of signaling TCH/F handover attempt ...................................32-20 C901260017 Number of signaling TCH/F handover success ..................................32-23 C901260018 Number of signaling TCH/F handover failure with reconnection.........32-25 C901260019 Number of signaling TCH/F handover failure without reconnection ....32-27 C901260021 Number of voice TCH/F seizure success for assignment ...................32-28 C901260024 Number of voice TCH/F seizure success for handover ......................32-29 C901260026 Number of TCH/F allocation attempts for assignment (speech version 1) ...........................................................................................................................32-32 C901260032 Number of TCH/F allocation attempts by BSC for handover (speech version 1) ...............................................................................................................32-33 C901260033 Number of TCH/F allocation success by BSC for handover (speech version 1) ...............................................................................................................32-36 C901260038 Number of TCH/F allocation attempts for assignment (speech version 2) ...........................................................................................................................32-38 C901260044 Number of TCH/F allocation attempts by BSC for handover (speech version 2) ...............................................................................................................32-40 C901260045 Number of TCH/F allocation success by BSC for handover (speech version 2) ...............................................................................................................32-42 C901260050 Number of TCH/F allocation attempts by BSC for assignment (speech version 3) ...............................................................................................................32-45 C901260056 Number of TCH/F allocation attempts by BSC for handover (speech version 3) ...............................................................................................................32-46 C901260057 Number of TCH/F allocation success by BSC for handover (speech version 3) ...............................................................................................................32-49 C901260062 Number of voice TCH/F assignment attempts by BSC.......................32-51 C901260065 Number of voice TCH/F handover attempts.......................................32-53 C901260067 Number of Voice TCH/F handover failure with reconnection ..............32-56 C901260068 Number of Voice TCH/F handover failure messages do not received by BSC...................................................................................................................32-57 C901260070 Number of data TCH/F seizure success for assignment ....................32-58
32-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901260073 Number of data TCH/F seizure success for handover........................32-60 C901260075 Number of data TCH/F allocation attempts for assignment ................32-62 C901260081 Number of data TCH/F allocation attempts by BSC for handover ......32-64 C901260082 Number of data TCH/F allocation success for handover ....................32-66 C901260087 Number of data TCH/F assignment attempts.....................................32-69 C901260090 Number of data TCH/F handover attempts ........................................32-70 C901260092 Number of data TCH/F handover failure with reconnection................32-73 C901260093 Number of data TCH/F handover failure messages do not received by BSC...................................................................................................................32-74 C901260094 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 1).....................................................................32-75 C901260095 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 1)................................................32-76 C901260096 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 1).....................................................................32-77 C901260097 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 1)................................................32-79 C901260098 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 2).....................................................................32-80 C901260099 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 2)................................................32-81 C901260100 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 2).....................................................................32-82 C901260101 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 2)................................................32-84 C901260102 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 3).....................................................................32-85 C901260103 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 3)................................................32-86 C901260104 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 3).....................................................................32-87 C901260105 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 3)................................................32-89 C901260106 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 1) ...............................................................32-90 C901260107 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 1)..........................................................................32-91 C901260108 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 1)...............................................................................32-92 C901260109 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 1)...................................................................32-93 C901260110 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 1) .............................................................................32-94 C901260111 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 1) ..................................................................................32-95
32-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

C901260112 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 2) ...............................................................32-96 C901260113 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 2)..........................................................................32-97 C901260114 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 2)...............................................................................32-98 C901260115 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 2)...................................................................32-99 C901260116 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 2) ...........................................................................32-100 C901260117 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 2) ................................................................................32-101 C901260118 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 3) .............................................................32-102 C901260119 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 3)........................................................................32-103 C901260120 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 3).............................................................................32-104 C901260121 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 3).................................................................32-105 C901260122 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 3) ...........................................................................32-106 C901260123 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 3) ................................................................................32-107 C901260124 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (data) .................................................................................32-108 C901260125 Number of TCH/F allocation failure due to request UDP port failure for assignment (data) ...........................................................................................32-109 C901260126 Number of TCH/F allocation failure due to AIPB connection failure for assignment (data) ................................................................................................ 32-110 C901260127 Number of TCH/F allocation failure due to request AIPB resource failure for handover (data) .................................................................................... 32-111 C901260128 Number of TCH/F allocation failure due to request UDP port failure for handover (data)............................................................................................... 32-112 C901260129 Number of TCH/F allocation failure due to AIPB connection failure for handover (data).................................................................................................... 32-113 C901260130 Number of assign TCH/F release by forced handover to forced handover source .................................................................................................. 32-114 C901260131 Number of assign TCH/F release by forced handover to queuing user...................................................................................................................... 32-115 C901260132 Number of restore TCH/F release by forced handover to DBS......... 32-116 C901260133 Number of assign TCHF release by forced release to forced release source .................................................................................................................. 32-116 C901260134 Number of assign TCH/F release by forced release to queuing user...................................................................................................................... 32-117
32-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901260135 Number of restore TCH/F release by forced release to DBS............ 32-117 C901260136 Number of signaling TCH/F seizure failure for assignment (cause:Abis) ......................................................................................................... 32-118 C901260137 Number of signaling TCH/F seizure failure for handover (cause:Abis) ......................................................................................................... 32-119 C901260138 Number of voice TCH/F seizure failure for assignment (cause:Abis) . 32-119 C901260139 Number of voice TCH/F seizure failure for handover (cause:Abis ) ..32-120 C901260140 Number of data TCH/F seizure failure for assignment (cause:Abis) .32-120 C901260141 Number of data TCH/F seizure failure for handover (cause:Abis) ....32-121 C901260142 Number of signaling TCH/F seizure failure for assignment (cause:radio resource) .........................................................................................32-121 C901260143 Number of signaling TCH/F seizure failure for handover (cause:radio resource)..............................................................................................................32-122 C901260144 Number of voice TCH/F seizure failure for assignment (cause:radio resource)..............................................................................................................32-122 C901260145 Number of voice TCH/F seizure failure for handover (cause:radio resource)..............................................................................................................32-123 C901260146 Number of data TCH/F seizure failure for assignment (cause:radio resource)..............................................................................................................32-123 C901260147 Number of data TCH/F seizure failure for handover (cause:radio resource)..............................................................................................................32-124 C901260148 Number of FR_V1 assignment attempts ..........................................32-124 C901260149 Number of FR_V1 assignment success...........................................32-125 C901260150 Number of FR_V2 assignment attempts ..........................................32-125 C901260151 Number of FR_V2 assignment success...........................................32-126 C901260152 Number of FR_V3 assignment attempts ..........................................32-126 C901260153 Number of FR_V3 assignment success...........................................32-127 C901260154 Number of FR_V1 handover............................................................32-127 C901260155 Number of FR_V1 handover success ..............................................32-128 C901260156 Number of FR_V2 handover............................................................32-128 C901260157 Number of FR_V2 handover success ..............................................32-129 C901260158 Number of FR_V3 handover............................................................32-129 C901260159 Number of FR_V3 handover success ..............................................32-130 C901260185 Resourse releasing of ordinary users due to being grabbed (TCH/F) ................................................................................................................32-130 C901260186 Handover of ordinary users due to be grabbed (TCH/F) ..................32-132 C901260187 Number of Channel Request of priority users (TCH/F).....................32-133 C901260188 Number of Successful Channel seize of priority users (TCH/F)........32-135 C901260189 Number of Successful grabbing channel of priority users (TCH/F) ...32-136 C901260190 Number of TCH/F Allocation Attempts for Assignment (Speech Version 4).............................................................................................................32-137 C901260191 Number of TCH/F Allocation Success for Assignment (Speech Version 4).............................................................................................................32-138 C901260192 Number of TCH/F Allocation Failure Due to Channel Activation Failure for Assignment (Speech Version 4)...........................................................32-140
32-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

C901260193 Number of TCH/F Allocation Failure Due to BIU Connection Failure for Assignment (Speech Version 4) ......................................................................32-141 C901260194 Number of TCH/F Allocation Attempts by BSC for Handover (Speech Version 4).............................................................................................................32-142 C901260195 Number of TCH/F Allocation Success by BSC for Handover (Speech Version 4).............................................................................................................32-145 C901260196 Number of TCH/F Allocation Failure Due to Channel Activation Failure for Handover (Speech Version 4) ..............................................................32-147 C901260197 Number of TCH/F Allocation Failure Due to BIU Connection Failure for Handover (Speech Version 4)..........................................................................32-149 C901260198 Number of TCH/F Allocation Attempts for Assignment (Speech Version 5).............................................................................................................32-150 C901260199 Number of TCH/F Allocation Success for Assignment (Speech Version 5).............................................................................................................32-151 C901260200 Number of TCH/F Allocation Failure Due to Channel Activation Failure for Assignment (Speech Version 5)...........................................................32-153 C901260201 Number of TCH/F Allocation Failure Due to BIU Connection Failure for Assignment (Speech Version 5) ......................................................................32-154 C901260202 Number of TCH/F Allocation Attempts by BSC for Handover (Speech Version 5).............................................................................................................32-155 C901260203 Number of TCH/F Allocation Success by BSC for Handover (Speech Version 5).............................................................................................................32-158 C901260204 Number of TCH/F Allocation Failure Due to Channel Activation Failure for Handover (Speech Version 5) ..............................................................32-160 C901260205 Number of TCH/F Allocation Failure Due to BIU Connection Failure for Handover (Speech Version 5)..........................................................................32-162 C901260206 Number of TCH/F Allocation Failure Due to Request AIPB Resource Failure for Assignment (Speech Version 4)...........................................................32-163 C901260207 Number of TCH/F Allocation Failure Due to Request UDP Port Failure for Assignment (Speech Version 4)...........................................................32-164 C901260208 Number of TCH/F Allocation Failure Due to AIPB Connection Failure for Assignment (Speech Version 4) ......................................................................32-165 C901260209 Number of TCH/F Allocation Failure Due to Request AIPB Resource Failure for Handover (Speech Version 4) ..............................................................32-166 C901260210 Number of TCH/F Allocation Failure Due to Request UDP Port Failure for Handover (Speech Version 4) ..............................................................32-167 C901260211 Number of TCH/F Allocation Failure Due to AIPB Connection Failure for Handover (Speech Version 4)..........................................................................32-168 C901260212 Number of TCH/F Allocation Failure Due to Request AIPB Resource Failure for Assignment (Speech Version 5)...........................................................32-169 C901260213 Number of TCH/F Allocation Failure Due to Request UDP Port Failure for Assignment (Speech Version 5)...........................................................32-170 C901260214 Number of TCH/F Allocation Failure Due to AIPB Connection Failure for Assignment (Speech Version 5) ......................................................................32-171

32-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901260215 Number of TCH/F Allocation Failure Due to Request AIPB Resource Failure for Handover (Speech Version 5) ..............................................................32-172 C901260216 Number of TCH/F Allocation Failure Due to Request UDP Port Failure for Handover (Speech Version 5) ..............................................................32-174 C901260217 Number of TCH/F Allocation Failure Due to AIPB Connection Failure for Handover (Speech Version 5)..........................................................................32-175 C901260218 Number of FR_V4 Assignment Attempts .........................................32-176 C901260219 Number of FR_V4 Assignment Success..........................................32-176 C901260220 Number of FR_V5 Assignment Attempts .........................................32-177 C901260221 Number of FR_V5 Assignment Success..........................................32-177 C901260222 Number of FR_V4 Handover ...........................................................32-178 C901260223 Number of FR_V4 Handover Success .............................................32-178 C901260224 Number of FR_V5 Handover ...........................................................32-179 C901260225 Number of FR_V5 Handover Success .............................................32-179

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

32-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-2 Common assignment flow (internal TC)

Figure 32-3 Common assignment flow (external TC)

During internal and external TC, for the measurement positions of TCH/F counter in internal handover flow (like intra-cell handover), see Figure 32-4and Figure 32-5.

32-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-6 External handover flow (internal TC)

Figure 32-7 External handover flow (external TC)

32.2 C901260002 Number of signaling TCH/F seizure success for assignment

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-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
Figure 32-8 Immediate assignment flow

Unit
Times

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

32.3 C901260005 Number of signaling TCH/F seizure 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. After BSC receives channel request message, it will try to allocate channel for this request. 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-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

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.
Figure 32-9 Internal handover (like intra-cell handover) flow (internal TC)

Figure 32-10 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

32-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-11 External handover flow (internal TC)

Figure 32-12 External handover flow (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking

32-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

32.4 C901260007 Number of signaling TCH/F allocation attempts for assignment

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.
Figure 32-13 Immediate assignment flow

32-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

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

32.5 C901260010 Number of signaling TCH/F allocation attempts for handover

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

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-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-14 Internal handover (like intra-cell handover) flow (internal TC)

Figure 32-15 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

32-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-16 External handover flow (internal TC)

Figure 32-17 External handover flow (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking

32-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

32.6 C901260011 Number of signaling TCH/F allocation success for handover

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 activation success, CHL_ACT_ACK message sent by BTS will be received, indicating 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.
Figure 32-18 Internal handover (like intra-cell handover) flow (internal TC)

32-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-19 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 32-20 External handover flow (internal TC)

32-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-21 External handover flow (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking

32.7 C901260013 Number of signaling TCH/F 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. 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. 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.

32-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 32-22 Immediate assignment flow

Unit
Times

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

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.
32-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

For intra-cell handover, handover success symbolic message is ASS_COM; for inter-cell handover and external handover, handover success symbolic message is HO_COM. For intra-cell and inter-cell handover, this counter accumulates on the basis of source instance; for external handover, this counter accumulates on target instance because source instance doesnt at this BSC side.

Measurement Point
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.
Figure 32-23 Internal handover (like intra-cell handover) flow (internal TC)

Figure 32-24 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

32-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-25 External handover flow (internal TC)

Figure 32-26 External handover flow (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking

32-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

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. For intra-cell and inter-cell handover, this counter accumulates on the basis of source instance; for external handover, this counter accumulates on target instance because source instance doesnt at this BSC side.

Measurement Point
BSC receives ASS_COM or HO_COM message. The measurement points are C4 and D4, as shown in Figure 32-27, Figure 32-28, Figure 32-29, and Figure 32-30.
Figure 32-27 Internal handover (like intra-cell handover) flow (internal TC)

32-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-28 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 32-29 External handover flow (internal TC)

32-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-30 External handover flow (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking

32.10 C901260018 Number of signaling TCH/F 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-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking

32-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

32.11 C901260019 Number of signaling TCH/F 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.
Figure 32-33 Internal handover (internal TC intra-cell handover) failure flow 2

Figure 32-34 Internal handover (internal TC intra-cell handover) failure flow 3

32-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking

32.12 C901260021 Number of voice TCH/F seizure success for assignment

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. After BSC receives channel request message, it will try to allocate channel for this request. 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.

Measurement Point
BSC successfully applies for channel (due to assignment, used for voice channel) and does successful seizure, or BSC receives internal waiting resource effective message. The measurement point is B1, as shown in Figure 32-35, Figure 32-36.
Figure 32-35 Common assignment flow (internal TC)

32-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-36 Common assignment flow (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.13 C901260024 Number of voice TCH/F seizure success for handover

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. After BSC receives channel request message, it will try to allocate channel for this request. 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.

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-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-37 Internal handover (like intra-cell handover) flow (internal TC)

Figure 32-38 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

32-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-39 External handover flow (internal TC)

Figure 32-40 External handover flow (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

32.14 C901260026 Number of TCH/F allocation 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). After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC firstly finishes connection, then sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation succeeds, BSC will receive CHL_ACT_ACK message sent by BTS, indicating TCH/F allocation success, this counter and C900060023 accumulate simultaneously; reversely, if failed, this counter and the counter that corresponds to failure will accumulate simultaneously.

Measurement Point
This counter accumulates when allocation succeeds or fails (due to assignment, used for voice channel, using speech version 1). The measurement points are B2 and B3, as shown in Figure 32-41, Figure 32-42.
Figure 32-41 Common assignment flow (internal TC)

32-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-42 Common assignment flow (external TC)

Unit
Times

Related Features
l l l ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.15 C901260032 Number of TCH/F allocation 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 channel (for speech version 1), including the number of allocation success (C901260033) and failure (C900060156+C900060157+C900060158+C900060159). After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC firstly finishes connection, then sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation succeeds, BSC will receive CHL_ACT_ACK message sent by BTS, indicating TCH/F allocation success, this counter and C901260033 accumulate simultaneously; reversely, if failed, this counter and the counter that corresponds to failure will accumulate simultaneously.

32-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 shown in Figure 32-43, Figure 32-44, Figure 32-45, and Figure 32-46.
Figure 32-43 Internal handover (like intra-cell handover) flow (internal TC)

Figure 32-44 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

32-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-45 External handover flow (internal TC)

Figure 32-46 External handover flow (external TC)

Unit
Times

Related Features
l l l l ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

32.16 C901260033 Number of TCH/F allocation success by BSC for handover (speech version 1)
Definition
Number of TCH/F allocation success by BSC for handover(speech version 1)

Description
This counter counts the number of TCH/F allocation success during handover of voice channel (for speech version 1). After BSC responds channel request message allocation and successfully seizes channel, BSC sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation success, CHL_ACT_ACK message sent by BTS will be received, indicating TCH/F allocation success, this counter accumulates.

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 points are C3 and D3, as shown in Figure 32-47, Figure 32-48, Figure 32-49, and Figure 32-50.
Figure 32-47 Internal handover (like intra-cell handover) flow (internal TC)

32-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-48 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 32-49 External handover flow (internal TC)

32-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-50 External handover flow (external TC)

Unit
Times

Related Features
l l l l ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.17 C901260038 Number of TCH/F allocation attempts for assignment (speech version 2)
Definition
Number of TCH/F allocation attempts for assignment (speech version 2)

Description
This counter counts the number of TCH/F allocation attempts when assigning voice channel (for speech version 2), including the number of allocation success (C900060025) and failure (C900060141+C900060142+C900060143+C900060144). After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC firstly finishes connection, then sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation succeeds, BSC will receive CHL_ACT_ACK message sent by BTS, indicating TCH/F allocation success, this counter and C900060025 accumulate simultaneously; reversely, if failed, this counter and the counter that corresponds to failure will accumulate simultaneously.

32-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Measurement Point
This counter accumulates when allocation succeeds or fails (due to assignment, used for voice channel, using speech version 2). The measurement points are B2 and B3, as shown in Figure 32-51, Figure 32-52.
Figure 32-51 Common assignment flow (internal TC)

Figure 32-52 Common assignment flow (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

32.18 C901260044 Number of TCH/F allocation attempts by BSC for handover (speech version 2)
Definition
Number of TCH/F allocation attempts by BSC for handover (speech version 2)

Description
This counter counts the number of TCH/F allocation attempts during handover of voice channel (for speech version 2), including the number of allocation success (C901260045) and failure (C900060160+C900060161+C900060162+C900060163). After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC firstly finishes connection, then sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation succeeds, BSC will receive CHL_ACT_ACK message sent by BTS, indicating TCH/F allocation success, this counter and C901260045 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 handover, used for voice channel, using speech version 2). The measurement points are C3 and D3, as shown in Figure 32-53, Figure 32-54, Figure 32-55, and Figure 32-56.
Figure 32-53 Internal handover (like intra-cell handover) flow (internal TC)

32-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-54 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 32-55 External handover flow (internal TC)

32-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-56 External handover flow (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.19 C901260045 Number of TCH/F allocation success by BSC for handover (speech version 2)
Definition
Number of TCH/F allocation success by BSC for handover (speech version 2)

Description
This counter counts the number of TCH/F allocation success during handover of voice channel (for speech version 2). After BSC responds channel request message allocation and successfully seizes channel, BSC sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation success, CHL_ACT_ACK message sent by BTS will be received, indicating TCH/F allocation success, this counter accumulates.

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 2). The measurement

32-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

points are C3 and D3, as shown in Figure 32-57, Figure 32-58, Figure 32-59, and Figure 32-60.
Figure 32-57 Internal handover (like intra-cell handover) flow (internal TC)

Figure 32-58 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

32-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-59 External handover flow (internal TC)

Figure 32-60 External handover flow (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

32.20 C901260050 Number of TCH/F allocation attempts by BSC for assignment (speech version 3)
Definition
Number of TCH/F allocation attempts for assignment (speech version 3)

Description
This counter counts the number of TCH/F allocation attempts when assigning voice channel (for speech version 3), including the number of allocation success (C900060026) and failure (C900060027+C900060145+C900060146+C900060147). After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC firstly finishes connection, then sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation succeeds, BSC will receive CHL_ACT_ACK message sent by BTS, indicating TCH/F allocation success, this counter and C900060026 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 3). The measurement points are B2 and B3, as shown in Figure 32-61, Figure 32-62.
Figure 32-61 Common assignment flow (internal TC)

32-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-62 Common assignment flow (external TC)

Unit
Times

Related Features
l l l ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.21 C901260056 Number of TCH/F allocation attempts by BSC for handover (speech version 3)
Definition
Number of TCH/F allocation attempts by BSC for handover (speech version 3)

Description
This counter counts the number of TCH/F allocation attempts during handover of voice channel (for speech version 3), including the number of allocation success (C901260057) and failure (C900060164+C900060165+C900060166+C900060167). After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC firstly finishes connection, then sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation succeeds, BSC will receive CHL_ACT_ACK message sent by BTS, indicating TCH/F allocation success, this counter and C901260057 accumulate simultaneously; reversely, if failed, this counter and the counter that corresponds to failure will accumulate simultaneously.

32-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Measurement Point
This counter accumulates when allocation succeeds or fails (due to handover, used for voice channel, using speech version 3). The measurement points are C3 and D3, as shown in Figure 32-63, Figure 32-64, Figure 32-65, and Figure 32-66.
Figure 32-63 Internal handover (like intra-cell handover) flow (internal TC)

Figure 32-64 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

32-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-65 External handover flow (internal TC)

Figure 32-66 External handover flow (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

32.22 C901260057 Number of TCH/F allocation success by BSC for handover (speech version 3)
Definition
Number of TCH/F allocation success by BSC for handover (speech version 3)

Description
This counter counts the number of TCH/F allocation success during handover of voice channel (for speech version 3). After BSC responds channel request message allocation and successfully seizes channel, BSC sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation success, CHL_ACT_ACK message sent by BTS will be received, indicating TCH/F allocation success, this counter accumulates.

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 3). The measurement points are C3 and D3, as shown in Figure 32-67, Figure 32-68, Figure 32-69, and Figure 32-70.
Figure 32-67 Internal handover (like intra-cell handover) flow (internal TC)

32-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-68 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 32-69 External handover flow (internal TC)

32-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-70 External handover flow (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.23 C901260062 Number of voice TCH/F assignment 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). 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. For the assignment form port A, this counter and C900060028 accumulate simultaneously after receiving assignment success message. This counter and C900060029 accumulate simultaneously if MS access notice cant be received within specified duration, that is, this assignment failed at this time.

32-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 32-71 Common assignment flow (internal TC)

Figure 32-72 Common assignment flow (external TC)

Unit
Times

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

32-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

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. For intra-cell and inter-cell handover, this counter accumulates on the basis of source instance; for external handover, this counter accumulates on target instance because source instance doesnt at this BSC side.

Measurement Point
This counter accumulates when BSC receives ASS_COM/HO_COM message, ASS_FAIL/HO_FAIL message, or messages of exception, released instance, force-released instance, or timer timeout. The measurement points are C4 and D4, as shown in Figure 32-73, Figure 32-74, Figure 32-75, and Figure 32-76.

32-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-73 Internal handover (like intra-cell handover) flow (internal TC)

Figure 32-74 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

32-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-75 External handover flow (internal TC)

Figure 32-76 External handover flow (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking

32-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

32.25 C901260067 Number of Voice TCH/F handover failure with reconnection

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
BSC receives ASS_FAIL or HO_FAIL message. The measurement points are C4 and D4, as shown in Figure 32-77, Figure 32-78.
Figure 32-77 Internal handover (internal TC intra-cell handover) failure flow 1

32-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-78 External handover failure flow (internal TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking

32.26 C901260068 Number of Voice TCH/F handover failure messages do not received by BSC
Definition
Number of Voice TCH/F handover failure messages do not received by BSC

Description
This counter counts the number of voice TCH/F handover failure without response during handover of voice channel. This counter accumulates when handover fails or it cant return to source channel after BSC sends assignment / handover command to MS.

Measurement Point
This counter accumulates when BSC receives messages of exception, timer timeout, released instance, or force-released instance. The measurement points are C4 and D4, as shown in Figure 32-79, Figure 32-80.
32-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-79 Internal handover (internal TC intra-cell handover) failure flow 2

Figure 32-80 Internal handover (internal TC intra-cell handover) failure flow 3

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking

32.27 C901260070 Number of data TCH/F seizure success for assignment

Definition
Number of data TCH/F seizure success for assignment

Description
This counter counts the number of data TCH/F seizure success during assignment of signaling channel.
32-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

After BSC receives channel request message, it will try to allocate channel for this request. 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.

Measurement Point
BSC successfully applies for channel (due to assignment, used for data channel) and does successful seizure, or BSC receives internal waiting resource effective message. The measurement point is B1, as shown in Figure 32-81, Figure 32-82.
Figure 32-81 Common assignment flow (internal TC)

Figure 32-82 Common assignment flow (external TC)

Unit
Times

32-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.28 C901260073 Number of data TCH/F seizure success for handover

Definition
Number of data TCH/F seizure success for handover

Description
This counter counts the number of data TCH/F seizure success during handover of signaling channel. After BSC receives channel request message, it will try to allocate channel for this request. 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.

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.
Figure 32-83 Internal handover (like intra-cell handover) flow (internal TC)

32-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-84 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 32-85 External handover flow (internal TC)

32-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-86 External handover flow (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.29 C901260075 Number of data TCH/F allocation attempts for assignment

Definition
Number of data TCH/F allocation attempts for assignment

Description
This counter counts the number of data TCH/F allocation attempts when assigning signaling channel, including the number of allocation success (C900060034) and failure (C900060035+C900060148+C900060149+C900060150).

Usage
After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC firstly finishes connection, then sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation succeeds, BSC will receive CHL_ACT_ACK message sent by BTS, indicating TCH/F allocation success, this counter and C900060034 accumulate simultaneously; reversely, if failed, this counter and the counter that corresponds to failure will accumulate simultaneously.
32-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Measurement Point
This counter accumulates when allocation succeeds or fails (due to assignment, used for data channel). The measurement points are B2 and B3, as shown in Figure 32-87, Figure 32-88.
Figure 32-87 Common assignment flow (internal TC)

Figure 32-88 Common assignment flow (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

32.30 C901260081 Number of data TCH/F allocation 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). After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC firstly finishes connection, then sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation succeeds, BSC will receive CHL_ACT_ACK message sent by BTS, indicating TCH/F allocation success, this counter and C901260082 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 handover, used for 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.
Figure 32-89 Internal handover (like intra-cell handover) flow (internal TC)

32-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-90 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 32-91 External handover flow (internal TC)

32-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-92 External handover flow (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.31 C901260082 Number of data TCH/F allocation success for handover

Definition
Number of data TCH/F allocation success for handover

Description
This counter counts the number of data TCH/F allocation success during handover of signaling channel. After BSC responds channel request message allocation and successfully seizes channel, BSC sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation success, CHL_ACT_ACK message sent by BTS will be received, indicating 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 data channel. The measurement

32-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

points are C3 and D3, as shown in Figure 32-93, Figure 32-94, Figure 32-95, and Figure 32-96.
Figure 32-93 Internal handover (like intra-cell handover) flow (internal TC)

Figure 32-94 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

32-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-95 External handover flow (internal TC)

Figure 32-96 External handover flow (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

32.32 C901260087 Number of data TCH/F assignment 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). 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. For the assignment form port A, this counter and C900060036 accumulate simultaneously after receiving assignment success message. This counter and C900060037 accumulate simultaneously if MS access notice cant be received within specified duration, that is, this assignment failed at this time.

Measurement Point
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.
Figure 32-97 Common assignment flow (internal TC)

32-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-98 Common assignment flow (external TC)

Unit
Times

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

32.33 C901260090 Number of data TCH/F handover 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. 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-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Measurement Point
This counter accumulates when BSC receives ASS_COM/HO_COM message, ASS_FAIL/HO_FAIL message, or messages of exception, released instance, force-released instance, or timer timeout. The measurement points are C4 and D4, as shown in Figure 32-99, Figure 32-100, Figure 32-101, and Figure 32-102.
Figure 32-99 Internal handover (like intra-cell handover) flow (internal TC)

Figure 32-100 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

32-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-101 External handover flow (internal TC)

Figure 32-102 External handover flow (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking

32-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

32.34 C901260092 Number of data TCH/F handover failure with reconnection

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
BSC receives ASS_FAIL or HO_FAIL message. The measurement points are C4 and D4, as shown in Figure 32-103, Figure 32-104.
Figure 32-103 Internal handover (internal TC intra-cell handover) failure flow 1

32-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-104 External handover failure flow (internal TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking

32.35 C901260093 Number of data TCH/F handover failure messages do not received by BSC
Definition
Number of data TCH/F handover failure messages do not received by BSC

Description
This counter counts the number of data TCH/F handover failure without response during handover of data channel. This counter accumulates when handover fails or it cant return to source channel after BSC sends assignment / handover command to MS.

Measurement Point
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-105and Figure 32-106.
32-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-105 Internal handover (internal TC intra-cell handover) failure flow 2

Figure 32-106 Internal handover (internal TC intra-cell handover) failure flow 3

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking

32.36 C901260094 Number of data TCH/F allocation 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-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of data TCH/F allocation failure for assignment due to TIPB connection failure (speech version 1) when assigning voice channel. After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC sends TIU connection requests to TIPB. This counter accumulates when it receives the messages of TIU connection failure, incorrect TIU connection response message, or timer timeout.

Measurement Point
BSC uses TCH/F due to assignment; this counter accumulates when it receives connection failure message, incorrect connection response message, or timer timeout during TIU connection. The measurement point is B2, as shown in Figure 32-107.
Figure 32-107 General Assignment Failure Flow 1 (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.37 C901260095 Number of data TCH/F allocation 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 failure (Speech version 1)

32-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Description
This counter counts the number of data TCH/F allocation failure for assignment due to resource request to iTC failure (speech version 1) when assigning voice channel. After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC requests resource from iTC. If application of iTC resource fails due to receive the messages of unavailable iTC resource, incorrect response message, or timer timeout, this leads to TCH/F assignment failure, and this counter accumulates.

Measurement Point
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.
Figure 32-108 General Assignment Failure Flow 2 (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.38 C901260096 Number of data TCH/F allocation 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-77 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of data TCH/F allocation failure for handover due to TIPB connection failure (speech version 1) during handover. After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC sends TIU connection requests to TIPB. This counter accumulates when it receives the messages of TIU connection failure, incorrect TIU connection response message, or timer timeout.

Measurement Point
BSC uses TCH/F due to assignment; this counter accumulates when it receives 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

Figure 32-110 External handover flow (external TC)

Unit
Times
32-78 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Related Features
l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.39 C901260097 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 1)
Definition
Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 1)

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. After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC requests TC resource after determining channel types are changed. If application of iTC resource fails due to receive the messages of unavailable iTC resource, incorrect response, or timer timeout, this leads to TCH/F assignment failure, and this counter accumulates.

Measurement Point
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.
Figure 32-111 Internal handover (external TC intra-cell handover, and channel types are changed) failure flow 2

32-79 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-112 External handover failure flow 2 (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.40 C901260098 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 2)
Definition
Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 2)

Description
This counter counts the number of data TCH/F allocation failure for assignment due to TIPB connection failure (speech version 2) when assigning voice channel. After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC sends TIU connection requests to TIPB. This counter accumulates when it receives the messages of TIU connection failure, incorrect TIU connection response message, or timer timeout.

Measurement Point
BSC uses TCH/F due to assignment; this counter accumulates when it receives connection failure message, incorrect connection response message, or timer timeout during TIU connection. The measurement point is B2, as shown in Figure 32-113.
32-80 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-113 General Assignment Failure Flow 1 (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.41 C901260099 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 2)
Definition
Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 2)

Description
This counter counts the number of data TCH/F allocation failure for assignment due to resource request to iTC failure (speech version 2) when assigning voice channel. After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC requests resource from iTC. If application of iTC resource fails due to receive the messages of unavailable iTC resource, incorrect response message, or timer timeout, this leads to TCH/F assignment failure, and this counter accumulates.

Measurement Point
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-114.

32-81 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-114 General Assignment Failure Flow 2 (external TC)

Unit
Times

Related Features
l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.42 C901260100 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 2)
Definition
Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 2)

Description
This counter counts the number of data TCH/F allocation failure for handover due to TIPB connection failure (speech version 2) during handover. After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC sends TIU connection requests to TIPB. This counter accumulates when it receives the messages of TIU connection failure, incorrect TIU connection response message, or timer timeout.

Measurement Point
BSC uses TCH/F due to assignment; this counter accumulates when it receives 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-115and Figure 32-116.
32-82 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-115 Internal handover (external TC intra-cell handover, and channel types are changed) failure flow 1

Figure 32-116 External handover flow (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32-83 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

32.43 C901260101 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 2)
Definition
Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 2)

Description
This counter counts the number of data TCH/F allocation failure for handover due to resource request to iTC failure (speech version 2) during handover of voice channel. After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC requests TC resource after determining channel types are changed. If application of iTC resource fails due to receive the messages of unavailable iTC resource, incorrect response, or timer timeout, this leads to TCH/F assignment failure, and this counter accumulates.

Measurement Point
BSC uses TCH/F due to handover; this counter accumulates when it receives the messages of unavailable iTC resource, incorrect response message, or timer timeout during iTC resource application. The measurement points are C1 and D1, as shown in Figure 32-117and Figure 32-118.
Figure 32-117 Internal handover (external TC intra-cell handover, and channel types are changed) failure flow 2

32-84 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-118 External handover failure flow 2 (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.44 C901260102 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 3)
Definition
Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 3)

Description
This counter counts the number of data TCH/F allocation failure for assignment due to TIPB connection failure (speech version 3) when assigning voice channel. After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC sends TIU connection requests to TIPB. This counter accumulates when it receives the messages of TIU connection failure, incorrect TIU connection response message, or timer timeout.

Measurement Point
BSC uses TCH/F due to assignment; this counter accumulates when it receives connection failure message, incorrect connection response message, or timer timeout during TIU connection. The measurement point is B2, as shown in Figure 32-119.
32-85 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-119 General Assignment Failure Flow 1 (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.45 C901260103 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 3)
Definition
Number of data TCH/F allocation failure for assignment due to resource request to iTC failure (Speech version 3)

Description
This counter counts the number of data TCH/F allocation failure for assignment due to resource request to iTC failure (speech version 3) when assigning voice channel. After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC requests resource from iTC. If application of iTC resource fails due to receive the messages of unavailable iTC resource, incorrect response message, or timer timeout, this leads to TCH/F assignment failure, and this counter accumulates.

Measurement Point
BSC uses TCH/F due to assignment; this counter accumulates when it receives the messages of unavailable iTC resource, incorrect response message, or timer timeout during iTC resource application. The measurement point is B1, as shown in Figure 32-120.
32-86 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-120 General Assignment Failure Flow 2 (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.46 C901260104 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 3)
Definition
Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 3)

Description
This counter counts the number of data TCH/F allocation failure for handover due to TIPB connection failure (speech version 3) during handover. After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC sends TIU connection requests to TIPB. This counter accumulates when it receives the messages of TIU connection failure, incorrect TIU connection response message, or timer timeout.

Measurement Point
BSC uses TCH/F due to assignment; this counter accumulates when it receives 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-121and Figure 32-122.
32-87 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-121 Internal handover (external TC intra-cell handover, and channel types are changed) failure flow 1

Figure 32-122 External handover flow (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32-88 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

32.47 C901260105 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 3)
Definition
Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 3)

Description
This counter counts the number of data TCH/F allocation failure for handover due to resource request to iTC failure (speech version 3) during handover of voice channel. After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC requests TC resource after determining channel types are changed. If application of iTC resource fails due to receive the messages of unavailable iTC resource, incorrect response, or timer timeout, this leads to TCH/F assignment failure, and this counter accumulates.

Measurement Point
BSC uses TCH/F due to handover; this counter accumulates when it receives the messages of unavailable iTC resource, incorrect response message, or timer timeout during iTC resource application. The measurement points are C1 and D1, as shown in Figure 32-123and Figure 32-124.
Figure 32-123 Internal handover (external TC intra-cell handover, and channel types are changed) failure flow 2

32-89 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-124 External handover failure flow 2 (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

32.48 C901260106 Number of TCH/F allocation 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.

32-90 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

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.49 C901260107 Number of TCH/F allocation failure 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
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure.
32-91 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-04-003 A over IP

32.50 C901260108 Number of TCH/F allocation failure 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
This counter counts the number of TCH/F channel allocation failure due to AIPB connection 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 AIPB connection failure.

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure.

32-92 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for assignment. The measurement point is A as shown in Figure 32-127.
Figure 32-127 Channel allocation failure

Unit
Times

Related Features
ZGO-05-04-003 A over IP

32.51 C901260109 Number of TCH/F allocation failure 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
This counter counts the number of TCH/F allocation failure due to request AIPB resource failure for assignment. 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
This counter is used to find out the frequency of TCH/F allocation failure due to request AIPB resource failure for assignment.

32-93 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter increments while BSC correctly receives database return failure or no AIPB board resource, and the reason to apply for channel is handover and purpose is voice channel. The measurement point is A as shown in Figure 32-128.
Figure 32-128 Request Resource Failure

Unit
Times

Related Features
l l ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP

32.52 C901260110 Number of TCH/F allocation failure 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
This counter counts the number of TCH/F channel allocation failure due to UDP port failure during handover. When BSC receives EV_RANUMC_RADIO_APPLY message (speech version 1), the reason to request channel is handover, to request access request for access module. This counter increments while access module returns failure and the reason is failed to request UDP port.

32-94 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for handover. The measurement point is A as shown in Figure 32-129.
Figure 32-129 Channel allocation failure

Unit
Times

Related Features
l l ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP

32.53 C901260111 Number of TCH/F allocation failure 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. When BSC receives EV_RANUMC_RADIO_APPLY message (speech version 1), the reason to request channel is handover, to request access request for access module. This counter increments while access module returns failure and the reason is failed to access AIPB.
32-95 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for handover. The measurement point is A as shown in Figure 32-130.
Figure 32-130 Channel allocation failure

Unit
Times

Related Features
l l ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP

32.54 C901260112 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 2)
Definition
Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 2)

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 2) to apply for AIPB board resource from database, failed request (including database return failure or no AIPB board resource) indicates TCH/F allocation failure.

32-96 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

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-131.
Figure 32-131 Request Resource Failure

Unit
Times

Related Features
ZGO-05-04-003 A over IP

32.55 C901260113 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 2)
Definition
Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 2)

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 2), access request is sent to access module, if access module returns access failure due to UDP port request failure.
32-97 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for assignment. The measurement point is A as shown in Figure 32-132.
Figure 32-132 Channel allocation failure

Unit
Times

Related Features
ZGO-05-04-003 A over IP

32.56 C901260114 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 2)
Definition
Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 2)

Description
This counter counts the number of TCH/F channel allocation failure due to AIPB connection failure during assigning voice channel. This counter increments while BSC receives assignment requests (speech version 2), access request is sent to access module, if access module returns access failure due to AIPB connection failure.

32-98 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for assignment. The measurement point is A as shown in Figure 32-133.
Figure 32-133 Channel allocation failure

Unit
Times

Related Features
ZGO-05-04-003 A over IP

32.57 C901260115 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 2)
Definition
Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 2)

Description
This counter counts the number of TCH/F allocation failure due to request AIPB resource failure for assignment. When BSC receives EV_RANUMC_RADIO_APPLY message (speech version 2), 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.

32-99 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 handover and purpose is voice channel. The measurement point is A as shown in Figure 32-134.
Figure 32-134 Request Resource Failure

Unit
Times

Related Features
l l ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP

32.58 C901260116 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 2)
Definition
Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 2)

Description
This counter counts the number of TCH/F channel allocation failure due to UDP port failure 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.
32-100 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for handover. The measurement point is A as shown in Figure 32-135.
Figure 32-135 Channel allocation failure

Unit
Times

Related Features
l l ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP

32.59 C901260117 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 2)
Definition
Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 2)

Description
This counter counts the number of TCH/F channel allocation failure due to AIPB access failure during handover. When BSC receives EV_RANUMC_RADIO_APPLY message (speech version 2), the reason to request channel is handover, to request access request for access module. This counter increments while access module returns failure and the reason is failed to access AIPB.
32-101 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for handover. The measurement point is A as shown in Figure 32-136.
Figure 32-136 Channel allocation failure

Unit
Times

Related Features
l l ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP

32.60 C901260118 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 3)
Definition
Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 3)

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 3) to apply for AIPB board resource from database, failed request (including database return failure or no AIPB board resource) indicates TCH/F allocation failure.

32-102 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

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-137.
Figure 32-137 Request Resource Failure

Unit
Times

Related Features
l l ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-05-04-003 A over IP

32.61 C901260119 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 3)
Definition
Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 3)

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 3), access request is sent to access module, if access module returns access failure due to UDP port request failure.
32-103 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for assignment. The measurement point is A as shown in Figure 32-138.
Figure 32-138 Channel allocation failure

Unit
Times

Related Features
l l ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-05-04-003 A over IP

32.62 C901260120 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 3)
Definition
Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 3)

Description
This counter counts the number of TCH/F channel allocation failure due to AIPB connection failure during assigning voice channel. This counter increments while BSC receives assignment requests (speech version 3), access request is sent to access module, if access module returns access failure due to AIPB connection failure.

32-104 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for assignment. The measurement point is A as shown in Figure 32-139.
Figure 32-139 Channel allocation failure

Unit
Times

Related Features
l l ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-05-04-003 A over IP

32.63 C901260121 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 3)
Definition
Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 3)

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 EV_RANUMC_RADIO_APPLY message (speech version 3), the reason to request channel is handover and request AIPB resource from database, if request AIPB fails (including database return failure or no AIPB resource), indicating TCH/F allocation failure.
32-105 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 handover and purpose is voice channel. The measurement point is A as shown in Figure 32-140.
Figure 32-140 Request Resource Failure

Unit
Times

Related Features
l l l ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP

32.64 C901260122 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 3)
Definition
Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 3)

Description
This counter counts the number of TCH/F channel allocation failure due to UDP port failure during handover. When BSC receives EV_RANUMC_RADIO_APPLY message (speech version 3), the reason to request channel is handover, to request access request for access module.
32-106 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

This counter increments while access module returns failure and the reason is failed to request UDP port.

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for handover. The measurement point is A as shown in Figure 32-141.
Figure 32-141 Channel allocation failure

Unit
Times

Related Features
l l l ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP

32.65 C901260123 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 3)
Definition
Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 3)

Description
This counter counts the number of TCH/F channel allocation failure due to AIPB access failure during handover.
32-107 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

When BSC receives EV_RANUMC_RADIO_APPLY message (speech version 3), the reason to request channel is handover, to request access request for access module. This counter increments while access module returns failure and the reason is failed to access AIPB.

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for handover. The measurement point is A as shown in Figure 32-142.
Figure 32-142 Channel allocation failure

Unit
Times

Related Features
l l l ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP

32.66 C901260124 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (data)
Definition
Number of TCH/F allocation failure due to request AIPB resource failure for assignment (data)

32-108 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

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 (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
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-143.
Figure 32-143 Request Resource Failure

Unit
Times

Related Features
ZGO-05-04-003 A over IP

32.67 C901260125 Number of TCH/F allocation failure due to request UDP port failure for assignment (data)
Definition
Number of TCH/F allocation failure due to request UDP port failure for assignment (data)

32-109 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 (data), access request is sent to access module, if access module returns access failure due to UDP port request failure.

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for assignment. The measurement point is A as shown in Figure 32-144.
Figure 32-144 Channel allocation failure

Unit
Times

Related Features
ZGO-05-04-003 A over IP

32.68 C901260126 Number of TCH/F allocation failure due to AIPB connection failure for assignment (data)
Definition
Number of TCH/F allocation failure due to AIPB connection failure for assignment (data)

32-110 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Description
This counter counts the number of TCH/F channel allocation failure due to AIPB connection failure during assigning voice channel. This counter increments while BSC receives assignment requests (data), access request is sent to access module, if access module returns access failure due to AIPB connection failure.

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for assignment. The measurement point is A as shown in Figure 32-145.
Figure 32-145 Channel allocation failure

Unit
Times

Related Features
ZGO-05-04-003 A over IP

32.69 C901260127 Number of TCH/F allocation failure due to request AIPB resource failure for handover (data)
Definition
Number of TCH/F allocation failure due to request AIPB resource failure for handover (data)

32-111 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of TCH/F allocation failure due to request AIPB resource failure for assignment. 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
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 handover and purpose is voice channel. The measurement point is A as shown in Figure 32-146.
Figure 32-146 Request Resource Failure

Unit
Times

Related Features
l l ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP

32.70 C901260128 Number of TCH/F allocation failure 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)
32-112 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Description
This counter counts the number of TCH/F channel allocation failure due to UDP port failure during handover. When BSC receives EV_RANUMC_RADIO_APPLY message (data), the reason to request channel is handover, to request access request for access module. This counter increments while access module returns failure and the reason is failed to request UDP port.

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for handover. The measurement point is A as shown in Figure 32-147.
Figure 32-147 Channel allocation failure

Unit
Times

Related Features
l l ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP

32.71 C901260129 Number of TCH/F allocation failure due to AIPB connection failure for handover (data)
Definition
Number of TCH/F allocation failure due to AIPB connection failure for handover (data)

32-113 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of TCH/F channel allocation failure due to AIPB access failure during handover. When BSC receives EV_RANUMC_RADIO_APPLY message (data), the reason to request channel is handover, to request access request for access module. This counter increments while access module returns failure and the reason is failed to access AIPB.

Usage
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for handover. The measurement point is A as shown in Figure 32-148.
Figure 32-148 Channel allocation failure

Unit
Times

Related Features
l l ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP

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.
32-114 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

The BSC CS service instance is forcibly handover to release resource, if the released TCH/F resource is assigned to the forced handover source, the counter accumulates.

Usage
This counter is used to find out the frequency of the TCH/F released by forced handover being assigned to the forced handover source.

Measurement Point
The BSC CS service instance is forcibly handover to release resource, if the released TCH/F resource is assigned to the forced handover source, the counter accumulates.

Unit
Times

32.73 C901260131 Number of assign TCH/F release by forced handover to queuing user
Definition
Number of assign TCH/F release by forced handover to queuing user

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 queuing user. The BSC CS service instance is forcibly handover to release resource, if the released TCH/F resource is assigned to the queuing user, the counter accumulates.

Usage
This counter is used to find out the frequency of the TCH/F released by forced handover being assigned to the queuing user.

Measurement Point
The BSC CS service instance is forcibly handover to release resource, if the released TCH/F resource is assigned to the queuing user, the counter accumulates.

Unit
Times

32-115 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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 queuing user. The BSC CS service instance is forcibly handover to release resource, if the released TCH/F resource is assigned to the queuing user, the counter accumulates.

Usage
This counter is used to find out the frequency of the TCH/F released by forced handover being restored to DBS.

Measurement Point
The BSC CS service instance is forcibly handover to release resource, if the released TCH/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.
32-116 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

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

Unit
Times

32.76 C901260134 Number of assign TCH/F release by forced release to queuing user
Definition
Number of assign TCH/F release by forced release to queuing user

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 queuing user. The BSC CS service instance is forcibly released to release resource, if the released TCH/F resource is assigned to the queuing user, 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 queuing user.

Measurement Point
The BSC CS service instance is forcibly released to release resource, if the released TCH/F resource is assigned to the queuing user, the counter accumulates.

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

32-117 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. The BSC CS service instance is forcibly released to release resource, if the released TCH/F resource is just released instead of being assigned to other users, the counter accumulates.

Usage
This counter is used to find out the frequency of the TCH/F released by forced release being restored to DBS.

Measurement Point
The BSC CS service instance is forcibly released to release resource, if the released TCH/F resource is just released instead of being assigned to other users, the counter accumulates.
Figure 32-149 Channel allocation failure

Unit
Times

32.78 C901260136 Number of signaling TCH/F seizure 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.

32-118 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

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

32.79 C901260137 Number of signaling TCH/F seizure failure for handover (cause:Abis)
Description
This counter counts the number of failed signaling TCH/F seizure attempts during the process of signaling channel handover. When BSC receives the channel request, it attempts to allocate channel for the request. If the channel occupation fails due to no available Abis resource, the counter accumulates. If the request is responded with the message that no channel is available but queuing or forced release is possible, then the instance enters the queuing state. If the queuing fails, the counter accumulates. If the request 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

32.80 C901260138 Number of voice TCH/F seizure failure for assignment (cause:Abis)
Description
This counter counts the number of failed voice TCH/F seizure attempts during the process of voice channel assignment. When 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.
32-119 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when the request for channel is sent to BSC (due to assignment, used for voice channel) but the channel occupation fails or waiting for resource inside BSC fails.

Unit
Times

32.81 C901260139 Number of voice TCH/F seizure failure for handover (cause:Abis )
Description
This counter counts the number of failed voice TCH/F seizure attempts during the process of voice channel handover. When BSC receives the channel request, it attempts to allocate channel for the request. If the channel occupation fails due to no available Abis resource, the counter accumulates. If the request is responded with the message that no channel is available but queuing or forced release is possible, then the instance enters the queuing state. If the queuing fails, the counter accumulates. If the request is responded with the message that the transceiver is faulty, the 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 voice channel) but the channel occupation fails or waiting for resource inside BSC fails.

Unit
Times

32.82 C901260140 Number of data TCH/F seizure failure for assignment (cause:Abis)
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 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.
32-120 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Measurement Point
The counter counts when the request for channel is sent to BSC (due to assignment, used for data channel) but the channel occupation fails or waiting for resource inside BSC fails.

Unit
Times

32.83 C901260141 Number of data TCH/F seizure failure for handover (cause:Abis)
Description
This counter counts the number of failed data TCH/F seizure attempts during the process of data channel handover. When BSC 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
The counter counts when the request for channel is sent to BSC (due to handover, used for data channel) but the channel occupation fails or waiting for resource inside BSC fails.

Unit
Times

32.84 C901260142 Number of signaling TCH/F seizure failure for assignment (cause:radio resource)
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 radio resource, the counter accumulates. If the request is responded with the message that the transceiver is faulty, the counter does not count.

32-121 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

32.85 C901260143 Number of signaling TCH/F seizure failure for handover (cause:radio resource)
Description
This counter counts the number of failed signaling TCH/F seizure attempts during the process of signaling channel handover. When BSC receives the channel request, it attempts to allocate channel for the request. If the channel occupation fails due to no available radio 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
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

32.86 C901260144 Number of voice TCH/F seizure failure for assignment (cause:radio resource)
Description
This counter counts the number of failed voice TCH/F seizure attempts during the process of voice channel assignment. When BSC receives the channel request, it attempts to allocate channel for the request. If the channel occupation fails due to no available radio resource, the counter accumulates. If the request is responded with the message that no channel is available but queuing 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.
32-122 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Measurement Point
The counter counts when the request for channel is sent to BSC (due to assignment, used for voice channel) but the channel occupation fails or waiting for resource inside BSC fails.

Unit
Times

32.87 C901260145 Number of voice TCH/F seizure failure for handover (cause:radio resource)
Description
This counter counts the number of failed voice TCH/F seizure attempts during the process of voice channel handover. When BSC receives the channel request, it attempts to allocate channel for the request. If the channel occupation fails due to no available radio resource, the counter accumulates. If the request is responded with the message that no channel is available but queuing 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
The counter counts when the request for channel is sent to BSC (due to handover, used for voice channel) but the channel occupation fails or waiting for resource inside BSC fails.

Unit
Times

32.88 C901260146 Number of data TCH/F seizure failure for assignment (cause:radio resource)
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 channel for the request. If the channel occupation fails due to no available radio resource, the counter accumulates. If the request is responded with the message that no channel is available but queuing 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.
32-123 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when the request for channel is sent to BSC (due to assignment, used for data channel) but the channel occupation fails or waiting for resource inside BSC fails.

Unit
Times

32.89 C901260147 Number of data TCH/F seizure failure for handover (cause:radio resource)
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 channel for the request. If the channel occupation fails due to no available radio resource, the counter accumulates. If the request is responded with the message that no channel is available but queuing 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
The counter counts when the request for channel is sent to BSC (due to handover, used for data channel) but the channel occupation fails or waiting for resource inside BSC fails.

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.

32-124 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

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

32.91 C901260149 Number of FR_V1 assignment 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, 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 accumulates after the assignment success message is received.

Measurement Point
For the assignment from A-interface, this counter accumulates after BSC receives the assignment success message.

Unit
Times

32.92 C901260150 Number of FR_V2 assignment attempts

Description
This counter counts the number of attempts of assigning TCH/F of voice version 2 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 C901260151 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.

32-125 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

32.93 C901260151 Number of FR_V2 assignment success

Description
This counter counts the number of successes of assigning TCH/F of voice version 2 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 accumulates after the assignment success message is received.

Measurement Point
For the assignment from A-interface, this counter accumulates after BSC receives the assignment success message.

Unit
Times

32.94 C901260152 Number of FR_V3 assignment attempts

Description
This counter counts the number of attempts of assigning TCH/F of voice version 3 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 C901260153 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.

32-126 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

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

32.95 C901260153 Number of FR_V3 assignment success

Description
This counter counts the number of successes of assigning TCH/F of voice version 3 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 accumulates after the assignment success message is received.

Measurement Point
For the assignment from A-interface, this counter accumulates after BSC receives the assignment success message.

Unit
Times

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.
32-127 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

32.98 C901260156 Number of FR_V2 handover

Description
This counter counts the number of handover attempts that the destination voice channel is of full-rate voice version 2. 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 C901260157 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
32-128 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

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.99 C901260157 Number of FR_V2 handover success

Description
This counter counts the number of successful handovers that the destination voice channel is of full-rate voice version 2. This counter accumulates when BSC detects the handover success message sent from MS on the newly allocated TCH/F channel. For intra-cell handover, the handover success message is ASS_COM; for inter-cell handover and external handover, the handover success message is HO_COM. For intra-cell handover and inter-cell handover, the counter accumulates on the basis of source instances. For external handover, because the source instance is not at the BSC, the counter accumulates on the basis of destination instances.

Measurement Point
The counter counts when BSC receives the ASS_COM message or the HO_COM message.

Unit
Times

32.100 C901260158 Number of FR_V3 handover

Description
This counter counts the number of handover attempts that the destination voice channel is of full-rate voice version 3. 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 C901260159 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
32-129 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.101 C901260159 Number of FR_V3 handover success

Description
This counter counts the number of successful handovers that the destination voice channel is of full-rate voice version 3. This counter accumulates when BSC detects the handover success message sent from MS on the newly allocated TCH/F channel. For intra-cell handover, the handover success message is ASS_COM; for inter-cell handover and external handover, the handover success message is HO_COM. For intra-cell handover and inter-cell handover, the counter accumulates on the basis of source instances. For external handover, because the source instance is not at the BSC, the counter accumulates on the basis of destination instances.

Measurement Point
The counter counts when BSC receives the ASS_COM message or the HO_COM message.

Unit
Times

32.102 C901260185 Resourse releasing of ordinary users due to being grabbed (TCH/F)
Description
This counter counts the number of ordinary user's call on TCH/F being released due to resource being preempted. After the ordinary user obtains TCH/F, call drop occurs. If the problem is caused by high-priority user's preempting resource, the counter increments.
32-130 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Usage
This counter is used to find out the number of ordinary user's call on TCH/F being released due to high-priority user's preempting resource. This counter is supported in version V6.20.61 or later.

Measurement Point
After the ordinary user obtains TCH/F, if the forced release message from other call is received, the counter counts. The measurement point is A, as shown in Figure 32-150.
Figure 32-150 Flow of Ordinary User's Call Being Released due to Resource Being Preempted

Unit
Times

32-131 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

32.103 C901260186 Handover of ordinary users due to be grabbed (TCH/F)

Description
This counter counts the number of handovers performed for ordinary user's call on TCH/F due to resource being preempted. After the ordinary user obtains TCH/F, handover is performed due to no available resource under the BSC. If the problem is caused by high-priority user's preempting resource, the counter increments.

Usage
This counter is used to find out the number of handovers performed for ordinary user's call on TCH/F due to high-priority user's preempting resource. This counter is supported in version V6.20.61 or later.

Measurement Point
After the ordinary user obtains TCH/F, if the forced handover message is received, the counter counts. The measurement point is A, as shown in Figure 32-151.

32-132 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-151 Flow of Handover for Ordinary User's Call due to Resource Being Preempted

Unit
Times

32.104 C901260187 Number of Channel Request of priority users (TCH/F)

Description
This counter counts the number of requesting for TCH/F by high-priority users. After BSC receives the channel request, it attempts to allocate channel for the request. If the channel request is initiated by high-priority user, the counter increments.

Usage
This counter is used to find out the number of requesting for TCH/F by high-priority users.
32-133 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter is supported in version V6.20.61 or later.

Measurement Point
When the high-priority user requests for TCH/F, the counter counts. The measurement point is A, as shown in Figure 32-152, Figure 32-153, and Figure 32-154.
Figure 32-152 Flow of Occupying TCH/F during Assignment

Figure 32-153 Flow of Occupying TCH/F during Inter-BSC Handover

Figure 32-154 Flow of Occupying TCH/F during Intra-BSC Handover

Unit
Times

32-134 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

32.105 C901260188 Number of Successful Channel seize of priority users (TCH/F)

Description
This counter counts the number of high-priority users' requesting for TCH/F successfully. After BSC receives the channel request, it attempts to allocate channel for the request. If the channel request is initiated by high-priority user and the channel is obtained successfully, the counter increments.

Usage
This counter is used to find out the number of high-priority users' requesting for TCH/F successfully. This counter is supported in version V6.20.61 or later.

Measurement Point
When the high-priority user requests for TCH/F, if the channel is obtained successfully, the counter counts. The measurement point is A, as shown in Figure 32-155, Figure 32-156, and Figure 32-157.
Figure 32-155 Flow of Occupying TCH/F during Assignment

Figure 32-156 Flow of Occupying TCH/F during Inter-BSC Handover

Figure 32-157 Flow of Occupying TCH/F during Intra-BSC Handover

32-135 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

32.106 C901260189 Number of Successful grabbing channel of priority users (TCH/F)

Description
When the high-priority user requests for TCH/F, this counter counts the number of high-priority user's successfully preempting resource from the ordinary user due to no available resource in the system. After BSC receives the channel request, it attempts to allocate channel for the request. If the request is initiated by high-priority user but there is no available resource, the system initiates the flow of preempting resource from ordinary user. If the resource is preempted successfully, the counter increments.

Usage
This counter is used to find out the number of high-priority user's preempting resource from ordinary user successfully. This counter is supported in version V6.20.61 or later.

Measurement Point
When high-priority user requests for TCH/F but there is no available resource, if high-priority user preempts resource from ordinary user successfully, the counter counts. The measurement point is A, as shown in Figure 32-158, Figure 32-159, and Figure 32-160.
Figure 32-158 Flow of Occupying TCH/F during Assignment

Figure 32-159 Flow of Occupying TCH/F during Inter-BSC Handover

32-136 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-160 Flow of Occupying TCH/F during Intra-BSC Handover

Unit
Times

32.107 C901260190 Number of TCH/F Allocation Attempts for Assignment (Speech Version 4)
Definition
Number of TCH/F allocation attempts for assignment (speech version 4)

Description
This counter counts the allocation attempts that occur to allocate a voice TCH/F (speech version 4) for assignment. Allocation attempts includes both successful allocation attempts (C901260191) and failed allocation attempts (C901260192+C901260193+C901260206+C901260207+C901260208). Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC completes the connection, and then sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/F. The BTS sends a CHL_ACT_ACK message to the BSC after the channel is successfully activated. When the TCH/F allocation succeeds with a CHL_ACT_ACK message received, this counter and counter C901260191 are incremented. When the TCH/F allocation fails, this counter and the counter corresponding to the failure reason are incremented.

Measurement Point
This counter is incremented each time a voice TCH/F allocation attempt for assignment succeeds or fails. The measurement point is B2 in the case of internal transcoder (TCU), or B3 in the case of external transcoder (iTC), as shown in Figure 32-161 and Figure 32-162.

32-137 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-161 General Assignment Procedure (Internal TC)

Figure 32-162 General Assignment Procedure (External TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.108 C901260191 Number of TCH/F Allocation Success for Assignment (Speech Version 4)
Definition
Number of successful TCH/F allocations (speech version 4) for assignment
32-138 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Description
This counter counts successful TCH/F allocation attempts that occur to allocate a voice TCH/F (speech version 4) for assignment. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/F. The BTS sends a CHL_ACT_ACK message to the BSC after the channel is successfully activated. This counter is incremented when the TCH/F allocation succeeds with a CHL_ACT_ACK message received.

Measurement Point
This counter is incremented each time the BSC receives a CHL_ACT_ACK message from the BTS in the case of TCH/F allocation (speech version 4) for assignment. The measurement point is B2 in the case of internal transcoder (TCU), or B3 in the case of external transcoder (iTC), as shown in Figure 32-163 and Figure 32-164.
Figure 32-163 General Assignment Procedure (Internal TC)

Figure 32-164 General Assignment Procedure (External TC)

32-139 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.109 C901260192 Number of TCH/F Allocation Failure Due to Channel Activation Failure for Assignment (Speech Version 4)
Definition
Number of failed TCH/F allocations (speech version 4) for assignment due to channel activation failure

Description
This counter counts TCH/F allocation failures due to channel activation failure during voice channel allocation (speech version 4) for assignment. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC completes the connection, and then sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/F. When the channel activation fails, this counter is incremented. The BSC considers the channel activation failed when the ChannelActivationNack message is received, the ChannelActivationAck message is not received, the timer T9103 expires, the channel instance is released, or the channel is forcibly disconnected.

Measurement Point
This counter is incremented each time the TCH/F allocation fails due to channel activation failure during the channel allocation (speech version 4) for assignment. The measurement point is B3, as shown in Figure 32-165.

32-140 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-165 Assignment Failure 1 (Internal TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.110 C901260193 Number of TCH/F Allocation Failure Due to BIU Connection Failure for Assignment (Speech Version 4)
Definition
Number of failed TCH/F allocations (speech version 4) for assignment due to BIU connection failure

Description
This counter counts TCH/F allocation failures due to BIU connection failure during voice channel allocation (speech version 4) for assignment. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC sends a BIU connection request to the BIPB. If the BIU connection fails, this counter is incremented. The BSC considers the BIU connection failed when the BIU connection non-acknowledgement message is received, the BIU connection acknowledgement message is not received, or the corresponding timer expires.

Measurement Point
This counter is incremented each time the TCH/F allocation fails due to BIU connection failure during the voice channel allocation (speech version 4) for assignment. The measurement point is B2, as shown in Figure 32-166.
32-141 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-166 Assignment Failure 3 (Internal TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.111 C901260194 Number of TCH/F Allocation Attempts by BSC for Handover (Speech Version 4)
Definition
Number of TCH/F allocation attempts for handover (speech version 4)

Description
This counter counts the TCH/F allocation attempts that occur to allocate a full rate voice channel (speech version 4) for handover. The allocation attempts include both successful allocation attempts (C901260195) and failed allocation attempts (C901260196+C901260197+C901260209+C901260210+C901260211). Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC completes the connection, and then sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/F. The BTS sends a CHL_ACT_ACK message to the BSC after the channel is successfully activated. When the TCH/F allocation succeeds with a CHL_ACT_ACK message received, this counter and counter C901260195 are incremented. When the TCH/F allocation fails, this counter and the counter corresponding to the failure reason are incremented.

Measurement Point
This counter is incremented each time a TCH/F allocation attempt succeeds or fails during the voice channel allocation (speech version 4) for handover. The measurement point varies with different handover procedures and transcoders. In an internal handover (intra-BSC handover), the measurement point is C3, as shown in Figure 32-167 and
32-142 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-168. In an external handover (inter-BSC handover), the measurement point is D3, as shown in Figure 32-169 and Figure 32-170.
Figure 32-167 Internal Handover Procedure - Intra-Cell Handover (Internal TC)

Figure 32-168 Internal Handover Procedure - Intra-Cell Handover with Channel Type Changed (External TC)

32-143 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-169 External Handover Procedure (Internal TC)

Figure 32-170 External Handover Procedure (External TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32-144 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

32.112 C901260195 Number of TCH/F Allocation Success by BSC for Handover (Speech Version 4)
Definition
Number of TCH/F allocation successes for handover (speech version 4)

Description
This counter counts successful TCH/F allocation attempts that occur to allocate a voice TCH/F (speech version 4) for handover. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/F. The BTS sends a CHL_ACT_ACK message to the BSC after the channel is successfully activated. When the TCH/F allocation succeeds with a CHL_ACT_ACK message received, this counter is incremented.

Measurement Point
This counter is incremented each time the BSC receives a CHL_ACT_ACK message from the BTS in the case of TCH/F allocation (speech version 4) for handover. The measurement point varies with different handover procedures and transcoders. In an internal handover (intra-BSC handover), the measurement point is C3, as shown in Figure 32-171 and Figure 32-172. In an external handover (inter-BSC handover), the measurement point is D3, as shown in Figure 32-173 and Figure 32-174.
Figure 32-171 Internal Handover Procedure - Intra-Cell Handover (Internal TC)

32-145 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-172 Internal Handover Procedure - Intra-Cell Handover with Channel Type Changed (External TC)

Figure 32-173 External Handover Procedure (Internal TC)

32-146 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-174 External Handover Procedure (External TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.113 C901260196 Number of TCH/F Allocation Failure Due to Channel Activation Failure for Handover (Speech Version 4)
Definition
Number of failed TCH/F allocations (speech version 4) for handover

Description
This counter counts TCH/F allocation failures due to channel activation failure during voice TCH/F allocation (speech version 4) for handover. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F is allocated and occupied. After that, the BSC completes the connection, and then sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/F. If the channel activation fails, this counter is incremented. The BSC considers the channel activation failed when the ChannelActivationNack message is received, the ChannelActivationAck message is not received, the timer T9103 expires, the channel instance is released, or the channel is forcibly disconnected.

32-147 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the TCH/F allocation fails due to channel activation failure during the channel allocation (speech version 4) for handover. The measurement point varies with different handover procedures and transcoders. In an internal handover (intra-BSC handover), the measurement point is C3, as shown in Figure 32-175. In an external handover (inter-BSC handover), the measurement point is D3, as shown in Figure 32-176.
Figure 32-175 Internal Handover Failure 1 - Intra-Cell Handover (Internal TC)

Figure 32-176 External Handover Failure 2 (Internal TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32-148 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

32.114 C901260197 Number of TCH/F Allocation Failure Due to BIU Connection Failure for Handover (Speech Version 4)
Definition
Number of failed TCH/F allocations (speech version 4) for handover due to BIU connection failure

Description
This counter counts TCH/F allocation failures due to BIU connection failure during voice channel allocation (speech version 4) for handover. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC sends a BIU connection request to the BIPB. If the BIU connection fails, this counter is incremented. The BSC considers the BIU connection failed when the BIU connection non-acknowledgement message is received, the BIU connection acknowledgement message is not received, or the corresponding timer expires.

Measurement Point
This counter is incremented each time the TCH/F allocation fails due to BIU connection failure during the voice channel allocation (speech version 4) for handover. The measurement point varies with different handover procedures and transcoders. In an internal handover (intra-BSC handover), the measurement point is C2, as shown in Figure 32-177. In an external handover (inter-BSC handover), the measurement point is D2, as shown in Figure 32-178.
Figure 32-177 Internal Handover Failure 2 - Intra-Cell Handover (Internal TC)

32-149 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-178 External Handover Failure 3 (Internal TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.115 C901260198 Number of TCH/F Allocation Attempts for Assignment (Speech Version 5)
Definition
Number of TCH/F allocation attempts for assignment (speech version 5)

Description
This counter counts the allocation attempts that occur to allocate a voice TCH/F (speech version 5) for assignment. The allocation attempts include both successful allocation attempts (C901260199) and failed allocation attempts (C901260200+C901260201+C901260214+C901260215+C901260216). Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC completes the connection, and then sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/F. The BTS sends a CHL_ACT_ACK message to the BSC after the channel is successfully activated. When the TCH/F allocation succeeds with a CHL_ACT_ACK message received, this counter and counter C901260199 are incremented. When the TCH/F allocation fails, this counter and the counter corresponding to the failure reason are incremented.

Measurement Point
This counter is incremented each time a voice TCH/F allocation attempt (speech version 5) for assignment succeeds or fails. The measurement point is B2 in the case of internal transcoder (TCU), or B3 in the case of external transcoder (iTC), as shown in Figure 32-179 and Figure 32-180.
32-150 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-179 General Assignment Procedure (Internal TC)

Figure 32-180 General Assignment Procedure (External TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.116 C901260199 Number of TCH/F Allocation Success for Assignment (Speech Version 5)
Definition
Number of successful TCH/F allocations (speech version 5) for assignment
32-151 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts successful TCH/F allocation attempts that occur to allocate a voice TCH/F (speech version 5) for assignment. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/F. The BTS sends a CHL_ACT_ACK message to the BSC after the channel is successfully activated. When the TCH/F allocation succeeds with a CHL_ACT_ACK message received, this counter is incremented.

Measurement Point
This counter is incremented each time the BSC receives a CHL_ACT_ACK message from the BTS in the case of TCH/F allocation (speech version 5) for assignment. The measurement point is B3, as shown in Figure 32-181 and Figure 32-182.
Figure 32-181 General Assignment Procedure (Internal TC)

Figure 32-182 General Assignment Procedure (External TC)

32-152 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.117 C901260200 Number of TCH/F Allocation Failure Due to Channel Activation Failure for Assignment (Speech Version 5)
Definition
Number of failed TCH/F allocations (speech version 5) for assignment due to channel activation failure

Description
This counter counts TCH/F allocation failures due to channel activation failure during voice channel allocation (speech version 5) for assignment. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC completes the connection, and then sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/F. If the channel activation fails, this counter is incremented. The BSC considers the channel activation failed when the ChannelActivationNack message is received, the ChannelActivationAck message is not received, the timer T9103 expires, the channel instance is released, or the channel is forcibly disconnected.

Measurement Point
This counter is incremented each time the TCH/F allocation fails due to channel activation failure during the channel allocation (speech version 5) for assignment. The measurement point is B3, as shown in Figure 32-183.

32-153 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-183 Assignment Failure 1 (Internal TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.118 C901260201 Number of TCH/F Allocation Failure Due to BIU Connection Failure for Assignment (Speech Version 5)
Definition
Number of failed TCH/F allocations (speech version 5) for assignment due to BIU connection failure

Description
This counter counts TCH/F allocation failures due to BIU connection failure during voice channel allocation (speech version 5) for assignment. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC sends a BIU connection request to the BIPB. If the BIU connection fails, this counter is incremented. The BSC considers the BIU connection failed when the BIU connection non-acknowledgement message is received, the BIU connection acknowledgement message is not received, or the corresponding timer expires.

Measurement Point
This counter is incremented each time the TCH/F allocation fails due to BIU connection failure during the voice channel allocation (speech version 4) for assignment. The measurement point is B2, as shown in Figure 32-184.
32-154 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-184 Assignment Failure 3 (Internal TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.119 C901260202 Number of TCH/F Allocation Attempts by BSC for Handover (Speech Version 5)
Definition
Number of TCH/F allocation attempts for handover (speech version 5)

Description
This counter counts the TCH/F allocation attempts that occur to allocate a full rate voice channel (speech version 5) for handover. The allocation attempts include both successful allocation attempts (C901260203) and failed allocation attempts (C901260204+C901260205+C901260217+C901260218+C901260219). Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC completes the connection, and then sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/F. The BTS sends a CHL_ACT_ACK message to the BSC after the channel is successfully activated. When the TCH/F allocation succeeds with a CHL_ACT_ACK message received, this counter and counter C901260203 are incremented. When the TCH/F allocation fails, this counter and the counter corresponding to the failure reason are incremented.

Measurement Point
This counter is incremented each time a TCH/F allocation attempt succeeds or fails during the voice channel allocation (speech version 5) for handover. The measurement point varies with different handover procedures and transcoders. In an internal handover (intra-BSC handover), the measurement point is C3, as shown in Figure 32-185 and
32-155 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-186. In an external handover (inter-BSC handover), the measurement point is D3, as shown in Figure 32-187 and Figure 32-188.
Figure 32-185 Internal Handover Procedure - Intra-Cell Handover (Internal TC)

Figure 32-186 Internal Handover Procedure - Intra-Cell Handover with Channel Type Changed (External TC)

32-156 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-187 External Handover Procedure (Internal TC)

Figure 32-188 External Handover Procedure (External TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32-157 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

32.120 C901260203 Number of TCH/F Allocation Success by BSC for Handover (Speech Version 5)
Definition
Number of TCH/F allocation successes for handover (speech version 5)

Description
This counter counts successful TCH/F allocation attempts that occur to allocate a voice TCH/F (speech version 5) for handover. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/F. The BTS sends a CHL_ACT_ACK message to the BSC after the channel is successfully activated. When the TCH/F allocation succeeds with a CHL_ACT_ACK message received, this counter is incremented.

Measurement Point
This counter is incremented each time the BSC receives a CHL_ACT_ACK message from the BTS in the case of TCH/F allocation (speech version 5) for handover. The measurement point varies with different handover procedures and transcoders. In an internal handover (intra-BSC handover), the measurement point is C3, as shown in Figure 32-189 and Figure 32-190. In an external handover (inter-BSC handover), the measurement point is D3, as shown in Figure 32-191 and Figure 32-192.
Figure 32-189 Internal Handover Procedure - Intra-Cell Handover (Internal TC)

32-158 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-190 Internal Handover Procedure - Intra-Cell Handover with Channel Type Changed (External TC)

Figure 32-191 External Handover Procedure (Internal TC)

32-159 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 32-192 External Handover Procedure (External TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.121 C901260204 Number of TCH/F Allocation Failure Due to Channel Activation Failure for Handover (Speech Version 5)
Definition
Number of failed TCH/F allocations (speech version 5) for handover

Description
This counter counts TCH/F allocation failures due to channel activation failure during voice TCH/F allocation (speech version 5) for handover. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC completes the connection, and then sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/F. If the channel activation fails, this counter is incremented. The BSC considers the channel activation failed when the ChannelActivationNack message is received, the ChannelActivationAck message is not received, the timer T9103 expires, the channel instance is released, or the channel is forcibly disconnected.

32-160 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Measurement Point
This counter is incremented each time the TCH/F allocation fails due to channel activation failure during the channel allocation (speech version 4) for handover. The measurement point varies with different handover procedures and transcoders. In an internal handover (intra-BSC handover), the measurement point is C3, as shown in Figure 32-193. In an external handover (inter-BSC handover), the measurement point is D3, as shown in Figure 32-194.
Figure 32-193 Internal Handover Failure 1 - Intra-Cell Handover (Internal TC)

Figure 32-194 External Handover Failure 2 (Internal TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32-161 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

32.122 C901260205 Number of TCH/F Allocation Failure Due to BIU Connection Failure for Handover (Speech Version 5)
Definition
Number of failed TCH/F allocations (speech version 5) for handover due to BIU connection failure

Description
This counter counts TCH/F allocation failures due to BIU connection failure during voice channel allocation (speech version 5) for handover. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC sends a BIU connection request to the BIPB. If the BIU connection fails, this counter is incremented. The BSC considers the BIU connection failed when the BIU connection non-acknowledgement message is received, the BIU connection acknowledgement message is not received, or the corresponding timer expires.

Measurement Point
This counter is incremented each time the TCH/F allocation fails due to BIU connection failure during the voice channel allocation (speech version 4) for handover. The measurement point varies with different handover procedures and transcoders. In an internal handover (intra-BSC handover), the measurement point is C2, as shown in Figure 32-195. In an external handover (inter-BSC handover), the measurement point is D2, as shown in Figure 32-196.
Figure 32-195 Internal Handover Failure 2 - Intra-Cell Handover (Internal TC)

32-162 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Figure 32-196 External Handover Failure 3 (Internal TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.123 C901260206 Number of TCH/F Allocation Failure Due to Request AIPB Resource Failure for Assignment (Speech Version 4)
Definition
Number of failed TCH/F allocations (speech version 4) for assignment due to AIPB resource request failure

Description
This counter counts the TCH/F allocation failures due to failed request for AIPB resource during voice channel allocation for assignment. Upon receiving an assignment request (speech version 4) message, the BSC sends a request for AIPB resource to the database. If the database responds with a message of non-acknowledgement or no available AIPB resource, the BSC considers the AIPB resource request failed. This counter is incremented when the TCH/F allocation fails due to the AIPB resource request failure.

Usage
This counter reflects the frequency that TCH/F allocation fails due to AIPB resource request failure.

32-163 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the BSC receives a non-acknowledgement or no available AIPB resource message from the database during TCH/F allocation (speech version 4) for assignment. The measurement point is A, as shown in Figure 32-197.
Figure 32-197 Resource Request Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.124 C901260207 Number of TCH/F Allocation Failure Due to Request UDP Port Failure for Assignment (Speech Version 4)
Definition
Number of failed TCH/F allocations (speech version 4) for assignment due to UDP port request failure

Description
This counter counts TCH/F allocations that fail due to UDP port request failure during voice channel allocation for assignment. Upon receiving the assignment request (speech version 4) message, the BSC sends a connection request to the connection module. If the connection module responds with a connection failure message, which indicates that the failure reason is UDP port request failure, this counter is incremented.

Usage
This counter reflects the frequency that TCH/F allocation fails due to UDP port request failure.
32-164 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Measurement Point
This counter is incremented each time the BSC receives an EV_RANCONN_IPA_CONN_NACK message from the connection module, which indicates that the failure reason is UDP port request failure, during TCH/F allocation for assignment. The measurement point is A, as shown in Figure 32-198.
Figure 32-198 Channel Allocation Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.125 C901260208 Number of TCH/F Allocation Failure Due to AIPB Connection Failure for Assignment (Speech Version 4)
Definition
Number of failed TCH/F allocations (speech version 4) for assignment due to AIPB connection failure

Description
This counter counts TCH/F allocations that fail due to AIPB connection failure during voice channel allocation for assignment. Upon receiving the assignment request (speech version 4) message, the BSC sends a connection request to the connection module. If the connection module responds with a connection failure message, which indicates the failure reason is AIPB connection failure, this counter is incremented.

Usage
This counter reflects the frequency that TCH/F allocation fails due to AIPB connection failure.
32-165 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the BSC receives an EV_RANCONN_IPA_CONN_NACK message (indicating the failure reason is AIPB connection failure) from the connection module or the TwaitConn timer expires during TCH/F allocation for assignment. The measurement point is A, as shown in Figure 32-199.
Figure 32-199 Channel Allocation Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.126 C901260209 Number of TCH/F Allocation Failure Due to Request AIPB Resource Failure for Handover (Speech Version 4)
Definition
Number of failed TCH/F allocations (speech version 4) for handover due to AIPB resource request failure

Description
This counter counts TCH/F allocations that fail due to AIPB resource request failure during voice channel allocation for handover. Upon receiving an EV_RANUMC_RADIO_APPLY message during the voice channel allocation (speech version 4) for handover, the BSC sends a request for AIPB resource to the database. If the database responds with a request non-acknowledgement or no available AIPB resource message, the request for AIPB resource fails, which results in TCH/F allocation failure. This counter is incremented when the TCH/F allocation fails due to AIPB resource request failure.

32-166 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Usage
This counter reflects the frequency that TCH/F allocation fails due to AIPB resource request failure.

Measurement Point
This counter is incremented each time the BSC receives a request non-acknowledgement or no available AIPB resource message from the database during TCH/F allocation (speech version 4) for handover. The measurement point is A, as shown in Figure 32-200.
Figure 32-200 Resource Request Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.127 C901260210 Number of TCH/F Allocation Failure Due to Request UDP Port Failure for Handover (Speech Version 4)
Definition
Number of failed TCH/F allocations (speech version 4) for handover due to UDP port request failure

Description
This counter counts TCH/F allocations that fail due to UDP port request failure during voice channel allocation for handover. Upon receiving an EV_RANUMC_RADIO_APPLY message during the voice channel allocation (speech version 4) for handover, the BSC sends a connection request to the connection module. If the connection module responds with a connection failure
32-167 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

message, which indicates that the failure reason is UDP port request failure, this counter is incremented.

Usage
This counter reflects the frequency that TCH/F allocation fails due to UDP port request failure.

Measurement Point
This counter is incremented each time the BSC receives an EV_RANCONN_IPA_CONN_NACK message from the connection module, which indicates that the failure reason is UDP port request failure, during TCH/F allocation for handover. The measurement point is A, as shown in Figure 32-201.
Figure 32-201 Channel Allocation Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.128 C901260211 Number of TCH/F Allocation Failure Due to AIPB Connection Failure for Handover (Speech Version 4)
Definition
Number of failed TCH/F allocations (speech version 4) for handover due to AIPB connection failure

Description
This counter counts TCH/F allocations that fail due to AIPB connection failure during voice channel allocation for handover. Upon receiving an EV_RANUMC_RADIO_APPLY message during the voice channel allocation (speech version 4) for handover, the BSC sends a connection request to
32-168 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

the connection module. If the connection module responds with a connection failure message, which indicates that the failure reason is AIPB connection failure, this counter is incremented.

Usage
This counter reflects the frequency that TCH/F allocation fails due to AIPB connection failure.

Measurement Point
This counter is incremented each time the BSC receives an EV_RANCONN_IPA_CONN_NACK message (indicating the failure reason is AIPB connection failure) from the connection module or the TwaitConn timer expires during TCH/F allocation for handover. The measurement point is A, as shown in Figure 32-202.
Figure 32-202 Channel Allocation Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.129 C901260212 Number of TCH/F Allocation Failure Due to Request AIPB Resource Failure for Assignment (Speech Version 5)
Definition
Number of failed TCH/F allocations (speech version 5) for assignment due to AIPB resource request failure

Description
This counter counts the TCH/F allocation failures due to failed request for AIPB resource during voice channel allocation for assignment.
32-169 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Upon receiving an assignment request (speech version 5) message, the BSC sends a request for AIPB resource to the database. If the database responds with a message of non-acknowledgement or no available AIPB resource, the BSC considers the AIPB resource request failed. This counter is incremented when the TCH/F allocation fails due to the AIPB resource request failure.

Usage
This counter reflects the frequency that TCH/F allocation fails due to AIPB resource request failure.

Measurement Point
This counter is incremented each time the BSC receives a non-acknowledgement or no available AIPB resource message from the database during TCH/F allocation (speech version 5) for assignment. The measurement point is A, as shown in Figure 32-203.
Figure 32-203 Resource Request Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.130 C901260213 Number of TCH/F Allocation Failure Due to Request UDP Port Failure for Assignment (Speech Version 5)
Definition
Number of failed TCH/F allocations (speech version 5) for assignment due to UDP port request failure

32-170 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Description
This counter counts TCH/F allocations that fail due to UDP port request failure during voice channel allocation for assignment. Upon receiving the assignment request (speech version 5) message, the BSC sends a connection request to the connection module. If the connection module responds with a connection failure message, which indicates that the failure reason is UDP port request failure, this counter is incremented.

Usage
This counter reflects the frequency that TCH/F allocation fails due to UDP port request failure.

Measurement Point
This counter is incremented each time the BSC receives an EV_RANCONN_IPA_CONN_NACK message from the connection module, which indicates that the failure reason is UDP port request failure, during TCH/F allocation for assignment. The measurement point is A, as shown in Figure 32-204.
Figure 32-204 Channel Allocation Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.131 C901260214 Number of TCH/F Allocation Failure Due to AIPB Connection Failure for Assignment (Speech Version 5)
Definition
Number of failed TCH/F allocations (speech version 5) for assignment due to AIPB connection failure
32-171 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts TCH/F allocations that fail due to AIPB connection failure during voice channel allocation for assignment. Upon receiving the assignment request (speech version 5) message, the BSC sends a connection request to the connection module. If the connection module responds with a connection failure message, which indicates that the failure reason is AIPB connection failure, this counter is incremented.

Usage
This counter reflects the frequency that TCH/F allocation fails due to AIPB connection failure.

Measurement Point
This counter is incremented each time the BSC receives an EV_RANCONN_IPA_CONN_NACK message (indicating the failure reason is AIPB connection failure) from the connection module or the TwaitConn timer expires during TCH/F allocation for assignment. The measurement point is A, as shown in Figure 32-205.
Figure 32-205 Channel Allocation Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32.132 C901260215 Number of TCH/F Allocation Failure Due to Request AIPB Resource Failure for Handover (Speech Version 5)
Definition
Number of failed TCH/F allocations (speech version 5) for handover due to AIPB resource request failure
32-172 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Description
This counter counts TCH/F allocations that fail due to AIPB resource request failure during voice channel allocation for handover. Upon receiving an EV_RANUMC_RADIO_APPLY message during the voice channel allocation (speech version 5) for handover, the BSC sends a request for AIPB resource to the database. If the database responds with a request non-acknowledgement or no available AIPB resource message, the request for AIPB resource fails, which results in TCH/F allocation failure. This counter is incremented when the TCH/F allocation fails due to AIPB resource request failure.

Usage
This counter reflects the frequency that TCH/F allocation fails due to AIPB resource request failure.

Measurement Point
This counter is incremented each time the BSC receives a request non-acknowledgement or no available AIPB resource message from the database during TCH/F allocation (speech version 4) for handover. The measurement point is A, as shown in Figure 32-206.
Figure 32-206 Resource Request Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

32-173 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

32.133 C901260216 Number of TCH/F Allocation Failure Due to Request UDP Port Failure for Handover (Speech Version 5)
Definition
Number of failed TCH/F allocations (speech version 5) for handover due to UDP port request failure

Description
This counter counts TCH/F allocations that fail due to UDP port request failure during voice channel allocation for handover. Upon receiving an EV_RANUMC_RADIO_APPLY message during the voice channel allocation (speech version 5) for handover, the BSC sends a connection request to the connection module. If the connection module responds with a connection failure message, which indicates that the failure reason is UDP port request failure, this counter is incremented.

Usage
This counter reflects the frequency that TCH/F allocation fails due to UDP port request failure.

Measurement Point
This counter is incremented each time the BSC receives an EV_RANCONN_IPA_CONN_NACK message from the connection module, which indicates that the failure reason is UDP port request failure, during TCH/F allocation for handover. The measurement point is A, as shown in Figure 32-207.
Figure 32-207 Channel Allocation Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)
32-174 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

32.134 C901260217 Number of TCH/F Allocation Failure Due to AIPB Connection Failure for Handover (Speech Version 5)
Definition
Number of failed TCH/F allocations (speech version 5) for handover due to AIPB connection failure

Description
This counter counts TCH/F allocations that fail due to AIPB connection failure during voice channel allocation for handover. Upon receiving an EV_RANUMC_RADIO_APPLY message during the voice channel allocation (speech version 5) for handover, the BSC sends a connection request to the connection module. If the connection module responds with a connection failure message, which indicates that the failure reason is AIPB connection failure, this counter is incremented.

Usage
This counter reflects the frequency that TCH/F allocation fails due to AIPB connection failure.

Measurement Point
This counter is incremented each time the BSC receives an EV_RANCONN_IPA_CONN_NACK message (indicating the failure reason is AIPB connection failure) from the connection module or the TwaitConn timer expires during TCH/F allocation for handover. The measurement point is A, as shown in Figure 32-208.
Figure 32-208 Channel Allocation Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)
32-175 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

32.135 C901260218 Number of FR_V4 Assignment Attempts

Description
This counter counts the attempts that occur to assign a voice TCH/F channel (speech version 4). Upon receiving a channel request message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC sends a CHL_ACT message to the BTS for activating the TCH/F. In the case of assignment request coming from A interface, this counter and counter C901260219 are incremented when an assignment complete message is received. If no attaching message is received from the MS during the required time, this assignment fails and this counter is incremented.

Measurement Point
This counter is incremented when the BSC receives an assignment complete message, an assignment failure message, a timer expiry message, or an unexpected message, or the channel instance is released or forcibly disconnected.

Unit
Times

32.136 C901260219 Number of FR_V4 Assignment Success

Description
This counter counts successful assignments of voice TCH/F channel (speech version 4). Upon receiving a channel request message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC sends a CHL_ACT message to the BTS for activating the TCH/F. In the case of assignment request from A interface, this counter is incremented when an assignment complete message is received.

Measurement Point
This counter is incremented when an assignment complete message is received.

Unit
Times

32-176 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

32.137 C901260220 Number of FR_V5 Assignment Attempts

Description
This counter counts the attempts that occur to assign a voice TCH/F channel (speech version 5). Upon receiving a channel request message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC sends a CHL_ACT message to the BTS for activating the TCH/F. In the case of assignment request from A interface, this counter and counter C901260221 are incremented when an assignment complete message is received. If no attaching message is received from the MS during the required time, this assignment fails and this counter is incremented.

Measurement Point
This counter is incremented when the BSC receives an assignment complete message, an assignment failure message, a timer expiry message, or an unexpected message, or the channel instance is released or forcibly disconnected.

Unit
Times

32.138 C901260221 Number of FR_V5 Assignment Success

Description
This counter counts successful assignments of voice TCH/F channel (speech version 5). Upon receiving a channel request message, the BSC responds to the message with a TCH/F allocated and occupied. After that, the BSC sends a CHL_ACT message to the BTS for activating the TCH/F. In the case of assignment request from A interface, this counter is incremented when an assignment complete message is received.

Measurement Point
This counter is incremented when an assignment complete message is received.

Unit
Times

32-177 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

32.139 C901260222 Number of FR_V4 Handover

Description
This counter counts the handover attempts that occur to hand over an MS to a voice TCH/F (speech version 4). When the MS is successfully attached to the target voice TCH/F channel, the BSC receives an ASS_COM message (intra-cell handover), or an HO_COM message (inter-cell handover or external handover). When the BSC receives the ASS_COM or HO_COM message within the required time, which indicates that the handover succeeds, this counter and counter C901260223 are incremented. When the BSC receives an HO_FAILURE message, which indicates a responded handover failure, this counter is incremented. When the handover fails but the BSC does not receive an HO_FAILURE message, which indicates a un-responded handover failure, this counter is incremented. In the case of intra-cell handover or inter-cell handover, the counter corresponding to the source instance is incremented. In the case of external handover, the counter corresponding to the target instance is incremented because the source instance is not in the local BSC.

Measurement Point
This counter is incremented when the BSC receives an ASS_COM, HO_COM, ASS_FAIL, HO_FAIL, or an unexpected message, the instance is released or forcibly disconnected, or the corresponding timer expires.

Unit
Times

32.140 C901260223 Number of FR_V4 Handover Success

Description
This counter counts the successes of handover to a voice TCH/F (speech version 4). When the BSC receives a message indicating the handover success from the MS through the allocated TCH/F, this counter is incremented. In the case of intra-cell handover, the ASS_COM message indicates the handover success. In the case of inter-cell or external handover, the HO_COM message indicates the handover success. In the case of intra-cell handover or inter-cell handover, the counter corresponding to the source instance is incremented. In the case of external handover, the counter corresponding to the target instance is incremented because the source instance is not in the local BSC.

32-178 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 32 TCH/F Measurement

Measurement Point
This counter is incremented when the BSC receives an ASS_COM or HO_COM message.

Unit
Times

32.141 C901260224 Number of FR_V5 Handover

Description
This counter counts the handover attempts that occur to hand over an MS to a voice TCH/F (speech version 5). When the MS is successfully attached to the target voice TCH/F channel, the BSC receives an ASS_COM message (intra-cell handover), or an HO_COM message (inter-cell handover or external handover). When the BSC receives the ASS_COM or HO_COM message within the required time, which indicates that the handover succeeds, this counter and counter C901260225 are incremented. When the BSC receives an HO_FAILURE message, which indicates a responded handover failure, this counter is incremented. When the handover fails but the BSC does not receive an HO_FAILURE message, which indicates a un-responded handover failure, this counter is incremented. In the case of intra-cell handover or inter-cell handover, the counter corresponding to the source instance is incremented. In the case of external handover, the counter corresponding to the target instance is incremented because the source instance is not in the local BSC.

Measurement Point
This counter is incremented when the BSC receives an ASS_COM, HO_COM, ASS_FAIL, HO_FAIL, or an unexpected message, the instance is released or forcibly disconnected, or the corresponding timer expires.

Unit
Times

32.142 C901260225 Number of FR_V5 Handover Success

Description
This counter counts the successes of handover to a voice TCH/F (speech version 5). When the BSC receives a message indicating the handover success from the MS through the allocated TCH/F, this counter is incremented. In the case of intra-cell handover, the
32-179 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ASS_COM message indicates the handover success. In the case of inter-cell or external handover, the HO_COM message indicates the handover success. In the case of intra-cell handover or inter-cell handover, the counter corresponding to the source instance is incremented. In the case of external handover, the counter corresponding to the target instance is incremented because the source instance is not in the local BSC.

Measurement Point
This counter is incremented when the BSC receives an ASS_COM or HO_COM message.

Unit
Times

32-180 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 with reconnection ........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 C901270050 Number of TCH/H allocation attempts for assignment (speech version 3) ...........................................................................................................................33-41 C901270051 Number of TCH/H allocation success for assignment (speech version 3) ...........................................................................................................................33-43 C901270056 Number of TCH/H allocation attempts by BSC for handover (speech version 3) ...............................................................................................................33-44 C901270057 Number of TCH/H allocation success for handover (speech version 3) ...........................................................................................................................33-47 C901270062 Number of Voice TCH/H assignment attempts by BSC......................33-49 C901270065 Number of Voice TCH/H handover attempts ......................................33-51 C901270067 Number of Voice TCH/H handover failure with reconnection..............33-54
33-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901270068 Number of Voice TCH/H handover failure messages do not received by BSC...................................................................................................................33-55 C901270070 Number of data TCH/H seizure success for assignment ....................33-56 C901270073 Number of data TCH/H seizure success for handover .......................33-58 C901270075 Number of data TCH/H allocation attempts for assignment by BSC...33-60 C901270076 Number of data TCH/H allocation success for assignment ................33-62 C901270081 Number of data TCH/H allocation attempts by BSC...........................33-63 C901270082 Number of data TCH/H allocation success for handover....................33-66 C901270087 Number of data TCH/H assignment attempts by BSC........................33-68 C901270090 Number of data TCH/H handover attempts........................................33-70 C901270092 Number of data TCH/H handover failure with reconnection ...............33-73 C901270093 Number of data TCH/H handover failure do not received by BSC ......33-74 C901270094 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 1).....................................................................33-76 C901270095 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 1)................................................................33-77 C901270096 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 1).....................................................................33-78 C901270097 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 1)................................................................33-79 C901270102 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 3).....................................................................33-81 C901270103 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 3)................................................................33-82 C901270104 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 3).....................................................................33-83 C901270105 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 3)................................................................33-84 C901270106 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 1) ...............................................................33-86 C901270107 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 1)..........................................................................33-87 C901270108 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 1)...............................................................................33-88 C901270109 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 1)...................................................................33-89 C901270110 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 1) .............................................................................33-90 C901270111 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 1) ..................................................................................33-91 C901270118 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 3) ...............................................................33-92 C901270119 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 3)..........................................................................33-93

33-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

C901270120 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 3)...............................................................................33-94 C901270121 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 3)...................................................................33-95 C901270122 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 3) .............................................................................33-96 C901270123 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 3) ..................................................................................33-97 C901270124 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (data) ...................................................................................33-98 C901270125 Number of TCH/H allocation failure due to request UDP port failure for assignment (data) .............................................................................................33-99 C901270126 Number of TCH/H allocation failure due to AIPB connection failure for assignment (data) ................................................................................................33-100 C901270127 Number of TCH/H allocation failure due to request AIPB resource failure for handover (data) ....................................................................................33-101 C901270128 Number of TCH/H allocation failure due to request UDP port failure for handover (data)...............................................................................................33-102 C901270129 Number of TCH/H allocation failure due to AIPB connection failure for handover (data)....................................................................................................33-103 C901270130 Number of assign TCH/H release by forced handover to forced handover source ..................................................................................................33-104 C901270131 Number of assign TCH/H release by forced handover to queuing user......................................................................................................................33-104 C901270132 Number of restore TCH/H release by forced handover to DBS ........33-105 C901270133 Number of assign TCH/H release by forced release to forced release source ..................................................................................................................33-105 C901270134 Number of assign TCH/H release by forced release to queuing user......................................................................................................................33-106 C901270135 Number of restore TCH/H release by forced release to DBS ...........33-107 C901270136 Number of signaling TCH/H seize failure for assign due to Abis lack ......................................................................................................................33-107 C901270137 Number of signaling TCH/H seize failure for handover due to Abis lack ......................................................................................................................33-108 C901270138 Number of voice TCH/H seizure failure for assignment (cause:Abis) .........................................................................................................33-108 C901270139 Number of voice TCH/H seizure failure for handover (cause:Abis )..33-109 C901270140 Number of data TCH/H seizure failure for assignment (cause:Abis) .33-109 C901270141 Number of data TCH/H seizure failure for handover (cause:Abis) .... 33-110 C901270142 Number of signaling TCH/H seize failure for assign due to radio resource lack........................................................................................................ 33-110 C901270143 Number of signaling TCH/H seize failure for handover due to radio resource lack........................................................................................................ 33-111 C901270144 Number of voice TCH/H seizure failure for assignment (cause:radio resource).............................................................................................................. 33-111
33-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901270145 Number of voice TCH/H seizure failure for handover (cause:radio resource).............................................................................................................. 33-112 C901270146 Number of data TCH/H seizure failure for assignment (cause:radio resource).............................................................................................................. 33-112 C901270147 Number of data TCH/H seizure failure for handover (cause:radio resource).............................................................................................................. 33-113 C901270148 Number of HR_V1 assignment attempts.......................................... 33-113 C901270149 Number of HR_V1 assignment success .......................................... 33-114 C901270150 Number of HR_V3 assignment attempts.......................................... 33-114 C901270151 Number of HR_V3 assignment success .......................................... 33-115 C901270152 Number of HR_V1 handover ........................................................... 33-115 C901270153 Number of HR_V1 handover success.............................................. 33-116 C901270154 Number of HR_V3 handover ........................................................... 33-116 C901270155 Number of HR_V3 handover success.............................................. 33-117 C901270177 Resource releasing of ordinary users due to being grabbed (TCH/H) ............................................................................................................... 33-117 C901270178 Handover of ordinary users due to being grabbed (TCH/H) ............. 33-118 C901270179 Number of Channel Request of priority users (TCH/H) ....................33-120 C901270180 Number of Successful Channel seize of priority users (TCH/H) .......33-121 C901270181 Number of Successful grabbing channel of priority users (TCH/H)...33-122 C901270182 Number of HR_V4 Assignment Attempts .........................................33-123 C901270183 Number of HR_V4 Assignment Success .........................................33-124 C901270184 Number of HR_V4 Handover...........................................................33-124 C901270185 Number of HR_V4 Handover Success.............................................33-125 C901270186 Number of TCH/H Allocation Attempts for Assignment (Speech Version 4).............................................................................................................33-125 C901270187 Number of TCH/H Allocation Success for Assignment (Speech Version4)..............................................................................................................33-127 C901270188 Number of TCH/H Allocation Failure Due to Channel Activation Failure for Assignment (Speech Version 4)...........................................................33-128 C901270189 Number of TCH/H Allocation Failure Due to BIU Connection Failure for Assignment (Speech Version 4) ......................................................................33-129 C901270190 Number of TCH/H Allocation Attempts by BSC for Handover (Speech Version 4).............................................................................................................33-130 C901270191 Number of TCH/H Allocation Success by BSC for Handover (Speech Version 4).............................................................................................................33-133 C901270192 Number of TCH/H Allocation Failure Due to Channel Activation Failure for Handover (Speech Version 4) ..............................................................33-135 C901270193 Number of TCH/H Allocation Failure Due to BIU Connection Failure for Handover (Speech Version 4)..........................................................................33-137 C901270194 Number of TCH/H Allocation Failure Due to Request AIPB Resource Failure for Assignment (Speech Version 4)...........................................................33-138 C901270195 Number of TCH/H Allocation Failure Due to Request UDP Port Failure for Assignment (Speech Version 4)...........................................................33-139

33-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

C901270196 Number of TCH/H Allocation Failure Due to AIPB Connection Failure for Assignment (Speech Version 4) ......................................................................33-140 C901270197 Number of TCH/H Allocation Failure Due to Request AIPB Resource Failure for Handover (Speech Version 4) ..............................................................33-141 C901270198 Number of TCH/H Allocation Failure Due to Request UDP Port Failure for Handover (Speech Version 4) ..............................................................33-142 C901270199 Number of TCH/H Allocation Failure Due to AIPB Connection Failure for Handover (Speech Version 4)..........................................................................33-143

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.
Figure 33-1 Immediate assignment flow

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-2 Common assignment flow (internal TC)

Figure 33-3 Common assignment flow (external TC)

When TC is internal and external, the measurement point of TCH/H counter in inner handover process is shown in Figure 33-4 and Figure 33-5.

33-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-4 Internal handover (like intra-cell handover) flow (internal TC)

Figure 33-5 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-6 External handover flow (internal TC)

Figure 33-7 External handover flow (external TC)

33.2 C901270002 Number of signaling TCH/H seizure success for assignment

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.

33-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

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.
Figure 33-8 Immediate assignment flow

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation

33.3 C901270005 Number of signaling TCH/H seizure success for handover

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.
33-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 33-9 Internal handover (like intra-cell handover) flow (internal TC)

Figure 33-10 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

33-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-11 External handover flow (internal TC)

Figure 33-12 External handover flow (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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). The measurement point is A2, as shown in Figure 33-13.
Figure 33-13 Immediate assignment flow

33-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation

33.5 C901270008 Number of signaling TCH/H allocation success for assignment

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.
Figure 33-14 Immediate assignment flow

33-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation

33.6 C901270010 Number of signaling TCH/H allocation 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-15 Internal handover (like intra-cell handover) flow (internal TC)

Figure 33-16 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

33-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-17 External handover flow (internal TC)

Figure 33-18 External handover flow (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.7 C901270011 Number of signaling TCH/H allocation 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 shown in Figure 33-19, Figure 33-20, Figure 33-21, and Figure 33-22.
Figure 33-19 Internal handover (like intra-cell handover) flow (internal TC)

33-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-20 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 33-21 External handover flow (internal TC)

33-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-22 External handover flow (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33.8 C901270012 Number of signaling TCH/H allocation 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. After BSC responds channel request message assignment and successfully occupies TCH/H channel, BSC send channel activation message CHL_ACT to BTS to activate the TCH/H. If channel activation fails due to receiving channel activation failure message, wrong channel activation response message, timer T9103 timeout, channel instance being released, channel being forced to disconnection etc, this counter will increment.

Measurement Point
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-23 Internal handover (internal TC intra-cell handover) failure flow 1

Figure 33-24 External handover failure flow 2 (internal TC)

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation

33.9 C901270013 Number of signaling TCH/H 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

After BSC responds channel request message assignment and successfully occupies channel, BSC sends channel activation message CHL_ACT to BTS to activate the TCH/H. To immediate allocation, after activated successfully BTS receives MS and send EST_IND message to BSC, BSC receives the messages and this counter 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.
Figure 33-25 Immediate assignment flow

Unit
Times

Related Features
l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

33.10 C901270016 Number of signaling TCH/H handover attempts

Definition
Number of signaling TCH/H handover attempts

33-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 33-26 Internal handover (like intra-cell handover) flow (internal TC)

33-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-27 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 33-28 External handover flow (internal TC)

33-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-29 External handover flow (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33.11 C901270017 Number of signaling TCH/H 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

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.
Figure 33-30 Internal handover (like intra-cell handover) flow (internal TC)

Figure 33-31 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

33-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-32 External handover flow (internal TC)

Figure 33-33 External handover flow (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.12 C901270018 Number of signaling TCH/H handover failure with reconnection

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.
Figure 33-34 Internal handover (internal TC intra-cell handover) failure flow 1

33-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-35 External handover failure flow (internal TC)

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33.13 C901270019 Number of signaling TCH/H 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-36 Internal handover (internal TC intra-cell handover) failure flow 2

Figure 33-37 Internal handover (internal TC intra-cell handover) failure flow 3

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33.14 C901270021 Number of voice TCH/H seizure success for assignment

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 33-38 Internal handover (internal TC intra-cell handover) failure flow 1

Figure 33-39 External handover failure flow (internal TC)

33-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33.15 C901270024 Number of voice TCH/H seizure success for handover

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. 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 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-40 Internal handover (like intra-cell handover) flow (internal TC)

Figure 33-41 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

33-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-42 External handover flow (internal TC)

Figure 33-43 External handover flow (external TC)

Unit
Times

Related Features
l l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 33-44 Common assignment flow (internal TC)

33-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-45 Common assignment flow (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33.17 C901270027 Number of TCH/H allocation success for assignment (speech version1)
Definition
Number of TCH/H allocation success for assignment (speech version1)

Description
This counter counts the number of TCH/H channel being attempt to assign on allocation voice channel (used for voice version 1). After BSC respond channel request message assignment and successfully occupied channel, BSC sends channel activation message CHL_ACT to BTS to activate the TCH/F. If activation succeeds, BSC will receive the CHL_ACT_ACK message sent by BTS. It indicated that TCH/H assignment succeeds, this counter accumulate.

Measurement Point
BSC correctly receives the CHL_ACT_ACK message sent by BTS, and because allocation and usage are voice channel (use voice version 1). The measurement point is B3, as shown in Figure 33-46, Figure 33-47.
33-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-46 Common assignment flow (internal TC)

Figure 33-47 Common assignment flow (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.18 C901270032 Number of TCH/H allocation 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) 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 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.
Figure 33-48 Internal handover (like intra-cell handover) flow (internal TC)

33-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-49 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 33-50 External handover flow (internal TC)

Unit
Times

Related Features
l l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.19 C901270033 Number of TCH/H allocation success during handover (speech version 1)
Definition
Number of TCH/H allocation success during handover (speech version 1)

Description
This counter counts the number of TCH/H channel success assignment on voice channel (use voice version 1). After BSC respond channel request message assignment and successfully occupied channel, BSC sends channel activation message CHL_ACT to BTS to activate the TCH/F. If activation succeeds, it will receive CHL_ACT_ACK message sent by BTS. It indicated that TCH/H assignment succeeds, this counter accumulate.

Measurement Point
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.
Figure 33-51 Internal handover (like intra-cell handover) flow (internal TC)

33-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-52 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 33-53 External handover flow (internal TC)

33-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-54 External handover flow (external TC)

Unit
Times

Related Features
l l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33.20 C901270050 Number of TCH/H allocation attempts for assignment (speech version 3)
Definition
Number of TCH/H allocation attempts for assignment (speech version 3)

Description
This counter counts the number of TCH/H channel being attempt to assign on allocation voice channel (use voice version 3), including assignment success (C901270051) and assignment failure (C900060191+C900060192+900060193+C900060194) After BSC responds 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 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 C901270045 accumulate simultaneously; on the contrary, if failed, this counter and another counter related the failure reason accumulate simultaneously.
33-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-55and Figure 33-56.
Figure 33-55 Common assignment flow (internal TC)

Figure 33-56 Common assignment flow (external TC)

Unit
Times

Related Features
l l l l l ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface
33-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.21 C901270051 Number of TCH/H allocation success 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). After BSC responds channel request message assignment and successfully occupied channel, BSC sends channel activation message CHL_ACT to BTS to activate the TCH/F. If activation succeeds, it will receive CHL_ACT_ACK message sent by BTS. It indicated that TCH/H assignment succeeds, this counter accumulate.

Measurement Point
BSC correctly receives the CHL_ACT_ACK message sent by BTS, and because allocation and usage are voice channel (use voice version 3). The measurement point is B3, as shown in Figure 33-57 and Figure 33-58.
Figure 33-57 Common assignment flow (internal TC)

33-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-58 Common assignment flow (external TC)

Unit
Times

Related Features
l l l l l ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33.22 C901270056 Number of TCH/H allocation attempts by BSC for handover (speech version 3)
Definition
Number of TCH/H allocation attempts by BSC for handover (speech version 3)

Description
This counter counts the number of TCH/H channel being attempt to assign on voice channel (use voice version 3), including assignment success (C901270057) and assignment failure (C900060195+C900060196+900060197+C900060198) After BSC responds 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 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 C901270057 accumulate simultaneously; on the contrary, if failed, this counter and another counter related the failure reason accumulate simultaneously.

33-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Measurement Point
Assignment succeeds or fails (because handover, usage are voice channel, use voice version 3). The measurement points are C3, D3, as shown in Figure 33-59, Figure 33-60, Figure 33-61, and Figure 33-62.
Figure 33-59 Internal handover (like intra-cell handover) flow (internal TC)

Figure 33-60 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

33-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-61 External handover flow (internal TC)

Figure 33-62 External handover flow (external TC)

Unit
Times

Related Features
l l l l l l ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.23 C901270057 Number of TCH/H allocation success for handover (speech version 3)
Definition
Number of TCH/H allocation success for handover (speech version 3)

Description
This counter counts the number of TCH/H channel success assignment on voice channel (use voice version 3). After BSC responds channel request message assignment and successfully occupied channel, BSC sends channel activation message CHL_ACT to BTS to activate the 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
BSC correctly receives the CHL_ACT_ACK message sent by BTS, and because handover and usage are voice channel (use voice version 3). The measurement points are C3, D3, as shown in Figure 33-63, Figure 33-64, Figure 33-65, and Figure 33-66.
Figure 33-63 Internal handover (like intra-cell handover) flow (internal TC)

33-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-64 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 33-65 External handover flow (internal TC)

33-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-66 External handover flow (external TC)

Unit
Times

Related Features
l l l l l l ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33.24 C901270062 Number of Voice TCH/H assignment 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). After BSC responds channel request message assignment and successfully occupied channel, BSC sends channel activation message CHL_ACT to BTS to activate the TCH/H. For allocation from A-interface, after receiving allocation success message, this counter and C900060199 accumulate simultaneously. If it is impossible to receive MS access notification in the certain time, the assignment fails, this counter and C900060200 accumulate simultaneously.
33-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-67and Figure 33-68.
Figure 33-67 Common assignment flow (internal TC)

Figure 33-68 Common assignment flow (external TC)

Unit
Times

Related Features
l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation

33-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.25 C901270065 Number of Voice TCH/H handover 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-69, Figure 33-70, Figure 33-71, and Figure 33-72.

33-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-69 Internal handover (like intra-cell handover) flow (internal TC)

Figure 33-70 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

33-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-71 External handover flow (internal TC)

Figure 33-72 External handover flow (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.26 C901270067 Number of Voice TCH/H handover failure with reconnection

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-73and Figure 33-74.
Figure 33-73 Internal handover (internal TC intra-cell handover) failure flow 1

33-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-74 External handover failure flow (internal TC)

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33.27 C901270068 Number of Voice TCH/H handover failure messages do not received by BSC
Definition
Number of Voice TCH/H handover failure messages do not received by BSC

Description
This counter counts the number of TCH/H channel returning no handover failure on voice channel handover. BSC sends allocation request/handover request to MS, MS does not handover successfully, not return resource channel, and then accumulates.

Measurement Point
BSC receives abnormal message, timer timeout message or the instance being released, the instance being forced to disconnection. The measurement points are C4, D4, as shown in Figure 33-75and Figure 33-76.
33-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-75 Internal handover (internal TC intra-cell handover) failure flow 2

Figure 33-76 Internal handover (internal TC intra-cell handover) failure flow 3

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33.28 C901270070 Number of data TCH/H seizure success for assignment

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-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

After BSC receives channel request message, it attempts to assign channel for the request. If assignments and occupation succeed, this counter will accumulate; If application returns no channel but possible to queue or force to disconnect, it enters the status of waiting resource. This counter will also accumulate until waiting succeeds.

Measurement Point
BSC applies for channel (because allocation, usage are data channels) and occupies successfully, or BSC receives inner waiting resource valid message. The measurement points is B1, as shown in Figure 33-77and Figure 33-78.
Figure 33-77 Common assignment flow (internal TC)

Figure 33-78 Common assignment flow (external TC)

Unit
Times

33-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33.29 C901270073 Number of data TCH/H seizure success for handover

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. After BSC receives channel request message, it attempts to assign channel for the request. If assignments and occupation succeed, this counter will accumulate; If application returns no channel but possible to queue or force to disconnect, it enters the status of waiting resource. This counter will also accumulate until waiting succeeds.

Measurement Point
BSC applies for channel (because handover, usage are data channels) and occupies successfully, or BSC receives inner waiting resource valid message. The measurement points are C1, D1, as shown in Figure 33-79, Figure 33-80, Figure 33-81, and Figure 33-82.
Figure 33-79 Internal handover (like intra-cell handover) flow (internal TC)

33-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-80 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 33-81 External handover flow (internal TC)

33-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-82 External handover flow (external TC)

Unit
Times

Related Features
l l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33.30 C901270075 Number of data TCH/H allocation 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
After BSC responds 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 TCH/H. If activation succeeds, it will receive the CHL_ACT_ACK message sent by BTS. It indicated that TCH/H assignment succeeds,
33-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

this related counter and C901270076 accumulate simultaneously; on the contrary, if fails, this counter and another counter related the failure reason accumulate simultaneously.

Measurement Point
Assignment succeeds or fails (because allocation, usage are data channel). measurement points are B2, B5, as shown in Figure 33-83and Figure 33-84.
Figure 33-83 Common assignment flow (internal TC)

The

Figure 33-84 Common assignment flow (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation
33-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33.31 C901270076 Number of data TCH/H allocation success for assignment

Definition
Number of data TCH/H allocation success for assignment

Description
This counter counts the number of TCH/H channel being assigned successfully. After BSC responds channel request message assignment and successfully occupied channel, BSC sends 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 indicated that TCH/H assignment succeeds, This counter accumulates.

Measurement Point
BSC correctly receives the CHL_ACT_ACK message sent by BTS, and because allocation and usage are data channel. The measurement points is B3, as shown in Figure 33-85and Figure 33-86.
Figure 33-85 Common assignment flow (internal TC)

33-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-86 Common assignment flow (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33.32 C901270081 Number of data TCH/H allocation 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). After BSC responds 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 TCH/H. If activation succeeds, it will receive the CHL_ACT_ACK message sent by BTS. It indicated that TCH/H assignment succeeds, this related counter and C901270082 accumulate simultaneously; on the contrary, if fails, this counter and another counter related the failure reason accumulate simultaneously.

33-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
Assignment succeeds or fails (because handover, usage are data channels). The measurement points are C3, D3, as shown in Figure 33-87, Figure 33-88, Figure 33-89, and Figure 33-90.
Figure 33-87 Internal handover (like intra-cell handover) flow (internal TC)

Figure 33-88 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

33-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-89 External handover flow (internal TC)

Figure 33-90 External handover flow (external TC)

Unit
Times

Related Features
l l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.33 C901270082 Number of data TCH/H allocation success for handover

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. After BSC responds channel request message assignment and successfully occupied channel, BSC sends 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 and indicate that TCH/H assignment succeeds. This counter accumulates.

Measurement Point
BSC correctly receives the CHL_ACT_ACK message sent by BTS, and because handover and usage are data channel. The measurement points are C3, D3, as shown in Figure 33-91, Figure 33-92, Figure 33-93, and Figure 33-94.
Figure 33-91 Internal handover (like intra-cell handover) flow (internal TC)

33-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-92 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

Figure 33-93 External handover flow (internal TC)

33-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-94 External handover flow (external TC)

Unit
Times

Related Features
l l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33.34 C901270087 Number of data TCH/H assignment attempts by BSC

Definition
Number of data TCH/H assignment attempts by BSC

Description
This counter counts the number of attempting TCH/H channel to be data channel, including assignment success (C900060210) and allocation failure (C900060211). After BSC responds channel request message assignment and successfully occupied channel, BSC sends channel activation message CHL_ACT to BTS to activate the TCH/H. For allocation from A-interface, after receiving allocation success message, this counter and C900060210 accumulate simultaneously. If it is impossible to receive MS access notification in the certain time, the assignment fails, this counter and C900060211 accumulate simultaneously.

33-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

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-95and Figure 33-96.
Figure 33-95 Common assignment flow (internal TC)

Figure 33-96 Common assignment flow (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation

33-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.35 C901270090 Number of data TCH/H handover 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-97, Figure 33-98, Figure 33-99, and Figure 33-100.

33-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-97 Internal handover (like intra-cell handover) flow (internal TC)

Figure 33-98 Internal handover (during Intra-cell handover, and channel types are changed) flow (external TC)

33-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-99 External handover flow (internal TC)

Figure 33-100 External handover flow (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.36 C901270092 Number of data TCH/H handover failure with reconnection

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-101and Figure 33-102.
Figure 33-101 Internal handover (internal TC intra-cell handover) failure flow 1

33-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-102 External handover failure flow (internal TC)

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33.37 C901270093 Number of data TCH/H handover failure do not received by BSC
Definition
Number of data TCH/H handover failure do not received by BSC

Description
This counter counts the number of TCH/H channel returning no handover failure on data channel handover. After BSC sends allocation request/handover request to MS, MS does not handover successfully, not go back to the original channel, then accumulate.

33-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

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-103and Figure 33-104.
Figure 33-103 Internal handover (internal TC intra-cell handover) failure flow 2

Figure 33-104 Internal handover (internal TC intra-cell handover) failure flow 3

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking

33-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.38 C901270094 Number of TCH/H allocation failure 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). After BSC responds channel request message assignment and successfully occupied TCH/H channel, BSC sends TIU connection request to TIPB. If TIU connection fails due to receiving TIU connection failure, or wrong TIU connection respond message, timer timeout, then this counter will accumulate.

Measurement Point
Due to allocation BSC uses TCH/H. Receive connection failure message, wrong connection respond message, or timer timeout when in TIU connection. The measurement point is B2, as shown in Figure 33-105.
Figure 33-105 General Assignment Failure Flow 1 (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface
33-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.39 C901270095 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 1)
Definition
Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 1)

Description
This counter counts the number of TCH/H channel assignment failure due to iTC application resource failure when allocating voice channel (use voice version 1). After BSC responds channel request message assignment and successfully occupied TCH/H channel, BSC apply for resource to iTC. If iTC application resource fails due to receiving iTC resource unavailability, or wrong response message, or timer timeout, then it contributes to TCH/H assignment failure and this counter will accumulate.

Measurement Point
Due to allocation BSC uses TCH/H. Receive iTC resource unabailability, wrong respond message, or timer timeout when in iTC application resource. The measurement point is B1, as shown in Figure 33-106.
Figure 33-106 General Assignment Failure Flow 2 (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface
33-77 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.40 C901270096 Number of TCH/H allocation failure 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). After BSC responds channel request message assignment and successfully occupied TCH/H channel, BSC sends TIU connection request to TIPB. If TIU connection fails due to receiving TIU connection failure, or wrong TIU connection response message, timer timeout, then this counter will accumulate.

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-107and Figure 33-108.
Figure 33-107 Internal handover (external TC intra-cell handover, and channel types are changed) failure flow 1

33-78 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-108 External handover flow (external TC)

Unit
Times

Related Features
l l l l l ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33.41 C901270097 Number of TCH/H allocation failure 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
This counter counts the number of TCH/H channel assignment failure due to iTC application resource failure when voice channel handover (use voice version 1). After BSC responds channel request message assignment and successfully occupied TCH/H channel, the type of BSC judgement channel changes. Need to reapply TC resource, then BSC apply for resource to iTC. If iTC application resource fails due to receiving iTC resource unavailability, or wrong response message, or timer timeout, then it contributes to TCH/H assignment failure and this counter will accumulate.
33-79 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-109and Figure 33-110.
Figure 33-109 Internal handover (external TC intra-cell handover, and channel types are changed) failure flow 2

Figure 33-110 External handover failure flow 2 (external TC)

Unit
Times

Related Features
l l l l l ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33-80 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.42 C901270102 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 3)
Definition
Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 3)

Description
This counter counts the number of TCH/H channel assignment failure due to TIU connection failure when allocating voice channel (use voice version 3). After BSC responds channel request message assignment and successfully occupied TCH/H channel, BSC sends TIU connection request to TIPB. If TIU connection fails due to receiving TIU connection failure, or wrong TIU connection response message, timer timeout, then this counter will accumulate.

Measurement Point
Due to allocation BSC uses TCH/H. Receive connection failure message, wrong connection response message, or timer timeout when in TIU connection. The measurement point is B2, as shown in Figure 33-111.
Figure 33-111 General Assignment Failure Flow 1 (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33-81 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.43 C901270103 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 3)
Definition
Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 3)

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 3). After BSC responds channel request message assignment and successfully occupies 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 unavailability, wrong response message, or timer timeout when in iTC application resource. The measurement point is B1, as shown in Figure 33-112.
Figure 33-112 General Assignment Failure Flow 2 (external TC)

Unit
Times

Related Features
l l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33-82 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.44 C901270104 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 3)
Definition
Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 3)

Description
This counter counts the number of TCH/H channel assignment failure due to TIU connection failure when voice channel (use voice version 3) handover. After BSC responds channel request message assignment and successfully occupies TCH/H channel, BSC sends TIU connection request to TIPB. If TIU connection fails due to receiving TIU connection failure, or wrong TIU connection response message, timer timeout, then this counter will accumulate.

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-113and Figure 33-114.
Figure 33-113 Internal handover (external TC intra-cell handover, and channel types are changed) failure flow 1

33-83 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-114 External handover flow (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33.45 C901270105 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 3)
Definition
Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 3)

Description
This counter counts the number of TCH/H channel assignment failure due to iTC application resource failure when voice channel (use voice version 3) handover. After BSC responds channel request message assignment and successfully occupies TCH/H channel, BSC applies for resource to iTC. 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.

33-84 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Measurement Point
Due to allocation BSC uses TCH/H. Receive iTC resource unavailability, wrong response message, or timer timeout when in iTC application resource. The measurement points are C1, D1, as shown in Figure 33-115 and Figure 33-116.
Figure 33-115 Internal handover (external TC intra-cell handover, and channel types are changed) failure flow 2

Figure 33-116 External handover failure flow 2 (external TC)

Unit
Times

Related Features
l l l l ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface

33-85 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.46 C901270106 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 1)
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 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/H allocation failure.

Usage
This counter is used to find out the frequency of TCH/H 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 33-117.
Figure 33-117 Request Resource Failure

Unit
Times

33-86 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.47 C901270107 Number of TCH/H allocation failure due to request UDP port failure for assignment (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 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
This counter is used to find out the frequency of TCH/H allocation failure due to request UDP port failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for assignment. The measurement point is A as shown in Figure 33-118.
Figure 33-118 Channel allocation failure

Unit
Times

33-87 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.48 C901270108 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 1)
Definition
Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 1)

Description
This counter counts the number of TCH/H 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
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for assignment. The measurement point is A as shown in Figure 33-119.
Figure 33-119 Channel allocation failure

Unit
Times

33-88 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.49 C901270109 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 1)
Definition
Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 1)

Description
This counter counts the number of TCH/H allocation failure due to request AIPB resource failure for assignment. 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/H allocation failure.

Usage
This counter is used to find out the frequency of TCH/H 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 handover and purpose is voice channel. The measurement point is A as shown in Figure 33-120.
Figure 33-120 Request Resource Failure

Unit
Times

Related Features
ZGO-03-02-011 Channel Repacking
33-89 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.50 C901270110 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 1)
Definition
Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 1)

Description
This counter counts the number of TCH/H channel allocation failure due to UDP port failure during handover. When BSC receives EV_RANUMC_RADIO_APPLY message (speech version 1), the reason to request channel is handover, to request access request for access module. This counter increments while access module returns failure and the reason is failed to request UDP port.

Usage
This counter is used to find out the frequency of TCH/H allocation failure due to request UDP port failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for handover. The measurement point is A as shown in Figure 33-121.
Figure 33-121 Channel allocation failure

Unit
Times

Related Features
ZGO-03-02-011 Channel Repacking

33-90 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.51 C901270111 Number of TCH/H allocation failure due to AIPB connection failure for handover (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 failure during handover. When BSC receives EV_RANUMC_RADIO_APPLY message (speech version 1), the reason to request channel is handover, to request access request for access module. This counter increments while access module returns failure and the reason is failed to access AIPB.

Usage
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for handover. The measurement point is A as shown in Figure 33-122.
Figure 33-122 Channel allocation failure

Unit
Times

Related Features
ZGO-03-02-011 Channel Repacking

33-91 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.52 C901270118 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 3)
Definition
Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 3)

Description
This counter counts the number of TCH/H allocation failure due to request AIPB resource failure for assignment. This counter increments while BSC receives assignment requests (speech version 3) to apply for AIPB board resource from database, failed request (including database return 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 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 33-123.
Figure 33-123 Request Resource Failure

Unit
Times

Related Features
ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)
33-92 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.53 C901270119 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 3)
Definition
Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 3)

Description
This counter counts the number of TCH/H channel allocation failure due to UDP port failure during assigning voice channel. This counter increments while BSC receives assignment requests (speech version 3), access request is sent to access module, if access module returns access failure due to UDP port request failure.

Usage
This counter is used to find out the frequency of TCH/H allocation failure due to request UDP port failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for assignment. The measurement point is A as shown in Figure 33-124.
Figure 33-124 Channel allocation failure

Unit
Times

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

33-93 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.54 C901270120 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 3)
Definition
Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 3)

Description
This counter counts the number of TCH/H channel allocation failure due to UDP port failure during assigning voice channel. This counter increments while BSC receives assignment requests (speech version 3), access request is sent to access module, if access module returns access failure due to UDP port request failure.

Usage
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for assignment. The measurement point is A as shown in Figure 33-125.
Figure 33-125 Channel allocation failure

Unit
Times

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

33-94 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.55 C901270121 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 3)
Definition
Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 3)

Description
This counter counts the number of TCH/H allocation failure due to request AIPB resource failure for assignment. This counter increments while BSC receives EV_RANUMC_RADIO_APPLY message (speech version 3), the reason to request channel is handover and request AIPB resource from database, if request AIPB fails (including database return failure or no AIPB resource), indicating TCH/H allocation failure.

Usage
This counter is used to find out the frequency of TCH/H 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 handover and purpose is voice channel. The measurement point is A as shown in Figure 33-126.
Figure 33-126 Request Resource Failure

Unit
Times

Related Features
l ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)
33-95 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ZGO-03-02-011 Channel Repacking

33.56 C901270122 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 3)
Definition
Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 3)

Description
This counter counts the number of TCH/H channel allocation failure due to UDP port failure during handover. When BSC receives EV_RANUMC_RADIO_APPLY message (speech version 3), the reason to request channel is handover, to request access request for access module. This counter increments while access module returns failure and the reason is failed to request UDP port.

Usage
This counter is used to find out the frequency of TCH/H allocation failure due to request UDP port failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for handover. The measurement point is A as shown in Figure 33-127.
Figure 33-127 Channel allocation failure

Unit
Times

Related Features
l ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)
33-96 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

ZGO-03-02-011 Channel Repacking

33.57 C901270123 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 3)
Definition
Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 3)

Description
This counter counts the number of TCH/H channel allocation failure due to AIPB access failure during handover. When BSC receives EV_RANUMC_RADIO_APPLY message (speech version 3), the reason to request channel is handover, to request access request for access module. This counter increments while access module returns failure and the reason is failed to access AIPB.

Usage
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for handover. The measurement point is A as shown in Figure 33-128.
Figure 33-128 Channel allocation failure

Unit
Times

Related Features
l ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)
33-97 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

ZGO-03-02-011 Channel Repacking

33.58 C901270124 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (data)
Definition
Number of TCH/H allocation failure due to request AIPB resource failure for assignment (data)

Description
This counter counts the number of TCH/H allocation failure due to request AIPB resource failure for assignment. 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
This counter is used to find out the frequency of TCH/H 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 33-129.
Figure 33-129 Request Resource Failure

Unit
Times

33-98 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.59 C901270125 Number of TCH/H allocation failure due to request UDP port failure for assignment (data)
Definition
Number of TCH/H allocation failure due to request UDP port failure for assignment (data)

Description
This counter counts the number of TCH/H channel allocation failure due to UDP port failure during assigning voice channel. 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
This counter is used to find out the frequency of TCH/H allocation failure due to request UDP port failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for assignment. The measurement point is A as shown in Figure 33-130.
Figure 33-130 Channel allocation failure

Unit
Times

33-99 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.60 C901270126 Number of TCH/H allocation failure due to AIPB connection failure for assignment (data)
Definition
Number of TCH/H allocation failure due to AIPB connection failure for assignment (data)

Description
This counter counts the number of TCH/H channel allocation failure due to UDP port failure during assigning voice channel. 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
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for assignment. The measurement point is A as shown in Figure 33-131.
Figure 33-131 Channel allocation failure

Unit
Times

33-100 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.61 C901270127 Number of TCH/H allocation failure due to request AIPB resource failure for handover (data)
Definition
Number of TCH/H allocation failure due to request AIPB resource failure for handover (data)

Description
This counter counts the number of TCH/H allocation failure due to request AIPB resource failure for assignment. 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/H allocation failure.

Usage
This counter is used to find out the frequency of TCH/H 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 handover and purpose is voice channel. The measurement point is A as shown in Figure 33-132.
Figure 33-132 Request Resource Failure

Unit
Times

Related Features
ZGO-03-02-011 Channel Repacking
33-101 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.62 C901270128 Number of TCH/H allocation failure 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
This counter counts the number of TCH/H channel allocation failure due to UDP port failure during handover. When BSC receives EV_RANUMC_RADIO_APPLY message (data), the reason to request channel is handover, to request access request for access module. This counter increments while access module returns failure and the reason is failed to request UDP port.

Usage
This counter is used to find out the frequency of TCH/H allocation failure due to request UDP port failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for handover. The measurement point is A as shown in Figure 33-133.
Figure 33-133 Channel allocation failure

Unit
Times

Related Features
ZGO-03-02-011 Channel Repacking

33-102 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.63 C901270129 Number of TCH/H allocation failure due to AIPB connection failure for handover (data)
Definition
Number of TCH/H allocation failure due to AIPB connection failure for handover (data)

Description
This counter counts the number of TCH/H channel allocation failure due to AIPB access failure during handover. When BSC receives EV_RANUMC_RADIO_APPLY message (data), the reason to request channel is handover, to request access request for access module. This counter increments while access module returns failure and the reason is failed to access AIPB.

Usage
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure.

Measurement Point
This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for handover. The measurement point is A as shown in Figure 33-134.
Figure 33-134 Channel allocation failure

Unit
Times

Related Features
ZGO-03-02-011 Channel Repacking

33-103 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.64 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
When the BSC CS service instance is forcibly handover, this counter counts the number of times that the released TCH/H resource is assigned to the forced handover source. The BSC CS service instance is forcibly handover to release resource, if the released TCH/H resource is assigned to the forced 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
The BSC CS service instance is forcibly handover to release resource, if the released TCH/H resource is assigned to the forced handover source, the counter accumulates.

Unit
Times

33.65 C901270131 Number of assign TCH/H release by forced handover to queuing user
Definition
Number of assign TCH/H release by forced handover to queuing user

Description
When the BSC CS service instance is forcibly handover, this counter counts the number of times that the released TCH/H resource is assigned to the queuing user. The BSC CS service instance is forcibly handover to release resource, if the released TCH/H resource is assigned to the queuing user, 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 queuing user.
33-104 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Measurement Point
The BSC CS service instance is forcibly handover to release resource, if the released TCH/H resource is assigned to the queuing user, the counter accumulates.

Unit
Times

33.66 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
When the BSC CS service instance is forcibly handover, this counter counts the number of times that the released TCH/H resource is restored to the database instead of being assigned to other users. The BSC CS service instance is forcibly handover to release resource, if the released TCH/H resource is just released instead of being assigned to other users, the counter accumulates.

Usage
This counter is used to find out the frequency of the TCH/H released by forced handover being restored to DBS.

Measurement Point
The BSC CS service instance is forcibly handover to release resource, if the released TCH/H resource is just released instead of being assigned to other users, the counter accumulates.

Unit
Times

33.67 C901270133 Number of assign TCH/H release by forced release to forced release source
Definition
Number of assign TCH/H release by forced release to forced release source
33-105 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
When the BSC CS service instance is forcibly released, this counter counts the number of times that the released TCH/H resource is assigned to the forced release source. The BSC CS service instance is forcibly released to release resource, if the released TCH/H resource is assigned to the forced 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
The BSC CS service instance is forcibly released to release resource, if the released TCH/H resource is assigned to the forced release source, the counter accumulates.

Unit
Times

33.68 C901270134 Number of assign TCH/H release by forced release to queuing user
Definition
Number of assign TCH/H release by forced release to queuing user

Description
When the BSC CS service instance is forcibly released, this counter counts the number of times that the released TCH/H resource is assigned to the queuing user. The BSC CS service instance is forcibly released to release resource, if the released TCH/H resource is assigned to the queuing user, 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 queuing user.

Measurement Point
The BSC CS service instance is forcibly released to release resource, if the released TCH/H resource is assigned to the queuing user, the counter accumulates.

Unit
Times
33-106 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.69 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 assigned to other users. The BSC CS service instance is forcibly released to release resource, if the released TCH/H resource is just released instead of being assigned to other users, the counter accumulates.

Usage
This counter is used to find out the frequency of the TCH/H released by forced release being restored to DBS.

Measurement Point
The BSC CS service instance is forcibly released to release resource, if the released TCH/H resource is just released instead of being assigned to other users, the counter accumulates.

Unit
Times

33.70 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 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.
33-107 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

33.71 C901270137 Number of signaling TCH/H seize failure for handover due to Abis lack
Description
This counter counts the number of failed signaling TCH/H seizure attempts during the process of signaling channel handover. When BSC receives the channel request, it attempts to allocate channel for the request. If the channel occupation fails due to no available Abis resource, the counter accumulates. If the request is responded with the message that no channel is available but queuing or forced release is possible, then the instance enters the queuing state. If the queuing fails, the counter accumulates. If the request 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

33.72 C901270138 Number of voice TCH/H seizure failure for assignment (cause:Abis)
Description
This counter counts the number of failed voice TCH/H 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
The counter counts when the request for channel is sent to BSC (due to assignment, used for voice channel) but the channel occupation fails or waiting for resource inside BSC fails.
33-108 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Unit
Times

33.73 C901270139 Number of voice TCH/H seizure failure for handover (cause:Abis )
Description
This counter counts the number of failed voice TCH/H seizure attempts during the process of voice channel handover. When BSC 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
The counter counts when the request for channel is sent to BSC (due to handover, used for voice channel) but the channel occupation fails or waiting for resource inside BSC fails.

Unit
Times

33.74 C901270140 Number of data TCH/H seizure failure for assignment (cause:Abis)
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 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
The counter counts when the request for channel is sent to BSC (due to assignment, used for data channel) but the channel occupation fails or waiting for resource inside BSC fails.
33-109 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

33.75 C901270141 Number of data TCH/H seizure failure for handover (cause:Abis)
Description
This counter counts the number of failed data TCH/H seizure attempts during the process of data channel handover. When BSC 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
The counter counts when the request for channel is sent to BSC (due to handover, used for data channel) but the channel occupation fails or waiting for resource inside BSC fails.

Unit
Times

33.76 C901270142 Number of signaling TCH/H seize failure for assign due to radio resource lack
Description
This counter counts the number of failed signaling TCH/H 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 radio 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
33-110 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.77 C901270143 Number of signaling TCH/H seize failure for handover due to radio resource lack
Description
This counter counts the number of failed signaling TCH/H seizure attempts during the process of signaling channel handover. When BSC receives the channel request, it attempts to allocate channel for the request. If the channel occupation fails due to no available radio 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
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

33.78 C901270144 Number of voice TCH/H seizure failure for assignment (cause:radio resource)
Description
This counter counts the number of failed voice TCH/H 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 radio 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
The counter counts when the request for channel is sent to BSC (due to assignment, used for voice channel) but the channel occupation fails or waiting for resource inside BSC fails.

Unit
Times
33-111 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.79 C901270145 Number of voice TCH/H seizure failure for handover (cause:radio resource)
Description
This counter counts the number of failed voice TCH/H seizure attempts during the process of voice channel handover. When BSC receives the channel request, it attempts to allocate channel for the request. If the channel occupation fails due to no available radio 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
The counter counts when the request for channel is sent to BSC (due to handover, used for voice channel) but the channel occupation fails or waiting for resource inside BSC fails.

Unit
Times

33.80 C901270146 Number of data TCH/H seizure failure for assignment (cause:radio resource)
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 allocate channel for the request. If the channel occupation fails due to no available radio resource, the counter accumulates. If the request is responded with the message that no channel is available but queuing 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
The counter counts when the request for channel is sent to BSC (due to assignment, used for data channel) but the channel occupation fails or waiting for resource inside BSC fails.

Unit
Times
33-112 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.81 C901270147 Number of data TCH/H seizure failure for handover (cause:radio resource)
Description
This counter counts the number of failed data TCH/H seizure attempts during the process of data 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 radio 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
The counter counts when the request for channel is sent to BSC (due to handover, used for data channel) but the channel occupation fails or waiting for resource inside BSC fails.

Unit
Times

33.82 C901270148 Number of HR_V1 assignment attempts

Description
This counter counts the number of attempts of assigning TCH/H 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/H. For the assignment from A-interface, this counter and C901270149 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
33-113 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.83 C901270149 Number of HR_V1 assignment success

Description
This counter counts the number of successes of assigning TCH/H 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/H. For the assignment from A-interface, this counter accumulates after the assignment success message is received.

Measurement Point
For the assignment from A-interface, this counter accumulates after BSC receives the assignment success message.

Unit
Times

33.84 C901270150 Number of HR_V3 assignment attempts

Description
This counter counts the number of attempts of assigning TCH/H of voice version 3 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/H. For the assignment from A-interface, this counter and C901270151 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

33-114 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.85 C901270151 Number of HR_V3 assignment success

Description
This counter counts the number of successes of assigning TCH/H of voice version 3 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/H. For the assignment from A-interface, this counter accumulates after the assignment success message is received.

Measurement Point
For the assignment from A-interface, this counter accumulates after BSC receives the assignment success message.

Unit
Times

33.86 C901270152 Number of HR_V1 handover

Description
This counter counts the number of handover attempts that the destination voice channel is of half-rate voice version 1. During handover, after MS is successfully accessed on the new channel, BSC 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 C901270153 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
33-115 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.87 C901270153 Number of HR_V1 handover success

Description
This counter counts the number of successful handovers that the destination voice channel is of half-rate voice version 1. This counter accumulates when BSC detects the handover success message sent from MS on the newly allocated TCH/H channel. For intra-cell handover, the handover success message is ASS_COM; for inter-cell handover and external handover, the handover success message is HO_COM. For intra-cell handover and inter-cell handover, the counter accumulates on the basis of source instances. For external handover, because the source instance is not at the BSC, the counter accumulates on the basis of destination instances.

Measurement Point
The counter counts when BSC receives the ASS_COM message or the HO_COM message.

Unit
Times

33.88 C901270154 Number of HR_V3 handover

Description
This counter counts the number of handover attempts that the destination voice channel is of half-rate voice version 3. During handover, after MS is successfully accessed on the new channel, BSC 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 C901270155 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.

33-116 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Unit
Times

33.89 C901270155 Number of HR_V3 handover success

Description
This counter counts the number of successful handovers that the destination voice channel is of half-rate voice version 3. This counter accumulates when BSC detects the handover success message sent from MS on the newly allocated TCH/H channel. For intra-cell handover, the handover success message is ASS_COM; for inter-cell handover and external handover, the handover success message is HO_COM. For intra-cell handover and inter-cell handover, the counter accumulates on the basis of source instances. For external handover, because the source instance is not at the BSC, the counter accumulates on the basis of destination instances.

Measurement Point
The counter counts when BSC receives the ASS_COM message or the HO_COM message.

Unit
Times

33.90 C901270177 Resource releasing of ordinary users due to being grabbed (TCH/H)
Description
This counter counts the number of ordinary user's call on TCH/H being released due to resource being preempted. After the ordinary user obtains TCH/H, call drop occurs. If the problem is caused by high-priority user's preempting resource, the counter increments.

Usage
This counter is used to find out the number of ordinary user's call on TCH/H being released due to high-priority user's preempting resource. This counter is supported in version V6.20.61 or later.

Measurement Point
After the ordinary user obtains TCH/H, if the forced release message from other call is received, the counter counts. The measurement point is A, as shown in Figure 33-135.

33-117 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-135 Resource releasing of ordinary users due to being grabbed (TCH/H)

Unit
Times

33.91 C901270178 Handover of ordinary users due to being grabbed (TCH/H)

Description
This counter counts the number of handovers performed for ordinary user's call on TCH/H due to resource being preempted. After the ordinary user obtains TCH/H, handover is performed due to no available resource under the BSC. If the problem is caused by high-priority user's preempting resource, the counter increments.

33-118 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Usage
This counter is used to find out the number of handovers performed for ordinary user's call on TCH/H due to high-priority user's preempting resource. This counter is supported in version V6.20.61 or later.

Measurement Point
After the ordinary user obtains TCH/H, if the forced handover message is received, the counter counts. The measurement point is A, as shown in Figure 33-136.
Figure 33-136 Handover of ordinary users due to being grabbed (TCH/H)

Unit
Times

33-119 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.92 C901270179 Number of Channel Request of priority users (TCH/H)

Description
This counter counts the number of requesting for TCH/H by high-priority users. After BSC receives the channel request, it attempts to allocate channel for the request. If the channel request is initiated by high-priority user, the counter increments.

Usage
This counter is used to find out the number of requesting for TCH/H by high-priority users. This counter is supported in version V6.20.61 or later.

Measurement Point
When the high-priority user requests for TCH/H, the counter counts. The measurement point is A, as shown in Figure 33-137, Figure 33-138, and Figure 33-139.
Figure 33-137 Flow of Occupying TCH/F during Assignment

Figure 33-138 Flow of Occupying TCH/F during Inter-BSC Handover

Figure 33-139 Flow of Occupying TCH/F during Intra-BSC Handover

33-120 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Unit
Times

33.93 C901270180 Number of Successful Channel seize of priority users (TCH/H)

Description
This counter counts the number of high-priority users' requesting for TCH/H successfully. After BSC receives the channel request, it attempts to allocate channel for the request. If the channel request is initiated by high-priority user and the channel is obtained successfully, the counter increments.

Usage
This counter is used to find out the number of high-priority users' requesting for TCH/H successfully. This counter is supported in version V6.20.61 or later.

Measurement Point
When the high-priority user requests for TCH/H, if the channel is obtained successfully, the counter counts. The measurement point is A, as shown in Figure 33-140, Figure 33-141, and Figure 33-142.
Figure 33-140 Flow of Occupying TCH/F during Assignment

Figure 33-141 Flow of Occupying TCH/F during Inter-BSC Handover

33-121 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-142 Flow of Occupying TCH/F during Intra-BSC Handover

Unit
Times

33.94 C901270181 Number of Successful grabbing channel of priority users (TCH/H)

Description
When the high-priority user requests for TCH/H, this counter counts the number of high-priority user's successfully preempting resource from the ordinary user due to no available resource in the system. After BSC receives the channel request, it attempts to allocate channel for the request. If the request is initiated by high-priority user but there is no available resource, the system initiates the flow of preempting resource from ordinary user. If the resource is preempted successfully, the counter increments.

Usage
This counter is used to find out the number of high-priority user's preempting resource from ordinary user successfully. This counter is supported in version V6.20.61 or later.

Measurement Point
When high-priority user requests for TCH/H but there is no available resource, if high-priority user preempts resource from ordinary user successfully, the counter counts. The measurement point is A, as shown in Figure 33-143, Figure 33-144, and Figure 33-145.
Figure 33-143 Flow of Occupying TCH/F during Assignment

33-122 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-144 Flow of Occupying TCH/F during Inter-BSC Handover

Figure 33-145 Flow of Occupying TCH/F during Intra-BSC Handover

Unit
Times

33.95 C901270182 Number of HR_V4 Assignment Attempts

Description
This counter counts the attempts that occur to assign a voice TCH/H channel (speech version 4). Upon receiving a channel request message, the BSC responds to the message with a TCH/H allocated and occupied. After that, the BSC sends a CHL_ACT message to the BTS for activating the TCH/H. In the case of assignment request from A interface, this counter and counter C901270183 are incremented when an assignment complete message is received. If no attaching message is received from the MS during the required time, this assignment fails and this counter is incremented.

Measurement Point
This counter is incremented when the BSC receives an assignment complete message, an assignment failure message, a timer expiry message, or an unexpected message, or the channel instance is released or forcibly disconnected.

Unit
Times

33-123 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

33.96 C901270183 Number of HR_V4 Assignment Success

Description
This counter counts successful assignments of voice TCH/H channel (speech version 4). Upon receiving a channel request message, the BSC responds to the message with a TCH/H allocated and occupied. After that, the BSC sends a CHL_ACT message to the BTS for activating the TCH/H. In the case of assignment request from A interface, this counter is incremented when an assignment complete message is received.

Measurement Point
This counter is incremented when an assignment complete message is received.

Unit
Times

33.97 C901270184 Number of HR_V4 Handover

Description
This counter counts the handover attempts that occur to hand over an MS to a voice TCH/H (speech version 4). When the MS is successfully attached to the target voice TCH/H channel, the BSC receives an ASS_COM message (intra-cell handover), or an HO_COM message (inter-cell handover or external handover). When the BSC receives the ASS_COM or HO_COM message within the required time, which indicates that the handover succeeds, this counter and counter C901270185 are incremented. When the BSC receives an HO_FAILURE message, which indicates a responded handover failure, this counter is incremented. When the handover fails but the BSC does not receive an HO_FAILURE message, which indicates a un-responded handover failure, this counter is incremented. In the case of intra-cell handover or inter-cell handover, the counter corresponding to the source instance is incremented. In the case of external handover, the counter corresponding to the target instance is incremented because the source instance is not in the local BSC.

Measurement Point
This counter is incremented when the BSC receives an ASS_COM, HO_COM, ASS_FAIL, HO_FAIL, or an unexpected message, the instance is released or forcibly disconnected, or the corresponding timer expires.

33-124 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Unit
Times

33.98 C901270185 Number of HR_V4 Handover Success

Description
This counter counts the successes of handover to a voice TCH/H (speech version 4). When the BSC receives a message indicating the handover success from the MS through the allocated TCH/H, this counter is incremented. In the case of intra-cell handover, the ASS_COM message indicates the handover success. In the case of inter-cell or external handover, the HO_COM message indicates the handover success. In the case of intra-cell handover or inter-cell handover, the counter corresponding to the source instance is incremented. In the case of external handover, the counter corresponding to the target instance is incremented because the source instance is not in the local BSC.

Measurement Point
This counter is incremented when the BSC receives an ASS_COM or HO_COM message.

Unit
Times

33.99 C901270186 Number of TCH/H Allocation Attempts for Assignment (Speech Version 4)
Definition
Number of TCH/H allocation attempts for assignment (speech version 4)

Description
This counter counts the allocation attempts that occur to allocate a voice TCH/H (speech version 4) for assignment. The allocation attempts include both successful allocation attempts (C901270187) and failed allocation attempts (C901270188+C901270189+C901270194+C901270195+C901270196). Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/H allocated and occupied. After that, the BSC completes the connection, and then sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/H. The BTS sends a CHL_ACT_ACK message to the BSC after the channel is successfully activated. When the TCH/H allocation succeeds
33-125 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

with a CHL_ACT_ACK message received, this counter and counter C901270187 are incremented. When the TCH/H allocation fails, this counter and the counter corresponding to the failure reason are incremented.

Measurement Point
This counter is incremented each time a voice TCH/H allocation attempt (speech version 4) for assignment succeeds or fails. The measurement point is B2 in the case of internal transcoder (TCU), or B3 in the case of external transcoder (iTC), as shown in Figure 33-146 and Figure 33-147.
Figure 33-146 General Assignment Procedure (Internal TC)

Figure 33-147 General Assignment Procedure (External TC)

Unit
Times

33-126 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33.100 C901270187 Number of TCH/H Allocation Success for Assignment (Speech Version4)
Definition
Number of successful TCH/H allocations (speech version 4) for assignment

Description
This counter counts successful TCH/H allocation attempts that occur to allocate a voice TCH/H (speech version 4) for assignment. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/H allocated and occupied. After that, the BSC sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/H. The BTS sends a CHL_ACT_ACK message to the BSC after the channel is successfully activated. When the TCH/H allocation succeeds with a CHL_ACT_ACK message received, this counter is incremented.

Measurement Point
This counter is incremented each time the BSC receives a CHL_ACT_ACK message from the BTS in the case of TCH/H allocation (speech version 4) for assignment. The measurement point is B3, as shown in Figure 33-148 and Figure 33-149.
Figure 33-148 General Assignment Procedure (Internal TC)

33-127 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-149 General Assignment Procedure (External TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33.101 C901270188 Number of TCH/H Allocation Failure Due to Channel Activation Failure for Assignment (Speech Version 4)
Definition
Number of failed TCH/H allocations (speech version 4) for assignment due to channel activation failure

Description
This counter counts TCH/H allocation failures due to channel activation failure during voice channel allocation (speech version 4) for assignment. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/H allocated and occupied. After that, the BSC completes the connection, and then sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/H. When the channel activation fails, this counter is incremented. The BSC considers the channel activation failed when the ChannelActivationNack message is received, the ChannelActivationAck message is not received, the timer T9103 expires, the channel instance is released, or the channel is forcibly disconnected.

33-128 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Measurement Point
This counter is incremented each time the TCH/H allocation fails due to channel activation failure during the channel allocation (speech version 4) for assignment. The measurement point is B3, as shown in Figure 33-150.
Figure 33-150 Assignment Failure 1 (Internal TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33.102 C901270189 Number of TCH/H Allocation Failure Due to BIU Connection Failure for Assignment (Speech Version 4)
Definition
Number of failed TCH/H allocations (speech version 4) for assignment due to BIU connection failure

Description
This counter counts TCH/H allocation failures due to BIU connection failure during voice channel allocation (speech version 4) for assignment. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/H allocated and occupied. After that, the BSC sends a BIU connection request to the BIPB. When the BIU connection fails, this counter is incremented. The BSC considers the BIU connection failed when the BIU connection non-acknowledgement message is received, the BIU connection acknowledgement message is not received, or the corresponding timer expires.
33-129 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the TCH/H allocation fails due to BIU connection failure during the voice channel allocation (speech version 4) for assignment. The measurement point is B2, as shown in Figure 33-151.
Figure 33-151 Assignment Failure 3 (Internal TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33.103 C901270190 Number of TCH/H Allocation Attempts by BSC for Handover (Speech Version 4)
Definition
Number of TCH/H allocation attempts for handover (speech version 4)

Description
This counter counts the TCH/H allocation attempts that occur to allocate a full rate voice channel (speech version 4) for handover. The allocation attempts include both successful allocation attempts (C901270191) and failed allocation attempts (C901270192+C9012701913+C901270197+C901270198+C901270199). Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/H allocated and occupied. After that, the BSC completes the connection, and then sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/H. The BTS sends a CHL_ACT_ACK message to the BSC after the channel is successfully activated. When the TCH/H allocation succeeds with a CHL_ACT_ACK message received, this counter and counter C901270191 are incremented. When the TCH/H allocation fails, this counter and the counter corresponding to the failure reason are incremented.

33-130 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Measurement Point
This counter is incremented each time a TCH/H allocation attempt succeeds or fails during the voice channel allocation (speech version 4) for handover. The measurement point varies with different handover procedures and transcoders. In an internal handover (intra-BSC handover), the measurement point is C3, as shown in Figure 33-152 and Figure 33-153. In an external handover (inter-BSC handover), the measurement point is D3, as shown in Figure 33-154 and Figure 33-155.
Figure 33-152 Internal Handover Procedure - Intra-Cell Handover (Internal TC)

Figure 33-153 Internal Handover Procedure - Intra-Cell Handover with Channel Type Changed (External TC)

33-131 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-154 External Handover Procedure (Internal TC)

Figure 33-155 External Handover Procedure (External TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33-132 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.104 C901270191 Number of TCH/H Allocation Success by BSC for Handover (Speech Version 4)
Definition
Number of successful TCH/H allocations for handover (speech version 4)

Description
This counter counts successful TCH/H allocation attempts that occur to allocate a voice TCH/H (speech version 4) for handover. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/H allocated and occupied. After that, the BSC sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/H. The BTS sends a CHL_ACT_ACK message to the BSC after the channel is successfully activated. When the TCH/H allocation succeeds with a CHL_ACT_ACK message received, this counter is incremented.

Measurement Point
This counter is incremented each time the BSC receives a CHL_ACT_ACK message from the BTS in the case of TCH/H allocation (speech version 4) for handover. The measurement point varies with different handover procedures and transcoders. In an internal handover (intra-BSC handover), the measurement point is C3, as shown in Figure 33-156 and Figure 33-157. In an external handover (inter-BSC handover), the measurement point is D3, as shown in Figure 33-158 and Figure 33-159.
Figure 33-156 Internal Handover Procedure - Intra-Cell Handover (Internal TC)

33-133 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-157 Internal Handover Procedure - Intra-Cell Handover with Channel Type Changed (External TC)

Figure 33-158 External Handover Procedure (Internal TC)

33-134 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Figure 33-159 External Handover Procedure (External TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33.105 C901270192 Number of TCH/H Allocation Failure Due to Channel Activation Failure for Handover (Speech Version 4)
Definition
Number of failed TCH/H allocations (speech version 4) for handover

Description
This counter counts TCH/H allocation failures due to channel activation failure during voice TCH/H allocation (speech version 4) for handover. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/H allocated and occupied. After that, the BSC completes the connection, and then sends a channel activation (CHL_ACT) message to the BTS to activate the TCH/H. When the channel activation fails, this counter is incremented. The BSC considers the channel activation failed when the ChannelActivationNack message is received, the ChannelActivationAck message is not received, the timer T9103 expires, the channel instance is released, or the channel is forcibly disconnected.

33-135 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the TCH/H allocation fails due to channel activation failure during the channel allocation (speech version 4) for handover. The measurement point varies with different handover procedures and transcoders. In an internal handover (intra-BSC handover), the measurement point is C3, as shown in Figure 33-160. In an external handover (inter-BSC handover), the measurement point is D3, as shown in Figure 33-161.
Figure 33-160 Internal Handover Failure 1 - Intra-Cell Handover (Internal TC)

Figure 33-161 External Handover Failure 2 (Internal TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33-136 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

33.106 C901270193 Number of TCH/H Allocation Failure Due to BIU Connection Failure for Handover (Speech Version 4)
Definition
Number of failed TCH/H allocations (speech version 4) for handover due to BIU connection failure

Description
This counter counts TCH/H allocation failures due to BIU connection failure during voice channel allocation (speech version 4) for assignment. Upon receiving an assignment request (ASS_REQ) message, the BSC responds to the message with a TCH/H allocated and occupied. After that, the BSC sends a BIU connection request to the BIPB. When the BIU connection fails, this counter is incremented. The BSC considers the BIU connection failed when the BIU connection non-acknowledgement message is received, the BIU connection acknowledgement message is not received, or the corresponding timer expires.

Measurement Point
This counter is incremented each time the TCH/H allocation fails due to BIU connection failure during the voice channel allocation (speech version 4) for handover. The measurement point varies with different handover procedures and transcoders. In an internal handover (intra-BSC handover), the measurement point is C2, as shown in Figure 33-162. In an external handover (inter-BSC handover), the measurement point is D2, as shown in Figure 33-163.
Figure 33-162 Internal Handover Failure 2 - Intra-Cell Handover (Internal TC)

33-137 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 33-163 External Handover Failure 3 (Internal TC)

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33.107 C901270194 Number of TCH/H Allocation Failure Due to Request AIPB Resource Failure for Assignment (Speech Version 4)
Definition
Number of failed TCH/H allocations (speech version 4) for assignment due to AIPB resource request failure

Description
This counter counts the TCH/H allocation failures due to failed request for AIPB resource during voice channel allocation for assignment. Upon receiving a assignment request (speech version 4) message, the BSC sends a request for AIPB resource to the database. If the database responds with a message of non-acknowledgement or no available AIPB resource, the BSC considers the AIPB resource request failed. This counter is incremented when the TCH/H allocation fails due to the AIPB resource request failure.

Usage
This counter reflects the frequency that TCH/H allocation fails due to AIPB resource request failure.

33-138 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Measurement Point
This counter is incremented each time the BSC receives a non-acknowledgement or no available AIPB resource message from the database during TCH/H allocation (speech version 4) for assignment. The measurement point is A, as shown in Figure 33-164.
Figure 33-164 Resource Request Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33.108 C901270195 Number of TCH/H Allocation Failure Due to Request UDP Port Failure for Assignment (Speech Version 4)
Definition
Number of failed TCH/H allocations (speech version 4) for assignment due to UDP port request failure

Description
This counter counts TCH/H allocations that fail due to UDP port request failure during voice channel allocation for assignment. Upon receiving the assignment request (speech version 4) message, the BSC sends a connection request to the connection module. If the connection module responds with a connection failure message, which indicates that the failure reason is UDP port request failure, this counter is incremented.

Usage
This counter reflects the frequency that TCH/H allocation fails due to UDP port request failure.
33-139 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the BSC receives an EV_RANCONN_IPA_CONN_NACK message from the connection module, which indicates that the failure reason is UDP port request failure, during TCH/H allocation for assignment. The measurement point is A, as shown in Figure 33-165.
Figure 33-165 Channel Allocation Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33.109 C901270196 Number of TCH/H Allocation Failure Due to AIPB Connection Failure for Assignment (Speech Version 4)
Definition
Number of failed TCH/H allocations (speech version 4) for assignment due to AIPB connection failure

Description
This counter counts TCH/H allocations that fail due to AIPB connection failure during voice channel allocation for assignment. Upon receiving the assignment request (speech version 4) message, the BSC sends a connection request to the connection module. If the connection module responds with a connection failure message, which indicates that the failure reason is AIPB connection failure, this counter is incremented.

Usage
This counter reflects the frequency that TCH/H allocation fails due to AIPB connection failure.
33-140 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

Measurement Point
This counter is incremented each time the BSC receives an EV_RANCONN_IPA_CONN_NACK message (indicating the failure reason is AIPB connection failure) from the connection module or the TwaitConn timer expires during TCH/H allocation for assignment. The measurement point is A, as shown in Figure 33-166.
Figure 33-166 Channel Allocation Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33.110 C901270197 Number of TCH/H Allocation Failure Due to Request AIPB Resource Failure for Handover (Speech Version 4)
Definition
Number of failed TCH/H allocations (speech version 4) for handover due to AIPB resource request failure

Description
This counter counts TCH/H allocations that fail due to AIPB resource request failure during voice channel allocation for handover. Upon receiving an EV_RANUMC_RADIO_APPLY message during the voice channel allocation (speech version 4) for handover, the BSC sends a request for AIPB resource to the database. If the database responds with a request non-acknowledgement or no available AIPB resource message, the request for AIPB resource fails, which results in TCH/H allocation failure. This counter is incremented when the TCH/H allocation fails due to AIPB resource request failure.

33-141 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter reflects the frequency that TCH/H allocation fails due to AIPB resource request failure.

Measurement Point
This counter is incremented each time the BSC receives a request non-acknowledgement or no available AIPB resource message from the database during TCH/H allocation (speech version 4) for handover. The measurement point is A, as shown in Figure 33-167.
Figure 33-167 Resource Request Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33.111 C901270198 Number of TCH/H Allocation Failure Due to Request UDP Port Failure for Handover (Speech Version 4)
Definition
Number of failed TCH/H allocations (speech version 4) for handover due to UDP port request failure

Description
This counter counts TCH/H allocations that fail due to UDP port request failure during voice channel allocation for handover. Upon receiving an EV_RANUMC_RADIO_APPLY message during the voice channel allocation (speech version 4) for handover, the BSC sends a connection request to the connection module. If the connection module responds with a connection failure
33-142 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 33 TCH/H Measurement

message, which indicates that the failure reason is UDP port request failure, this counter is incremented.

Usage
This counter reflects the frequency that TCH/H allocation fails due to UDP port request failure.

Measurement Point
This counter is incremented each time the BSC receives an EV_RANCONN_IPA_CONN_NACK message from the connection module, which indicates that the failure reason is UDP port request failure, during TCH/H allocation for handover. The measurement point is A, as shown in Figure 33-168.
Figure 33-168 Channel Allocation Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33.112 C901270199 Number of TCH/H Allocation Failure Due to AIPB Connection Failure for Handover (Speech Version 4)
Definition
Number of failed TCH/H allocations (speech version 4) for handover due to AIPB connection failure

Description
This counter counts TCH/H allocations that fail due to AIPB connection failure during voice channel allocation for handover. Upon receiving an EV_RANUMC_RADIO_APPLY message during the voice channel allocation (speech version 4) for handover, the BSC sends a connection request to
33-143 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

the connection module. If the connection module responds with a connection failure message, which indicates that the failure reason is AIPB connection failure, this counter is incremented.

Usage
This counter reflects the frequency that TCH/H allocation fails due to AIPB connection failure.

Measurement Point
This counter is incremented each time the BSC receives an EV_RANCONN_IPA_CONN_NACK message (indicating the failure reason is AIPB connection failure) from the connection module or the TwaitConn timer expires during TCH/H allocation for handover. The measurement point is A, as shown in Figure 33-169.
Figure 33-169 Channel Allocation Failure

Unit
Times

Related Feature
ZGO-01-01-004 Adaptive Multi-Rate WideBand (AMR-WB)

33-144 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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-6 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-32 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-36 C901280040 Number of ABIS_IMM_ASSIGN_CMD messages .............................34-37 C901280041 Number of ABIS_SMS_BROADCAST_REQ messages ....................34-38 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-42 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-45 C901280051 Number of ABIS_OVERLOAD messages ..........................................34-46 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-49 C901280056 Number of ABIS_PWRCTRL_IND messages ....................................34-50 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-52 C901280063 Number of ABIS_PACKET_PBCCH_PARA messages ......................34-53 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-56 C901280068 Number of ABIS_PACKET_PRACH_OVERLOAD messages ............34-57 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-59 C901280072 Number of ABIS_PACKET_CHN_CONFIG_CHG messages.............34-60 C901280073 Number of ABIS_PACKET_CHN_CONFIG_CHG_RESP messages .34-61 C901280074 Number of ABIS_PACKET_PIA_DEL_IND messages .......................34-62 C901280075 Number of ABIS_PACKET_SEND_PIA_IND messages ....................34-62 C901280076 Number of ABIS_PACKET_CHN_CONFIG_REQ messages .............34-63 C901280077 Number of ABIS_EGPRS_PACKET_CHN_REQ messages ..............34-64 C901280078 Number of ABIS_PS_CHANNEL_ACTIVE messages .......................34-65
34-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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-67 C901280082 Number of ABIS_PS_CHANNEL_RELEASE_ACK messages...........34-68 C901280083 Number of ABIS_PS_CHANNEL_RELEASE_NACK messages ........34-69 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-71 C901280087 Number of ABIS_GLOBAL_RESET messages..................................34-72 C901280088 Number of ABIS_GLOBAL_RESET_ACK messages.........................34-73 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-75 C901280092 Number of ABIS_CSCONN_CMM_REQ messages ..........................34-76 C901280093 Number of ABIS_CSCONN_CMM_ACK messages...........................34-77 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-79 C901280097 Number of ABIS_CCMCONN_CMM_NACK messages .....................34-80 C901280098 Number ABIS_PACKET_ACCESS_REJ messages...........................34-81 C901280099 Number of ABIS_PACKET_IMM_ASSIGN_CMD_NEW messages....34-82 C901280100 Number of PACKET_DOWNLINK_ASSIGN messages......................34-82 C901280101 Number of PACKET_UPLINK_ASSIGN messages............................34-83 C901280102 Number of ABIS_PACKET_ACCESS_REJ_NEW messages.............34-84 C901280105 Peak of CS Paging Messages From CN............................................34-85 C901280106 Peak of CS Paging Messages From SGSN .......................................34-86 C901280107 Peak of PS Paging Messages From SGSN .......................................34-86 C901280108 Peak of Paging Messages.................................................................34-87 C901280109 Time of Paging reached the threshold ...............................................34-87

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.

34-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A, as shown in Figure 34-2.
Figure 34-2 Measurement Point when BSC Sends Abis Message to BTS

The measurement takes cell as the statistics unit.

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 measurement point is A, as shown in Figure 34-3.

34-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Figure 34-3 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

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. measurement point is A, as shown in Figure 34-4.
Figure 34-4 BTS sends measurement point of Abis message to BSC

The

34-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

34.4 C901280003 Number of ERROR INDICATION messages

Definition
Number of ERROR INDICATION messages

Description
When radio channel generates errors (for example radio link fault), BTS sends ERROR INDication message to notify BSC. This counter counts the number of ERROR INDication messages of Abis 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. measurement point is A, as shown in Figure 34-5.
Figure 34-5 BTS sends measurement point of Abis message to BSC

The

Unit
Times

34.5 C901280004 Number of ESTABLISH REQUEST messages

Definition
Number of ESTABLISH REQUEST messages
34-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

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.

Measurement Point
This counter increments when BSC sends Establish Request message to BTS. The measurement point is A, as shown in Figure 34-6.
Figure 34-6 Measurement Point when BSC Sends Abis Message to BTS

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.
34-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter increments when BSC receives Establish Confirm message. measurement point is A, as shown in Figure 34-7.
Figure 34-7 BTS sends measurement point of Abis message to BSC

The

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 messages of Abis interface messages received by BSC.

Usage
This counter is used to find out the frequency of Establish Indication messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives Establish Indication message. measurement point is A, as shown in Figure 34-8. The

34-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Figure 34-8 BTS sends measurement point of Abis message to BSC

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 measurement point is A, as shown in Figure 34-9.
Figure 34-9 Measurement Point when BSC Sends Abis Message to BTS

34-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

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 messages of Abis interface messages received by BSC.

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. measurement point is A, as shown in Figure 34-10.
Figure 34-10 BTS sends measurement point of Abis message to BSC

The

Unit
Times

34.10 C901280009 Number of RELEASE INDICATION messages

Definition
Number of RELEASE INDICATION messages
34-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

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 messages of Abis interface messages received by BSC.

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. measurement point is A, as shown in Figure 34-11.
Figure 34-11 BTS sends measurement point of Abis message to BSC

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 transmitting on Abis interface.
34-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter increments when BSC sends UNIT DATA REQUEST messages to BTS. The measurement point is A, as shown in Figure 34-12.
Figure 34-12 Measurement Point when BSC Sends Abis Message to BTS

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives UNIT DATA INDICATION messages. The measurement point is A, as shown in Figure 34-13.

34-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Figure 34-13 BTS sends measurement point of Abis message to BSC

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends CHANNEL ACTIVATION messages. The measurement point is A, as shown in Figure 34-14.
Figure 34-14 Measurement Point when BSC Sends Abis Message to BTS

34-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

34.14 C901280013 Number of CHANNEL ACTIVATION ACK messages

Definition
Number of CHANNEL ACTIVATION ACK messages

Description
After BSC finishes activating channel, it sends CHANNEL ACTIVATION ACK message to BSC as the response of channel activation message. This counter counts the number of CHANNEL ACTIVATION ACK messages of Abis interface messages received by BSC.

Usage
This counter is used to find out the frequency of CHANNEL ACTIVATION ACK messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives CHANNEL ACTIVATION ACK messages. The measurement point is A, as shown in Figure 34-15.
Figure 34-15 BTS sends measurement point of Abis message to BSC

Unit
Times

34.15 C901280014 Number of CHANNEL ACTIVATION Negative ACK messages

Definition
Number of CHANNEL ACTIVATION Negative ACK messages
34-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

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.
Figure 34-16 BTS sends measurement point of Abis message to BSC

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of CONNECTION FAILURE INDICATION messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives CONNECTION FAILURE INDICATION messages. The measurement point is A, as shown in Figure 34-17.
Figure 34-17 BTS sends measurement point of Abis message to BSC

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives DEACTIVATE SACCH messages. The measurement point is A, as shown in Figure 34-18.

34-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Figure 34-18 Measurement Point when BSC Sends Abis Message to BTS

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ENCRYPTION COMMAND messages to BTS. The measurement point is A, as shown in Figure 34-19.
Figure 34-19 Measurement Point when BSC Sends Abis Message to BTS

34-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives HANDOVER DETCTION messages. The measurement point is A, as shown in Figure 34-20.
Figure 34-20 BTS sends measurement point of Abis message to BSC

Unit
Times

34-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives MEASUREMENT RESULTS messages. The measurement point is A, as shown in Figure 34-21.
Figure 34-21 BTS sends measurement point of Abis message to BSC

Unit
Times

34-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends MODE MODIFY REQUEST messages to BTS. The measurement point is A, as shown in Figure 34-22.
Figure 34-22 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.22 C901280021 Number of MODE MODIFY ACK messages

Definition
Number of MODE MODIFY ACK messages
34-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives MODE MODIFY ACK messages. measurement point is A, as shown in Figure 34-23.
Figure 34-23 BTS sends measurement point of Abis message to BSC

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 interface messages received by BSC.

Usage
This counter is used to find out the frequency of MODE MODIFY NACK messages transmitting on Abis interface.
34-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter increments when BSC receives MODE MODIFY NACK messages. The measurement point is A, as shown in Figure 34-24.
Figure 34-24 BTS sends measurement point of Abis message to BSC

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 messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends PHYSICAL CONTEXT REQUEST messages to BTS. The measurement point is A, as shown in Figure 34-25.

34-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Figure 34-25 Measurement Point when BSC Sends Abis Message to BTS

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 interface messages received by BSC.

Usage
This counter is used to find out the frequency of PHYSICAL CONTEXT COMFIRM messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives PHYSICAL CONTEXT COMFIRM messages to BTS. The measurement point is A, as shown in Figure 34-26.
Figure 34-26 BTS sends measurement point of Abis message to BSC

34-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends RF CHANNEL RELEASE messages to BTS. The measurement point is A, as shown in Figure 34-27.
Figure 34-27 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends MS POWER CONTROL messages to BTS. The measurement point is A, as shown in Figure 34-28.
Figure 34-28 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.28 C901280027 Number of BS POWER CONTROL messages

Definition
Number of BS POWER CONTROL messages
34-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
BSC can calculate the proper transmitting power used by BTS side according to measurement data result. Therefore it notifies control parameters to BTS through BS POWER CONTROL messages. BTS conducts the corresponding transmission power adjustment work immediately. This counter counts the number of BS POWER CONTROL messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of BS POWER CONTROL messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends BS POWER CONTROL messages to BTS. The measurement point is A, as shown in Figure 34-29.
Figure 34-29 Measurement Point when BSC Sends Abis Message to BTS

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

basic control parameters being processed. This counter counts the number of PREPROCESSED CONFIGURE messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of PREPROCESSED CONFIGURE messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends PREPROCESSED CONFIGURE messages to BTS. The measurement point is A, as shown in Figure 34-30.
Figure 34-30 Measurement Point when BSC Sends Abis Message to BTS

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 34-31 BTS sends measurement point of Abis message to BSC

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives RF CHANNEL RELEASE ACK messages to BTS. The measurement point is A, as shown in Figure 34-32.

34-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Figure 34-32 BTS sends measurement point of Abis message to BSC

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends SACCH INFO MODIFY messages to BTS. The measurement point is A, as shown in Figure 34-33.

34-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 34-33 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.33 C901280032 Number of ABIS_PREPROC_ENHANCEMEAS_RESULT messages

Definition
Number of ABIS_PREPROC_ENHANCEMEAS_RESULT messages

Description
This counter counts the number of ABIS_PREPROC_ENHANCEMEAS_RESULT messages received by BSC.

Usage
This counter is used to find out the frequency of enhanced preprocessed measurement report message transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_PREPROC_ENHANCEMEAS_RESULT messages. The measurement point is A, as shown in Figure 34-34.

34-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Figure 34-34 BTS sends measurement point of Abis message to BSC

Unit
Times

34.34 C901280033 Number of ABIS_ROUND_TRIP_DELAY_REPORT messages

Definition
Number of ABIS_ROUND_TRIP_DELAY_REPORT messages

Description
This counter counts the number of ABIS_ROUND_TRIP_DELAY_REPORT messages received by BSC.

Usage
This counter is used to find out the frequency of ROUND TRIP DELAY REPORT messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ROUND TRIP DELAY REPORT messages. The measurement point is A, as shown in Figure 34-35.
Figure 34-35 BTS sends measurement point of Abis message to BSC

34-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

34.35 C901280034 Number of ABIS_PRE_HO_NOTIFY messages

Definition
Number of ABIS_PRE_HO_NOTIFY messages

Description
This counter counts the number of ABIS_PRE_HO_NOTIFY messages received by BSC.

Usage
This counter is used to find out the frequency of PRE_HO_NOTIFY messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends PRE-HANDOVER NOFICATION messages. The measurement point is A, as shown in Figure 34-36.
Figure 34-36 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.36 C901280035 Number of ABIS_BCCH_INFO messages

Definition
Number of ABIS_BCCH_INFO messages

34-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

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.

Measurement Point
This counter increments when BSC sends BCCH INFOMATION messages. measurement point is A, as shown in Figure 34-37.
Figure 34-37 Measurement Point when BSC Sends Abis Message to BTS

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 transmitting on Abis interface.
34-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter increments when BSC receives CCCH LOAD INDICATION messages. The measurement point is A, as shown in Figure 34-38.
Figure 34-38 BTS sends measurement point of Abis message to BSC

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 measurement point is A, as shown in Figure 34-39.

34-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Figure 34-39 BTS sends measurement point of Abis message to BSC

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives DELETE INDICATION messages. The measurement point is A, as shown in Figure 34-40.
Figure 34-40 BTS sends measurement point of Abis message to BSC

34-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

34.40 C901280039 Number of ABIS_PAGING_CMD messages

Definition
Number of ABIS_PAGING_CMD messages

Description
When BSC receives PADING message of BSSMAP protocol sent by MSC from A-interface, it sends one PAGING COMMAND message to BTS, including MS identity (TMSI or IMSI). BTS sends to MS on PCH of radio interface through PAGING REQUEST. This counter counts the number of ABIS_PAGING_CMD messages sent by BSC.

Usage
This counter is used to find out the frequency of PAGING COMMAND messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends PAGING COMMAND messages to BTS. The measurement point is A, as shown in Figure 34-41.
Figure 34-41 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

Related Features
ZGB-02-01-001 Paging

34-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

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. This message includes one complete Um interface RR layer IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED or IMMEDIATE ASSIGNMENT REJECT (if there is no channel) to notify MS. After BTS receives this message, it is in charge of assigning Um interface RR layer message of the message on CCCH to MS. This counter counts the number of ABIS_IMM_ASSIGN_CMD messages sent by BSC.

Usage
This counter is used to find out the frequency of IMMEDIATE ASSIGN COMMAND messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends IMMEDIATE ASSIGN COMMAND messages to BTS. The measurement point is A, as shown in Figure 34-42.
Figure 34-42 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

34.42 C901280041 Number of ABIS_SMS_BROADCAST_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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends SMS BROADCAST REQUEST messages to BTS. The measurement point is A, as shown in Figure 34-43.
Figure 34-43 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

Related Features
ZGO-01-03-004 Cell Broadcast SMS

34.43 C901280042 Number of ABIS_SMS_BROADCAST_CMD messages

Definition
Number of ABIS_SMS_BROADCAST_CMD messages
34-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends MS BROADCAST COMMAND messages to BTS. The measurement point is A, as shown in Figure 34-44.
Figure 34-44 Measurement Point when BSC Sends Abis Message to BTS

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 messages sent by BSC.

34-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the frequency of CBCH LOAD INDICATION messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives CBCH LOAD INDICATION messages to BTS. The measurement point is A, as shown in Figure 34-45.
Figure 34-45 BTS sends measurement point of Abis message to BSC

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 measurement point is A, as shown in Figure 34-46.

34-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Figure 34-46 BTS sends measurement point of Abis message to BSC

Unit
Times

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives CCCHLOAD INDICATION messages. The measurement point is A, as shown in Figure 34-47.
Figure 34-47 BTS sends measurement point of Abis message to BSC

34-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

34.47 C901280046 Number of ABIS_END_LOAD_CONTROL messages

Definition
Number of ABIS_END_LOAD_CONTROL messages

Description
This counter counts the number of ABIS_END_LOAD_CONTROL messages sent by BSC.

Usage
This counter is used to find out the frequency of END LOAD CONTROL messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ABIS_END_LOAD_CONTROL messages to BTS. The measurement point is A, as shown in Figure 34-48.
Figure 34-48 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.48 C901280047 Number of ABIS_END_LOAD_CONTROL_ACK messages

Definition
Number of ABIS_END_LOAD_CONTROL_ACK messages

34-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Description
This counter counts the number of ABIS_END_LOAD_CONTROL_ACK messages received by BSC.

Usage
This counter is used to find out the frequency of END LOAD CONTROL RETURN messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_END_LOAD_CONTROL_ACK messages to BTS. The measurement point is A, as shown in Figure 34-49.
Figure 34-49 BTS sends measurement point of Abis message to BSC

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 interface messages received by BSC.

Usage
This counter is used to find out the frequency of PCCH flow control control command messages transmitting on Abis interface.

34-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter increments when BSC receives ABIS_PCCCH_LOAD_CONTROL_IND messages to BTS. The measurement point is A, as shown in Figure 34-50.
Figure 34-50 BTS sends measurement point of Abis message to BSC

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives RF RESOURCE INDICATION messages. The measurement point is A, as shown in Figure 34-51.

34-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Figure 34-51 BTS sends measurement point of Abis message to BSC

Unit
Times

34.51 C901280050 Number of ABIS_SACCH_FILLING messages

Definition
Number of ABIS_SACCH_FILLING messages

Description
When BSC modifies SI1/5bis/6/EXTENDED MEASUREMENT ORDER message sent on SACCH, it sends one SACCH FILLING message to BTS. This counter counts the number of SACCH FILLING INFORMATION CHANGE messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of SACCH FILLING INFORMATION CHANGE messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends SACCH FILLING messages. The measurement point is A, as shown in Figure 34-52.
Figure 34-52 Measurement Point when BSC Sends Abis Message to BTS

34-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.

Measurement Point
This counter increments when BSC receives overload messages. The measurement point is A, as shown in Figure 34-53.
Figure 34-53 BTS sends measurement point of Abis message to BSC

Unit
Times

34.53 C901280052 Number of ABIS_ERROR_REPORT messages

Definition
Number of ABIS_ERROR_REPORT messages
34-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

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 point is A, as shown in Figure 34-54.
Figure 34-54 BTS sends measurement point of Abis message to BSC

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 messages transmitting on Abis interface.

34-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter increments when BSC receives ABIS_SYSINFO_REQ messages. measurement point is A, as shown in Figure 34-55.
Figure 34-55 BTS sends measurement point of Abis message to BSC

The

Unit
Times

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 measurement point is A, as shown in Figure 34-56.

34-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Figure 34-56 Measurement Point when BSC Sends Abis Message to BTS

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.

Usage
This counter is used to find out the frequency of SI_NACK messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_SI_NACK messages to BTS. The measurement point is A, as shown in Figure 34-57.
Figure 34-57 BTS sends measurement point of Abis message to BSC

34-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_PWRCTRL_IND messages. The measurement point is A, as shown in Figure 34-58.
Figure 34-58 BTS sends measurement point of Abis message to BSC

Unit
Times

34.58 C901280057 Number of ABIS_SYSINFO_ACK messages

Definition
Number of ABIS_SYSINFO_ACK messages

34-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

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. measurement point is A, as shown in Figure 34-59.
Figure 34-59 BTS sends measurement point of Abis message to BSC

The

Unit
Times

34.59 C901280061 Number of ABIS_PACKET_PBCCH_INF 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 messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ABIS_PACKET_PBCCH_INF messages. The measurement point is A, as shown in Figure 34-60.
34-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 34-60 Measurement Point when BSC Sends Abis Message to BTS

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.

Usage
This counter is used to find out the frequency of CCCH INFORMATION messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ABIS_PACKET_CCCH_PARA messages. The measurement point is A, as shown in Figure 34-61.
Figure 34-61 Measurement Point when BSC Sends Abis Message to BTS

34-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

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 transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ABIS_PACKET_PBCCH_PARA messages to BTS. The measurement point is A, as shown in Figure 34-62.
Figure 34-62 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.62 C901280064 Number of ABIS_PACKET_CHN_REQ messages

Definition
Number of ABIS_PACKET_CHN_REQ messages
34-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of ABIS_PACKET_CHN_REQ messages received by BSC.

Usage
This counter is used to find out the frequency of UL PACKET CHANNEL REQUIREMENT messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_PACKET_CHN_REQ messages to BTS. The measurement point is A, as shown in Figure 34-63.
Figure 34-63 BTS sends measurement point of Abis message to BSC

Unit
Times

34.63 C901280065 Number of ABIS_PACKET_PAGING_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 transmitting on Abis interface.

34-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Measurement Point
This counter increments when BSC sends ABIS_PACKET_PAGING_CMD messages to BTS. The measurement point is A, as shown in Figure 34-64.
Figure 34-64 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

Related Features
ZGB-02-01-001 Paging

34.64 C901280066 Number of ABIS_PACKET_IMM_ASSIGN_CMD messages

Definition
Number of ABIS_PACKET_IMM_ASSIGN_CMD messages

Description
This counter counts the number of PACKET IMMEDIATE ASSIGNMENT messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of PACKET IMMEDIATE ASSIGNMENT messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ABIS_PACKET_IMM_ASSIGN_CMD messages to BTS. The measurement point is A, as shown in Figure 34-65.

34-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 34-65 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.65 C901280067 Number of ABIS_PACKET_CONNECT_FAIL_IND messages

Definition
Number of ABIS_PACKET_CONNECT_FAIL_IND messages

Description
This counter counts the number of PACKET CONNECT FAILURE INDICATION messages of Abis interface messages received by BSC.

Usage
This counter is used to find out the frequency of PACKET CONNECT FAILURE INDICATION messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_PACKET_CONNECT_FAIL_IND messages to BTS. The measurement point is A, as shown in Figure 34-66.
Figure 34-66 BTS sends measurement point of Abis message to BSC

34-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

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 messages received by BSC.

Usage
This counter is used to find out the frequency of PRACH OVERLOAD messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_PACKET_PRACH_OVERLOAD messages. The measurement point is A, as shown in Figure 34-67.
Figure 34-67 BTS sends measurement point of Abis message to BSC

Unit
Times

34.67 C901280069 Number of ABIS_PACKET_PCH_OVERLOAD messages

Definition
Number of ABIS_PACKET_PCH_OVERLOAD messages
34-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of PCH OVERLOAD messages of Abis interface messages received by BSC.

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 messages. The measurement point is A, as shown in Figure 34-68.
Figure 34-68 BTS sends measurement point of Abis message to BSC

Unit
Times

34.68 C901280070 Number of ABIS_PACKET_TA_REQUEST messages

Definition
Number of ABIS_PACKET_TA_REQUEST messages

Description
This counter counts the number of TIME ADVANCE REQUEST messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of TIME ADVANCE REQUEST messages transmitting on Abis interface.

34-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Measurement Point
This counter increments when BSC sends ABIS_PACKET_TA_REQUEST messages. The measurement point is A, as shown in Figure 34-69.
Figure 34-69 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.69 C901280071 Number of ABIS_PACKET_TA_REQUEST_ACK messages

Definition
Number of ABIS_PACKET_TA_REQUEST_ACK messages

Description
This counter counts the number of TIME ADVANCE REQUEST ACKNOWLEDGE messages of Abis interface messages received by BSC.

Usage
This counter is used to find out the frequency of TIME ADVANCE REQUEST ACKNOWLEDGE messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_PACKET_TA_REQUEST_ACK messages. The measurement point is A, as shown in Figure 34-70.

34-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 34-70 BTS sends measurement point of Abis message to BSC

Unit
Times

34.70 C901280072 Number of ABIS_PACKET_CHN_CONFIG_CHG messages

Definition
Number of ABIS_PACKET_CHN_CONFIG_CHG messages

Description
This counter counts the number of CHANNEL CONFIGURATION CHANGE messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of CHANNEL CONFIGURATION CHANGE messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ABIS_PACKET_CHG_CONFIG_CHG messages. The measurement point is A, as shown in Figure 34-71.
Figure 34-71 Measurement Point when BSC Sends Abis Message to BTS

34-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Unit
Times

34.71 C901280073 Number of ABIS_PACKET_CHN_CONFIG_CHG_RESP messages

Definition
Number of ABIS_PACKET_CHN_CONFIG_CHG_RESP messages

Description
This counter counts the number of CHANNEL CONFIGURATION CHANGE RESPONSE messages of Abis interface messages received by BSC.

Usage
This counter is used to find out the frequency of CHANNEL CONFIGURATION CHANGE RESPONSE messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_PACKET_CHG_CONFIG_CHG_RESP messages. The measurement point is A, as shown in Figure 34-72.
Figure 34-72 BTS sends measurement point of Abis message to BSC

Unit
Times

34-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

34.72 C901280074 Number of ABIS_PACKET_PIA_DEL_IND messages

Definition
Number of ABIS_PACKET_PIA_DEL_IND messages

Description
This counter counts the number of IMMEDIATE ASSIGNMENT TRANSMISSION FAILURE INDICATION messages of Abis interface 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. The measurement point is A, as shown in Figure 34-73.
Figure 34-73 BTS sends measurement point of Abis message to BSC

Unit
Times

34.73 C901280075 Number of ABIS_PACKET_SEND_PIA_IND messages

Definition
Number of ABIS_PACKET_SEND_PIA_IND messages

Description
This counter counts the number of IMMEDIATE ASSIGNMENT TRANSMISSION SUCCESS INDICATION messages of Abis interface messages received by BSC.
34-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Usage
This counter is used to find out the frequency of IMMEDIATE ASSIGNMENT TRANSMISSION SUCCESS INDICATION messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_PACKET_SEND_PIA_IND messages. The measurement point is A, as shown in Figure 34-74.
Figure 34-74 BTS sends measurement point of Abis message to BSC

Unit
Times

34.74 C901280076 Number of ABIS_PACKET_CHN_CONFIG_REQ messages

Definition
Number of ABIS_PACKET_CHN_CONFIG_REQ messages

Description
This counter counts the number of PS PARAMETER CONFIGURATION REQUEST messages of Abis interface messages received by BSC.

Usage
This counter is used to find out the frequency of PS PARAMETER CONFIGURATION REQUEST messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_PACKET_CHN_CONFIG_REQ messages. The measurement point is A, as shown in Figure 34-75.

34-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 34-75 BTS sends measurement point of Abis message to BSC

Unit
Times

34.75 C901280077 Number of ABIS_EGPRS_PACKET_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 interface messages received by BSC.

Usage
This counter is used to find out the frequency of UL EGPRS PACKET REQUEST messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_EGPRS_PACKET _CHN_REQ messages. The measurement point is A, as shown in Figure 34-76.
Figure 34-76 BTS sends measurement point of Abis message to BSC

34-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Unit
Times

34.76 C901280078 Number of ABIS_PS_CHANNEL_ACTIVE messages

Definition
Number of ABIS_PS_CHANNEL_ACTIVE messages

Description
This counter counts the number of PS CHANNEL ACTIVE COMMAND messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of PS CHANNEL ACTIVE COMMAND messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ABIS_PS_CHANNEL _ACTIVE messages. The measurement point is A, as shown in Figure 34-77.
Figure 34-77 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.77 C901280079 Number of ABIS_PS_CHANNEL_ACTIVE_ACK messages

Definition
Number of ABIS_PS_CHANNEL_ACTIVE_ACK messages
34-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 messages. The measurement point is A, as shown in Figure 34-78.
Figure 34-78 BTS sends measurement point of Abis message to BSC

Unit
Times

34.78 C901280080 Number of ABIS_PS_CHANNEL_ACTIVE_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.

34-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Measurement Point
This counter increments when BSC receives ABIS_PS_CHANNEL _ACTIVE_NACK messages. The measurement point is A, as shown in Figure 34-79.
Figure 34-79 BTS sends measurement point of Abis message to BSC

Unit
Times

34.79 C901280081 Number of ABIS_PS_CHANNEL_RELEASE messages

Definition
Number of ABIS_PS_CHANNEL_RELEASE messages

Description
This counter counts the number of PS CHANNEL RELEASE COMMAND messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of PS CHANNEL RELEASE COMMAND messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ABIS_PS_CHANNEL_RELEASE messages to BTS. The measurement point is A, as shown in Figure 34-80.

34-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 34-80 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.80 C901280082 Number of ABIS_PS_CHANNEL_RELEASE_ACK messages

Definition
Number of ABIS_PS_CHANNEL_RELEASE_ACK messages

Description
This counter counts the number of PS CHANNEL RELEASE ACKNOWLEDGEMENT COMMAND messages of Abis interface messages received by BSC.

Usage
This counter is used to find out the frequency of PS CHANNEL RELEASE ACKNOWLEDGEMENT COMMAND messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_PS_CHANNEL_RELEASE_ACK messages. The measurement point is A, as shown in Figure 34-81.
Figure 34-81 BTS sends measurement point of Abis message to BSC

34-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Unit
Times

34.81 C901280083 Number of ABIS_PS_CHANNEL_RELEASE_NACK messages

Definition
Number of ABIS_PS_CHANNEL_RELEASE_NACK messages

Description
This counter counts the number of PS CHANNEL RELEASE UNACKNOWLEDGEMENT COMMAND messages of Abis interface messages received by BSC.

Usage
This counter is used to find out the frequency of PS CHANNEL RELEASE UNACKNOWLEDGEMENT COMMAND messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_PS_CHANNEL_RELEASE_NACK messages. The measurement point is A, as shown in Figure 34-82.
Figure 34-82 BTS sends measurement point of Abis message to BSC

Unit
Times

34.82 C901280084 Number of ABIS_PSCONN_CMM_REQ messages

Definition
Number of ABIS_PSCONN_CMM_REQ messages
34-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of PS CONNECTION COMMAND messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of PS CONNECTION COMMAND messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ABIS_PSCONN_CMM_REQ messages to BTS. The measurement point is A, as shown in Figure 34-83.
Figure 34-83 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.83 C901280085 Number of ABIS_PSCONN_CMM_ACK messages

Definition
Number of ABIS_PSCONN_CMM_ACK messages

Description
This counter counts the number of PS CONNECTION SUCCESS COMMAND ACKNOWLEDGEMENT messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of PS CONNECTION SUCCESS COMMAND ACKNOWLEDGEMENT messages transmitting on Abis interface.

34-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Measurement Point
This counter increments when BSC receives ABIS_PSCONN_CMM_ACK messages. The measurement point is A, as shown in Figure 34-84.
Figure 34-84 BTS sends measurement point of Abis message to BSC

Unit
Times

34.84 C901280086 Number of ABIS_PSCONN_CMM_NACK messages

Definition
Number of ABIS_PSCONN_CMM_NACK messages

Description
This counter counts the number of PS CONNECTION FAILURE COMMAND ACKNOWLEDGEMENT messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of PS CONNECTION FAILURE COMMAND ACKNOWLEDGEMENT messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_PSCONN_CMM_NACK messages. The measurement point is A, as shown in Figure 34-85.

34-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 34-85 BTS sends measurement point of Abis message to BSC

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 interface messages sent by BSC.

Usage
This counter is used to find out the frequency of GLOBAL RESET COMMAND messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ABIS_GLOBAL_RESET messages to BTS. The measurement point is A, as shown in Figure 34-86.
Figure 34-86 Measurement Point when BSC Sends Abis Message to BTS

34-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Unit
Times

34.86 C901280088 Number of ABIS_GLOBAL_RESET_ACK messages

Definition
Number of ABIS_GLOBAL_RESET_ACK messages

Description
This counter counts the number of GLOBAL RESET ACKNOWLEDGEMENT COMMAND messages of Abis interface messages sent by BSC.

Usage
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. The measurement point is A, as shown in Figure 34-87.
Figure 34-87 BTS sends measurement point of Abis message to BSC

Unit
Times

34.87 C901280089 Number of ABIS_GLOBAL_RESET_NACK messages

Definition
Number of ABIS_GLOBAL_RESET_NACK messages
34-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 UNACKNOWLEDGEMENT COMMAND messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_GLOBAL_RESET_NACK messages. The measurement point is A, as shown in Figure 34-88.
Figure 34-88 BTS sends measurement point of Abis message to BSC

Unit
Times

34.88 C901280090 Number of ABIS_PACKET_UP_ASSIGN messages

Definition
Number of ABIS_PACKET_UP_ASSIGN messages

Description
This counter counts the number of PS UL ASSIGNMENT COMMAND messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of PS UL ASSIGNMENT COMMAND messages transmitting on Abis interface.

34-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Measurement Point
This counter increments when BSC sends ABIS_PACKET_UP_ASSIGN messages to BTS. The measurement point is A, as shown in Figure 34-89.
Figure 34-89 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.89 C901280091 Number of ABIS_PACKET_DOWN_ASSIGN messages

Definition
Number of ABIS_PACKET_DOWN_ASSIGN messages

Description
This counter counts the number of PS DL ASSIGNMENT COMMAND messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of PS DL ASSIGNMENT COMMAND messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ABIS_PACKET_DOWN_ASSIGN messages to BTS. The measurement point is A, as shown in Figure 34-90.

34-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 34-90 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.90 C901280092 Number of ABIS_CSCONN_CMM_REQ messages

Definition
Number of ABIS_CSCONN_CMM_REQ messages

Description
This counter counts the number of CS CONNECTION COMMAND messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of CS CONNECTION COMMAND messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ABIS_CSCONN_CMM_REQ messages to BTS. The measurement point is A, as shown in Figure 34-91.
Figure 34-91 Measurement Point when BSC Sends Abis Message to BTS

34-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Unit
Times

34.91 C901280093 Number of ABIS_CSCONN_CMM_ACK messages

Definition
Number of ABIS_CSCONN_CMM_ACK messages

Description
This counter counts the number of CS CONNECTION SUCCESS COMMAND ACKNOWLEDGEMENT messages of Abis interface messages received by BSC.

Usage
This counter is used to find out the frequency of CS CONNECTION SUCCESS COMMAND ACKNOWLEDGEMENT messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_CSCONN_CMM_ACK messages. The measurement point is A, as shown in Figure 34-92.
Figure 34-92 BTS sends measurement point of Abis message to BSC

Unit
Times

34.92 C901280094 Number of ABIS_CSCONN_CMM_NACK messages

Definition
Number of ABIS_CSCONN_CMM_NACK messages
34-77 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of CS CONNECTION FAILURE COMMAND ACKNOWLEDGEMENT messages of Abis interface messages received by BSC.

Usage
This counter is used to find out the frequency of CS CONNECTION FAILURE COMMAND ACKNOWLEDGEMENT messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_CSCONN_CMM_NACK messages. The measurement point is A, as shown in Figure 34-93.
Figure 34-93 BTS sends measurement point of Abis message to BSC

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 interface messages sent by BSC.

Usage
This counter is used to find out the frequency of CCM CONNECTION COMMAND messages transmitting on Abis interface.

34-78 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Measurement Point
This counter increments when BSC sends ABIS_CCMCONN_CMM_REQ messages to BTS. The measurement point is A, as shown in Figure 34-94.
Figure 34-94 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.94 C901280096 Number of ABIS_CCMCONN_CMM_ACK messages

Definition
Number of ABIS_CCMCONN_CMM_ACK messages

Description
This counter counts the number of CCM CONNECTION SUCCESS COMMAND ACKNOWLEDGEMENT messages of Abis interface messages received by BSC.

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. The measurement point is A, as shown in Figure 34-95.

34-79 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 34-95 BTS sends measurement point of Abis message to BSC

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 ACKNOWLEDGEMENT messages of Abis interface messages received by BSC.

Usage
This counter is used to find out the frequency of CCM CONNECTION FAILURE COMMAND ACKNOWLEDGEMENT messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC receives ABIS_CCMCONN_CMM_NACK messages. The measurement point is A, as shown in Figure 34-96.
Figure 34-96 BTS sends measurement point of Abis message to BSC

34-80 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Unit
Times

34.96 C901280098 Number ABIS_PACKET_ACCESS_REJ messages

Definition
Number ABIS_PACKET_ACCESS_REJ messages

Description
This counter counts the number of PS ACCESS REJECT messages of Abis interface messages sent by BSC.

Usage
This counter is used to find out the frequency of PS ACCESS REJECT messages transmitting on Abis interface.

Measurement Point
This counter increments when BSC sends ABIS_PACKET_ACCESS_REJ messages to BSC. The measurement point is A, as shown in Figure 34-97.
Figure 34-97 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34-81 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

34.97 C901280099 Number of ABIS_PACKET_IMM_ASSIGN_CMD_NEW messages

Definition
Number of ABIS_PACKET_IMM_ASSIGN_CMD_NEW messages

Description
This counter counts the number of new packet immediate assignment messages in the Abis interface messages sent by BSC.

Usage
The counter is used to find out the frequency of new packet immediate assignment messages transmitted at Abis interface.

Measurement Point
When BSC sends the ABIS_PACKET_IMM_ASSIGN_CMD_NEW message to BTS, the counter increments. The measurement point is A, as shown in Figure 34-98.
Figure 34-98 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.98 C901280100 Number of PACKET_DOWNLINK_ASSIGN messages

Definition
Number of PACKET_DOWNLINK_ASSIGN messages

34-82 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Description
This counter counts the number of packet downlink assignment messages in the Abis interface messages sent by BSC.

Usage
The counter is used to find out the frequency of packet downlink assignment messages transmitted at Abis interface.

Measurement Point
When BSC sends the PACKET_DOWNLINK_ASSIGN message to BTS, the counter increments. The measurement point is A, as shown in Figure 34-99.
Figure 34-99 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.99 C901280101 Number of PACKET_UPLINK_ASSIGN messages

Definition
Number of PACKET_UPLINK_ASSIGN messages

Description
This counter counts the number of packet uplink assignment messages in the Abis interface messages sent by BSC.

Usage
The counter is used to find out the frequency of packet uplink assignment messages transmitted at Abis interface.

34-83 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC sends the PACKET_UPLINK_ASSIGN message to BTS, the counter increments. The measurement point is A, as shown in Figure 34-100.
Figure 34-100 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.100 C901280102 Number of ABIS_PACKET_ACCESS_REJ_NEW messages

Definition
Number of ABIS_PACKET_ACCESS_REJ_NEW messages

Description
This counter counts the number of new PS access reject messages in the Abis interface messages sent by BSC.

Usage
The counter is used to find out the frequency of new PS access reject messages transmitted at Abis interface.

Measurement Point
When BSC sends the ABIS_PACKET_ACCESS_REJ_NEW message to BTS, the counter increments. The measurement point is A, as shown in Figure 34-101.

34-84 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Figure 34-101 Measurement Point when BSC Sends Abis Message to BTS

Unit
Times

34.101 C901280105 Peak of CS Paging Messages From CN

Description
This counter records the peak value of the number of CS paging messages that are sent from the core network through the Abis interface in a measurement period (per second). In each measurement period, CS paging messages are counted from zero. The CMP board starts the corresponding timer upon being powered on. The Abis interface at the BSC side receives and counts CS paging messages from the core network. When the timer expires, the BSC compares the number of received paging messages with that recorded in the previous measurement period, updates this counter with the greater number, and then restarts the timer.

Usage
This counter indicates the peak value of the number of CS paging messages received through the Abis interface.

Measurement Point
This counter is updated upon the expiry of the timer that is used for counting the CS paging messages received from the core network through the Abis interface.

Unit
Times

34-85 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

34.102 C901280106 Peak of CS Paging Messages From SGSN

Description
This counter records the peak value of the number of CS paging messages that are sent from the core network through the Abis interface in a measurement period (per second). In each measurement period, CS paging messages are counted from zero. The CMP board starts the corresponding timer upon being powered on. The Abis interface at the BSC side receives and counts CS paging messages from the core network. When the timer expires, the BSC compares the number of received paging messages with that recorded in the previous measurement period, updates this counter with the greater number, and then restarts the timer.

Usage
This counter indicates the peak value of the number of CS paging messages received through the Gb interface.

Measurement Point
This counter is updated upon the expiry of the timer that is used for counting the CS paging messaages received from the core network through the Abis interface.

Unit
Times

34.103 C901280107 Peak of PS Paging Messages From SGSN

Description
This counter records the peak value of the number of PS paging messages that are sent from the core network through the Abis interface in a measurement period (per second). In each measurement period, PS paging messages are counted from zero. The CMP board starts the corresponding timer upon being powered on. The Abis interface at the BSC side receives and counts PS paging messages from the core network. When the timer expires, the BSC compares the number of received paging messages with that recorded in the previous measurement period, updates this counter with the greater number, and then restarts the timer.

Usage
This counter indicates the peak value of the number of PS paging messages received through the Gb interface.
34-86 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 34 Abis Interface Message Counter Measurement

Measurement Point
This counter is updated upon the expiry of the timer that is used for counting the PS paging messaages received from the core network through the Abis interface.

Unit
Times

34.104 C901280108 Peak of Paging Messages

Description
This counter records the peak value of the number of paging messages (CS and PS) that are sent from the core network through the Abis interface in a measurement period (per second). In each measurement period, paging messages are counted from zero. The CMP board starts the corresponding timer upon being powered on. The Abis interface at the BSC side receives and counts paging messages from the core network. When the timer expires, the BSC compares the number of received paging messages with that recorded in the previous measurement period, updates this counter with the greater number, and then restarts the timer.

Usage
This counter indicates the peak value of the number of paging messages.

Measurement Point
This counter is updated upon the expiry of the timer that is used for counting the paging messaages received from the core network through the Abis interface.

Unit
Times

34.105 C901280109 Time of Paging reached the threshold

Description
This counter counts the seconds during which the number of paging messages (CS and PS) received from the core network through the Abis interface exceeds the preset threshold. The number of paging messages received in each measurement period is compared with the preset threshold. If the number exceeds 90% of the preset threshold, this counter is updated.

34-87 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter indicates the number of seconds during which the number of paging messages exceeds the preset threshold.

Measurement Point
This counter is updated upon the expiry of the corresponding timer when the number of paging messages received through the Abis interface exceeds 90% of the preset threshold.

Unit
Times

34-88 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 35

Gb Message Statistics (BVC Cell)

Table of Contents
Overview ..................................................................................................................35-2 C901290001 Sum of UL UNITDATA messages handled at BSSGP level..................35-2 C901290002 Sum of DL UNITDATA messages handled at BSSGP level..................35-3 C901290003 Number of RA-CAPABILITY message received...................................35-4 C901290004 Number of PTP packet paging received by BSC..................................35-4 C901290005 Number of PTP circuit paging received by BSC...................................35-5 C901290006 Number of RA-CAPABILITY-UPDATE message sent...........................35-6 C901290007 Number of RA-CAPABILITY-UPDATE-ACK message received............35-6 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 C901290016 Number of FLOW-CONTROL-PFC messages sent by BSC ..............35-13 C901290017 Number of FLOW-CONTROL-PFC-ACK messages received by 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-16 C901290021 Number of Status messages sent with Cell service congestion..........35-16 C901290022 Number of Status messages sent with protocol error.........................35-17 C901290023 Number of Status messages sent with Processor overload ...............35-17 C901290024 Number of Status messages received with BVCI Unknown ...............35-18 C901290025 Number of Status messages received with Cell service congestion ...35-18 C901290026 Number of Status messages received with protocol error ..................35-19 C901290027 Number of Status messages received with Processor overload.........35-19 C901290028 Number of DOWNLOAD-BSS-PFC messages sent by BSC ..............35-20
35-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901290029 Number of BVCCREATE-BSS-PFC messages received by BSC.......35-20 C901290030 Number of CREATE-BSS-PFC-ACK messages sent by BSC ............35-21 C901290031 Number of CREATE-BSS-PFC-NACK messages sent by BSC..........35-22 C901290032 Number of MODIFY-BSS-PFC messages sent by BSC .....................35-23 C901290033 Number of MODIFY-BSS-PFC-ACK messages received by BSC ......35-24 C901290034 Number of DELETE-BSS-PFC messages received by BSC ..............35-24 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.

35.2 C901290001 Sum of UL UNITDATA messages handled at BSSGP level

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 point is A, as shown in Figure 35-1.

35-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 35 Gb Message Statistics (BVC Cell)

Figure 35-1 Measurement point of sum of UL UNITDATA message handled at BSSGP level

Unit
Times

35.3 C901290002 Sum of DL UNITDATA messages handled at BSSGP level

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. measurement point is A, as shown in Figure 35-2. The

Figure 35-2 Measurement point of sum of DL UNITDATA message handled at BSSGP level

35-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
When BSC receives a RA-CAPABILITY message, this counter increments. measurement point is A, as shown in Figure 35-3. The

Figure 35-3 Measurement point of the number of RA-CAPABILITY message received

Unit
Times

35.5 C901290004 Number of PTP packet paging 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 for MS. This counter counts the number of receiving this message by BSC.

35-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 35 Gb Message Statistics (BVC Cell)

Measurement Point
When BSC receives a PAGING PS message, this counter increments. The measurement point is A, as shown in Figure 35-4.
Figure 35-4 PTP Packet Paging Process

Unit
Times

35.6 C901290005 Number of PTP circuit paging 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 for MS. This counter counts the number of receiving this message by BSC.

Measurement Point
When BSC receives a PAGING CS message, this counter increments. The measurement point is A, as shown in Figure 35-5.
Figure 35-5 PTP Circuit Paging Process

Unit
Times
35-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

35.7 C901290006 Number of RA-CAPABILITY-UPDATE 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
When BSC sends a RA-CAPABILITY-UPDATE message to SGSN, this counter increments. The measurement point is A1, as shown in Figure 35-6.
Figure 35-6 RA-CAPABILITY-UPDATE Process

Unit
Times

35.8 C901290007 Number of RA-CAPABILITY-UPDATE-ACK message received

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 35 Gb Message Statistics (BVC Cell)

Measurement Point
When BSC sends a RA-CAPABILITY-UPDATE-ACK message from SGSN, this counter increments. The measurement point is A2, as shown in Figure 35-7.
Figure 35-7 RA-CAPABILITY-UPDATE Process

Unit
Times

35.9 C901290008 Number of Wireless Status PDU messages sent by BSC

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
When BSC sends a RADIO-STATUS message to SGSN, this counter increments. The measurement point is A, as shown in Figure 35-8.

35-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 35-8 RADIO-STATUS Process

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 wireless association with MS.

Usage
View the status at radio interface by counting this message.

Measurement Point
When BSC sends a RADIO-STATUS message due to Losing wireless association with MS, this counter increments.

Unit
Times

35-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 35 Gb Message Statistics (BVC Cell)

35.11 C901290010 Number of wireless status messages sent by BSC due to Bad Link Quality
Definition
Number of wireless status messages sent by BSC due to Bad Link Quality

Description
BSC sends wireless status message, to indicate exception occurred at SGSN radio interface. This counter counts the number of sending this message by BSC due to bad link quality.

Usage
View the status at radio interface by counting this message.

Measurement Point
When BSC sends a RADIO-STATUS message to SGSN due to bad link quality, this 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
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 cell reselection command.

Usage
View the status at radio interface by counting this message.

35-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC sends a RADIO-STATUS message to SGSN due to cell reselection command, this counter increments.

Unit
Times

35.13 C901290012 Number of FLOW-CONTROL-BVC messages sent by BSC

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.
Figure 35-9 RADIO-STATUS Process

Unit
Times

35.14 C901290013 Number of FLOW-CONTROL-BVC-ACK messages received by BSC

Definition
Number of FLOW-CONTROL-BVC-ACK messages received by BSC
35-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 35 Gb Message Statistics (BVC Cell)

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
When BSC receives a FLOW-CONTROL-BVC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 35-10.
Figure 35-10 FLOW-CONTROL-BVC Process

Unit
Times

35.15 C901290014 Number of FLOW-CONTROL-MS messages sent by BSC

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 measurement point is A1, as shown in Figure 35-11.

35-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 35-11 FLOW-CONTROL-MS Process

Unit
Times

35.16 C901290015 Number of FLOW-CONTROL-MS-ACK messages received by BSC

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. The measurement point is A2, as shown in Figure 35-12.
Figure 35-12 FLOW-CONTROL-MS Process

35-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 35 Gb Message Statistics (BVC Cell)

Unit
Times

35.17 C901290016 Number of FLOW-CONTROL-PFC messages sent by BSC

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 measurement point is A1, as shown in Figure 35-13.
Figure 35-13 FLOW-CONTROL-PFC Process

Unit
Times

35.18 C901290017 Number of FLOW-CONTROL-PFC-ACK messages received by BSC

Definition
Number of FLOW-CONTROL-PFC-ACK messages received by BSC
35-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
BSC sends FLOW-CONTROL-PFC-ACK message to notify BSC of accepted PFC flow control policy for designated MS. This counter counts the number of receiving this message by BSC.

Measurement Point
When BSC receives a FLOW-CONTROL-PFC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 35-14.
Figure 35-14 FLOW-CONTROL-PFC Process

Unit
Times

35.19 C901290018 Number of Status messages sent by BSC

Definition
Number of Status messages sent by BSC

Description
BSC sends status message to SGSN, to indicate exception occurred. This counter counts the number of sending this message by BSC.

Measurement Point
When BSC sends a STATUS message, this counter increments. The measurement point is A1, as shown in Figure 35-15.

35-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 35 Gb Message Statistics (BVC Cell)

Figure 35-15 STATUS Process

Unit
Times

35.20 C901290019 Number of Status messages received by BSC

Definition
Number of Status messages received by BSC

Description
SGSN sends status message to BSC, to indicate exception occurred. This counter counts the number of receiving this message by BSC.

Measurement Point
When BSC receives a STATUS message, this counter increments. The measurement point is A2, as shown in Figure 35-16.
Figure 35-16 STATUS Process

Unit
Times
35-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

35.21 C901290020 Number of Status messages sent with BVCI Unknown

Definition
Number of Status messages sent with BVCI Unknown

Description
BSC sends status message to SGSN, to indicate exception occurred. This counter counts the number of sending this message by BSC due to BVCI Unknown.

Measurement Point
When BSC sends a STATUS message due to BVCI Unknown, this counter increments.

Unit
Times

35.22 C901290021 Number of Status messages sent with Cell service congestion
Definition
Number of Status messages sent with Cell service congestion

Description
BSC sends status message to SGSN, to indicate exception occurred. This counter counts 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

35-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 35 Gb Message Statistics (BVC Cell)

35.23 C901290022 Number of Status messages sent with protocol error

Definition
Number of Status messages sent with protocol error

Description
BSC sends status message to SGSN, to indicate exception occurred. This counter counts 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.24 C901290023 Number of Status messages sent with Processor overload

Definition
Number of Status messages sent 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.

Unit
Times

35-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

35.25 C901290024 Number of Status messages received with BVCI Unknown

Definition
Number of Status messages 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

35.26 C901290025 Number of Status messages received with Cell service congestion
Definition
Number of Status messages received with Cell service congestion

Description
SGSN sends status message to BSC, to indicate exception occurred. This counter counts 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

35-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 35 Gb Message Statistics (BVC Cell)

35.27 C901290026 Number of Status messages received with protocol error

Definition
Number of Status messages received with protocol error

Description
SGSN sends status message to BSC, to indicate exception occurred. This counter counts 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.28 C901290027 Number of Status messages received with Processor overload

Definition
Number of Status messages received with cause Processor overload

Description
SGSN sends status message to BSC, to indicate exception occurred. This counter counts 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

35-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

35.29 C901290028 Number of DOWNLOAD-BSS-PFC messages sent by BSC

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 measurement point is A1, as shown in Figure 35-17.
Figure 35-17 CREATE-BSS-PFC Process

Unit
Times

35.30 C901290029 Number of BVCCREATE-BSS-PFC messages received by BSC

Definition
Number of BVCCREATE-BSS-PFC messages received by BSC

35-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 35 Gb Message Statistics (BVC Cell)

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
When BSC receives a CREATE-BSS-PFC message, this counter increments. The measurement point is A2, as shown in Figure 35-18.
Figure 35-18 CREATE-BSS-PFC Process

Unit
Times

35.31 C901290030 Number of CREATE-BSS-PFC-ACK messages sent by BSC

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
When BSC sends a CREATE-BSS-PFC-ACK message, this counter increments. The measurement point is A3, as shown in Figure 35-19.

35-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 35-19 CREATE-BSS-PFC Process

Unit
Times

35.32 C901290031 Number of CREATE-BSS-PFC-NACK messages sent by BSC

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
When BSC sends a CREATE-BSS-PFC-NACK message, this counter increments. The measurement point is A4, as shown in Figure 35-20.

35-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 35 Gb Message Statistics (BVC Cell)

Figure 35-20 CREATE-BSS-PFC Process

Unit
Times

35.33 C901290032 Number of MODIFY-BSS-PFC messages sent by BSC

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. measurement point is A1, as shown in Figure 35-21.
Figure 35-21 MODIFY-BSS-PFC Process

The

35-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

35.34 C901290033 Number of MODIFY-BSS-PFC-ACK messages received by BSC

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
When BSC receives a MODIFY-BSS-PFC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 35-22.
Figure 35-22 MODIFY-BSS-PFC Process

Unit
Times

35.35 C901290034 Number of DELETE-BSS-PFC messages received by BSC

Definition
Number of DELETE-BSS-PFC messages received by BSC

35-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 35 Gb Message Statistics (BVC Cell)

Description
SGSN sends DELETE-BSS-PFC message to request BSC delete a packet flow control context. This counter counts the number of receiving this message by BSC.

Measurement Point
When BSC receives a DELETE-BSS-PFC message, this counter increments. measurement point is A1, as shown in Figure 35-23.
Figure 35-23 DELETE-BSS-PFC Process

The

Unit
Times

35.36 C901290035 Number of DELETE -BSS-PFC-ACK messages sent by BSC

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
When BSC sends a DELETE-BSS-PFC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 35-24.

35-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 35-24 DELETE-BSS-PFC Process

Unit
Times

35.37 C901290036 Number of DELETE -BSS-PFC-REQ messages received by BSC

Definition
Number of DELETE-BSS-PFC-REQ messages received by BSC

Description
This counter is not used.

35-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 C901300032 Number of congestion occurrence of level 2 ......................................36-25 C901300033 Number of congestion recovery of level 2 ..........................................36-25 C901300034 Number of congestion occurrence of level 3 ......................................36-25 C901300035 Number of congestion recovery of level 3 ..........................................36-25 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

36.4 C901300003 Time of PVC congestion of level 1

Definition
Time of PVC congestion of level 1

Description
This counter is not used.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 36 NSVC Statistic Measurement

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. 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 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

'

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
The NSVC service load can be checked through this counter. '

Measurement Point
The counter increments each time BSC's FR receives a PDU data from SGSN. The measurement point is A2.
Figure 36-6 SENDING AND RECEIVING PDU DATA

36-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 36 NSVC Statistic Measurement

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
The NSVC service load can be checked through this counter. '

Measurement Point
l l The counter increments when NS sub layer receives an illegal PDU data. 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. measurement point is A1.
Figure 36-8 NSVC RESETTING PROCESS

The

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 36 NSVC Statistic Measurement

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. measurement point is A3.
Figure 36-9 NSVC RESETTING PROCESS

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 measurement point is A4.
36-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 36-10 NSVC RESETTING PROCESS

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 measurement point is A2.
Figure 36-11 NSVC RESETTING PROCESS

Unit
Times
36-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 36 NSVC Statistic Measurement

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. measurement point is A1.
Figure 36-12 NSVC BLOCKING PROCESS

The

Unit
Times

36.15 C901300014 Number of received blocking messages sent by opposite end

Definition
Number of received blocking messages sent by opposite end

Description
SGSN sends the NSVC blocking message to indicate BSC to block specified NSVC. This counter counts the number of SGSN's blocking specified NSVC.

36-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
Each time BSC receives the NS-BLOCK message, this counter increments. measurement point is A3.
Figure 36-13 NSVC BLOCKING PROCESS

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 measurement point is A4.

36-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 36 NSVC Statistic Measurement

Figure 36-14 NSVC BLOCKING PROCESS

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 measurement point is A2.
Figure 36-15 NSVC BLOCKING PROCESS

36-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. measurement point is A1.
Figure 36-16 NSVC UNBLOCKING PROCESS

The

Unit
Times

36.19 C901300018 Number of received unblocking messages sent by opposite end

Definition
Number of received unblocking messages sent by opposite end

36-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 36 NSVC Statistic Measurement

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 measurement point is A3.
Figure 36-17 NSVC UNBLOCKING PROCESS

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 measurement point is A4.

36-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 36-18 NSVC UNBLOCKING PROCESS

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 measurement point is A2.
Figure 36-19 NSVC UNBLOCKING PROCESS

36-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 36 NSVC Statistic Measurement

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

36.23 C901300022 Number of abnormal cases in NS transmission due to O&M interference

Definition
Number of abnormal cases in NS transmission due to O&M interference

36-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

36.24 C901300023 Number of abnormal cases in NS transmission due to equipment fault

Definition
Number of abnormal cases in NS transmission due to equipment fault

Description
This counter counts the number of abnormal cases in NS sub layer transmission due to equipment fault.

Measurement Point
When NS sub layer receives reported fault from frame relay and the fault is due to equipment fault, the counter increments. The measurement point is A1.

36-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 36 NSVC Statistic Measurement

Figure 36-22 FR REPORTING EQUIPMENT FAULT

Unit
Times

36.25 C901300024 Number of abnormal cases in NS transmission due to NSVC block

Definition
Number of abnormal cases in NS transmission due to NSVC block

Description
This counter counts the number of abnormal cases in NS sub layer transmission due to NSVC block.

Measurement Point
When NS sub layer sends the status message which is due to NSVC BLOCKED, the counter increments. The measurement point is A1.
Figure 36-23 NSVC BLOCKED

36-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

36.26 C901300025 Number of abnormal cases in NS transmission due to unknown NSVC

Definition
Number of abnormal cases in NS transmission due to unknown NSVC

Description
This counter counts the number of abnormal cases in NS sub layer transmission due to unknown NSVC.

Measurement Point
When NS sub layer sends the status message which is due to unknown NSVC, the counter increments. The measurement point is A1.
Figure 36-24 NSVC UNKNOWN

Unit
Times

36.27 C901300026 Number of abnormal cases in NS transmission due to protocol error

Definition
Number of abnormal cases in NS transmission due to protocol error

36-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 36 NSVC Statistic Measurement

Description
This counter counts the number of abnormal cases in NS sub layer transmission due to protocol error.

Measurement Point
When NS sub layer sends the status message which is due to protocol error, including PDU semantic error, PDU being incompatible with protocol, protocol error, invalid necessary IE, and missing necessary IE, the counter increments. The measurement point is A1.
Figure 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 increments. The measurement point is A1.

36-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
This counters counts the number of test failure due to the maximum retransmission times 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 increments. The measurement point is A1.

36-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 36 NSVC Statistic Measurement

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
This counters counts the number of test failure due to the maximum retransmission times 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 increments. The measurement point is A1.

36-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
This counter is not used.

36.32 C901300031 Number of congestion recovery of level 1

Definition
Number of congestion recovery of level 1

Description
This counter is not used.

36-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 36 NSVC Statistic Measurement

36.33 C901300032 Number of congestion occurrence of level 2

Definition
Number of congestion occurrence of level 2

Description
This counter is not used.

36.34 C901300033 Number of congestion recovery of level 2

Definition
Number of congestion recovery of level 2

Description
This counter is not used.

36.35 C901300034 Number of congestion occurrence of level 3

Definition
Number of congestion occurrence of level 3

Description
This counter is not used.

36.36 C901300035 Number of congestion recovery of level 3

Definition
Number of congestion recovery of level 3

Description
This counter is not used.

36-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A1.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 36 NSVC Statistic Measurement

Measurement Point
When FECN in the data received by FR from SGSN is set, the counter accumulates. The measurement point is A2.
Figure 36-30 UPLINK/DOWNLINK DATA BECN BEING SET

Unit
Times

36-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

36-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 C901310027 Number of status messages sent with BVCI Unknown ......................37-22 C901310028 Number of status messages sent with cell service congestion ...........37-22 C901310029 Number of status messages sent with protocol error .........................37-23 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 C901310039 Number of status messages received with cell service congestion ....37-29 C901310040 Number of status messages received with protocol error...................37-29 C901310041 Number of status messages received with processor overload..........37-30 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 increments. The measurement point is A.
Figure 37-2 MEASUREMENT POINT OF BSS RECEIVING PS PAGING MESSAGE

Unit
Times
37-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

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. measurement point is A2.
Figure 37-4 SUSPEND PROCESS

The

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. measurement point is A2. The

37-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

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 messages received by NSE.

Usage
The counter is used to find out causes due to which SGSN has no response when MS requests for resuming GPRS service.

Measurement Point
When BSS receives the RESUME_ACK message, the counter increments. measurement point is A2.
Figure 37-7 RESUME PROCESS

The

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

is, unknown MS. At this moment, BSS will terminate the RESUME process and ask MS to update routing area. This counter counts the number of RESUME_NACK messages received by NSE.

Usage
The counter is used to find out cases in which SGSN has no response when MS requests for resuming GPRS service.

Measurement Point
When BSS receives the RESUME_NACK message, the counter increments. measurement point is A2. 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

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. measurement point is A2.
Figure 37-10 FLUSH_LL PROCESS

The

37-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. measurement point is A. The

Figure 37-11 MEASUREMENT POINT OF BSS SENDING LLC_DISCARDED MESSAGE

Unit
Times

37.13 C901310012 Number of BVC-BLOCK message sent

Definition
Number of BVC-BLOCK message sent

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

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. measurement point is A2.
37-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

The

ZXG10 iBSC Performance Counter Reference

Figure 37-13 BVC_BLOCK PROCESS

Unit
Times

37.15 C901310014 Number of BVC-UNBLOCK message sent

Definition
Number of BVC-UNBLOCK message sent

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. measurement point is A1.
Figure 37-14 BVC_UNBLOCK PROCESS

The

Unit
Times
37-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

37.16 C901310015 Number of BVC-UNBLOCK-ACK message received

Definition
Number of BVC-UNBLOCK-ACK message received

Description
When SGSN receives the BVC_UNBLOCK message from BSS, it identifies the BVC to be unblocked and replies the BVC_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 measurement point is A2.
Figure 37-15 BVC_UNBLOCK PROCESS

Unit
Times

37.17 C901310016 Number of BVC-RESET message sent

Definition
Number of BVC-RESET message sent

Description
This counter counts the number of PCU sending signaling BVC resetting message through Gb interface.
37-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

37.18 C901310017 Number of BVC-RESET message received

Definition
Number of BVC-RESET message received

Description
This counter counts the number of PCU's receiving the signaling BVC resetting message.

Usage
The counter is used to find out cases when BVC is restarted.

Measurement Point
When NSE at BSC receives message of which the type is BVC_RESET and BVCI is zero, the counter increments. The measurement point is A1.

37-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

Figure 37-17 PROCESS OF RECEIVING BVC_RESET

Unit
Times

37.19 C901310018 Number of BVC-RESET-ACK 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

37.20 C901310019 Number of BVC-RESET-ACK 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

37-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

Description
When SGSN receives the location request and BSS supports LCS, SGSN will start the locating process and send PERFORM_LOCATION_REQUEST message to BSS. This counter counts the number of BSS's receiving the location request message.

Usage
The counter is used to find out the frequency of SGSN's sending location request to BSS.

Measurement Point
When BSS receives the PERFORM_LOCATION_REQUEST message, the counter increments. The measurement point is A1.
Figure 37-20 PERFORM_LOCATION_REQUEST PROCESS

Unit
Times

37.22 C901310021 Number of PERFORM_LOCATION_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.

37-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSS sends the PERFORM_LOCATION_RESPONSE message, the counter increments. The measurement point is A2.
Figure 37-21 PERFORM_LOCATION_REQUEST PROCESS

Unit
Times

37.23 C901310022 Number of PERFORM_LOCATION_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 increments. The measurement point is A.
Figure 37-22 MEASUREMENT POINT OF BSS RECEIVING PERFORM_LOCATION_ABORT MESSAGE

37-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

Unit
Times

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 measurement point is A1.
Figure 37-23 POSITION_COMMAND PROCESS

Unit
Times

37.25 C901310024 Number of POSITION_RESPONSE message received

Definition
Number of POSITION_RESPONSE message received
37-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. The measurement point is A2.
Figure 37-24 POSITION_COMMAND PROCESS

Unit
Times

37.26 C901310025 Number of status messages sent

Definition
Number of status messages sent

Description
When NSE receives downlink BSSGP PDU, if there is any abnormality, NSE will send the STATUS message to the opposite end entity. The STATUS message sent indicates causes of the abnormality: BVCI unknown, cell traffic congestion, Protocol error, Processor overload, Semantically incorrect PDU, Invalid mandatory information, Missing mandatory IE, or Missing conditional IE. This counter counts the number of abnormality that occurs.

Usage
The counter is used to find out abnormality occurring when NSE receives downlink BSSGP PDU.
37-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

Measurement Point
When NSE at BSC sends message of which the type is STATUS to opposite end entity, the counter increments. The measurement point is A1.
Figure 37-25 STATUS PROCESS

Unit
Times

37.27 C901310026 Number of status messages 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 37-26 STATUS PROCESS

Unit
Times

37.28 C901310027 Number of status messages sent 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

37.29 C901310028 Number of status messages sent with cell service congestion
Definition
Number of status messages sent with cell service congestion
37-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "cell traffic congestion".

Usage
The counter is used to find out the frequency of abnormality due to "cell traffic congestion" 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 "cell traffic congestion", the counter increments.

Unit
Times

37.30 C901310029 Number of status messages sent with protocol error

Definition
Number of status messages sent with protocol error

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Protocol error".

Usage
The counter is used to find out the frequency of abnormality due to "Protocol error" 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 "Protocol error", the counter increments.

Unit
Times

37-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

37.31 C901310030 Number of status messages sent with processor overload

Definition
Number of status messages sent with processor overload

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Processor overload".

Usage
The counter is used to find out the frequency of abnormality due to "Processor overload" 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 "Processor overload", the counter increments.

Unit
Times

37.32 C901310031 Number of status messages sent with semantically incorrect PDU
Definition
Number of status messages sent with semantically incorrect PDU

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Semantically incorrect PDU".

Usage
The counter is used to find out the frequency of abnormality due to "Semantically incorrect PDU" occurring when NSE receives downlink BSSGP PDU.

Measurement Point
When NSE sends the STATUS message to opposite end entity and the message indicates that the abnormality is due to "Semantically incorrect PDU", the counter increments.
37-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

Unit
Times

37.33 C901310032 Number of status messages sent with invalid mandatory information element
Definition
Number of status messages sent with invalid mandatory information element

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, 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
When NSE sends the STATUS message to opposite end entity and the message indicates that the abnormality is due to "Invalid mandatory information", the counter increments.

Unit
Times

37.34 C901310033 Number of status messages sent with missing mandatory IE

Definition
Number of status messages sent with missing mandatory IE

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When NSE sends the STATUS message to opposite end entity and the message indicates that the abnormality is due to "Missing mandatory IE", the counter increments.

Unit
Times

37.35 C901310034 Number of status messages sent with missing conditional IE

Definition
Number of status messages sent with missing conditional IE

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Missing conditional IE".

Usage
The counter is used to find out the frequency of abnormality due to "Missing conditional IE" 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 "Missing conditional IE", the counter increments.

Unit
Times

37.36 C901310035 Number of status messages sent with unexpected conditional IE

Definition
Number of status messages sent with unexpected conditional IE

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Unexpected conditional IE".

37-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

Usage
The counter is used to find out the frequency of abnormality due to "Unexpected conditional IE" 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 "Unexpected conditional IE", the counter increments.

Unit
Times

37.37 C901310036 Number of status messages sent with conditional IE error

Definition
Number of status messages sent with conditional IE error

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Conditional IE error".

Usage
The counter is used to find out the frequency of abnormality due to "Conditional IE error" 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 "Conditional IE error", the counter increments.

Unit
Times

37.38 C901310037 Number of status messages sent with protocol status incompatible error
Definition
Number of status messages sent with protocol status incompatible error

37-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, 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
When NSE sends the STATUS message to opposite end entity and the message indicates that the abnormality is due to "PDU not compatible with the protocol state", the counter increments.

Unit
Times

37.39 C901310038 Number of status messages 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
The counter is used to find out the frequency of abnormality due to "BVCI unknown" 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

37.40 C901310039 Number of status messages received with cell service congestion
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
The counter is used to find out the frequency of abnormality due to "cell traffic congestion" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "cell traffic congestion", the counter increments.

Unit
Times

37.41 C901310040 Number of status messages received with protocol error

Definition
Number of status messages received with protocol error

Description
This counter counts the number of received STATUS messages which indicate "Protocol error".

Usage
The counter is used to find out the frequency of abnormality due to "Protocol error" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "Protocol error", the counter increments.
37-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

37.42 C901310041 Number of status messages received with processor overload

Definition
Number of status messages received with processor overload

Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "Processor overload".

Usage
The counter is used to find out the frequency of abnormality due to "Processor overload" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "Processor overload", the counter increments.

Unit
Times

37.43 C901310042 Number of status messages received with BVC blocking

Definition
Number of status messages received with BVC blocking

Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "BVCI-blocked".

Usage
The counter is used to find out the frequency of abnormality due to "BVCI-blocked" occurring when SGSN receives downlink BSSGP PDU.

37-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

Measurement Point
When PCU receives STATUS message which indicates "BVCI-blocked", the counter increments.

Unit
Times

37.44 C901310043 Number of status messages 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
The counter is used to find out the frequency of abnormality due to "Semantically incorrect PDU" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "Semantically incorrect PDU", the counter increments.

Unit
Times

37.45 C901310044 Number of status messages 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
The counter is used to find out the frequency of abnormality due to "Invalid mandatory information" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "Invalid mandatory information", the counter increments.

Unit
Times

37.46 C901310045 Number of status messages 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
The counter is used to find out the frequency of abnormality due to "Missing mandatory 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

37.47 C901310046 Number of status messages received with missing conditional IE

Definition
Number of status messages received with missing conditional IE

37-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

Description
This counter counts the number of received STATUS messages which indicate "Missing conditional IE".

Usage
The counter is used to find out the frequency of abnormality due to "Missing conditional IE" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "Missing conditional IE", the counter increments.

Unit
Times

37.48 C901310047 Number of status messages received with unexpected conditional IE

Definition
Number of status messages received with unexpected conditional IE

Description
This counter counts the number of received STATUS messages which indicate "Unexpected conditional IE".

Usage
The counter is used to find out the frequency of abnormality due to "Unexpected conditional IE" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "Unexpected conditional IE", the counter increments.

Unit
Times

37-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

37.49 C901310048 Number of status messages received with conditional IE error

Definition
Number of status messages received with conditional IE error

Description
This counter counts the number of received STATUS messages which indicate "Conditional IE error".

Usage
The counter is used to find out the frequency of abnormality due to "Conditional IE error" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "Conditional IE error", the counter increments.

Unit
Times

37.50 C901310049 Number of status messages 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
The counter is used to find out the frequency of abnormality due to "PDU not compatible 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 37 NSE Statistic Measurement

Unit
Times

37.51 C901310050 Number of status messages received with SGSN congestion

Definition
Number of status messages received with SGSN congestion

Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "SGSN congestion".

Usage
The counter is used to find out the frequency of abnormality due to "SGSN congestion" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "SGSN congestion", the counter increments.

Unit
Times

37-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

37-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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-36 C901320035 Sum of Periodic BS Power (TCH/H) Search Result ...........................38-36 C901320036 Number of Periodic BS Power (TCH/H) Search .................................38-37
38-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901320037 Sum of Periodic BS Power (SDCCH) Search Result..........................38-37 C901320038 Number of Periodic BS Power (SDCCH) Search ...............................38-38 C901320039 Sum of Periodic DL Signal Level (TCH/F) Search Result...................38-38 C901320040 Number of Periodic DL Signal Level (TCH/F) Search ........................38-39 C901320041 Sum of Periodic DL Signal Level (TCH/H) Search Result ..................38-39 C901320042 Number of Periodic DL Signal Level (TCH/H) Search ........................38-40 C901320043 Sum of Periodic DL Signal Level (SDCCH) Search Result.................38-40 C901320044 Number of Periodic DL Signal Level (SDCCH) Search ......................38-41 C901320045 Number of BTS Power Increase Fails Due to Power Increase Freeze....................................................................................................................38-41 C901320046 Number of Uplink CIR Normal Grade0 (Below -2 dB) Samples..........38-42 C901320047 Number of Uplink CIR Normal Grade1 (-2 to 0.5 dB) Samples...........38-42 C901320048 Number of Uplink CIR Normal Grade2 (1 to 3.5 dB) Samples............38-43 C901320049 Number of Uplink CIR Normal Grade3 (4 to 6.5 dB) Samples............38-43 C901320050 Number of Uplink CIR Normal Grade4 (7 to 9.5 dB) Samples............38-44 C901320051 Number of Uplink CIR Normal Grade5 (10 to 12.5 dB) Samples........38-44 C901320052 Number of Uplink CIR Normal Grade6 (13 to 15.5 dB) Samples........38-45 C901320053 Number of Uplink CIR Normal Grade7 (16 to 18.5 dB) Samples........38-45 C901320054 Number of Uplink CIR Normal Grade8 (19 to 21.5 dB) Samples........38-46 C901320055 Number of Uplink CIR Normal Grade9 (Above 21.5 dB) Samples......38-46 C901320056 Number of Uplink CIR Improved Grade0 (Below -2 dB) Samples ......38-47 C901320057 Number of Uplink CIR Improved Grade1 (-2 to 0.5 dB) Samples .......38-47 C901320058 Number of Uplink CIR Improved Grade2 (1 to 3.5 dB) Samples ........38-48 C901320059 Number of Uplink CIR Improved Grade3 (4 to 6.5 dB) Samples ........38-48 C901320060 Number of Uplink CIR Improved Grade4 (7 to 9.5 dB) Samples ........38-49 C901320061 Number of Uplink CIR Improved Grade5 (10 to 12.5 dB) Samples.....38-49 C901320062 Number of Uplink CIR Improved Grade6 (13 to 15.5 dB) Samples.....38-50 C901320063 Number of Uplink CIR Improved Grade7 (16 to 18.5 dB) Samples.....38-50 C901320064 Number of Uplink CIR Improved Grade8 (19 to 21.5 dB) Samples.....38-51 C901320065 Number of Uplink CIR Improved Grade9 (Above 21.5 dB) Samples ..38-51 C901320070 Number of BTS Power Increase Due to Power Rescue .....................38-52 C901320071 Number of Channel Active BTS Power Change Due to Power Dynamic Share.......................................................................................................38-52

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.

38-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

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

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, and the counter increments.

38-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when BTS sends the message of increasing transmission power to MS. The measurement point is A1
Figure 38-2 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-002 Dynamic MS Power Control

38.3 C901320002 Number of rapid increase in MS power due to UL signal level

Definition
Number of rapid increase in MS power due to UL signal level

Description
In rapid power control, after BTS measures the uplink level and 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.

38-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Measurement Point
The counter counts when BTS sends the message of increasing transmission power to MS. The measurement point is A1.
Figure 38-3 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-002 Dynamic MS Power Control

38.4 C901320003 Number of normal decrease of MS power due to UL signal level

Definition
Number of normal decrease 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 decrease MS's transmission power, it sends the message of decreasing transmission power to MS, and the counter increments.

38-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when BTS sends the message of decreasing transmission power to MS. The measurement point is A1.
Figure 38-4 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-002 Dynamic MS Power Control

38.5 C901320004 Number of rapid decrease in MS power due to UL signal level

Definition
Number of rapid decrease 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 decrease MS's transmission power, it sends the message of decreasing transmission power to MS, and the counter increments.

38-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Measurement Point
The counter counts when BTS sends the message of decreasing transmission power to MS. The measurement point is A1.
Figure 38-5 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-002 Dynamic MS Power Control

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

38-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when BTS sends the message of increasing transmission power to itself. The measurement point is A2.
Figure 38-6 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

38.7 C901320006 Number of rapid increase in BS power due to DL signal level

Definition
Number of rapid increase in BS power due to DL signal level

Description
In rapid power control, after BTS receives the MS measurement 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.

38-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Measurement Point
The counter counts when BTS sends the message of increasing transmission power to itself. The measurement point is A2.
Figure 38-7 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

38.8 C901320007 Number of normal decrease of BS power due to DL signal level

Definition
Number of normal decrease of BS power due to DL signal level

Description
In common power control, after BTS receives the MS measurement report, it compares the MS's downlink receiving level with the configured downlink receiving level threshold according to the power control algorithm and makes decision. If BTS decides to decrease BTS's transmission power, it sends the message of decreasing transmission power to BTS, and the counter increments.

38-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when BTS sends the message of decreasing transmission power to itself. The measurement point is A2.
Figure 38-8 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

38.9 C901320008 Number of rapid decrease in BS power due to DL signal level

Definition
Number of rapid decrease in BS power due to DL signal level

Description
In rapid power control, after BTS receives the MS measurement report, it compares the MS's downlink receiving level with the configured downlink receiving level threshold according to the power control algorithm and makes decision. If BTS decides to decrease BTS's transmission power, it sends the message of decreasing transmission power to BTS, and the counter increments.

38-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Measurement Point
The counter counts when BTS sends the message of decreasing transmission power to itself. The measurement point is A2.
Figure 38-9 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

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
In common power control, after BTS measures the uplink level and quality of MS, it compares the MS's uplink quality with the configured uplink receiving quality threshold according to the power control algorithm and makes decision. If BTS decides to increase MS's transmission power, it sends the message of increasing transmission power to MS, and the counter increments.

38-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when BTS sends the message of increasing transmission power to MS. The measurement point is A1.
Figure 38-10 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-002 Dynamic MS Power Control

38.11 C901320010 Number of rapid increase in MS power due to UL signal quality

Definition
Number of rapid increase in MS power due to UL signal quality

Description
In rapid power control, after BTS measures the uplink level and quality of MS, it compares the MS's uplink quality with the configured uplink receiving quality threshold according to the power control algorithm and makes decision. If BTS decides to increase MS's transmission power, it sends the message of increasing transmission power to MS, and the counter increments.

38-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Measurement Point
The counter counts when BTS sends the message of increasing transmission power to MS. The measurement point is A1.
Figure 38-11 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-002 Dynamic MS Power Control

38.12 C901320011 Number of normal decrease of MS power due to UL signal quality

Definition
Number of normal decrease of MS power due to UL signal quality

Description
In common power control, after BTS measures the uplink level and quality of MS, it compares the MS's uplink quality with the configured uplink receiving quality threshold according to the power control algorithm and makes decision. If BTS decides to decrease MS's transmission power, it sends the message of decreasing transmission power to MS, and the counter increments.

38-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when BTS sends the message of decreasing transmission power to MS. The measurement point is A1.
Figure 38-12 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-002 Dynamic MS Power Control

38.13 C901320012 Number of rapid decrease in MS power due to UL signal quality

Definition
Number of rapid decrease in MS power due to UL signal quality

Description
In rapid power control, after BTS measures the uplink level and quality of MS, it compares the MS's uplink quality with the configured uplink receiving quality threshold according to the power control algorithm and makes decision. If BTS decides to decrease MS's transmission power, it sends the message of decreasing transmission power to MS, and the counter increments.

38-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Measurement Point
The counter counts when BTS sends the message of decreasing transmission power to MS. The measurement point is A1.
Figure 38-13 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-002 Dynamic MS Power Control

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
In common power control, after BTS receives the MS measurement report, it compares the MS's downlink receiving quality with the configured downlink receiving quality threshold according to the power control algorithm and makes decision. If BTS decides to increase BTS's transmission power, it sends the message of increasing transmission power to BTS, and the counter increments.

38-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when BTS sends the message of increasing transmission power to itself. The measurement point is A2.
Figure 38-14 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

38.15 C901320014 Number of rapid increase in BTS power due to DL signal quality
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 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.

38-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Measurement Point
The counter counts when BTS sends the message of increasing transmission power to itself. The measurement point is A2.
Figure 38-15 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

38.16 C901320015 Number of normal decrease of BS power due to DL signal quality

Definition
Number of normal decrease of BS power due to DL signal quality

Description
In common power control, after BTS receives the MS measurement report, it compares the MS's downlink receiving quality with the configured downlink receiving quality threshold according to the power control algorithm and makes decision. If BTS decides to decrease BTS's transmission power, it sends the message of decreasing transmission power to BTS, and the counter increments.

38-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when BTS sends the message of decreasing transmission power to itself. The measurement point is A2.
Figure 38-16 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

38.17 C901320016 Number of rapid decrease in BTS power due to DL signal quality
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 according to the power control algorithm and makes decision. If BTS decides to decrease BTS's transmission power, it sends the message of decreasing transmission power to BTS, and the counter increments.

38-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Measurement Point
The counter counts when BTS sends the message of decreasing transmission power to itself. The measurement point is A2.
Figure 38-17 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

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.
38-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 38-18 POWER CONTROL MEASUREMENT

Unit
Grade

Related Features
ZGO-04-02-002 Dynamic MS Power Control

38.19 C901320018 Number of regular scanning and 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.

38-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Figure 38-19 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-002 Dynamic MS Power Control

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 result to BSC, BTS may perform multiple periodical scannings. This counter accumulates the BTS utilization power value of each scanning.

Measurement Point
The counter accumulates when BTS performs periodical scanning. The measurement point is A3.

38-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 38-20 POWER CONTROL MEASUREMENT

Unit
Grade

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

38.21 C901320020 Number of regular scanning and 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 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.

38-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Figure 38-21 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

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
The counter counts when BTS performs periodical scanning. The measurement point is A3.

38-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 38-22 POWER CONTROL MEASUREMENT

Unit
Grade

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

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
The counter counts when BTS performs periodical scanning. The measurement point is A3.

38-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Figure 38-23 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

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
The counter counts when BTS performs periodical scanning. The measurement point is A3.

38-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 38-24 POWER CONTROL MEASUREMENT

Unit
Grade

Related Features
ZGO-04-02-002 Dynamic MS Power Control

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
The counter counts when BTS performs periodical scanning. The measurement point is A3.

38-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Figure 38-25 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-002 Dynamic MS Power Control

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
The counter counts when BTS performs periodical scanning. The measurement point is A3.

38-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 38-26 POWER CONTROL MEASUREMENT

Unit
Grade

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

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
The counter counts when BTS performs periodical scanning. The measurement point is A3.

38-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Figure 38-27 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

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
The counter counts when BTS performs periodical scanning. The measurement point is A3.

38-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 38-28 POWER CONTROL MEASUREMENT

Unit
Grade

Related Features
ZGO-04-02-002 Dynamic MS Power Control

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
The counter counts when BTS performs periodical scanning. The measurement point is A3.

38-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Figure 38-29 POWER CONTROL MEASUREMENT

Unit
Times

Related Features
ZGO-04-02-002 Dynamic MS Power Control

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.

38-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 38-30 POWER CONTROL MEASUREMENT

Unit
Grade

Related Features
ZGO-04-02-002 Dynamic MS Power Control

38.31 C901320030 Minimum value of UL signal level in regular scan

Definition
Minimum value of UL signal level in regular scan

Description
When BSC collects information of power control measurement counters, this counter records the minimum 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.

38-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Figure 38-31 POWER CONTROL MEASUREMENT

Unit
Grade

Related Features
ZGO-04-02-002 Dynamic MS Power Control

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
When BSC collects information of power control measurement counters, this counter records the maximum downlink 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.

38-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 38-32 POWER CONTROL MEASUREMENT

Unit
Grade

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

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
When BSC collects information of power control measurement counters, this counter records the minimum downlink 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.

38-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

Figure 38-33 POWER CONTROL MEASUREMENT

Unit
Grade

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

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
ZGO-04-02-001 Dynamic BTS Power Control
38-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-04-02-001 Dynamic BTS Power Control

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
ZGO-04-02-001 Dynamic BTS Power Control
38-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

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 contains BS power information, then the counter increments.

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

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
ZGO-04-02-001 Dynamic BTS Power Control
38-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 contains BS power information, then the counter increments.

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

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
ZGO-04-02-001 Dynamic BTS Power Control
38-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

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
ZGO-04-02-001 Dynamic BTS Power Control

38.42 C901320041 Sum of Periodic DL Signal Level (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
ZGO-04-02-001 Dynamic BTS Power Control
38-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

38.43 C901320042 Number of Periodic DL Signal Level (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 contains downlink signal level information, then the counter increments.

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

38.44 C901320043 Sum of Periodic DL Signal Level (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
ZGO-04-02-001 Dynamic BTS Power Control
38-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

38.45 C901320044 Number of Periodic DL Signal Level (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 contains downlink signal level information, then the counter increments.

Unit
Times

Related Features
ZGO-04-02-001 Dynamic BTS Power Control

38.46 C901320045 Number of BTS Power Increase Fails Due to Power Increase Freeze
Description
This counter counts the number of times that a BTS fails to increase the downlink power during a power increase freezing procedure.

Measurement Point
None

Unit
Times

38-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

38.47 C901320046 Number of Uplink CIR Normal Grade0 (Below -2 dB) Samples
Description
This counter counts the number of uplink CIR normal grade0 (below -2 dBm) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38.48 C901320047 Number of Uplink CIR Normal Grade1 (-2 to 0.5 dB) Samples
Description
This counter counts the number of uplink CIR normal grade1 (-2 to 0.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

38.49 C901320048 Number of Uplink CIR Normal Grade2 (1 to 3.5 dB) Samples
Description
This counter counts the number of uplink CIR normal grade2 (1 to 3.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38.50 C901320049 Number of Uplink CIR Normal Grade3 (4 to 6.5 dB) Samples
Description
This counter counts the number of uplink CIR normal grade3 (4 to 6.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

38.51 C901320050 Number of Uplink CIR Normal Grade4 (7 to 9.5 dB) Samples
Description
This counter counts the number of uplink CIR normal grade4 (7 to 9.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38.52 C901320051 Number of Uplink CIR Normal Grade5 (10 to 12.5 dB) Samples
Description
This counter counts the number of uplink CIR normal grade5 (10 to 12.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

38.53 C901320052 Number of Uplink CIR Normal Grade6 (13 to 15.5 dB) Samples
Description
This counter counts the number of uplink CIR normal grade6 (13 to 15.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38.54 C901320053 Number of Uplink CIR Normal Grade7 (16 to 18.5 dB) Samples
Description
This counter counts the number of uplink CIR normal grade7 (16 to 18.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

38.55 C901320054 Number of Uplink CIR Normal Grade8 (19 to 21.5 dB) Samples
Description
This counter counts the number of uplink CIR normal grade8 (19 to 21.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38.56 C901320055 Number of Uplink CIR Normal Grade9 (Above 21.5 dB) Samples
Description
This counter counts the number of uplink CIR normal grade9 (above 21.5 dBm) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

38.57 C901320056 Number of Uplink CIR Improved Grade0 (Below -2 dB) Samples
Description
This counter counts the number of uplink CIR improved grade0 (below -2 dBm) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38.58 C901320057 Number of Uplink CIR Improved Grade1 (-2 to 0.5 dB) Samples
Description
This counter counts the number of uplink CIR improved grade1 (-2 to 0.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

38.59 C901320058 Number of Uplink CIR Improved Grade2 (1 to 3.5 dB) Samples
Description
This counter counts the number of uplink CIR improved grade2 (1 to 3.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38.60 C901320059 Number of Uplink CIR Improved Grade3 (4 to 6.5 dB) Samples
Description
This counter counts the number of uplink CIR improved grade3 (4 to 6.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

38.61 C901320060 Number of Uplink CIR Improved Grade4 (7 to 9.5 dB) Samples
Description
This counter counts the number of uplink CIR improved grade4 (7 to 9.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38.62 C901320061 Number of Uplink CIR Improved Grade5 (10 to 12.5 dB) Samples
Description
This counter counts the number of uplink CIR improved grade5 (10 to 12.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

38.63 C901320062 Number of Uplink CIR Improved Grade6 (13 to 15.5 dB) Samples
Description
This counter counts the number of uplink CIR improved grade6 (13 to 15.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38.64 C901320063 Number of Uplink CIR Improved Grade7 (16 to 18.5 dB) Samples
Description
This counter counts the number of uplink CIR improved grade7 (16 to 18.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 38 BTS TRX Measurement

38.65 C901320064 Number of Uplink CIR Improved Grade8 (19 to 21.5 dB) Samples
Description
This counter counts the number of uplink CIR improved grade8 (19 to 21.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38.66 C901320065 Number of Uplink CIR Improved Grade9 (Above 21.5 dB) Samples
Description
This counter counts the number of uplink CIR improved grade9 (above 21.5 dB) samples reported in the measurement report by the BTS.

Usage
None

Measurement Point
None

Unit
Time

38-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

38.67 C901320070 Number of BTS Power Increase Due to Power Rescue

Description
This counter counts the number of times that the BTS initiates a downlink rescue power control to adjust its transmit power after detecting that the downlink receive level is lower than the downlink level threshold and the downlink receive quality is higher than the downlink quality threshold in a measurement report received from an MS.

Measurement Point
This counter is incremented each time the BTS, after receiving a measurement report from an MS, detects that the downlink measurement results meet the conditions for downlink rescue power control.

Unit
Number of times

38.68 C901320071 Number of Channel Active BTS Power Change Due to Power Dynamic Share
Description
When the dynamic power sharing function and the downlink power control function are enabled, the BTS decreases the initial downlink power to the transmit power P0, which has the same gain as the BCCH carrier, if the static power configured for the TCH carrier is the sum of the maximum transmit power and P (0.5 dB to 3 dB). During a downlink power control, the BTS dynamically increases the downlink transmit power to a value within the range from P0 to the sum when the following conditions are met after the filtering process: l l The downlink receive level is lower than the target threshold. The receive quality is higher than the target threshold.

This counter counts the number of times that the BTS dynamically increases the downlink transmit power to a value within the range from P0 to the sum of the maximum power and P.

Measurement Point
This counter is incremented each time the SDR determines to dynamically increase the downlink power.

Unit
Number of times
38-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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. Statistic unit in this measurement is NSVC.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Second

Related Features
ZGO-05-04-002 Gb over IP

39.3 C901330002 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 is not used for the time being.

Related Features
ZGO-05-04-002 Gb over IP

39.4 C901330003 Number of abnormal cases in NS transmission due to O&M interference

Definition
Number of abnormal cases in NS transmission due to O&M interference

Description
This counter is not used for the time being.

Related Features
ZGO-05-04-002 Gb over IP

39.5 C901330004 Number of abnormal cases in NS transmission due to equipment fault

Definition
Number of abnormal cases in NS transmission due to equipment fault

39-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 39 NSVC on IPGB HOST Measurement

Description
This counter is not used for the time being.

Related Features
ZGO-05-04-002 Gb over IP

39.6 C901330005 Number of abnormal cases in NS transmission due to unknown NSVC

Definition
Number of abnormal cases in NS transmission due to unknown NSVC

Description
This counter counts the number of abnormal cases in NS sub layer transmission due to unknown NSVC.

Measurement Point
During the NS sub layer signaling interaction, the counter accumulates the number of signaling transmitted by unknown NSVC.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

39.7 C901330006 Number of abnormal cases in NS transmission due to protocol error

Definition
Number of abnormal cases in NS transmission due to protocol error

Description
This counter counts the number of abnormal cases in NS sub layer transmission due to protocol error.

39-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When the field in NS signaling is inconsistent with that defined in protocol, the counter accumulates.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

39.8 C901330007 Number of unsuccess test due to over max

Definition
Number of unsuccess test due to over max

Description
This counters counts the number of test failure due to the maximum retransmission times being exceeded during the NS sub layer test procedure.

Measurement Point
When the number of NS sub layer's sending NS-ALIVE PDU exceeds the maximum retransmission times NS-ALIVE-RETRIES and there is no response, the counter increments. The measurement point is A1.
Figure 39-1 TEST PROCEDURE BEING ABNORMAL

Unit
Times
39-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 39 NSVC on IPGB HOST Measurement

Related Features
ZGO-05-04-002 Gb over IP

39-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

39-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40

GB Message on IPGB HOST Measurement

Table of Contents
Overview ..................................................................................................................40-2 C901340001 Number of RA-CAPABILITY message recevied...................................40-2 C901340002 Number of PTP packet paging received by BSC..................................40-3 C901340003 Number of PTP circuit paging received by BSC...................................40-4 C901340004 Number of RA-CAPABILITY-UPDATE message sent...........................40-4 C901340005 Number of RA-CAPABILITY-UPDATE-ACK message received............40-5 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 C901340014 Number of FLOW-CONTROL-PFC messages sent by BSC ..............40-12 C901340015 Number of FLOW-CONTROL-PFC-ACK messages received by BSC .......................................................................................................................40-13 C901340016 Number of status messages sent by BSC .........................................40-13 C901340017 Number of status messages received by BSC ...................................40-14 C901340018 Number of status messages sent with BVCI Unknown ......................40-15 C901340019 Number of status messages sent with cell service congestion ...........40-15 C901340020 Number of status messages sent with protocol error .........................40-16 C901340021 Number of status messages sent with Processor overload ................40-16 C901340022 Number of status messages received with BVCI Unknown................40-17 C901340023 Number of status messages received with cell service congestion ....40-18 C901340024 Number of status messages received with protocol error...................40-18 C901340025 Number of status messages received with processor overload..........40-19 C901340026 Number of DOWNLOAD-BSS-PFC messages sent by BSC ..............40-19 C901340027 Number of BVCCREATE-BSS-PFC messages received by BSC.......40-20 C901340028 Number of CREATE-BSS-PFC-ACK messages sent by BSC ............40-21 C901340029 Number of CREATE-BSS-PFC-NACK messages sent by BSC..........40-22
40-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901340030 Number of MODIFY-BSS-PFC messages sent by BSC .....................40-23 C901340031 Number of MODIFY-BSS-PFC-ACK messages received by BSC ......40-24 C901340032 Number of DELETE-BSS-PFC messages received by BSC ..............40-25 C901340033 Number of DELETE-BSS-PFC-ACK messages sent by BSC.............40-25 C901340034 Number of DELETE-BSS-PFC-REQ messages received by BSC......40-26 C901340035 Number of PS-HANDOVER-REQUIRED messages sent by BSC......40-26 C901340036 Number of PS-HANDOVER-REQUIRED-ACK messages received by BSC .......................................................................................................................40-27 C901340037 Number of PS-HANDOVER-REQUIRED-NACK messages received by BSC...................................................................................................................40-28 C901340038 Number of PS-HANDOVER-REQUEST messages received by BSC .40-29 C901340039 Number of PS-HANDOVER-REQUEST-ACK messages sent by BSC .......................................................................................................................40-30 C901340040 Number of PS-HANDOVER-REQUEST-NACK messages sent by BSC .......................................................................................................................40-31 C901340041 Number of PS-HANDOVER-COMPLETE messages sent by BSC.....40-33 C901340042 Number of PS-HANDOVER-CANCEL messages sent by BSC..........40-34 C901340043 Number of PS-HANDOVER-REQUEST messages with Service UTRAN CCO received by BSC...............................................................................40-34 C901340044 Number of CREATE-BSS-PFC messages with Service UTRAN CCO received by BSC ....................................................................................................40-35

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. Statistic unit in this measurement is cell.

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
When BSC receives a RA-CAPABILITY message, this counter increments. measurement point is A.
40-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

The

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
ZGO-05-04-002 Gb over IP

40.3 C901340002 Number of PTP packet paging 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
When BSC receives a PAGING PS message, this counter increments. The measurement point is A.
Figure 40-2 PTP PACKET PAGING PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP
40-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

40.4 C901340003 Number of PTP circuit paging 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
When BSC receives a PAGING CS message, this counter increments. The measurement point is A.
Figure 40-3 PTP CIRCUIT PAGING PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.5 C901340004 Number of RA-CAPABILITY-UPDATE 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

Measurement Point
When BSC sends a RA-CAPABILITY-UPDATE message to SGSN, this counter increments. The measurement point is A1.
Figure 40-4 RA-CAPABILITY-UPDATE PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.6 C901340005 Number of RA-CAPABILITY-UPDATE-ACK message received

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 counter increments. The measurement point is A2.
Figure 40-5 RA-CAPABILITY-UPDATE PROCESS

40-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.7 C901340006 Number of wireless status PDU messages sent by BSC

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
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 measurement point is A.
Figure 40-6 RADIO-STATUS PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

40.8 C901340007 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 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
The radio interface status can be checked by counting this message.

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
ZGO-05-04-002 Gb over IP

40.9 C901340008 Number of wireless status messages sent by BSC due to bad link quality
Definition
Number of wireless status messages sent by BSC due to bad link quality

Description
BSC sends the wireless status message to indicate SGSN that abnormality occurs at radio interface. This counter counts the number of BSC's sending this message due to bad link quality.

40-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
The radio interface status can be checked by counting this message.

Measurement Point
When BSC sends a RADIO-STATUS message to SGSN due to bad link quality, this counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.10 C901340009 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
BSC sends the wireless status message to indicate SGSN that abnormality occurs at radio interface. This counter counts the number of BSC's sending this message due to cell reselection command.

Usage
The radio interface status can be checked by counting this message.

Measurement Point
When BSC sends a RADIO-STATUS message to SGSN due to cell reselection command, this counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

40.11 C901340010 Number of FLOW-CONTROL-BVC messages sent by BSC

Definition
Number of FLOW-CONTROL-BVC messages sent by BSC

Description
BSC sends the FLOW-CONTROL-BVC message to notify SGSN of the current BVC flow control policy. This counter counts the number of BSC's sending this message.

Measurement Point
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
ZGO-05-04-002 Gb over IP

40.12 C901340011 Number of FLOW-CONTROL-BVC-ACK messages received by BSC

Definition
Number of FLOW-CONTROL-BVC-ACK messages received by BSC

40-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
SGSN sends the FLOW-CONTROL-BVC-ACK message to notify BSC that the current BVC flow control policy is accepted. This counter counts the number of BSC's receiving this message.

Measurement Point
When BSC receives a FLOW-CONTROL-BVC-ACK message, this counter increments. The measurement point is A2.
Figure 40-8 FLOW-CONTROL-BVC PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.13 C901340012 Number of FLOW-CONTROL-MS messages sent by BSC

Definition
Number of FLOW-CONTROL-MS messages sent by BSC

Description
BSC sends the FLOW-CONTROL-MS message to notify SGSN of the current MS flow control policy. This counter counts the number of BSC's sending this message.

Measurement Point
When BSC sends the FLOW-CONTROL-MS message, this counter increments. The measurement point is A1.

40-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

Figure 40-9 FLOW-CONTROL-MS PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.14 C901340013 Number of FLOW-CONTROL-MS-ACK messages received by BSC

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. The measurement point is A2.
Figure 40-10 FLOW-CONTROL-MS PROCESS

40-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.15 C901340014 Number of FLOW-CONTROL-PFC messages sent by BSC

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 sending this message.

Measurement Point
When BSC sends the FLOW-CONTROL-PFC message, this counter increments. The measurement point is A1.
Figure 40-11 FLOW-CONTROL-PFC PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

40.16 C901340015 Number of FLOW-CONTROL-PFC-ACK messages received by BSC

Definition
Number of FLOW-CONTROL-PFC-ACK messages received by BSC

Description
SGSN sends the FLOW-CONTROL-PFC-ACK message to notify BSC that the PFC flow control policy for designated MS is accepted. This counter counts the number of BSC's receiving this message.

Measurement Point
When BSC receives a FLOW-CONTROL-PFC-ACK message, this counter increments. The measurement point is A2.
Figure 40-12 FLOW-CONTROL-PFC PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.17 C901340016 Number of status messages sent by BSC

Definition
Number of status messages sent by BSC

40-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 is A1.
Figure 40-13 STATUS PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.18 C901340017 Number of status messages received by BSC

Definition
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 point is A2.

40-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

Figure 40-14 STATUS PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.19 C901340018 Number of status messages sent with BVCI Unknown

Definition
Number of status messages sent with BVCI Unknown

Description
BSC sends the status message to SGSN to indicate that abnormality occurs. This counter 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
ZGO-05-04-002 Gb over IP

40.20 C901340019 Number of status messages sent with cell service congestion
Definition
Number of status messages sent with cell service congestion
40-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
BSC sends the status message to SGSN to indicate that abnormality occurs. This counter 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
ZGO-05-04-002 Gb over IP

40.21 C901340020 Number of status messages sent with protocol error

Definition
Number of status messages sent with protocol error

Description
BSC sends the status message to SGSN to indicate that abnormality occurs. This counter 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
ZGO-05-04-002 Gb over IP

40.22 C901340021 Number of status messages sent with Processor overload

Definition
Number of status messages sent with Processor overload
40-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

Description
BSC sends the status message to SGSN to indicate that abnormality occurs. This counter 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
ZGO-05-04-002 Gb over IP

40.23 C901340022 Number of status messages received with BVCI Unknown

Definition
Number of status messages received with BVCI Unknown

Description
BSC sends the status message to SGSN to indicate that abnormality occurs. This counter counts the number of BSC's receiving this message due to BVCI Unknown.

Measurement Point
When BSC receives a "STATUS" message due to BVCI Unknown, this counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

40.24 C901340023 Number of status messages received with cell service congestion
Definition
Number of status messages received with cell service congestion

Description
SGSN sends the status message to BSC to indicate that abnormality occurs. This counter 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
ZGO-05-04-002 Gb over IP

40.25 C901340024 Number of status messages received with protocol error

Definition
Number of status messages received with protocol error

Description
SGSN sends the status message to BSC to indicate that abnormality occurs. This counter 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
ZGO-05-04-002 Gb over IP
40-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

40.26 C901340025 Number of status messages received with processor overload

Definition
Number of status messages received with processor overload

Description
BSC sends the status message to SGSN to indicate that abnormality occurs. This counter counts the number of BSC's receiving this message due to processor overload.

Measurement Point
When BSC receives a "STATUS" message due to processor overload, this counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.27 C901340026 Number of DOWNLOAD-BSS-PFC messages sent by BSC

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 measurement point is A1.

40-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 40-15 CREATE-BSS-PFC PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.28 C901340027 Number of BVCCREATE-BSS-PFC messages received by BSC

Definition
Number of BVCCREATE-BSS-PFC messages received by BSC

Description
SGSN sends the CREATE-BSS-PFC message to request BSC to create or modify a packet flow control context. This counter counts the number of BSC's receiving this message.

Measurement Point
When BSC receives a CREATE-BSS-PFC message, this counter increments. The measurement point is A2.

40-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

Figure 40-16 CREATE-BSS-PFC PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.29 C901340028 Number of CREATE-BSS-PFC-ACK messages sent by BSC

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
When BSC sends a CREATE-BSS-PFC-ACK message, this counter increments. The measurement point is A3.

40-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 40-17 CREATE-BSS-PFC PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.30 C901340029 Number of CREATE-BSS-PFC-NACK messages sent by BSC

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 sending this message.

Measurement Point
When BSC sends a CREATE-BSS-PFC-NACK message, this counter increments. The measurement point is A4.

40-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

Figure 40-18 CREATE-BSS-PFC PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.31 C901340030 Number of MODIFY-BSS-PFC messages sent by BSC

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. measurement point is A1.
Figure 40-19 MODIFY-BSS-PFC PROCESS

The

40-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.32 C901340031 Number of MODIFY-BSS-PFC-ACK messages received by BSC

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
When BSC receives a MODIFY-BSS-PFC-ACK message, this counter increments. The measurement point is A2.
Figure 40-20 MODIFY-BSS-PFC PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

40.33 C901340032 Number of DELETE-BSS-PFC messages received by BSC

Definition
Number of DELETE-BSS-PFC messages received by BSC

Description
SGSN sends the DELETE-BSS-PFC message to request BSC to delete a packet flow control context. This counter counts the number of BSC's receiving this message.

Measurement Point
When BSC receives a DELETE-BSS-PFC message, this counter increments. measurement point is A1.
Figure 40-21 DELETE-BSS-PFC PROCESS

The

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.34 C901340033 Number of DELETE-BSS-PFC-ACK messages sent by BSC

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-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC sends a DELETE-BSS-PFC-ACK message, this counter increments. The measurement point is A2.
Figure 40-22 DELETE-BSS-PFC PROCESS

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

40.35 C901340034 Number of DELETE-BSS-PFC-REQ messages received by BSC

Definition
Number of DELETE-BSS-PFC-REQ messages received by BSC

Description
This counter is not used for the time being.

Related Features
ZGO-05-04-002 Gb over IP

40.36 C901340035 Number of PS-HANDOVER-REQUIRED messages sent by BSC

Statistics object
BSC

40-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

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

40.37 C901340036 Number of PS-HANDOVER-REQUIRED-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-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 40-24 Measurement Point of Number of PS-HANDOVER-REQUIRED-ACK messages received by BSC

Times

40.38 C901340037 Number of PS-HANDOVER-REQUIRED-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 shown in Figure 40-25.

40-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

Figure 40-25 Measurement Point of Number of PS-HANDOVER-REQUIRED-NACK messages received by BSC

Times

40.39 C901340038 Number of PS-HANDOVER-REQUEST 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 measurement point is A2, as shown in Figure 40-26.

40-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 40-26 Measurement Point of Number of PS-HANDOVER-REQUEST messages received by BSC

Times

40.40 C901340039 Number of PS-HANDOVER-REQUEST-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-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

Figure 40-27 Measurement Point of Number of PS-HANDOVER-REQUEST-ACK messages sent by BSC

Times

40.41 C901340040 Number of PS-HANDOVER-REQUEST-NACK messages sent by BSC

Statistics object
BSC
40-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 messages sent by BSC

Times
40-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

40.42 C901340041 Number of PS-HANDOVER-COMPLETE 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 shown in Figure 40-29.
Figure 40-29 Measurement Point of Number of PS-HANDOVER-COMPLETE messages sent by BSC

Times

40-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

40.43 C901340042 Number of PS-HANDOVER-CANCEL messages sent by BSC

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 in IP transmission mode. The counter increments when BSC sends the PS-HANDOVER-CANCEL message. The measurement point is A, as shown in Figure 40-30.
Figure 40-30 Measurement Point of Number of PS-HANDOVER-CANCEL messages sent by BSC

Times

40.44 C901340043 Number of PS-HANDOVER-REQUEST messages with Service UTRAN CCO received by BSC
Statistics object
BSC
40-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 40 GB Message on IPGB HOST Measurement

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 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 40-31.
Figure 40-31 Measurement Point of Number of PS-HANDOVER-REQUEST messages with Service UTRAN CCO received by BSC

Times

40.45 C901340044 Number of CREATE-BSS-PFC messages with Service UTRAN CCO received by BSC
Statistics object
BSC

40-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
When BSC receives the CREATE-BSS-PFC message from SGSN, the message might contain the field Service UTRAN CCO. This counter counts the number of CREATE-BSS-PFC messages, which contains the field Service UTRAN CCO, received by BSC in IP transmission mode. After BSC receives the CREATE-BSS-PFC message from SGSN, it decodes the message to decide whether the message contains the field Service UTRAN CCO. If the message contains the field, the counter increments. The measurement point is A, as shown in Figure 40-32.
Figure 40-32 Measurement Point of Number of CREATE-BSS-PFC messages with Service UTRAN CCO received by BSC

Times

40-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 C901350003 Number of SUSPEND message sent ..................................................41-3 C901350004 Number of SUSPEND-ACK message received....................................41-4 C901350005 Number of SUSPEND-NACK message received .................................41-5 C901350006 Number of RESUME message sent ....................................................41-5 C901350007 Number of RESUME-ACK message received .....................................41-6 C901350008 Number of RESUME-NACK message received ...................................41-7 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 C901350027 Number of status messages sent with BVCI Unknown ......................41-19 C901350028 Number of status messages sent with cell service congestion ...........41-19 C901350029 Number of status messages sent with protocol error .........................41-20 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 C901350039 Number of status messages received with cell service congestion ....41-27 C901350040 Number of status messages received with protocol error...................41-27 C901350041 Number of status messages received with processor overload..........41-28 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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
ZGO-05-04-002 Gb over IP

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
ZGO-05-04-002 Gb over IP

41.4 C901350003 Number of SUSPEND message sent

Definition
Number of SUSPEND message sent

41-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-04-002 Gb over IP

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

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

Related Features
ZGO-05-04-002 Gb over IP

41.6 C901350005 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 sends the SUSPEND_NACK message, the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

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

41-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-04-002 Gb over IP

41.8 C901350007 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 messages received by NSE.

Usage
The counter is used to find out causes due to which SGSN has no response when MS requests for resuming GPRS service.

Measurement Point
When BSS sends the RESUME_ACK message, the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

41.9 C901350008 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 is, unknown MS. At this moment, BSS will terminate the RESUME process and ask MS to update routing area. This counter counts the number of RESUME_NACK messages received by NSE.

Usage
The counter is used to find out cases in which SGSN has no response when MS requests for resuming GPRS service.

Measurement Point
When BSS receives the RESUME_NACK message, the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSS receives the FLUSH_LL message, the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

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
ZGO-05-04-002 Gb over IP

41.12 C901350011 Number of LLC-DISCARDED message sent

Definition
Number of LLC-DISCARDED message sent
41-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

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
ZGO-05-04-002 Gb over IP

41.13 C901350012 Number of BVC-BLOCK message sent

Definition
Number of BVC-BLOCK message sent

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
ZGO-05-04-002 Gb over IP
41-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-04-002 Gb over IP

41.15 C901350014 Number of BVC-UNBLOCK message sent

Definition
Number of BVC-UNBLOCK message sent

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.16 C901350015 Number of BVC-UNBLOCK-ACK message received

Definition
Number of BVC-UNBLOCK-ACK message received

Description
When SGSN receives the BVC_UNBLOCK message from BSS, it identifies the BVC to be unblocked and replies the BVC_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
ZGO-05-04-002 Gb over IP

41.17 C901350016 Number of BVC-RESET message sent

Definition
Number of BVC-RESET message sent

Description
This counter counts the number of PCU sending signaling BVC resetting message through Gb interface.
41-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
The counter is used to find out the frequency of requesting to restart BVC due to BVC failure.

Measurement Point
When NSE at BSC sends message of which the type is BVC_RESET and BVCI is zero, the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.18 C901350017 Number of BVC-RESET message received

Definition
Number of BVC-RESET message received

Description
This counter counts the number of PCU's receiving the signaling BVC resetting message.

Usage
The counter is used to find out cases when BVC is restarted.

Measurement Point
When NSE at BSC receives message of which the type is BVC_RESET and BVCI is zero, the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

41.19 C901350018 Number of BVC-RESET-ACK 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
ZGO-05-04-002 Gb over IP

41.20 C901350019 Number of BVC-RESET-ACK 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-04-002 Gb over IP

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
When BSS receives the PERFORM_LOCATION_REQUEST message, the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

41.22 C901350021 Number of PERFORM-LOCATION-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 receives the PERFORM_LOCATION_REQUEST message, the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.23 C901350022 Number of PERFORM-LOCATION-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.
41-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSS receives the PERFORM_LOCATION_REQUEST message, the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

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
ZGO-05-04-002 Gb over IP

41-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

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
ZGO-05-04-002 Gb over IP

41.26 C901350025 Number of status messages sent

Definition
Number of status messages sent

Description
When NSE receives downlink BSSGP PDU, if there is any abnormality, NSE will send the STATUS message to the opposite end entity. The STATUS message sent indicates causes of the abnormality: BVCI unknown, cell traffic congestion, Protocol error, Processor overload, Semantically incorrect PDU, Invalid mandatory information, Missing mandatory IE, or Missing conditional IE. This counter counts the number of abnormality that occurs.

41-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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, the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.27 C901350026 Number of status messages 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
ZGO-05-04-002 Gb over IP
41-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

41.28 C901350027 Number of status messages sent 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

Related Features
ZGO-05-04-002 Gb over IP

41.29 C901350028 Number of status messages sent with cell service congestion
Definition
Number of status messages sent with cell service congestion

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "cell traffic congestion".

Usage
The counter is used to find out the frequency of abnormality due to "cell traffic congestion" occurring when NSE receives downlink BSSGP PDU.

41-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When NSE sends the STATUS message to opposite end entity and the message indicates that the abnormality is due to "cell traffic congestion", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.30 C901350029 Number of status messages sent with protocol error

Definition
Number of status messages sent with protocol error

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Protocol error".

Usage
The counter is used to find out the frequency of abnormality due to "Protocol error" 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 "Protocol error", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

41.31 C901350030 Number of status messages sent with processor overload

Definition
Number of status messages sent with processor overload

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Processor overload".

Usage
The counter is used to find out the frequency of abnormality due to "Processor overload" 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 "Processor overload", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.32 C901350031 Number of status messages sent with semantically incorrect PDU
Definition
Number of status messages sent with semantically incorrect PDU

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Semantically incorrect PDU".

Usage
The counter is used to find out the frequency of abnormality due to "Semantically incorrect PDU" occurring when NSE receives downlink BSSGP PDU.

41-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When NSE sends the STATUS message to opposite end entity and the message indicates that the abnormality is due to "Semantically incorrect PDU", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.33 C901350032 Number of status messages sent with invalid mandatory information element
Definition
Number of status messages sent with invalid mandatory information element

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, 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
When NSE sends the STATUS message to opposite end entity and the message indicates that the abnormality is due to "Invalid mandatory information", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

41.34 C901350033 Number of status messages sent with missing mandatory IE

Definition
Number of status messages sent with missing mandatory IE

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, 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.

Measurement Point
When NSE sends the STATUS message to opposite end entity and the message indicates that the abnormality is due to "Missing mandatory IE", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.35 C901350034 Number of status messages sent with missing conditional IE

Definition
Number of status messages sent with missing conditional IE

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Missing conditional IE".

Usage
The counter is used to find out the frequency of abnormality due to "Missing conditional IE" occurring when NSE receives downlink BSSGP PDU.

41-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When NSE sends the STATUS message to opposite end entity and the message indicates that the abnormality is due to "Missing conditional IE", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.36 C901350035 Number of status messages sent with unexpected conditional IE

Definition
Number of status messages sent with unexpected conditional IE

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Unexpected conditional IE".

Usage
The counter is used to find out the frequency of abnormality due to "Unexpected conditional IE" 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 "Unexpected conditional IE", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

41.37 C901350036 Number of status messages sent with conditional IE error

Definition
Number of status messages sent with conditional IE error

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Conditional IE error".

Usage
The counter is used to find out the frequency of abnormality due to "Conditional IE error" 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 "Conditional IE error", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.38 C901350037 Number of status messages sent with protocol status incompatible error
Definition
Number of status messages sent with protocol status incompatible error

Description
This counter counts the number of NSE's sending STATUS message to opposite end entity, 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.

41-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When NSE sends the STATUS message to opposite end entity and the message indicates that the abnormality is due to "PDU not compatible with the protocol state", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.39 C901350038 Number of status messages 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
The counter is used to find out the frequency of abnormality due to "BVCI unknown" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "BVCI unknown", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

41.40 C901350039 Number of status messages received with cell service congestion
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
The counter is used to find out the frequency of abnormality due to "cell traffic congestion" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "cell traffic congestion", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.41 C901350040 Number of status messages received with protocol error

Definition
Number of status messages received with protocol error

Description
This counter counts the number of received STATUS messages which indicate "Protocol error".

Usage
The counter is used to find out the frequency of abnormality due to "Protocol error" occurring when SGSN receives downlink BSSGP PDU.

41-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When PCU receives STATUS message which indicates "Protocol error", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.42 C901350041 Number of status messages received with processor overload

Definition
Number of status messages received with processor overload

Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "Processor overload".

Usage
The counter is used to find out the frequency of abnormality due to "Processor overload" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "Processor overload", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

41.43 C901350042 Number of status messages received with BVC blocking

Definition
Number of status messages received with BVC blocking

Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "BVCI-blocked".

Usage
The counter is used to find out the frequency of abnormality due to "BVCI-blocked" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "BVCI-blocked", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.44 C901350043 Number of status messages 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
The counter is used to find out the frequency of abnormality due to "Semantically incorrect PDU" occurring when SGSN receives downlink BSSGP PDU.

41-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When PCU receives STATUS message which indicates "Semantically incorrect PDU", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.45 C901350044 Number of status messages 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
The counter is used to find out the frequency of abnormality due to "Invalid mandatory information" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "Invalid mandatory information", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

41.46 C901350045 Number of status messages 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
The counter is used to find out the frequency of abnormality due to "Missing mandatory 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

Related Features
ZGO-05-04-002 Gb over IP

41.47 C901350046 Number of status messages received with missing conditional IE

Definition
Number of status messages received with missing conditional IE

Description
This counter counts the number of received STATUS messages which indicate "Missing conditional IE".

Usage
The counter is used to find out the frequency of abnormality due to "Missing conditional IE" occurring when SGSN receives downlink BSSGP PDU.

41-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When PCU receives STATUS message which indicates "Missing conditional IE", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.48 C901350047 Number of status messages received with unexpected conditional IE

Definition
Number of status messages received with unexpected conditional IE

Description
This counter counts the number of received STATUS messages which indicate "Unexpected conditional IE".

Usage
The counter is used to find out the frequency of abnormality due to "Unexpected conditional IE" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "Unexpected conditional IE", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 41 NSE on IPGB HOST Measurement

41.49 C901350048 Number of status messages received with conditional IE error

Definition
Number of status messages received with conditional IE error

Description
This counter counts the number of received STATUS messages which indicate "Conditional IE error".

Usage
The counter is used to find out the frequency of abnormality due to "Conditional IE error" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "Conditional IE error", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.50 C901350049 Number of status messages 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
The counter is used to find out the frequency of abnormality due to "PDU not compatible with the protocol state" occurring when SGSN receives downlink BSSGP PDU.

41-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When PCU receives STATUS message which indicates "PDU not compatible with the protocol state", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41.51 C901350050 Number of status messages received with SGSN congestion

Definition
Number of status messages received with SGSN congestion

Description
This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "SGSN congestion".

Usage
The counter is used to find out the frequency of abnormality due to "SGSN congestion" occurring when SGSN receives downlink BSSGP PDU.

Measurement Point
When PCU receives STATUS message which indicates "SGSN congestion", the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

41-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 C901360086 Number of Release Clear Request on SDCCH..................................42-74 C901360087 Number of Release Clear Request on TCH/F ....................................42-74 C901360088 Number of Release Clear Request on TCH/H ...................................42-75

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 messages received by BSC.

Usage
The counter is used to find out the frequency of assignment request messages transmitted at A-interface.

Measurement Point
When BSC receives the ASSIGNMENT REQUEST message, the counter increments. The measurement point is A.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 increments. The measurement point is A.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A.

42-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 increments. The measurement point is A.
Figure 42-7 MEASUREMENT POINT OF BSC SENDING RESOURCE INDICATION MESSAGE TO MSC

42-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Description
When MSC decides to modify the cipher mode of channel, it sends a CIPHER MODE COMMAND message to BSC through A-interface. This counter counts the number of CIPHER MODE COMMAND messages in A-interface BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of CIPHER MODE COMMAND messages transmitted at A-interface.

Measurement Point
When BSC receives the CIPHER MODE COMMAND message, the 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 transmitted at A-interface.
42-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC sends the CIPHER MODE COMPLETE message to MSC, the counter increments. The measurement point is A.
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 transmitted at A-interface.

Measurement Point
When BSC sends the CIPHER MODE REJECT message to MSC, the counter increments. The measurement point is A.

42-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 A-interface BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the sending frequency of CLASSMARK UPDATE messages transmitted at A-interface.

Measurement Point
When BSC sends the CLASSMARK UPDATE message to MSC, the counter increments. The measurement point is A.
Figure 42-12 MEASUREMENT POINT OF BSC SENDING CLASSMARK UPDATE MESSAGE TO MSC

42-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 transmitted at A-interface.

Measurement Point
When BSC sends the QUEUING INDICATION message to MSC, the counter increments. The measurement point is A.
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 A-interface BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of COMPLETE LAYER 3 INFORMATION messages transmitted at A-interface.
42-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC sends the COMPLETE LAYER 3 INFORMATION message to MSC, the counter increments. The measurement point is A.
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 transmitted at A-interface.

Measurement Point
When BSC receives the CLASSMARK REQUEST message, the counter increments. The measurement point is A.

42-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 measurement point is A.
Figure 42-17 MEASUREMENT POINT OF BSC SENDING LOAD INDICATION MESSAGE TO MSC

42-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 messages received by BSC.

Usage
The counter is used to find out the frequency of downlink load indication messages transmitted at A-interface.

Measurement Point
When BSC receives the LOAD INDICATION message, the counter increments. The measurement point is A.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 measurement point is A.
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 transmitted at A-interface.

42-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC sends the HANDOVER REQUIRED message to MSC, the counter increments. The measurement point is A1.
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 BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of HANDOVER COMMAND messages transmitted at A-interface.

42-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Measurement Point
When BSC receives the HANDOVER COMMAND message, the counter increments. The measurement point is A4.
Figure 42-21 INTER-BSC HANDOVER PROCESS INITIATED BY BSC

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 transmitted at A-interface.

42-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC sends the HANDOVER REQUEST ACK message to MSC, the counter increments. The measurement point is A3.
Figure 42-22 INTER-BSC HANDOVER PROCESS INITIATED BY BSC

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 in A-interface BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of HANDOVER COMPLETE messages transmitted at A-interface.

Measurement Point
When BSC sends the HANDOVER COMPLETE message to MSC, the counter increments. The measurement point is A5.
42-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Figure 42-23 INTER-BSC HANDOVER PROCESS INITIATED BY BSC

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 in A-interface BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of HANDOVER SUCCEEDED messages transmitted at A-interface.

Measurement Point
When BSC receives the HANDOVER SUCCEEDED message, the counter increments. The measurement point is A6.

42-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 42-24 INTER-BSC HANDOVER PROCESS INITIATED BY BSC

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 messages received by BSC.

Usage
The counter is used to find out the frequency of HANDOVER CANDIDATE ENQUIRE messages transmitted at A-interface.

Measurement Point
When BSC receives the HANDOVER CANDIDATE ENQUIRE message, the counter increments. The measurement point is A1.

42-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 A-interface BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of HANDOVER CANDIDATE RESPONSE messages transmitted at A-interface.

Measurement Point
When BSC sends the HANDOVER CANDIDATE RESPONSE message to MSC, the counter increments. The measurement point is A2.

42-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 transmitted at A-interface.

Measurement Point
When BSC sends the HANDOVER FAILURE message to MSC, the counter increments. The measurement point is A.
Figure 42-27 MEASUREMENT POINT OF BSC SENDING HANDOVER FAILURE MESSAGE TO MSC

Unit
Times
42-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 transmitted at A-interface.

Measurement Point
When BSC sends the HANDOVER PERFORMED message to MSC, the counter increments. The measurement point is A.
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 A-interface BSSMAP messages received by BSC.
42-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
The counter is used to find out the frequency of HANDOVER REQUIRED REJECT messages transmitted at A-interface.

Measurement Point
When BSC receives the HANDOVER REQUIRED REJECT message, the counter increments. The measurement point is A.
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 BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of HANDOVER DETECT messages transmitted at A-interface.

Measurement Point
When BSC sends the HANDOVER DETECT message to MSC, the counter increments. The measurement point is A.

42-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 A-interface BSSMAP messages received by BSC.

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 measurement point is A1.
Figure 42-31 CLEAR PROCESS

Unit
Times
42-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A2.
Figure 42-32 CLEAR PROCESS

Unit
Times

42.32 C901360031 Number of CLEAR REQUEST messages

Definition
Number of CLEAR REQUEST messages

42-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Description
BSC sends the CLEAR REQUEST message to MSC, asking MSC to release the conneciton. This counter counts the number of CLEAR REQUEST messages in A-interface BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of CLEAR REQUEST messages transmitted at A-interface.

Measurement Point
When BSC sends the CLEAR REQUEST message to MSC, the counter increments. The measurement point is A.
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 messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of SAPI "N" REJECT messages transmitted at A-interface.

42-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC sends the SAPI "N" REJECT message to MSC, the counter increments. The measurement point is A.
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 A-interface BSSMAP messages sent to MSC from BSC.

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 measurement point is A.

42-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 A-interface BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of downlink CONFUSION messages transmitted at A-interface.

Measurement Point
When BSC receives the CONFUSION message, the counter increments. measurement point is A. The

Figure 42-36 MEASUREMENT POINT OF MSC SENDING CONFUSION MESSAGE TO BSC

Unit
Times
42-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. measurement point is A1.
Figure 42-37 UPLINK RESET PROCESS

The

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of uplink RESET ACKNOWLEDGE messages transmitted at A-interface.

Measurement Point
When BSC sends the RESET ACKNOWLEDGE message to MSC, the counter increments. The measurement point is A2.
42-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 42-39 DOWNLINK RESET PROCESS

Unit
Times

42.39 C901360038 Number of DL RESET ACKNOWLEDGE messages

Definition
Number of DL RESET ACKNOWLEDGE messages

Description
When BSC detects that it has serious global fault, it will send a RESET message to MSC. After MSC receives the message, it releases all calls and relevant information, and after a period of time, it returns the RESET ACKNOWLEDGE message as response. This counter counts the number of RESET ACKNOWLEDGE messages in A-interface BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of downlink RESET ACKNOWLEDGE messages transmitted at A-interface.

Measurement Point
When BSC receives the RESET ACKNOWLEDGE message, the counter increments. The measurement point is A2.
Figure 42-40 UPLINK RESET PROCESS

42-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 messages sent to MSC from BSC.

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. measurement point is A. 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
When MSC detects that its processor is overloaded, it will send the OVERLOAD message to the BSC under it. If the overload problem persists, MSC will send the OVERLOAD message to BSC periodically. This counter counts the number of OVERLOAD messages in A-interface BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of downlink OVERLOAD messages transmitted at A-interface.

Measurement Point
When BSC receives the OVERLOAD message, the counter increments. measurement point is A. 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 messages received by BSC.

Usage
The counter is used to find out the frequency of MSC INVOKE TRACE messages transmitted at A-interface.
42-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Measurement Point
When BSC receives the MSC INVOKE TRACE message, the counter increments. The measurement point is A.
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 messages sent by BSC.

Usage
The counter is used to find out the frequency of sending BSS INVOKE TRACE messages transmitted at A-interface.

Measurement Point
When BSC sends the BSS INVOKE TRACE message to MSC, the counter increments. The measurement point is A.

42-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of receiving BSS INVOKE TRACE messages transmitted at A-interface.

Measurement Point
When BSC receives the BSS INVOKE TRACE message, the counter increments. The measurement point is A.
Figure 42-45 MEASUREMENT POINT OF MSC SENDING BSS INVOKE TRACE MESSAGE TO BSC

Unit
Times
42-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 increments. The measurement point is A.
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 A-interface BSSMAP messages received by BSC.
42-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
The counter is used to find out the frequency of receiving CONNECTIONLESS INFORMATION messages transmitted at A-interface.

Measurement Point
When BSC receives the CONNECTIONLESS INFORMATION message, the counter increments. The measurement point is A.
Figure 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 BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of SUSPEND messages transmitted at A-interface.

Measurement Point
When BSC sends the SUSPEND message to MSC, the counter increments. measurement point is A. The

42-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 messages sent to MSC from BSC.

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. measurement point is A. The

Figure 42-49 MEASUREMENT POINT OF BSC SENDING RESUME MESSAGE TO MSC

Unit
Times

42-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 messages received by BSC.

Usage
The counter is used to find out the frequency of Common ID messages transmitted at A-interface.

Measurement Point
When BSC receives the Common ID message, the counter increments. The measurement point is A.
Figure 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 A-interface BSSMAP messages received by BSC.
42-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 measurement point is A.
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 A-interface BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of PERFORM LOCATION REQUEST messages transmitted at A-interface.

Measurement Point
When BSC receives the PERFORM LOCATION REQUEST message, the counter increments. The measurement point is A1.

42-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 42-52 PROCESS OF MSC SENDING PERFORM LOCATION REQUEST MESSAGE TO BSC

Unit
Times

42.52 C901360051 Number of PERFORM LOCATION RESPONSE messages

Definition
Number of PERFORM LOCATION RESPONSE messages

Description
This counter counts the number of PERFORM LOCATION RESPONSE messages in A-interface BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of PERFORM LOCATION RESPONSE messages transmitted at A-interface.

Measurement Point
When BSC sends the PERFORM LOCATION RESPONSE message to MSC, the counter increments. The measurement point is A2.
Figure 42-53 PROCESS OF MSC SENDING PERFORM LOCATION REQUEST MESSAGE TO BSC

42-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Unit
Times

42.53 C901360052 Number of PERFORM LOCATION ABORT messages

Definition
Number of PERFORM LOCATION ABORT messages

Description
This counter counts the number of PERFORM LOCATION ABORT messages in A-interface BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of PERFORM LOCATION ABORT messages transmitted at A-interface.

Measurement Point
When BSC receives the PERFORM LOCATION ABORT message, the counter increments. The measurement point is A.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
When BSC decides to block a terrestrial circuit of A-interface, it sends a BLOCK message to MSC. This counter counts the number of BLOCK messages in A-interface BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of sending BLOCK messages transmitted at A-interface.

Measurement Point
When BSC sends the BLOCK message to MSC, the counter increments. measurement point is A1.
Figure 42-55 PROCESS OF BSC SENDING BLOCK MESSAGE TO MSC

The

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 BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of receiving BLOCK ACK messages transmitted at A-interface.
42-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Measurement Point
When BSC receives the BLOCK ACK message, the counter increments. measurement point is A2.
Figure 42-56 PROCESS OF BSC SENDING BLOCK MESSAGE TO MSC

The

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 BSSMAP messages sent to MSC from BSC.

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. measurement point is A1. The

42-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 A-interface BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of receiving UNBLOCK ACK messages transmitted at A-interface.

Measurement Point
When BSC receives the UNBLOCK ACK message, the counter increments. measurement point is A2.
Figure 42-58 PROCESS OF BSC SENDING UNBLOCK MESSAGE TO MSC

The

42-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 messages received by BSC.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
When MSC decides to block a terrestrial circuit of A-interface, it sends a BLOCK message to BSC. BSC performs appropriate handling and returns a BLOCK ACK message as response. This counter counts the number of BLOCK ACK messages in A-interface BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of sending BLOCK ACK messages transmitted at A-interface.

Measurement Point
When BSC sends the BLOCK ACK message to MSC, the counter increments. The measurement point is A2.
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 BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of receiving UNBLOCK messages transmitted at A-interface.
42-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 A-interface BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of sending UNBLOCK ACK messages transmitted at A-interface.

Measurement Point
When BSC sends the UNBLOCK ACK message to MSC, the counter increments. The measurement point is A2.

42-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 transmitted at A-interface.

Measurement Point
When BSC sends the RESET CIRCUIT message to MSC, the counter increments. The measurement point is A1.
Figure 42-63 PROCESS OF BSC SENDING RESET CIRCUIT MESSAGE TO MSC

42-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 transmitted at A-interface.

Measurement Point
When BSC receives the RESET CIRCUIT message, the counter increments. measurement point is A1.
Figure 42-64 PROCESS OF MSC SENDING RESET CIRCUIT MESSAGE TO BSC

The

Unit
Times

42.64 C901360063 Number of UL RESET CIRCUIT ACK messages

Definition
Number of UL RESET CIRCUIT ACK messages
42-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
When MSC detects that an abnormal SCCP connection release causes a circuit to become idle, it sends a RESET CIRCUIT message to BSC. After BSC receives the message, it clears relevant calls and makes corresponding circuits to become idle, and sends a RESET CIRCUIT ACK message to MSC. This counter counts the number of RESET CIRCUIT ACK messages in A-interface BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of uplink RESET CIRCUIT ACK messages transmitted at A-interface.

Measurement Point
When BSC sends the RESET CIRCUIT ACK message to MSC, the counter increments. The measurement point is A2.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Usage
The counter is used to find out the frequency of downlink RESET CIRCUIT ACK messages transmitted at A-interface.

Measurement Point
When BSC receives the RESET CIRCUIT ACK message, the counter increments. The measurement point is A2.
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 in A-interface BSSMAP messages sent to MSC from BSC.

Usage
The counter is used to find out the frequency of uplink CIRCUIT GROUP BLOCK messages transmitted at A-interface.

Measurement Point
When BSC sends the CIRCUIT GROUP BLOCK message to MSC, the counter increments. The measurement point is A1.
42-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 in A-interface BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of downlink CIRCUIT GROUP BLOCK messages transmitted at A-interface.

Measurement Point
When BSC receives the CIRCUIT GROUP BLOCK message, the counter increments. The measurement point is A1.
Figure 42-68 PROCESS OF MSC SENDING CIRCUIT GROUP BLOCK MESSAGE TO BSC

42-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Unit
Times

42.68 C901360067 Number of UL CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages

Definition
Number of UL CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages

Description
When MSC decides to block some terrestrial circuits of A-interface 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 messages sent to MSC from BSC.

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, the counter increments. The measurement point is A2.
Figure 42-69 PROCESS OF MSC SENDING CIRCUIT GROUP BLOCK MESSAGE TO BSC

Unit
Times

42-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

42.69 C901360068 Number of DL CIRCUIT GROUP 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 BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of downlink CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages transmitted at A-interface.

Measurement Point
When BSC receives the CIRCUIT GROUP BLOCKING ACKNOWLEDGE message, the counter increments. The measurement point is A2.
Figure 42-70 PROCESS OF BSC SENDING CIRCUIT GROUP BLOCK MESSAGE TO MSC

Unit
Times

42.70 C901360069 Number of UL CIRCUIT GROUP UNBLOCK messages

Definition
Number of UL CIRCUIT GROUP UNBLOCK messages
42-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 messages transmitted at A-interface.

Measurement Point
When BSC sends the CIRCUIT GROUP UNBLOCK message to MSC, the counter increments. The measurement point is A1.
Figure 42-71 PROCESS OF BSC SENDING CIRCUIT GROUP UNBLOCK MESSAGE TO MSC

Unit
Times

42.71 C901360070 Number of DL CIRCUIT GROUP UNBLOCK messages

Definition
Number of DL CIRCUIT GROUP UNBLOCK messages

Description
When MSC decides to unblock some terrestrial circuit of A-interface, it sends a CIRCUIT GROUP UNBLOCK message to BSC. This counter counts the number of CIRCUIT GROUP UNBLOCK messages in A-interface BSSMAP messages received by BSC.

Usage
The counter is used to find out the frequency of downlink CIRCUIT GROUP UNBLOCK messages transmitted at A-interface.
42-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC receives the CIRCUIT GROUP UNBLOCK message, the counter increments. The measurement point is A1.
Figure 42-72 PROCESS OF MSC SENDING CIRCUIT GROUP UNBLOCK MESSAGE TO BSC

Unit
Times

42.72 C901360071 Number of UL CIRCUIT GROUP 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 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 UNBLOCKING ACKNOWLEDGE messages transmitted at A-interface.

Measurement Point
When BSC sends the CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message to MSC, the counter increments. The measurement point is A2.

42-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Figure 42-73 PROCESS OF MSC SENDING CIRCUIT GROUP UNBLOCK MESSAGE TO BSC

Unit
Times

42.73 C901360072 Number of DL CIRCUIT GROUP 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 ACKNOWLEDGE messages transmitted at A-interface.

Measurement Point
When BSC receives the CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message, the counter increments. The measurement point is A2.

42-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 transmitted at A-interface.

Measurement Point
When BSC sends the UNEQUIPPED CIRCUIT message to MSC, the counter increments. The measurement point is A.
Figure 42-75 MEASUREMENT POINT OF BSC SENDING UNEQUIPPED CIRCUIT MESSAGE TO MSC

42-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 messages transmitted at A-interface.

Measurement Point
When BSC receives the UNEQUIPPED CIRCUIT message, the counter increments. The measurement point is A.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A1.
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 BSSMAP messages received by BSC.
42-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Usage
The counter is used to find out the frequency of CHANGE CIRCUIT ACK messages transmitted at A-interface.

Measurement Point
When BSC sends the CHANGE CIRCUIT ACK message to MSC, the counter increments. The measurement point is A2.
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 BSSMAP messages received by BSC.

Usage
The counter is used to find out cases of BSC receiving the HANDOVER PERFORMED ACK message from MSC.

Measurement Point
When BSC receives the HANDOVER PERFORMED ACK message from MSC, the counter increments.
42-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A1, as shown in Figure 42-79. Times

42-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Figure 42-79 Measurement Point of the Count of Sending INTERNAL HANDOVER REQUIRED

Reference
3GPP TS 48008

42-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. The measurement point is A2, as shown in Figure 42-80. Times

42-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Figure 42-80 Measurement Point of the Count of Receiving INTERNAL HANDOVER COMMAND

Reference
3GPP TS 48008

42-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. The measurement point is A1, as shown in Figure 42-81. 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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, the counter increments. The measurement point is A, as shown in Figure 42-83.

42-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 42-83 OMCR Initiating IP Resource Resetting Flow

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 increments. The measurement point is A, as shown in Figure 42-84.
Figure 42-84 MSC Initiating IP Resource Resetting Flow

Unit
Times

42-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

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 shown in Figure 42-85.
Figure 42-85 MSC Initiating IP Resource Resetting Flow

Unit
Times

Reference
3GPP TS 48008

42.86 C901360085 Number of DL RESET IP RESOURCE ACKNOWLEDGE messages

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 .
Figure 42-86 OMCR Initiating IP Resource Resetting Flow

Unit
Times

42.87 C901360086 Number of Release Clear Request on SDCCH

Description
This counter is incremented each time a clear request is initiated by the BSC when the SDCCH is occupied by an MS.

Usage
This counter is available in later versions of V6.20.200a.

Measurement Point
None

Unit
Times

42.88 C901360087 Number of Release Clear Request on TCH/F

Description
This counter is incremented each time a clear request is initiated by the BSC when the TCH/F is occupied by an MS.
42-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 42 BSSMAP Message Measurement

Usage
None

Measurement Point
None

Unit
Times

42.89 C901360088 Number of Release Clear Request on TCH/H

Description
This counter is incremented each time a clear request is initiated by the BSC when the TCH/H is occupied by an MS.

Usage
None

Measurement Point
None

Unit
Times

42-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

42-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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-4 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 C901370008 Number of Chosen for MSC by NRI.....................................................43-6 C901370009 Number of Chosen for MSC by Paging Source....................................43-7 C901370010 Number of Chosen for MSC Load Share by IMSI ................................43-8 C901370011 Number of Chosen for MSC Load Share by IMEI.................................43-8 C901370012 Number of Chosen for MSC Load Share by Reselect MSC .................43-9

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 A-interface BSSMAP messages sent to MSC from BSC.

43-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
The counter analyzes the frequency of uplink DTAP messages transmitted at A-interface.

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.

43-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 43 A-Interface Message Measurement

Figure 43-2 MEASUREMENT POINT OF MSC SENDING A-INTERFACE DTAP MESSAGE TO BSC

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-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

43.5 C901370004 Number of DL BSSMAP messages

Definition
Number of DL BSSMAP messages

Description
This counter counts the number of BSSMAP messages received by BSC from MSC. MSC can carry the BSSMAP message in the Connection Indication message, Connection Confirm message, Data Indication message, and UnitData Indication message.

Usage
The counter analyzes the frequency of downlink BSSMAP messages 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.
43-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 43 A-Interface Message Measurement

Usage
The counter analyzes the frequency of received incorrect BSSMAP messages transmitted at A-interface.

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 within the measurement period.

Usage
This counter is used to find out the frequency that the original serving MSC in the pool allocates NULL_NRI to MS to make a MSC actively shares the load.

Measurement Point
The counter counts when iBSC chooses an appropriate MSC route for MS access.

Unit
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

43-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of a MSC being chosen for load sharing by non-NULL_NRI within the measurement period.

Usage
This counter is used to find out the frequency of a MSC's sharing load due to MS accessing the network through NRI which is not of the MSC.

Measurement Point
The counter counts when iBSC chooses an appropriate MSC route for MS access.

Unit
Times

43.9 C901370008 Number of Chosen for MSC by NRI

Description
In FLEXA networking mode, the BSC receives the link establishment indication message EST_IND from the BTS. The message is not a paging response and it carries TMSI. The corresponding MSC of the NRI is in the available state. The service is distributed to certain MSC in the MSCPOOL. This counter is updated when the BSC sends the COMP_LAYER3 message to the MSC.

Usage
None

Measurement Point
The measurement point is shown in Figure 43-5.

43-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 43 A-Interface Message Measurement

Figure 43-5 Number of Choosing MSC by NRI

Unit
Time

43.10 C901370009 Number of Chosen for MSC by Paging Source

Description
In FLEXA networking mode, the BSC receives the link establishment indication message EST_IND from the BTS. The BSC distributes the service to the MSC in the MSCPOOL that initiates paging when the BSC detects that the message is the paging response. This counter is updated when the BSC sends the COMP_LAYER3 message to the MSC.

Usage
None

Measurement Point
The measurement point is shown in Figure Number of Choosing MSC by NRI.

Unit
Time

43-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

43.11 C901370010 Number of Chosen for MSC Load Share by IMSI

Description
In FLEXA networking mode, the BSC receives the link establishment indication message EST_IND from the BTS. The message is not a paging response and it carries IMSI. The service is distributed to certain MSC in the MSCPOOL in the load sharing mode. This counter is updated when the BSC sends the COMP_LAYER3 message to the MSC.

Usage
None

Measurement Point
The measurement point is shown in Figure Number of Chosen for MSC by NRI.

Unit
Time

43.12 C901370011 Number of Chosen for MSC Load Share by IMEI

Description
In FLEXA networking mode, the BSC receives the link establishment indication message EST_IND from the BTS. The message is not a paging response and it carries IMEI. The service is distributed to certain MSC in the MSCPOOL in the load sharing mode. This counter is updated when the BSC sends the COMP_LAYER3 message to the MSC.

Usage
None

Measurement Point
The measurement point is shown in Figure Number of Chosen for MSC by NRI.

Unit
Time

43-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 43 A-Interface Message Measurement

43.13 C901370012 Number of Chosen for MSC Load Share by Reselect MSC
Description
In FLEXA networking mode, the BSC receives the link establishment indication message EST_IND from the BTS. The message is not a paging response and it carries TMSI. The corresponding MSC of the NRI is in the unavailable state. The service is distributed to certain MSC in the MSCPOOL in the load sharing mode. This counter is updated when the BSC sends the COMP_LAYER3 message to the MSC.

Usage
None

Measurement Point
The measurement point is shown in Figure Number of Chosen for MSC by NRI.

Unit
Time

43-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

43-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 C901380016 The times of User Plane transport without RTP multiplexing..............44-12 C901380017 The times of RTP multiplexing applied without RTP header compression...........................................................................................................44-13 C901380018 The times of RTP multiplexing applied with RTP header compression...........................................................................................................44-14 C901380019 Mean number of busy trunk circuits ...................................................44-15 C901380020 Mean number of seizure UDP port ....................................................44-16

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The counter counts when system periodically queries database for circuit information.

Unit
Times

44-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 l 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. Before the trunk circuit is released, if the maximum number of busy trunk circuits exceeds the recorded value, then the counter's value is updated. During periodical measurement, if the maximum number of busy trunk circuits exceeds the recorded value, then the counter's value is updated.

Unit
Times

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

l l l

Before the trunk circuit is occupied successfully, the counter calculates the occupation time and accumulates. Before the trunk circuit is released, the counter calculates the occupation time and accumulates. During periodical measurement, the counter calculates the occupation time and accumulates.

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 l 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. Before the trunk circuit is released, if the congestion identifier is set, then the counter calculates the congestion time and accumulates. During periodical measurement, if the congestion identifier is set, then the counter calculates the congestion time and accumulates.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 44 Terrestrial Resource Availability Measurement

Usage
The counter is used to find out the average number of available UDP ports.

Measurement Point
The counter counts when system periodically queries database for circuit information.

Unit
Times

Related Features
ZGO-05-04-003 A over IP

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
The counter counts when system periodically queries database for circuit information.

Unit
Times

Related Features
ZGO-05-04-003 A over IP

44.9 C901380008 Number of allocation AIPB board success

Definition
Number of allocation AIPB board success
44-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-04-003 A over IP

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 44 Terrestrial Resource Availability Measurement

Measurement Point
When the request of AIPB board from database fails, the counter accumulates. The measurement point is A.
Figure 44-2 REQUESTING RESOURCE FROM DATABASE FAILURE

Unit
Times

Related Features
ZGO-05-04-003 A over IP

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
The counter counts at the following time points. l l 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. Before the UDP port is released, if the maximum number of busy UDP ports exceeds the recorded value, then the counter's value is updated. During periodical measurement, if the maximum number of busy UDP ports exceeds the recorded value, then the counter's value is updated.
44-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-05-04-003 A over IP

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

Usage
The counter is used to find out the frequency of successfully requesting AIPB board for UDP port through only one request.

Measurement Point
When the connection succeeds and the requesting AIPB board for UDP port succeeds through only one request, the counter accumulates. The measurement point is A
Figure 44-3 REQUESTING RESOURCE FROM DATABASE SUCCESSFULLY

44-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 44 Terrestrial Resource Availability Measurement

Unit
Times

Related Features
ZGO-05-04-003 A over IP

44.13 C901380012 Number of successful two time request UDP port to AIPB
Definition
Number of successful two time request UDP port to AIPB

Description
This counter counts the number of successfully requesting AIPB board for UDP port through two requests. 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 two, then the counter accumulates.

Usage
The counter is used to find out the frequency of successfully requesting AIPB board for UDP port through two requests.

Measurement Point
When the connection succeeds and the requesting AIPB board for UDP port succeeds after two requests, the counter accumulates. The measurement point is A.
Figure 44-4 REQUESTING RESOURCE FROM DATABASE SUCCESSFULLY

44-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-05-04-003 A over IP

44.14 C901380013 Number of successful three time request UDP port to AIPB
Definition
Number of successful three time request UDP port to AIPB

Description
This counter counts the number of successfully requesting AIPB board for UDP port through three requests. 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 three, then the counter accumulates.

Usage
The counter is used to find out the frequency of successfully requesting AIPB board for UDP port through three requests.

Measurement Point
When the connection succeeds and the requesting AIPB board for UDP port succeeds after three requests, the counter accumulates. The measurement point is A.
Figure 44-5 REQUESTING RESOURCE FROM DATABASE SUCCESSFULLY

44-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 44 Terrestrial Resource Availability Measurement

Unit
Times

Related Features
ZGO-05-04-003 A over IP

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. 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_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. measurement point is A.
Figure 44-6 REQUESTING RESOURCE FROM DATABASE FAILURE

The

Unit
Times
44-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-05-04-003 A over IP

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
The counter counts at the following time points. l l l Before UDPPort is occupied successfully, the counter calculates the occupation time and accumulates. Before UDPPort is released, the counter calculates the occupation time and accumulates. During periodical measurement, the counter calculates the occupation time and accumulates.

Unit
Second

Related Features
ZGO-05-04-003 A over IP

44.17 C901380016 The times of User Plane transport without RTP multiplexing
Description
When IP A mode is adopted, BSC and MGW negotiate the RTP transmission mode of user plane at A-interface. If BSC or MGW does not enable the RTP multiplexing mode for transmission, or if the RTP multiplexing modes used at BSC and MGW are not consistent, then the message at UDP port of A-interface will not be transmitted in RTP multiplexing mode.
44-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 44 Terrestrial Resource Availability Measurement

Usage
This counter counts the number of user plane not applying RTP multiplexing mode in AoIP call at BSC side. This counter is supported in version V6.20.61 or later.

Measurement Point
After the call is established, BSC and MGW negotiate the RTP transmission mode. When control plane receives the RTP_MUX_RPT message from user plane, if the RTP multiplexing mode is not applied, the counter counts. The measurement point is A, as shown in Figure 44-7.
Figure 44-7 The times of User Plane transport without RTP multiplexing

Unit
Times

44.18 C901380017 The times of RTP multiplexing applied without RTP header compression
Description
When IP A mode is adopted, BSC and MGW negotiate the RTP transmission mode of user plane at A-interface. If both BSC and MGW support RTP multiplexing and the negotiation succeeds, then the message at UDP port of A-interface will be transmitted in RTP multiplexing mode.

Usage
This counter counts the number of user plane applying RTP multiplexing mode in AoIP call at BSC side. This counter is supported in version V6.20.61 or later.

Measurement Point
After the call is established, BSC and MGW negotiate the RTP transmission mode. When control plane receives the RTP_MUX_RPT message from user plane, if the RTP

44-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

multiplexing mode is applied, the counter counts. The measurement point is A, as shown in Figure 44-8.
Figure 44-8 The times of RTP multiplexing applied without RTP header compression

Unit
Times

44.19 C901380018 The times of RTP multiplexing applied with RTP header compression
Description
When IP A mode is adopted, BSC and MGW negotiate the RTP transmission mode of user plane at A-interface. If both BSC and MGW support compressed RTP multiplexing and the negotiation succeeds, then the message at UDP port of A-interface will be transmitted in compressed RTP multiplexing mode.

Usage
This counter counts the number of user plane applying compressed RTP multiplexing mode in AoIP call at BSC side. This counter is supported in version V6.20.61 or later.

Measurement Point
After the call is established, BSC and MGW negotiate the RTP transmission mode. When control plane receives the RTP_MUX_RPT message from user plane, if the compressed RTP multiplexing mode is applied, the counter counts. The measurement point is A, as shown in Figure 44-9.
Figure 44-9 The times of RTP multiplexing applied with RTP header compression

44-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 44 Terrestrial Resource Availability Measurement

Unit
Times

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

Usage
This counter is used to find out the occupation of trunk circuits. This counter is supported in version V6.20.200a or above.

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-10.
Figure 44-10 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-11.

44-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 44-11 Standby umc Database Being Released

Unit
Times

44.21 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. This counter is supported in version V6.20.200a or above.

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

44-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 44 Terrestrial Resource Availability Measurement

Figure 44-12 OMS Reporting Data to Database

Unit
Times

44-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

44-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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
ZGO-05-02-005 Flex Ater

45-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-02-005 Flex Ater

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
ZGO-05-02-005 Flex Ater
45-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 45 Ater Message Measurement

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
ZGO-05-02-005 Flex Ater

45.7 C901390006 Number of UL BLOCKING Ater single CIRCUIT ACKNOWLEDGE messages

Definition
Number of UL BLOCKING Ater single CIRCUIT ACKNOWLEDGE messages

Description
This counter counts the number of BLOCKING ACKNOWLEDGE messages sent by BSC to iTC.

Measurement Point
When BSC sends a BLOCKING ACKNOWLEDGE message, this counter increments.

Unit
Times

Related Features
ZGO-05-02-005 Flex Ater

45-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-02-005 Flex Ater

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
ZGO-05-02-005 Flex Ater
45-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 45 Ater Message Measurement

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
ZGO-05-02-005 Flex Ater

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
ZGO-05-02-005 Flex Ater

45-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

45.12 C901390011 Number of UL RESET Ater CIRCUIT ACKNOWLEDGE messages

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
ZGO-05-02-005 Flex Ater

45.13 C901390012 Number of DL RESET Ater CIRCUIT ACKNOWLEDGE messages

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
ZGO-05-02-005 Flex Ater
45-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 45 Ater Message Measurement

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
ZGO-05-02-005 Flex Ater

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
ZGO-05-02-005 Flex Ater
45-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-02-005 Flex Ater

45.17 C901390016 Number of DL BLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages

Definition
Number of DL BLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages

Description
This counter counts the number of BLOCKING CIRCUIT GROUP ACKNOWLEDGE messages received by BSC from iTC.

Measurement Point
When BSC receives a BLOCKING CIRCUIT GROUP ACKNOWLEDGE message, this counter increments.

Unit
Times

Related Features
ZGO-05-02-005 Flex Ater
45-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 45 Ater Message Measurement

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
ZGO-05-02-005 Flex Ater

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
ZGO-05-02-005 Flex Ater
45-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

45.20 C901390019 Number of UL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages

Definition
Number of UL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages

Description
This counter counts the number of UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE messages sent by BSC to iTC.

Measurement Point
When BSC sends an UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE message, this counter increments.

Unit
Times

Related Features
ZGO-05-02-005 Flex Ater

45.21 C901390020 Number of DL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages

Definition
Number of DL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages

Description
This counter counts the number of UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE messages received by BSC from iTC.

Measurement Point
When BSC receives an UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE message, this counter increments.

Unit
Times

Related Features
ZGO-05-02-005 Flex Ater
45-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 45 Ater Message Measurement

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
ZGO-05-02-005 Flex Ater

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
ZGO-05-02-005 Flex Ater
45-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 ACKNOWLEDGE messages

Definition
Number of DL BLOCKING A CIRCUIT ACKNOWLEDGE messages

Description
This counter counts the number of BLOCKING A CIRCUIT ACKNOWLEDGE messages received by BSC from iTC.

Measurement Point
When BSC receives a BLOCKING A CIRCUIT ACKNOWLEDGE message, this counter increments.

Unit
Times

45.26 C901390025 Number of UL UNBLOCK A CIRCUIT messages

Definition
Number of UL UNBLOCK A CIRCUIT messages
45-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 45 Ater Message Measurement

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 CIRCUIT ACKNOWLEDGE messages

Definition
Number of DL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages

Description
This counter counts the number of UNBLOCKING A CIRCUIT ACKNOWLEDGE messages received by BSC from iTC.

Measurement Point
When BSC receives an UNBLOCKING A CIRCUIT ACKNOWLEDGE 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

45.29 C901390028 Number of UL BLOCKING A CIRCUIT ACKNOWLEDGE messages

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 45 Ater Message Measurement

45.31 C901390030 Number of UL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages

Definition
Number of UL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages

Description
This counter counts the number of UNBLOCKING A CIRCUIT ACKNOWLEDGE messages sent by BSC to iTC.

Measurement Point
When BSC sends an UNBLOCKING A CIRCUIT ACKNOWLEDGE 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 messages sent by BSC to iTC.

Measurement Point
When BSC sends a BLOCKING A CIRCUIT GROUP ACKNOWLEDGE message, this counter increments.

Unit
Times

45-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 45 Ater Message Measurement

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 messages received by BSC from iTC.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 messages sent by BSC to iTC.

Measurement Point
When BSC sends an UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE message, this counter increments.

Unit
Times

45-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 45 Ater Message Measurement

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 messages received by BSC from iTC.

Measurement Point
When BSC receives an UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE message, this counter increments.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-02-005 Flex Ater

45.43 C901390042 Number of DL Ater RESET messages

Definition
Number of DL Ater RESET messages
45-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 45 Ater Message Measurement

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
ZGO-05-02-005 Flex Ater

45.44 C901390043 Number of UL Ater RESET ACKNOWLEDGE messages

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
ZGO-05-02-005 Flex Ater

45.45 C901390044 Number of DL Ater RESET ACKNOWLEDGE messages

Definition
Number of DL Ater RESET ACKNOWLEDGE messages

45-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-02-005 Flex Ater

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
ZGO-05-02-005 Flex Ater

45.47 C901390046 Number of DL Ater CONFUSION messages

Definition
Number of DL Ater CONFUSION messages

45-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 45 Ater Message Measurement

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
ZGO-05-02-005 Flex Ater

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 received by BSC from iTC.
45-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 messages received by BSC from iTC.

Measurement Point
When BSC receives a RESOURCE REQUEST NEGTIVE ACKNOWLEDGE message, this counter increments.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 45 Ater Message Measurement

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 received by BSC from iTC.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 45 Ater Message Measurement

Measurement Point
When BSC sends a TFO CONTROL INFORMATION message, this counter increments.

Unit
Times

45-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

45-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 46 MTP2 Signal Link Measurement

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 46 MTP2 Signal Link Measurement

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

46.15 C901400014 Number of SL failure due to Excessive delay of ack

Definition
Number of SL failure due to Excessive delay of ack

Description
This counter counts the number of SL failures due to excessive delay of acknowledgement.

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

46.16 C901400015 Number of SL failure due to Excessive error rate

Definition
Number of SL failure due to Excessive error rate
46-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 46 MTP2 Signal Link Measurement

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

46.17 C901400016 Number of SL failure due to 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

46-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

47-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 48

SCTP AS Measurement
Table of Contents
Overview ..................................................................................................................48-2 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 C901420030 Number of abort from peer ................................................................48-18 C901420031 Number of association break by retransmission.................................48-18

48-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.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.
48-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 48 SCTP AS Measurement

Unit
Times

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 48 SCTP AS Measurement

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 48 SCTP AS Measurement

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

Usage
This counter is used to find out the statistics of RTT lower than T1.

Measurement Point
When the sampled RTT is lower than T1, this counter will counts.

Unit
None

48-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 48 SCTP AS Measurement

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

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 48 SCTP AS Measurement

Measurement Point
When RTT is calculated based on RTO sampling, determine the maximum delay of network transmission.

Unit
ms

Related Features
ZGO-05-04-005 IP SLA Monitoring

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
ZGO-05-04-005 IP SLA Monitoring

48-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-04-005 IP SLA Monitoring

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 48 SCTP AS Measurement

Measurement Point
When RTT is calculated based on RTO sampling, delay of network transmission is accumulated.

Unit
ms

Related Features
ZGO-05-04-005 IP SLA Monitoring

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. measurement internal, each time delay is sampled, this counter accumulates. In

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
ZGO-05-04-005 IP SLA Monitoring

48.24 C901420023 Maximum dithering of network transmission

Definition
Maximum dithering of network transmission
48-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-04-005 IP SLA Monitoring

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 48 SCTP AS Measurement

Related Features
ZGO-05-04-005 IP SLA Monitoring

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
ZGO-05-04-005 IP SLA Monitoring

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-05-04-005 IP SLA Monitoring

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. measurement internal, each time dithering is sampled, this counter accumulates. In

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
ZGO-05-04-005 IP SLA Monitoring

48-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 48 SCTP AS Measurement

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. This counter is supported in version V6.20.600f or above.

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. This counter is supported in version V6.20.600f or above.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

48.31 C901420030 Number of abort from peer

Description
This counter counts the number of link breaks due to abort initiated from the peer end.

Usage
This counter is supported in version V6.20.61 or later.

Measurement Point
When the abort message is received from the peer end, the counter increments.

Unit
Times

48.32 C901420031 Number of association break by retransmission

Description
This counter counts the number of link breaks due to retransmission.

Usage
This counter is supported in version V6.20.61 or later.

Measurement Point
When the link breaks due to retransmission, the counter increments.

Unit
Times

48-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

49-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The counter counts when PS user requests for the UPU DSP timeslot resource 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
The counter counts when PS user requests for the UPU DSP timeslot resource successfully.

Unit
Times

50-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 50 GTRUNK Resource Statistics

50.5 C901440004 Number of regular scanning and sampling

Definition
Number of regular scanning and sampling

Description
The counter increments at the measurement point of C901440003. This counter and 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
The counter counts when PS user requests for the UPU DSP timeslot resource successfully.

Unit
Times

50-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

50-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51

Other Process Statistics

Table of Contents
Overview ..................................................................................................................51-3 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(ms) .........................51-22 C901450027 The min length of packet latency period in Abis(ms) ..........................51-23 C901450028 The average length of packet latency period in Abis(ms) ...................51-23 C901450029 The latest length of packet latency period in Abis(ms) .......................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 C901450032 The length of packet latency period between 40 ms and 60 ms (60 included) in Abis.....................................................................................................51-25
51-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901450033 The length of packet latency period between 60 ms and 80 ms (80 included) in Abis.....................................................................................................51-26 C901450034 The length of packet latency period between 80 ms and 100 ms (100 included) in Abis.....................................................................................................51-26 C901450035 The length of packet latency period between 100 ms and 120 ms (120 included) in Abis.............................................................................................51-27 C901450036 The length of packet latency period between 120 ms and 140 ms (140 included) in Abis.............................................................................................51-27 C901450037 The length of packet latency period between 140 ms and 160 ms (160 included) in Abis.............................................................................................51-28 C901450038 The length of packet latency period between 160 ms and 180 ms (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(ms).............51-29 C901450041 The min length of downlink packet latency period in Gb(ms) .............51-30 C901450042 The average length of downlink packet latency period in Gb(ms) ......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 C901450045 The length of downlink packet latency period between 200 ms and 300 ms (300 included) in Gb...................................................................................51-32 C901450046 The length of downlink packet latency period between 300 ms and 400 ms (400 included) in Gb...................................................................................51-32 C901450047 The length of downlink packet latency period between 400 ms and 600 ms (600 included) in Gb...................................................................................51-33 C901450048 The length of downlink packet latency period between 600 ms and 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(ms) .................51-34 C901450051 The min length of uplink packet latency period in Gb(ms) ..................51-35 C901450052 The average length of uplink packet latency period in Gb(ms) ...........51-35 C901450053 LLC Stall Num ...................................................................................51-35 C901450054 MAC Resource Congestion ...............................................................51-36 C901450055 BSSGP Resource Congestion...........................................................51-36 C901450056 Number of Pushing Down Uplink BandWidth ....................................51-37 C901450057 Number of Pushing Down Downlink BandWidth ...............................51-37 C901450058 Number of Pushing Up Uplink BandWidth .........................................51-38 C901450059 Number of Pushing Up Downlink BandWidth.....................................51-39 C901450060 PDTCH Downlink Signaling Buffer Average Length ...........................51-40 C901450073 Total Uplink GPRS Throughput Efficiency..........................................51-40 C901450074 Total Downlink GPRS Throughput Efficiency .....................................51-41 C901450075 Total Uplink EGPRS Throughput Efficiency .......................................51-42 C901450076 Total Downlink EGPRS Throughput Efficiency ...................................51-43
51-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

51.1 Overview
Other process measurements contain the measurement on adjustments of frame number and NACC processes. Statistic unit in this measurement is cell.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

51.3 C901450002 Minimum 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 minimum duration of NACC.

Measurement Point
The measurement point is A, as shown in Figure 51-2.
Figure 51-2 NACC Duration

Minimum time of this NACC is the minimum of all NACC periods in a sampling period.

51-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

51.4 C901450003 Total 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 total time of all successful NACCs in this cell.

Measurement Point
The measurement point is A, as shown in Figure 51-3.
Figure 51-3 NACC Duration

Total time of this NACC is the sum of all NACC periods in a sampling period.

51-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

51.5 C901450004 Number of NACC cell reselection (PCCN to flush LL)

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 number of NACC success.

Measurement Point
The measurement point is A, as shown in Figure 51-4.
Figure 51-4 Measurement point of number of NACC success

51-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

51.6 C901450005 Number of NACC cell reselection without receiving flush LL

Description
Do NACC after receiving the Packet Cell Change Notification message sent by MS at network side. The MS decides whether to do cell reselection after the MS gets the system message about adjacent cell at network side.

Usage
It is used to measure the number of NACC without receiving flush LL.

Measurement Point
The measurement point is A, as shown in Figure 51-5.
Figure 51-5 Measurement point of number of NACCs

51-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

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. The measurement point is A, as shown in Figure 51-6.
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 measurement point is A, as shown in Figure 51-7.
51-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 51-7 Measurement point for the sum of C

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 point is A, as shown in Figure 51-8.

51-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

Figure 51-8 Measurement point for the sum of C

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 receives EGPRS PACKET DOWNLINK ACK.

Usage
This counter measures the GMSK-CV-BEP value about the channel quality.

Measurement Point
This counter increments when EGPRS receives PACKET DOWNLINK ACK and the GMSK_MEAN_BEP indication bit is 1 in the channel quality report. The measurement point is A, as shown in Figure 51-9.

51-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 51-9 Measurement point for the sum of C

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 receives EGPRS PACKET DOWNLINK ACK.

Usage
This counter measures the 8PSK-MEAN-BEP value about the channel quality.

Measurement Point
This counter increments when EGPRS receives PACKET DOWNLINK ACK and the 8PSK_MEAN_BEP indication bit is 1 in the channel quality report. The measurement point is A, as shown in Figure 51-10.

51-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

Figure 51-10 Measurement point for the sum of C

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
This counter increments when EGPRS receives PACKET DOWNLINK ACK and the 8PSK_MEAN_BEP indication bit is 1 in the channel quality report. The measurement point is A, as shown in Figure 51-11.

51-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 51-11 Measurement point for the sum of C

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. The measurement point is A, as shown in Figure 51-12.

51-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

Figure 51-12 Measurement point for the sum of C

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 measurement point is A, as shown in Figure 51-13.

51-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 51-13 Measurement point for the sum of C

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
This counter increments when EGPRS receives PACKET DOWNLINK ACK and the GMSK_MEAN_BEP indication bit is 1 in the channel quality report. The measurement point is A, as shown in Figure 51-14.

51-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

Figure 51-14 Measurement point for the sum of C

Unit
None

51.18 C901450017 Number of sampling of GMSK-CV-BEP

Description
This counter counts the number of GMSK-CV-BEP sampling points in channel quality report while DRLC receives EGPRS PACKET DOWNLINK ACK.

Usage
This counter measures the number of GMSK-CV-BEP sampling points about the channel quality.

Measurement Point
This counter increments when EGPRS receives PACKET DOWNLINK ACK and the GMSK_MEAN_BEP indication bit is 1 in the channel quality report. The measurement point is A, as shown in Figure 51-15.

51-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 51-15 Measurement point for the sum of C

Unit
Times

51.19 C901450018 Number of sampling of 8PSK-MEAN-BEP

Description
This counter counts the number of 8PSK-MEAN-BEP sampling points in channel quality report while DRLC receives EGPRS PACKET DOWNLINK ACK.

Usage
This counter measures the number of 8PSK-MEAN-BEP sampling points about the channel quality.

Measurement Point
This counter increments when EGPRS receives PACKET DOWNLINK ACK and the 8PSK_MEAN_BEP indication bit is 1 in the channel quality report. The measurement point is A, as shown in Figure 51-16.

51-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

Figure 51-16 Measurement point for the sum of C

Unit
None

51.20 C901450019 Number of sampling of 8PSK-CV-BEP

Description
This counter counts the number of 8PSK-CV-BEP sampling points in channel quality report while DRLC receives EGPRS PACKET DOWNLINK ACK.

Usage
This counter measures the number of 8PSK-CV-BEP sampling points about the channel quality.

Measurement Point
This counter increments when EGPRS receives PACKET DOWNLINK ACK and the 8PSK_MEAN_BEP indication bit is 1 in the channel quality report. The measurement point is A, as shown in Figure 51-17.

51-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 51-17 Measurement point for the sum of C

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 51-19 Measurement point of Number of RLC uplink ACK TBF

Unit
Times

51.23 C901450022 Number of DL-UNITDATA messages with Service UTRAN CCO received by BSC
This counter is not used for the time being.

51.24 C901450023 Total Block Num

This counter is not used for the time being.

51.25 C901450024 UL Idle Block Num

This counter is not used for the time being.

51.26 C901450025 DL Idle Block Num

This counter is not used for the time being.

51.27 C901450026 The max length of packet latency period in Abis(ms)

Statistics object
Cell

51-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

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(ms)

Statistics object
Cell

Description
This counter counts the minimum delay of the cell's PS service at Abis interface within the measurement period. When the uplink frame number and downlink frame number of PS service at BSC are synchronized, the counter gets the difference between the uplink frame number and downlink frame number, thus to get the delay of PS service at Abis interface. After comparison, the counter records the minimum delay.

Unit
ms

51.29 C901450028 The average length of packet latency period in Abis(ms)

Statistics object
Cell

Description
This counter counts the average delay of the cell's PS service at Abis interface within the measurement period. When the uplink frame number and downlink frame number of PS service at BSC are synchronized, the counter gets the difference between the uplink frame number and downlink frame number, thus to get the delay of PS service at Abis interface. After adding all delays and dividing the sum by the number of measurements, the counter records the average delay.
51-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
ms

51.30 C901450029 The latest length of packet latency period in Abis(ms)

Statistics object
Cell

Description
This counter counts the latest 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. 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

51.32 C901450031 The length of packet latency period between 20 ms and 40 ms (40 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 (20 ms, 40 ms] within the measurement period. When the uplink frame number and downlink frame number of PS service at BSC are synchronized, the counter gets the difference between the uplink frame number and downlink frame number, thus to get the delay of PS service at Abis interface. If the delay is in the range, then the counter increments.

Unit
Times

51.33 C901450032 The length of packet latency period between 40 ms and 60 ms (60 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 (40 ms, 60 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-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

51.34 C901450033 The length of packet latency period between 60 ms and 80 ms (80 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 (60 ms, 80 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.35 C901450034 The length of packet latency period between 80 ms and 100 ms (100 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 (80 ms, 100 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-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

51.36 C901450035 The length of packet latency period between 100 ms and 120 ms (120 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 (100 ms, 120 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.37 C901450036 The length of packet latency period between 120 ms and 140 ms (140 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 (120 ms, 140 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-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

51.38 C901450037 The length of packet latency period between 140 ms and 160 ms (160 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 (140 ms, 160 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.39 C901450038 The length of packet latency period between 160 ms and 180 ms (180 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 (160 ms, 180 ms] within the measurement period. When the uplink frame number and downlink frame number of PS service at BSC are synchronized, the counter gets the difference between the uplink frame 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-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

51.40 C901450039 The length of packet latency period larger than 180 ms 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 (180 ms, +] within the measurement period. When the uplink frame number and downlink frame number of PS service at BSC are synchronized, the counter gets the difference between the uplink frame 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.41 C901450040 The max length of downlink packet latency period in Gb(ms)
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

51.42 C901450041 The min length of downlink packet latency period in Gb(ms)
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 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 minimum delay.

Unit
ms

51.43 C901450042 The average length of downlink packet latency period in Gb(ms)
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 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. 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

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

51.45 C901450044 The length of downlink packet latency period between 100 ms and 200 ms (200 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 (100 ms, 200 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

51-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

51.46 C901450045 The length of downlink packet latency period between 200 ms and 300 ms (300 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 (200 ms, 300 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

51.47 C901450046 The length of downlink packet latency period between 300 ms and 400 ms (400 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 (300 ms, 400 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

51-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

51.48 C901450047 The length of downlink packet latency period between 400 ms and 600 ms (600 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 (400 ms, 600 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

51.49 C901450048 The length of downlink packet latency period between 600 ms and 1000 ms (1000 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 (600 ms, 1000 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

51-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

51.50 C901450049 The length of downlink packet latency period larger than 1000 ms 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 (1000 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

51.51 C901450050 The max length of uplink packet latency period in Gb(ms)
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

51.52 C901450051 The min length of uplink packet latency period in Gb(ms)
Statistics object
Cell

Description
This counter counts the minimum delay of the cell's PS service in uplink transmission at Gb interface within the measurement period. At BSC, when IP packet is sent at Gb interface, the uplink sent time is recorded; when IP packet is received at Gb interface, the uplink received time is recorded. Subtract the uplink sent time from the uplink received time to get the uplink delay at Gb interface. After comparison, the counter records the minimum delay.

Unit
ms

51.53 C901450052 The average length of uplink packet latency period in Gb(ms)
Statistics object
Cell

Description
This counter counts the average delay of the cell's PS service in uplink transmission at Gb interface within the measurement period. At BSC, when IP packet is sent at Gb interface, the uplink sent time is recorded; when IP packet is received at Gb interface, the uplink received time is recorded. Subtract the uplink sent time from the uplink received time to get the uplink delay at Gb interface. Add the subtraction result with all uplink delays at Gb interface to get the total delay. Divide the sum by the number of measurements, and the counter records the average delay.

Unit
ms

51.54 C901450053 LLC Stall Num

This counter is not used for the time being.

51-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. This counter is supported in version V6.20.200f or above.

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. This counter is supported in version V6.20.200f or above.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

51.57 C901450056 Number of Pushing Down Uplink BandWidth

Description
This counter counts the number of pushing down uplink bandwidth in the cell. When BSC control plane judges that the actual uplink bandwidth exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool, if the current theoretically allocated uplink bandwidth of resource pool is larger than available uplink bandwidth, BSC control plane sends the message of pushing down uplink bandwidth to BSC user plane. When BSC user plane receives the message, the counter increments.

Usage
The counter is used to find out the frequency of pushing down uplink bandwidth in the cell. This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC user plane receives the message of pushing down uplink bandwidth. The measurement point is A, as shown in Figure 51-20.
Figure 51-20 Flow of Pushing Down Uplink Bandwidth

Unit
Times

51.58 C901450057 Number of Pushing Down Downlink BandWidth

Description
This counter counts the number of pushing down downlink bandwidth in the cell. When BSC control plane judges that the actual downlink bandwidth exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool, if the current theoretically allocated downlink bandwidth of resource pool is larger than available downlink bandwidth,
51-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

BSC control plane sends the message of pushing down downlink bandwidth to BSC user plane. When BSC user plane receives the message, the counter increments.

Usage
The counter is used to find out the frequency of pushing down downlink bandwidth in the cell. This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC user plane receives the message of pushing down downlink bandwidth. The measurement point is A, as shown in Figure 51-21.
Figure 51-21 Flow of Pushing Down Downlink Bandwidth

Unit
Times

51.59 C901450058 Number of Pushing Up Uplink BandWidth

Description
This counter counts the number of pushing up uplink bandwidth in the cell. When BSC control plane judges that the actual uplink bandwidth is lower than C3, which is the congestion pushing up limit, BSC control plane sends the message of pushing up uplink bandwidth to BSC user plane. When BSC user plane receives the message, the counter increments.

Usage
The counter is used to find out the frequency of pushing up uplink bandwidth in the cell. This counter is supported in version V6.20.61 or later.

51-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

Measurement Point
The counter counts when BSC user plane receives the message of pushing up uplink bandwidth. The measurement point is A, as shown in Figure 51-22.
Figure 51-22 Flow of Pushing Up Uplink Bandwidth

Unit
Times

51.60 C901450059 Number of Pushing Up Downlink BandWidth

Description
This counter counts the number of pushing up downlink bandwidth in the cell. When BSC control plane judges that the actual downlink bandwidth is lower than C3, which is the congestion pushing up limit, BSC control plane sends the message of pushing up downlink bandwidth to BSC user plane. When BSC user plane receives the message, the counter increments.

Usage
The counter is used to find out the frequency of pushing up downlink bandwidth in the cell. This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC user plane receives the message of pushing up downlink bandwidth. The measurement point is A, as shown in Figure 51-23.

51-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 51-23 Flow of Pushing Up Downlink Bandwidth

Unit
Times

51.61 C901450060 PDTCH Downlink Signaling Buffer Average Length

Description
This counter counts the average length of signaling buffered over each PDTCH in a cell in 1s. The length of signaling buffered over each channel in the cell in every second is accumulated on the UPPB. When the 15-minute reporting granularity is up, the arithmetic average length of signaling buffered in each channel in 15 minutes is calculated. This counter records the average value.

Usage
None

Measurement Point
None

Unit
Bytes

51.62 C901450073 Total Uplink GPRS Throughput Efficiency

Description
This counter records the total uplink GPRS throughput efficiency when the UPPB board receives the uplink blocks. This counter is updated when the URLC module of the UPPB
51-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

board in the expansion state receives data blocks or switches from the transmission state to the expansion/delay state and when TBF is of the GPRS type. The statistical result that the counter records is the throughput efficiency of each uplink TBF multiplying transmission bytes.

Usage
This counter records the throughput efficiency of the uplink GPRS data TBF.

Measurement Point
This counter is updated when the URLC module receives the uplink blocks, as shown in Figure 51-24.
Figure 51-24 Calculating Uplink TBF Throughput Efficiency

Unit
kBps * kB

51.63 C901450074 Total Downlink GPRS Throughput Efficiency

Description
This counter records the total downlink GPRS throughput efficiency when the UPPB board receives the downlink packet Ack. When the DRLC module of the UPPB board receives the downlink Ack, this counter is updated if the DRLC module switches from the transmission state to the delay state and TBF is of the GPRS type. The statistical result that the counter records is the throughput efficiency of each downlink TBF multiplying transmission bytes.

Usage
This counter records the throughput efficiency of the downlink GPRS data TBF.

51-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is updated when the DRLC module receives the downlink Ack, as shown in Figure 51-25.
Figure 51-25 Calculating Downlink TBF Throughput Efficiency

Unit
kBps * kB

51.64 C901450075 Total Uplink EGPRS Throughput Efficiency

Description
This counter records the total uplink EGPRS throughput efficiency when the UPPB board receives the uplink blocks. This counter is updated when the URLC module of the UPPB board in the expansion state receives data blocks or switches from the transmission state to the expansion/delay state and when TBF is of the EGPRS type. The statistical result that the counter records is the throughput efficiency of each uplink TBF multiplying transmission bytes.

Usage
This counter records throughput efficiency of the uplink EGPRS data TBF.

Measurement Point
This counter is updated when the URLC module receives the uplink blocks, as shown in Figure Calculating Uplink TBF Throughput Efficiency.

Unit
kBps * kB

51-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 51 Other Process Statistics

51.65 C901450076 Total Downlink EGPRS Throughput Efficiency

Description
This counter records the total downlink EGPRS throughput efficiency when the UPPB board receives the downlink packet Ack. When the DRLC module of the UPPB board receives the downlink Ack, this counter is updated if the DRLC module switches from the transmission state to the delay state and TBF is of the GPRS type. The statistical result that the counter records is the throughput efficiency of each downlink TBF multiplying transmission bytes.

Usage
This counter records the throughput efficiency of the downlink EGPRS data TBF.

Measurement Point
This counter is updated when the DRLC module receives the downlink Ack, as shown in Figure Calculating Downlink Throughput Efficiency.

Unit
kBps * kB

51-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

51-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 C901460006 Peak Downlink throughput in FR .........................................................52-5 C901460007 Peak Uplink throughput in FR..............................................................52-5

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. measurement point is A1, as shown in Figure 52-1. The

52-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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" messages received by BSC.

Measurement Point
When BSC receives the "Status" message, this counter increments. The measurement point is A2, as shown in Figure 52-2.

52-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 52 FR Carried Links Statistics

Figure 52-2 Status Query Process

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 52-3 Status Query Process

52.5 C901460004 Number of bytes received on BRCH

Description
This counter counts the number of bytes received on BRCH of FR sublayer. This counter performs statistics for FR layer, and the statistic data contains FR header.

Usage
Check the number of bytes received on BRCH to observe the load of BRCH.

Measurement Point
FR accumulates the number of bytes received on BRCH from Gb interface.

52.6 C901460005 Number of bytes sent on BRCH

Description
This counter counts the number of bytes sent on BRCH of FR sublayer. This counter performs statistics for FR layer, and the statistic data contains FR header.

Usage
Check the number of bytes sent on BRCH to observe the load of BRCH.
52-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 52 FR Carried Links Statistics

Measurement Point
FR accumulates the number of bytes sent on BRCH from Gb interface.

52.7 C901460006 Peak Downlink throughput in FR

Description
On the GIPB board, the sent uplink throughput efficiency in FR is calculated once a second. When the 15-minute reporting granularity is up, this counter records the maximum value in the granularity.

Usage
None

Measurement Point
None

Unit
kbps

52.8 C901460007 Peak Uplink throughput in FR

Description
On the GIPB board, the received downlink throughput efficiency in FR is calculated once a second. When the 15-minute reporting granularity is up, this counter records the maximum value in the granularity.

Usage
None

Measurement Point
None

Unit
kbps

52-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

52-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 53

OMP PS Service Statistics

Table of Contents
Overview ..................................................................................................................53-1 C901470001 Number of SUSPEND message sent ..................................................53-1 C901470002 Number of SUSPEND-ACK message received....................................53-2 C901470003 Number of SUSPEND-NACK message received .................................53-2 C901470004 Number of RESUME message sent ....................................................53-3 C901470005 Number of RESUME-ACK message received .....................................53-3 C901470006 Number of RESUME-NACK message received ...................................53-4

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. Statistic unit in this measurement is cell.

53.2 C901470001 Number of SUSPEND message sent

Description
This counter counts the number of SUSPEND messages sent to an SGSN from site or cell within the measurement period.

Usage
This counter counts the number of SUSPEND messages sent to an SGSN from site or cell in downlink within the measurement period.

Measurement Point
The counter counts when the GB_SUSPEND message is sent.

Unit
Times

53-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

53.3 C901470002 Number of SUSPEND-ACK message received

Description
This counter counts the number of SUSPEND-ACK messages received by site or cell from an SGSN within the measurement period.

Usage
This counter counts the number of SUSPEND-ACK messages received by site or cell from an SGSN within the measurement period.

Measurement Point
The counter counts when the GB_SUSPEND_ACK message is received from SGSN.

Unit
Times

53.4 C901470003 Number of SUSPEND-NACK message 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 53 OMP PS Service Statistics

53.5 C901470004 Number of RESUME message sent

Description
This counter counts the number of RESUME messages sent to an SGSN from site or cell within the measurement period.

Usage
This counter counts the number of RESUME messages sent to an SGSN from site or cell in downlink within the measurement period.

Measurement Point
The counter counts when the GB_RESUME message is sent.

Unit
Times

53.6 C901470005 Number of RESUME-ACK message received

Description
This counter counts the number of RESUME-ACK messages received by site or cell from an SGSN within the measurement period.

Usage
This counter counts the number of RESUME-ACK messages received by site or cell from an SGSN within the measurement period.

Measurement Point
The counter counts when the GB_RESUME_ACK message is received from SGSN.

Unit
Times

53-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

53.7 C901470006 Number of RESUME-NACK message received

Description
This counter counts the number of RESUME-NACK messages received by site or cell from an SGSN within the measurement period.

Usage
This counter counts the number of RESUME-NACK messages received by site or cell from an SGSN within the measurement period.

Measurement Point
The counter counts when the GB_RESUME_NACK message is received from SGSN.

Unit
Times

53-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 acknowledgements...................................................................................................54-5 C901480008 Number of SNS-CONFIG initiated by BSC without response ...............54-5 C901480009 Number of SNS-CONFIG initiated by SGSN received successful acknowledgements...................................................................................................54-6 C901480010 Number of SNS-CONFIG initiated by SGSN received failed acknowledgements...................................................................................................54-7 C901480011 Number of SNS-ADD initiated by BSC.................................................54-7 C901480012 Number of SNS-ADD initiated by BSC received successful acknowledgements...................................................................................................54-8 C901480013 Number of SNS-ADD initiated by BSC received failed acknowledgements...................................................................................................54-8 C901480014 Number of SNS-ADD initiated by BSC without response .....................54-9 C901480015 Number of SNS-ADD initiated by SGSN received successful acknowledgements...................................................................................................54-9 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 acknowledgements.................................................................................................54-12 C901480020 Number of SNS-DELETE initiated by BSC without response .............54-12 C901480021 Number of SNS-DELETE initiated by SGSN received successful acknowledgements.................................................................................................54-13 C901480022 Number of SNS-DELETE initiated by SGSN received failed acknowledgements.................................................................................................54-13 C901480023 Number of SNS-CHANGEWEIGHT initiated by BSC .........................54-14

54-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901480024 Number of SNS-CHANGEWEIGHT initiated by BSC received successful acknowledgements ...............................................................................54-14 C901480025 Number of SNS-CHANGEWEIGHT initiated by BSC received failed acknowledgements.................................................................................................54-15 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 acknowledgements.................................................................................................54-17

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
ZGO-05-04-002 Gb over IP

54-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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
This counter counts the number of acknowledged responses from NSE after NSE receives 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
ZGO-05-04-002 Gb over IP

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
This counter counts the number of unacknowledged responses from NSE after NSE receives SNS-SIZE within the measurement period.

Measurement Point
After the SNS-SIZE message is received, this counter counts when NSE sends response message with the cause of unavailable NSVC or unavailable IPV4.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP
54-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

54.5 C901480004 Number of SNS-SIZE initiated by BSC without response

This counter is not used for the time being.

Related Features
ZGO-05-04-002 Gb over IP

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
ZGO-05-04-002 Gb over IP

54.7 C901480006 Number of SNS-CONFIG initiated by BSC received successful acknowledgements

Description
This counter counts the number of acknowledged responses from NSE after NSE receives the SNS-CONFIG message within the measurement period.

Usage
This counter counts the number of acknowledged responses from NSE after NSE receives the SNS-CONFIG message successfully within the measurement period.
54-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 54 SNS on OMP Statistics

Measurement Point
The counter counts when NSE returns the acknowledged response after receiving the SNS-CONFIG message.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54.8 C901480007 Number of SNS-CONFIG initiated by BSC received failed acknowledgements

Description
This counter counts the number of unacknowledged responses from NSE after NSE receives the SNS-CONFIG message within the measurement period.

Usage
This counter counts the number of unacknowledged responses from NSE after NSE 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
ZGO-05-04-002 Gb over IP

54.9 C901480008 Number of SNS-CONFIG initiated by 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter counts the number of SNS-CONFIG messages initiated by BSC but without any response within the measurement period.

Measurement Point
The counter counts when it is timeout during the process of waiting for NSE's response for the SNS-CONFIG message.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54.10 C901480009 Number of SNS-CONFIG initiated by SGSN received successful acknowledgements

Description
This counter counts the number of acknowledged responses of SNS-CONFIG messages initiated by SGSN within the measurement period.

Usage
This counter counts the number of acknowledged responses of SNS-CONFIG messages initiated by SGSN within the measurement period.

Measurement 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
ZGO-05-04-002 Gb over IP

54-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 54 SNS on OMP Statistics

54.11 C901480010 Number of SNS-CONFIG initiated by SGSN received failed acknowledgements

Description
This counter counts the number of failures of the SNS-CONFIG message initiated by SGSN within the measurement period.

Usage
This counter counts the number of failures of the SNS-CONFIG message initiated by SGSN within the measurement period.

Measurement Point
The counter counts when the EV_NSCTRL_CONFIG_IND message is received which indicates that the IP endpoint at SGSN fails to be recorded.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-05-04-002 Gb over IP

54.13 C901480012 Number of SNS-ADD initiated by BSC received successful acknowledgements

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 initiated by BSC within the measurement period.

Measurement Point
When BSC receives the EV_NSCTRL_SNSACK_IND message with acknowledgement, the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54.14 C901480013 Number of SNS-ADD initiated by BSC received failed acknowledgements

Description
This counter counts the number of unacknowledged responses of the SNS-ADD message initiated by BSC within the measurement period.

Usage
This counter counts the number of unacknowledged responses of the SNS-ADD message initiated by BSC within the measurement period.

Measurement Point
When BSC receives the EV_NSCTRL_SNSACK_IND message with unacknowledgement, the counter increments.
54-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 54 SNS on OMP Statistics

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54.15 C901480014 Number of SNS-ADD initiated by BSC without response

Description
This counter counts the number of SNS-ADD messages initiated by BSC but without any response within the measurement period.

Usage
This counter counts the number of SNS-ADD messages initiated 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
ZGO-05-04-002 Gb over IP

54.16 C901480015 Number of SNS-ADD initiated by SGSN received successful acknowledgements

Description
This counter counts the number of acknowledged responses of SNS-ADD messages initiated by SGSN within the measurement period.

Usage
This counter counts the number of acknowledged responses of SNS-ADD messages initiated by SGSN within the measurement period.

54-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when the EV_NSCTRL_ADD_IND message is received which indicates that the IP endpoint at SGSN is recorded successfully.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54.17 C901480016 Number of SNS-ADD initiated by SGSN received failed acknowledgements

Description
This counter counts the number of unacknowledged responses of SNS-ADD messages initiated by SGSN within the measurement period.

Usage
This counter counts the number of unacknowledged responses of SNS-ADD messages initiated by SGSN within the measurement period.

Measurement Point
The counter counts when the EV_NSCTRL_ADD_IND message is received which indicates that the IP endpoint at SGSN fails to be recorded.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 54 SNS on OMP Statistics

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
ZGO-05-04-002 Gb over IP

54.19 C901480018 Number of SNS-DELETE initiated by BSC received successful acknowledgements

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 message initiated by BSC within the measurement period.

Measurement Point
The counter counts when BSC receives the SNS-ACK message with acknowledgement.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

54.20 C901480019 Number of SNS-DELETE initiated by BSC received failed acknowledgements

Description
This counter counts the number of unacknowledged responses of the SNS-DELETE message initiated by BSC within the measurement period.

Usage
This counter counts the number of unacknowledged responses of the SNS-DELETE message initiated by BSC within the measurement period.

Measurement Point
The counter counts when BSC receives the SNS-ACK message with unacknowledgement.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54.21 C901480020 Number of SNS-DELETE initiated by BSC without response

Description
This counter counts the number of SNS-DELETE messages initiated by BSC but without any response within the measurement period.

Usage
This counter counts the number of SNS-DELETE 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 of SNS-DELETE message.

Unit
Times

54-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 54 SNS on OMP Statistics

Related Features
ZGO-05-04-002 Gb over IP

54.22 C901480021 Number of SNS-DELETE initiated by SGSN received successful acknowledgements

Description
This counter counts the number of acknowledged responses of SNS-DELETE messages initiated by SGSN within the measurement period.

Usage
This counter counts the number of acknowledged 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 indicates that the IP endpoint at SGSN is recorded successfully.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54.23 C901480022 Number of SNS-DELETE initiated by SGSN received failed acknowledgements

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 indicates that the IP endpoint at SGSN fails to be recorded.
54-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54.24 C901480023 Number of SNS-CHANGEWEIGHT initiated by BSC

Description
This counter counts the number of SNS-CHANGEWEIGHT messages initiated by BSC within the measurement period.

Usage
This counter counts the number of SNS-CHANGEWEIGHT messages initiated by BSC within the measurement period.

Measurement Point
The counter counts when BSC receives the EV_NSOAM_CHANGEWEIGHT_REQ message.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54.25 C901480024 Number of SNS-CHANGEWEIGHT initiated by BSC received successful acknowledgements

Description
This counter counts the number of acknowledged responses of SNS-CHANGEWEIGHT message initiated by BSC within the measurement period. the

Usage
This counter counts the number of acknowledged responses of SNS-CHANGEWEIGHT message initiated by BSC within the measurement period.
54-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

the

Chapter 54 SNS on OMP Statistics

Measurement Point
When BSC receives the EV_NSCTRL_SNSACK_IND message with acknowledgement, the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54.26 C901480025 Number of SNS-CHANGEWEIGHT initiated by BSC received failed acknowledgements

Description
This counter counts the number of unacknowledged responses of SNS-CHANGEWEIGHT message initiated by BSC within the measurement period. the

Usage
This counter counts the number of unacknowledged responses of SNS-CHANGEWEIGHT message initiated by BSC within the measurement period. the

Measurement Point
When BSC receives the EV_NSCTRL_SNSACK_IND message with unacknowledgement, the counter increments.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54.27 C901480026 Number of SNS-CHANGEWEIGHT initiated by BSC without response

Description
This counter counts the number of SNS-CHANGEWEIGHT messages initiated by BSC but without any response within the measurement period.

54-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter counts the number of SNS-CHANGEWEIGHT 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-CHANGEWEIGHT message.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54.28 C901480027 Number of SNS-CHANGEWEIGHT initiated by SGSN received successful acknowledgements

Description
This counter counts the number of acknowledged responses of the SNS-CHANGEWEIGHT message initiated by SGSN within the measurement period.

Usage
This counter counts the number of acknowledged responses of the SNS-CHANGEWEIGHT message initiated by SGSN within the measurement period.

Measurement Point
The counter counts when the EV_NSCTRL_CHANGEWEIGHT_IND message is received which indicates that the IP endpoint at SGSN is recorded successfully.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 54 SNS on OMP Statistics

54.29 C901480028 Number of SNS-CHANGEWEIGHT initiated by SGSN received failed acknowledgements

Description
This counter counts the number of unacknowledged responses of the SNS-CHANGEWEIGHT message initiated by SGSN within the measurement period.

Usage
This counter counts the number of unacknowledged responses of the SNS-CHANGEWEIGHT message initiated by SGSN within the measurement period.

Measurement Point
The counter counts when the EV_NSCTRL_CHANGEWEIGHT_IND message is received which indicates that the IP endpoint at SGSN fails to be recorded.

Unit
Times

Related Features
ZGO-05-04-002 Gb over IP

54-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

54-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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. Statistic unit in this measurement is NSVC.

55.2 C901490001 Number of bytes received from SGSN

This counter is not used for the time being.

Related Features
ZGO-05-04-002 Gb over IP

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
The NSVC load can be checked through this counter. This counter is supported in version V6.10.100a or above.

55-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
IP accumulates the number of bytes sent each time. The measurement point is A1, as shown in Figure 55-1.
Figure 55-1 Uplink NS Data

Unit
Byte

Related Features
ZGO-05-04-002 Gb over IP

55.4 C901490003 Number of PDU data sent by NS sub layer

This counter is not used for the time being.

Related Features
ZGO-05-04-002 Gb over IP

55.5 C901490004 Number of PDU data received by NS sub layer

This counter is not used for the time being.

Related Features
ZGO-05-04-002 Gb over IP

55-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 55 IPGB StrongARM NSVC Statistics

55.6 C901490005 Number of PDU data discarded by NS sub layer

This counter is not used for the time being.

Related Features
ZGO-05-04-002 Gb over IP

55-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

55-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 56

IPGB StrongARM Gb Statistics

Table of Contents
Overview ..................................................................................................................56-1 C901500001 Sum of UL UNITDATA messages handled at BSSGP level..................56-1 C901500002 Sum of DL UNITDATA messages handled at BSSGP level..................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. Statistic unit in this measurement is cell.

56.2 C901500001 Sum of UL UNITDATA messages handled at BSSGP level

This counter is not used for the time being.

Related Features
ZGO-05-04-002 Gb over IP

56.3 C901500002 Sum of DL UNITDATA messages handled at BSSGP level

This counter is not used for the time being.

Related Features
ZGO-05-04-002 Gb over IP

56-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

56-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 measurement point is B2, as shown in Figure 57-2 and Figure 57-3.
Figure 57-2 Measurement Point of Queuing Duration when Queuing Fails

57-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 57 Queue Measurement

Figure 57-4 Measurement Point of Queuing Duration when Queuing Fails

Figure 57-5 Measurement Point of Queuing Duration when Queuing Succeeds

57-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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, as shown in Figure 57-6.
Figure 57-6 Measurement Point of Queuing Duration when Queuing Succeeds

57-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 57 Queue Measurement

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 measurement point is B2, as shown in Figure 57-7.
Figure 57-7 Measurement Point of Queuing Duration when Queuing Succeeds

Unit
Times

57-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

57-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 58

HO 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 58-2 Measurement Point of MS Sending Assignment/Handover Completion Message to BSC

Statistic unit in this measurement is cell.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 58 HO Synchronization Mode Measurement

58.3 C901520002 Number of synchronous handover 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 channel activation completion message is received.

Usage
This counter is used to find out the number of pre-synchronous handover executions in the cell.

Measurement Point
After BSC receives the channel activation completion message from BTS, if the handover is pre-synchronous handover, the counter increments.

Unit
Times

58-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

58.5 C901520004 Number of pre-synchronous handover successes

Description
This counter counts the number of successful pre-synchronous handovers after the uplink handover(assignment) completion message is received.

Usage
This counter is used to find out the number of successful pre-synchronous handovers in the cell.

Measurement Point
After BSC receives the uplink handover (assignment) completion message from BTS, if 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
After BSC receives the channel activation completion message from BTS, if the handover is pseudo-synchronous handover, the counter increments.

Unit
Times

58-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 58 HO 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
After BSC receives the uplink handover (assignment) completion message from BTS, if 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 channel activation completion message is received.

Usage
This counter is used to find out the number of asynchronous handover executions in the cell.

Measurement Point
After BSC receives the channel activation completion message from BTS, if the handover is asynchronous handover, the counter increments.

Unit
Times

58-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

58.9 C901520008 Number of asynchronous handover successes

Description
This counter counts the number of successful asynchronous handovers after the uplink handover(assignment) completion message is received.

Usage
This counter is used to find out the number of successful asynchronous handovers in the cell.

Measurement Point
After BSC receives the uplink handover (assignment) completion message from BTS, if the handover is asynchronous handover, the counter increments.

Unit
Times

58-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 in Figure 59-1 and Figure 59-2.
Figure 59-1 Measurement Point of BSC Receiving Paging Message from A-Interface

59-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 59-2 Measurement Point of BSC Receiving PS/CS Paging Message from Gb Interface

Statistic unit in this measurement is BSC.

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 measurement point is A, as shown in Figure 59-3.

59-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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. The measurement point is A, as shown in Figure 59-4.

59-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 59-4 Measurement Point of BSC Receiving PS/CS Paging Message from Gb Interface

Measurement Point
When BSC receives the PS paging message from Gb interface, the counter increments. The measurement point is A, as shown in Figure 59-4.

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. The measurement point is A, as shown in Figure 59-5.

59-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 59 Paging Message Measurement

Figure 59-5 Measurement Point of BSC Receiving PS/CS Paging Message from Gb Interface

Measurement Point
When BSC receives the CS paging message from Gb interface, the counter increments. The measurement point is A, as shown in Figure 59-5.

Unit
Times

59-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

59-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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. Statistic unit in this measurement is cell.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 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 data channel resource request to the database succeeds and the acquired resource is reserved channel, the counter 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 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 handover process, when the voice channel resource request to the database succeeds and the acquired resource is reserved channel, the counter increments.

Unit
Times
60-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 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 handover process, when the data channel resource request to the database succeeds and the acquired resource is reserved channel, the counter 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

60-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When BSC sends the Connect Req message to MSC, the counter increments. The measurement point is A, as shown in Figure 61-1.
Figure 61-1 Measurement Point of Number of BSC originated SCCP Connection attempts

Unit
Times

61.3 C901550002 Number of BSC originated SCCP Connection success

Description
This counter counts the number of successful SCCP link establishments initiated by BSC towards MSC.

61-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 increments. The measurement point is A, as shown in Figure 61-2.
Figure 61-2 Measurement Point of Number of BSC originated SCCP Connection attempts

Unit
Times

61-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

61.4 C901550003 Number of BSC originated SCCP Connection failure due to timeout
Description
This counter counts the number of SCCP link establishment failures due to timeout, and the SCCP link establishment is initiated by BSC towards MSC.

Usage
This counter is used to find out the number of SCCP link establishment failures due to timeout, and the SCCP link establishment is initiated by BSC towards MSC.

Measurement Point
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 61 SCCP Connection Measurement

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. The measurement point is A, as shown in Figure 61-4.
61-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A, as shown in Figure 61-5.
61-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 61 SCCP Connection Measurement

Figure 61-5 Measurement Point of Number of MSC originated SCCP Connection success

Unit
Times

61-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

61-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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-3 C901560003 Number of received IMSI when link establish ......................................62-4 C901560004 Number of RANCS module received IMSI when handover ..................62-4 C901560005 Number of mobile sent GTTP message under DTM mode...................62-5 C901560006 Number of BSC successfully sent GTTP message under DTM mode ..62-5 C901560007 Number of DTM attempts in mobile .....................................................62-6 C901560008 Number of DTM uplink attempt failure .................................................62-6 C901560009 Number of UL DTM database resource assignment success in dedicated mode .......................................................................................................62-7 C901560010 Number of UL DTM database resource assignment failure in dedicated mode .......................................................................................................62-8 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-9 C901560013 Number of handover(intra-cell) failure due to uplink DTM ....................62-9 C901560014 Number of DTM failure due to handover............................................62-10 C901560015 Number of UL DTM link establishment success.................................62-10 C901560016 Attempt number of sending LLC packet on FACCH in dedicated mode ..................................................................................................................... 62-11 C901560017 Number of successfully sent LLC packet on FACCH in dedicated mode .....................................................................................................................62-12 C901560018 Attempt Number of DTM established due to SGSN sent LLC packets ..................................................................................................................62-12 C901560019 Number of DTM attempts failure........................................................62-13 C901560020 Number of DL DTM resource assignment success ............................62-13 C901560021 Number of DL DTM resource assignment failure ...............................62-14 C901560022 Number of handover(intra-cell) attempts due to DL DTM ...................62-15 C901560023 Number of successfully handover occurs due to DL DTM..................62-15 C901560024 Number of handover failure occurs due to DL DTM ...........................62-16 C901560025 Number of DL DTM failure occurs due to handover ...........................62-16 C901560026 Number of successfully DL DTM establishment.................................62-17 C901560027 Number of Packet CS Request in Packet Transfer Mode...................62-17 C901560028 Number of MO CS Success and PS Reallocation..............................62-18 C901560029 Number of MO CS Success and PS Non-Reallocation ......................62-18 C901560030 Number of MO CS Success and PS Release ....................................62-19 C901560031 Number of MO CS Fail and PS Maintain ...........................................62-19
62-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901560032 Number of MO CS Fail and PS Release............................................62-19 C901560033 Number of CS Paging in Packet Transfer Mode ................................62-20 C901560034 Number of MT CS Success and PS Reallocation ..............................62-20 C901560035 Number of MT CS Success and PS Non-Reallocation.......................62-21 C901560036 Number of MT CS Success and PS Release.....................................62-21 C901560037 Number of MT CS Fail and PS Maintain ............................................62-21 C901560038 Number of MT CS Fail and PS Release ............................................62-22 C901560039 Number of Packet CS Release Indication ..........................................62-22 C901560040 Number of CS Release and PS Maintain ...........................................62-23 C901560041 Number of DTM Successful Establishment........................................62-23 C901560042 Number of CS drop at DTM mode .....................................................62-24 C901560043 Number of PS drop at DTM mode .....................................................62-24 C901560044 Peak Value of Uplink GPRS Throughput Efficiency............................62-25 C901560045 Peak Value of Uplink EGPRS Throughput Efficiency .........................62-26 C901560046 Peak Value of Downlink GPRS Throughput Efficiency .......................62-26 C901560047 Peak Value of Downlink EGPRS Throughput Efficiency.....................62-27 C901560048 Number of Enhanced DTM CS Drop at DTM Mode ...........................62-27 C901560049 Number of DLDC Resource Request in Dedicated Mode...................62-28 C901560050 Number of DLDC Resource Assignment in Dedicated Mode .............62-28 C901560051 Number of RTTI Resource Request in Dedicated Mode ....................62-28 C901560052 Number of RTTI Resource Assignment in Dedicated Mode ...............62-29

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
The counter counts in the following three cases.

62-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

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
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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.

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
The counter counts in the following three cases. 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
ZGO-03-02-003 Full dynamic channel allocation on Um interface

62-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 within the measurement period.

Usage
This counter is used to find out the number of IMSIs received during link establishment in the cell.

Measurement Point
When BSC receives the COMMON ID message from MSC, if no IMSI information is saved originally, then the IMSI information carried in the COMMON ID message is saved, and the counter increments.

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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
62-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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.
62-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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.

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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 the measurement period.

Usage
This counter is used to find out the number of failed attempts of uplink DTM service in the cell.

Measurement Point
1. When BSC receives the DTM request from MS but does not process due to MS not on SDCCH, the counter increments.
62-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

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
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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.

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
l l ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-003 Full dynamic channel allocation on Um interface

62-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
l l ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-003 Full dynamic channel allocation on Um interface

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.

62-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

62.13 C901560012 Number of handover(intra-cell) success due to uplink DTM

Description
This counter counts the number of successful intra-cell handovers due to uplink DTM service in dedicated mode in the cell within the measurement period.

Usage
This counter is used to find out the number of successful intra-cell handovers due to uplink DTM service in dedicated mode in the cell.

Measurement Point
After the intra-cell handover is completed, if BSC judges that the MS is implementing DTM service, the counter increments.

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

62.14 C901560013 Number of handover(intra-cell) failure due to uplink DTM

Description
This counter counts the number of failed intra-cell handovers due to uplink DTM service in dedicated mode in the cell within the measurement period.

Usage
This counter is used to find out the number of failed intra-cell handovers due to uplink DTM service in dedicated mode in the cell.

62-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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 mode in the cell within the measurement period.

Usage
This counter is used to find out the number of failed uplink DTM service due to handover in dedicated mode in the cell within the measurement period.

Measurement Point
During BSC's voice service process, when the DTM request is received and the DTM service fails due to MS being in the handover status, the counter increments.

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

62.16 C901560015 Number of UL DTM link establishment success

Description
This counter counts the number of successful uplink DTM service establishments in dedicated mode in the cell within the measurement period.
62-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

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
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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 mode in the cell within the measurement period.

Usage
This counter is used to find out the number of attempts of sending LLC frame on FACCH in dedicated mode in the cell.

Measurement Point
During BSC's voice service process, when the downlink LLC data frame is received in GTTP mode, the counter increments.

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

62-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 mode in the cell within the measurement period.

Usage
This counter is used to find out the number of successfully sending LLC frame on FACCH in dedicated mode in the cell.

Measurement Point
During BSC's voice service process, when the LLC frame is sent on FACCH in GTTP mode, the counter increments.

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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.

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
62-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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 the measurement period.

Usage
This counter is used to find out the number of failed attempts of downlink DTM service in the cell.

Measurement Point
During BSC's voice service process, when DTM service is initiated due to receiving LLC data frame sent by SGSN, if the system judges that the rancs module on CMP is not in stable service status, then the following messages are not processed: DTM assignment message, PS assignment message, and LLC frame sending message. In this case, the counter increments.

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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.

62-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
l l ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-003 Full dynamic channel allocation on Um interface

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.

Unit
Times

Related Features
l l ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-003 Full dynamic channel allocation on Um interface

62-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

62.23 C901560022 Number of handover(intra-cell) attempts due to DL DTM

Description
This counter counts the number of attempts of intra-cell handover due to downlink DTM service in dedicated mode in the cell within the measurement period.

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
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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 service in dedicated mode in the cell within the measurement period.

Usage
This counter is used to find out the number of successful intra-cell handovers due to downlink DTM service in dedicated mode in the cell.

Measurement Point
After the intra-cell handover is completed, if BSC judges that the MS is implementing DTM service and the DTM resource assignment is in downlink, the counter increments.

Unit
Times
62-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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 in dedicated mode in the cell within the measurement period.

Usage
This counter is used to find out the number of failed intra-cell handovers due to downlink DTM service in dedicated mode in the cell.

Measurement Point
During intra-cell handover, when the handover fails due to BSC assignment failure or T3107 timeout, if BSC judges that the MS is implementing DTM service and the DTM resource assignment is in downlink, the counter increments.

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

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 dedicated mode in the cell within the measurement period.

Usage
This counter is used to find out the number of failed downlink DTM service due to handover in dedicated mode in the cell within the measurement period.

62-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

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
ZGO-03-02-003 Full dynamic channel allocation on Um interface

62.27 C901560026 Number of successfully DL DTM establishment

Description
This counter counts the number of successful downlink DTM service establishments in dedicated mode in the cell within the measurement period.

Usage
This counter is used to find out the number of successful downlink DTM service establishments in dedicated mode in the cell.

Measurement Point
During downlink DTM service process, when the RANPS module on CMP inside BSC receives the instance establishment indication message from the MAC module on UPPB, the counter increments.

Unit
Times

Related Features
ZGO-03-02-003 Full dynamic channel allocation on Um interface

62.28 C901560027 Number of Packet CS Request in Packet Transfer Mode

Description
This counter counts CS establishment requests received in packet transfer mode.
62-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter is not used in this version.

Measurement Point
None

Unit
Times

62.29 C901560028 Number of MO CS Success and PS Reallocation

Description
This counter counts the number of times that a CS connection is successfully established and PS resources are reallocated upon a CS establishment request received in packet transfer mode. This counter is not used in this version.

Measurement Point
None

Unit
Times

62.30 C901560029 Number of MO CS Success and PS Non-Reallocation

Description
This counter counts the number of times that a CS connection is successfully established and PS resources are not reallocated upon a CS establishment request received in packet transfer mode. This counter is not used in this version.

Measurement Point
None

Unit
Times
62-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

62.31 C901560030 Number of MO CS Success and PS Release

Description
This counter counts the number of times that a CS connection is successfully established and PS resources are released upon a CS establishment request received in packet transfer mode. This counter is not used in this version.

Measurement Point
None

Unit
Times

62.32 C901560031 Number of MO CS Fail and PS Maintain

Description
This counter counts the number of times that a CS establishment fails and PS resources are not reallocated upon a CS establishment request received in packet transfer mode. This counter is not used in this version.

Measurement Point
None

Unit
Times

62.33 C901560032 Number of MO CS Fail and PS Release

Description
This counter counts the number of times that a CS establishment fails and PS resources are released upon a CS establishment request received in packet transfer mode. This counter is not used in this version.
62-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
None

Unit
Times

62.34 C901560033 Number of CS Paging in Packet Transfer Mode

Description
This counter counts CS paging requests received in packet transfer mode. This counter is not used in this version.

Measurement Point
None

Unit
Times

62.35 C901560034 Number of MT CS Success and PS Reallocation

Description
This counter counts the number of times that a CS connection is successfully established and PS resources are reallocated upon a CS paging request received in packet transfer mode. This counter is not used in this version.

Measurement Point
None

Unit
Times

62-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

62.36 C901560035 Number of MT CS Success and PS Non-Reallocation

Description
This counter counts the number of times that a CS connection is successfully established and PS resources are not reallocated upon a CS paging request received in packet transfer mode. This counter is not used in this version.

Measurement Point
None

Unit
Times

62.37 C901560036 Number of MT CS Success and PS Release

Description
This counter counts the number of times that a CS connection is successfully established and PS resources are released upon a CS paging request received in packet transfer mode. This counter is not used in this version.

Measurement Point
None

Unit
Times

62.38 C901560037 Number of MT CS Fail and PS Maintain

Description
This counter counts the number of times that a CS establishment fails and PS resources are not reallocated upon a CS paging request received in packet transfer mode. This counter is not used in this version.
62-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
None

Unit
Times

62.39 C901560038 Number of MT CS Fail and PS Release

Description
This counter counts the number of times that a CS establishment fails and PS resources are released upon a CS paging request received in packet transfer mode. This counter is not used in this version.

Measurement Point
None

Unit
Times

62.40 C901560039 Number of Packet CS Release Indication

Description
This counter counts Packet CS Release Indication messages that are sent. This counter is not used in this version.

Measurement Point
None

Unit
Times

62-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

62.41 C901560040 Number of CS Release and PS Maintain

Description
This counter counts the number of times that PS resources are not reallocated after CS release. This counter is not used in this version.

Measurement Point
None

Unit
Times

62.42 C901560041 Number of DTM Successful Establishment

Description
This counter counts the times that DTM instance is established successfully upon receipt of the DTM Request in dedicated mode. This counter increases by 1 when the RANC receives the EV_MAC_EST_IND message after the uplink/downlink PS instance is established successfully upon receipt of the DTM Request in dedicated mode.

Usage
None

Measurement Point
The measurement point is shown in Figure 62-1.

62-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 62-1 Times of DTM Establishment Success

Unit
Time

62.43 C901560042 Number of CS drop at DTM mode

Description
This counter counts the number of CS drops in DTM mode. This counter increases by 1 in the case of abnormal CS drop in DTM mode (namely, the PS instance also exists).

Usage
None

Measurement Point
The measurement point is as shown in Figure Number of CS Drops.

Unit
Time

62.44 C901560043 Number of PS drop at DTM mode

Description
This counter counts the number of abnormal PS drops in DTM mode. This counter increases by 1 in the case of abnormal PS drop in DTM mode. This counter also increases by 1 in the case of abnormal CS drop in DTM mode.

Usage
None
62-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

Measurement Point
The measurement point is shown in Figure 62-2.
Figure 62-2 Number of PS drops in DTM mode

Unit
Time

62.45 C901560044 Peak Value of Uplink GPRS Throughput Efficiency

Description
This counter records the peak throughput efficiency of the sent uplink GPRS LLC frames. On the UPPB board, the throughput efficiency of the LLC frames composed of the uplink GPRS RLC blocks is calculated every 10 seconds. When the 15-minute reporting granularity is up, this counter records the maximum value in the granularity.

Usage
None

Measurement Point
None

Unit
kbps

62-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

62.46 C901560045 Peak Value of Uplink EGPRS Throughput Efficiency

Description
This counter records the peak throughput efficiency of the sent uplink EGPRS LLC frames. On the UPPB board, the throughput efficiency of the LLC frames composed of the uplink EGPRS RLC blocks is calculated every 10 seconds. When the 15-minute reporting granularity is up, this counter records the maximum value in the granularity.

Usage
None

Measurement Point
None

Unit
kbps

62.47 C901560046 Peak Value of Downlink GPRS Throughput Efficiency

Description
This counter records the peak throughput efficiency of the received downlink GPRS LLC frames. On the UPPB board, the throughput efficiency of the received downlink GPRS LLC frames is calculated every 10 seconds. When the 15-minute reporting granularity is up, this counter records the the maximum value in the granularity.

Usage
None

Measurement Point
None

Unit
kbps

62-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

62.48 C901560047 Peak Value of Downlink EGPRS Throughput Efficiency

Description
This counter records the peak throughput efficiency of the received downlink EGPRS LLC frames. On the UPPB board, the throughput efficiency of the received EGPRS LLC frames is calculated every 10 seconds. When the 15-minute reporting granularity is up, this counter records the maximum value in the granularity.

Usage
None

Measurement Point
None

Unit
kbps

62.49 C901560048 Number of Enhanced DTM CS Drop at DTM Mode

Description
This counter counts the number of times that an enhanced DTM CS call is dropped. This counter is not used in this version.

Measurement Point
None

Unit
Times

62-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

62.50 C901560049 Number of DLDC Resource Request in Dedicated Mode

Description
This counter counts the number of times that DLDC resources are requested in dedicated mode. This counter is not used in this version.

Measurement Point
None

Unit
Times

62.51 C901560050 Number of DLDC Resource Assignment in Dedicated Mode

Description
This counter counts the number of times that DLDC resources are assigned in dedicated mode. This counter is not used in this version.

Measurement Point
None

Unit
Times

62.52 C901560051 Number of RTTI Resource Request in Dedicated Mode

Description
This counter counts the number of times that RTTI resources are requested in dedicated mode. This counter is not used in this version.

62-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 62 DTM Cell Measurement

Measurement Point
None

Unit
Times

62.53 C901560052 Number of RTTI Resource Assignment in Dedicated Mode

Description
This counter counts the number of times that RTTI resources are assigned in dedicated mode. This counter is not used in this version.

Measurement Point
None

Unit
Times

62-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

62-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 63 LAPD Measurement

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 63 LAPD Measurement

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 measurement point is A, as shown in Figure 63-1.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The measurement point is A, as shown in Figure 63-2.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 63 LAPD Measurement

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
The measurement point is A, as shown in Figure 63-3.

63-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.

63.21 C901570020 Number of T201 Overtime

Description
T201 defines the time limit of response for LAPD identification authentication. This counter counts the number of T201 timeout on LAPD link.

Usage
his counter is used to find out the number of T201 timeout on LAPD link. It studies whether the LAPD identification authentication request is acknowledged.

Measurement Point
The counter counts when the LAPD process receives the T201 timeout message.
63-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 63 LAPD Measurement

63.22 C901570021 Number of T203 Overtime

Description
T203 defines the maximum time allowed for no frame interaction. This counter counts the number of T203 timeout on LAPD link.

Usage
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
The counter counts when the LAPD process receives the T203 timeout message.

63.23 C901570022 Number of T204 Overtime

Description
T204 defines the time limit of sending unacknowledgement due to hop frame in the slide window. This counter counts the number of T204 timeout on LAPD link.

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
The counter counts when the LAPD process receives the T204 timeout message.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 63 LAPD Measurement

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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-18 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. The measurement point is A, as shown in Figure 64-1.
Figure 64-1 Measurement Point of Number of receiving location request in CS

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 64 LCS Measurement

Related Features
ZGO-01-03-002 LCS with CGI+TA

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 measurement point is A, as shown in Figure 64-5.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when iBSC receives the position response from MS. The measurement point is A, as shown in Figure 64-6.
Figure 64-6 Measurement Point of Number of MS Position Response in CS Domain

Unit
Times

Related Features
ZGO-01-03-003 LCS with AGPS

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 point is A, as shown in Figure 64-7.

64-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 64 LCS Measurement

Figure 64-7 Measurement Point of Number of Location Successes in CS Domain

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64.10 C901580009 Number of location failure due to radio Timer expiration in CS

Description
After iBSC sends the location command to MS, the radio timer starts. If no response is received from MS before the timer is timeout, the counter counts the number of location failures in CS domain due to radio timer timeout.

Measurement Point
After iBSC sends the location command to MS, the radio timer starts. When the timer is timeout, the counter counts the number 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
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 64 LCS Measurement

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. The measurement point is A, as shown in Figure 64-10.
Figure 64-10 Measurement Point of Number of Location Delays in CS Domain due to Intra-BSC Handover

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64.12 C901580011 Number of location failure due to Intra-BSS handover expiration in CS

Description
When iBSC receives the MS position command from SMLC, if iBSC is initiating intra-BSC inter-cell handover at the moment, the timer starts. This counter counts the number of location failures due to timer timout.

64-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when the intra-BSC handover timer is timeout in CS domain. The measurement point is A, as shown in Figure 64-11.
Figure 64-11 Measurement Point of Number of Location Failures due to Intra-BSS Handover Timer Timeout in CS Domain

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64.13 C901580012 Number of location failure due to 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 is A, as shown in Figure 64-12.

64-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 64 LCS Measurement

Figure 64-12 Measurement Point of Number of Location Failure due to Location Monitoring Timer Timeout in CS Domain

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64.14 C901580013 Number of location failure due to 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64.15 C901580014 Number of location failure due to call drop in CS

Description
During the location process, iBSC receives the clear command from the core network.

Measurement Point
During the location process, the counter counts when iBSC receives the clear command from the core network. The measurement point is A, as shown in Figure 64-14.
Figure 64-14 Measurement Point of Number of Location Failure due to Call Drop in CS Domain

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 64 LCS Measurement

64.16 C901580015 Number of location failure due to other BSC's cause in CS

Description
Location fails due to other causes inside iBSC, such as message sending failure between modules, requesting SCCP connection failure, and timer setting failure.

Measurement Point
The counter counts when the following problems occur: message sending failure between modules, requesting SCCP connection failure, and timer setting failure.

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

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. The measurement point is A, as shown in Figure 64-15.

64-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 64-15 Measurement Point of Number of Location Requests in PS Domain

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

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

64-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 64 LCS Measurement

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

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
ZGO-01-03-002 LCS with CGI+TA

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.
64-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.
Figure 64-18 Measurement Point of Number of TA Responses in PS Domain

Unit
Times

Related Features
ZGO-01-03-002 LCS with CGI+TA

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 measurement point is A, as shown in Figure 64-19.

64-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 64 LCS Measurement

Figure 64-19 Measurement Point of Number of MS Position Commands in PS Domain

Unit
Times

Related Features
ZGO-01-03-003 LCS with AGPS

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 measurement point is A, as shown in Figure 64-20.
Figure 64-20 Measurement Point of Number of MS Position Response in PS Domain

64-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Related Features
ZGO-01-03-003 LCS with AGPS

64.23 C901580022 Number of location success in PS

Description
This counter counts the number of location successes in PS domain.

Measurement Point
The counter counts when iBSC receives the position result from SMLC. The measurement point is A, as shown in Figure 64-21.
Figure 64-21 Measurement Point of Number of Location Successes in PS Domain

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64.24 C901580023 Number of location failure due to 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.
64-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 64 LCS Measurement

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.
Figure 64-22 Measurement Point of Number of location failure due to abnormal status of Lb interface in PS

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64.25 C901580024 Number of location failure due to radio Timer expiration in PS

Description
After iBSC sends the location command to the core network, the radio timer starts. If no response is received from MS before the timer is timeout, the counter counts the number of location failures in PS domain due to radio timer timeout.

Measurement Point
After iBSC sends the location command to the core network, the radio timer starts. When the timer is timeout, the counter counts the number of location failures in PS domain due to radio timer timeout. The measurement point is A, as shown in Figure 64-23.

64-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 64-23 Number of Location Failures in PS domain due to Radio Timer Timeout

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64.26 C901580025 Number of location failure due to Inter-CMP cell reselection in PS

Description
During the positioning process in PS domain, if inter-module cell reselection occurs, the FLUSH LL message is received from the core network, then the location fails.

Measurement Point
During the positioning process in PS domain, if inter-module cell reselection occurs, the counter counts when the FLUSH LL message is received from the core network. The measurement point is A, as shown in Figure 64-24.
Figure 64-24 Measurement Point of Number of Location Failure due to Inter-Module Cell Reselection in PS Domain

64-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 64 LCS Measurement

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

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 measurement point is A, as shown in Figure 64-25.
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
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

64.28 C901580027 Number of location failure due to 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 is A, as shown in Figure 64-26.
Figure 64-26 Measurement Point of Number of Location Failure due to Location Monitoring Timer Timeout in PS Domain

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64.29 C901580028 Number of location failure due to other BSC's cause in PS

Description
Location fails due to other causes inside iBSC, such as message sending failure between modules, requesting SCCP connection failure, and timer setting failure.

64-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 64 LCS Measurement

Measurement Point
The counter counts when the following problems occur: message sending failure between modules, requesting SCCP connection failure, and timer setting failure.

Unit
Times

Related Features
l l ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS

64-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

64-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 measurement point is A, as shown in Figure 65-1.

65-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A, as shown in Figure 65-2.

65-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 measurement point is A, as shown in Figure 65-3.

65-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A, as shown in Figure 65-4.

65-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 65 LB Global Msg Measurement

Figure 65-4 Measurement Point of Number of RESET ACK Messages Received from SMLC

Unit
Times

65-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

65-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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. Statistic unit in this measurement is office.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 circuits of Ater interface

Description
This counter counts the average number of unavailable 16 K relay circuits at Ater interface.

Usage
This counter is used to find out the average number of unavailable 16 K relay circuits at Ater interface.

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

66-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 circuits of Ater interface

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

66-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 66 Ater Interface Relays Measurement

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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-6 and B in Figure 66-7. (Note: Figure 66-7 only gives one case of Ater interface terrestrial circuit being released.)
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 66 Ater Interface Relays Measurement

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
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-8 and B in Figure 66-9. (Note: Figure 66-9 only gives one case of Ater interface terrestrial circuit being released.)
Figure 66-8 Measurement Point of Total busy time of 16 K relay circuits of Ater interface - (1)

66-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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-10 and B in Figure 66-11. (Note: Figure 66-11 only gives one case of Ater interface terrestrial circuit being released.)

66-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 66 Ater Interface Relays Measurement

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

66-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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. Statistic unit in this measurement is office.

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 is A, as shown in Figure 67-1.

67-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 increments. The measurement point is A, as shown in Figure 67-2.

67-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 67 Ater Interface SCCP Connections Measurement

Figure 67-2 Measurement Point of Number of SCCP Connection Successes

Unit
Times

67.4 C901610003 Number of SCCP establishment failure due to timeout (BSC to TC)
Description
This counter counts the number of failed link establishments, which is due to timer timeout, initiated by BSC towards TC.

Measurement Point
When the Ater process expires at the timer TAterWaitConn, the counter increments. The measurement point is A, as shown in Figure 67-3.

67-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 67-3 Measurement Point of Number of SCCP Connection Failure due to Timeout

Unit
Times

67.5 C901610004 Number of SCCP establishment 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 67 Ater Interface SCCP Connections Measurement

Figure 67-4 Measurement Point of Number of SCCP Connection Request Being Rejected

Unit
Times

67-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

67-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68

Measurement Reprot 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 C901620003 Number of samples of UL RQ=0 and receive level between 16 and 20 .68-7 C901620004 Number of samples of UL RQ=0 and receive level between 21 and 30 .68-8 C901620005 Number of samples of UL RQ=0 and receive level between 31 and 40 .68-8 C901620006 Number of samples of UL RQ=0 and receive level between 41 and 63 .68-9 C901620007 Number of samples of UL RQ=1 and receive level between 0 and 10 .68-10 C901620008 Number of samples of UL RQ=1 and receive level between 11 and 15........................................................................................................................... 68-11 C901620009 Number of samples of UL RQ=1 and receive level between 16 and 20........................................................................................................................... 68-11 C901620010 Number of samples of UL RQ=1 and receive level between 21 and 30...........................................................................................................................68-12 C901620011 Number of samples of UL RQ=1 and receive level between 31 and 40...........................................................................................................................68-13 C901620012 Number of samples of UL RQ=1 and receive level between 41 and 63...........................................................................................................................68-14 C901620013 Number of samples of UL RQ=2 and receive level between 0 and 10 .68-15 C901620014 Number of samples of UL RQ=2 and receive level between 11 and 15...........................................................................................................................68-15 C901620015 Number of samples of UL RQ=2 and receive level between 16 and 20...........................................................................................................................68-16 C901620016 Number of samples of UL RQ=2 and receive level between 21 and 30...........................................................................................................................68-17 C901620017 Number of samples of UL RQ=2 and receive level between 31 and 40...........................................................................................................................68-18 C901620018 Number of samples of UL RQ=2 and receive level between 41 and 63...........................................................................................................................68-19 C901620019 Number of samples of UL RQ=3 and receive level between 0 and 10 .68-19 C901620020 Number of samples of UL RQ=3 and receive level between 11 and 15...........................................................................................................................68-20 C901620021 Number of samples of UL RQ=3 and receive level between 16 and 20...........................................................................................................................68-21
68-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901620022 Number of samples of UL RQ=3 and receive level between 21 and 30...........................................................................................................................68-22 C901620023 Number of samples of UL RQ=3 and receive level between 31 and 40...........................................................................................................................68-23 C901620024 Number of samples of UL RQ=3 and receive level between 41 and 63...........................................................................................................................68-23 C901620025 Number of samples of UL RQ=4 and receive level between 0 and 10 .68-24 C901620026 Number of samples of UL RQ=4 and receive level between 11 and 15...........................................................................................................................68-25 C901620027 Number of samples of UL RQ=4 and receive level between 16 and 20...........................................................................................................................68-26 C901620028 Number of samples of UL RQ=4 and receive level between 21 and 30...........................................................................................................................68-27 C901620029 Number of samples of UL RQ=4 and receive level between 31 and 40...........................................................................................................................68-27 C901620030 Number of samples of UL RQ=4 and receive level between 41 and 63...........................................................................................................................68-28 C901620031 Number of samples of UL RQ=5 and receive level between 0 and 10 .68-29 C901620032 Number of samples of UL RQ=5 and receive level between 11 and 15...........................................................................................................................68-30 C901620033 Number of samples of UL RQ=5 and receive level between 16 and 20...........................................................................................................................68-31 C901620034 Number of samples of UL RQ=5 and receive level between 21 and 30...........................................................................................................................68-31 C901620035 Number of samples of UL RQ=5 and receive level between 31 and 40...........................................................................................................................68-32 C901620036 Number of samples of UL RQ=5 and receive level between 41 and 63...........................................................................................................................68-33 C901620037 Number of samples of UL RQ=6 and receive level between 0 and 10 .68-34 C901620038 Number of samples of UL RQ=6 and receive level between 11 and 15...........................................................................................................................68-35 C901620039 Number of samples of UL RQ=6 and receive level between 16 and 20...........................................................................................................................68-35 C901620040 Number of samples of UL RQ=6 and receive level between 21 and 30...........................................................................................................................68-36 C901620041 Number of samples of UL RQ=6 and receive level between 31 and 40...........................................................................................................................68-37 C901620042 Number of samples of UL RQ=6 and receive level between 41 and 63...........................................................................................................................68-38 C901620043 Number of samples of UL RQ=7 and receive level between 0 and 10 .68-39 C901620044 Number of samples of UL RQ=7 and receive level between 11 and 15...........................................................................................................................68-39 C901620045 Number of samples of UL RQ=7 and receive level between 16 and 20...........................................................................................................................68-40

68-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

C901620046 Number of samples of UL RQ=7 and receive level between 21 and 30...........................................................................................................................68-41 C901620047 Number of samples of UL RQ=7 and receive level between 31 and 40...........................................................................................................................68-42 C901620048 Number of samples of UL RQ=7 and receive level between 41 and 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 C901620051 Number of samples of DL RQ=0 and receive level between 16 and 20...........................................................................................................................68-45 C901620052 Number of samples of DL RQ=0 and receive level between 21 and 30...........................................................................................................................68-46 C901620053 Number of samples of DL RQ=0 and receive level between 31 and 40...........................................................................................................................68-47 C901620054 Number of samples of DL RQ=0 and receive level between 41 and 63...........................................................................................................................68-47 C901620055 Number of samples of DL RQ=1 and receive level between 0 and 10 .68-48 C901620056 Number of samples of DL RQ=1 and receive level between 11 and 15...........................................................................................................................68-49 C901620057 Number of samples of DL RQ=1 and receive level between 16 and 20...........................................................................................................................68-50 C901620058 Number of samples of DL RQ=1 and receive level between 21 and 30...........................................................................................................................68-51 C901620059 Number of samples of DL RQ=1 and receive level between 31 and 40...........................................................................................................................68-51 C901620060 Number of samples of DL RQ=1 and receive level between 41 and 63...........................................................................................................................68-52 C901620061 Number of samples of DL RQ=2 and receive level between 0 and 10 .68-53 C901620062 Number of samples of DL RQ=2 and receive level between 11 and 15...........................................................................................................................68-54 C901620063 Number of samples of DL RQ=2 and receive level between 16 and 20...........................................................................................................................68-55 C901620064 Number of samples of DL RQ=2 and receive level between 21 and 30...........................................................................................................................68-55 C901620065 Number of samples of DL RQ=2 and receive level between 31 and 40...........................................................................................................................68-56 C901620066 Number of samples of DL RQ=2 and receive level between 41 and 63...........................................................................................................................68-57 C901620067 Number of samples of DL RQ=3 and receive level between 0 and 10 .68-58 C901620068 Number of samples of DL RQ=3 and receive level between 11 and 15...........................................................................................................................68-59 C901620069 Number of samples of DL RQ=3 and receive level between 16 and 20...........................................................................................................................68-59

68-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901620070 Number of samples of DL RQ=3 and receive level between 21 and 30...........................................................................................................................68-60 C901620071 Number of samples of DL RQ=3 and receive level between 31 and 40...........................................................................................................................68-61 C901620072 Number of samples of DL RQ=3 and receive level between 41 and 63...........................................................................................................................68-62 C901620073 Number of samples of DL RQ=4 and receive level between 0 and 10 .68-63 C901620074 Number of samples of DL RQ=4 and receive level between 11 and 15...........................................................................................................................68-63 C901620075 Number of samples of DL RQ=4 and receive level between 16 and 20...........................................................................................................................68-64 C901620076 Number of samples of DL RQ=4 and receive level between 21 and 30...........................................................................................................................68-65 C901620077 Number of samples of DL RQ=4 and receive level between 31 and 40...........................................................................................................................68-66 C901620078 Number of samples of DL RQ=4 and receive level between 41 and 63...........................................................................................................................68-67 C901620079 Number of samples of DL RQ=5 and receive level between 0 and 10 .68-67 C901620080 Number of samples of DL RQ=5 and receive level between 11 and 15...........................................................................................................................68-68 C901620081 Number of samples of DL RQ=5 and receive level between 16 and 20...........................................................................................................................68-69 C901620082 Number of samples of DL RQ=5 and receive level between 21 and 30...........................................................................................................................68-70 C901620083 Number of samples of DL RQ=5 and receive level between 31 and 40...........................................................................................................................68-71 C901620084 Number of samples of DL RQ=5 and receive level between 41 and 63...........................................................................................................................68-71 C901620085 Number of samples of DL RQ=6 and receive level between 0 and 10 .68-72 C901620086 Number of samples of DL RQ=6 and receive level between 11 and 15...........................................................................................................................68-73 C901620087 Number of samples of DL RQ=6 and receive level between 16 and 20...........................................................................................................................68-74 C901620088 Number of samples of DL RQ=6 and receive level between 21 and 30...........................................................................................................................68-75 C901620089 Number of samples of DL RQ=6 and receive level between 31 and 40...........................................................................................................................68-75 C901620090 Number of samples of DL RQ=6 and receive level between 41 and 63...........................................................................................................................68-76 C901620091 Number of samples of DL RQ=7 and receive level between 0 and 10 .68-77 C901620092 Number of samples of DL RQ=7 and receive level between 11 and 15...........................................................................................................................68-78 C901620093 Number of samples of DL RQ=7 and receive level between 16 and 20...........................................................................................................................68-79

68-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

C901620094 Number of samples of DL RQ=7 and receive level between 21 and 30...........................................................................................................................68-79 C901620095 Number of samples of DL RQ=7 and receive level between 31 and 40...........................................................................................................................68-80 C901620096 Number of samples of DL RQ=7 and receive level between 41 and 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-2 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.3 C901620002 Number of samples of UL RQ=0 and receive level between 11 and 15
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 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 11 and 15.

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 11 and 15. The measurement point is A, as shown in Figure 68-3.
Figure 68-3 Measurement Point of BTS Sending Meaurement Report to BSC

68-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.4 C901620003 Number of samples of UL RQ=0 and receive level between 16 and 20
Description
This counter counts the number of samples of UL RQ=0 and receive level between 16 and 20 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 16 and 20.

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 16 and 20. The measurement point is A, as shown in Figure 68-4.
Figure 68-4 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

68.5 C901620004 Number of samples of UL RQ=0 and receive level between 21 and 30
Description
This counter counts the number of samples of UL RQ=0 and receive level between 21 and 30 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 21 and 30.

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 21 and 30. The measurement point is A, as shown in Figure 68-5.
Figure 68-5 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.6 C901620005 Number of samples of UL RQ=0 and receive level between 31 and 40
Description
This counter counts the number of samples of UL RQ=0 and receive level between 31 and 40 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 31 and 40.
68-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

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 31 and 40. The measurement point is A, as shown in Figure 68-6.
Figure 68-6 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.7 C901620006 Number of samples of UL RQ=0 and receive level between 41 and 63
Description
This counter counts the number of samples of UL RQ=0 and receive level between 41 and 63 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 41 and 63.

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 41 and 63. The measurement point is A, as shown in Figure 68-7.

68-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-7 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.8 C901620007 Number of samples of UL RQ=1 and receive level between 0 and 10
Description
This counter counts the number of samples of UL RQ=1 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=1 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=1 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-8.
Figure 68-8 Measurement Point of BTS Sending Meaurement Report to BSC

68-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.9 C901620008 Number of samples of UL RQ=1 and receive level between 11 and 15
Description
This counter counts the number of samples of UL RQ=1 and receive level between 11 and 15 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=1 and receive level is between 11 and 15.

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=1 and receive level is between 11 and 15. The measurement point is A, as shown in Figure 68-9.
Figure 68-9 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.10 C901620009 Number of samples of UL RQ=1 and receive level between 16 and 20
Description
This counter counts the number of samples of UL RQ=1 and receive level between 16 and 20 in UL radio measurement report (preprocessing report or enhanced preprocessing
68-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=1 and receive level is between 16 and 20.

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=1 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-10.
Figure 68-10 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.11 C901620010 Number of samples of UL RQ=1 and receive level between 21 and 30
Description
This counter counts the number of samples of UL RQ=1 and receive level between 21 and 30 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=1 and receive level is between 21 and 30.

Usage
This counter is used to find out radio channel's UL quality and receive level.

68-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=1 and receive level is between 21 and 30. The measurement point is A, as shown in Figure 68-11.
Figure 68-11 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.12 C901620011 Number of samples of UL RQ=1 and receive level between 31 and 40
Description
This counter counts the number of samples of UL RQ=1 and receive level between 31 and 40 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=1 and receive level is between 31 and 40.

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=1 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-12.

68-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-12 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.13 C901620012 Number of samples of UL RQ=1 and receive level between 41 and 63
Description
This counter counts the number of samples of UL RQ=1 and receive level between 41 and 63 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=1 and receive level is between 41 and 63.

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=1 and receive level is between 41 and 63. The measurement point is A, as shown in Figure 68-13.
Figure 68-13 Measurement Point of BTS Sending Meaurement Report to BSC

68-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.14 C901620013 Number of samples of UL RQ=2 and receive level between 0 and 10
Description
This counter counts the number of samples of UL RQ=2 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=2 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=2 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-14.
Figure 68-14 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.15 C901620014 Number of samples of UL RQ=2 and receive level between 11 and 15
Description
This counter counts the number of samples of UL RQ=2 and receive level between 11 and 15 in UL radio measurement report (preprocessing report or enhanced preprocessing
68-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=2 and receive level is between 11 and 15.

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=2 and receive level is between 11 and 15. The measurement point is A, as shown in Figure 68-15.
Figure 68-15 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.16 C901620015 Number of samples of UL RQ=2 and receive level between 16 and 20
Description
This counter counts the number of samples of UL RQ=2 and receive level between 16 and 20 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=2 and receive level is between 16 and 20.

Usage
This counter is used to find out radio channel's UL quality and receive level.

68-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=2 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-16.
Figure 68-16 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.17 C901620016 Number of samples of UL RQ=2 and receive level between 21 and 30
Description
This counter counts the number of samples of UL RQ=2 and receive level between 21 and 63 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=2 and receive level is between 21 and 30.

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=2 and receive level is between 21 and 30. The measurement point is A, as shown in Figure 68-17.

68-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-17 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.18 C901620017 Number of samples of UL RQ=2 and receive level between 31 and 40
Description
This counter counts the number of samples of UL RQ=2 and receive level between 31 and 40 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=2 and receive level is between 31 and 40.

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=2 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-18.
Figure 68-18 Measurement Point of BTS Sending Meaurement Report to BSC

68-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.19 C901620018 Number of samples of UL RQ=2 and receive level between 41 and 63
Description
This counter counts the number of samples of UL RQ=2 and receive level between 41 and 63 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=2 and receive level is between 41 and 63.

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=2 and receive level is between 41 and 63. The measurement point is A, as shown in Figure 68-19.
Figure 68-19 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.20 C901620019 Number of samples of UL RQ=3 and receive level between 0 and 10
Description
This counter counts the number of samples of UL RQ=3 and receive level between 0 and 10 in UL radio measurement report (preprocessing report or enhanced preprocessing
68-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=3 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=3 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-20.
Figure 68-20 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.21 C901620020 Number of samples of UL RQ=3 and receive level between 11 and 15
Description
This counter counts the number of samples of UL RQ=3 and receive level between 11 and 15 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=3 and receive level is between 11 and 15.

Usage
This counter is used to find out radio channel's UL quality and receive level.

68-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=3 and receive level is between 11 and 15. The measurement point is A, as shown in Figure 68-21.
Figure 68-21 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.22 C901620021 Number of samples of UL RQ=3 and receive level between 16 and 20
Description
This counter counts the number of samples of UL RQ=3 and receive level between 16 and 20 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=3 and receive level is between 16 and 20.

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=3 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-22.

68-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-22 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.23 C901620022 Number of samples of UL RQ=3 and receive level between 21 and 30
Description
This counter counts the number of samples of UL RQ=3 and receive level between 21 and 30 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=3 and receive level is between 21 and 30.

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=3 and receive level is between 21 and 30. The measurement point is A, as shown in Figure 68-23.
Figure 68-23 Measurement Point of BTS Sending Meaurement Report to BSC

68-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.24 C901620023 Number of samples of UL RQ=3 and receive level between 31 and 40
Description
This counter counts the number of samples of UL RQ=3 and receive level between 31 and 40 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=3 and receive level is between 31 and 40.

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=3 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-24.
Figure 68-24 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.25 C901620024 Number of samples of UL RQ=3 and receive level between 41 and 63
Description
This counter counts the number of samples of UL RQ=3 and receive level between 41 and 63 in UL radio measurement report (preprocessing report or enhanced preprocessing
68-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=3 and receive level is between 41 and 63.

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=3 and receive level is between 41 and 63. The measurement point is A, as shown in Figure 68-25.
Figure 68-25 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.26 C901620025 Number of samples of UL RQ=4 and receive level between 0 and 10
Description
This counter counts the number of samples of UL RQ=4 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=4 and receive level is between 0 and 10.

Usage
This counter is used to find out radio channel's UL quality and receive level.

68-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=4 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-26.
Figure 68-26 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.27 C901620026 Number of samples of UL RQ=4 and receive level between 11 and 15
Description
This counter counts the number of samples of UL RQ=4 and receive level between 11 and 15 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=4 and receive level is between 11 and 15.

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=4 and receive level is between 11 and 15. The measurement point is A, as shown in Figure 68-27.

68-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-27 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.28 C901620027 Number of samples of UL RQ=4 and receive level between 16 and 20
Description
This counter counts the number of samples of UL RQ=4 and receive level between 16 and 20 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=4 and receive level is between 16 and 20.

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=4 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-28.
Figure 68-28 Measurement Point of BTS Sending Meaurement Report to BSC

68-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.29 C901620028 Number of samples of UL RQ=4 and receive level between 21 and 30
Description
This counter counts the number of samples of UL RQ=4 and receive level between 21 and 30 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=4 and receive level is between 21 and 30.

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=4 and receive level is between 21 and 30. The measurement point is A, as shown in Figure 68-29.
Figure 68-29 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.30 C901620029 Number of samples of UL RQ=4 and receive level between 31 and 40
Description
This counter counts the number of samples of UL RQ=4 and receive level between 31 and 40 in UL radio measurement report (preprocessing report or enhanced preprocessing
68-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=4 and receive level is between 31 and 40.

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=4 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-30.
Figure 68-30 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.31 C901620030 Number of samples of UL RQ=4 and receive level between 41 and 63
Description
This counter counts the number of samples of UL RQ=4 and receive level between 41 and 63 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=4 and receive level is between 41 and 63.

Usage
This counter is used to find out radio channel's UL quality and receive level.

68-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=4 and receive level is between 41 and 63. The measurement point is A, as shown in Figure 68-31.
Figure 68-31 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.32 C901620031 Number of samples of UL RQ=5 and receive level between 0 and 10
Description
This counter counts the number of samples of UL RQ=5 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=5 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=5 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-32.

68-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-32 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.33 C901620032 Number of samples of UL RQ=5 and receive level between 11 and 15
Description
This counter counts the number of samples of UL RQ=5 and receive level between 11 and 15 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=5 and receive level is between 11 and 15.

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=5 and receive level is between 11 and 15. The measurement point is A, as shown in Figure 68-33.
Figure 68-33 Measurement Point of BTS Sending Meaurement Report to BSC

68-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.34 C901620033 Number of samples of UL RQ=5 and receive level between 16 and 20
Description
This counter counts the number of samples of UL RQ=5 and receive level between 16 and 20 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=5 and receive level is between 16 and 20.

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=5 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-34.
Figure 68-34 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.35 C901620034 Number of samples of UL RQ=5 and receive level between 21 and 30
Description
This counter counts the number of samples of UL RQ=5 and receive level between 21 and 30 in UL radio measurement report (preprocessing report or enhanced preprocessing
68-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=5 and receive level is between 21 and 30.

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=5 and receive level is between 21 and 30. The measurement point is A, as shown in Figure 68-35.
Figure 68-35 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.36 C901620035 Number of samples of UL RQ=5 and receive level between 31 and 40
Description
This counter counts the number of samples of UL RQ=5 and receive level between 31 and 40 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=5 and receive level is between 31 and 40.

Usage
This counter is used to find out radio channel's UL quality and receive level.

68-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=5 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-36.
Figure 68-36 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.37 C901620036 Number of samples of UL RQ=5 and receive level between 41 and 63
Description
This counter counts the number of samples of UL RQ=5 and receive level between 41 and 63 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=5 and receive level is between 41 and 63.

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=5 and receive level is between 41 and 63. The measurement point is A, as shown in Figure 68-37.

68-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-37 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.38 C901620037 Number of samples of UL RQ=6 and receive level between 0 and 10
Description
This counter counts the number of samples of UL RQ=6 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=6 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=6 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-38.
Figure 68-38 Measurement Point of BTS Sending Meaurement Report to BSC

68-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.39 C901620038 Number of samples of UL RQ=6 and receive level between 11 and 15
Description
This counter counts the number of samples of UL RQ=6 and receive level between 11 and 15 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=6 and receive level is between 11 and 15.

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=6 and receive level is between 11 and 15. The measurement point is A, as shown in Figure 68-39.
Figure 68-39 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.40 C901620039 Number of samples of UL RQ=6 and receive level between 16 and 20
Description
This counter counts the number of samples of UL RQ=6 and receive level between 16 and 20 in UL radio measurement report (preprocessing report or enhanced preprocessing
68-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=6 and receive level is between 16 and 20.

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=6 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-40.
Figure 68-40 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.41 C901620040 Number of samples of UL RQ=6 and receive level between 21 and 30
Description
This counter counts the number of samples of UL RQ=6 and receive level between 21 and 30 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=6 and receive level is between 21 and 30.

Usage
This counter is used to find out radio channel's UL quality and receive level.

68-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=6 and receive level is between 21 and 30. The measurement point is A, as shown in Figure 68-41.
Figure 68-41 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.42 C901620041 Number of samples of UL RQ=6 and receive level between 31 and 40
Description
This counter counts the number of samples of UL RQ=6 and receive level between 31 and 40 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=6 and receive level is between 31 and 40.

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=6 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-42.

68-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-42 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.43 C901620042 Number of samples of UL RQ=6 and receive level between 41 and 63
Description
This counter counts the number of samples of UL RQ=6 and receive level between 41 and 63 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=6 and receive level is between 41 and 63.

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=6 and receive level is between 41 and 63. The measurement point is A, as shown in Figure 68-43.
Figure 68-43 Measurement Point of BTS Sending Meaurement Report to BSC

68-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.44 C901620043 Number of samples of UL RQ=7 and receive level between 0 and 10
Description
This counter counts the number of samples of UL RQ=7 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=7 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=7 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-44.
Figure 68-44 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.45 C901620044 Number of samples of UL RQ=7 and receive level between 11 and 15
Description
This counter counts the number of samples of UL RQ=7 and receive level between 11 and 15 in UL radio measurement report (preprocessing report or enhanced preprocessing
68-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=7 and receive level is between 11 and 15.

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=7 and receive level is between 11 and 15. The measurement point is A, as shown in Figure 68-45.
Figure 68-45 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.46 C901620045 Number of samples of UL RQ=7 and receive level between 16 and 20
Description
This counter counts the number of samples of UL RQ=7 and receive level between 16 and 20 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=7 and receive level is between 16 and 20.

Usage
This counter is used to find out radio channel's UL quality and receive level.

68-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=7 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-46.
Figure 68-46 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.47 C901620046 Number of samples of UL RQ=7 and receive level between 21 and 30
Description
This counter counts the number of samples of UL RQ=7 and receive level between 21 and 30 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=7 and receive level is between 21 and 30.

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=7 and receive level is between 21 and 30. The measurement point is A, as shown in Figure 68-47.

68-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-47 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.48 C901620047 Number of samples of UL RQ=7 and receive level between 31 and 40
Description
This counter counts the number of samples of UL RQ=7 and receive level between 31 and 40 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=7 and receive level is between 31 and 40.

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=7 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-48.
Figure 68-48 Measurement Point of BTS Sending Meaurement Report to BSC

68-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.49 C901620048 Number of samples of UL RQ=7 and receive level between 41 and 63
Description
This counter counts the number of samples of UL RQ=7 and receive level between 41 and 63 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=7 and receive level is between 41 and 63.

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=7 and receive level is between 41 and 63. The measurement point is A, as shown in Figure 68-49.
Figure 68-49 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.50 C901620049 Number of samples of DL RQ=0 and receive level between 0 and 10
Description
This counter counts the number of samples of DL RQ=0 and receive level between 0 and 10 in DL radio measurement report (preprocessing report or enhanced preprocessing
68-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level is between 0 and 10.

Usage
This counter is used to find out radio channel's DL quality and receive level.

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-50.
Figure 68-50 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.51 C901620050 Number of samples of DL RQ=0 and receive level between 11 and 15
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 measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level is between 11 and 15.

Usage
This counter is used to find out radio channel's DL quality and receive level.

68-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level between 11 and 15. The measurement point is A, as shown in Figure 68-51.
Figure 68-51 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.52 C901620051 Number of samples of DL RQ=0 and receive level between 16 and 20
Description
This counter counts the number of samples of DL RQ=0 and receive level between 16 and 20 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level is between 16 and 20.

Usage
This counter is used to find out radio channel's DL quality and receive level.

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-52.

68-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-52 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.53 C901620052 Number of samples of DL RQ=0 and receive level between 21 and 30
Description
This counter counts the number of samples of DL RQ=0 and receive level between 21 and 30 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level is between 21 and 30.

Usage
This counter is used to find out radio channel's DL quality and receive level.

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level between 21 and 30. The measurement point is A, as shown in Figure 68-53.
Figure 68-53 Measurement Point of BTS Sending Meaurement Report to BSC

68-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.54 C901620053 Number of samples of DL RQ=0 and receive level between 31 and 40
Description
This counter counts the number of samples of DL RQ=0 and receive level between 31 and 40 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level is between 31 and 40.

Usage
This counter is used to find out radio channel's DL quality and receive level.

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-54.
Figure 68-54 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.55 C901620054 Number of samples of DL RQ=0 and receive level between 41 and 63
Description
This counter counts the number of samples of DL RQ=0 and receive level between 41 and 63 in DL radio measurement report (preprocessing report or enhanced preprocessing
68-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level is between 41 and 63.

Usage
This counter is used to find out radio channel's DL quality and receive level.

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level between 41 and 63. The measurement point is A, as shown in Figure 68-55.
Figure 68-55 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.56 C901620055 Number of samples of DL RQ=1 and receive level between 0 and 10
Description
This counter counts the number of samples of DL RQ=1 and receive level between 0 and 10 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=1 and receive level is between 0 and 10.

Usage
This counter is used to find out radio channel's DL quality and receive level.

68-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=1 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-56.
Figure 68-56 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.57 C901620056 Number of samples of DL RQ=1 and receive level between 11 and 15
Description
This counter counts the number of samples of DL RQ=1 and receive level between 11 and 15 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=1 and receive level is between 11 and 15.

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=1 and receive level between 11 and 15. The measurement point is A, as shown in Figure 68-57.

68-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-57 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.58 C901620057 Number of samples of DL RQ=1 and receive level between 16 and 20
Description
This counter counts the number of samples of DL RQ=1 and receive level between 16 and 20 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=1 and receive level is between 16 and 20.

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=1 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-58.
Figure 68-58 Measurement Point of BTS Sending Meaurement Report to BSC

68-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.59 C901620058 Number of samples of DL RQ=1 and receive level between 21 and 30
Description
This counter counts the number of samples of DL RQ=1 and receive level between 21 and 30 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=1 and receive level is between 21 and 30.

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=1 and receive level between 21 and 30. The measurement point is A, as shown in Figure 68-59.
Figure 68-59 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.60 C901620059 Number of samples of DL RQ=1 and receive level between 31 and 40
Description
This counter counts the number of samples of DL RQ=1 and receive level between 31 and 40 in DL radio measurement report (preprocessing report or enhanced preprocessing
68-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=1 and receive level is between 31 and 40.

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=1 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-60.
Figure 68-60 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.61 C901620060 Number of samples of DL RQ=1 and receive level between 41 and 63
Description
This counter counts the number of samples of DL RQ=1 and receive level between 41 and 63 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=1 and receive level is between 41 and 63.

Usage
This counter is used to find out radio channel's DL quality and receive level.

68-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=1 and receive level between 41 and 63. The measurement point is A, as shown in Figure 68-61.
Figure 68-61 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.62 C901620061 Number of samples of DL RQ=2 and receive level between 0 and 10
Description
This counter counts the number of samples of DL RQ=2 and receive level between 0 and 10 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=2 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=2 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-62.

68-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-62 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.63 C901620062 Number of samples of DL RQ=2 and receive level between 11 and 15
Description
This counter counts the number of samples of DL RQ=2 and receive level between 11 and 15 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=2 and receive level is between 11 and 15.

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=2 and receive level between 11 and 15. The measurement point is A, as shown in Figure 68-63.
Figure 68-63 Measurement Point of BTS Sending Meaurement Report to BSC

68-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.64 C901620063 Number of samples of DL RQ=2 and receive level between 16 and 20
Description
This counter counts the number of samples of DL RQ=2 and receive level between 16 and 20 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=2 and receive level is between 16 and 20.

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=2 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-64.
Figure 68-64 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.65 C901620064 Number of samples of DL RQ=2 and receive level between 21 and 30
Description
This counter counts the number of samples of DL RQ=2 and receive level between 21 and 30 in DL radio measurement report (preprocessing report or enhanced preprocessing
68-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=2 and receive level is between 21 and 30.

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=2 and receive level is between 21 and 30. The measurement point is A, as shown in Figure 68-65.
Figure 68-65 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.66 C901620065 Number of samples of DL RQ=2 and receive level between 31 and 40
Description
This counter counts the number of samples of DL RQ=2 and receive level between 31 and 40 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=2 and receive level is between 31 and 40.

Usage
This counter is used to find out radio channel's DL quality and receive level.

68-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=2 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-66.
Figure 68-66 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.67 C901620066 Number of samples of DL RQ=2 and receive level between 41 and 63
Description
This counter counts the number of samples of DL RQ=2 and receive level between 41 and 63 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=2 and receive level is between 41 and 63.

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=2 and receive level between 41 and 63. The measurement point is A, as shown in Figure 68-67.

68-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-67 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.68 C901620067 Number of samples of DL RQ=3 and receive level between 0 and 10
Description
This counter counts the number of samples of DL RQ=3 and receive level between 0 and 10 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=3 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=3 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-68.
Figure 68-68 Measurement Point of BTS Sending Meaurement Report to BSC

68-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.69 C901620068 Number of samples of DL RQ=3 and receive level between 11 and 15
Description
This counter counts the number of samples of DL RQ=3 and receive level between 11 and 15 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=3 and receive level is between 11 and 15.

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=3 and receive level between 11 and 15. The measurement point is A, as shown in Figure 68-69.
Figure 68-69 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.70 C901620069 Number of samples of DL RQ=3 and receive level between 16 and 20
Description
This counter counts the number of samples of DL RQ=3 and receive level between 16 and 20 in DL radio measurement report (preprocessing report or enhanced preprocessing
68-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=3 and receive level is between 16 and 20.

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=3 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-70.
Figure 68-70 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.71 C901620070 Number of samples of DL RQ=3 and receive level between 21 and 30
Description
This counter counts the number of samples of DL RQ=3 and receive level between 21 and 30 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=3 and receive level is between 21 and 30.

Usage
This counter is used to find out radio channel's DL quality and receive level.

68-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=3 and receive level between 21 and 30. The measurement point is A, as shown in Figure 68-71.
Figure 68-71 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.72 C901620071 Number of samples of DL RQ=3 and receive level between 31 and 40
Description
This counter counts the number of samples of DL RQ=3 and receive level between 31 and 40 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=3 and receive level is between 31 and 40.

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=3 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-72.

68-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-72 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.73 C901620072 Number of samples of DL RQ=3 and receive level between 41 and 63
Description
This counter counts the number of samples of DL RQ=3 and receive level between 41 and 63 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=3 and receive level is between 41 and 63.

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=3 and receive level between 41 and 63. The measurement point is A, as shown in Figure 68-73.
Figure 68-73 Measurement Point of BTS Sending Meaurement Report to BSC

68-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.74 C901620073 Number of samples of DL RQ=4 and receive level between 0 and 10
Description
This counter counts the number of samples of DL RQ=4 and receive level between 0 and 10 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=4 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=4 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-74.
Figure 68-74 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.75 C901620074 Number of samples of DL RQ=4 and receive level between 11 and 15
Description
This counter counts the number of samples of DL RQ=4 and receive level between 11 and 15 in DL radio measurement report (preprocessing report or enhanced preprocessing
68-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=4 and receive level is between 11 and 15.

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=4 and receive level between 11 and 15. The measurement point is A, as shown in Figure 68-75.
Figure 68-75 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.76 C901620075 Number of samples of DL RQ=4 and receive level between 16 and 20
Description
This counter counts the number of samples of DL RQ=4 and receive level between 16 and 20 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=4 and receive level is between 16 and 20.

Usage
This counter is used to find out radio channel's DL quality and receive level.

68-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=4 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-76.
Figure 68-76 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.77 C901620076 Number of samples of DL RQ=4 and receive level between 21 and 30
Description
This counter counts the number of samples of DL RQ=4 and receive level between 21 and 30 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=4 and receive level is between 21 and 30.

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=4 and receive level between 21 and 30. The measurement point is A, as shown in Figure 68-77.

68-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-77 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.78 C901620077 Number of samples of DL RQ=4 and receive level between 31 and 40
Description
This counter counts the number of samples of DL RQ=4 and receive level between 31 and 40 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=4 and receive level is between 31 and 40.

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=4 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-78.
Figure 68-78 Measurement Point of BTS Sending Meaurement Report to BSC

68-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.79 C901620078 Number of samples of DL RQ=4 and receive level between 41 and 63
Description
This counter counts the number of samples of DL RQ=4 and receive level between 41 and 63 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=4 and receive level is between 41 and 63.

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=4 and receive level between 41 and 63. The measurement point is A, as shown in Figure 68-79.
Figure 68-79 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.80 C901620079 Number of samples of DL RQ=5 and receive level between 0 and 10
Description
This counter counts the number of samples of DL RQ=5 and receive level between 0 and 10 in DL radio measurement report (preprocessing report or enhanced preprocessing
68-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=5 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=5 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-80.
Figure 68-80 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.81 C901620080 Number of samples of DL RQ=5 and receive level between 11 and 15
Description
This counter counts the number of samples of DL RQ=5 and receive level between 11 and 15 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=5 and receive level is between 11 and 15.

Usage
This counter is used to find out radio channel's DL quality and receive level.

68-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=5 and receive level between 11 and 15. The measurement point is A, as shown in Figure 68-81.
Figure 68-81 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.82 C901620081 Number of samples of DL RQ=5 and receive level between 16 and 20
Description
This counter counts the number of samples of DL RQ=5 and receive level between 16 and 20 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=5 and receive level is between 16 and 20.

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=5 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-82.

68-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-82 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.83 C901620082 Number of samples of DL RQ=5 and receive level between 21 and 30
Description
This counter counts the number of samples of DL RQ=5 and receive level between 21 and 30 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=5 and receive level is between 21 and 30.

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=5 and receive level between 21 and 30. The measurement point is A, as shown in Figure 68-83.
Figure 68-83 Measurement Point of BTS Sending Meaurement Report to BSC

68-70 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.84 C901620083 Number of samples of DL RQ=5 and receive level between 31 and 40
Description
This counter counts the number of samples of DL RQ=5 and receive level between 31 and 40 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=5 and receive level is between 31 and 40.

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=5 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-84.
Figure 68-84 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.85 C901620084 Number of samples of DL RQ=5 and receive level between 41 and 63
Description
This counter counts the number of samples of DL RQ=5 and receive level between 41 and 63 in DL radio measurement report (preprocessing report or enhanced preprocessing
68-71 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=5 and receive level is between 41 and 63.

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=5 and receive level between 41 and 63. The measurement point is A, as shown in Figure 68-85.
Figure 68-85 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.86 C901620085 Number of samples of DL RQ=6 and receive level between 0 and 10
Description
This counter counts the number of samples of DL RQ=6 and receive level between 0 and 10 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=6 and receive level is between 0 and 10.

Usage
This counter is used to find out radio channel's DL quality and receive level.

68-72 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=6 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-86.
Figure 68-86 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.87 C901620086 Number of samples of DL RQ=6 and receive level between 11 and 15
Description
This counter counts the number of samples of DL RQ=6 and receive level between 11 and 15 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=6 and receive level is between 11 and 15.

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=6 and receive level between 11 and 15. The measurement point is A, as shown in Figure 68-87.

68-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-87 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.88 C901620087 Number of samples of DL RQ=6 and receive level between 16 and 20
Description
This counter counts the number of samples of DL RQ=6 and receive level between 16 and 20 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=6 and receive level is between 16 and 20.

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=6 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-88.
Figure 68-88 Measurement Point of BTS Sending Meaurement Report to BSC

68-74 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.89 C901620088 Number of samples of DL RQ=6 and receive level between 21 and 30
Description
This counter counts the number of samples of DL RQ=6 and receive level between 21 and 30 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=6 and receive level is between 21 and 30.

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=6 and receive level between 21 and 30. The measurement point is A, as shown in Figure 68-89.
Figure 68-89 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.90 C901620089 Number of samples of DL RQ=6 and receive level between 31 and 40
Description
This counter counts the number of samples of DL RQ=6 and receive level between 31 and 40 in DL radio measurement report (preprocessing report or enhanced preprocessing
68-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=6 and receive level is between 31 and 40.

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=6 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-90.
Figure 68-90 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.91 C901620090 Number of samples of DL RQ=6 and receive level between 41 and 63
Description
This counter counts the number of samples of DL RQ=6 and receive level between 41 and 63 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=6 and receive level is between 41 and 63.

Usage
This counter is used to find out radio channel's DL quality and receive level.

68-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=6 and receive level between 41 and 63. The measurement point is A, as shown in Figure 68-91.
Figure 68-91 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.92 C901620091 Number of samples of DL RQ=7 and receive level between 0 and 10
Description
This counter counts the number of samples of DL RQ=7 and receive level between 0 and 10 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=7 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=7 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 68-92.

68-77 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-92 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.93 C901620092 Number of samples of DL RQ=7 and receive level between 11 and 15
Description
This counter counts the number of samples of DL RQ=7 and receive level between 11 and 15 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=7 and receive level is between 11 and 15.

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=7 and receive level between 11 and 15. The measurement point is A, as shown in Figure 68-93.
Figure 68-93 Measurement Point of BTS Sending Meaurement Report to BSC

68-78 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Unit
Times

68.94 C901620093 Number of samples of DL RQ=7 and receive level between 16 and 20
Description
This counter counts the number of samples of DL RQ=7 and receive level between 16 and 20 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=7 and receive level is between 16 and 20.

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=7 and receive level is between 16 and 20. The measurement point is A, as shown in Figure 68-94.
Figure 68-94 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.95 C901620094 Number of samples of DL RQ=7 and receive level between 21 and 30
Description
This counter counts the number of samples of DL RQ=7 and receive level between 21 and 30 in DL radio measurement report (preprocessing report or enhanced preprocessing
68-79 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=7 and receive level is between 21 and 30.

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=7 and receive level between 21 and 30. The measurement point is A, as shown in Figure 68-95.
Figure 68-95 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.96 C901620095 Number of samples of DL RQ=7 and receive level between 31 and 40
Description
This counter counts the number of samples of DL RQ=7 and receive level between 31 and 40 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=7 and receive level is between 31 and 40.

Usage
This counter is used to find out radio channel's DL quality and receive level.

68-80 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 68 Measurement Reprot Serving Cell Measurement

Measurement Point
This counter counts when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=7 and receive level is between 31 and 40. The measurement point is A, as shown in Figure 68-96.
Figure 68-96 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68.97 C901620096 Number of samples of DL RQ=7 and receive level between 41 and 63
Description
This counter counts the number of samples of DL RQ=7 and receive level between 41 and 63 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=7 and receive level is between 41 and 63.

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=7 and receive level between 41 and 63. The measurement point is A, as shown in Figure 68-97.

68-81 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 68-97 Measurement Point of BTS Sending Meaurement Report to BSC

Unit
Times

68-82 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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.
Figure 69-1 Measurement Point of BTS Sending Meaurement Report to BSC

Statistic unit in this measurement is cell.

69-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
This counter counts the number of samples with DL level in local cell subtracting the level in adjacent cell within -9dB~-5dB in received DL radio measurement report (preprocessing report or enhanced preprocessing measurement report).

Usage
This counter is used to find out DL level of adjacent cell.

69-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 69 Measurement Report Adjacent Cell Measurement

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 within -9dB~-5dB, as shown in Figure 69-3.
Figure 69-3 Measurement Point of BTS Sending Measurement Report to BSC

Unit
Times

69.4 C901630003 Number of samples with C/I between -4db and 0db
Description
This counter counts the number of samples with DL level in local cell subtracting the level in adjacent cell within -4dB~0dB 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 within -4dB~0dB, as shown in Figure 69-4.

69-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 69-4 Measurement Point of BTS Sending Measurement Report to BSC

Unit
Times

69.5 C901630004 Number of samples with C/I between 1db and 5db
Description
This counter counts the number of samples with DL level in local cell subtracting the level in adjacent cell within 1dB~5dB 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 within 1dB~5dB, as shown in Figure 69-5.
Figure 69-5 Measurement Point of BTS Sending Measurement Report to BSC

Unit
Times
69-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 69 Measurement Report Adjacent Cell Measurement

69.6 C901630005 Number of samples with C/I between 6db and 10db
Description
This counter counts the number of samples with DL level in local cell subtracting the level in adjacent cell within 6dB~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 within 6dB~10dB, as shown in Figure 69-6.
Figure 69-6 Measurement Point of BTS Sending Measurement Report to BSC

Unit
Times

69.7 C901630006 Number of samples with C/I between 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 report or enhanced preprocessing measurement report).

Usage
This counter is used to find out DL level of adjacent cell.
69-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 within 11dB~15dB, as shown in Figure 69-7.
Figure 69-7 Measurement Point of BTS Sending Measurement Report to BSC

Unit
Times

69.8 C901630007 Number of samples with C/I between 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 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 within 16dB~20dB, as shown in Figure 69-8.

69-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 69 Measurement Report Adjacent Cell Measurement

Figure 69-8 Measurement Point of BTS Sending Measurement Report to BSC

Unit
Times

69.9 C901630008 Number of samples with C/I > 20db

Description
This counter counts the number of samples with DL level in local cell subtracting the level in adjacent cell > 20dB in received DL radio measurement report (preprocessing report or enhanced preprocessing measurement report).

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 higher than 20dB, as shown in Figure 69-9.
Figure 69-9 Measurement Point of BTS Sending Measurement Report to BSC

Unit
Times

69-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

69-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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 x 9 ...................................................70-3 C901640004 Average length of PCH queue: 9*64....................................................70-3 C901640005 The percentage of PCH Blocks validly used ........................................70-4 C901640006 Number of paging messages seized by other hyper-priority messages while transmitting on PCH blocks .............................................................................70-4 C901640007 Number of paging messages retransmitted zero times ........................70-5 C901640008 Number of paging messages retransmitted one times .........................70-5 C901640009 Number of paging messages retransmitted two times..........................70-5 C901640010 Number of paging messages retransmitted three times .......................70-6 C901640011 Numbers of paging messages retransmitted four times........................70-6 C901640012 Number of ImmAss message retransmitted zero time..........................70-7 C901640013 Number of ImmAss message retransmitted one time...........................70-7 C901640014 Number of discarded Packet Channel Request ...................................70-7 C901640015 Number of discarded channel requests that are suspected as HO ACC .........................................................................................................................70-8 C901640016 Number of channel requests discarded due to BP board load..............70-9 C901640017 Number of CS Paging MS .................................................................70-10 C901640018 Number of PS Paging MS .................................................................70-10

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.

70-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 70-1 Paging Performance Measurement Reporting

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. This counter is supported in version V6.20.200a or above.

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.
70-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 70 TRX Paging Measurement

Usage
This counter is used to find out the number of failures in receiving CS paging messages at BTS. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the paging performance measurement data is reported periodically.

Unit
Times

70.4 C901640003 Average length of PCH queue: 9 x 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the paging performance measurement data is reported periodically.

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.
70-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the paging performance measurement data is reported periodically.

Unit
Times

70.6 C901640005 The percentage of PCH Blocks validly used

Description
This counter records the percentage of sending valid information on PCH resource block of CCCH of the cell. This counter is supported in version V6.20.614c.

Unit
Percent

Statistics Object
Cell

70.7 C901640006 Number of paging messages seized by other hyper-priority messages while transmitting on PCH blocks
Description
This counter counts the number of sending paging message on the resource block being delayed due to the PCH resource block being preempted by message of higher priority. This counter is supported in version V6.20.614c.

Unit
Times

Statistics Object
Cell
70-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 70 TRX Paging Measurement

70.8 C901640007 Number of paging messages retransmitted zero times

Description
This counter counts the number of paging messages not being retransmitted after the original paging messages are sent. This counter is supported in version V6.20.614c.

Unit
Times

Statistics Object
Cell

70.9 C901640008 Number of paging messages retransmitted one times

Description
This counter counts the number of paging messages being retransmitted once after the original paging messages are sent. This counter is supported in version V6.20.614c.

Unit
Times

Statistics Object
Cell

70.10 C901640009 Number of paging messages retransmitted two times

Description
This counter counts the number of paging messages being retransmitted twice after the original paging messages are sent. This counter is supported in version V6.20.614c.

70-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

Statistics Object
Cell

70.11 C901640010 Number of paging messages retransmitted three times

Description
This counter counts the number of paging messages being retransmitted three times after the original paging messages are sent. This counter is supported in version V6.20.614c.

Unit
Times

Statistics Object
Cell

70.12 C901640011 Numbers of paging messages retransmitted four times

Description
This counter counts the number of paging messages being retransmitted four times after the original paging messages are sent. This counter is supported in version V6.20.614c.

Unit
Times

Statistics Object
Cell

70-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 70 TRX Paging Measurement

70.13 C901640012 Number of ImmAss message retransmitted zero time

Description
This counter counts the number of the original ImmAss messages that are not retransmitted after being transmitted.

Usage
None

Measurement Point
None

Unit
Time

70.14 C901640013 Number of ImmAss message retransmitted one time

Description
This counter counts the number of the original ImmAss messages that are retransmitted once after being transmitted.

Usage
None

Measurement Point
None

Unit
Time

70.15 C901640014 Number of discarded Packet Channel Request

Measured Object
Carrier frequency
70-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
Number of PS channel requests discarded due to flow control This counter is incremeted each time a PS channel request is discarded due to flow control. Upon receiving a PS channel request message from the MS, the BTS uses the channel request filter to evaluate whether this message should be discarded. If the PS channel request message is not discarded, a procedure is initiated for random request message processing. If the PS channel request message meets the condition of flow control, the BTS discards this message, not reporting it to the BSC.

Usage
None

Measurement Point
The measurement point is shown in Figure 70-2.
Figure 70-2 Flow Chart of PS Channel Request Discard

Unit
N/A

70.16 C901640015 Number of discarded channel requests that are suspected as HO ACC
Measured Object
Carrier frequency

Description
Number of random access request messages discarded because they are suspected as HO ACC

70-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 70 TRX Paging Measurement

This counter is incremented each time a random access request message sent to the BUC is discarded. Upon receiving a random access request message from the MS, the BTS filters the random access request message with the channel request filter. If the received message meets the filtering condition, the BTS discards this message.

Usage
None

Measurement Point
The measurement point is shown in Figure 70-3.
Figure 70-3 Flow Chart of Channel Request Discard Due to Being Suspected as HO ACC

Unit
N/A

70.17 C901640016 Number of channel requests discarded due to BP board load

Measured Object
Carrier frequency

Description
Number of CHAN RQD messages discarded due to heavy load of the BP board When the load of the BP board is too heavy, the CHAN RQD messages sent from the MS to the BTS are discarded. The BTS counts the discarded CS CHAN RQD messages and PS CHAN RQD messages.

Usage
None
70-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The measurement point is shown in Figure 70-4.
Figure 70-4 Flow Chart of CHAN RQD Message Discard Due to Heavy Load of BP Board

Unit
N/A

70.18 C901640017 Number of CS Paging MS

Description
This counter counts mobile stations that send CS paging requests through PCH.

Usage
This counter indicates the total number of mobile stations that send CS paging requests through the radio interface

Measurement Point
This counter is updated when the base station reports the number of mobile stations that send CS paging requests.

Unit
None

70.19 C901640018 Number of PS Paging MS

Description
This counter counts mobile stations that send PS paging requests through PCH.

70-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 70 TRX Paging Measurement

Usage
This counter indicates the total number of mobile stations that send PS paging requests through the radio interface

Measurement Point
This counter is updated when the base station reports the number of mobile stations that send PS paging requests.

Unit
None

70-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

70-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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. SDR base station does not support the measurement.
71-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
TRU is measured and reported periodically.

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. SDR base station does not support the measurement.

Measurement Point
TRU is measured and reported periodically.

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. SDR base station does not support the measurement.

Measurement Point
TRU is measured and reported periodically.

Unit
Celsius

71-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

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. SDR base station does not support the measurement.

Measurement Point
TRU is measured and reported periodically.

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. SDR base station does not support the measurement.

Measurement Point
TRU is measured and reported periodically.

Unit
Celsius

71-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

71-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72

Terminal Ability Statistic

Table of Contents
Terminal Ability Statistics ..........................................................................................72-3 C901660001 Number of mobile support single TS DTM ability .................................72-3 C901660002 Number of mobile support DTM GPRS multi TS ability 5 .....................72-4 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 C901660014 Number of mobile support extend DTM EGPRS multi TS ability 6 .....72-15 C901660015 Number of mobile support extend DTM EGPRS multi TS ability 9 .....72-16 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 C901660019 Number of mobile of GPRS multi TS ability 2 ....................................72-21 C901660020 Number of mobile of GPRS multi TS ability 3 ....................................72-22 C901660021 Number of mobile of GPRS multi TS ability 4 ....................................72-24 C901660022 Number of mobile of GPRS multi TS ability 5 ....................................72-25 C901660023 Number of mobile of GPRS multi TS ability 6 ....................................72-27 C901660024 Number of mobile of GPRS multi TS ability 7 ....................................72-28 C901660025 Number of mobile of GPRS multi TS ability 8 ....................................72-30 C901660026 Number of mobile of GPRS multi TS ability 9 ....................................72-31 C901660027 Number of mobile of GPRS multi TS ability 10 ..................................72-33 C901660028 Number of mobile of GPRS multi TS ability 11...................................72-34 C901660029 Number of mobile of GPRS multi TS ability 12 ..................................72-36 C901660030 Number of mobile of GPRS multi TS ability 30 ..................................72-37 C901660031 Number of mobile of GPRS multi TS ability 31 ..................................72-39 C901660032 Number of mobile of GPRS multi TS ability 32 ..................................72-40 C901660033 Number of mobile of GPRS multi TS ability 33 ..................................72-42 C901660034 Number of mobile of GPRS multi TS ability 34 ..................................72-43 C901660035 Number of mobile of EGPRS multi TS ability 1 ..................................72-45 C901660036 Number of mobile of EGPRS multi TS ability 2 ..................................72-46
72-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901660037 Number of mobile of EGPRS multi TS ability 3 ..................................72-48 C901660038 Number of mobile of EGPRS multi TS ability 4 ..................................72-49 C901660039 Number of mobile of EGPRS multi TS ability 5 ..................................72-51 C901660040 Number of mobile of EGPRS multi TS ability 6 ..................................72-52 C901660041 Number of mobile of EGPRS multi TS ability 7 ..................................72-54 C901660042 Number of mobile of EGPRS multi TS ability 8 ..................................72-55 C901660043 Number of mobile of EGPRS multi TS ability 9 ..................................72-57 C901660044 Number of mobile of EGPRS multi TS ability 10 ................................72-58 C901660045 Number of mobile of EGPRS multi TS ability 11 ................................72-60 C901660046 Number of mobile of EGPRS multi TS ability 12 ................................72-61 C901660047 Number of mobile of EGPRS multi TS ability 30 ................................72-63 C901660048 Number of mobile of EGPRS multi TS ability 31 ................................72-64 C901660049 Number of mobile of EGPRS multi TS ability 32 ................................72-66 C901660050 Number of mobile of EGPRS multi TS ability 33 ................................72-67 C901660051 Number of mobile of EGPRS multi TS ability 34 ................................72-69 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 C901660067 Number of MS Supporting Downlink EGPRS2-A ...............................72-85 C901660068 Number of MS Supporting Uplink EGPRS2-A....................................72-86 C901660069 Num of MS supporting PS handover .................................................72-87 C901660070 The Number of MS which Support SAIC............................................72-88 C901660071 The Number of MS which not Support SAIC......................................72-89 C901660072 Num of MS Supporting DLDC............................................................72-90 C901660073 Num of DTM MS Supporting DLDC ...................................................72-90 C901660074 Num of MS Supporting RTTI .............................................................72-91 C901660075 Num of MS Supporting MSRD...........................................................72-91 C901660076 The Number of MS which Support DARP2 ........................................72-92 C901660077 The Number of MS which Support VAMOS1 .....................................72-93 C901660078 The Number of MS which Support VAMOS2 .....................................72-94

72-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

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. Statistic unit in this measurement is cell.

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.

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

72.4 C901660003 Number of mobile support DTM GPRS multi TS ability 9

Description
This counter counts the number of mobiles that support DTM GPRS multi TS ability 9.

72-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Usage
It is used to measure the number of mobiles that support DTM GPRS multi TS ability 9.

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 DTM GPRS multi TS ability 9. The measurement point is A1 or A2, as shown in Figure 72-3.
Figure 72-3 Measurement Point of Number of mobile support DTM GPRS multi TS ability 9

Unit
Times

72.5 C901660004 Number of mobile support DTM GPRS multi TS ability 11

Description
This counter counts the number of mobiles that support DTM GPRS multi TS ability 11.

Usage
It is used to measure the number of mobiles that support DTM GPRS multi TS ability 11.

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 DTM GPRS multi TS ability 11. The measurement point is A1 or A2, as shown in Figure 72-4.
72-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-4 Measurement Point of Number of mobile support DTM GPRS multi TS ability 11

Unit
Times

72.6 C901660005 Number of mobile support DTM EGPRS multi TS ability 5

Description
This counter counts the number of mobiles that support DTM EGPRS multi TS ability 5.

Usage
It is used to measure the number of mobiles that support DTM EGPRS multi TS ability 5.

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 DTM EGPRS multi TS ability 5. The measurement point is A1 or A2, as shown in Figure 72-5.

72-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-5 Measurement Point of Number of mobile support DTM EGPRS multi TS ability 5

Unit
Times

72.7 C901660006 Number of mobile support DTM EGPRS multi TS ability 9

Description
This counter counts the number of mobiles that support DTM EGPRS multi TS ability 9.

Usage
It is used to measure the number of mobiles that support DTM EGPRS multi TS ability 9.

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 DTM EGPRS multi TS ability 9. The measurement point is A1 or A2, as shown in Figure 72-6.

72-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-6 Measurement Point of Number of mobile support DTM EGPRS multi TS ability 9

Unit
Times

72.8 C901660007 Number of mobile support DTM EGPRS multi TS ability 11

Description
This counter counts the number of mobiles that support DTM EGPRS multi TS ability 11.

Usage
It is used to measure the number of mobiles that support DTM EGPRS multi TS ability 11.

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 DTM EGPRS multi TS ability 11. The measurement point is A1 or A2, as shown in Figure 72-7.

72-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-7 Measurement Point of Number of mobile support DTM EGPRS multi TS 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
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 extend DTM GPRS multi TS ability 5. The measurement point is A1 or A2, as shown in Figure 72-8.

72-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-8 Measurement Point of Number of mobile support extend DTM GPRS multi TS ability 5

Unit
Times

72.10 C901660009 Number of mobile support extend DTM GPRS multi TS ability 6
Description
This counter counts the number of mobiles that support extend DTM GPRS multi TS ability 6.

Usage
It is used to measure the number of mobiles that support extend DTM GPRS multi TS ability 6.

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 extend DTM GPRS multi TS ability 6. The measurement point is A1 or A2, as shown in Figure 72-9.

72-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-9 Measurement Point of Number of mobile support extend DTM GPRS multi TS ability 6

Unit
Times

72.11 C901660010 Number of mobile support extend DTM GPRS multi TS ability 9
Description
This counter counts the number of mobiles that support extend DTM GPRS multi TS ability 9.

Usage
It is used to measure the number of mobiles that support extend DTM GPRS multi TS ability 9.

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 extend DTM GPRS multi TS ability 9. The measurement point is A1 or A2, as shown in Figure 72-10.

72-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-10 Measurement Point of Number of mobile support extend DTM GPRS multi TS ability 9

Unit
Times

72.12 C901660011 Number of mobile support extend DTM GPRS multi TS ability 10
Description
This counter counts the number of mobiles that support extend DTM GPRS multi TS ability 10.

Usage
It is used to measure the number of mobiles that support extend DTM GPRS multi TS ability 10.

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 extend DTM GPRS multi TS ability 10. The measurement point is A1 or A2, as shown in Figure 72-11.

72-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-11 Measurement Point of Number of mobile support extend DTM GPRS multi TS ability 10

Unit
Times

72.13 C901660012 Number of mobile support extend DTM GPRS multi TS ability 11
Description
This counter counts the number of mobiles that support extend DTM GPRS multi TS ability 11.

Usage
It is used to measure the number of mobiles that support extend DTM GPRS multi TS ability 11.

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 extend DTM GPRS multi TS ability 11. The measurement point is A1 or A2, as shown in Figure 72-12.

72-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-12 Measurement Point of Number of mobile support extend DTM GPRS multi TS ability 11

Unit
Times

72.14 C901660013 Number of mobile support extend 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
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 extend DTM EGPRS multi TS ability 5. The measurement point is A1 or A2, as shown in Figure 72-13.

72-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-13 Measurement Point of Number of mobile support extend DTM EGPRS multi TS ability 5

Unit
Times

72.15 C901660014 Number of mobile support extend DTM EGPRS multi TS ability 6
Description
This counter counts the number of mobiles that support extend DTM EGPRS multi TS ability 6.

Usage
It is used to measure the number of mobiles that support extend DTM EGPRS multi TS ability 6.

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 extend DTM EGPRS multi TS ability 6. The measurement point is A1 or A2, as shown in Figure 72-14.

72-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-14 Measurement Point of Number of mobile support extend DTM EGPRS multi TS ability 6

Unit
Times

72.16 C901660015 Number of mobile support extend DTM EGPRS multi TS ability 9
Description
This counter counts the number of mobiles that support extend DTM EGPRS multi TS ability 9.

Usage
It is used to measure the number of mobiles that support extend DTM EGPRS multi TS ability 9.

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 extend DTM EGPRS multi TS ability 9. The measurement point is A1 or A2, as shown in Figure 72-15.

72-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-15 Measurement Point of Number of mobile support extend DTM EGPRS multi TS ability 9

Unit
Times

72.17 C901660016 Number of mobile support extend DTM EGPRS multi TS ability 10
Description
This counter counts the number of mobiles that support extend DTM EGPRS multi TS ability 10.

Usage
It is used to measure the number of mobiles that support extend DTM EGPRS multi TS ability 10.

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 extend DTM EGPRS multi TS ability 10. The measurement point is A1 or A2, as shown in Figure 72-16.

72-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-16 Measurement Point of Number of mobile support extend DTM EGPRS multi TS ability 10

Unit
Times

72.18 C901660017 Number of mobile support extend DTM EGPRS multi TS ability 11
Description
This counter counts the number of mobiles that support extend DTM EGPRS multi TS ability 11.

Usage
It is used to measure the number of mobiles that support extend DTM EGPRS multi TS ability 11.

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 extend DTM EGPRS multi TS ability 11. The measurement point is A1 or A2, as shown in Figure 72-17.

72-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-17 Measurement Point of Number of mobile support extend DTM EGPRS 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-18 Measurement Point of Number of mobile of GPRS multi TS ability 1 - (1)

Figure 72-19 Measurement Point of Number of mobile of GPRS multi TS ability 1 - (2)

Figure 72-20 Measurement Point of Number of mobile of GPRS multi TS ability 1 - (3)

Unit
Times
72-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

72.20 C901660019 Number of mobile of GPRS multi TS ability 2

Description
This counter counts the number of mobiles that support GPRS multi TS ability 2.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 2.

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 2. The measurement point is A1, A2, and A3, as shown in Figure 72-21, Figure 72-22, Figure 72-23.
Figure 72-21 Measurement Point of Number of mobile of GPRS multi TS ability 2 - (1)

Figure 72-22 Measurement Point of Number of mobile of GPRS multi TS ability 2 - (2)

72-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-23 Measurement Point of Number of mobile of GPRS multi TS ability 2 - (3)

Unit
Times

72.21 C901660020 Number of mobile of GPRS multi TS ability 3

Description
This counter counts the number of mobiles that support GPRS multi TS ability 3.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 3.

Measurement Point
This counter increments while PS control plane receives the downlink assignment requests sent by the user plane, the resource 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 3. The measurement point is A1, A2, and A3, as shown in Figure 72-24, Figure 72-25, Figure 72-26.

72-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-24 Measurement Point of Number of mobile of GPRS multi TS ability 3 - (1)

Figure 72-25 Measurement Point of Number of mobile of GPRS multi TS ability 3 - (2)

Figure 72-26 Measurement Point of Number of mobile of GPRS multi TS ability 3 - (3)

Unit
Times

72-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

72.22 C901660021 Number of mobile of GPRS multi TS ability 4

Description
This counter counts the number of mobiles that support GPRS multi TS ability 4.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 4.

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 4. The measurement point is A1, A2, and A3, as shown in Figure 72-27, Figure 72-28, Figure 72-29.
Figure 72-27 Measurement Point of Number of mobile of GPRS multi TS ability 4 - (1)

Figure 72-28 Measurement Point of Number of mobile of GPRS multi TS ability 4 - (2)

72-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-29 Measurement Point of Number of mobile of GPRS multi TS ability 4 - (3)

Unit
Times

72.23 C901660022 Number of mobile of GPRS multi TS ability 5

Description
This counter counts the number of mobiles that support GPRS multi TS ability 5.

Usage
This counter is used to measure the number of link setup requests originated from BSC to TC.

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 5. The measurement point is A1, A2, and A3, as shown in Figure 72-30, Figure 72-31, Figure 72-32.

72-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-30 Measurement Point of Number of mobile of GPRS multi TS ability 5 - (1)

Figure 72-31 Measurement Point of Number of mobile of GPRS multi TS ability 5 - (2)

Figure 72-32 Measurement Point of Number of mobile of GPRS multi TS ability 5 - (3)

Unit
Times

72-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

72.24 C901660023 Number of mobile of GPRS multi TS ability 6

Description
This counter counts the number of mobiles that support GPRS multi TS ability 6.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 6.

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 6. The measurement point is A1, A2, and A3, as shown in Figure 72-33, Figure 72-34, Figure 72-35.
Figure 72-33 Measurement Point of Number of mobile of GPRS multi TS ability 6 - (1)

Figure 72-34 Measurement Point of Number of mobile of GPRS multi TS ability 6 - (2)

72-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-35 Measurement Point of Number of mobile of GPRS multi TS ability 6 - (3)

Unit
Times

72.25 C901660024 Number of mobile of GPRS multi TS ability 7

Description
This counter counts the number of mobiles that support GPRS multi TS ability 7.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 7.

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 7. The measurement point is A1, A2, and A3, as shown in Figure 72-36, Figure 72-37, Figure 72-38.

72-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-36 Measurement Point of Number of mobile of GPRS multi TS ability 7 - (1)

Figure 72-37 Measurement Point of Number of mobile of GPRS multi TS ability 7 - (2)

Figure 72-38 Measurement Point of Number of mobile of GPRS multi TS ability 7 - (3)

Unit
Times

72-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

72.26 C901660025 Number of mobile of GPRS multi TS ability 8

Description
This counter counts the number of mobiles that support GPRS multi TS ability 8.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 8.

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 8. The measurement point is A1, A2, and A3, as shown in Figure 72-39, Figure 72-40, Figure 72-41.
Figure 72-39 Measurement Point of Number of mobile of GPRS multi TS ability 8 - (1)

Figure 72-40 Measurement Point of Number of mobile of GPRS multi TS ability 8 - (2)

72-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-41 Measurement Point of Number of mobile of GPRS multi TS ability 8 - (3)

Unit
Times

72.27 C901660026 Number of mobile of GPRS multi TS ability 9

Description
This counter counts the number of mobiles that support GPRS multi TS ability 9.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 9.

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 9. The measurement point is A1, A2, and A3, as shown in Figure 72-42, Figure 72-43, Figure 72-44.

72-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-42 Measurement Point of Number of mobile of GPRS multi TS ability 9 - (1)

Figure 72-43 Measurement Point of Number of mobile of GPRS multi TS ability 9 - (2)

Figure 72-44 Measurement Point of Number of mobile of GPRS multi TS ability 9 - (3)

Unit
Times

72-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

72.28 C901660027 Number of mobile of GPRS multi TS ability 10

Description
This counter counts the number of mobiles that support GPRS multi TS ability 10.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 10.

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 10. The measurement point is A1, A2, and A3, as shown in Figure 72-45, Figure 72-46, Figure 72-47.
Figure 72-45 Measurement Point of Number of mobile of GPRS multi TS ability 10 - (1)

Figure 72-46 Measurement Point of Number of mobile of GPRS multi TS ability 10 - (2)

72-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-47 Measurement Point of Number of mobile of GPRS multi TS ability 10 - (3)

Unit
Times

72.29 C901660028 Number of mobile of GPRS multi TS ability 11

Description
This counter counts the number of mobiles that support GPRS multi TS ability 11.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 11.

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 11. The measurement point is A1, A2, and A3, as shown in Figure 72-48, Figure 72-49, Figure 72-50.

72-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-48 Measurement Point of Number of mobile of GPRS multi TS ability 11 - (1)

Figure 72-49 Measurement Point of Number of mobile of GPRS multi TS ability 11 - (2)

Figure 72-50 Measurement Point of Number of mobile of GPRS multi TS ability 11 - (3)

Unit
Times

72-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

72.30 C901660029 Number of mobile of GPRS multi TS ability 12

Description
This counter counts the number of mobiles that support GPRS multi TS ability 12.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 12.

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 12. The measurement point is A1, A2, and A3, as shown in Figure 72-51, Figure 72-52, Figure 72-53.
Figure 72-51 Measurement Point of Number of mobile of GPRS multi TS ability 12 - (1)

Figure 72-52 Measurement Point of Number of mobile of GPRS multi TS ability 12 - (2)

72-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-53 Measurement Point of Number of mobile of GPRS multi TS ability 12 - (3)

Unit
Times

72.31 C901660030 Number of mobile of GPRS multi TS ability 30

Description
This counter counts the number of mobiles that support GPRS multi TS ability 30.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 30.

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 30. The measurement point is A1, A2, and A3, as shown in Figure 72-54, Figure 72-55, Figure 72-56.

72-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-54 Measurement Point of Number of mobile of GPRS multi TS ability 30 - (1)

Figure 72-55 Measurement Point of Number of mobile of GPRS multi TS ability 30 - (2)

Figure 72-56 Measurement Point of Number of mobile of GPRS multi TS ability 30 - (3)

Unit
Times

72-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

72.32 C901660031 Number of mobile of GPRS multi TS ability 31

Description
This counter counts the number of mobiles that support GPRS multi TS ability 31.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 31.

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 31. The measurement point is A1, A2, and A3, as shown in Figure 72-57, Figure 72-58, Figure 72-59.
Figure 72-57 Measurement Point of Number of mobile of GPRS multi TS ability 31 - (1)

Figure 72-58 Measurement Point of Number of mobile of GPRS multi TS ability 31 - (2)

72-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-59 Measurement Point of Number of mobile of GPRS multi TS ability 31 - (3)

Unit
Times

72.33 C901660032 Number of mobile of GPRS multi TS ability 32

Description
This counter counts the number of mobiles that support GPRS multi TS ability 32.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 32.

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 32. The measurement point is A1, A2, and A3, as shown in Figure 72-60, Figure 72-61, Figure 72-62.

72-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-60 Measurement Point of Number of mobile of GPRS multi TS ability 32 - (1)

Figure 72-61 Measurement Point of Number of mobile of GPRS multi TS ability 32 - (2)

Figure 72-62 Measurement Point of Number of mobile of GPRS multi TS ability 32 - (3)

Unit
Times

72-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

72.34 C901660033 Number of mobile of GPRS multi TS ability 33

Description
This counter counts the number of mobiles that support GPRS multi TS ability 33.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 33.

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 33. The measurement point is A1, A2, and A3, as shown in Figure 72-63, Figure 72-64, Figure 72-65.
Figure 72-63 Measurement Point of Number of mobile of GPRS multi TS ability 33 - (1)

Figure 72-64 Measurement Point of Number of mobile of GPRS multi TS ability 33 - (2)

72-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-65 Measurement Point of Number of mobile of GPRS multi TS ability 33 - (3)

Unit
Times

72.35 C901660034 Number of mobile of GPRS multi TS ability 34

Description
This counter counts the number of mobiles that support GPRS multi TS ability 34.

Usage
It is used to measure the number of mobiles that support GPRS multi TS ability 34.

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 34. The measurement point is A1, A2, and A3, as shown in Figure 72-66, Figure 72-67, Figure 72-68.

72-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-66 Measurement Point of Number of mobile of GPRS multi TS ability 34 - (1)

Figure 72-67 Measurement Point of Number of mobile of GPRS multi TS ability 34 - (2)

Figure 72-68 Measurement Point of Number of mobile of GPRS multi TS ability 34 - (3)

Unit
Times

72-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

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
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 EGPRS multi TS ability 1. The measurement point is A1, A2, and A3, as shown in Figure 72-69, Figure 72-70, Figure 72-71.
Figure 72-69 Measurement Point of Number of mobile of EGPRS multi TS ability 1 - (1)

Figure 72-70 Measurement Point of Number of mobile of EGPRS multi TS ability 1 - (2)

72-45 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-71 Measurement Point of Number of mobile of EGPRS multi TS ability 1 - (3)

Unit
Times

72.37 C901660036 Number of mobile of EGPRS multi TS ability 2

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 2.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 2.

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 EGPRS multi TS ability 2. The measurement point is A1, A2, and A3, as shown in Figure 72-72, Figure 72-73, Figure 72-74.

72-46 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-72 Measurement Point of Number of mobile of EGPRS multi TS ability 2 - (1)

Figure 72-73 Measurement Point of Number of mobile of EGPRS multi TS ability 2 - (2)

Figure 72-74 Measurement Point of Number of mobile of EGPRS multi TS ability 2 - (3)

Unit
Times
72-47 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

72.38 C901660037 Number of mobile of EGPRS multi TS ability 3

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 3.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 3.

Measurement Point
This counter increments while PS control plane receives the downlink assignment requests sent by the user plane, the resource 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 EGPRS multi TS ability 3. The measurement point is A1, A2, and A3, as shown in Figure 72-75, Figure 72-76, Figure 72-77.
Figure 72-75 Measurement Point of Number of mobile of EGPRS multi TS ability 3 - (1)

Figure 72-76 Measurement Point of Number of mobile of EGPRS multi TS ability 3 - (2)

72-48 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-77 Measurement Point of Number of mobile of EGPRS multi TS ability 3 - (3)

Unit
Times

72.39 C901660038 Number of mobile of EGPRS multi TS ability 4

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 4.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 4.

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 EGPRS multi TS ability 4. The measurement point is A1, A2, and A3, as shown in Figure 72-78, Figure 72-79, Figure 72-80.

72-49 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-78 Measurement Point of Number of mobile of EGPRS multi TS ability 4 - (1)

Figure 72-79 Measurement Point of Number of mobile of EGPRS multi TS ability 4 - (2)

Figure 72-80 Measurement Point of Number of mobile of EGPRS multi TS ability 4 - (3)

Unit
Times

72-50 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

72.40 C901660039 Number of mobile of EGPRS multi TS ability 5

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 5.

Usage
This counter is used to measure the number of link setup requests originated from BSC to TC.

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 EGPRS multi TS ability 5. The measurement point is A1, A2, and A3, as shown in Figure 72-81, Figure 72-82, Figure 72-83.
Figure 72-81 Measurement Point of Number of mobile of EGPRS multi TS ability 5 - (1)

72-51 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-82 Measurement Point of Number of mobile of EGPRS multi TS ability 5 - (2)

Figure 72-83 Measurement Point of Number of mobile of EGPRS multi TS ability 5 - (3)

Unit
Times

72.41 C901660040 Number of mobile of EGPRS multi TS ability 6

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 6.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 6.

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,
72-52 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

or the instance setup indication sent by the user plane and the message indicates the MS supports EGPRS multi TS ability 6. The measurement point is A1, A2, and A3, as shown in Figure 72-84, Figure 72-85, Figure 72-86.
Figure 72-84 Measurement Point of Number of mobile of EGPRS multi TS ability 6 - (1)

Figure 72-85 Measurement Point of Number of mobile of EGPRS multi TS ability 6 - (2)

Figure 72-86 Measurement Point of Number of mobile of EGPRS multi TS ability 6 - (3)

72-53 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

72.42 C901660041 Number of mobile of EGPRS multi TS ability 7

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 7.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 7.

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 EGPRS multi TS ability 7. The measurement point is A1, A2, and A3, as shown in Figure 72-87, Figure 72-88, Figure 72-89.
Figure 72-87 Measurement Point of Number of mobile of EGPRS multi TS ability 7 - (1)

72-54 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-88 Measurement Point of Number of mobile of EGPRS multi TS ability 7 - (2)

Figure 72-89 Measurement Point of Number of mobile of EGPRS multi TS ability 7 - (3)

Unit
Times

72.43 C901660042 Number of mobile of EGPRS multi TS ability 8

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 8.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 8.

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,
72-55 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

or the instance setup indication sent by the user plane and the message indicates the MS supports EGPRS multi TS ability 8. The measurement point is A1, A2, and A3, as shown in Figure 72-90, Figure 72-91, Figure 72-92.
Figure 72-90 Measurement Point of Number of mobile of EGPRS multi TS ability 8 - (1)

Figure 72-91 Measurement Point of Number of mobile of EGPRS multi TS ability 8 - (2)

Figure 72-92 Measurement Point of Number of mobile of EGPRS multi TS ability 8 - (3)

72-56 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Unit
Times

72.44 C901660043 Number of mobile of EGPRS multi TS ability 9

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 9.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 9.

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 EGPRS multi TS ability 9. The measurement point is A1, A2, and A3, as shown in Figure 72-93, Figure 72-94, Figure 72-95.
Figure 72-93 Measurement Point of Number of mobile of EGPRS multi TS ability 9 - (1)

72-57 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-94 Measurement Point of Number of mobile of EGPRS multi TS ability 9 - (2)

Figure 72-95 Measurement Point of Number of mobile of EGPRS multi TS ability 9 - (3)

Unit
Times

72.45 C901660044 Number of mobile of EGPRS multi TS ability 10

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 10.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 10.

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,
72-58 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

or the instance setup indication sent by the user plane and the message indicates the MS supports EGPRS multi TS ability 10. The measurement point is A1, A2, and A3, as shown in Figure 72-96, Figure 72-97, Figure 72-98.
Figure 72-96 Measurement Point of Number of mobile of EGPRS multi TS ability 10 - (1)

Figure 72-97 Measurement Point of Number of mobile of EGPRS multi TS ability 10 - (2)

Figure 72-98 Measurement Point of Number of mobile of EGPRS multi TS ability 10 - (3)

72-59 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

72.46 C901660045 Number of mobile of EGPRS multi TS ability 11

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 11.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 11.

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 EGPRS multi TS ability 11. The measurement point is A1, A2, and A3, as shown in Figure 72-99, Figure 72-100, Figure 72-101.
Figure 72-99 Measurement Point of Number of mobile of EGPRS multi TS ability 11 - (1)

72-60 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-100 Measurement Point of Number of mobile of EGPRS multi TS ability 11 - (2)

Figure 72-101 Measurement Point of Number of mobile of EGPRS multi TS ability 11 - (3)

Unit
Times

72.47 C901660046 Number of mobile of EGPRS multi TS ability 12

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 12.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 12.

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,
72-61 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

or the instance setup indication sent by the user plane and the message indicates the MS supports EGPRS multi TS ability 12. The measurement point is A1, A2, and A3, as shown in Figure 72-102, Figure 72-103, Figure 72-104.
Figure 72-102 Measurement Point of Number of mobile of EGPRS multi TS ability 12 - (1)

Figure 72-103 Measurement Point of Number of mobile of EGPRS multi TS ability 12 - (2)

Figure 72-104 Measurement Point of Number of mobile of EGPRS multi TS ability 12 - (3)

72-62 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Unit
Times

72.48 C901660047 Number of mobile of EGPRS multi TS ability 30

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 30.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 30.

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 EGPRS multi TS ability 30. The measurement point is A1, A2, and A3, as shown in Figure 72-105, Figure 72-106, Figure 72-107.
Figure 72-105 Measurement Point of Number of mobile of EGPRS multi TS ability 30 - (1)

72-63 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-106 Measurement Point of Number of mobile of EGPRS multi TS ability 30 - (2)

Figure 72-107 Measurement Point of Number of mobile of EGPRS multi TS ability 30 - (3)

Unit
Times

72.49 C901660048 Number of mobile of EGPRS multi TS ability 31

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 31.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 31.

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,
72-64 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

or the instance setup indication sent by the user plane and the message indicates the MS supports EGPRS multi TS ability 31. The measurement point is A1, A2, and A3, as shown in Figure 72-108, Figure 72-109, Figure 72-110.
Figure 72-108 Measurement Point of Number of mobile of EGPRS multi TS ability 31 - (1)

Figure 72-109 Measurement Point of Number of mobile of EGPRS multi TS ability 31 - (2)

Figure 72-110 Measurement Point of Number of mobile of EGPRS multi TS ability 31 - (3)

72-65 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

72.50 C901660049 Number of mobile of EGPRS multi TS ability 32

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 32.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 32.

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 EGPRS multi TS ability 32. The measurement point is A1, A2, and A3, as shown in Figure 72-111, Figure 72-112, Figure 72-113.
Figure 72-111 Measurement Point of Number of mobile of EGPRS multi TS ability 32 - (1)

72-66 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-112 Measurement Point of Number of mobile of EGPRS multi TS ability 32 - (2)

Figure 72-113 Measurement Point of Number of mobile of EGPRS multi TS ability 32 - (3)

Unit
Times

72.51 C901660050 Number of mobile of EGPRS multi TS ability 33

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 33.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 33.

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,
72-67 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

or the instance setup indication sent by the user plane and the message indicates the MS supports EGPRS multi TS ability 33. The measurement point is A1, A2, and A3, as shown in Figure 72-114, Figure 72-115, Figure 72-116.
Figure 72-114 Measurement Point of Number of mobile of EGPRS multi TS ability 33 - (1)

Figure 72-115 Measurement Point of Number of mobile of EGPRS multi TS ability 33 - (2)

Figure 72-116 Measurement Point of Number of mobile of EGPRS multi TS ability 33 - (3)

72-68 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Unit
Times

72.52 C901660051 Number of mobile of EGPRS multi TS ability 34

Description
This counter counts the number of mobiles that support EGPRS multi TS ability 34.

Usage
It is used to measure the number of mobiles that support EGPRS multi TS ability 34.

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 EGPRS multi TS ability 34. The measurement point is A1, A2, and A3, as shown in Figure 72-117, Figure 72-118, Figure 72-119.
Figure 72-117 Measurement Point of Number of mobile of EGPRS multi TS ability 34 - (1)

72-69 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-118 Measurement Point of Number of mobile of EGPRS multi TS ability 34 - (2)

Figure 72-119 Measurement Point of Number of mobile of EGPRS multi TS ability 34 - (3)

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
This counter increments while Rancs process receives the setup (caller) or call confirmed message (callee) and the voice version contained in this message is EFR. The measurement point is A1 (caller) and A2 (callee), as shown in Figure 72-122.
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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

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 AMRFR. The measurement point is A1 (caller) and A2 (callee), as shown in Figure 72-123.
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
This counter increments while Rancs process receives the setup (caller) or call confirmed message (callee) and the voice version contained in this message is AMRHR. The measurement point is A1 (caller) and A2 (callee), as shown in Figure 72-124.

72-73 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
This counter increments while Rancs process receives the setup (caller) or call confirmed 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-125 Measurement Point of Number of mobile support wideband AMROFR

Unit
Times

72.59 C901660058 Number of mobile support wideband 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
This counter increments while Rancs process receives the setup (caller) or call confirmed message (callee) and the voice version contained in this message is wideband AMRFR. The measurement point is A1 (caller) and A2 (callee), as shown in Figure 72-126.

72-75 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-126 Measurement Point of Number of mobile support wideband AMRFR

Unit
Times

72.60 C901660059 Number of mobile support wideband 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
This counter increments while Rancs process receives the setup (caller) or call confirmed message (callee) and the voice version contained in this message is wideband AMROHR. The measurement point is A1 (caller) and A2 (callee), as shown in Figure 72-127.

72-76 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

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
This counter increments while Rancs process receives the setup (caller) or call confirmed message (callee) and the voice version contained in this message is AMROHR. The measurement point is A1 (caller) and A2 (callee), as shown in Figure 72-128.
Figure 72-128 Measurement Point of Number of mobile support AMROHR

72-77 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

72.62 C901660061 Number of mobile support extend uplink TBF

Description
This counter counts the number of mobiles that support extended uplink TBF.

Usage
It is used to measure the number of mobiles that support extended uplink TBF.

Measurement 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 in Figure 72-129 and Figure 72-130.
Figure 72-129 Measurement Point of Number of mobile support extend uplink TBF - (1)

72-78 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

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 Figure 72-131 and Figure 72-132.

72-79 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

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 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
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 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 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

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
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 Classmark3 is received. The measurement point is A1 or A2, as shown in Figure 72-137.

72-83 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
This counter increments while PS control plane receives the downlink assignment requests sent by the user plane or the resource requests sent by the user plane on two-phase access and it counts the number of samples that receive that radio access ability. The measurement point is A1 and A2, as shown in Figure 72-138 and Figure 72-139.

72-84 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

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 C901660067 Number of MS Supporting Downlink EGPRS2-A

Description
This counter counts the number of mobiles that support Downlink EGPRS2-A.

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 Downlink

72-85 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

EGPRS2-A is supported, the counter increments. The measurement point is A1 and A2, as shown in Figure 72-140 and Figure 72-141.
Figure 72-140 Updated of Number of mobile support Downlink EGPRS2-A - (1)

Figure 72-141 Updated of Number of mobile support Downlink EGPRS2-A - (2)

Unit
Times

72.69 C901660068 Number of MS Supporting Uplink EGPRS2-A

Description
This counter counts the number of mobiles that support Uplink EGPRS2-A.

72-86 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

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 Uplink EGPRS2-A is supported, the counter increments. The measurement point is A1 and A2, as shown in Figure 72-142 and Figure 72-143.
Figure 72-142 Updated of Number of mobile support Uplink EGPRS2-A - (1)

Figure 72-143 Updated of Number of mobile support Uplink EGPRS2-A - (2)

Unit
Times

72.70 C901660069 Num of MS supporting PS handover

Statistics object: MS
MS

72-87 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 measurement point is A, as shown in Figure 72-144.
Figure 72-144 Measurement Point of Number of MS supporting PS handover

Unit
Times

72.71 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. This counter is supported in version V6.20.210a or above.

Measurement Point
1. When BSC receives the handover/assignment failure message after sending the AssignCmd command, if the classmark is changed or updated, the counter counts. The measurement point is A1, as shown in Figure 72-145.

72-88 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-145 Assignment/Handover Flow

2. When BSC receives the Hoperformed Ack message, the counter counts. measurement point is A1, as shown in Figure 72-146.
Figure 72-146 Handover Flow

The

Unit
Times

72.72 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.
72-89 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter is supported in version V6.20.210a or above.

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.73 C901660072 Num of MS Supporting DLDC

Description
This counter counts mobile stations that support Downlink Dual Carrier (DLDC) in a cell.

Measurement Point
This counter is incremented when the RANPS in IDLE state receives a downlink assignment request, which contains the DLDC flag value 1, from the UMC.

Unit
Times

72.74 C901660073 Num of DTM MS Supporting DLDC

Description
This counter counts mobile stations that support DLDC Dual Transfer Mode (DTM) in a cell.

Measurement Point
This counter is incremented when the RANPS in IDLE state receives a downlink assignment request, which contains the DLDC DTM flag value 1, from the UMC.

Unit
Times

72-90 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

72.75 C901660074 Num of MS Supporting RTTI

Description
This counter counts mobile stations that support Reduced Transmission Time Interval (RTTI) in the downlink in a cell.

Measurement Point
This counter is incremented when the RANPS in IDLE state receives a downlink assignment request, which contains the RTTI flag value 1, from the UMC.

Unit
Times

72.76 C901660075 Num of MS Supporting MSRD

Description
This counter counts the number of mobiles that support MSRD.

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 MSRD is supported, the counter increments. The measurement point is A1 and A2, as shown in Figure 72-147 and Figure 72-148.
Figure 72-147 Updated of Number of mobile support MSRD - (1)

72-91 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 72-148 Updated of Number of mobile support MSRD - (2)

Unit
Times

72.77 C901660076 The Number of MS which Support DARP2

Measured Object
Cell

Description
This counter is incremented each time a classmark change message or classmark update message is received from an MS supporting DARP2.

Measurement Point
The measurement point is A1 in Figure 72-149, and A2 in Figure 72-150.
Figure 72-149 Classmark Change Procedure

72-92 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 72 Terminal Ability Statistic

Figure 72-150 Classmark Update Procedure

Unit
Times

72.78 C901660077 The Number of MS which Support VAMOS1

Measured Object
Cell

Description
This counter is incremented each time a classmark change message or classmark update message is received from an MS supporting VAMOS1.

Measurement Point
The measurement point is A1 in Figure 72-151, and A2 in Figure 72-152.
Figure 72-151 Classmark Change Procedure

Figure 72-152 Classmark Update Procedure

Unit
Times
72-93 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

72.79 C901660078 The Number of MS which Support VAMOS2

Measured Object
Cell

Description
This counter is incremented each time a classmark change message or classmark update message is received from an MS supporting VAMOS2.

Measurement Point
The measurement point is A1 in Figure 72-153, and A2 in Figure 72-154.
Figure 72-153 Classmark Change Procedure

Figure 72-154 Classmark Update Procedure

Unit
Times

72-94 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 73

MTP3 Signaling Link Statistics

Table of Contents
Overview ..................................................................................................................73-2 C901670001 Duration of Signaling Link Out of Service ............................................73-3 C901670002 Number of Signaling Link Out of Service .............................................73-3 C901670003 Number of Message Signal Unit Sent ..................................................73-3 C901670004 Octets of SIF-SIO Sent........................................................................73-4 C901670005 Number of Message Signal Unit Received...........................................73-4 C901670006 Octets of SIF-SIO Received ................................................................73-4 C901670007 Peak Traffic of Signaling Link ..............................................................73-4 C901670008 Peak Traffic Duration of Signaling Link ................................................73-5 C901670009 Number of Change Over on OMP........................................................73-6 C901670010 Number of TFP Received ....................................................................73-6 C901670011 Ten thousand rate of Mtp3 Link Occupy...............................................73-6 C901670012 Number of SCCP Message Signal Unit Received................................73-7 C901670013 Number of SCCP Message Signal Unit Sent .......................................73-7 C901670014 Number of A2SP Message Signal Unit Received.................................73-8 C901670015 Number of A2SP Message Signal Unit Sent ........................................73-8 C901670016 Number of Stm Message Signal Unit Received ...................................73-8 C901670017 Number of Stm Message Signal Unit Sent...........................................73-8 C901670018 Number of Sltm Message Signal Unit Received...................................73-9 C901670019 Number of Sltm Message Signal Unit Sent ..........................................73-9 C901670020 Octets of SCCP SIF-SIO Received......................................................73-9 C901670021 Octets of SCCP SIF-SIO Sent .............................................................73-9 C901670022 Octets of MTP2 SIF-SIO Received ....................................................73-10 C901670023 Octets of MTP2 SIF-SIO Sent ...........................................................73-10 C901670024 Octets of Stm SIF-SIO Received .......................................................73-10 C901670025 Octets of Stm SIF-SIO Sent ..............................................................73-10 C901670026 Octets of Sltm SIF-SIO Received ...................................................... 73-11 C901670027 Octets of Sltm SIF-SIO Sent.............................................................. 73-11 C901670028 Number of message discarded due to Congestion ............................ 73-11 C901670029 Number of restrictions Level 1 ........................................................... 73-11 C901670030 Number of restrictions Level 2 ...........................................................73-12 C901670031 Number of restrictions Level 3 ...........................................................73-12 C901670032 Duration of Restrictions Level 1 .........................................................73-12 C901670033 Duration of Restrictions Level 2 .........................................................73-13
73-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901670034 Duration of Restrictions Level 3 .........................................................73-13 C901670035 Duration of manual prohibition...........................................................73-13 C901670036 Number of local automatic change back ............................................73-14 C901670037 Number of SL restoration ..................................................................73-14 C901670038 Number of Local management inhibit ................................................73-14 C901670039 Duration of SL inhibition due to Local management actions...............73-15 C901670040 Number of remote management inhibit..............................................73-15 C901670041 Duration of SL inhibition due to remote management actions ............73-15 C901670042 Number of remote processor outage .................................................73-16 C901670043 Duration of SL inhibition due to remote processor outage..................73-16 C901670044 Number of sending unaccess messages ...........................................73-16 C901670045 Number of sending flow-control discarded messages ........................73-17 C901670046 Ten thousand multiple bandwidth occupancy rate on outgoing signaling link ..........................................................................................................73-17 C901670047 Ten thousand multiple bandwidth occupancy rate on incoming signaling link .........................................................................................................73-18 C901670048 Link type ...........................................................................................73-18 C901670049 Number of TFA sent ..........................................................................73-19 C901670050 Number of TFA received....................................................................73-19 C901670051 Number of TFC sent..........................................................................73-19 C901670052 Number of TFC received ...................................................................73-19 C901670053 Number of RST sent..........................................................................73-19 C901670054 Number of RST received ...................................................................73-20 C901670055 Number of TRA sent..........................................................................73-20 C901670056 Number of TRA received ...................................................................73-20 C901670057 Number of UPU sent .........................................................................73-20 C901670058 Number of UPU received...................................................................73-21 C901670059 Number of message discard controlled by license .............................73-21

73.1 Overview
Message Transfer Part Level 3, MTP3 for short, implements bearer of narrow-band messages and broad-band messages of upper-layer users. The MTP3 link measurement task takes the link as the unit. It performs measurement of messages related to MTP3 link management, the number of data messages received and sent, and the number of bytes of data messages received and sent. Statistic unit in this measurement is link. This chapter introduces the meaning, usage, and measurement point of MTP3 link measurement counters.

73-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 73 MTP3 Signaling Link Statistics

73.2 C901670001 Duration of Signaling Link Out of Service

Description
This counter counts the duration of the signaling link being faulty, blocked, or not activated.

Measurement Point
During a measurement period, the counter counts the duration of MTP3 link not in the service status.

Unit
Second

73.3 C901670002 Number of Signaling Link Out of Service

Description
This counter counts the number of the signaling link exiting the service status.

Measurement Point
The counter accumulates when the link status is changed from available to unavailable.

Unit
Times

73.4 C901670003 Number of Message Signal Unit Sent

Description
This counter counts the number of MSUs sent on the signaling link.

Measurement Point
The counter accumulates when the upper-layer user sends the MSU message through MTP3 or MTP3 forwards the MSU message outwards from the local office.

73-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

73.5 C901670004 Octets of SIF-SIO Sent

Description
This counter counts the number of octets of SIF and SIO sent on the signaling link.

Measurement Point
The counter accumulates when the MSU message is sent on the link (only counting the number of octets of SIF and SIO).

73.6 C901670005 Number of Message Signal Unit Received

Description
This counter counts the number of MSUs received on the signaling link.

Measurement Point
The counter accumulates when the MSU message is received on the link.

73.7 C901670006 Octets of SIF-SIO Received

Description
This counter counts the number of octets of SIF and SIO received on the signaling link.

Measurement Point
The counter accumulates when the MSU message is received on the link (only counting the number of octets of SIF and SIO).

73.8 C901670007 Peak Traffic of Signaling Link

Description
During the measurement period, this counter counts the peak traffic load of the signaling link. Because the M2PA link shares the bandwidth, precise calculation of traffic load is not possible. The peak traffic load is calculated on the basis of a 2 Mbps link: Measurement unit time: 15 seconds 1. Number of bytes of messages sent within the measurement unit time = Number of octets of SIF and SIO sent within the measurement unit time + Number of MSUs sent within the measurement unit time * Length of the message header
73-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 73 MTP3 Signaling Link Statistics

2. Number of bytes of messages received within the measurement unit time = Number of octets of SIF and SIO received within the measurement unit time + Number of MSUs received within the measurement unit time * Length of the message header

Note: For 64 kbps link and broadband link, the message header's length is 6. For 2 Mbps link and N * 64 kbps link, the message header's length is 9.

3. Traffic load within the measurement unit time = 10000 * (Number of bytes of messages sent + Number of bytes of messages received) * 8 / (Link bandwidth * 2 * 15)

Note: Here, 10000 indicates , 8 indicates the number of bits of the message's bytes, 2 indicates the receiving and the sending are on two directions, and 15 indicates the measurement unit time.

4. During the measurement period, the counter compares the traffic load of each measurement unit time, and the maximum traffic load is recorded as the peak traffic load.

Measurement Point
During a measurement period, the counter records the peak traffic load of the link.

Unit

73.9 C901670008 Peak Traffic Duration of Signaling Link

Description
This counter records the duration of the signaling link being in the status of peak traffic load within the measurement period. Like the peak traffic load, the peak traffic duration is not precise, only for reference. At present, if the counter is not cleared, its value will be accumulated. If the buffer size is not unlimited, the counter's value cannot be accumulated when its value reaches 900 seconds. If the counter is cleared, the number of route being unavailable will be cleared
73-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

too. If the route is unavailable, then the following case might exist and is considered normal: the number of link being unavailable is 0 but the duration of link being unavailable is still recorded.

Measurement Point
This counter records the duration of the signaling link being in the status of peak traffic load within the measurement period.

Unit
Second

73.10 C901670009 Number of Change Over on OMP

Description
This counter counts the number of changeovers occurred on the signaling link (on OMP).

Measurement Point
When the MTP3 link exits the service and changeover is initiated on the link, the counter accumulates.

73.11 C901670010 Number of TFP Received

Description
This counter counts the number of transfer-prohibited messages received on the signaling link.

Measurement Point
The counter increments when the TFP message is received on the link.

73.12 C901670011 Ten thousand rate of Mtp3 Link Occupy

Description
This counter counts the ratio () of link bandwidth that the signaling message occupies. Because the M2PA link shares the bandwidth, precise calculation of ratio is not possible. The ratio is calculated on the basis of a 2 Mbps link, and the calculation result is only for reference. 1. Number of bytes of messages sent = Number of octets of SIF and SIO sent + Number of MSUs sent * Length of the message header
73-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 73 MTP3 Signaling Link Statistics

2. Number of bytes of messages received = Number of octets of SIF and SIO received + Number of MSUs received * Length of the message header

Note: For 64 kbps link and broadband link, the message header's length is 6. For 2 Mbps link and N * 64 kbps link, the message header's length is 9.

3. Link occupation ratio () = 10000 * (Number of bytes of messages sent + Number of bytes of messages received) * 8 / (Link bandwidth * 2 * counting time)

Measurement Point
The counter counts when the request of MTP3 link performance statistics is received.

Unit

73.13 C901670012 Number of SCCP Message Signal Unit Received

Description
This counter counts the number of SCCP messages received on the link.

Measurement Point
The counter accumulates when the SCCP message is received on the link. The counter increments when the link status is changed from available to unavailable.

73.14 C901670013 Number of SCCP Message Signal Unit Sent

Description
This counter counts the number of SCCP messages sent on the link.

Measurement Point
The counter accumulates when the SCCP message is sent on the link.

73-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

73.15 C901670014 Number of A2SP Message Signal Unit Received

Description
This counter counts the number of ALCAP messages received on the link. The counter's value is not zero only for the broadband link (ATM), for other link types, its value is always zero.

Measurement Point
The counter accumulates when the ALCAP message is received on the link.

73.16 C901670015 Number of A2SP Message Signal Unit Sent

Description
This counter counts the number of ALCAP messages sent on the link. The counter's value is not zero only for the broadband link (ATM), for other link types, its value is always zero.

Measurement Point
The counter accumulates when the ALCAP message is sent on the link.

73.17 C901670016 Number of Stm Message Signal Unit Received

Description
This counter counts the number of SNM messages received on the link.

Measurement Point
The counter accumulates when the SNM message is received on the link.

73.18 C901670017 Number of Stm Message Signal Unit Sent

Description
This counter counts the number of SNM messages sent on the link.

73-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 73 MTP3 Signaling Link Statistics

Measurement Point
The counter accumulates when the SNM message is sent on the link.

73.19 C901670018 Number of Sltm Message Signal Unit Received

Description
This counter counts the number of STM messages (i.e. link test message) received on the link.

Measurement Point
The counter accumulates when the STM message is received on the link.

73.20 C901670019 Number of Sltm Message Signal Unit Sent

Description
This counter counts the number of STM messages (i.e. link test message) sent on the link.

Measurement Point
The counter accumulates when the STM message is sent on the link.

73.21 C901670020 Octets of SCCP SIF-SIO Received

Description
This counter counts the number of octets of SCCP SIF and SIO received on the link.

Measurement Point
The counter accumulates when the SCCP message is received on the link.

73.22 C901670021 Octets of SCCP SIF-SIO Sent

Description
This counter counts the number of octets of SCCP SIF and SIO sent on the link.

Measurement Point
The counter accumulates when the SCCP message is sent on the link.
73-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

73.23 C901670022 Octets of MTP2 SIF-SIO Received

Description
This counter counts the number of octets of ALCAP SIF and SIO received on the link. The counter's value is not zero only for the broadband link (ATM), for other link types, its value is always zero.

Measurement Point
The counter accumulates when the ALCAP message is received on the link.

73.24 C901670023 Octets of MTP2 SIF-SIO Sent

Description
This counter counts the number of octets of ALCAP SIF and SIO sent on the link. The counter's value is not zero only for the broadband link (ATM), for other link types, its value is always zero.

Measurement Point
The counter accumulates when the ALCAP message is sent on the link.

73.25 C901670024 Octets of Stm SIF-SIO Received

Description
This counter counts the number of octets of SNM SIF and SIO received on the link.

Measurement Point
The counter accumulates when the SNM message is received on the link.

73.26 C901670025 Octets of Stm SIF-SIO Sent

Description
This counter counts the number of octets of SNM SIF and SIO sent on the link.

Measurement Point
The counter accumulates when the SNM message is sent on the link.

73-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 73 MTP3 Signaling Link Statistics

73.27 C901670026 Octets of Sltm SIF-SIO Received

Description
This counter counts the number of octets of SIF and SIO of the link test message (STM) received on the link.

Measurement Point
The counter accumulates when the STM message is received on the link.

73.28 C901670027 Octets of Sltm SIF-SIO Sent

Description
This counter counts the number of octets of SIF and SIO of the link test message (STM) sent on the link.

Measurement Point
The counter accumulates when the STM message is sent on the link.

73.29 C901670028 Number of message discarded due to Congestion

Description
This counter counts the number of messages discarded due to congestion. The counter's value is not zero only for ANSI standard, for other protocol types, its value is always zero. When the function of flow control according to link level is enabled, the message will not be discarded due to congestion.

Measurement Point
When the MSU message is sent on the link, if the congestion level of the link or office is higher than the message's priority, the message is discarded and the counter accumulates.

73.30 C901670029 Number of restrictions Level 1

Description
This counter counts the number of the link being at the congestion level 1. The counter's value is not zero only for ANSI standard, for other protocol types, its value is always zero.

73-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter accumulates when the link congestion is at level 1.

73.31 C901670030 Number of restrictions Level 2

Description
This counter counts the number of the link being at the congestion level 2. The counter's value is not zero only for ANSI standard, for other protocol types, its value is always zero.

Measurement Point
The counter accumulates when the link congestion is at level 2.

73.32 C901670031 Number of restrictions Level 3

Description
This counter counts the number of the link being at the congestion level 3. The counter's value is not zero only for ANSI standard, for other protocol types, its value is always zero.

Measurement Point
The counter accumulates when the link congestion is at level 3.

73.33 C901670032 Duration of Restrictions Level 1

Description
This counter counts the duration of the link being at the congestion level 1. The counter's value is not zero only for ANSI standard, for other protocol types, its value is always zero.

Measurement Point
The counter records the duration of the link being at the congestion level 1 during a measurement period.

Unit
Second

73-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 73 MTP3 Signaling Link Statistics

73.34 C901670033 Duration of Restrictions Level 2

Description
This counter counts the duration of the link being at the congestion level 2. The counter's value is not zero only for ANSI standard, for other protocol types, its value is always zero.

Measurement Point
The counter records the duration of the link being at the congestion level 2 during a measurement period.

Unit
Second

73.35 C901670034 Duration of Restrictions Level 3

Description
This counter counts the duration of the link being at the congestion level 3. The counter's value is not zero only for ANSI standard, for other protocol types, its value is always zero.

Measurement Point
The counter records the duration of the link being at the congestion level 3 during a measurement period.

Unit
Second

73.36 C901670035 Duration of manual prohibition

Description
This counter counts the duration of the link being in the manual deactivation status.

Measurement Point
The counter records the duration of the link being in the manual deactivation status during a measurement period.

Unit
Second

73-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

73.37 C901670036 Number of local automatic change back

Description
This counter counts the number of changebacks occurred on the signaling link (on OMP).

Measurement Point
When the MTP3 link is put into service and changeback is initiated on the link, the counter accumulates.

Unit
Times

73.38 C901670037 Number of SL restoration

Description
This counter counts the number of signaling link being restored to be available.

Measurement Point
The counter accumulates when the link status is changed from unavailable to available.

Unit
Times

73.39 C901670038 Number of Local management inhibit

Description
This counter counts the number of local inhibitions successfully initiated by management entity (on OMP).

Measurement Point
When the management entity initiates local inhibition successfully, the counter accumulates.

Unit
Times
73-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 73 MTP3 Signaling Link Statistics

73.40 C901670039 Duration of SL inhibition due to Local management actions

Description
This counter counts the duration from local inhibition being initiated successfully and local uninhibition being initiated successfully (on OMP).

Measurement Point
When the local inhibition is initiated successfully, the counter starts counting. When the local uninhibition succeeds, the counter stops counting and records the duration.

Unit
Second

73.41 C901670040 Number of remote management inhibit

Description
This counter counts the number of remote inhibitions successfully initiated by management entity (on OMP).

Measurement Point
When the management entity initiates remote inhibition successfully, the counter accumulates.

Unit
Times

73.42 C901670041 Duration of SL inhibition due to remote management actions

Description
This counter counts the duration from remote inhibition being initiated successfully and remote uninhibition being initiated successfully (on OMP).

Measurement Point
When the remote inhibition is initiated successfully, the counter starts counting. When the remote uninhibition succeeds, the counter stops counting and records the duration.
73-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Second

73.43 C901670042 Number of remote processor outage

Description
This counter counts the number of the remote processor being faulty.

Measurement Point
This counter accumulates when the remote processor is faulty.

Unit
Times

73.44 C901670043 Duration of SL inhibition due to remote processor outage

Description
This counter counts the duration of the remote processor being faulty.

Measurement Point
This counter counts when the remote processor is faulty.

Unit
Second

73.45 C901670044 Number of sending unaccess messages

Description
This counter counts the number of transfer-prohibited messages (TFP) on the link.

Measurement Point
The counter accumulates when the TFP message is sent on the link.

Unit
Times
73-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 73 MTP3 Signaling Link Statistics

73.46 C901670045 Number of sending flow-control discarded messages

Description
This counter counts the number of flow-control discarded messages sent on the link.

Measurement Point
The counter accumulates when the flow-control discarded messages is sent on the link.

73.47 C901670046 Ten thousand multiple bandwidth occupancy rate on outgoing signaling link
Description
This counter counts the ratio () of bandwidth occupied by the outgoing link. Outgoing link occupation ratio () = 10000 * Number of bytes of messages sent * 8 / (Link bandwidth * Measurement time)

Note: Here, 10000 indicates , multiplication of 8 indicates conversion from byte to bit, the link bandwidth unit is bit/s, and the measurement time unit is s.

Number of bytes of messages sent = Number of octets of SIF and SIO sent + Number of MSUs sent * Length of the message header

Note: For 64 kbps link and broadband link, the message header's length is 6. For 2 Mbps link and N * 64 kbps link, the message header's length is 9.

The link bandwidth is described as follows: l For 64 kbps link, N * 64 kbps link, and 2 Mbps link database configuration, the bandwidth means the number of timeslots. In other words, if the configured bandwidth is n, the bandwidth is n * 64000 bps. For broadband link, the bandwidth unit is kbps. In other words, if the bandwidth obtained from the database is n, the bandwidth is n * 1000 bps.
73-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when the request of MTP3 link performance statistics is received.

73.48 C901670047 Ten thousand multiple bandwidth occupancy rate on incoming signaling link
Description
This counter counts the ratio () of bandwidth occupied by the incoming link. Incoming link occupation ratio () = 10000 * Number of bytes of messages received * 8 / (Link bandwidth * Measurement time) Number of bytes of messages received = Number of octets of SIF and SIO received + Number of MSUs received * Length of the message header

Note: For 64 kbps link and broadband link, the message header's length is 6. For 2 Mbps link and N * 64 kbps link, the message header's length is 9.

Measurement Point
The counter counts when the request of MTP3 link performance statistics is received.

73.49 C901670048 Link type

Description
This counter records the link type. l l l l l If the link or link group is 64 kbps, the corresponding value is 1, represented as Narrow 64K Signaling. If the link or link group is n * 64 kbps, the corresponding value is 2, represented as Narrow N*64K Signaling. If the link or link group is 2 Mbps, the corresponding value is 3, represented as Narrow 2M Signaling. If the link or link group is broadband, the corresponding value is 4, represented as ATM Signaling - SSCS. If the link or link group is M2PA, the corresponding value is 5, represented as M2PA Signaling.

73-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 73 MTP3 Signaling Link Statistics

73.50 C901670049 Number of TFA sent

Description
This counter counts the number of TFA messages sent on the link.

Measurement Point
The counter accumulates when the TFA message is sent on the link.

73.51 C901670050 Number of TFA received

Description
This counter counts the number of TFA messages received on the link.

Measurement Point
The counter accumulates when the TFA message is received on the link.

73.52 C901670051 Number of TFC sent

Description
This counter counts the number of TFC messages sent on the link.

Measurement Point
The counter accumulates when the TFC message is sent on the link.

73.53 C901670052 Number of TFC received

Description
This counter counts the number of TFC messages received on the link.

Measurement Point
The counter accumulates when the TFC message is received on the link.

73.54 C901670053 Number of RST sent

Description
This counter counts the number of RST messages (i.e. route-set test message) sent on the link.
73-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter accumulates when the RST message is sent on the link.

73.55 C901670054 Number of RST received

Description
This counter counts the number of RST messages (i.e. route-set test message) received on the link.

Measurement Point
The counter accumulates when the RST message is received on the link.

73.56 C901670055 Number of TRA sent

Description
This counter counts the number of service-restart-allowed messages (TRA) sent on the link.

Measurement Point
The counter accumulates when the TRA message is sent on the link.

73.57 C901670056 Number of TRA received

Description
This counter counts the number of service-restart-allowed messages (TRA) received on the link.

Measurement Point
The counter accumulates when the TRA message is received on the link.

73.58 C901670057 Number of UPU sent

Description
This counter counts the number of user-part-unavailable messages (UPU) sent on the link.

Measurement Point
The counter accumulates when the UPU message is sent on the link.
73-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 73 MTP3 Signaling Link Statistics

73.59 C901670058 Number of UPU received

Description
This counter counts the number of user-part-unavailable messages (UPU) received on the link.

Measurement Point
The counter accumulates when the UPU message is received on the link.

73.60 C901670059 Number of message discard controlled by license

Description
When the number of forwarding message exceeds the maximum forwarding times allowed in Licence, the overload control function decides whether the subsequent messages will be discarded. If a message should be discarded, then the message will not be forwarded outwards from the local office and is directly discarded, and the counter accumulates.

Measurement Point
When the number of forwarding message exceeds the maximum forwarding times allowed in Licence, call the overload control function to decide whether the subsequent messages will be discarded.

73-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

73-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 74

M3UA Performance Statistics

Table of Contents
Overview ..................................................................................................................74-2 C901680001 Number of data message sent.............................................................74-2 C901680002 Number of data message received ......................................................74-2 C901680003 Number of ASP Up message sent .......................................................74-3 C901680004 Number of ASP Up message received ................................................74-3 C901680005 Number of ASP Up Ack message received..........................................74-3 C901680006 Number of ASP Up Ack message sent ................................................74-4 C901680007 Number of ASP Down message sent ..................................................74-4 C901680008 Number of ASP Down message received ............................................74-4 C901680009 Number of ASP Down Ack message received .....................................74-5 C901680010 Number of ASP Down Ack message sent............................................74-5 C901680011 Number of ASP Inactive message sent................................................74-5 C901680012 Number of ASP Inactive message received.........................................74-6 C901680013 Number of ASP Inactive Ack message received ..................................74-6 C901680014 Number of ASP Inactive Ack message sent.........................................74-6 C901680015 Number of ASP Active message sent ..................................................74-7 C901680016 Number of ASP Active message received ...........................................74-7 C901680017 Number of ASP Active Ack message received ....................................74-7 C901680018 Number of ASP Active Ack message sent ...........................................74-8 C901680019 Number of DAUD message sent .........................................................74-8 C901680020 Number of SCON message received...................................................74-8 C901680021 Number of DAVA message received....................................................74-9 C901680022 Number of DUNA message received ...................................................74-9 C901680023 Number of invalid message received ...................................................74-9 C901680024 Number of MGMT message sent.........................................................74-9 C901680025 Number of MGMT message received ................................................74-10 C901680026 Number of Heartbeat message received ...........................................74-10 C901680027 Number of HeartBeat Ack message sent ...........................................74-10 C901680028 Bytes of data message received........................................................ 74-11 C901680029 Bytes of data message transmitted.................................................... 74-11 C901680030 Bytes of MGMT message sent .......................................................... 74-11 C901680031 Bytes of MGMT message received.................................................... 74-11 C901680032 Counts of discarding messages by Flow Control ...............................74-12 C901680033 Number of message discard controlled by license .............................74-12 C901680034 Bytes of all message sent..................................................................74-12 C901680035 Bytes of all message received ...........................................................74-13 C901680036 Number of ERROR message sent.....................................................74-13
74-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901680037 Number of ERROR message received ..............................................74-13 C901680038 Number of NOTIFY message sent.....................................................74-14 C901680039 Number of NOTIFY message received ..............................................74-14

74.1 Overview
M3UA is short for MTP3-User Adaptation Layer. M3UA measurement performs measurement of messages related to M3UA link management, the number of data messages received and sent, and the number of bytes of data messages received and sent. Statistic unit in this measurement is SCTP. l l l It supports IP bearer of messages of some SS7 MTP3 users. It supports seamless operations of peer-layer MTP3 user protocols. It supports MTP3 nework management functions.

This chapter introduces the meaning, usage, and measurement point of M3UA performance measurement counters.

74.2 C901680001 Number of data message sent

Description
This counter counts the number of data messages sent.

Measurement Point
The counter accumulates when the data message is sent.

Unit
Times

74.3 C901680002 Number of data message received

Description
This counter counts the number of data messages received.

Measurement Point
The counter accumulates when the data message is received.

Unit
Times

74-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 74 M3UA Performance Statistics

74.4 C901680003 Number of ASP Up message sent

Description
This counter counts the number of ASP Up messages sent.

Measurement Point
The counter accumulates when the ASP Up message is sent.

Unit
Times

74.5 C901680004 Number of ASP Up message received

Description
This counter counts the number of ASP Up messages received.

Measurement Point
The counter accumulates when the ASP Up message is received.

Unit
Times

74.6 C901680005 Number of ASP Up Ack message received

Description
This counter counts the number of ASP Up Ack messages received.

Measurement Point
The counter accumulates when the ASP Up Ack message is received.

Unit
Times

74-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

74.7 C901680006 Number of ASP Up Ack message sent

Description
This counter counts the number of ASP Up Ack messages sent.

Measurement Point
The counter accumulates when the ASP Up Ack message is sent.

Unit
Times

74.8 C901680007 Number of ASP Down message sent

Description
This counter counts the number of ASP Down messages sent.

Measurement Point
The counter accumulates when the ASP Down message is sent.

Unit
Times

74.9 C901680008 Number of ASP Down message received

Description
This counter counts the number of ASP Down messages received.

Measurement Point
The counter accumulates when the ASP Down message is received.

Unit
Times

74-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 74 M3UA Performance Statistics

74.10 C901680009 Number of ASP Down Ack message received

Description
This counter counts the number of ASP Down Ack messages received.

Measurement Point
The counter accumulates when the ASP Down Ack message is received.

Unit
Times

74.11 C901680010 Number of ASP Down Ack message sent

Description
This counter counts the number of ASP Down Ack messages sent.

Measurement Point
The counter accumulates when the ASP Down Ack message is sent.

Unit
Times

74.12 C901680011 Number of ASP Inactive message sent

Description
This counter counts the number of ASP Inactive messages sent.

Measurement Point
The counter accumulates when the ASP Inactive message is sent.

Unit
Times

74-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

74.13 C901680012 Number of ASP Inactive message received

Description
This counter counts the number of ASP Inactive messages received.

Measurement Point
The counter accumulates when the ASP Inactive message is received.

Unit
Times

74.14 C901680013 Number of ASP Inactive Ack message received

Description
This counter counts the number of ASP Inactive Ack messages received.

Measurement Point
The counter accumulates when the ASP Inactive Ack message is received.

Unit
Times

74.15 C901680014 Number of ASP Inactive Ack message sent

Description
This counter counts the number of ASP Inactive Ack messages sent.

Measurement Point
The counter accumulates when the ASP Inactive Ack message is sent.

Unit
Times

74-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 74 M3UA Performance Statistics

74.16 C901680015 Number of ASP Active message sent

Description
This counter counts the number of ASP Active messages sent.

Measurement Point
The counter accumulates when the ASP Active message is sent.

Unit
Times

74.17 C901680016 Number of ASP Active message received

Description
This counter counts the number of ASP Active messages received.

Measurement Point
The counter accumulates when the ASP Active message is received.

Unit
Times

74.18 C901680017 Number of ASP Active Ack message received

Description
This counter counts the number of ASP Active Ack messages received.

Measurement Point
The counter accumulates when the ASP Active Ack message is received.

Unit
Times

74-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

74.19 C901680018 Number of ASP Active Ack message sent

Description
This counter counts the number of ASP Active Ack messages sent.

Measurement Point
The counter accumulates when the ASP Active Ack message is sent.

Unit
Times

74.20 C901680019 Number of DAUD message sent

Description
This counter counts the number of DAUD messages sent.

Measurement Point
The counter accumulates when the DAUD message is sent.

Unit
Times

74.21 C901680020 Number of SCON message received

Description
This counter counts the number of SCON messages received.

Measurement Point
The counter accumulates when the SCON message is received.

Unit
Times

74-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 74 M3UA Performance Statistics

74.22 C901680021 Number of DAVA message received

Description
This counter counts the number of DAVA messages received.

Measurement Point
The counter accumulates when the DAVA message is received.

Unit
Times

74.23 C901680022 Number of DUNA message received

Description
This counter counts the number of DUNA messages received.

Measurement Point
The counter accumulates when the DUNA message is received.

Unit
Times

74.24 C901680023 Number of invalid message received

Description
This counter counts the number of invalid data message received.

Measurement Point
The counter counts when the key information carried in the message is incorrect.

Unit
Times

74.25 C901680024 Number of MGMT message sent

Description
This counter counts the number of MGMT messages sent.
74-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter accumulates when the MGMT message is sent.

74.26 C901680025 Number of MGMT message received

Description
This counter counts the number of MGMT messages received.

Measurement Point
The counter accumulates when the MGMT message is received.

74.27 C901680026 Number of Heartbeat message received

Description
This counter counts the number of HeartBeat messages received.

Measurement Point
The counter accumulates when the HeartBeat message is received.

Unit
Times

74.28 C901680027 Number of HeartBeat Ack message sent

Description
This counter counts the number of HeartBeatAck messages sent.

Measurement Point
The counter accumulates when the HeartBeatAck message is sent.

Unit
Times

74-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 74 M3UA Performance Statistics

74.29 C901680028 Bytes of data message received

Description
This counter counts the number of bytes of DATA messages received by M3UA.

Measurement Point
The counter counts when M3UA receives the DATA message.

Unit
Byte

74.30 C901680029 Bytes of data message transmitted

Description
This counter counts the number of bytes of DATA messages sent by M3UA.

Measurement Point
The counter counts when M3UA sends the DATA message.

Unit
Byte

74.31 C901680030 Bytes of MGMT message sent

Description
This counter counts the number of bytes of MGMT messages sent.

Measurement Point
The counter counts when the NTFY message or the ERR message is sent.

Unit
Byte

74.32 C901680031 Bytes of MGMT message received

Description
This counter counts the number of bytes of management messages received.
74-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when the NTFY message or the ERR message is received.

Unit
Byte

74.33 C901680032 Counts of discarding messages by Flow Control

Description
When a message is discarded due to flow control, the counter's value increments. The measurement is performed according to SCTP.

Measurement Point
The counter counts when a message is discarded due to flow control.

74.34 C901680033 Number of message discard controlled by license

Description
When the number of forwarding message exceeds the maximum forwarding times allowed in Licence, the overload control function decides whether the subsequent messages will be discarded. If a message should be discarded, then the message will not be forwarded outwards from the local office and is directly discarded. The condition is reported to OAM and the counter accumulates.

Measurement Point
When the number of forwarding message exceeds the maximum forwarding times allowed in Licence, call the overload control function to decide whether the subsequent messages will be discarded.

74.35 C901680034 Bytes of all message sent

Description
This counter counts the bytes of all messages sent on SCTP, including data message, management message, ASPSM message, ASPTM message, and MGMT message.

74-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 74 M3UA Performance Statistics

Unit
Byte

74.36 C901680035 Bytes of all message received

Description
This counter counts the bytes of all messages received on SCTP, including data message, management message, ASPSM message, ASPTM message, and MGMT message.

Unit
Byte

74.37 C901680036 Number of ERROR message sent

Description
This counter counts the number of ERROR messages sent.

Measurement Point
The counter accumulates when the ERROR message is sent.

Unit
Times

74.38 C901680037 Number of ERROR message received

Description
This counter counts the number of ERROR messages received.

Measurement Point
The counter accumulates when the ERROR message is received.

Unit
Times

74-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

74.39 C901680038 Number of NOTIFY message sent

Description
This counter counts the number of NOTIFY messages sent.

Measurement Point
The counter accumulates when the NOTIFY message is sent.

Unit
Times

74.40 C901680039 Number of NOTIFY message received

Description
This counter counts the number of NOTIFY messages received.

Measurement Point
The counter accumulates when the NOTIFY message is received.

Unit
Times

74-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 75

SCCP Performance Statistics

Table of Contents
Overview ..................................................................................................................75-2 C901690001 Number of UDT Sent...........................................................................75-2 C901690002 Number of UDT Received ...................................................................75-3 C901690003 Number of UDTS Sent ........................................................................75-3 C901690004 Number of UDTS Received .................................................................75-3 C901690005 Number of ERR Sent...........................................................................75-4 C901690006 Number of ERR Received ...................................................................75-4 C901690007 Number of SSP Sent ...........................................................................75-4 C901690008 Number of SSP Received....................................................................75-4 C901690009 Number of RSR Sent...........................................................................75-4 C901690010 Number of RSR Received ...................................................................75-5 C901690011 Number of RSC Sent ...........................................................................75-5 C901690012 Number of RSC Received ...................................................................75-5 C901690013 Number of UnAnswered SST ..............................................................75-5 C901690014 Number of CREF Sent ........................................................................75-6 C901690015 Number of CREF Received .................................................................75-6 C901690016 Number of XUDT Sent ........................................................................75-6 C901690017 Number of XUDT Received .................................................................75-6 C901690018 Number of XUDTS Sent ......................................................................75-6 C901690019 Number of XUDTS Received...............................................................75-7 C901690020 Number of LUDT Sent .........................................................................75-7 C901690021 Number of LUDT Received .................................................................75-7 C901690022 Number of LUDTS Sent.......................................................................75-7 C901690023 Number of LUDTS Received ...............................................................75-8 C901690024 Number of DT1 Received ....................................................................75-8 C901690025 Number of DT1 Sent ...........................................................................75-8 C901690026 Number of DT2 Received ....................................................................75-8 C901690027 Number of DT2 Sent ...........................................................................75-8 C901690028 Number of CONNECTREQ Sent .........................................................75-9 C901690029 Number of CONNECTCON Received..................................................75-9 C901690030 Number of CONNECTIND Received ...................................................75-9 C901690031 Number of CONNECTRES Sent..........................................................75-9 C901690032 Number of DISCONNECTREQ Sent .................................................75-10 C901690033 Number of DISCONNECTIND received.............................................75-10 C901690034 Number of CR Sent ...........................................................................75-10 C901690035 Number of CR Received....................................................................75-10 C901690036 Number of CC Sent ...........................................................................75-10
75-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901690037 Number of CC Received.................................................................... 75-11 C901690038 Number of UDT gtt ............................................................................ 75-11 C901690039 Number of UDTS gtt.......................................................................... 75-11 C901690040 Number of XUDT gtt.......................................................................... 75-11 C901690041 Number of XUDTS gtt .......................................................................75-12 C901690042 Number of LUDT gtt ..........................................................................75-12 C901690043 Number of LUDTS gtt........................................................................75-12 C901690044 Number of UDT gtt failure..................................................................75-12 C901690045 Number of UDTS gtt failure ...............................................................75-13 C901690046 Number of XUDT gtt failure ...............................................................75-13 C901690047 Number of XUDTS gtt failure .............................................................75-13 C901690048 Number of LUDT gtt failure................................................................75-13 C901690049 Number of LUDTS gtt failure .............................................................75-14 C901690050 Number of CR gtt ..............................................................................75-14 C901690051 Number of CR gtt failure....................................................................75-14 C901690052 Number of gtt Count ..........................................................................75-15 C901690053 Number of gtt failure..........................................................................75-15 C901690054 Number of N_UnitDataReq LongUserData gtt failure.........................75-15 C901690055 Number of UPU received...................................................................75-15 C901690056 Number of SSA received ...................................................................75-16 C901690057 Number of SSA sent..........................................................................75-16 C901690058 Number of SST received ...................................................................75-16 C901690059 Number of SST sent..........................................................................75-16

75.1 Overview
SCCP is short for Signalling Connection Control Part. It works with MTP3 to implement the network-layer function of Signaling System No.7 (SS7 ), providing data transmission service which is either connectionless or connection-oriented. SCCP performance measurement takes module as the measurement unit. It measures the following information related to connectionless service or connection-oriented service: the number of received or sent data messages, the number of GT translations, and the number of GT translation failures. This chapter introduces the meaning, usage, and measurement point of SCCP performance measurement counters.

75.2 C901690001 Number of UDT Sent

Description
This counter counts the number of UDTs sent by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP sends UDT.
75-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 75 SCCP Performance Statistics

Unit
Times

75.3 C901690002 Number of UDT Received

Description
This counter counts the number of UDTs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives UDT.

Unit
Times

75.4 C901690003 Number of UDTS Sent

Description
This counter counts the number of UDTSs sent by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP sends UDTS.

Unit
Times

75.5 C901690004 Number of UDTS Received

Description
This counter counts the number of UDTSs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives UDTS.

Unit
Times

75-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

75.6 C901690005 Number of ERR Sent

Description
This counter counts the number of ERRs sent by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP sends ERR.

75.7 C901690006 Number of ERR Received

Description
This counter counts the number of ERRs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives ERR.

75.8 C901690007 Number of SSP Sent

Description
This counter counts the number of SSPs sent by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP sends SSP.

75.9 C901690008 Number of SSP Received

Description
This counter counts the number of SSPs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives SSP.

75.10 C901690009 Number of RSR Sent

Description
This counter counts the number of RSRs sent by SCCP of the local office.

75-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 75 SCCP Performance Statistics

Measurement Point
The counter accumulates when SCCP sends RSR.

75.11 C901690010 Number of RSR Received

Description
This counter counts the number of RSRs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives RSR.

75.12 C901690011 Number of RSC Sent

Description
This counter counts the number of RSCs sent by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP sends RSC.

75.13 C901690012 Number of RSC Received

Description
This counter counts the number of RSCs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives RSC.

75.14 C901690013 Number of UnAnswered SST

Description
This counter counts the number of SSTs that does not receive the response. The SST is sent by SCCP of the local office.

Measurement Point
The counter accumulates when the SST sent by SCCP does not receive the response.

75-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

75.15 C901690014 Number of CREF Sent

Description
This counter counts the number of CREFs sent by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP sends CREF.

75.16 C901690015 Number of CREF Received

Description
This counter counts the number of CREFs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives CREF.

75.17 C901690016 Number of XUDT Sent

Description
This counter counts the number of XUDTs sent by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP sends XUDT.

75.18 C901690017 Number of XUDT Received

Description
This counter counts the number of XUDTs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives XUDT.

75.19 C901690018 Number of XUDTS Sent

Description
This counter counts the number of XUDTSs sent by SCCP of the local office.

75-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 75 SCCP Performance Statistics

Measurement Point
The counter accumulates when SCCP sends XUDTS.

75.20 C901690019 Number of XUDTS Received

Description
This counter counts the number of XUDTSs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives XUDTS.

75.21 C901690020 Number of LUDT Sent

Description
This counter counts the number of LUDTs sent by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP sends LUDT.

75.22 C901690021 Number of LUDT Received

Description
This counter counts the number of LUDTs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives LUDT.

75.23 C901690022 Number of LUDTS Sent

Description
This counter counts the number of LUDTSs sent by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP sends LUDTS.

75-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

75.24 C901690023 Number of LUDTS Received

Description
This counter counts the number of LUDTSs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives LUDTS.

75.25 C901690024 Number of DT1 Received

Description
This counter counts the number of DT1s received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives DT1.

75.26 C901690025 Number of DT1 Sent

Description
This counter counts the number of DT1s sent by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP sends DT1.

75.27 C901690026 Number of DT2 Received

Description
This counter counts the number of DT2s received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives DT2.

75.28 C901690027 Number of DT2 Sent

Description
This counter counts the number of DT2s sent by SCCP of the local office.

75-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 75 SCCP Performance Statistics

Measurement Point
The counter accumulates when SCCP sends DT2.

75.29 C901690028 Number of CONNECTREQ Sent

Description
This counter counts the number of sending CONNECTREQ to SCCP.

Measurement Point
The counter accumulates when SCCP receives CONNECTREQ.

75.30 C901690029 Number of CONNECTCON Received

Description
This counter counts the number of sending CONNECTCON to SCCP.

Measurement Point
This counter accumulates when SCCP receives CONNECTCON.

75.31 C901690030 Number of CONNECTIND Received

Description
This counter counts the number of sending CONNECTRES to SCCP.

Measurement Point
The counter accumulates when SCCP receives CONNECTRES.

75.32 C901690031 Number of CONNECTRES Sent

Description
This counter counts the number of sending CONNECTRES to SCCP.

Measurement Point
The counter accumulates when SCCP receives CONNECTRES.

75-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

75.33 C901690032 Number of DISCONNECTREQ Sent

Description
This counter counts the number of sending DISCONNECTREQ to SCCP.

Measurement Point
The counter accumulates when SCCP receives DISCONNECTREQ.

75.34 C901690033 Number of DISCONNECTIND received

Description
This counter counts the number of DISCONNECTINDs received from SCCP.

Measurement Point
This counter accumulates when DISCONNECTIND is received from SCCP.

75.35 C901690034 Number of CR Sent

Description
This counter counts the number of CRs sent by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP sends CR.

75.36 C901690035 Number of CR Received

Description
This counter counts the number of CRs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives CR.

75.37 C901690036 Number of CC Sent

Description
This counter counts the number of CCs sent by SCCP of the local office.
75-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 75 SCCP Performance Statistics

Measurement Point
The counter accumulates when SCCP sends CC.

75.38 C901690037 Number of CC Received

Description
This counter counts the number of CCs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives CC.

75.39 C901690038 Number of UDT gtt

Description
This counter counts the number of UDT GT translations.

Measurement Point
The counter when uplink/downlink UDT GT translation is performed.

75.40 C901690039 Number of UDTS gtt

Description
This counter counts the number of UDTS GT translations.

Measurement Point
The counter when uplink/downlink UDTS GT translation is performed.

75.41 C901690040 Number of XUDT gtt

Description
This counter counts the number of XUDT GT translations.

Measurement Point
The counter when uplink/downlink XUDT GT translation is performed.

75-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

75.42 C901690041 Number of XUDTS gtt

Description
This counter counts the number of XUDTS GT translations.

Measurement Point
The counter when uplink/downlink XUDTS GT translation is performed.

75.43 C901690042 Number of LUDT gtt

Description
This counter counts the number of LUDT GT translations.

Measurement Point
The counter when uplink/downlink LUDT GT translation is performed.

75.44 C901690043 Number of LUDTS gtt

Description
This counter counts the number of LUDTS GT translations.

Measurement Point
The counter when uplink/downlink LUDTS GT translation is performed.

75.45 C901690044 Number of UDT gtt failure

Description
This counter counts the number of UDT GT translation failures.

Measurement Point
The counter counts when uplink/downlink UDT GT translation fails.

Unit
Times

75-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 75 SCCP Performance Statistics

75.46 C901690045 Number of UDTS gtt failure

Description
This counter counts the number of UDTS GT translation failures.

Measurement Point
The counter counts when uplink/downlink UDTS GT translation fails.

Unit
Times

75.47 C901690046 Number of XUDT gtt failure

Description
This counter counts the number of XUDT GT translation failures.

Measurement Point
The counter counts when uplink/downlink XUDT GT translation fails.

75.48 C901690047 Number of XUDTS gtt failure

Description
This counter counts the number of XUDTS GT translation failures.

Measurement Point
The counter counts when uplink/downlink XUDTS GT translation fails.

Unit
Times

75.49 C901690048 Number of LUDT gtt failure

Description
This counter counts the number of LUDT GT translation failures.

Measurement Point
The counter counts when uplink/downlink LUDT GT translation fails.
75-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

75.50 C901690049 Number of LUDTS gtt failure

Description
This counter counts the number of LUDTS GT translation failures.

Measurement Point
The counter counts when uplink/downlink LUDTS GT translation fails.

Unit
Times

75.51 C901690050 Number of CR gtt

Description
This counter counts the number of CR GT translations.

Measurement Point
The counter when uplink/downlink CR GT translation is performed.

Unit
Times

75.52 C901690051 Number of CR gtt failure

Description
This counter counts the number of CR GT translation failures.

Measurement Point
The counter counts when uplink/downlink CR GT translation fails.

Unit
Times

75-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 75 SCCP Performance Statistics

75.53 C901690052 Number of gtt Count

Description
This counter counts the number of GT translations.

Measurement Point
The counter counts when GT translation is performed.

75.54 C901690053 Number of gtt failure

Description
This counter counts the number of GT translation failures.

Measurement Point
The counter counts when GT translation fails.

Unit
Times

75.55 C901690054 Number of N_UnitDataReq LongUserData gtt failure

Description
This counter counts the number of failures of GT translation of downlink N_UnitDataReq long user message.

Measurement Point
The counter counts when the GT translation of downlink N_UnitDataReq long user message fails.

Unit
Times

75.56 C901690055 Number of UPU received

Description
This counter counts the number of UPUs received by SCCP of the local office.
75-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter accumulates when SCCP receives UPU.

75.57 C901690056 Number of SSA received

Description
This counter counts the number of SSAs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives SSA.

75.58 C901690057 Number of SSA sent

Description
This counter counts the number of SSAs sent by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP sends SSA.

75.59 C901690058 Number of SST received

Description
This counter counts the number of SSTs received by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP receives SST.

75.60 C901690059 Number of SST sent

Description
This counter counts the number of SSTs sent by SCCP of the local office.

Measurement Point
The counter accumulates when SCCP sends SST.

75-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 76

MTP3 Signaling Link Set Statistics

Table of Contents
Overview ..................................................................................................................76-1 C901700001 Times of Signaling Link Set Out of Service ..........................................76-1 C901700002 Duration of Signaling Link Set Out of Service ......................................76-2 C901700003 Number of Available Signaling Link .....................................................76-2 C901700004 Linkset type.........................................................................................76-2

76.1 Overview
Message Transfer Part Level 3, MTP3 for short, implements bearer of narrow-band messages and broad-band messages of upper-layer users. This meaurement takes link set as the unit. It performs measurement of the following information: duration of link set being unavailable, number of link sets being unavailable, and number of links available. A signaling link set is available so long as it has one link available. If all links in a signaling link set are unavailable, the signaling link set is unavailable. This chapter introduces the meaning, usage, and measurement point of MTP3 signaling link set statistic measurement.

76.2 C901700001 Times of Signaling Link Set Out of Service

Description
This counter counts the number of all links being available in the signaling link set.

Measurement Point
When the signaling link set's status changes from at least one link being available to all links being unavailable, the counter increments.

Unit
Times

76-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

76.3 C901700002 Duration of Signaling Link Set Out of Service

Description
This counter counts the duration of all links being available in the signaling link set.

Measurement Point
During a measurement period, the counter starts counting when all links in the signaling link set become unavailable and stops counting once the signaling link set has a link available.

Unit
Second

76.4 C901700003 Number of Available Signaling Link

Description
This counter counts the number of available signaling links in the signaling link set, including the signaling link currently being used.

Measurement Point
This counter counts the number of available signaling links in the signaling link set, including the signaling link currently being used.

76.5 C901700004 Linkset type

Description
There are five link set types: l l l l l 64 kbps signaling link set n * 64 kbps signaling link set 2 Mbps signaling link set Broadband signaling link set M2PA signaling link set

76-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 77

M3UA Error Statistics

Table of Contents
Overview ..................................................................................................................77-2 C901710001 Invalid Version(T) ................................................................................77-2 C901710002 Unsupported Message Class(T) ..........................................................77-2 C901710003 Unsupported Message Type(T) ...........................................................77-3 C901710004 Unexpected Message(T) .....................................................................77-3 C901710005 Unsupported Traffic Mode Type(T) ......................................................77-3 C901710006 Invalid Routing Context(T)...................................................................77-3 C901710007 Protocol Error(T) .................................................................................77-4 C901710008 Invalid Message Type(T) .....................................................................77-4 C901710009 Number of error message sent ............................................................77-4 C901710010 Invalid Version(R) ................................................................................77-4 C901710011 Unsupported Message Class(R) ..........................................................77-5 C901710012 Unsupported Message Type(R) ...........................................................77-5 C901710013 Unexpected Message(R).....................................................................77-5 C901710014 Unsupported Traffic Mode Type(R)......................................................77-5 C901710015 Invalid Routing Context(R) ..................................................................77-6 C901710016 Protocol Error(R) .................................................................................77-6 C901710017 Invalid Message Type(R).....................................................................77-6 C901710018 Number of error message received .....................................................77-6 C901710019 Unknown Remote User .......................................................................77-7 C901710020 Unequipped Remote User ...................................................................77-7 C901710021 Inaccessible Remote User...................................................................77-7 C901710022 Number of DUPU message received ...................................................77-8 C901710023 Invalid Net APPEARANCE(T)..............................................................77-8 C901710024 Invalid Net APPEARANCE(R) .............................................................77-8 C901710025 Number of DUPU message sent which cause is unknown...................77-8 C901710026 Number of DUPU message sent which cause is Unequipped Remote User .........................................................................................................................77-9 C901710027 Number of DUPU message sent which cause is Inaccessible Remote User .........................................................................................................................77-9 C901710028 Number of DUPU message sent .........................................................77-9 C901710029 Number of message discard controlled by license .............................77-10 C901710030 Sending invalid stream ID..................................................................77-10 C901710031 Sending refuse error, reason is management blocking ......................77-10 C901710032 Sending required ASP ID .................................................................. 77-11 C901710033 Sending invalid ASP ID ..................................................................... 77-11 C901710034 Sending invalid parameter value ....................................................... 77-11
77-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901710035 Sending parameter field error ............................................................ 77-11 C901710036 Sending unexpected parameter error ................................................77-12 C901710037 Sending destination status unknown .................................................77-12 C901710038 Sending missing parameter error.......................................................77-12 C901710039 Sending no configured AS for ASP....................................................77-13 C901710040 Receiving invalid stream ID ...............................................................77-13 C901710041 Receiving refuse error, reason is management blocking ....................77-13 C901710042 Receiving required ASP ID ................................................................77-13 C901710043 Receiving invalid ASP ID...................................................................77-14 C901710044 Receiving invalid parameter value .....................................................77-14 C901710045 Receiving parameter field error .........................................................77-14 C901710046 Receiving unexpected parameter error..............................................77-15 C901710047 Receiving destination status unknown ...............................................77-15 C901710048 Receiving missing parameter error ....................................................77-15 C901710049 Receiving no configured AS for ASP .................................................77-15

77.1 Overview
M3UA is short for MTP3-User Adaptation Layer. It supports IP bearer of messages of some SS7 MTP3 users, seamless operations of peer-layer MTP3 user protocols, and MTP3 nework management functions. The M3UA error statistics task performs measurement of various errors of M3UA. This chapter introduces the meaning, usage, and measurement point of M3UA error statistic measurement counters.

77.2 C901710001 Invalid Version(T)

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Invalid Version".

Measurement Point
The counter accumulates when an Error message with the error code of "Invalid Version" is sent outwards from the local office.

77.3 C901710002 Unsupported Message Class(T)

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Unsupported Message Class".

77-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 77 M3UA Error Statistics

Measurement Point
The counter accumulates when an Error message with the error code of "Unsupported Message Class" is sent outwards from the local office.

77.4 C901710003 Unsupported Message Type(T)

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Unsupported Message Type".

Measurement Point
The counter accumulates when an Error message with the error code of "Unsupported Message Type" is sent outwards from the local office.

77.5 C901710004 Unexpected Message(T)

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Unexpected Message".

Measurement Point
The counter accumulates when an Error message with the error code of "Unexpected Message" is sent outwards from the local office.

77.6 C901710005 Unsupported Traffic Mode Type(T)

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Unsupported Traffic Mode".

Measurement Point
The counter accumulates when an Error message with the error code of "Unsupported Traffic Mode" is sent outwards from the local office.

77.7 C901710006 Invalid Routing Context(T)

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Invalid Routing Context".
77-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter accumulates when an Error message with the error code of "Invalid Routing Context" is sent outwards from the local office.

77.8 C901710007 Protocol Error(T)

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Protocol Error".

Measurement Point
The counter accumulates when an Error message with the error code of "Protocol Error" is sent outwards from the local office.

77.9 C901710008 Invalid Message Type(T)

Description
This counter counts the number of invalid message types sent. It is same as the counter "Unsupported Message Type(T)".

Measurement Point
The counter counts when the message type sent is invalid.

77.10 C901710009 Number of error message sent

Description
This counter counts the number of error messages sent outwards from the local office.

Measurement Point
The counter accumulates when the error message is sent outwards from the local office.

77.11 C901710010 Invalid Version(R)

Description
This counter counts when an Error message is received, with the error code of "Invalid Version".

77-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 77 M3UA Error Statistics

Measurement Point
The counter accumulates when an Error message with the error code of "Invalid Version" is received.

77.12 C901710011 Unsupported Message Class(R)

Description
This counter counts when an Error message is received, with the error code of "Unsupported Message Class".

Measurement Point
The counter accumulates when an Error message with the error code of "Unsupported Message Class" is received.

77.13 C901710012 Unsupported Message Type(R)

Description
This counter counts when an Error message is received, with the error code of "Unsupported Message Type".

Measurement Point
The counter accumulates when an Error message with the error code of "Unsupported Message Type" is received.

77.14 C901710013 Unexpected Message(R)

Description
This counter counts when an Error message is received, with the error code of "Unexpected Message".

Measurement Point
The counter accumulates when an Error message with the error code of "Unexpected Message" is received.

77.15 C901710014 Unsupported Traffic Mode Type(R)

Description
This counter counts when an Error message is received, with the error code of "Unsupported Traffic Mode".
77-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter accumulates when an Error message with the error code of "Unsupported Traffic Mode" is received.

77.16 C901710015 Invalid Routing Context(R)

Description
This counter counts when an Error message is received, with the error code of "Invalid Routing Context".

Measurement Point
The counter accumulates when an invalid routing context message is received.

77.17 C901710016 Protocol Error(R)

Description
This counter counts when an Error message is received, with the error code of "Protocol Error".

Measurement Point
The counter accumulates when an Error message with the error code of "Protocol Error" is received.

77.18 C901710017 Invalid Message Type(R)

Description
This counter counts the number of invalid message types received. It is same as the counter "Unsupported Message Type(R)".

Measurement Point
The counter counts when the message type received is invalid.

77.19 C901710018 Number of error message received

Description
This counter counts the number of error messages received.

77-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 77 M3UA Error Statistics

Measurement Point
The counter accumulates when the error message is received.

Unit
Times

77.20 C901710019 Unknown Remote User

Description
This counter counts when a DUPU message is received, with the indication of "Unknown".

Measurement Point
The counter accumulates when a DUPU message with the indication of "Unknown" is received.

77.21 C901710020 Unequipped Remote User

Description
This counter counts when a DUPU message is received, with the indication of "Unequipped Remote User".

Measurement Point
The counter accumulates when a DUPU message with the indication of "Unequipped Remote User" is received.

77.22 C901710021 Inaccessible Remote User

Description
This counter counts when a DUPU message is received, with the indication of "Inaccessible Remote User".

Measurement Point
The counter accumulates when a DUPU message with the indication of "Inaccessible Remote User" is received.

77-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

77.23 C901710022 Number of DUPU message received

Description
This counter counts the number of DUPU messages received.

Measurement Point
The counter accumulates when the DUPU message is received.

Unit
Times

77.24 C901710023 Invalid Net APPEARANCE(T)

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Invalid Network Appearance".

Measurement Point
The counter accumulates when an Error message with the error code of "Invalid Network Appearance" is sent outwards from the local office.

77.25 C901710024 Invalid Net APPEARANCE(R)

Description
This counter counts when an Error message is received, with the error code of "Invalid Network Appearance".

Measurement Point
The counter accumulates when an Error message with the error code of "Invalid Network Appearance" is received.

77.26 C901710025 Number of DUPU message sent which cause is unknown

Description
This counter counts when a DUPU message is sent, with the indication of "Unknown".

77-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 77 M3UA Error Statistics

Measurement Point
The counter accumulates when a DUPU message with the indication of "Unknown" is sent.

Unit
Times

77.27 C901710026 Number of DUPU message sent which cause is Unequipped Remote User
Description
This counter counts when a DUPU message is sent, with the indication of "Unequipped Remote User".

Measurement Point
The counter accumulates when a DUPU message with the indication of "Unequipped Remote User" is sent.

Unit
Times

77.28 C901710027 Number of DUPU message sent which cause is Inaccessible Remote User
Description
This counter counts when a DUPU message is sent, with the indication of "Inaccessible Remote User".

Measurement Point
The counter accumulates when a DUPU message with the indication of "Inaccessible Remote User" is sent.

Unit
Times

77.29 C901710028 Number of DUPU message sent

Description
This counter counts the number of DUPU messages sent.
77-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter accumulates when the DUPU message is sent.

Unit
Times

77.30 C901710029 Number of message discard controlled by license

Description
When the number of forwarding message exceeds the maximum forwarding times allowed in Licence, the overload control function decides whether the subsequent messages will be discarded. If a message should be discarded, then the message will not be forwarded outwards from the local office and is directly discarded. The condition is reported to OAM and the counter accumulates.

Measurement Point
When the number of forwarding message exceeds the maximum forwarding times allowed in Licence, call the overload control function to decide whether the subsequent messages will be discarded.

77.31 C901710030 Sending invalid stream ID

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Invalid Stream ID".

Measurement Point
The counter accumulates when an Error message with the error code of "Invalid Stream ID" is sent outwards from the local office.

77.32 C901710031 Sending refuse error, reason is management blocking

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Management Blocking Rejection".

77-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 77 M3UA Error Statistics

Measurement Point
The counter accumulates when an Error message with the error code of "Management Blocking Rejection" is sent outwards from the local office.

77.33 C901710032 Sending required ASP ID

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "ASP ID Required".

Measurement Point
The counter accumulates when an Error message with the error code of "ASP ID Required" is sent outwards from the local office.

77.34 C901710033 Sending invalid ASP ID

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Invalid ASP ID".

Measurement Point
The counter accumulates when an Error message with the error code of "Invalid ASP ID" is sent outwards from the local office.

77.35 C901710034 Sending invalid parameter value

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Invalid Parameter Value".

Measurement Point
The counter accumulates when an Error message with the error code of "Invalid Parameter Value" is sent outwards from the local office.

77.36 C901710035 Sending parameter field error

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Parameter Field Error".
77-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter accumulates when an Error message with the error code of "Parameter Field Error" is sent outwards from the local office.

77.37 C901710036 Sending unexpected parameter error

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Unexpected Parameter".

Measurement Point
The counter accumulates when an Error message with the error code of "Unexpected Parameter" is sent outwards from the local office.

77.38 C901710037 Sending destination status unknown

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Destination Status Unknown".

Measurement Point
The counter accumulates when an Error message with the error code of "Destination Status Unknown" is sent outwards from the local office.

77.39 C901710038 Sending missing parameter error

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "Missing Parameter Error".

Measurement Point
The counter accumulates when an Error message with the error code of "Missing Parameter Error" is sent outwards from the local office.

77-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 77 M3UA Error Statistics

77.40 C901710039 Sending no configured AS for ASP

Description
This counter counts when an Error message is sent outwards from the local office, with the error code of "AS not configured with the ASP".

Measurement Point
The counter accumulates when an Error message with the error code of "AS not configured with the ASP" is sent outwards from the local office.

77.41 C901710040 Receiving invalid stream ID

Description
This counter counts when an Error message is received, with the error code of "Invalid Stream ID".

Measurement Point
The counter accumulates when an Error message with the error code of "Invalid Stream ID" is received.

77.42 C901710041 Receiving refuse error, reason is management blocking

Description
This counter counts when an Error message is received, with the error code of "Management Blocking Rejection".

Measurement Point
The counter accumulates when an Error message with the error code of "Management Blocking Rejection" is received.

77.43 C901710042 Receiving required ASP ID

Description
This counter counts when an Error message is received, with the error code of "ASP ID Required".

77-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter accumulates when an Error message with the error code of "ASP ID Required" is received.

77.44 C901710043 Receiving invalid ASP ID

Description
This counter counts when an Error message is received, with the error code of "Invalid ASP ID".

Measurement Point
The counter accumulates when an Error message with the error code of "Invalid ASP ID" is received.

77.45 C901710044 Receiving invalid parameter value

Description
This counter counts when an Error message is received, with the error code of "Invalid Parameter Value".

Measurement Point
The counter accumulates when an Error message with the error code of "Invalid Parameter Value" is received.

77.46 C901710045 Receiving parameter field error

Description
This counter counts when an Error message is received, with the error code of "Parameter Field Error".

Measurement Point
The counter accumulates when an Error message with the error code of "Parameter Field Error" is received.

77-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 77 M3UA Error Statistics

77.47 C901710046 Receiving unexpected parameter error

Description
This counter counts when an Error message is received, with the error code of "Unexpected Parameter".

Measurement Point
The counter accumulates when an Error message with the error code of "Unexpected Parameter" is received.

77.48 C901710047 Receiving destination status unknown

Description
This counter counts when an Error message is received, with the error code of "Destination Status Unknown".

Measurement Point
The counter accumulates when an Error message with the error code of "Destination Status Unknown" is received.

77.49 C901710048 Receiving missing parameter error

Description
This counter counts when an Error message is received, with the error code of "Missing Parameter Error".

Measurement Point
The counter accumulates when an Error message with the error code of "Missing Parameter Error" is received.

77.50 C901710049 Receiving no configured AS for ASP

Description
This counter counts when an Error message is received, with the error code of "AS not configured with the ASP".
77-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter accumulates when an Error message with the error code of "AS not configured with the ASP" is received.

77-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 78

M3UA AS Performance Statistics

Table of Contents
Overview ..................................................................................................................78-1 C901720001 Number of service message transmitted..............................................78-1 C901720002 Bytes of service message transmitted .................................................78-2 C901720003 Number of service message received..................................................78-2 C901720004 Bytes of service message received .....................................................78-2

78.1 Overview
M3UA is short for MTP3-User Adaptation Layer. It supports IP bearer of messages of some SS7 MTP3 users, seamless operations of peer-layer MTP3 user protocols, and MTP3 nework management functions. AS is short for Application Server. AS, which works for M3UA, is the logic entity that works for the specific route keyword of M3UA. This measurement takes AS as the unit. It performs measurement of the number of messages between M3UA and upper-layer users and the number of bytes of messages between M3UA and upper-layer users. This chapter introduces the meaning, usage, and measurement point of M3UA AS performance statistic measurement counters.

78.2 C901720001 Number of service message transmitted

Description
This counter counts the number of upper-layer user messages sent by AS of M3UA.

Measurement Point
The counter counts when M3UA sends the upper-layer user message.

Unit
Times

78-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

78.3 C901720002 Bytes of service message transmitted

Description
This counter counts the number of bytes of upper-layer user messages sent by AS of M3UA.

Measurement Point
The counter counts when M3UA sends the upper-layer user message.

Unit
Byte

78.4 C901720003 Number of service message received

Description
This counter counts the number of upper-layer user messages received by AS of M3UA.

Measurement Point
The counter counts when M3UA receives the upper-layer user message from SCTP.

Unit
Times

78.5 C901720004 Bytes of service message received

Description
This counter counts the number of bytes of upper-layer user messages received by AS of M3UA.

Measurement Point
The counter counts when M3UA receives the upper-layer user message from SCTP.

Unit
Byte

78-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 79

Timer Statistics
Table of Contents
Overview ..................................................................................................................79-1 C901730001 Number of all timers ............................................................................79-1 C901730002 Number of available timer....................................................................79-2 C901730003 Peak value of timer..............................................................................79-2 C901730004 Number of success to set timer ...........................................................79-2 C901730005 Number of failure to set timer ..............................................................79-2

79.1 Overview
Timer statistics performs measurement of the following information: total number of timers, number of available timers, peak value of the timer, number of successes in setting timer, and number of failures in setting timer. Timer resource refers to the memory block resource allocated according to the configuration during the system power-on process. The total number of timers is fixed, which is decided by the system configuration. The number of available timers refers to the number of idle timer control blocks. Peak value of the timer refers to the maximum usage value of the control block of the timer occupied during a period of time. During the system running, if the timer control block is released due to that the timer expires, the number of available timers increases. If the system sets timer to get the timer control block, the number of available timers decreases.

79.2 C901730001 Number of all timers

Description
This counter counts the total number of timers.

Measurement Point
The counter's value is fixed, depending on the configuration.

79-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

79.3 C901730002 Number of available timer

Description
This counter counts the number of available timers.

Measurement Point
The counter counts when a timer control block is released successfully.

79.4 C901730003 Peak value of timer

Description
This counter records the peak value of timer usage.

Measurement Point
The counter counts when the timer usage exceeds the current peak value.

79.5 C901730004 Number of success to set timer

Description
This counter counts the number of successes in setting timer.

Measurement Point
The counter counts when the timer is set successfully.

Unit
Times

79.6 C901730005 Number of failure to set timer

Description
This counter counts the number of failures in setting timer.

Measurement Point
The counter counts when the timer setting fails.

Unit
Times
79-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 80

Scheduling Performance Statistics

Table of Contents
Overview ..................................................................................................................80-1 C901740001 Number of active process....................................................................80-1 C901740002 Number of process ..............................................................................80-2 C901740003 Number of process scheduled .............................................................80-2

80.1 Overview
Scheduling performance statistics refer to the statistics on the scheduling of level-2 processes, including the number of active process instances, number of process instances, and number of processes instances scheduled in the last two seconds. Through the statistics on the scheduling of level-2 processes, user can have a rough knowledge of the system operation status. The number of active process instances means the number of process instances that can obtain CPU for operation and that are being running, that is, process instances in the ready queue or running state under each scheduling task. The number of process instances means the maximum number of process instances allowed for user registration in registry. The number of tasks scheduled in current 2 seconds means the number of tasks that are scheduled in the last two seconds.

80.2 C901740001 Number of active process

Description
This counter counts the total number of active processes.

Measurement Point
The measurement point is determined during process creation and is not changed during the operation.

80-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

80.3 C901740002 Number of process

Description
This counter counts the total number of processes.

Measurement Point
The measurement point is configured in the configuration file.

80.4 C901740003 Number of process scheduled

Description
This counter counts the total number of scheduled processes.

Measurement Point
This counter increments when a process is scheduled. It counts the times of process scheduling in the last 2 seconds.

80-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 81

UB Memory Performance Statistics

Table of Contents
Overview ..................................................................................................................81-1 C901750001 ID of UB Set ........................................................................................81-1 C901750002 Size of UB ...........................................................................................81-2 C901750003 Number of UB .....................................................................................81-2 C901750004 Number of UB used.............................................................................81-2

81.1 Overview
UB memory performance statistics refer to the statistics on the usage of current system UB and user UB on a certain board, including the statistics based on UB size and number of used UBs. Two statistic methods are available: l l Calculate UB usage based on quantity Calculate UB usage based on size

The statistics based on quantity reflects the percentage of used UB from the perspective of quantity. The statistics based on size reflects the usage of UB from the perspective of used size. If the query mode is 1, the system starts statistics based on the quantity of used UBs and returns the percentage of currently used UBs. If the query mode is -1, the system starts statistics based on the size of used UBs and returns the percentage of currently used USs. The unit of this UB performance statistics is board.

81.2 C901750001 ID of UB Set

Description
This counter counts the ID of a UB set. INNER_MEM_POOL_GROUP represents the memory pool sets that are internally used. USER_MEM_POOL_GROUP represents the memory pool sets that are used by user.

Measurement Point
The measurement point is configured and unchanged.
81-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

81.3 C901750002 Size of UB

Description
This counter counts the size of the UBs in a UB set.

Measurement Point
The measurement point is configured and unchanged.

81.4 C901750003 Number of UB

Description
This counter counts the number of UBs in the UB pool set.

Measurement Point
The measurement point is related to current UB usage status and may dynamically change with the addition or reduction of switching blocks.

81.5 C901750004 Number of UB used

Description
This counter counts the number of used UBs.

Measurement Point
The measurement point is related to the current UB usage status.

81-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 82

Hard Disk and FLASH Performance Statistics

Table of Contents
Overview ..................................................................................................................82-1 C901760001 Disk Device ID.....................................................................................82-1 C901760002 Total space..........................................................................................82-1 C901760003 Free space ..........................................................................................82-2

82.1 Overview
The disks used by platform are hard disks and FLASHs. If the remaining space is insufficient, the upper application of those requiring storage is affected. Therefore, it is necessary to take real-time statistics on disk space so that user can know the disk usage situation timely. Disk space performance statistics refer to the statistics on remaining space and total space of disks on a board. The keyword is the device name of disk.

82.2 C901760001 Disk Device ID

Description
This counter indicates the disk device ID, which is /FLASH0, /DOC0, /IDE0, /IDE1, /IDE2, or /IDE3.

Measurement Point
The measurement point is related to the disk configuration on the current board.

82.3 C901760002 Total space

Description
This counter counts the total space.

Measurement Point
The measurement point is unchanged.

82-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
KB

82.4 C901760003 Free space

Description
This counter counts the free space.

Measurement Point
The disk space occupation changes each time a file is added, modified, or deleted.

Unit
KB

82-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 83

SCTP Protocol Statistics

Table of Contents
Overview ..................................................................................................................83-2 C901770001 Number of Association Accepted.........................................................83-2 C901770002 Number of Association Initiated ...........................................................83-2 C901770003 Number of Association Shutdown........................................................83-2 C901770004 Number of Association Abort ...............................................................83-3 C901770005 Number of Chunk Retransmitted .........................................................83-3 C901770006 Number of Unordered Chunk Sent ......................................................83-3 C901770007 Number of Unordered Chunk Received ...............................................83-3 C901770008 Number of Chunk Sent ........................................................................83-4 C901770009 Number of Chunk Received ................................................................83-4 C901770010 Number of Init Sent .............................................................................83-4 C901770011 Number of Init Received ......................................................................83-4 C901770012 Number of Init Ack Sent.......................................................................83-4 C901770013 Number of Init Ack Received ...............................................................83-5 C901770014 Number of COOKIE Sent ....................................................................83-5 C901770015 Number of Cookie Received................................................................83-5 C901770016 Number of Cookie Ack Sent ................................................................83-5 C901770017 Number of Cookie Ack Received .........................................................83-6 C901770018 Number of Heartbeat Sent...................................................................83-6 C901770019 Number of Heartbeat Received ...........................................................83-6 C901770020 Number of Heartbeat Ack Sent............................................................83-6 C901770021 Number of Heartbeat Ack Received ....................................................83-6 C901770022 Number of Abort Chunk Sent...............................................................83-7 C901770023 Number of Abort Chunk Received .......................................................83-7 C901770024 Number of Shutdown Chunk Sent .......................................................83-7 C901770025 Number of Shutdown Chunk Received ................................................83-7 C901770026 Number of Shutdown Ack Chunk Sent.................................................83-8 C901770027 Number of Shutdown Ack Chunk Received .........................................83-8 C901770028 Number of Shutdown Complete Sent ..................................................83-8 C901770029 Number of Shutdown Complete Received ...........................................83-8 C901770030 Number of Error Chunk Sent ...............................................................83-9 C901770031 Number of Error Chunk Received........................................................83-9 C901770032 Number of ECNE Chunk Sent .............................................................83-9 C901770033 Number of ECNE Chunk Received......................................................83-9 C901770034 Number of CWR Chunk Sent.............................................................83-10 C901770035 Number of CWR Chunk Received .....................................................83-10 C901770036 Number of Error Packet Received .....................................................83-10
83-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901770037 Number of OOTB Chunk Received....................................................83-10 C901770038 Number of ULP Sent Chunk Request in association alive.................. 83-11 C901770039 Number of ULP Sent Chunk Request to SCTP OK in association alive ....................................................................................................................... 83-11 C901770040 Number of ULP Sent Chunk Request during a little time.................... 83-11 C901770041 Number of ULP Sent Chunk Request to SCTP OK during a little time . 83-11 C901770042 Number of SCTP Sent Chunk Request to ULP ..................................83-12 C901770043 Number of Abort Request from ULP ..................................................83-12 C901770044 Number of Received Abort From Peer ..............................................83-12 C901770045 Number of Link Break for Retransfer .................................................83-12

83.1 Overview
SCTP, that is, stream control transmission protocol, supports the transmission of PSTN signaling messages over IP network and the transmission of signaling messages within IP network. This measurement task uses module as the unit to measure SCTP-related data messages, number of management messages, and number bytes. In addition, it classifies the statistics based on the local SCTP transceiving errors. This chapter describes the meanings, usages, and measurement points of SCTP stack measurement counters.

83.2 C901770001 Number of Association Accepted

Description
This counter counts the number of associations passively established.

Measurement Point
When an association is accepted, this counter counts.

83.3 C901770002 Number of Association Initiated

Description
This counter counts the number of initiated associations.

Measurement Point
When an association is actively initiated, this counter counts.

83.4 C901770003 Number of Association Shutdown

Description
This counter counts the number of shutdown associations.
83-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 83 SCTP Protocol Statistics

Measurement Point
When an association is shut down, this counter counts.

83.5 C901770004 Number of Association Abort

Description
This counter counts the number of aborted associations.

Measurement Point
When an association is aborted, this counter counts.

83.6 C901770005 Number of Chunk Retransmitted

Description
This counter counts the times of chunk retransmission.

Measurement Point
When a chunks is retransmitted, this counter counts.

83.7 C901770006 Number of Unordered Chunk Sent

Description
This counter counts the number of sent unordered chunks.

Measurement Point
When an unordered chunk is sent, this counter counts.

83.8 C901770007 Number of Unordered Chunk Received

Description
This counter counts the number of received unordered chunks.

Measurement Point
When an unordered chunk is received, this counter counts.

83-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

83.9 C901770008 Number of Chunk Sent

Description
This counter counts the number of sent chunks.

Measurement Point
When a chunk is sent, this counter counts.

83.10 C901770009 Number of Chunk Received

Description
This counter counts the number of received chunks.

Measurement Point
When a chunk is received, this counter counts.

83.11 C901770010 Number of Init Sent

Description
This counter counts the number of sent INIT chunks.

Measurement Point
When an INIT chunk is sent, this counter counts.

83.12 C901770011 Number of Init Received

Description
This counter counts the number of received INIT chunks.

Measurement Point
When an INIT chunk is received, this counter counts.

83.13 C901770012 Number of Init Ack Sent

Description
This counter counts the number of sent INITACK chunks.

83-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 83 SCTP Protocol Statistics

Measurement Point
When an INITACK chunks is sent, this counter counts.

83.14 C901770013 Number of Init Ack Received

Description
This counter counts the number of received INITACK chunks.

Measurement Point
When an INITACK chunk is received, this counter counts.

83.15 C901770014 Number of COOKIE Sent

Description
This counter counts the number of sent COOKIE chunks.

Measurement Point
When a COOKIE chunk is sent, this counter counts.

83.16 C901770015 Number of Cookie Received

Description
This counter counts the number of received COOKIE chunks.

Measurement Point
When a COOKIE chunk is received, this counter counts.

83.17 C901770016 Number of Cookie Ack Sent

Description
This counter counts the number of sent COOKIE ACK chunks.

Measurement Point
When a COOKIE ACK chunk is sent, this counter counts.

83-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

83.18 C901770017 Number of Cookie Ack Received

Description
This counter counts the number of received COOKIE ACK chunks.

Measurement Point
When a COOKIE ACK chunk is received, this counter counts.

83.19 C901770018 Number of Heartbeat Sent

Description
This counter counts the number of sent heartbeat chunks.

Measurement Point
When a HEARTBEAT chunk is sent, this counter counts.

83.20 C901770019 Number of Heartbeat Received

Description
This counter counts the number of received heartbeats.

Measurement Point
When a HEARTBEAT chunk is received, this counter counts.

83.21 C901770020 Number of Heartbeat Ack Sent

Description
This counter counts the number of sent heartbeat acknowledgement chunks.

Measurement Point
When a HEARTBEAT ACK chunk is sent, this counter counts.

83.22 C901770021 Number of Heartbeat Ack Received

Description
This counter counts the number of sent heartbeat acknowledgement chunks.

83-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 83 SCTP Protocol Statistics

Measurement Point
When a HEARTBEAT ACK chunk is sent, this counter counts.

83.23 C901770022 Number of Abort Chunk Sent

Description
This counter counts the number of sent ABORT chunks.

Measurement Point
When an ABORT chunk is sent, this counter counts.

83.24 C901770023 Number of Abort Chunk Received

Description
This counter counts the number of received ABORT chunks.

Measurement Point
When an ABORT chunk is received, this counter counts.

83.25 C901770024 Number of Shutdown Chunk Sent

Description
This counter counts the number of sent SHUTDOWN chunks.

Measurement Point
When a SHUTDOWN chunk is sent, this counter counts.

83.26 C901770025 Number of Shutdown Chunk Received

Description
This counter counts the number of received SHUTDOWN chunks.

Measurement Point
When a SHUTDOWN chunk is received, this counter counts.

83-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

83.27 C901770026 Number of Shutdown Ack Chunk Sent

Description
This counter counts the number of sent SHUTDOWN ACK chunks.

Measurement Point
When a SHUTDOWN ACK chunk is sent, this counter counts.

83.28 C901770027 Number of Shutdown Ack Chunk Received

Description
This counter counts the number of received SHUTDOWN ACK chunks.

Measurement Point
When a SHUTDOWN ACK chunk is received, this counter counts.

83.29 C901770028 Number of Shutdown Complete Sent

Description
This counter counts the number of sent SHUTDOWN COMPLETE chunks.

Measurement Point
When a SHUTDOWN COMPLETE chunk is sent, this counter counts.

83.30 C901770029 Number of Shutdown Complete Received

Description
This counter counts the number of received SHUTDOWN COMPLETE chunks.

Measurement Point
When a SHUTDOWN COMPLETE chunk is received, this counter counts.

83-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 83 SCTP Protocol Statistics

83.31 C901770030 Number of Error Chunk Sent

Description
This counter counts the number of sent ERROR chunks.

Measurement Point
When an ERROR chunk is sent, this counter counts.

83.32 C901770031 Number of Error Chunk Received

Description
This counter counts the number of received ERROR chunks.

Measurement Point
When an ERROR chunk is received, this counter counts.

83.33 C901770032 Number of ECNE Chunk Sent

Description
This counter counts the number of sent ECNE chunks. As the implementation at bottom layer is not supported, the statistics are invalid.

Measurement Point
When an ECNE chunk is sent, this counter counts.

83.34 C901770033 Number of ECNE Chunk Received

Description
This counter counts the number of sent ECNE chunks. As the implementation at bottom layer is not supported, the statistics are invalid.

Measurement Point
When an ECNE chunk is sent, this counter counts.

83-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

83.35 C901770034 Number of CWR Chunk Sent

Description
This counter counts the number of sent CWR chunks. As the implementation at bottom layer is not supported, the statistics are invalid.

Measurement Point
When a CWR chunk is sent, this counter counts.

83.36 C901770035 Number of CWR Chunk Received

Description
This counter counts the number of received CWR chunks. As the implementation in bottom layer is not supported, the statistics are invalid.

Measurement Point
When a CWR chunk is received, this counter counts.

83.37 C901770036 Number of Error Packet Received

Description
This counter counts the number of received Error packets.

Measurement Point
When an Error packet is received, this counter counts.

83.38 C901770037 Number of OOTB Chunk Received

Description
This counter counts the number of received OOTB chunks.

Measurement Point
When an OOTB chunk is received, this counter counts.

83-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 83 SCTP Protocol Statistics

83.39 C901770038 Number of ULP Sent Chunk Request in association alive

Description
This counter counts the number of chunk requests sent by ULP when association is alive.

Measurement Point
When ULP initiates chunk requests when association is alive, this counter counts.

83.40 C901770039 Number of ULP Sent Chunk Request to SCTP OK in association alive
Description
This counter counts the number of successful chunk requests sent by ULP to SCTP when association is alive. As the implementation at bottom layer is not supported, the statistics is invalid.

Measurement Point
Each time there is a successful chunk request sent by ULP when association is alive, this counter counts.

83.41 C901770040 Number of ULP Sent Chunk Request during a little time
Description
This counter counts the number of chunk requests sent by ULP. As the implementation at bottom layer is not supported, the statistics are invalid.

Measurement Point
When ULP sends a chunk request, this counter counts.

83.42 C901770041 Number of ULP Sent Chunk Request to SCTP OK during a little time
Description
This counter counts the number of successful chunk requests sent by ULP to SCTP. As the implementation at bottom layer is not supported, the statistics are invalid.
83-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When a chunk request sent by ULP to SCTP is successful, this counter counts.

83.43 C901770042 Number of SCTP Sent Chunk Request to ULP

Description
This counter counts the number of chunk requests sent by SCTP to ULP. As the implementation at bottom layer is not supported, the statistics are invalid.

Measurement Point
When SCTP sends chunk requests to ULP, this counter counts.

83.44 C901770043 Number of Abort Request from ULP

Description
This counter counts the number of ABORT requests from ULP. As the implementation at lower layer is not supported, the statistics are invalid.

Measurement Point
When ULP sends an ABORT request to SCTP, this counter counts.

83.45 C901770044 Number of Received Abort From Peer

Description
This counter counts the number of received ABORT messages from peer end. As the implementation at lower layer is not supported, the statistics are invalid.

Measurement Point
When SCTP receives an ABORT message from the peer end, this counter counts.

83.46 C901770045 Number of Link Break for Retransfer

Description
This counter counts the number of link disconnections due to retransfer.
83-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 83 SCTP Protocol Statistics

Measurement Point
When a link is broken due to retransmission, this counter counts.

83-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

83-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 84

SCTP Association Statistics

Table of Contents
Overview ..................................................................................................................84-1 C901780001 State of association .............................................................................84-1 C901780002 Send synchronous Msg to ULP fail......................................................84-2 C901780003 ULPID from ULP invalid.......................................................................84-2 C901780004 Number of Association Initiated to ULP ...............................................84-2 C901780005 Number of Association Accepted to ULP .............................................84-2 C901780006 Number of Association Restarted to ULP ............................................84-3 C901780007 Number of Association lost to ULP ......................................................84-3 C901780008 Number of Destroy instance ................................................................84-3 C901780009 Number of Shutdown request from ULP ..............................................84-3 C901780010 Number of Abort request from ULP .....................................................84-4

84.1 Overview
Media Control Transmission Protocol (SCTP) supports transmission of PSTN signaling messages over IP network and transmission of signaling messages within IP network. Association refers to the relation between two SCTP endpoints, including the protocol status information including the two endpoints, verification tag, and Transmission Sequence Number (TSN). SCTP association-based measurement task uses association as the unit to measure the number of SCTP-related messages and bytes on each association, etc. In addition, it classifies the local SCTP reception errors and collects statistics respectively. This chapter describes the meanings, usages, and measurement points of SCTP association-based measurement counters.

84.2 C901780001 State of association

Description
Association states are as follows: Closed, Cookie wait, Cookie Echoed, Established, Shutdown Pending, Shutdown Received, Shutdown Sent, and Shutdown Ack Sent.

Measurement Point
None

84-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

84.3 C901780002 Send synchronous Msg to ULP fail

Description
This counter counts the number of unsuccessful synchronization message sent to ULP.

Measurement Point
When synchronization messages are sent to ULP, this counter counts.

84.4 C901780003 ULPID from ULP invalid

Description
This counter counts the number of invalid ULPIDs returned by ULP.

Measurement Point
When ULP returns ULPID, this counter counts.

84.5 C901780004 Number of Association Initiated to ULP

Description
This counter counts the number of associations initiated to ULP.

Measurement Point
When association is actively established and Cookie ACK is received, this counter increments.

84.6 C901780005 Number of Association Accepted to ULP

Description
This counter counts the number of passively established associations reported to ULP.

Measurement Point
When association is passively established and Cookie Echo is received, this counter increments.

84-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 84 SCTP Association Statistics

84.7 C901780006 Number of Association Restarted to ULP

Description
This counter counts the number of restarted associations reported to ULP.

Measurement Point
When an association is restarted, this counter counts.

84.8 C901780007 Number of Association lost to ULP

Description
This counter counts the number of lost associations reported to ULP.

Measurement Point
When an association is lost, this counter counts.

84.9 C901780008 Number of Destroy instance

Description
This counter counts the number of Destroy instance requests sent by ULP.

Measurement Point
When ULP sends a Destroy instance request, this counter counts.

84.10 C901780009 Number of Shutdown request from ULP

Description
This counter counts the number of association shutdown requests sent by ULP.

Measurement Point
When ULP sends a SHUTDOWN message, this counter counts.

84-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

84.11 C901780010 Number of Abort request from ULP

Description
This counter counts the number of association abort requests sent by ULP.

Measurement Point
When ULP sends an ABORT message, this counter counts.

84-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 85

SDTB Fiber Performance Statistics

Table of Contents
Overview ..................................................................................................................85-2 C901790001 slot number (no description) ................................................................85-3 C901790002 master/slave state (no description) ......................................................85-3 C901790003 SDH Type............................................................................................85-3 C901790004 Regenerator Section BIP-8 Error .........................................................85-3 C901790005 Multiplex Section BIP-24 Error.............................................................85-3 C901790006 VC-4 BIP-8 Error (High-order path 1) ..................................................85-4 C901790007 VC-4 BIP-8 Error (High-order path 2) ..................................................85-4 C901790008 VC-4 BIP-8 Error (High-order path 3) ..................................................85-4 C901790009 Multiplex Section Remote Error Indication ...........................................85-5 C901790010 VC-4 Remote Error Indication (High-order path 1) ...............................85-5 C901790011 VC-4 Remote Error Indication (High-order path 2) ...............................85-5 C901790012 VC-4 Remote Error Indication (High-order path 3) ...............................85-6 C901790013 Multiplex Section Remote Background Block Error Ratio.....................85-6 C901790014 Multiplex Section Remote Errored Second Ratio .................................85-6 C901790015 Multiplex Section Remote Errored Second ..........................................85-7 C901790016 Multiplex Section Remote Severely Errored Second............................85-7 C901790017 Multiplex Section Remote Unavailable Second....................................85-8 C901790018 VC-4 Remote Background Block Error Ratio (High-order path 1).........85-8 C901790019 VC-4 Remote Background Block Error Ratio (High-order path 2).........85-9 C901790020 VC-4 Remote Background Block Error Ratio (High-order path 3).........85-9 C901790021 VC-4 Remote Errored Second Ratio (High-order path 1) .....................85-9 C901790022 VC-4 Remote Errored Second Ratio (High-order path 2) ...................85-10 C901790023 VC-4 Remote Errored Second Ratio (High-order path 3) ...................85-10 C901790024 VC-4 Remote Errored Second (High-order path 1) ............................85-10 C901790025 VC-4 Remote Errored Second (High-order path 2) ............................ 85-11 C901790026 VC-4 Remote Errored Second (High-order path 3) ............................ 85-11 C901790027 VC-4 Remote Severely Errored Second (High-order path 1).............. 85-11 C901790028 VC-4 Remote Severely Errored Second (High-order path 2)..............85-12 C901790029 VC-4 Remote Severely Errored Second (High-order path 3)..............85-12 C901790030 VC-4 Remote Unavailable Second (High-order path 1)......................85-12 C901790031 VC-4 Remote Unavailable Second (High-order path 2)......................85-13 C901790032 VC-4 Remote Unavailable Second (High-order path 3)......................85-13 C901790033 B1(Regenerator Section) BIP-8 Background Block Error Ratio ..........85-13
85-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901790034 B1(Regenerator Section) BIP-8 Errored Second Ratio ......................85-14 C901790035 B1(Regenerator Section) BIP-8 Errored Second................................85-14 C901790036 B1(Regenerator Section) BIP-8 Severely Errored Second .................85-14 C901790037 B1(Regenerator Section) BIP-8 Unavailable Second .........................85-15 C901790038 B2(Multiplex Section) BIP-24 Background Block Error Ratio..............85-15 C901790039 B2(Multiplex Section) BIP-24 Errored Second Ratio ..........................85-16 C901790040 B2(Multiplex Section) BIP-24 Errored Second ...................................85-16 C901790041 B2(Multiplex Section) BIP-24 Severely Errored Second.....................85-16 C901790042 B2(Multiplex Section) BIP-24 Unavailable Second.............................85-17 C901790043 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 1)....85-17 C901790044 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 2)....85-18 C901790045 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 3)....85-18 C901790046 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 1) ................85-18 C901790047 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 2) ................85-19 C901790048 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 3) ................85-19 C901790049 B3(VC-4) BIP-8 Errored Second (High-order path 1) .........................85-19 C901790050 B3(VC-4) BIP-8 Errored Second (High-order path 2) .........................85-20 C901790051 B3(VC-4) BIP-8 Errored Second (High-order path 3) .........................85-20 C901790052 B3(VC-4) BIP-8 Severely Errored Second (High-order path 1)...........85-20 C901790053 B3(VC-4) BIP-8 Severely Errored Second (High-order path 2)...........85-21 C901790054 B3(VC-4) BIP-8 Severely Errored Second (High-order path 3)...........85-21 C901790055 B3(VC-4) BIP-8 Unavailable Second (High-order path 1)...................85-21 C901790056 B3(VC-4) BIP-8 Unavailable Second (High-order path 2)...................85-22 C901790057 B3(VC-4) BIP-8 Unavailable Second (High-order path 3)...................85-22 C901790058 LOF second ......................................................................................85-22

85.1 Overview
The statistic task of SDTB optical channel performance collects statistics on the number of error codes of each network section and channel layer in SDTB (accesses SDH transport network) receiving signals. It is used to represent the data performance of each section and channel in SDH transport network. This chapter describes the main performance statistic items, statistic method, and standard compliance of SDTB OI. SDH Digital Trunk Board (SDTB) accesses SDH transport network through a standard STM-1 port at line side. The system side provides 63 E1s or 84 T1s to bear TDM, IMA or PPP service for the system. The statistic items of SDTB optical channel performance include: SDH regenerator B1 error, SDH regenerator B2 error, SDH high-order path B3 error, and SDH low-order path tributary BIP2 error. The statistic method is periodically querying the number of errors of Rx signal at a fixed interval and implement error event handling in accordance with ITU-T G.826.

85-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 85 SDTB Fiber Performance Statistics

85.2 C901790001 slot number (no description)

Description Measurement Point Unit

85.3 C901790002 master/slave state (no description)

Description Measurement Point

85.4 C901790003 SDH Type

Description
SDH has the following types: AU-4, AU-3, and STS-3SDH.

85.5 C901790004 Regenerator Section BIP-8 Error

Description
Regeneration section overhead byte B1 is used as the BIP code to monitor bit errors of regeneration section.

Measurement Point
When the received B1 byte is verified to be inconsistent with the result of BIP-8 check for regenerator section of previous STM-1 frame at local end, the block is assumed to have error and dwB1E increments.

85.6 C901790005 Multiplex Section BIP-24 Error

Description
Three multiplex section overhead byte B2s are used as the BIP code to monitor bit errors of multiplex section.

85-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When the received three B2 bytes are verified to be inconsistent with the result of BIP-24 check for multiplex section of previous STM-1 frame at local end, the block is assumed to have error and dwB2E increments.

85.7 C901790006 VC-4 BIP-8 Error (High-order path 1)

Description
VC-4 POH byte B3 is used as the BIP code to monitor bit errors of VC-4 path. It is valid when SDH type is AU-4, AU-3, and STS-3. The corresponding high-order path is 1.

Measurement Point
When the received B3 byte received by high-order path 1 is verified to be inconsistent with the result of BIP-8 check for VC-4 section of previous STM-1 frame at local end, the block is assumed to have error and dwB3E1 increments.

85.8 C901790007 VC-4 BIP-8 Error (High-order path 2)

Description
This counter is similar to dwB3E1. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2.

Measurement Point
This counter is similar to dwB3E1. It corresponds to high-order path 2.

85.9 C901790008 VC-4 BIP-8 Error (High-order path 3)

Description
This counter is similar to dwB3E2. It corresponds to high-order path 3.

Measurement Point
This counter is similar to dwB3E2. It corresponds to high-order path 3.

85-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 85 SDTB Fiber Performance Statistics

85.10 C901790009 Multiplex Section Remote Error Indication

Description
When peer end device detects BIP-24 error according to the received three B2 bytes, it uses regenerator section overhead byte M1 to send the check result to the local end as Multiplex Section-Remote Error Indication (MS-REI).

Measurement Point
Because at most 24 bit errors can be found, the value range of M1 byte is 0 ~ 24. If M1 is not 0, it indicates that a remote error block exists. In this case, dwMSREI increments.

85.11 C901790010 VC-4 Remote Error Indication (High-order path 1)

Description
When peer end device detects BIP-8 error according to the received B3 byte, it uses bit1 ~ bit4 of VC-4 POH byte G1 to send the check result to the local end as VC-4 path-Remote Error Indication (VC4-REI). When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.

Measurement Point
Because at most eight bit errors can be found, the value range of VC4-REI is 0 ~ 8. If VC4-REI is not 0, it indicates that a remote error block exists. In this case, dwVC4REI1 increments.

85.12 C901790011 VC-4 Remote Error Indication (High-order path 2)

Description
This counter is similar to dwVC4REI1. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2.

Measurement Point
This counter is similar to dwVC4REI1. It corresponds to high-order path 2.

85-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

85.13 C901790012 VC-4 Remote Error Indication (High-order path 3)

Description
This counter is similar to dwVC4REI2. It corresponds to high-order path 3.

Measurement Point
This counter is similar to dwVC4REI2. It corresponds to high-order path 3.

85.14 C901790013 Multiplex Section Remote Background Block Error Ratio

Description
When peer end device detects BIP-24 error according to the received three B2 bytes, it uses regenerator section overhead byte M1 to send the check result to the local end as Multiplex Section-Remote Error Indication (MS-REI). Background block error (BBE) refers to the error blocks after deducting the unusable time and the error blocks appearing in the SES period. The ratio between the BBE numbers and total block numbers after deducting the unusable time and all the blocks during the SES period is called background block error rate (BBER).

Measurement Point
Because at most 24 bit errors can be found, the value range of M1 byte is 0 ~ 24. If M1 is not 0, it indicates that a remote error block exists. Multiplex Section-Remote Error Indication counter dwMSREI increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwMSFEBBE.

85.15 C901790014 Multiplex Section Remote Errored Second Ratio

Description
When peer end device detects BIP-24 error according to the received three B2 bytes, it uses regenerator section overhead byte M1 to send the check result to the local end as Multiplex Section-Remote Error Indication (MS-REI). The ratio between the ES within a specified period of measurement time and the total time used is called error code second ratio (ESR).

85-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 85 SDTB Fiber Performance Statistics

Measurement Point
Because at most 24 bit errors can be found, the value range of M1 byte is 0 ~ 24. If M1 is not 0, it indicates that a remote error block exists. Multiplex Section-Remote Error Indication counter dwMSREI increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwMSFEER.

85.16 C901790015 Multiplex Section Remote Errored Second

Description
When peer end device detects BIP-24 error according to the received three B2 bytes, it uses regenerator section overhead byte M1 to send the check result to the local end as Multiplex Section-Remote Error Indication (MS-REI). When one second has one or more error blocks or at least one deficiency, it is called an Error Second (ES).

Measurement Point
Because at most 24 bit errors can be found, the value range of M1 byte is 0 ~ 24. If M1 is not 0, it indicates that a remote error block exists. Multiplex Section-Remote Error Indication counter dwMSREI increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwMSFEES.

85.17 C901790016 Multiplex Section Remote Severely Errored Second

Description
When peer end device detects BIP-24 error according to the received three B2 bytes, it uses regenerator section overhead byte M1 to send the check result to the local end as Multiplex Section-Remote Error Indication (MS-REI). When one second contains no less than 30% error blocks or at least one deficiency, it is deemed as SES.

Measurement Point
Because at most 24 bit errors can be found, the value range of M1 byte is 0 ~ 24. If M1 is not 0, it indicates that a remote error block exists. Multiplex Section-Remote Error Indication counter dwMSREI increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwMSFESES.

85-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

85.18 C901790017 Multiplex Section Remote Unavailable Second

Description
When peer end device detects BIP-24 error according to the received three B2 bytes, it uses regenerator section overhead byte M1 to send the check result to the local end as Multiplex Section-Remote Error Indication (MS-REI). When SES is detected for continuous 10 seconds, UAS starts (UAS includes these 10 seconds). When no SES is detected for continuous 10 seconds, UAS ends (UAD excludes these 10 seconds).

Measurement Point
Because at most 24 bit errors can be found, the value range of M1 byte is 0 ~ 24. If M1 is not 0, it indicates that a remote error block exists. Multiplex Section-Remote Error Indication counter dwMSREI increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwMSFEUAS.

85.19 C901790018 VC-4 Remote Background Block Error Ratio (High-order path 1)
Description
When peer end device detects BIP-8 error according to the received B3 byte, it uses bit1 ~ bit4 of VC-4 POH byte G1 to send the check result to the local end as VC-4 path-Remote Error Indication (VC4-REI). Background block error (BBE) refers to the error blocks after deducting the unusable time and the error blocks appearing in the SES period. The ratio between the BBE numbers and total block numbers after deducting the unusable time and all the blocks during the SES period is called background block error rate (BBER). When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.

Measurement Point
Because at most eight bit errors can be found, the value range of VC4-REI is 0 ~ 8. If VC4-REI is not 0, it indicates that a remote error block exists. VC-4 path-Remote Error Indication counter dwVC4REI increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwVC4FEBBER1.

85-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 85 SDTB Fiber Performance Statistics

85.20 C901790019 VC-4 Remote Background Block Error Ratio (High-order path 2)
Description
This counter is similar to dwVC4FEBBER1. It corresponds to high-order path 2. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2.

Measurement Point
This counter is similar to dwVC4FEBBER1. It corresponds to high-order path 2.

85.21 C901790020 VC-4 Remote Background Block Error Ratio (High-order path 3)
Description
This counter is similar to dwVC4FEBBER2. It corresponds to high-order path 3.

Measurement Point
This counter is similar to dwVC4FEBBER2. It corresponds to high-order path 3.

85.22 C901790021 VC-4 Remote Errored Second Ratio (High-order path 1)

Description
When peer end device detects BIP-8 error according to the received B3 byte, it uses bit1 ~ bit4 of VC-4 POH byte G1 to send the check result to the local end as VC-4 path-Remote Error Indication (VC4-REI). The ratio between the ES within a specified period of measurement time and the total time used is called error code second ratio (ESR). When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.

Measurement Point
Because at most eight bit errors can be found, the value range of VC4-REI is 0 ~ 8. If VC4-REI is not 0, it indicates that a remote error block exists. VC-4 path-Remote Error Indication counter dwVC4REI increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwVC4FEER1.

85-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

85.23 C901790022 VC-4 Remote Errored Second Ratio (High-order path 2)

Description
This counter is similar to dwVC4FEER1. It corresponds to high-order path 2. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2.

Measurement Point
This counter is similar to dwVC4FEER1. It corresponds to high-order path 2.

85.24 C901790023 VC-4 Remote Errored Second Ratio (High-order path 3)

Description
This counter is similar to dwVC4FEER2. It corresponds to high-order path 3.

Measurement Point
This counter is similar to dwVC4FEER2. It corresponds to high-order path 3.

85.25 C901790024 VC-4 Remote Errored Second (High-order path 1)

Description
When peer end device detects BIP-8 error according to the received B3 byte, it uses bit1 ~ bit4 of VC-4 POH byte G1 to send the check result to the local end as VC-4 path-Remote Error Indication (VC4-REI). When one second has one or more error blocks or at least one deficiency, it is called an Error Second (ES). When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.

Measurement Point
Because at most eight bit errors can be found, the value range of VC4-REI is 0 ~ 8. If VC4-REI is not 0, it indicates that a remote error block exists. VC-4 path-Remote Error Indication counter dwVC4REI increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwVC4FEES1.

85-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 85 SDTB Fiber Performance Statistics

85.26 C901790025 VC-4 Remote Errored Second (High-order path 2)

Description
This counter is similar to dwVC4FEES1. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2.

Measurement Point
This counter is similar to dwVC4FEES1. It corresponds to high-order path 2.

85.27 C901790026 VC-4 Remote Errored Second (High-order path 3)

Description
This counter is similar to dwVC4FEES2. It corresponds to high-order path 3.

Measurement Point
This counter is similar to dwVC4FEES2. It corresponds to high-order path 3.

85.28 C901790027 VC-4 Remote Severely Errored Second (High-order path 1)

Description
When peer end device detects BIP-8 error according to the received B3 byte, it uses bit1 ~ bit4 of VC-4 POH byte G1 to send the check result to the local end as VC-4 path-Remote Error Indication (VC4-REI). When one second contains no less than 30% error blocks or at least one deficiency, it is deemed as SES. When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.

Measurement Point
Because at most eight bit errors can be found, the value range of VC4-REI is 0 ~ 8. If VC4-REI is not 0, it indicates that a remote error block exists. VC-4 path-Remote Error Indication counter dwVC4REI increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwVC4FESES1.

85-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

85.29 C901790028 VC-4 Remote Severely Errored Second (High-order path 2)

Description
This counter is similar to dwVC4FESES1. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2.

Measurement Point
This counter is similar to dwVC4FESES1. It corresponds to high-order path 2.

85.30 C901790029 VC-4 Remote Severely Errored Second (High-order path 3)

Description
This counter is similar to dwVC4FESES2. It corresponds to high-order path 3.

Measurement Point
This counter is similar to dwVC4FESES2. It corresponds to high-order path 3.

85.31 C901790030 VC-4 Remote Unavailable Second (High-order path 1)

Description
When peer end device detects BIP-8 error according to the received B3 byte, it uses bit1 ~ bit4 of VC-4 POH byte G1 to send the check result to the local end as VC-4 path-Remote Error Indication (VC4-REI). When SES is detected for continuous 10 seconds, UAS starts (UAS includes these 10 seconds). When no SES is detected for continuous 10 seconds, UAS ends (UAD excludes these 10 seconds). When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.

Measurement Point
Because at most eight bit errors can be found, the value range of VC4-REI is 0 ~ 8. If VC4-REI is not 0, it indicates that a remote error block exists. VC-4 path-Remote Error Indication counter dwVC4REI increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwVC4FEUAS1.

85-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 85 SDTB Fiber Performance Statistics

85.32 C901790031 VC-4 Remote Unavailable Second (High-order path 2)

Description
This counter is similar to dwVC4FEUAS1. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2.

Measurement Point
This counter is similar to dwVC4FEUAS1. It corresponds to high-order path 2.

85.33 C901790032 VC-4 Remote Unavailable Second (High-order path 3)

Description
This counter is similar to dwVC4FEUAS2. It corresponds to high-order path 3.

Measurement Point
This counter is similar to dwVC4FEUAS2. It corresponds to high-order path 3.

85.34 C901790033 B1(Regenerator Section) BIP-8 Background Block Error Ratio

Description
Regeneration section overhead byte B1 is used as the BIP code to monitor bit errors of regeneration section. Background block error (BBE) refers to the error blocks after deducting the unusable time and the error blocks appearing in the SES period. The ratio between the BBE numbers and total block numbers after deducting the unusable time and all the blocks during the SES period is called background block error rate (BBER).

Measurement Point
When the received B1 byte is verified to be inconsistent with the result of BIP-8 check for regenerator section of previous STM-1 frame at local end, the block is assumed to have error. Generator section BIP code counter dwB1E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB1BBER.

85-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

85.35 C901790034 B1(Regenerator Section) BIP-8 Errored Second Ratio

Description
Regeneration section overhead byte B1 is used as the BIP code to monitor bit errors of regeneration section. The ratio between the ES within a specified period of measurement time and the total time used is called error code second ratio (ESR).

Measurement Point
When the received B1 byte is verified to be inconsistent with the result of BIP-8 check of regenerator section of previous STM-1 frame at local end, the block is assumed to have error. Generator section BIP code counter dwB1E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB1ER.

85.36 C901790035 B1(Regenerator Section) BIP-8 Errored Second

Description
Regeneration section overhead byte B1 is used as the BIP code to monitor bit errors of regeneration section. When one second has one or more error blocks or at least one deficiency, it is called an Error Second (ES).

Measurement Point
When the received B1 byte is verified to be inconsistent with the result of BIP-8 check for regenerator section of previous STM-1 frame at local end, the block is assumed to have error. Generator section BIP code counter dwB1E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB1ES.

85.37 C901790036 B1(Regenerator Section) BIP-8 Severely Errored Second

Description
Regeneration section overhead byte B1 is used as the BIP code to monitor bit errors of regeneration section. When one second contains no less than 30% error blocks or at least one deficiency, it is deemed as SES.

Measurement Point
When the received B1 byte is verified to be inconsistent with the result of BIP-8 check for regenerator section of previous STM-1 frame at local end, the block is assumed to have
85-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 85 SDTB Fiber Performance Statistics

error. Generator section BIP code counter dwB1E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB1SES.

85.38 C901790037 B1(Regenerator Section) BIP-8 Unavailable Second

Description
Regeneration section overhead byte B1 is used as the BIP code to monitor bit errors of regeneration section. When SES is detected for continuous 10 seconds, UAS starts (UAS includes these 10 seconds). When no SES is detected for continuous 10 seconds, UAS ends (UAD excludes these 10 seconds).

Measurement Point
When the received B1 byte is verified to be inconsistent with the result of BIP-8 check for regenerator section of previous STM-1 frame at local end, the block is assumed to have error. Generator section BIP code counter dwB1E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB1UAS

85.39 C901790038 B2(Multiplex Section) BIP-24 Background Block Error Ratio

Description
Three multiplex section overhead byte B2s are used as the BIP code to monitor bit errors of multiplex section. Background block error (BBE) refers to the error blocks after deducting the unusable time and the error blocks appearing in the SES period. The ratio between the BBE numbers and total block numbers after deducting the unusable time and all the blocks during the SES period is called background block error rate (BBER).

Measurement Point
When the received three B2 bytes are verified to be inconsistent with the result of BIP-24 check for multiplex section of previous STM-1 frame at local end, the block is assumed to have error. Muliplex section BIP code counter dwB2E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB2BBER.

85-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

85.40 C901790039 B2(Multiplex Section) BIP-24 Errored Second Ratio

Description
Three multiplex section overhead byte B2s are used as the BIP code to monitor bit errors of multiplex section. The ratio between the ES within a specified period of measurement time and the total time used is called error code second ratio (ESR).

Measurement Point
When the received three B2 bytes are verified to be inconsistent with the result of BIP-24 check for multiplex section of previous STM-1 frame at local end, the block is assumed to have error. Muliplex section BIP code counter dwB2E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB2ER.

85.41 C901790040 B2(Multiplex Section) BIP-24 Errored Second

Description
Three multiplex section overhead byte B2s are used as the BIP code to monitor bit errors of multiplex section. When one second has one or more error blocks or at least one deficiency, it is called an Error Second (ES).

Measurement Point
When the received three B2 bytes are verified to be inconsistent with the result of BIP-24 check for multiplex section of previous STM-1 frame at local end, the block is assumed to have error. Muliplex section BIP code counter dwB2E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB2ES.

85.42 C901790041 B2(Multiplex Section) BIP-24 Severely Errored Second

Description
Three multiplex section overhead byte B2s are used as the BIP code to monitor bit errors of multiplex section. When one second contains no less than 30 error blocks or at least one deficiency, it is deemed as SES.

Measurement Point
When the received three B2 bytes are verified to be inconsistent with the result of BIP-24 check for multiplex section of previous STM-1 frame at local end, the block is assumed
85-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 85 SDTB Fiber Performance Statistics

to have error. Muliplex section BIP code counter dwB2E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB2SES.

85.43 C901790042 B2(Multiplex Section) BIP-24 Unavailable Second

Description
Three multiplex section overhead byte B2s are used as the BIP code to monitor bit errors of multiplex section. When SES is detected for continuous 10 seconds, UAS starts (UAS includes these 10 seconds). When no SES is detected for continuous 10 seconds, UAS ends (UAD excludes these 10 seconds).

Measurement Point
When the received three B2 bytes are verified to be inconsistent with the result of BIP-24 check for the multiplex section of previous STM-1 frame at local end, the block is assumed to have error. Muliplex section BIP code counter dwB2E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB2UAS.

85.44 C901790043 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 1)
Description
VC-4 POH byte B3 is used as the BIP code to monitor bit errors of VC-4 path. Background block error (BBE) refers to the error blocks after deducting the unusable time and the error blocks appearing in the SES period. The ratio between the BBE numbers and total block numbers after deducting the unusable time and all the blocks during the SES period is called background block error rate (BBER). When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.

Measurement Point
When the B3 byte received by high-order path 1 is verified to be inconsistent with the result of BIP-8 check for VC-4 block of previous STM-1 frame at local end, the block is assumed to have error. VC-4 path BIP code counter dwB3E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB3BBER1.

85-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

85.45 C901790044 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 2)
Description
This counter is similar to dwB3BBER1. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2.

Measurement Point
This counter is similar to dwB3BBER1. It corresponds to high-order path 2.

85.46 C901790045 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 3)
Description
This counter is similar to dwB3BBER2. It corresponds to high-order path 3.

Measurement Point
This counter is similar to dwB3BBER2. It corresponds to high-order path 3.

85.47 C901790046 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 1)

Description
VC-4 POH byte B3 is used as the BIP code to monitor bit errors of VC-4 path. The ratio between the ES within a specified period of measurement time and the total time used is called error code second ratio (ESR). When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.

Measurement Point
When the B3 byte received by high-order path 1 is verified to be inconsistent with the result of BIP-8 check for the VC-4 block of previous STM-1 frame at local end through, the block is assumed to have error. VC-4 path BIP code counter dwB3E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB3ER1.

85-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 85 SDTB Fiber Performance Statistics

85.48 C901790047 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 2)

Description
This counter is similar to dwB3ER1. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2.

Measurement Point
This counter is similar to dwB3ER1. It corresponds to high-order path 2.

85.49 C901790048 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 3)

Description
This counter is similar to dwB3ER2. It corresponds to high-order path 3.

Measurement Point
This counter is similar to dwB3ER2. It corresponds to high-order path 3.

85.50 C901790049 B3(VC-4) BIP-8 Errored Second (High-order path 1)

Description
VC-4 POH byte B3 is used as the BIP code to monitor bit errors of VC-4 path. When one second has one or more error blocks or at least one deficiency, it is called an Error Second (ES). When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.

Measurement Point
When the B3 byte received by high-order path 1 is verified to be inconsistent with the result of BIP-8 check for the VC-4 block of previous STM-1 frame at local end, the block is assumed to have error. VC-4 path BIP code counter dwB3E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB3ES1.

85-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

85.51 C901790050 B3(VC-4) BIP-8 Errored Second (High-order path 2)

Description
This counter is similar to dwB3ES1. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2.

Measurement Point
This counter is similar to dwB3ES1. It corresponds to high-order path 2.

85.52 C901790051 B3(VC-4) BIP-8 Errored Second (High-order path 3)

Description
This counter is similar to dwB3ES2. It corresponds to high-order path 3.

Measurement Point
This counter is similar to dwB3ES2. It corresponds to high-order path 3.

85.53 C901790052 B3(VC-4) BIP-8 Severely Errored Second (High-order path 1)

Description
VC-4 POH byte B3 is used as the BIP code to monitor bit errors of VC-4 path. When one second contains no less than 30% error blocks or at least one deficiency, it is deemed as SES. When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.

Measurement Point
When the B3 byte received by high-order path 1 is verified to be inconsistent with the result of BIP-8 check for the VC-4 block of previous STM-1 frame at local end, the block is assumed to have error. VC-4 path BIP code counter dwB3E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB3SES1.

85-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 85 SDTB Fiber Performance Statistics

85.54 C901790053 B3(VC-4) BIP-8 Severely Errored Second (High-order path 2)

Description
This counter is similar to dwB3SES1. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2.

Measurement Point
This counter is similar to dwB3SES1. It corresponds to high-order path 2.

85.55 C901790054 B3(VC-4) BIP-8 Severely Errored Second (High-order path 3)

Description
This counter is similar to dwB3SES2. It corresponds to high-order path 3.

Measurement Point
This counter is similar to dwB3SES2. It corresponds to high-order path 3.

85.56 C901790055 B3(VC-4) BIP-8 Unavailable Second (High-order path 1)

Description
VC-4 POH byte B3 is used as the BIP code to monitor bit errors of VC-4 path. When SES is detected for continuous 10 seconds, UAS starts (UAS includes these 10 seconds). When no SES is detected for continuous 10 seconds, UAS ends (UAD excludes these 10 seconds). When SDH type is AU-4, AU-3, and STS-3, the corresponding high-order path is 1.

Measurement Point
When the B3 byte received by high-order path 1 is verified to be inconsistent with the result of BIP-8 check for VC-4 block of previous STM-1 frame at local end, the block is assumed to have error. VC-4 path BIP code counter dwB3E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB3UAS1.

85-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

85.57 C901790056 B3(VC-4) BIP-8 Unavailable Second (High-order path 2)

Description
This counter is similar to dwB3UAS1. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2.

Measurement Point
This counter is similar to dwB3UAS1. It corresponds to high-order path 2.

85.58 C901790057 B3(VC-4) BIP-8 Unavailable Second (High-order path 3)

Description
This counter is similar to dwB3UAS2. It corresponds to high-order path 3.

Measurement Point
This counter is similar to dwB3UAS2. It corresponds to high-order path 3.

85.59 C901790058 LOF second

Description
This counter counts the seconds of LOF. The statistic result is 0 if it is not temporally used.

Measurement Point
This counter counts when LOF occurs and does not stop until LOF restores.

85-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 86

PEB22554 E1 Performance Statistics

Table of Contents
Overview ..................................................................................................................86-1 C901800001 Frame type..........................................................................................86-2 C901800002 slip Duration .......................................................................................86-2 C901800003 Near end available Second .................................................................86-2 C901800004 Near end unavailable Second..............................................................86-3 C901800005 Near end Errored Second....................................................................86-3 C901800006 Near end Severely Errored Second .....................................................86-3 C901800007 Near end Background Block Error .......................................................86-4 C901800008 Frame Alignment Signal error..............................................................86-4 C901800009 Cyclic Redundancy Check 4 error .......................................................86-4 C901800010 Bit error rate(PPM) ..............................................................................86-4 C901800011 Near end unavailable Second rate(One ten-thousandth)......................86-5 C901800012 Near end Errored Second rate(One ten-thousandth) ...........................86-5 C901800013 Near end Severely Errored Second rate(One ten-thousandth).............86-5 C901800014 Near end Background Block Error rate ................................................86-6 C901800015 far end available Second .....................................................................86-6 C901800016 far end unavailable Second .................................................................86-6 C901800017 far end Errored Second .......................................................................86-7 C901800018 far end Severely Errored Second.........................................................86-7 C901800019 far end Background Block Error...........................................................86-7 C901800020 E-Bit ERROR ......................................................................................86-8 C901800021 far end unavailable Second rate(One ten-thousandth).........................86-8 C901800022 far end Errored Second rate(One ten-thousandth)...............................86-8 C901800023 far end Severely Errored Second rate(One ten-thousandth) ................86-9 C901800024 far end Background Block Error rate(One ten-thousandth) ..................86-9

86.1 Overview
The statistic task of PEB22554 module E1 performance collects the statistics on the number of error codes generated in receiving signals of PEB22554 module during transmission on different network links. It is used to represent the data transmission performance of E1 signal in various sections and paths of transport network. This chapter describes the main performance statistic items, statistic method, and standard compliance of PEB22554 module.
86-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

PEB22554 module is a digital trunk access chip. It can connect the transport network as standard E1 port at line side. The system side provides four E1s to bear services such as IMA for the system. The performance statistic items of PEB22554 module in E1 mode include FAS error, CRC error, and E-bit error. The statistic method is as follows: query the number of error blocks of receiving end signals at the interval of 1S, and handle the error events in accordance with ITU-T G.826 standard.

86.2 C901800001 Frame type

Description
There are two frame types: basic frame and multi-frame. Basic frame: dual frame. Multi-frame: CRC, CAS, CAS with CRC, forced multi-frame, and no frame.

86.3 C901800002 slip Duration

Description
This counter counts the duration of code slip during detection period. Code slip occurs when receiving clock and transmitting clock are insynchronous.

Measurement Point
This counter counts the duration of code slip.

Unit
Second

86.4 C901800003 Near end available Second

Description
This counter counts the time available at near end, that is, the result of excluding UAS from total detection period.

Measurement Point
This counter counts the available seconds at near end.

Unit
Second

86-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 86 PEB22554 E1 Performance Statistics

86.5 C901800004 Near end unavailable Second

Description
If 10 consecutive near end SESs occur, the link is regarded to be unavailable (UAS). The ten seconds are counted as unavailable seconds. The link is regarded to be recovered if no near end SES occurs in 10 consecutive seconds. These ten seconds are counted as unavailable seconds.

Measurement Point
This counter counts the unavailable seconds at near end.

Unit
Second

86.6 C901800005 Near end Errored Second

Description
This counter increments each second near end detects LOF, LOS, AIS alarm, and FAS error when link is available. For multi-frame, this counter also counts the number of CRC-4 error blocks. If there is one or more CRC-4 errors within a second, this counter increments.

Measurement Point
This counter counts the errored seconds at near end.

Unit
Second

86.7 C901800006 Near end Severely Errored Second

Description
This counter increments each second near end detects LOF, LOS, AIS alarm, and FAS (FAS>=26) error when link is available. For multi-frame, this counter also counts the number of CRC-4 error blocks. If there is more than 805 CRC-4 errors within a second, this counter increments.

Measurement Point
When severely errored seconds at near end are detected, this counter counts.

86-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Second

86.8 C901800007 Near end Background Block Error

Description
This counter counts the accumulation of CRC and FAS error counter at each second. If a second is determined to be SES and UAS, it is not counted.

Measurement Point
When near end background block error occurs, this counter counts. The basic frame is invalid and thus use 0.

Unit
Second

86.9 C901800008 Frame Alignment Signal error

Description
This counter counts the number of FAS errors during the specified period.

Measurement Point
When FAS error is detected, this counter counts.

86.10 C901800009 Cyclic Redundancy Check 4 error

Description
This counter counts the number of CRC4 errors during the specified period.

Measurement Point
When CRC4 error is detected, this counter counts.

86.11 C901800010 Bit error rate(PPM)

Description
For details, see the formula under the table.

86-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 86 PEB22554 E1 Performance Statistics

Measurement Point
This counter counts the number of errored codes.

Unit
PPM

86.12 C901800011 Near end unavailable Second rate(One ten-thousandth)

Description
For details, see the formula under the table.

Measurement Point
When unavailable seconds are detected at near end, this counter counts.

Unit
Ten-thousandth

86.13 C901800012 Near end Errored Second rate(One ten-thousandth)

Description
For details, see the formula under the table.

Measurement Point
When errored seconds are detected at near end, this counter counts.

Unit
Ten-thousandth

86.14 C901800013 Near end Severely Errored Second rate(One ten-thousandth)

Description
For details, see the formula under the table.

86-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When severely errored seconds at near end are detected, this counter counts.

Unit
Ten-thousandth

86.15 C901800014 Near end Background Block Error rate

Description
For details, see the formula under the table.

Measurement Point
When background block error is detected at near end, this counter counts.

86.16 C901800015 far end available Second

Description
This counter counts the time available at far end, that is, the result of excluding UAS from total detection period.

Measurement Point
This counter counts the available seconds at far end.

Unit
Second

86.17 C901800016 far end unavailable Second

Description
If 10 consecutive far end SESs occur, the link is regarded to be unavailable (UAS). The ten seconds are counted as unavailable seconds. The link is regarded to be recovered if no far end SES occurs in 10 consecutive seconds. These ten seconds are counted as unavailable seconds.

Measurement Point
When unavailable seconds are detected at far end, this counter counts.
86-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 86 PEB22554 E1 Performance Statistics

Unit
Second

86.18 C901800017 far end Errored Second

Description
This counter increments each second near end detects RAI alarm and EBIT error when link is available.

Measurement Point
When errored seconds are detected at far end, this counter counts.

Unit
Second

86.19 C901800018 far end Severely Errored Second

Description
This counter increments each second far end detects RAI alarm and EBIT (EBIT>=805) error when link is available.

Measurement Point
When severely errored seconds are detected at far end, this counter counts.

Unit
Second

86.20 C901800019 far end Background Block Error

Description
This counter counts the accumulation of EBIT error counter at each second. If a second is determined to be SES and UAS, it is not counted.

Measurement Point
When far end background block errors are detected, this counter counts.

86-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

86.21 C901800020 E-Bit ERROR

Description
This counter counts the times of sub-frame errors in multi-frame during the detection period.

Measurement Point
When EBIT error is detected, this counter counts.

Unit
Times

86.22 C901800021 far end unavailable Second rate(One ten-thousandth)

Description
For details, see the formula under the table.

Measurement Point
When unavailable seconds are detected at far end, this counter counts.

Unit
Ten-thousandth

86.23 C901800022 far end Errored Second rate(One ten-thousandth)

Description
For details, see the formula under the table.

Measurement Point
When errored seconds are detected at far end, this counter counts.

Unit
Ten-thousandth

86-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 86 PEB22554 E1 Performance Statistics

86.24 C901800023 far end Severely Errored Second rate(One ten-thousandth)

Description
For details, see the formula under the table.

Measurement Point
When severely errored seconds are detected at far end, this counter counts.

Unit
Ten-thousandth

86.25 C901800024 far end Background Block Error rate(One ten-thousandth)

Description
For details, see the formula under the table.

Measurement Point
When background block error is detected at far end, this counter counts.

Unit
Ten-thousandth

86-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

86-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 87

PEB22554 T1 Performance Statistics

Table of Contents
Overview ..................................................................................................................87-1 C901810001 Frame type..........................................................................................87-2 C901810002 slip Duration .......................................................................................87-2 C901810003 Near end available Second .................................................................87-2 C901810004 Near end unavailable Second..............................................................87-2 C901810005 Near end Errored Second....................................................................87-3 C901810006 Near end Severely Errored Second ....................................................87-3 C901810007 number of Near end Background Block Error ......................................87-3 C901810008 number of Frame Alignment Signal error .............................................87-4 C901810009 number of Cyclic Redundancy Check 6 error.......................................87-4 C901810010 Bit error rate (PPM) .............................................................................87-4 C901810011 Near end unavailable Second rate(One ten-thousandth)......................87-4 C901810012 Near end Errored Second rate (One ten-thousandth) ..........................87-5 C901810013 Near end Severely Errored Second rate(One ten-thousandth) ............87-5 C901810014 Near end Background Block Error rate ................................................87-5

87.1 Overview
The statistic task of PEB22554 module T1 performance collects the statistics on the number of error codes generated in receiving signals of PEB22554 module during transmission on different network links. It is used to represent the data transmission performance of T1 signal in various sections and paths of transport network. This chapter describes the main performance statistic items, statistic method, and standard compliance of PEB22554 module in T1 mode. PEB22554 module is a digital trunk access chip. It can connect the transport network as standard T1 port at line side. The system side provides four T1s to bear services such as IMA for the system. The performance statistic items of PEB22554 module in T1 mode include FAS error and CRC error. The statistic method is as follows: query the number of error blocks of receiving end signals at the interval of 1s, and handle the error events in accordance with ITU-T G.826 standard.

87-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

87.2 C901810001 Frame type

Description
There are two frame types: basic frame and multi-frame. l l l l l 1 2 3 4 5 F24 (ESF) without CRC6 F24 (ESF) with CRC6 F12 (SF) F4 F72

87.3 C901810002 slip Duration

Description
This counter counts the duration of code slip during detection period. Code slip occurs when receiving clock and transmitting clock are insynchronous.

Measurement Point
This counter counts the duration of code slip.

Unit
Second

87.4 C901810003 Near end available Second

Description
This counter counts the time available at near end, that is, the result of excluding UAS from total detection period.

Measurement Point
This counter counts the available seconds at near end.

87.5 C901810004 Near end unavailable Second

Description
If 10 consecutive near end SESs occur, the link is regarded to be unavailable (UAS). The ten seconds are counted as unavailable seconds. The link is regarded to be recovered if no near end SES occurs in 10 consecutive seconds. These ten seconds are counted as unavailable seconds.
87-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 87 PEB22554 T1 Performance Statistics

Measurement Point
When unavailable seconds are detected at near end, this counter counts.

87.6 C901810005 Near end Errored Second

Description
This counter increments each second near end detects LOF, LOS, AIS, RAI alarm, and FAS error when link is available. If CRC is available, this counter counts the number of CRC-6 error blocks. If there is one or more CRC-6 errors within a second, this counter increments.

Measurement Point
When errored seconds are detected at near end, this counter counts.

87.7 C901810006 Near end Severely Errored Second

Description
This counter increments each second near end detects LOF, LOS, AIS, RAI alarm, and FAS (FAS>=26) error when link is available. For F24 (ESF) with CRC6 format, this counter also counts the number of CRC-4 error blocks. If there is more than 805 CRC-4 errors within a second, this counter increments.

Measurement Point
When severely errored seconds at near end are detected, this counter counts.

87.8 C901810007 number of Near end Background Block Error

Description
This counter counts the accumulation of CRC and FAS error counter at each second. If a second is determined to be SES and UAS, it is not counted.

Measurement Point
When near end background block errors are detected, this counter counts.

87-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

87.9 C901810008 number of Frame Alignment Signal error

Description
This counter counts the number of FAS errors during the specified period.

Measurement Point
When FAS error is detected, this counter counts.

87.10 C901810009 number of Cyclic Redundancy Check 6 error

Description
This counter counts the number of CRC6 errors during the specified period.

Measurement Point
When CRC6 error is detected, this counter counts.

87.11 C901810010 Bit error rate (PPM)

Description
See the formula.

Measurement Point
This counter counts the number of errored codes.

Unit
PPM

87.12 C901810011 Near end unavailable Second rate(One ten-thousandth)

Description
See the formula.

Measurement Point
When unavailable seconds are detected at near end, this counter counts.
87-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 87 PEB22554 T1 Performance Statistics

Unit
Ten-thousandth

87.13 C901810012 Near end Errored Second rate (One ten-thousandth)

Description
See the formula.

Measurement Point
When errored seconds are detected at near end, this counter counts.

Unit
Ten-thousandth

87.14 C901810013 Near end Severely Errored Second rate(One ten-thousandth)

Description
See the formula.

Measurement Point
When severely errored seconds at near end are detected, this counter counts.

Unit
Ten-thousandth

87.15 C901810014 Near end Background Block Error rate

Description
See the formula.

Measurement Point
When background block errors are detected at near end, this counter counts.

87-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

87-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 88

MAC Port Flow Statistics

Table of Contents
Overview ..................................................................................................................88-1 C901820001 receive bytes number (high 4 bytes) ....................................................88-1 C901820002 receive bytes number (low 4 bytes) .....................................................88-2 C901820003 transmit bytes number (high 4 bytes)...................................................88-2 C901820004 transmit bytes number (low 4 bytes) ....................................................88-3 C901820005 physical band width .............................................................................88-3 C901820006 mean receiving bit rate ........................................................................88-4 C901820007 max receiving bit rate ..........................................................................88-4 C901820008 mean transmitting bit rate ....................................................................88-4 C901820009 max transmitting bit rate ......................................................................88-5 C901820010 Number of packets discarded at RX side (high 4 bytes).......................88-5 C901820011 Number of packets discarded at RX side (low 4 bytes) ........................88-6 C901820012 Number of packets discarded at TX side (high 4 bytes) .......................88-6 C901820013 Number of packets discarded at TX side (low 4 bytes) ........................88-6 C901820014 Number of packets received when receiving bit rate is max during performance period ..................................................................................................88-7 C901820015 Number of packets sent when sending bit rate is max during performance period ..................................................................................................88-7

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

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

88-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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.

Unit
BYTE

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

Unit
BYTE

88.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, 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 transmitted at the port.
88-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 88 MAC Port Flow Statistics

Unit
BYTE

88.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
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 transmitted at the port.

Unit
BYTE

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

88-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

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

88.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
The counter's value is calculated when the data is reported.

Unit
bit/s

88.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
88-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 88 MAC Port Flow Statistics

Usage
This counter is used to find out the average transmitting rate at the port.

Measurement Point
The counter's value is calculated when the data is reported.

Unit
bit/s

88.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
The counter's value is calculated when the data is reported.

Unit
bit/s

88.11 C901820010 Number of packets discarded at RX side (high 4 bytes)

Description
This counter counts the number of packets discarded at the receiving end (higher 4 bytes).

Usage
This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when the discarded packet is received at the port.

88-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

88.12 C901820011 Number of packets discarded at RX side (low 4 bytes)

Description
This counter counts the number of packets discarded at the receiving end (lower 4 bytes).

Usage
This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when the discarded packet is received at the port.

88.13 C901820012 Number of packets discarded at TX side (high 4 bytes)

Description
This counter counts the number of packets discarded at the transmitting end (higher 4 bytes).

Usage
This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when the discarded packet is transmitted at the port.

88.14 C901820013 Number of packets discarded at TX side (low 4 bytes)

Description
This counter counts the number of packets discarded at the transmitting end (lower 4 bytes).

Usage
This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when the discarded packet is transmitted at the port.
88-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 88 MAC Port Flow Statistics

88.15 C901820014 Number of packets received when receiving bit rate is max during performance period
Description
This counter counts the number of packets received at the peak rate of the port.

Usage
This counter is supported in version V6.20.61 or later.

Measurement Point
Sampling is performed every second. Compare the receiving rate with the peak rate, and the number of received packets of corresponding measurement points is recorded in the counter.

88.16 C901820015 Number of packets sent when sending bit rate is max during performance period
Description
This counter counts the number of packets sent at the peak rate of the port.

Usage
This counter is supported in version V6.20.61 or later.

Measurement Point
Sampling is performed every second. Compare the sending rate with the peak rate, and the number of sent packets of corresponding measurement points is recorded in the counter.

88-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

88-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89

AMR Rate Statistics

Table of Contents
Overview ..................................................................................................................89-2 C901830001 Total Num of DL AFS12.2k frame ........................................................89-3 C901830002 Total Num of DL AFS10.2k frame ........................................................89-4 C901830003 Total Num of DL AFS7.95k frame ........................................................89-4 C901830004 Total Num of DL AFS7.40k frame ........................................................89-5 C901830005 Total Num of DL AFS6.70k frame ........................................................89-5 C901830006 Total Num of DL AFS5.90k frame ........................................................89-6 C901830007 Total Num of DL AFS5.15k frame ........................................................89-6 C901830008 Total Num of DL AFS4.75k frame ........................................................89-7 C901830009 Total Num of DL AHS7.95k frame........................................................89-7 C901830010 Total Num of DL AHS7.40k frame........................................................89-8 C901830011 Total Num of DL AHS6.70k frame ........................................................89-8 C901830012 Total Num of DL AHS5.90k frame........................................................89-9 C901830013 Total Num of DL AHS5.15k frame........................................................89-9 C901830014 Total Num of DL AHS4.75k frame......................................................89-10 C901830015 Total Num of UL AFS12.2k frame ......................................................89-10 C901830016 Total Num of UL AFS10.2k frame ...................................................... 89-11 C901830017 Total Num of UL AFS7.95k frame ...................................................... 89-11 C901830018 Total Num of UL AFS7.40k frame ......................................................89-12 C901830019 Total Num of UL AFS6.70k frame ......................................................89-12 C901830020 Total Num of UL AFS5.90k frame ......................................................89-13 C901830021 Total Num of UL AFS5.15k frame ......................................................89-13 C901830022 Total Num of UL AFS4.75k frame ......................................................89-14 C901830023 Total Num of UL AHS7.95k frame......................................................89-14 C901830024 Total Num of UL AHS7.40k frame......................................................89-15 C901830025 Total Num of UL AHS6.70k frame......................................................89-15 C901830026 Total Num of UL AHS5.90k frame......................................................89-16 C901830027 Total Num of UL AHS5.15k frame......................................................89-16 C901830028 Total Num of UL AHS4.75k frame......................................................89-17 C901830029 Total Number of DL WFS12.65k Frame .............................................89-17 C901830030 Total Number of DL WFS8.85k Frame ...............................................89-18 C901830031 Total Number of DL WFS6.60k Frame ...............................................89-19 C901830032 Total Number of DL OWFS23.85k Frame ..........................................89-19 C901830033 Total Number of DL OWFS15.85k Frame ..........................................89-20 C901830034 Total Number of DL OWFS12.65k Frame ..........................................89-21 C901830035 Total Number of DL OWFS8.85k Frame ............................................89-21 C901830036 Total Number of DL OWFS6.60k Frame ............................................89-22
89-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901830037 Total Number of DL OWHS12.65k Frame ..........................................89-23 C901830038 Total Number of DL OWHS8.85k Frame............................................89-24 C901830039 Total Number of DL OWHS6.60k Frame............................................89-24 C901830040 Total Number of UL WFS12.65k Frame .............................................89-25 C901830041 Total Number of UL WFS8.85k Frame ...............................................89-26 C901830042 Total Number of UL WFS6.60k Frame ...............................................89-26 C901830043 Total Number of UL OWFS23.85k Frame ..........................................89-27 C901830044 Total Number of UL OWFS15.85k Frame ..........................................89-28 C901830045 Total Number of UL OWFS12.65k Frame ..........................................89-28 C901830046 Total Number of UL OWFS8.85k Frame ............................................89-29 C901830047 Total Number of UL OWFS6.60k Frame ............................................89-30 C901830048 Total Number of UL OWHS12.65k Frame ..........................................89-31 C901830049 Total Number of UL OWHS8.85k Frame............................................89-31 C901830050 Total Number of UL OWHS6.60k Frame............................................89-32

89.1 Overview
AMR rate statistics counts the total number of uplink/downlink frames of absolute rate at the cell level. AMR rate statistics at baseband counts the total number of uplink/downlink frames of absolute rate (coding frame) according to cells. The full-rate channel has 8 rates while the half-rate channel has 6 rates. Each carriers requires 28 counters. Figure 89-1 shows the AMR rate statistics flow.

89-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Figure 89-1 AMR Rate Statistics Report

89.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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Number of frames

89.3 C901830002 Total Num of DL AFS10.2k frame

Description
This counter counts the number of coding frames which adopt 10.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 10.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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.4 C901830003 Total Num of DL AFS7.95k frame

Description
This counter counts the number of coding frames which adopt 7.95 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 7.95 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Unit
Number of frames

89.5 C901830004 Total Num of DL AFS7.40k frame

Description
This counter counts the number of coding frames which adopt 7.40 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 7.40 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.6 C901830005 Total Num of DL AFS6.70k frame

Description
This counter counts the number of coding frames which adopt 6.70 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 6.70 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Number of frames

89.7 C901830006 Total Num of DL AFS5.90k frame

Description
This counter counts the number of coding frames which adopt 5.90 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 5.90 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.8 C901830007 Total Num of DL AFS5.15k frame

Description
This counter counts the number of coding frames which adopt 5.15 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 5.15 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Unit
Number of frames

89.9 C901830008 Total Num of DL AFS4.75k frame

Description
This counter counts the number of coding frames which adopt 4.75 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 4.75 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.10 C901830009 Total Num of DL AHS7.95k frame

Description
This counter counts the number of coding frames which adopt 7.95 k coding rate in 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Number of frames

89.11 C901830010 Total Num of DL AHS7.40k frame

Description
This counter counts the number of coding frames which adopt 7.40 k coding rate in downlink in AMR half-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 7.40 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.12 C901830011 Total Num of DL AHS6.70k frame

Description
This counter counts the number of coding frames which adopt 6.70 k coding rate in downlink in AMR half-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 6.70 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Unit
Number of frames

89.13 C901830012 Total Num of DL AHS5.90k frame

Description
This counter counts the number of coding frames which adopt 5.90 k coding rate in downlink in AMR half-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 5.90 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.14 C901830013 Total Num of DL AHS5.15k frame

Description
This counter counts the number of coding frames which adopt 5.15 k coding rate in downlink in AMR half-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 5.15 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Number of frames

89.15 C901830014 Total Num of DL AHS4.75k frame

Description
This counter counts the number of coding frames which adopt 4.75 k coding rate in downlink in AMR half-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 4.75 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Unit
Number of frames

89.17 C901830016 Total Num of UL AFS10.2k frame

Description
This counter counts the number of coding frames which adopt 10.2 k coding rate in uplink in AMR full-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 10.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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.18 C901830017 Total Num of UL AFS7.95k frame

Description
This counter counts the number of coding frames which adopt 7.95 k coding rate in uplink in AMR full-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 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Number of frames

89.19 C901830018 Total Num of UL AFS7.40k frame

Description
This counter counts the number of coding frames which adopt 7.40 k coding rate in uplink in AMR full-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 7.40 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.20 C901830019 Total Num of UL AFS6.70k frame

Description
This counter counts the number of coding frames which adopt 6.70 k coding rate in uplink in AMR full-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 6.70 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Unit
Number of frames

89.21 C901830020 Total Num of UL AFS5.90k frame

Description
This counter counts the number of coding frames which adopt 5.90 k coding rate in uplink in AMR full-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 5.90 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.22 C901830021 Total Num of UL AFS5.15k frame

Description
This counter counts the number of coding frames which adopt 5.15 k coding rate in uplink in AMR full-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 5.15 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Number of frames

89.23 C901830022 Total Num of UL AFS4.75k frame

Description
This counter counts the number of coding frames which adopt 4.75 k coding rate in uplink in AMR full-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 4.75 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.24 C901830023 Total Num of UL AHS7.95k frame

Description
This counter counts the number of coding frames which adopt 7.95 k coding rate in uplink 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Unit
Number of frames

89.25 C901830024 Total Num of UL AHS7.40k frame

Description
This counter counts the number of coding frames which adopt 7.40 k coding rate in uplink in AMR half-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 7.40 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.26 C901830025 Total Num of UL AHS6.70k frame

Description
This counter counts the number of coding frames which adopt 6.70 k coding rate in uplink in AMR half-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 6.70 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Number of frames

89.27 C901830026 Total Num of UL AHS5.90k frame

Description
This counter counts the number of coding frames which adopt 5.90 k coding rate in uplink in AMR half-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 5.90 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.28 C901830027 Total Num of UL AHS5.15k frame

Description
This counter counts the number of coding frames which adopt 5.15 k coding rate in uplink in AMR half-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 5.15 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.
89-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Unit
Number of frames

89.29 C901830028 Total Num of UL AHS4.75k frame

Description
This counter counts the number of coding frames which adopt 4.75 k coding rate in uplink in AMR half-rate channel service.

Usage
This counter is used to find out the number of coding frames which adopt 4.75 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. This counter is supported in version V6.20.200a or above.

Measurement Point
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically.

Unit
Number of frames

89.30 C901830029 Total Number of DL WFS12.65k Frame

Description
This counter counts downlink frames using WFS12.65k during FR-AMR-WB calls (FR speech version 5). It counts downlink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of downlink frames using WFS12.65k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-2.
89-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 89-2 Count of AMR-WB Frames

Unit
N/A

89.31 C901830030 Total Number of DL WFS8.85k Frame

Description
This counter counts downlink frames using WFS8.85k during FR-AMR-WB calls (FR speech version 5). It counts downlink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of downlink frames using WFS8.85k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-3.
Figure 89-3 Count of AMR-WB Frames

Unit
N/A

89-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

89.32 C901830031 Total Number of DL WFS6.60k Frame

Description
This counter counts downlink frames using WFS6.60k during FR-AMR-WB calls (FR speech version 5). It counts downlink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of downlink frames using WFS6.60k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-4.
Figure 89-4 Count of AMR-WB Frames

Unit
N/A

89.33 C901830032 Total Number of DL OWFS23.85k Frame

Description
This counter counts downlink frames using OWFS23.85k during FR-AMR-WB calls (FR speech version 4). It counts downlink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of downlink frames using OWFS23.85k.

89-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-5.
Figure 89-5 Count of AMR-WB Frames

Unit
N/A

89.34 C901830033 Total Number of DL OWFS15.85k Frame

Description
This counter counts downlink frames using OWFS15.85k during FR-AMR-WB calls (FR speech version 4). It counts downlink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of downlink frames using OWFS15.85k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-6.
Figure 89-6 Count of AMR-WB Frames

89-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Unit
N/A

89.35 C901830034 Total Number of DL OWFS12.65k Frame

Description
This counter counts downlink frames using OWFS12.65k during FR-AMR-WB calls (FR speech version 4). It counts downlink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of downlink frames using OWFS12.65k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-7.
Figure 89-7 Count of AMR-WB Frames

Unit
N/A

89.36 C901830035 Total Number of DL OWFS8.85k Frame

Description
This counter counts downlink frames using OWFS8.85k during FR-AMR-WB calls (FR speech version 4). It counts downlink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

89-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter indicates the number of downlink frames using OWFS8.85k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-8.
Figure 89-8 Count of AMR-WB Frames

Unit
N/A

89.37 C901830036 Total Number of DL OWFS6.60k Frame

Description
This counter counts downlink frames using OWFS6.60k during FR-AMR-WB calls (FR speech version 4). It counts downlink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of downlink frames using OWFS6.60k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-9.

89-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Figure 89-9 Count of AMR-WB Frames

Unit
N/A

89.38 C901830037 Total Number of DL OWHS12.65k Frame

Description
This counter counts downlink frames using OWHS12.65k during FR-AMR-WB calls (FR speech version 4). It counts downlink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of downlink frames using OWHS12.65k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-10.
Figure 89-10 Count of AMR-WB Frames

Unit
N/A

89-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

89.39 C901830038 Total Number of DL OWHS8.85k Frame

Description
This counter counts downlink frames using OWHS8.85k during FR-AMR-WB calls (FR speech version 4). It counts downlink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of downlink frames using OWHS8.85k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-11.
Figure 89-11 Count of AMR-WB Frames

Unit
N/A

89.40 C901830039 Total Number of DL OWHS6.60k Frame

Description
This counter counts downlink frames using OWHS6.60k during FR-AMR-WB calls (FR speech version 4). It counts downlink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of downlink frames using OWHS6.60k.

89-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-12.
Figure 89-12 Count of AMR-WB Frames

Unit
N/A

89.41 C901830040 Total Number of UL WFS12.65k Frame

Description
This counter counts uplink frames using WFS12.65k during FR-AMR-WB calls (FR speech version 5). It counts uplink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of uplink frames using WFS12.65k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-13.
Figure 89-13 Count of AMR-WB Frames

89-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
N/A

89.42 C901830041 Total Number of UL WFS8.85k Frame

Description
This counter counts uplink frames using WFS8.85k during FR-AMR-WB calls (FR speech version 5). It counts uplink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of uplink frames using WFS8.85k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-14.
Figure 89-14 Count of AMR-WB Frames

Unit
N/A

89.43 C901830042 Total Number of UL WFS6.60k Frame

Description
This counter counts uplink frames using WFS6.60k during FR-AMR-WB calls (FR speech version 5). It counts uplink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of uplink frames using WFS6.60k.

89-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-15.
Figure 89-15 Count of AMR-WB Frames

Unit
N/A

89.44 C901830043 Total Number of UL OWFS23.85k Frame

Description
This counter counts uplink frames using OWFS23.85k during FR-AMR-WB calls (FR speech version 4). It counts uplink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of uplink frames using OWFS23.85k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-16.
Figure 89-16 Count of AMR-WB Frames

89-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
N/A

89.45 C901830044 Total Number of UL OWFS15.85k Frame

Description
This counter counts uplink frames using OWFS15.85k during FR-AMR-WB calls (FR speech version 4). It counts uplink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of uplink frames using OWFS15.85k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-17.
Figure 89-17 Count of AMR-WB Frames

Unit
N/A

89.46 C901830045 Total Number of UL OWFS12.65k Frame

Description
This counter counts uplink frames using OWFS12.65k during FR-AMR-WB calls (FR speech version 4). It counts uplink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

89-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Usage
This counter indicates the number of uplink frames using OWFS12.65k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-18.
Figure 89-18 Count of AMR-WB Frames

Unit
N/A

89.47 C901830046 Total Number of UL OWFS8.85k Frame

Description
This counter counts uplink frames using OWFS8.85k during FR-AMR-WB calls (FR speech version 4). It counts uplink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of uplink frames using OWFS8.85k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-19.

89-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 89-19 Count of AMR-WB Frames

Unit
N/A

89.48 C901830047 Total Number of UL OWFS6.60k Frame

Description
This counter counts uplink frames using OWFS6.60k during FR-AMR-WB calls (FR speech version 4). It counts uplink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of uplink frames using OWFS6.60k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-20.
Figure 89-20 Count of AMR-WB Frames

Unit
N/A

89-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

89.49 C901830048 Total Number of UL OWHS12.65k Frame

Description
This counter counts uplink frames using OWHS12.65k during FR-AMR-WB calls (FR speech version 4). It counts uplink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of uplink frames using OWHS12.65k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-21.
Figure 89-21 Count of AMR-WB Frames

Unit
N/A

89.50 C901830049 Total Number of UL OWHS8.85k Frame

Description
This counter counts uplink frames using OWHS8.85k during FR-AMR-WB calls (FR speech version 4). It counts uplink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of uplink frames using OWHS8.85k.

89-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-22.
Figure 89-22 Count of AMR-WB Frames

Unit
N/A

89.51 C901830050 Total Number of UL OWHS6.60k Frame

Description
This counter counts uplink frames using OWHS6.60k during FR-AMR-WB calls (FR speech version 4). It counts uplink frames according to the message containing the information of AMR rate being used, which is reported by the BTS.

Usage
This counter indicates the number of uplink frames using OWHS6.60k.

Measurement Point
The OMS increments the corresponding counter according to the reported AMR rate each time an EV_AMR_RATE_USE_REPORT message is received. The measurement point is A, as shown in Figure 89-23.
Figure 89-23 Count of AMR-WB Frames

89-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 89 AMR Rate Statistics

Unit
N/A

89-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

89-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 90

PPP channel measurement

Table of Contents
C901840001 Received byte count............................................................................90-1 C901840002 Received packet count ........................................................................90-1 C901840003 Received framing aborts......................................................................90-2 C901840004 Received FCS errors...........................................................................90-2 C901840005 Received packets greater than maximum length .................................90-2 C901840006 Non-octet aligned frames received ......................................................90-3 C901840007 Received small datagrams discarded byte count .................................90-3 C901840008 Received jumbo packets byte count ....................................................90-3 C901840009 Received small datagrams discarded event count ...............................90-4 C901840010 Received jumbo packets count............................................................90-4 C901840011 Transmitted byte count ........................................................................90-4 C901840012 Transmitted packet count ....................................................................90-5 C901840013 Transmit framing aborts.......................................................................90-5 C901840014 MLPPP ID ...........................................................................................90-5 C901840015 PPP band width ..................................................................................90-5

90.1 C901840001 Received byte count

Description
The received byte count.

Measurement Point
when receiving data.

Unit
Byte

90.2 C901840002 Received packet count

Description
The received packet count.

90-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter adds one when receiving data.

Unit
Piece

90.3 C901840003 Received framing aborts

Description
The received framing aborts.

Measurement Point
The counter adds one when receive the broken frame.

Unit
Piece

90.4 C901840004 Received FCS errors

Description
The received FCS errors.

Measurement Point
The counter adds one when receiving the FCS error occurs.

Unit
Piece

90.5 C901840005 Received packets greater than maximum length

Description
The received packets greater than maximum length.

Measurement Point
The counter adds one when receiving jumbo packet.

90-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 90 PPP channel measurement

Unit
Piece

90.6 C901840006 Non-octet aligned frames received

Description
The non-octet aligned frames received.

Measurement Point
The counter adds one when receiving non-octet aligned frames.

Unit
Piece

90.7 C901840007 Received small datagrams discarded byte count

Description
The received small datagrams discarded byte count.

Measurement Point
when discarding the small packet in RX direction.

Unit
Piece

90.8 C901840008 Received jumbo packets byte count

Description
The received jumbo packets total length.

Measurement Point
when receiving jumbo packet.

Unit
Byte

90-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

90.9 C901840009 Received small datagrams discarded event count

Description
The received small datagrams discarded event count.

Measurement Point
The counter adds one when discarding small packet in RX direction.

Unit
Piece

90.10 C901840010 Received jumbo packets count

Description
The received chunk buffer allocation exceeded event count.

Measurement Point
The counter adds one when receiving the jumbo package.

Unit
Piece

90.11 C901840011 Transmitted byte count

Description
The transmitted byte count.

Measurement Point
when transmitting data packet.

Unit
Byte

90-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 90 PPP channel measurement

90.12 C901840012 Transmitted packet count

Description
The transmitted packet count.

Measurement Point
The counter adds one when transmitting data packet.

Unit
Piece

90.13 C901840013 Transmit framing aborts

Description
The Transmit framing aborts.

Measurement Point
The counter adds one when transmitting frame.

Unit
Piece

90.14 C901840014 MLPPP ID

Description
ID of the ML-PPP that a PPP belongs to. It is only measured on the EUIP board.

Measurement Point
The counter is updated when a PPP is configured for an MP.

Unit
bps

90.15 C901840015 PPP band width

Description
Bandwidth of PPP link.
90-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When Configuration Ppp-port time slot, , the counter updated to the current value.

Unit
bps

90-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91

UMAC Measurement
Table of Contents
Overview ..................................................................................................................91-3 C901850001 receive discard packets flag ................................................................91-3 C901850002 receive discard packets low 32bits ......................................................91-4 C901850003 receive discard packets high 32bits .....................................................91-4 C901850004 receive bytes flag ................................................................................91-4 C901850005 receive bytes low 32bits ......................................................................91-5 C901850006 receive bytes high 32bits .....................................................................91-5 C901850007 receive packets flag.............................................................................91-5 C901850008 receive packets low 32bits...................................................................91-6 C901850009 receive packets high 32bits .................................................................91-6 C901850010 receive broadcast packets flag ............................................................91-6 C901850011 receive broadcast packets low 32bits...................................................91-7 C901850012 receive broadcast packets high 32bits .................................................91-7 C901850013 receive multicast packets flag..............................................................91-8 C901850014 receive multicast packets low 32bits ....................................................91-8 C901850015 receive multicast packets high 32bits ..................................................91-8 C901850016 receive CRC or align error packets flag ...............................................91-9 C901850017 receive CRC or align error packets low 32bits .....................................91-9 C901850018 receive CRC or align error packets high 32bits ..................................91-10 C901850019 receive small than 64 bytes packets flag ...........................................91-10 C901850020 receive small than 64 bytes packets low 32bits..................................91-10 C901850021 receive small than 64 bytes packets high 32bits ................................ 91-11 C901850022 receive large than 1518 bytes packets flag ........................................ 91-11 C901850023 receive large than 1518 bytes packets low 32bits ..............................91-12 C901850024 receive large than 1518 bytes packets high 32bits.............................91-12 C901850025 The flag of received fragment packets ...............................................91-12 C901850026 Number of fragment packets received (low 32 bit) .............................91-13 C901850027 Number of received fragment packets (high 32 bit)............................91-13 C901850028 receive Jabber packets flag ...............................................................91-14 C901850029 receive Jabber packets low 32bits .....................................................91-14 C901850030 receive Jabber packets high 32bits....................................................91-14 C901850031 receive Collision count flag ................................................................91-15 C901850032 receive Collision count low 32bits ......................................................91-15 C901850033 receive Collision count high 32bits.....................................................91-15 C901850034 receive 64 bytes packets flag ............................................................91-16 C901850035 receive 64 bytes packets low 32bits ..................................................91-16 C901850036 receive 64 bytes packets high 32bits .................................................91-17
91-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901850037 receive 65 to 127 bytes packets flag..................................................91-17 C901850038 receive 65 to 127 bytes packets low 32bits........................................91-17 C901850039 receive 65 to 127 bytes packets high 32bits ......................................91-18 C901850040 receive 128 to 255 bytes packets flag................................................91-18 C901850041 receive 128 to 255 bytes packets low 32bits......................................91-19 C901850042 receive 128 to 255 bytes packets high 32bits ....................................91-19 C901850043 receive 256 to 511 bytes packets flag ................................................91-19 C901850044 receive 256 to 511 bytes packets low 32bits ......................................91-20 C901850045 receive 256 to 511 bytes packets high 32bits.....................................91-20 C901850046 receive 512 to 1023 bytes packets flag..............................................91-21 C901850047 receive 512 to 1023 bytes packets low 32bits....................................91-21 C901850048 receive 512 to 1023 bytes packets high 32bits ..................................91-21 C901850049 receive 1024 to 1518 bytes packets flag............................................91-22 C901850050 receive 1024 to 1518 bytes packets low 32bits ..................................91-22 C901850051 receive 1024 to 1518 bytes packets high 32bits.................................91-23 C901850052 send discard packets flag ..................................................................91-23 C901850053 send discard packets low 32bits ........................................................91-23 C901850054 send discard packets high 32bits.......................................................91-24 C901850055 send packet bytes flag.......................................................................91-24 C901850056 send packet bytes low 32bits.............................................................91-24 C901850057 send packets bytes high 32bits..........................................................91-25 C901850058 send packets flag ..............................................................................91-25 C901850059 send packets low 32bits ....................................................................91-26 C901850060 send packets high 32bits ...................................................................91-26 C901850061 send broadcast packets flag ..............................................................91-26 C901850062 send broadcast packets low 32bits ....................................................91-27 C901850063 send broadcast packets high 32bits...................................................91-27 C901850064 send multicast packets flag ...............................................................91-27 C901850065 send multicast packets low 32bits......................................................91-28 C901850066 send multicast packets high 32bits ....................................................91-28 C901850067 send CRC or Align error packets flag ................................................91-28 C901850068 send CRC or Align error packets low 32bits.......................................91-29 C901850069 send CRC or Align error packets high 32bits .....................................91-29 C901850070 send small than 64 bytes packets flag ...............................................91-30 C901850071 send small than 64 bytes packets low 32bits .....................................91-30 C901850072 send small than 64 bytes packets high 32bits....................................91-30 C901850073 send large than 1518 bytes packets flag............................................91-31 C901850074 send large than 1518 bytes packets low 32bits..................................91-31 C901850075 send large than 1518 bytes packets high 32bits ................................91-32 C901850076 The flag of sent fragment packets......................................................91-32 C901850077 Number of sent fragment packets (low 32 bit)....................................91-32 C901850078 Number of sent fragment packets (high 32 bit) ..................................91-33 C901850079 send Jabber packets flag...................................................................91-33 C901850080 send Jabber packets low 32bits.........................................................91-34 C901850081 send Jabber packets high 32bits .......................................................91-34
91-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

C901850082 send Collision count flag....................................................................91-34 C901850083 send Collision count low 32bits..........................................................91-35 C901850084 send Collision count high 32bits ........................................................91-35 C901850085 send 64 bytes packets flag ................................................................91-35 C901850086 send 64 bytes packets low 32bits ......................................................91-36 C901850087 send 64 bytes packets high 32bits.....................................................91-36 C901850088 send 65 to 127 bytes packets flag .....................................................91-36 C901850089 send 65 to 127 bytes packets low 32bits ...........................................91-37 C901850090 send 65 to 127 bytes packets high 32bits ..........................................91-37 C901850091 send 128 to 255 bytes packets flag ...................................................91-38 C901850092 send 128 to 255 bytes packets low 32bits .........................................91-38 C901850093 send 128 to 255 bytes packets high 32bits ........................................91-38 C901850094 send 256 to 511 bytes packets flag....................................................91-39 C901850095 send 256 to 511 bytes packets low 32bits..........................................91-39 C901850096 send 256 to 511 bytes packets high 32bits ........................................91-40 C901850097 send 512 to 1023 bytes packets flag .................................................91-40 C901850098 send 512 to 1023 bytes packets low 32bits........................................91-40 C901850099 send 512 to 1023 bytes packets high 32bits ......................................91-41 C901850100 send 1024 to 1518 bytes packets flag................................................91-41 C901850101 send 1024 to 1518 bytes packets low 32bits......................................91-42 C901850102 send 1024 to 1518 bytes packets high 32bits ....................................91-42 C901850103 Logic port type...................................................................................91-42

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

91.2 C901850001 receive discard packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
91-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
None

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

91.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
The counter counts when the packet is received.

91.5 C901850004 receive bytes flag

Description
This counter flags the property of the statistic item.

Usage
l 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. 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.
91-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.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
The counter counts when the packet is received.

91.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
The counter counts when the packet is received.

91.8 C901850007 receive packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. 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.
91-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.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
The counter counts when the packet is received.

91.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
The counter counts when the packet is received.

91.11 C901850010 receive broadcast 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.
91-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.12 C901850011 receive broadcast packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of received broadcast packets.

Usage
This counter is used to find out the number of broadcast packets received.

Measurement Point
The counter counts when the packet is received.

91.13 C901850012 receive broadcast packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of received broadcast packets.

Usage
This counter is used to find out the number of broadcast packets received.

Measurement Point
The counter counts when the packet is received.

91-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

91.14 C901850013 receive multicast packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.15 C901850014 receive multicast packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of received multicast packets.

Usage
This counter is used to find out the number of multicast packets received.

Measurement Point
The counter counts when the packet is received.

91.16 C901850015 receive multicast packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of received multicast packets.

Usage
This counter is used to find out the number of multicast packets received.
91-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

Measurement Point
The counter counts when the packet is received.

91.17 C901850016 receive CRC or align error packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.18 C901850017 receive CRC or align error packets 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
The counter counts when the packet is received.

91-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

91.19 C901850018 receive CRC or align error packets 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
The counter counts when the packet is received.

91.20 C901850019 receive small than 64 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.21 C901850020 receive small than 64 bytes packets 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.
91-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

Usage
This counter is used to find out the number of received packets of which the size is smaller than 64 bytes.

Measurement Point
The counter counts when the packet is received.

91.22 C901850021 receive small than 64 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of received packets of which the size is smaller than 64 bytes.

Usage
This counter is used to find out the number of received packets of which the size is smaller than 64 bytes.

Measurement Point
The counter counts when the packet is received.

91.23 C901850022 receive large than 1518 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None
91-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

91.24 C901850023 receive large than 1518 bytes packets 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 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
The counter counts when the packet is received.

91.25 C901850024 receive large than 1518 bytes packets high 32bits
Description
This counter records the higher 32 bits of the statistic item of the number of received 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
The counter counts when the packet is received.

91.26 C901850025 The flag of received fragment packets

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.
91-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.27 C901850026 Number of fragment packets received (low 32 bit)

Description
This counter records the lower 32 bits of the statistic item of the number of received fragment packets.

Usage
This counter is used to find out the number of received fragment packets.

Measurement Point
The counter counts when the packet is received.

91.28 C901850027 Number of received fragment packets (high 32 bit)

Description
This counter records the higher 32 bits of the statistic item of the number of received fragment packets.

Usage
This counter is used to find out the number of received fragment packets.

Measurement Point
The counter counts when the packet is received.

91-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

91.29 C901850028 receive Jabber packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.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
The counter counts when the packet is received.

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

91-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

Measurement Point
The counter counts when the packet is received.

91.32 C901850031 receive Collision count flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.33 C901850032 receive Collision count low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of received collisions.

Usage
This counter is used to find out the number of received collisions.

Measurement Point
The counter counts when the packet is received.

91.34 C901850033 receive Collision count high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of received collisions.

91-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of received collisions.

Measurement Point
The counter counts when the packet is received.

91.35 C901850034 receive 64 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.36 C901850035 receive 64 bytes packets 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 64 bytes.

Usage
This counter is used to find out the number of received packets of which the size is 64 bytes.

Measurement Point
The counter counts when the packet is received.

91-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

91.37 C901850036 receive 64 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of received 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.

Measurement Point
The counter counts when the packet is received.

91.38 C901850037 receive 65 to 127 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.39 C901850038 receive 65 to 127 bytes packets 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 between 65 bytes and 127 bytes.

91-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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
The counter counts when the packet is received.

91.40 C901850039 receive 65 to 127 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of received packets 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
The counter counts when the packet is received.

91.41 C901850040 receive 128 to 255 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

91.42 C901850041 receive 128 to 255 bytes packets 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 between 128 bytes and 255 bytes.

Usage
This counter is used to find out the number of received packets of which the size is between 128 bytes and 255 bytes.

Measurement Point
The counter counts when the packet is received.

91.43 C901850042 receive 128 to 255 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of received packets of which the size is between 128 bytes and 255 bytes.

Usage
This counter is used to find out the number of received packets of which the size is between 128 bytes and 255 bytes.

Measurement Point
The counter counts when the packet is received.

91.44 C901850043 receive 256 to 511 bytes 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.

91-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.45 C901850044 receive 256 to 511 bytes packets 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 between 256 bytes and 511 bytes.

Usage
This counter is used to find out the number of received packets of which the size is between 256 bytes and 511 bytes.

Measurement Point
The counter counts when the packet is received.

91.46 C901850045 receive 256 to 511 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of received packets of which the size is between 256 bytes and 511 bytes.

Usage
This counter is used to find out the number of received packets of which the size is between 256 bytes and 511 bytes.

Measurement Point
The counter counts when the packet is received.

91-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

91.47 C901850046 receive 512 to 1023 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.48 C901850047 receive 512 to 1023 bytes packets 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 between 512 bytes and 1023 bytes.

Usage
This counter is used to find out the number of received packets of which the size is between 512 bytes and 1023 bytes.

Measurement Point
The counter counts when the packet is received.

91.49 C901850048 receive 512 to 1023 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of received packets of which the size is between 512 bytes and 1023 bytes.
91-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter is used to find out the number of received packets of which the size is between 512 bytes and 1023 bytes.

Measurement Point
The counter counts when the packet is received.

91.50 C901850049 receive 1024 to 1518 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.51 C901850050 receive 1024 to 1518 bytes packets 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 between 1024 bytes and 1518 bytes.

Usage
This counter is used to find out the number of received packets of which the size is between 1024 bytes and 1518 bytes.

Measurement Point
The counter counts when the packet is received.
91-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

91.52 C901850051 receive 1024 to 1518 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of received packets of which the size is between 1024 bytes and 1518 bytes.

Usage
This counter is used to find out the number of received packets of which the size is between 1024 bytes and 1518 bytes.

Measurement Point
The counter counts when the packet is received.

91.53 C901850052 send discard packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.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.
91-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when the packet is transmitted.

91.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
The counter counts when the packet is transmitted.

91.56 C901850055 send packet bytes flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

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

91-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

Usage
This counter is used to find out the total number of bytes of transmitted packets.

Measurement Point
The counter counts when the packet is transmitted.

91.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
The counter counts when the packet is transmitted.

91.59 C901850058 send packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

91.60 C901850059 send packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted packets.

Usage
This counter is used to find out the total number of transmitted packets.

Measurement Point
The counter counts when the packet is transmitted.

91.61 C901850060 send packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted packets.

Usage
This counter is used to find out the total number of transmitted packets.

Measurement Point
The counter counts when the packet is transmitted.

91.62 C901850061 send broadcast packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

91-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

Measurement Point
None

91.63 C901850062 send broadcast packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted broadcast packets.

Usage
This counter is used to find out the number of transmitted broadcast packets.

Measurement Point
The counter counts when the packet is transmitted.

91.64 C901850063 send broadcast packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted broadcast packets.

Usage
This counter is used to find out the number of transmitted broadcast packets.

Measurement Point
The counter counts when the packet is transmitted.

91.65 C901850064 send multicast packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. 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.
91-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.66 C901850065 send multicast packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted multicast packets.

Usage
This counter is used to find out the number of transmitted multicast packets.

Measurement Point
The counter counts when the packet is transmitted.

91.67 C901850066 send multicast packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted multicast packets.

Usage
This counter is used to find out the number of transmitted multicast packets.

Measurement Point
The counter counts when the packet is transmitted.

91.68 C901850067 send CRC or Align error 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.
91-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.69 C901850068 send CRC or Align error packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted CRC or alignment error packets.

Usage
This counter is used to find out the number of transmitted CRC or alignment error packets.

Measurement Point
The counter counts when the packet is transmitted.

91.70 C901850069 send CRC or Align error packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted CRC or alignment error packets.

Usage
This counter is used to find out the number of transmitted CRC or alignment error packets.

Measurement Point
The counter counts when the packet is transmitted.

91-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

91.71 C901850070 send small than 64 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.72 C901850071 send small than 64 bytes packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted packets of which the size is smaller than 64 bytes.

Usage
This counter is used to find out the number of transmitted packets of which the size is smaller than 64 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91.73 C901850072 send small than 64 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted packets of which the size is smaller than 64 bytes.
91-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

Usage
This counter is used to find out the number of transmitted packets of which the size is smaller than 64 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91.74 C901850073 send large than 1518 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.75 C901850074 send large than 1518 bytes packets low 32bits
Description
This counter records the lower 32 bits of the statistic item of the number of transmitted packets of which the size is larger than 1518 bytes.

Usage
This counter is used to find out the number of transmitted packets of which the size is larger than 1518 bytes.

Measurement Point
The counter counts when the packet is transmitted.
91-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

91.76 C901850075 send large than 1518 bytes packets high 32bits
Description
This counter records the higher 32 bits of the statistic item of the number of transmitted packets of which the size is larger than 1518 bytes.

Usage
This counter is used to find out the number of transmitted packets of which the size is larger than 1518 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91.77 C901850076 The flag of sent fragment packets

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.78 C901850077 Number of sent fragment packets (low 32 bit)

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted fragment packets.

91-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

Usage
This counter is used to find out the number of transmitted fragment packets.

Measurement Point
The counter counts when the packet is transmitted.

91.79 C901850078 Number of sent fragment packets (high 32 bit)

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted fragment packets.

Usage
This counter is used to find out the number of transmitted fragment packets.

Measurement Point
The counter counts when the packet is transmitted.

91.80 C901850079 send Jabber packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

91.81 C901850080 send Jabber packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted Jabber packets.

Usage
This counter is used to find out the number of transmitted Jabber packets.

Measurement Point
The counter counts when the packet is transmitted.

91.82 C901850081 send Jabber packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted Jabber packets.

Usage
This counter is used to find out the number of transmitted Jabber packets.

Measurement Point
The counter counts when the packet is transmitted.

91.83 C901850082 send Collision count flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

91-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

Measurement Point
None

91.84 C901850083 send Collision count low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted collisions.

Usage
This counter is used to find out the number of transmitted collisions.

Measurement Point
The counter counts when the packet is transmitted.

91.85 C901850084 send Collision count high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted collisions.

Usage
This counter is used to find out the number of transmitted collisions.

Measurement Point
The counter counts when the packet is transmitted.

91.86 C901850085 send 64 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. 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.
91-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.87 C901850086 send 64 bytes packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted packets of which the size is 64 bytes.

Usage
This counter is used to find out the number of transmitted packets of which the size is 64 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91.88 C901850087 send 64 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted packets of which the size is 64 bytes.

Usage
This counter is used to find out the number of transmitted packets of which the size is 64 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91.89 C901850088 send 65 to 127 bytes packets flag

Description
This counter flags the property of the statistic item.

91-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.90 C901850089 send 65 to 127 bytes packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted packets of which the size is between 65 bytes and 127 bytes.

Usage
This counter is used to find out the number of transmitted packets of which the size is between 65 bytes and 127 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91.91 C901850090 send 65 to 127 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted packets of which the size is between 65 bytes and 127 bytes.

Usage
This counter is used to find out the number of transmitted packets of which the size is between 65 bytes and 127 bytes.

Measurement Point
The counter counts when the packet is transmitted.
91-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

91.92 C901850091 send 128 to 255 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.93 C901850092 send 128 to 255 bytes packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted packets of which the size is between 128 bytes and 255 bytes.

Usage
This counter is used to find out the number of transmitted packets of which the size is between 128 bytes and 255 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91.94 C901850093 send 128 to 255 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted packets of which the size is between 128 bytes and 255 bytes.

91-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

Usage
This counter is used to find out the number of transmitted packets of which the size is between 128 bytes and 255 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91.95 C901850094 send 256 to 511 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.96 C901850095 send 256 to 511 bytes packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted packets of which the size is between 256 bytes and 511 bytes.

Usage
This counter is used to find out the number of transmitted packets of which the size is between 256 bytes and 511 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

91.97 C901850096 send 256 to 511 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted packets of which the size is between 256 bytes and 511 bytes.

Usage
This counter is used to find out the number of transmitted packets of which the size is between 256 bytes and 511 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91.98 C901850097 send 512 to 1023 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None

91.99 C901850098 send 512 to 1023 bytes packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted packets of which the size is between 512 bytes and 1023 bytes.

91-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

Usage
This counter is used to find out the number of transmitted packets of which the size is between 512 bytes and 1023 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91.100 C901850099 send 512 to 1023 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted packets of which the size is between 512 bytes and 1023 bytes.

Usage
This counter is used to find out the number of transmitted packets of which the size is between 512 bytes and 1023 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91.101 C901850100 send 1024 to 1518 bytes packets flag

Description
This counter flags the property of the statistic item.

Usage
l 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. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.

Measurement Point
None
91-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

91.102 C901850101 send 1024 to 1518 bytes packets low 32bits

Description
This counter records the lower 32 bits of the statistic item of the number of transmitted packets of which the size is between 1024 bytes and 1518 bytes.

Usage
This counter is used to find out the number of transmitted packets of which the size is between 1024 bytes and 1518 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91.103 C901850102 send 1024 to 1518 bytes packets high 32bits

Description
This counter records the higher 32 bits of the statistic item of the number of transmitted packets of which the size is between 1024 bytes and 1518 bytes.

Usage
This counter is used to find out the number of transmitted packets of which the size is between 1024 bytes and 1518 bytes.

Measurement Point
The counter counts when the packet is transmitted.

91.104 C901850103 Logic port type

Description
This counter records the logic port type (0: internal; 1: external; 0xffffffff: invalid).

Usage
None

Measurement Point
None
91-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 91 UMAC Measurement

Unit
None

91-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

91-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92

Downlink EGPRS2-A TBF Statistic

Table of Contents
C901860001 Total number DL EGPRS2-A TBF EST REQ .......................................92-3 C901860002 Number DL EGPRS2-A TBF EST REQ CCCH/PCCCH ......................92-3 C901860003 Number DL EGPRS2-A TBF EST REQ ...............................................92-4 C901860004 Number DL EGPRS2-A TBF est req fail CPU ......................................92-5 C901860005 Number DL EGPRS2-A TBF Est Req Fail ...........................................92-5 C901860006 Number DL EGPRS2-A TBF EST channel allocate fail........................92-5 C901860007 Number DL EGPRS2-A TBF est req fail Abis cong ..............................92-7 C901860008 Number DL EGPRS2-A TBF est req fail RR cong................................92-8 C901180009 Number DL EGPRS2-A TBF est req fail UPPB-DSP channel cong......92-9 C901860010 Number DL EGPRS2-A TBF EST channel allocate success..............92-10 C901860011 Number DL EGPRS2-A TBF successful EST..................................... 92-11 C901860012 Number DL EGPRS2-A TBF EST channel activate fail......................92-12 C901860013 Num DL EGPRS2-A TBF failed EST caused by connection with BTS........................................................................................................................92-12 C901860014 Num DL EGPRS2-A TBF failed EST caused by connection with BIU .92-13 C901860015 Number DL EGPRS2-A TBF EST channel activate success..............92-14 C901860016 Number DL EGPRS2-A TBF EST fail ................................................92-15 C901860017 Number DL EGPRS2-A TBF EST Fail MSidle PCCCH/CCCH...........92-15 C901860018 Number DL EGPRS2-A TBF EST fail MStrans ..................................92-16 C901860019 Number DL EGPRS2-A TBF EST success MSidle PCCCH/CCCH....92-16 C901860020 Number DL EGPRS2-A TBF EST Success MStrans .........................92-17 C901860021 Num DL EGPRS2-A TBF res realloc req for uplink TBF establishment .........................................................................................................92-17 C901860022 Number DL res realloc downlink TBF est channel allocate fail ...........92-18 C901860023 Number DL res realloc req fail Abis cong...........................................92-19 C901860024 Number DL res realloc req fail RR cong ............................................92-19 C901860025 Number res realloc req fail UPPB-DSP channel cong........................92-20 C901860026 Number DL res realloc downlink TBF est channel allocate success...92-21 C901860027 Number PDTCH successfully allocated for DL EGPRS2-A TBF while UL TBF est ............................................................................................................92-22 C901860028 Number DL EGPRS2-A TBF res realloc downlink TBF est channel activate fail .............................................................................................................92-23 C901860029 Number DL EGPRS2-A TBF res realloc downlink TBF est channel activate fail .............................................................................................................92-23
92-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901860030 Number DL EGPRS2-A TBF res realloc downlink TBF est channel activate fail .............................................................................................................92-24 C901860031 Number DL EGPRS2-A TBF res realloc downlink TBF est channel activate success.....................................................................................................92-25 C901860032 Number DL EGPRS2-A TBF res realloc downlink TBF est fail ...........92-26 C901860033 Number DL EGPRS2-A TBF Res Realloc Downlink TBF Est Success .................................................................................................................92-26 C901860034 Number DL EGPRS2-A TBF res realloc req ......................................92-26 C901860035 Number DL res realloc LLC cause channel allocate fail .....................92-27 C901860036 Number DL res realloc req LLC cause fail Abis cong .........................92-28 C901860037 Number DL res realloc req LLC cause fail RR cong...........................92-28 C901860038 Number res realloc req LLC cause fail UPPB-DSP channel cong ......92-29 C901860039 Number DL res realloc LLC cause channel allocate success .............92-30 C901860040 Number PDTCH reallocated for DL EGPRS2-A TBF caused by LLC transfer...................................................................................................................92-31 C901860041 Number DL EGPRS2-A TBF res realloc LLC cause channel activate fail ..........................................................................................................................92-32 C901860042 Number DL EGPRS2-A TBF res realloc LLC cause channel activate fail ..........................................................................................................................92-32 C901860043 Number DL EGPRS2-A TBF res realloc LLC cause channel activate fail ..........................................................................................................................92-33 C901860044 Number DL EGPRS2-A TBF res realloc LLC cause channel activate success ..................................................................................................................92-34 C901860045 Number DL EGPRS2-A TBF res realloc LLC cause fail .....................92-35 C901860046 Number DL EGPRS2-A TBF Res Realloc LLC Cause Success.........92-35 C901860047 Number of EGPRS2-A DL TBF release due to flush LL .....................92-35 C901860048 Number of EGPRS2-A DL TBF release due to EGPRS2-A suspend requests .................................................................................................................92-36 C901860049 Number DL EGPRS2-A TBF rel preemption radio .............................92-37 C901860050 Number DL EGPRS2-A TBF rel normal.............................................92-37 C901860051 Number DL EGPRS2-A TBF rel other................................................92-38 C901860052 Number DL EGPRS2-A TBF release caused by abnormal NSVC......92-39 C901860053 Number DL EGPRS2-A TBF release caused by abnormal BVC ........92-39 C901860054 Number DL EGPRS2-A TBF rel ........................................................92-40 C901860055 Preempted times of DL EGPRS2-A TBF ...........................................92-41 C901860056 Preempted inst number of DL EGPRS2-A TBF..................................92-41 C901860057 Times of DL EGPRS2-A TBF queuing up for resource.......................92-42 C901860058 Times of DL EGPRS2-A TBF successfully queuing up for resource...92-43 C901860059 Times of DL EGPRS2-A TBF released when queuing up for resource .................................................................................................................92-43

92-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

92.1 C901860001 Total number DL EGPRS2-A TBF EST REQ

Description
The counter counts the number of EGPRS2-A downlink TBF establishment requests received by control plane. It is the sum of CCCH/PCCCH requests (C901860002) and PACCH requests (C901860003). The counter collects information about the frequency of DL establishment requests received by the control plane when BSC attempts to establish DL EGPRS2-A TBFs.

Measurement Point
This counter increments in the following two cases: l l When PS control plane receives a DL TBF establishment request from PS user plane, this counter increments. When UL EGPRS2-A TBF exists and DL EGPRS2-A TBF is to be established, if PS control plane receives the DL assignment message from PS user plane, this counter increments.

Unit
Times

92.2 C901860002 Number DL EGPRS2-A TBF EST REQ CCCH/PCCCH

Description
This counter counts the number of DL establishment requests received by control plane when BSC initially attempts to establish EGPRS2-A DL TBF. 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 EGPRS2-A DL TBF.

Measurement Point
When PS control plane receives the DL request (EV_RANUMC_DLASS_REQ) sent from PS user plane, the counter increments. This measurement point is A, as shown in Figure 92-1.

92-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 92-1 - DL Request

Unit
Times

92.3 C901860003 Number DL EGPRS2-A TBF EST REQ

Description
This counter counts the number of establishing EGPRS2-A DL TBF on PACCH by MS. This counter is used to find out the frequency of establishing DL TBF in PACCH after MS has established EGPRS2-A UL TBF.

Measurement Point
After MS has established EGPRS2-A UL TBF, PS control plane receives EV_MAC_DL_ASSIGN_REQ message sent from PS user plane, the counter increments. This measurement point is A, as shown inFigure 92-2.
Figure 92-2 - DL Assignment Request

Unit
Times

92-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

92.4 C901860004 Number DL EGPRS2-A TBF est req fail CPU

Definition
Number of EGPRS2-A DL TBF establishment failure due to CPU.

Description
No statistics temporarily.

92.5 C901860005 Number DL EGPRS2-A TBF Est Req Fail

Description
This counter counts the number of times that a downlink EGPRS2-A TBF establishment request fails because an MS does not support DTM.

Measurement Point
l Upon receiving a downlink assignment request, the PS user plane requests DTM resources from the database after detecting that the MS supports DTM and is in a CS traffic call. If the PS user plane fails to request DTM resources, this counter is incremented. Upon receiving a downlink assignment request, the PS user plane requests DTM resources from the database and queries DTM channel information after detecting that the MS supports DTM and is in a CS traffic call. If the PS user plane fails to query DTM channel information, this counter is incremented. This counter is incremented each time the PS user plane, upon receiving a DTM establishment request from the CS instance, fails to obtain DTM resources from the database or the MS does not support DTM.

Unit
Number of times

92.6 C901860006 Number DL EGPRS2-A TBF EST channel allocate fail

Description
The counter counts the number of channel allocation failures when BSC attempts to establish EGPRS2-A DL TBFs and PS control plane applies to database for resources.
92-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

It involves the number of allocation failures caused by PDCH, Abis, and PCU having no available resource or in abnormal status. The counter collects information about the frequency of channel allocation failures when BSC attempts to establish EGPRS2-A DL TBFs and PS control plane applies to database for resources.

Measurement Point
This counter increments in the following two cases: 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 counter increments. The measurement point is A, as shown in Figure 92-3.
Figure 92-3 Measurement Point of Allocation Failures after Receiving DL TBF Establishment Request

When UL EGPRS2-A TBF exists and DL EGPRS2-A TBF is to be established, if PS control plane receives the DL TBF assignment message from PS user plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 92-4.
Figure 92-4 Measurement Point of Allocation Failures after Receiving DL TBF Assignment Message

Unit
Times

92-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

92.7 C901860007 Number DL EGPRS2-A TBF est req fail Abis cong
Description
This counter counts the number of failures that PS control plane applies to database for resource and the cause of failures is Abis congestion when BSC attempts to establish EGPRS2-A DL TBF. This counter is used to find out the frequency of failures that PS control plane applies to database for resource and the cause of failures is Abis congestion when BSC attempts to establish EGPRS2-A DL TBF.

Measurement Point
The measurement is taken at two time points listed below: l After PS control plane module receives DL request message (EV_RANUMC_DLASS_REQ) sent from PS user plane, if resource application fails and the cause of failure is Abis congestion, the counter increments. The measurement point is A, as shown in Figure 92-5.
Figure 92-5 - Database Application Failure Due To Abis Congestion (I)

After MS establishes EGPRS2-A UL TBF, PS control plane module receives EV_MAC_DL_ASSIGN_REQ message sent from PS user plane, if resource application fails and the cause of failure is Abis congestion, the counter increments. The measurement point is A, as shown in Figure 92-6.
Figure 92-6 - Database Application Failure Due To Abis Congestion (II)

92-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

92.8 C901860008 Number DL EGPRS2-A TBF est req fail RR cong

Description
This counter counts the number of failures that PS control plane applies to database for resource and the cause of failures is RR congestion when BSC attempts to establish EGPRS2-A DL TBF. There are three causes for RR congestion: MS per channel (number of MS reaches the peak in each channel), TAI/TFI (no TAI or TFI) and no PDCH (no PS channel). This counter is used to find out the frequency of failures that PS control plane applies to database for resource and the cause of failures is RR congestion when BSC attempts to establish EGPRS2-A DL TBF.

Measurement Point
The measurement is taken at two time points listed below: l After PS control plane module receives DL request message (EV_RANUMC_DLASS_REQ) sent from PS user plane, if resource application fails and the cause of failure is RR congestion, the counter increments. The measurement point is A, as shown inFigure 92-7.
Figure 92-7 - Database Application Failure Due To RR Congestion (I)

After MS establishes EGPRS2-A UL TBF, PS control plane module receives EV_MAC_DL_ASSIGN_REQ message sent from PS user plane, if resource application fails and the cause of failure is RR congestion, the counter increments. The measurement point is A, as shown inFigure 92-8.

92-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

Figure 92-8 - Database Application Failure Due To RR Congestion (II)

Unit
Times

92.9 C901180009 Number DL EGPRS2-A TBF est req fail UPPB-DSP channel cong
Description
This counter counts the number of failures that PS control plane applies to database for resource and the cause of failures is UPPB-DSP channel congestion when BSC attempts to establish EGPRS2-A DL TBF. This counter is used to find out the frequency of failures that PS control plane applies to database for resource and the cause of failures is UPPB-DSP channel congestion when BSC attempts to establish EGPRS2-A DL TBF.

Measurement Point
The measurement is taken at two time points listed below: l After PS control plane receives DL request message (EV_RANUMC_DLASS_REQ) sent from PS user plane, 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 92-9.

92-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 92-9 - Database Application Failure due to UPPB-DSP Channel Congestion (I)

After MS establishes EGPRS2-A UL TBF, PS control plane receives EV_MAC_DL_ASSIGN_REQ message sent from PS user plane, 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 92-10.
Figure 92-10 - Database Application Failure due to UPPB-DSP Channel Congestion (II)

Unit
Times

92.10 C901860010 Number DL EGPRS2-A TBF EST channel allocate success

Description
This counter counts the number of channel allocate success applied by PS control plane when BSC attempts to establish EGPRS2-A DL TBF. This counter is used to find out the frequency of successful resource application that PS control plane sends when BSC attempts to establish EGPRS2-A DL TBF.

92-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

Measurement Point
After PS control plane receives DL request message (EV_RANUMC_DLASS_REQ) sent from PS user plane, when resource application succeeds, the counter increments. The measurement point is A, as shown inFigure 92-11.
Figure 92-11 - Successful Resource Application

Unit
Times

92.11 C901860011 Number DL EGPRS2-A TBF successful EST

Description
This counter counts the number of successful allocated PDCH when BSC attempts to establish EGPRS2-A DL TBF. This counter is used to find out the number of successful allocated PDCH when BSC attempts to establish EGPRS2-A DL TBF.

Measurement Point
After PS control plane receives DL request message EV_RANUMC_DLASS_REQ sent from PS user plane, when resource application succeeds, the counter accumulates the PDCH number. The measurement point is A, as shown inFigure 92-12.
Figure 92-12 - Successful Resource Application

92-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

92.12 C901860012 Number DL EGPRS2-A TBF EST channel activate fail

Description
This counter counts the number of PDCH activate failure when BSC establishes EGPRS2-A DL TBF. This counter is used to find out the frequency of PDCH activate failure when BSC establishes EGPRS2-A DL TBF (including establishing DL TBF initially and establishing DL TBF while UL TBF already exists).

Measurement Point
The measurement is taken at two time points listed below: l When BSC receives PDCH activation failure message reported by BTS, the counter increments. The measurement point is A, as shown inFigure 92-13.
Figure 92-13 - PDCH Activation Failure

If 'wait for PDCH activate & connection response' timer expires, and BSC has not received PDCH activate response message reported by BTS, the counter increments.

Unit
Times

92.13 C901860013 Num DL EGPRS2-A TBF failed EST caused by connection with BTS
Description
This counter counts the number of connection failure due to BTS connection failed when BSC establishes EGPRS2-A DL TBF.
92-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

This counter is used to find out the frequency of connection failure due to BTS connection failed when BSC establishes EGPRS2-A DL TBF (including establishing DL TBF initially and establishing DL TBF while UL TBF already exists).

Measurement Point
The measurement is taken at two time points listed below: l If PS control plane receives connection failure message reported by connection module, and the cause of failure is BTS connection failure, the counter increments. The measurement point is A, as shown inFigure 92-14.
Figure 92-14 - Connection Failed Due To BTS Connection Failure

If 'wait for PDCH activation & connection response' timer expires, and BSC has not received connection success response message reported by connection module, the counter increments.

Unit
Times

92.14 C901860014 Num DL EGPRS2-A TBF failed EST caused by connection with BIU
Description
This counter counts the number of connection failure due to BIU connection failed when BSC establishes EGPRS2-A DL TBF. This counter is used to find out the frequency of connection failure due to BIU connection failed when BSC establishes EGPRS2-A DL TBF (including establishing DL TBF initially and establishing DL TBF while UL TBF already exists).

Measurement Point
If PS control plane receives connection failed message reported by connection module, and the cause of failure is BIU connection failed, the counter increments. The measurement point is A, as shown inFigure 92-15.

92-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 92-15 - Connection Failed Due To BIU Connection Failure

Unit
Times

92.15 C901860015 Number DL EGPRS2-A TBF EST channel activate success

Description
This counter counts the number of channel activate establishment success when BSC establishes EGPRS2-A DL TBF. This counter is used to find out the frequency of channel activate establishment success when BSC establishes EGPRS2-A DL TBF.

Measurement Point
When PS control plane 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 92-16.
Figure 92-16 - Immediate Assignment Sending Failure

Unit
Times
92-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

92.16 C901860016 Number DL EGPRS2-A TBF EST fail

Description
This counter counts the number of DL immediate assignment message sending failures when BSC establishes EGPRS2-A DL TBF. This counter is used to find out the frequency of DL immediate assignment message sending failures when BSC establishes EGPRS2-A DL TBF.

Measurement Point
The measurement is taken at two time points listed below: l When PS control plane receives immediate assignment sending failure message EV_PACKET_PIA_DEL_IND reported by BTS, the counter increments. The measurement point is A, as shown inFigure 92-17.
Figure 92-17 - Successful Immediate Assignment Sending

If 'wait for immediate assignment sending indication' timer expires, and BSC has not received immediate assignment sending message, the counter increments.

Unit
Times

92.17 C901860017 Number DL EGPRS2-A TBF EST Fail MSidle PCCCH/CCCH

Description
This counter counts downlink EGPRS2-A TBF establishment failures due to UPPB-DSP service congestion.

Measurement Point
This counter is incremented each time the PS control plane receives a release request from the PS user plane when waiting for a resource request from the MS during a two-step access, or the timer used to wait for a resource request expires.
92-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Number of times

92.18 C901860018 Number DL EGPRS2-A TBF EST fail MStrans

Description
No statistics for this counter is meaningless to EGPRS2-A DL TBF.

92.19 C901860019 Number DL EGPRS2-A TBF EST success MSidle PCCCH/CCCH

Description
This counter counts the number of successful DL immediate assignment message sendings when BSC establishes EGPRS2-A DL TBF. This counter is used to find out the frequency of EGPRS2-A DL TBF establishment success.

Measurement Point
When PS control plane receives successful immediate assignment sending message (SPS_ABIS_PACKET_SEND_PIA_IND) reported by BTS, the counter increments. The measurement point is A, as shown inFigure 92-18.
Figure 92-18 - Resource Application Failure Due To Abis Congestion (Assigned By UL)

Unit
Times

92-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

92.20 C901860020 Number DL EGPRS2-A TBF EST Success MStrans

Description
This counter counts downlink EGPRS2-A TBF establishment successes on PACCHs.

Measurement Point
This counter is incremented each time the PS control plane in normal assignment status, after receiving a downlink assignment request (to establish a downlink TBF when an uplink TBF exists), successfully obtains bidirectional resources from the database and activates the channels.

Unit
Number of times

92.21 C901860021 Num DL EGPRS2-A TBF res realloc req for uplink TBF establishment
Description
The counter counts the number of EGPRS2-A downlink TBF resource reallocation requests (concurrent PACCH UL TBF establishment request). The counter collects information about the frequency of EGPRS2-A downlink TBF resource reallocation requests.

Measurement Point
When MS has already established a DL EGPRS2-A TBF, if PS control plane receives an UL TBF assignment message from PS user plane, this counter increments. The measurement point is A, as shown in Figure 92-19.
Figure 92-19 Measurement Point of Number of EGPRS2-A DL TBF Resource Reallocation Requests due to UL TBF Establishment

92-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

92.22 C901860022 Number DL res realloc downlink TBF est channel allocate fail
Description
If MS has already established a DL EGPRS2-A TBF and it needs to establish an UL TBF on PACCH, PS control plane should apply to database for resources. The counter counts the number of DL resource reallocation failures of channel allocation caused by failed UL TBF establishment allocation. The counter collects information about the frequency of EGPRS2-A DL resource reallocation failures of channel allocation caused by failed UL TBF establishment allocation.

Measurement Point
When MS has already established a DL EGPRS2-A 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 92-20.
Figure 92-20 Measurement Point of Number of EGPRS2-A DL TBF Resource Reallocation Failure of channel allocation due to UL TBF Establishment

Unit
Times

92-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

92.23 C901860023 Number DL res realloc req fail Abis cong

Description
After MS establishes EGPRS2-A 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. This counter is used to find out the frequency of EGPRS2-A DL TBF establishment success.

Measurement Point
MS has established EGPRS2-A DL TBF, and after PS control plane receives EV_MAC_UL_ASSIGN_REQ message sent from PS user plane, if resource application fails due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 92-21.
Figure 92-21 - Resource Application Failure Due To Abis Congestion (Assigned by UL)

Unit
Times

92.24 C901860024 Number DL res realloc req fail RR cong

Description
After MS establishes EGPRS2-A 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 RR congestion.

92-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

There are three causes for RR congestion: MS per channel (number of MS reaches the peak in each channel), TAI/TFI (no TAI or TFI) and no PDCH (no PS channel). This counter is used to find out the frequency of EGPRS2-A DL TBF resource reallocation failure due to RR congestion.

Measurement Point
MS has established EGPRS2-A DL TBF, and after PS control plane receives EV_MAC_UL_ASSIGN_REQ message sent from PS user plane, if resource application fails due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 92-22.
Figure 92-22 - Resource Application Failure Due To RR Congestion (Assigned By UL)

Unit
Times

92.25 C901860025 Number res realloc req fail UPPB-DSP channel cong
Description
After MS establishes EGPRS2-A DL TBF, it shall establish UL TBF in PACCH. But resource application failure leads to DL resource reallocation failure. This counter counts the number of DL resource reallocation failures due to UPPB-DSP channel congestion. This counter is used to find out the frequency of EGPRS2-A DL TBF resource reallocation failure due to UPPB-DSP channel congestion.

Measurement Point
MS has established EGPRS2-A DL TBF, and after PS control plane receives EV_MAC_UL_ASSIGN_REQ message sent from PS user plane, if resource application
92-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

fails due to UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown inFigure 92-23.
Figure 92-23 - Resource Application Failure Due To UPPB-DSP Congestion (Assigned By UL)

Unit
Times

92.26 C901860026 Number DL res realloc downlink TBF est channel allocate success
Description
After MS establishes EGPRS2-A DL TBF, it shall establish UL TBF in PACCH. This counter counts the number of DL resource application success. This counter is used to find out the frequency of EGPRS2-A DL TBF resource reallocation success.

Measurement Point
MS has established EGPRS2-A DL TBF, and after PS control plane receives EV_MAC_UL_ASSIGN_REQ message sent from PS user plane, if resource application succeeds, the counter increments. The measurement point is A, as shown in Figure 92-24.

92-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 92-24 Successful Resource Application (Assigned By UL)

Unit
Times

92.27 C901860027 Number PDTCH successfully allocated for DL EGPRS2-A TBF while UL TBF est
Description
This counter counts the number of successfully allocated PDCH when EGPRS2-A DL TBF resource is reallocated. This counter is used to find out the number of successfully allocated PDCH when EGPRS2-A DL TBF resource is reallocated.

Measurement Point
MS has established EGPRS2-A DL TBF, and after PS control plane receives EV_MAC_UL_ASSIGN_REQ message sent from PS user plane, when resource application succeeds, the counter accumulates the PDTCH number. The measurement point is A, as shown inFigure 92-25.
Figure 92-25 - Successful Resource Application (Assigned By UL)

92-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

Unit
Times

92.28 C901860028 Number DL EGPRS2-A TBF res realloc downlink TBF est channel activate fail
Description
This counter counts the number of PDCH activate failure during the process of EGPRS2-A DL TBF resource reallocation. This counter is used to find out the frequency of PDCH activate failure during the process of EGPRS2-A DL TBF resource reallocation.

Measurement Point
The measurement is taken at two time points listed below: l l When BSC receives PDCH activate failure message reported by BTS, the counter increments. The measurement point is A, as shown in If 'wait for PDCH activate & connection response' timer expires, and BSC has not received PDCH activate response message reported by BTS, the counter increments.
Figure 92-26 - PDCH Activation Failure

Unit
Times

92.29 C901860029 Number DL EGPRS2-A TBF res realloc downlink TBF est channel activate fail
Description
This counter counts the number of connection failure due to BTS connection failure during the process of EGPRS2-A DL TBF resource reallocation.

92-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter is used to find out the frequency of connection failure due to BTS connection failure during the process of EGPRS2-A DL TBF resource reallocation.

Measurement Point
The measurement is taken at two time points listed below: l If PS control plane receives connection failure message reported by connection module, and the cause of failure is BTS connection failure, the counter increments. The measurement point is A, as shown inFigure 92-27.
Figure 92-27 - Connection Failed Due To BTS Connection Failure

If 'wait for PDCH activation & connection response' timer expires, and BSC has not received connection success response message reported by connection module, the counter increments.

Unit
Times

92.30 C901860030 Number DL EGPRS2-A TBF res realloc downlink TBF est channel activate fail
Description
This counter counts the number of connection failure due to BIU connection failure during the process of EGPRS2-A DL TBF resource reallocation. This counter is used to find out the frequency of connection failure due to BIU connection failure during the process of EGPRS2-A DL TBF resource reallocation.

Measurement Point
If PS control plane receives connection failure message reported by connection module, and the cause of failure is BIU connection failure, the counter increments. The measurement point is A, as shown in Figure 92-28.

92-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

Figure 92-28 - Connection Failed Due To BIU Connection Failure

Unit
Times

92.31 C901860031 Number DL EGPRS2-A TBF res realloc downlink TBF est channel activate success
Description
This counter counts the number of channel activate success during the process of EGPRS2-A DL TBF resource reallocation. This counter is used to find out the frequency of channel activate success during the process of EGPRS2-A DL TBF resource reallocation.

Measurement Point
When PS control plane 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 92-29.
Figure 92-29 - Successful Activation And Connection

Unit
Times
92-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

92.32 C901860032 Number DL EGPRS2-A TBF res realloc downlink TBF est fail
Description
No statistics for this counter is meaningless to EGPRS2-A DL TBF.

92.33 C901860033 Number DL EGPRS2-A TBF Res Realloc Downlink TBF Est Success
Description
This counter counts successful downlink EGPRS2-A TBF establishments after resource reallocation due to uplink TBF establishment.

Measurement Point
This counter is incremented each time the PS control plane in normal assignment status, after receiving a uplink assignment request (to establish a downlink TBF when a downlink TBF exists) from the MAC, successfully obtains bidirectional resources from the database and completes the channel activation and connection.

Unit
Number of times

92.34 C901860034 Number DL EGPRS2-A TBF res realloc req

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 EGPRS2-A TBF transmission. This counter collects information about the frequency of resource reallocation requests received by PS control plane during the DL EGPRS2-A TBF transmission.

Measurement Point
When PS control plane receives a resource reallocation request from PS user plane, if the current DL EGPRS2-A TBF exists, this counter increments, as A shown in Figure 92-30.

92-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

Figure 92-30 Measurement Point of Number of EGPRS2-A DL TBF Resource Reallocation Requests due to LLC Transmission

Unit
Times

92.35 C901860035 Number DL res realloc LLC cause channel allocate fail
Description
During the DL EGPRS2-A 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. This counter collects information about the frequency of failed resource allocations during the DL EGPRS2-A 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 92-31.
Figure 92-31 Measurement Point of Number of EGPRS2-A DL TBF Resource Reallocation Failure of channel allocation due to LLC Transmission

Unit
Times
92-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

92.36 C901860036 Number DL res realloc req LLC cause fail Abis cong
Description
During EGPRS2-A DL TBF transmission, PS user plane sends resource adjustment message (EV_MAC_RESOURCE_ADJU_REQ) to PS control plane due to UL/DL LLC changes. PS control plane applies for resource after it receives the message. This counter counts the number of resource application failures after PS control plane receives resource adjustment request during EGPRS2-A DL TBF transmission (the cause of database application failure is Abis congestion). This counter is used to find out the frequency of resource application failures after PS control plane receives resource adjustment request during EGPRS2-A DL TBF transmission (the cause of database application failure is Abis congestion).

Measurement Point
After PS control plane receives EV_MAC_RESOURCE_ADJU_REQ message sent from PS user plane, if resource application fails due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 92-32 .
Figure 92-32 - Resource Application Failure Due To Abis Congestion (Resource Adjustment)

Unit
Times

92.37 C901860037 Number DL res realloc req LLC cause fail RR cong
Description
During EGPRS2-A DL TBF transmission, PS user plane sends resource adjustment message (EV_MAC_RESOURCE_ADJU_REQ) to PS control plane due to UL/DL LLC changes. PS control plane applies for resource after it receives the message. This
92-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

counter counts the number of resource application failures after PS control plane receives resource adjustment request during EGPRS2-A DL TBF transmission (the cause of database application failure is RR congestion). There are three causes for RR congestion: MS per channel (number of MS reaches the peak in each channel), TAI/TFI (no TAI or TFI) and no PDCH (no PS channel). This counter is used to find out the frequency of resource application failures after PS control plane receives resource adjustment request during EGPRS2-A DL TBF transmission (the cause of database application failure is RR congestion).

Measurement Point
After PS control plane receives EV_MAC_RESOURCE_ADJU_REQ message sent from PS user plane, if resource application fails due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 92-33 .
Figure 92-33 - Resource Application Failure Due To RR Congestion (Resource Adjustment)

Unit
Times

92.38 C901860038 Number res realloc req LLC cause fail UPPB-DSP channel cong
Description
During EGPRS2-A DL TBF transmission, PS user plane sends resource adjustment message (EV_MAC_RESOURCE_ADJU_REQ) to PS control plane due to UL/DL LLC changes. PS control plane applies for resource after it receives the message. This counter counts the number of resource reallocation failure after PS control plane receives resource adjustment request during EGPRS2-A DL TBF transmission (the cause of database application failure is UPPB-DSP channel congestion). This counter is used to find out the frequency of resource reallocation failure after PS control plane receives resource adjustment request during EGPRS2-A DL TBF transmission (the cause of database application failure is UPPB-DSP channel congestion).
92-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
After PS control plane receives EV_MAC_RESOURCE_ADJU_REQ message sent from PS user plane, if resource application fails due to UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown inFigure 92-34.
Figure 92-34 - Resource Application Failure Due To UPPB-DSP Channel Congestion (Resource Adjustment)

Unit
Times

92.39 C901860039 Number DL res realloc LLC cause channel allocate success
Description
During EGPRS2-A DL TBF transmission, PS user plane sends resource adjustment message (EV_MAC_RESOURCE_ADJU_REQ) to PS control plane due to UL/DL LLC changes. PS control plane applies for resource after receiving the message. This counter counts the number of resource reallocation success after PS control plane receives resource adjustment request during EGPRS2-A DL TBF transmission. This counter is used to find out the frequency of resource reallocation success after PS control plane receives resource adjustment request during EGPRS2-A DL TBF transmission.

Measurement Point
After PS control plane receives EV_MAC_RESOURCE_ADJU_REQ message sent from PS user plane, if resource application succeeds, the counter increments. The measurement point is A, as shown in Figure 92-35.

92-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

Figure 92-35 Successful Resource Application (Resource Adjustment)

Unit
Times

92.40 C901860040 Number PDTCH reallocated for DL EGPRS2-A TBF caused by LLC transfer
Description
During EGPRS2-A DL TBF transmission, PS user plane sends resource adjustment message (EV_MAC_RESOURCE_ADJU_REQ) to PS control plane due to UL/DL LLC changes. PS control plane applies for resource after it receives the message. This counter counts the number of successfully allocated PDCH after PS control plane receives resource adjustment request during EGPRS2-A DL TBF transmission. This counter is used to find out the number of successfully allocated PDCH after PS control plane receives resource adjustment request during EGPRS2-A DL TBF transmission.

Measurement Point
After PS control plane receives EV_MAC_RESOURCE_ADJU_REQ message sent from PS user plane, if resource application succeeds, the counter accumulates the PDTCH number. The measurement point is A, as shown inFigure 92-36.
Figure 92-36 - Successful Resource Application (Resource Adjustment)

92-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

92.41 C901860041 Number DL EGPRS2-A TBF res realloc LLC cause channel activate fail
Description
This counter counts the number of PDCH activate failure after BSC receives resource adjustment request during EGPRS2-A DL TBF transmission. This counter is used to find out the frequency of PDCH activate failure after BSC receives resource adjustment request during EGPRS2-A DL TBF transmission.

Measurement Point
The measurement is taken at two time points listed below: l When BSC receives PDCH activate failure message reported by BTS, the counter increments. The measurement point is A, as shown inFigure 92-37.
Figure 92-37 - Connection Failed due to BTS Connection Failure

If 'wait for PDCH activate & connection response' timer expires, and BSC has not received PDCH activate response message reported by BTS, the counter increments.

Unit
Times

92.42 C901860042 Number DL EGPRS2-A TBF res realloc LLC cause channel activate fail
Description
This counter counts the number of connection failure due to BTS connection failure after BSC receives resource adjustment request during EGPRS2-A DL TBF transmission.

92-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

This counter is used to find out the frequency of connection failure due to BTS connection failure after BSC receives resource adjustment request during EGPRS2-A DL TBF transmission.

Measurement Point
The measurement is taken at two time points listed below: l If PS control plane receives connection failure message reported by connection module, and the cause of failure is BTS connection failure, the counter increments. The measurement point is A, as shown in Figure 92-38.
Figure 92-38 - Connection Failed Due To BTS Connection Failure

If 'wait for PDCH activate & connection response' timer expires, and BSC has not received connection success response message reported by connection module, the counter increments.

Unit
Times

92.43 C901860043 Number DL EGPRS2-A TBF res realloc LLC cause channel activate fail
Description
This counter counts the number of connection failure due to BIU connection failure after BSC receives resource adjustment request during EGPRS2-A DL TBF transmission. This counter is used to find out the frequency of connection failure due to BIU connection failure after BSC receives resource adjustment request during EGPRS2-A DL TBF transmission.

Measurement Point
If PS control plane receives connection failure message reported by connection module, and the cause of failure is BIU connection failure, the counter increments. The measurement point is A, as shown inFigure 92-39.

92-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 92-39 - Connection Failed Due To BIU Connection Failure

Unit
Times

92.44 C901860044 Number DL EGPRS2-A TBF res realloc LLC cause channel activate success
Description
This counter counts the number of channel activate success after BSC receives resource adjustment request during EGPRS2-A DL TBF transmission. This counter is used to find out the frequency of channel activate success after BSC receives resource adjustment request during EGPRS2-A DL TBF transmission.

Measurement Point
When PS control plane 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 in Figure 92-40.
Figure 92-40 - Successful Activation And Connection

Unit
Times

92-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

92.45 C901860045 Number DL EGPRS2-A TBF res realloc LLC cause fail
Description
No statistics for this counter is meaningless to EGPRS2-A DL TBF.

92.46 C901860046 Number DL EGPRS2-A TBF Res Realloc LLC Cause Success
Description
This counter counts successful downlink EGPRS2-A TBF establishments after resource reallocation due to LLC transmission.

Measurement Point
This counter is incremented each time the PS control plane, upon receiving a resource reallocation request from the PS user plane, successfully obtains bidirectional resources from the database and completes the channel activation and connection.

Unit
Number of times

92.47 C901860047 Number of EGPRS2-A DL TBF release due to flush LL

Description
This counter counts the number of EGPRS2-A DL TBF release due to flush LL. This counter is used to find out the frequency of EGPRS2-A DL TBF forcing Release Requests due to flush LL received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_RANUMC_REL_CMD) reported by PS user plane, if the cause of release is flush LL, and EGPRS2-A DL TBF exists, the counter increments. The measurement point is A, as shown in Figure 92-41.

92-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 92-41 - Release Request Due To Flush LL

Unit
Times

92.48 C901860048 Number of EGPRS2-A DL TBF release due to EGPRS2-A suspend requests
Description
This counter counts the number of EGPRS2-A DL TBF release due to EGPRS2-A suspend requests. This counter is used to find out the frequency of EGPRS2-A DL TBF forcing Release Requests due to suspend requests received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_RANUMC_REL_CMD) reported by PS user plane, if the cause of release is SUSPEND, and EGPRS2-A DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 92-42.
Figure 92-42 - Release Request Due To Suspend Request

Unit
Times

92-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

92.49 C901860049 Number DL EGPRS2-A TBF rel preemption radio

Description
This counter counts the number of EGPRS2-A DL TBF forcing release by CS due to PDCH REL. This counter is used to find out the frequency of EGPRS2-A DL TBF forcing Release Requests (EV_RANCCM_PDCH_REL) received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_RANCCM_PDCH_REL) reported by CS control plane, if EGPRS2-A DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 92-43.
Figure 92-43 - Release Request Due To PDCH REL

Unit
Times

92.50 C901860050 Number DL EGPRS2-A TBF rel normal

Description
This counter counts the number of EGPRS2-A DL TBF abnormal release due to abnormal Release Request by CS control plane. This counter is used to find out the frequency of EGPRS2-A DL TBF forcing Release Requests due to abnormal Release Request by CS control plane received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_MAC_REL_IND) reported by CS control plane, if the cause of release is abnormal Release Request by CS control plane, and EGPRS2-A DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 92-44.
92-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 92-44 - Release Request due to Normal Release Request by MAC

Unit
Times

92.51 C901860051 Number DL EGPRS2-A TBF rel other

Description
This counter counts the number of EGPRS2-A DL TBF abnormal release due to abnormal Release Request by MAC. This counter is used to find out the frequency of EGPRS2-A DL TBF forcing Release Requests due to abnormal Release Request by MAC received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_MAC_REL_IND) reported by MAC, if the cause of release is abnormal Release Request by MAC, and EGPRS2-A DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 92-45.
Figure 92-45 - Release Request due to Abnormal Release Request by MAC

Unit
Times

92-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

92.52 C901860052 Number DL EGPRS2-A TBF release caused by abnormal NSVC

Description
This counter counts the number of EGPRS2-A DL TBF release due to NSVC unavailability. This counter is used to find out the frequency of EGPRS2-A DL TBF forcing Release Requests due to NSVC unavailability received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_RANUMC_REL_CMD) reported by PS user plane, if the cause of release is NSVC unavailability, and EGPRS2-A DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 92-46.
Figure 92-46 - Release Request due to NVSC Unavailability

Unit
Times

92.53 C901860053 Number DL EGPRS2-A TBF release caused by abnormal BVC

Description
This counter counts the number of EGPRS2-A DL TBF release due to BVC unavailability. This counter is used to find out the frequency of EGPRS2-A DL TBF forcing Release Requests due to BVC unavailability received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_RANUMC_REL_CMD) reported by PS user plane, if the cause of release is BVC unavailability, and EGPRS2-A DL TBF exists, the counter increments. The measurement point is A, as shown in Figure 92-47.

92-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 92-47 - Release Request Due To BVC Unavailability

Unit
Times

92.54 C901860054 Number DL EGPRS2-A TBF rel

Description
This counter counts the number of EGPRS2-A DL TBF release due to other reasons. This counter is used to find out the frequency of EGPRS2-A DL TBF forcing Release Requests due to other reasons received by PS control plane.

Measurement Point
When PS control plane receives Release Request message (EV_RANUMC_REL_CMD) reported by PS user plane, if the reason of release is others, and EGPRS2-A DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 92-48 .
Figure 92-48 - Release Request Due To Other Reasons

Unit
Times

92-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

92.55 C901860055 Preempted times of DL EGPRS2-A TBF

Description
This counter counts the number of downlink EGPRS2-A TBF's grabbing resources. The counter is used to find out the frequency of downlink EGPRS2-A TBF grabbing other TBF resources.

Measurement Point
During the downlink EGPRS2-A TBF establishment and resource adjustment process, if the resource request succeeds and the other TBF resources is grabbed, the counter increments. The measurement point is A, as shown in Figure 92-49.
Figure 92-49 Downlink EGPRS2-A Requesting Resource Successfully

Unit
Times

92.56 C901860056 Preempted inst number of DL EGPRS2-A TBF

Description
This counter counts the number of instances grabbed by downlink EGRPS TBF. The counter is used to find out the frequency of downlink EGPRS2-A TBF grabbing other TBF resources.

Measurement Point
During the downlink EGPRS2-A 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 92-50.

92-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 92-50 Downlink EGPRS2-A Requesting Resource Successfully

Unit
Times

92.57 C901860057 Times of DL EGPRS2-A TBF queuing up for resource

Description
This counter counts the number of downlink EGRPS TBF's queuing. The counter is used to find out the frequency of downlink EGPRS2-A TBF's queuing.

Measurement Point
During the downlink EGPRS2-A TBF establishment and resource adjustment process, if the resource request succeeds but it can not guarantee queuing at the QoS rate, the counter increments. The measurement point is A, as shown in Figure 92-51.
Figure 92-51 Downlink EGPRS2-A Requesting Resource Successfully

Unit
Times

92-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 92 Downlink EGPRS2-A TBF Statistic

92.58 C901860058 Times of DL EGPRS2-A TBF successfully queuing up for resource

Description
This counter counts the number of downlink EGPRS2-A TBF's queuing success. 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 92-52.
Figure 92-52 Assigning Resource Successfully

Unit
Times

92.59 C901860059 Times of DL EGPRS2-A TBF released when queuing up for resource
Description
This counter counts the number of downlink EGPRS2-A TBF's releasing TBF during queuing. 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 counter increments. The measurement point is A, as shown in Figure 92-53.

92-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 92-53 Releasing Downlink EGPRS TBF

Unit
Times

92-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93

Up Link EGPRS2A TBF Statistic

Table of Contents
C901870001 Number of Uplink EGPRS2-A TBF Establishment Failure Due to Channel Allocation Failure........................................................................................93-4 C901870002 Number of Uplink EGPRS2-A TBF Establishment Failures Due to Abis Congestion .......................................................................................................93-5 C901870003 Number of Uplink EGPRS2-A TBF Establishment Failures Due to RR Congestion...............................................................................................................93-6 C901870004 Number of uplink EGPRS2-A TBF establishment failures due to UPU resource congestion .................................................................................................93-8 C901870005 Number of Uplink EGPRS2-A TBF EST Channel Allocation Success ..93-9 C901870006 Number of Failed Uplink EGPRS2-A TBF Establishments Due to Channel Activation Failure...................................................................................... 93-11 C901870007 Number of Failed Uplink EGPRS2-A TBF Establishments Due to BTS Connection Failure ................................................................................................. 93-11 C901870008 Number of Uplink EGPRS2-A TBF Establishment Failure Due to BIU Connection Failure .................................................................................................93-12 C901870009 Number of Uplink EGPRS2-A TBF Channel Activation and Connection Success...............................................................................................93-13 C901870010 Number of Uplink EGPRS2-A TBF Establishment Failure Due to Not Receiving PIA.........................................................................................................93-14 C901870011 Number of Uplink EGPRS2-A TBF Reallocation Requests Due to Downlink TBF Establishment..................................................................................93-14 C901870012 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to Channel Allocation Failure for Downlink TBF Establishment........................93-15 C901870013 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to Abis Congestion for Downlink TBF Establishment .......................................93-16 C901870014 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to RR Congestion for Downlink TBF Establishment.........................................93-17 C901870015 Number of uplink EGPRS2-A TBF resource reallocation failure due to UPU resource congestion as downlink TBF establishment .....................................93-18 C901870016 Number of Uplink EGPRS2-A TBF Resource Reallocation Success of Channel..............................................................................................................93-18 C901870017 Number of Allocated PDTCH for Uplink EGPRS2-A TBF Resource Reallocation Due to Downlink TBF Establishment ..................................................93-19

93-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901870018 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Downlink TBF Establishment Caused by Channel Activation Failure ......................93-20 C901870019 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to BTS Connection Failure for Downlink TBF Establishment ..............................................93-21 C901870020 Number of Uplink EGPRS2-A TBF Reallocation Failure for Downlink TBF Establishment Caused by BIU Connection Failure ..........................................93-22 C901870021 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Activation and Connection for Downlink TBF Establishment ...................................93-22 C901870022 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Downlink TBF Establishment..................................................................................93-23 C901870023 Number of Uplink EGPRS2-A TBF Reallocation Success Due to Downlink TBF Establishment..................................................................................93-24 C901870024 Number of Uplink EGPRS2-A TBF Reallocation Requests Due to LLC Transmission ..................................................................................................93-24 C901870025 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Channel Allocation Failure for LLC Transmission....................................................93-25 C901870026 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Abis Congestion for LLC Transmission...........................................................................93-26 C901870027 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to RR Congestion for LLC Transmission...........................................................................93-27 C901870028 Number of uplink EGPRS2-A TBF reallocation failure due to UPU resource congestion for LLC transmission ..............................................................93-28 C901870029 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Allocation for LLC Transmission .............................................................................93-29 C901870030 Number of Uplink EGPRS2-A TBF Reallocation Due to LLC Transmission..........................................................................................................93-29 C901870031 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Channel Activation Failure for LLC Transmission....................................................93-30 C901870032 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to BTS Connection Failure for LLC Transmission ...............................................................93-31 C901870033 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to BIU Connection Failure for LLC Transmission ...............................................................93-31 C901870034 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Activation and Connection for LLC Transmission....................................................93-32 C901870035 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to LLC Transmission..........................................................................................................93-32 C901870036 Number of Uplink EGPRS2-A TBF Reallocation Success Due to LLC Transmission..........................................................................................................93-32 C901870037 Number of Uplink EGPRS2-A TBF Reallocation Requests Due to Resourece Request................................................................................................93-33 C901870038 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Database Allocation Failure for Resource Request.................................................93-33 C901870039 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to Abis Congestion for Resource Request.......................................................93-34

93-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

C901870040 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to RR Congestion for Resource Request ........................................................93-34 C901870041 Number of uplink EGPRS2-A TBF reallocation failure due to UPU resource congestion for resource request...............................................................93-35 C901870042 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Allocation for Resource Request ............................................................................93-35 C901870043 Number of PDTCH Reallocated for Uplink EGPRS2-A TBF Triggered by Resource Request.............................................................................................93-36 C901870044 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Resource Request Caused by Channel Activation Failure ......................................93-36 C901870045 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to BTS Connection Failure for Resource Request ..............................................................93-37 C901870046 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Resource Request Caused by BIU Connection Failure...........................................93-37 C901870047 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Activation and Connection for Resource Request...................................................93-38 C901870048 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Resource Request..................................................................................................93-38 C901870049 Number of Uplink EGPRS2-A TBF Reallocation Success Due to Resource Request..................................................................................................93-38 C901870050 Number of Uplink EGPRS2-A TBF Release Due to Flush LLC ..........93-39 C901870051 Number of Uplink EGPRS2-A TBF Release Due to Suspend Requests................................................................................................................93-39 C901870052 Number of Uplink EGPRS2-A TBF Forced Release by CS ................93-40 C901870053 Number of Uplink EGPRS2-A TBF Normal Release Due to User Plane Requests......................................................................................................93-40 C901870054 Number of Uplink EGPRS2-A TBF Abnormal Release Due to Other Reason ..................................................................................................................93-40 C901870055 Number of Uplink EGPRS2-A TBF Release Due to NSVC Problem ..93-41 C901870056 Number of Uplink EGPRS2-A TBF Release Due to BVC Problem .....93-41 C901870057 Number of Uplink EGPRS2-A TBF Release Due to Other Reason ....93-41 C901870058 Number of Uplink EGPRS2-A TBF Preempting Resource .................93-42 C901870059 Number of Instances Preempted by Uplink EGPRS2-A TBF .............93-42 C901870060 Number of Uplink EGPRS2-A TBF Queuing Up for Resource............93-43 C901870061 Number of Uplink EGPRS2-A TBF Successfully Getting Resource Through Queuing ...................................................................................................93-43 C901870062 Number of Uplink EGPRS2-A TBF Released When Queuing Up for Resource................................................................................................................93-43 C901870063 Times of Uplink EGPR2A TBF Requesting DLDC Resources ............93-44 C901870064 Times of Allocating Uplink DLDC Resources for EGPRS2A TBF ......93-44

93-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

93.1 C901870001 Number of Uplink EGPRS2-A TBF Establishment Failure Due to Channel Allocation Failure
Description
The counter counts the number of EGPRS2-A UL TBF establishment channel allocation failures. It involves the number of allocation failures caused by PDCH, Abis, and PCU having no available resource or in abnormal status. The counter collects information about the frequency of channel allocation failures when the system attempts to establish EGPRS2-A UL TBFs.

Measurement Point
This counter increments in the following three cases: 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 measurement point is A, as shown in Figure 93-1.
Figure 93-1 Updated of Allocation Failures after Receiving CCCH Request

When PS control plane receives a PCCCH request from MS, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 93-2.
Figure 93-2 Updated of Allocation Failures after Receiving PCCCH Request

When MS has already established a DL EGPRS2-A 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 93-3.
93-4

SJ-20110531095035-015|2013-04-25 (R1.7)

ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

Figure 93-3 Updated of Allocation Failures (DL EGPRS2-A TBF Exists)

Unit
Times

93.2 C901870002 Number of Uplink EGPRS2-A TBF Establishment Failures Due to Abis Congestion
Description
The counter records the number of DB resource application failure when attempting UL EGPRS2-A TBF establishment due to Abis congestion. This counter is used to find out the number of DB resource application failure when attempting UL EGPRS2-A TBF establishment due to Abis congestion.

Measurement Point
The counter accumulates at the following three time points: 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 point is A, as shown inFigure 93-4.
Figure 93-4 - DB Resource Requests Failure Due To Abis Congestion (CCCH)

If PS control panel receives channel requests from MS on CCCH and fails to apply for DB resource due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 93-5.

93-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 93-5 - DB Resource Requests Failure Due To Abis Congestion (PCCCH)

If PS control panel receives UL assignment request messages from PS user plane on CCCH and fails to apply for DB resource due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 93-6.
Figure 93-6 - DB Resource Requests Failure Due To Abis Congestion (DL EGPRS2-A TBF Already Established)

Unit
Times

93.3 C901870003 Number of Uplink EGPRS2-A TBF Establishment Failures Due to RR Congestion
Description
The counter records the number of DB resource request failure when attempting UL EGPRS2-A 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. This counter is used to find out the number of DB resource application failure when attempting UL EGPRS2-A TBF establishment due to RR congestion.

Measurement Point
The counter accumulates at the following three time points:

93-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

If PS control plane receives channel requests from MS on CCCH and fails to apply for DB resource due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 93-7.
Figure 93-7 - DB Resource Requests Failure Due To RR Congestion (CCCH)

If PS control panel receives channel requests from MS on CCCH and fails to apply for DB resource due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 93-8.
Figure 93-8 - DB Resource Requests Failure Due To RR Congestion (PCCCH)

If PS control panel receives UL assignment request messages from PS user plane on CCCH and fails to apply for DB resource due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 93-9.
Figure 93-9 - DB Resource Requests Failure Due To Abis Congestion (DL EGPRS2-A TBF Already Established)

Unit
Times
93-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

93.4 C901870004 Number of uplink EGPRS2-A TBF establishment failures due to UPU resource congestion
Description
The counter records the number of DB resource application failure when attempting UL EGPRS2-A TBF establishment due to UPU resource congestion. This counter is used to find out the number of DB resource application failure when attempting UL EGPRS2-A TBF establishment due to UPU resource congestion.

Measurement Point
The counter accumulates at the following three time points: l If PS control plane receives channel requests from MS on CCCH and fails to apply for DB resource due to UPU resource congestion, the counter increments. The measurement point is A, as shown in Figure 93-10.
Figure 93-10 DB Resource Requests Failure Due To UPU resource Congestion (CCCH)

If PS control panel receives channel requests from MS on PCCCH and fails to apply for DB resource due to UPU resource congestion, the counter increments. The measurement point is A, as shown in Figure 93-11.

93-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

Figure 93-11 - DB Resource Requests Failure Due To Abis Congestion (PCCCH)

If PS control panel receives UL assignment request messages from PS user plane on CCCH (DL EGPRS2-A TBF already established) and fails to apply for DB resource due to UPU resource congestion, the counter increments. The measurement point is A, as shown in Figure 93-12.
Figure 93-12 - DB Resource Requests Failure Due To DPPB-DSP Congestion (DL EGPRS2-A TBF Already Established)

Unit
Times

93.5 C901870005 Number of Uplink EGPRS2-A TBF EST Channel Allocation Success
Description
This counter counts the number of DB resource request successes when attempting UL EGPRS2-A TBF establishment. This counter is used to find out the number of DB resource request successes when attempting UL EGPRS2-A TBF establishment.

93-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter accumulates at the following three time points: 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 shown inFigure 93-13.
Figure 93-13 - DB Resource Request Successes (CCCH)

If PS control panel receives channel requests from MS on PCCCH and succeed in applying for DB resource, the counter increments. The measurement point is A, as shown inFigure 93-14.
Figure 93-14 - DB Resource Request Successes (PCCCH)

If only EGPRS2-A is supported in the network, PS control plane receives EGPRS2-A channel request on CCCH or on PCCCH from MS, and DB resource request succeeds, the counter increments.

Unit
Times

93-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

93.6 C901870006 Number of Failed Uplink EGPRS2-A TBF Establishments Due to Channel Activation Failure
Description
This counter counts the number of PDTCH activate failure when establishing UL EGPRS2-A TBF. This counter is used to find out the number of PDTCH activate failure when establishing UL EGPRS2-A TBF (including initially establish UL TBF and establish UL TBF when DL TBF exists).

Measurement Point
The counter accumulates at the following two time points: l When BSC receives PDTCH channel activate failure message reported by BTS, the counter increments. The measurement point is A, as shown inFigure 93-15.
Figure 93-15 - PDCH Activation Failure

When 'wait for PDTCH channel activation and connection response' counter times out and BSC fails to receive PDTCH activate response message reported by BTS, this counter increments.

Unit
Times

93.7 C901870007 Number of Failed Uplink EGPRS2-A TBF Establishments Due to BTS Connection Failure
Description
This counter counts the number of failure to establish UL EGPRS2-A TBF due to BTS connection failure.

93-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This counter is used to find out the number of UL EGPRS2-A TBF establishment failure (including initially establish UL TBF and establish UL TBF when DL TBF exists) due to BTS connection failure.

Measurement Point
The counter accumulates at the following two time points: l When PS control plane receives connection failure message reported by connection module due to BTS connection failure, the counter increments. The measurement point is A, as shown in Figure 93-16.
Figure 93-16 - Connection Failed due to BTS Connection Failure

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

93.8 C901870008 Number of Uplink EGPRS2-A TBF Establishment Failure Due to BIU Connection Failure
Description
This counter counts the number of failure to establish UL EGPRS2-A TBF due to BIU connection failure. This counter is used to find out the number of UL EGPRS2-A TBF establishment failure (including initially establish UL TBF and establish UL TBF when DL TBF exists) due to BIU connection failure.

Measurement Point
When PS control plane receives connection failure message reported by connection modules due to BIU connection failure, the counter increments. The measurement point is A, as shown inFigure 93-17.
93-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

Figure 93-17 - Connection Failed Due To BIU Connection Failure

Unit
Times

93.9 C901870009 Number of Uplink EGPRS2-A TBF Channel Activation and Connection Success
Description
This counter counts the number of channel activate and connection successes when establishing UL EGPRS2-A TBF. This counter is used to find out the number of channel activate and connection successes when establishing UL EGPRS2-A TBF.

Measurement Point
When PS control plane receives channel activate response message reported by BTS and connection successes acknowledgement message reported by connection module, the counter increments. The measurement point is A, as shown inFigure 93-18.
Figure 93-18 - Resource Application Failure Due To Abis Congestion (Resource Adjustment)

93-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

93.10 C901870010 Number of Uplink EGPRS2-A TBF Establishment Failure Due to Not Receiving PIA
Description
This counter counts the number of failure to send immediate assignment message to MS when establishing UL GPRS TBF.

Measurement Point
The counter accumulates at the following two time points: l l When PS control plane receives immediate assignment failure message reported by BTS, the counter increments. When 'wait for immediate assignment and sending indication' counter times out and BSC fails to receive immediate assignment and sending indication message, the counter increments.

Unit
Times

93.11 C901870011 Number of Uplink EGPRS2-A TBF Reallocation Requests Due to Downlink TBF Establishment
Description
The counter counts the number of RS UL TBF resource reallocation requests due to DL TBF establishment. The counter collects information about the frequency of EGPRS2-A UL TBF resource reallocation requests.

Measurement Point
When MS has already established an UL EGPRS2-A TBF, if PS control plane receives a DL TBF assignment message from PS user plane, this counter increments. The measurement point is A, as shown in Figure 93-19.

93-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

Figure 93-19 Updated of Number of EGPRS2-A UL TBF Resource Reallocation Requests due to DL TBF Establishment

Unit
Times

93.12 C901870012 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to Channel Allocation Failure for Downlink TBF Establishment
Description
If MS has already established an UL EGPRS2-A TBF and it needs to establish a DL TBF on PACCH, PS control plane should apply to database for resources. The counter counts the number of UL resource reallocation failures of channel allocation caused by failed DL TBF establishment allocation. The counter collects information about the frequency of EGPRS2-A UL resource reallocation failures of channel allocation caused by failed DL TBF establishment allocation.

Measurement Point
When MS has already established an UL EGPRS2-A TBF, if PS control plane receives a 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 93-20 Updated of Allocation Failures after Receiving DL TBF Assignment Message

93-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

93.13 C901870013 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to Abis Congestion for Downlink TBF Establishment
Description
In the situation when UL EGPRS2-A 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. This counter is used to find out the number of UL EGPRS2-A TBF reallocation failure due to Abis congestion.

Measurement Point
In the situation when UL EGPRS2-A 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 93-21.
Figure 93-21 - Database Application Failure Due To Abis Congestion

Unit
Times

93-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

93.14 C901870014 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to RR Congestion for Downlink TBF Establishment
Description
In the situation when UL EGPRS2-A 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. 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. This counter is used to find out the number of UL EGPRS2-A TBF reallocation failure due to RR congestion.

Measurement Point
In the situation when UL EGPRS2-A TBF is established, PS control plane receives DL assignment request message from PS user plane, and DB resource request fails due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 93-22.
Figure 93-22 - Database Application Failure due to RR Congestion

Unit
Times

93-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

93.15 C901870015 Number of uplink EGPRS2-A TBF resource reallocation failure due to UPU resource congestion as downlink TBF establishment
Description
In the situation when UL EGPRS2-A 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 UPU resource resource congestion. This counter is used to find out the number of UL EGPRS2-A TBF reallocation failure due to UPU resource congestion.

Measurement Point
In the situation when UL EGPRS2-A TBF is established, PS control plane receives DL assignment request message from PS user plane, and DB resource request fails due to UPU resource congestion, the counter increments. The measurement point is A, as shown inFigure 93-23.
Figure 93-23 - Database Application Failure due to UPU resource Congestion

Unit
Times

93.16 C901870016 Number of Uplink EGPRS2-A TBF Resource Reallocation Success of Channel
Description
The counter records the number of successful DL TBF establishment on PACCH when UL EGPRS2-A TBF is already established. This counter is used to find out the number of DL EGPRS2-A TBF reallocation successes.
93-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

Measurement Point
In the situation when UL EGPRS2-A 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 93-24.
Figure 93-24 Successful Resource Application

Unit
Times

93.17 C901870017 Number of Allocated PDTCH for Uplink EGPRS2-A TBF Resource Reallocation Due to Downlink TBF Establishment
Description
The counter records the number of successful allocated PDTCH when UL EGPRS2-A TBF is successfully reallocated. This counter is used to find out the number of successful allocated PDTCH when UL EGPRS2-A TBF is successfully reallocated.

Measurement Point
In the situation when UL EGPRS2-A 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 93-25.

93-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 93-25 - Successful Resource Application

Unit
Times

93.18 C901870018 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Downlink TBF Establishment Caused by Channel Activation Failure
Description
The counter records the number of PDTCH activate failure during UL EGPRS2-A TBF resource reallocation. This counter is used to find out the number of PDTCH activate failure during UL EGPRS2-A TBF resource reallocation.

Measurement Point
The measurement is taken at two time points listed below: l When BSC receives PDTCH channel activate failure message from BTS, the counter increments. The measurement point is A, as shown inFigure 93-26 .
Figure 93-26 - PDTCH Activation Failure

93-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive PDTCH channel activate response message from BTS, the counter increments.

Unit
Times

93.19 C901870019 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to BTS Connection Failure for Downlink TBF Establishment
Description
The counter records the number of BTS connection failure during UL EGPRS2-A TBF resource reallocation. This counter is used to find out the number of BTS connection failure during UL EGPRS2-A TBF resource reallocation.

Measurement Point
The measurement is taken at two time points listed below: l When PS control plane receives connection failure message from connection module due to BTS connection failure, the counter increments. The measurement point is A, as shown inFigure 93-27 .
Figure 93-27 - Connection Failed due to BTS Connection Failure

When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive connection success message from connection module, the counter increments.

Unit
Times

93-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

93.20 C901870020 Number of Uplink EGPRS2-A TBF Reallocation Failure for Downlink TBF Establishment Caused by BIU Connection Failure
Description
The counter records the number of BIU connection failure during UL EGPRS2-A TBF resource reallocation. This counter is used to find out the number of BIU connection failure during UL EGPRS2-A 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 93-28.
Figure 93-28 - Connection Failed Due To BIU Connection Failure

Unit
Times

93.21 C901870021 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Activation and Connection for Downlink TBF Establishment
Description
The counter records the number of channel activate and connection successes during UL EGPRS2-A TBF resource reallocation.
93-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

This counter is used to find out the number of channel activate and connection successes during UL EGPRS2-A TBF resource reallocation.

Measurement Point
When PS control plane receives channel activate ack message and connection success ack message from connection module due to BIU connection failure, the counter increments. The measurement point is A, as shown inFigure 93-29.
Figure 93-29 - Resource Application Failure Due To Abis Congestion (Resource Adjustment)

Unit
Times

93.22 C901870022 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Downlink TBF Establishment
Description
This counter counts the number of times that required resources are not obtained from the database during uplink EGPRS2-A TBF resource reallocation.

Measurement Point
This counter is incremented each time the PS control plane, upon receiving a resource adjustment request from the PS user plane, fails to obtain resources from the database.

Unit
Times

93-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

93.23 C901870023 Number of Uplink EGPRS2-A TBF Reallocation Success Due to Downlink TBF Establishment
Description
This counter counts the number of times that required resources are successfully obtained from the database during uplink EGPRS2-A TBF resource reallocation.

Measurement Point
This counter is incremented each time the PS control plane, upon receiving a resource adjustment request from the PS user plane and downlink pre-establishment message, successfully obtains resources from the database in the case of successful connection or no connection required.

Unit
Times

93.24 C901870024 Number of Uplink EGPRS2-A TBF 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 UL EGPRS2-A TBF transmission. This counter collects information about the frequency of resource reallocation requests received by PS control plane during the UL EGPRS2-A TBF transmission.

Measurement Point
When PS control plane receives a resource reallocation request from PS user plane, if the current UL EGPRS2-A TBF exists, this counter increments. The measurement point is A, as shown in Figure 93-30.

93-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

Figure 93-30 Updated of Number of EGPRS2-A DL TBF Resource Reallocation Requests due to LLC Transmission

Unit
Times

93.25 C901870025 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Channel Allocation Failure for LLC Transmission
Description
During the UL EGPRS2-A 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. This counter collects information about the frequency of failed resource allocations during the UL EGPRS2-A 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 93-31.
Figure 93-31 Updated of Number of EGPRS2-A DL TBF Resource Reallocation Failure of channel allocation due to LLC Transmission

93-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

93.26 C901870026 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Abis Congestion for LLC Transmission
Description
During UL EGPRS2-A 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 EGPRS2-A TBF transmission process. 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 EGPRS2-A TBF transmission process.

Measurement Point
When PS control plane receives resource reallocation message from PS user plane, and DB resource request fails due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 93-32.
Figure 93-32 - Resource Application Failure Due To Abis Congestion

Unit
Times

93-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

93.27 C901870027 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to RR Congestion for LLC Transmission
Description
During UL EGPRS2-A 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 radio resource congestion after PS control plane receiving resource reallocation request during UL EGPRS2-A TBF transmission process. There are three causes leading to RR congestion: MS per channel (reaches its maximum), TAI/TFI (not available), and no PDTCH. 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 EGPRS2-A TBF transmission process.

Measurement Point
When PS control plane receives resource reallocation message from PS user plane, and DB resource request fails due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 93-33 .
Figure 93-33 - Resource Application Failure Due To RR Congestion (Resource Adjustment)

Unit
Times

93-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

93.28 C901870028 Number of uplink EGPRS2-A TBF reallocation failure due to UPU resource congestion for LLC transmission
Description
During UL EGPRS2-A 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 UPU resource congestion after PS control plane receiving resource reallocation request during UL EGPRS2-A TBF transmission process. This counter is used to find out DB resource request failure due to UPU resource congestion after PS control plane receiving resource reallocation request during UL EGPRS2-A TBF transmission process.

Measurement Point
When PS control plane receives resource reallocation message from PS user plane, and DB resource request fails due to UPU resource congestion, the counter increments. The measurement point is A, as shown in Figure 93-34.
Figure 93-34 - Resource Application Failure Due To UPU resource Congestion (Resource Adjustment)

Unit
Times

93-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

93.29 C901870029 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Allocation for LLC Transmission
Description
During UL EGPRS2-A 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 successes after PS control plane receiving resource reallocation request during UL EGPRS2-A TBF transmission process. This counter is used to find out DB resource request success due after PS control plane receiving resource reallocation request during UL EGPRS2-A TBF transmission process.

Measurement Point
When PS control plane receives resource reallocation message from PS user plane, and DB resource request succeeds, the counter increments. The measurement point is A, as shown inFigure 93-35.
Figure 93-35 Release Request Due To Flush LL

Unit
Times

93.30 C901870030 Number of Uplink EGPRS2-A TBF Reallocation Due to LLC Transmission
Description
During UL EGPRS2-A 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 successfully allocated PDTCH after PS control plane receiving resource reallocation requests during UL EGPRS2-A TBF. This counter is used to find out the number of successful allocated PDTCH when UL EGPRS2-A TBF is successfully reallocated.
93-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When PS control plane receives resource reallocation message from PS user plane, and DB resource request succeeds, the counter increments. The measurement point is A, as shown inFigure 93-36.
Figure 93-36 - Release Request Due To Flush LL

Unit
Times

93.31 C901870031 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Channel Activation Failure for LLC Transmission
Description
This counter counts PDTCH activation failures that occur during resource adjustment after the BSC receives a resource adjustment request in the case of uplink EGPRS2-A TBF.

Measurement Point
l l This counter is incremented each time the BSC receives a PDTCH activation failure message from a BTS. This counter is incremented if the BSC does not receive a PDTCH channel activation acknowledge message from a BTS before the timer for PDTCH activation and connection acknowledgement expires.

Unit
Times

93-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

93.32 C901870032 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to BTS Connection Failure for LLC Transmission
Description
This counter counts connection failures that occur during resource adjustment due to BTS connection failure after the BSC receives a resource adjustment request in the case of uplink EGPRS2-A TBF.

Measurement Point
l l This counter is incremented each time the PS control plane receives a connection failure message with the cause of BTS connection failure from the connection module. This counter is incremented if the BSC does not receive a connection success acknowledge message from the connection module before the timer for PDTCH activation and connection acknowledgement expires.

Unit
Times

93.33 C901870033 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to BIU Connection Failure for LLC Transmission
Description
This counter counts connection failures that occur during resource adjustment due to BIU connection failure after the BSC receives a resource adjustment request in the case of uplink EGPRS2-A TBF.

Measurement Point
This counter is incremented each time the PS control plane receives a connection failure message with the cause of BIU connection failure from the connection module.

Unit
Times

93-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

93.34 C901870034 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Activation and Connection for LLC Transmission
Description
This counter counts the number of times that channel activation and connection succeeds during resource adjustment after the RANPS module receives a resource adjustment request in the case of uplink EGPRS2-A TBF.

Measurement Point
This counter is incremented each time the PS control plane receives a channel activation acknowledge message from a BTS and a connection success acknowledge message from the connection module.

Unit
Times

93.35 C901870035 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to LLC Transmission
Description
This counter counts uplink EGPRS2-A TBF reallocation failures due to LLC transmission. This counter is not used in this version.

Measurement Point
None

Unit
Times

93.36 C901870036 Number of Uplink EGPRS2-A TBF Reallocation Success Due to LLC Transmission
Description
This counter counts the number of times that required resources are successfully obtained from the database during uplink EGPRS2-A TBF resource adjustment.
93-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

Measurement Point
This counter is incremented each time the PS control plane, upon receiving a resource adjustment request and downlink pre-establishment message, successfully obtains resources from the database in the case of successful connection or no connection required.

Unit
Times

93.37 C901870037 Number of Uplink EGPRS2-A TBF Reallocation Requests Due to Resourece Request
Description
This counter counts the number of times that the PS control plane receives a resource request message from a mobile station in the case of uplink EGPRS2-A TBF.

Measurement Point
This counter is incremented each time the PS control plane receives a resource allocation request from PS user plane.

Unit
Times

93.38 C901870038 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Database Allocation Failure for Resource Request
Description
This counter counts the number of times that the PS control plane, upon receiving a resource request message from a mobile station in the case of uplink EGPRS2-A TBF, fails to obtain resources from the database.

Measurement Point
This counter is incremented each time the PS control plane, upon receiving a resource reallocation request from the PS user plane, fails to obtain resources from the database.

Unit
Times
93-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

93.39 C901870039 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to Abis Congestion for Resource Request
Description
This counter counts the number of times that the PS control plane, upon receiving a resource request message from a mobile station in the case of uplink EGPRS2-A TBF, fails to obtain resources from the database due to oversubscription of Abis resources.

Measurement Point
This counter is incremented each time the PS control plane, upon receiving resource request message from the PS user plane, fails to obtain resources from the database due to oversubscription of Abis resources.

Unit
Times

93.40 C901870040 Number of Uplink EGPRS2-A TBF Resource Reallocation Failure Due to RR Congestion for Resource Request
Description
This counter counts the number of times that the PS control plane, upon receiving a resource request message from a mobile station in the case of uplink EGPRS2-A TBF, fails to obtain resources from the database due to oversubscription of radio resources.

Measurement Point
The probable causes of radio resource oversubscription are: MS per channel (The number of mobile stations per channel reaches the upper limit), TAI/TFI (No TAI and TFI is available for allocation) , and no PDCH (No PS channel is available for allocation). This counter is incremented each time the PS control plane, upon receiving resource request message from the PS user plane, fails to obtain resources from the database due to oversubscription of radio resources.

Unit
Times

93-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

93.41 C901870041 Number of uplink EGPRS2-A TBF reallocation failure due to UPU resource congestion for resource request
Description
This counter counts the number of times that the PS control plane, upon receiving a resource request message from a mobile station in the case of uplink EGPRS2-A TBF, fails to obtain resources from the database due to UPU resource congestion.

Measurement Point
This counter is incremented each time the PS control plane, upon receiving resource request message from the PS user plane, fails to obtain resources from the database due to UPU resource congestion.

Unit
Times

93.42 C901870042 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Allocation for Resource Request
Description
This counter counts the number of times that the PS control plane, upon receiving a resource request message from a mobile station in the case of uplink EGPRS2-A TBF, successfully obtains resources from the database.

Measurement Point
This counter is incremented each time the PS control plane, upon receiving resource request message from the PS user plane, successfully obtains resources from the database.

Unit
Times

93-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

93.43 C901870043 Number of PDTCH Reallocated for Uplink EGPRS2-A TBF Triggered by Resource Request
Description
This counter counts the number of PDTCHs that the database successfully allocated after the PS control plane receives a resource request message from a mobile station in the case of uplink EGPRS2-A TBF.

Measurement Point
This counter is incremented each time the PS control plane, upon receiving resource request message from the PS user plane, successfully obtains resources from the database.

Unit
Times

93.44 C901870044 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Resource Request Caused by Channel Activation Failure
Description
This counter counts PDTCH activation failures that occur during uplink TBF resource reallocation after the PS control plane receives a resource request message from a mobile station in the case of uplink EGPRS2-A TBF.

Measurement Point
l l This counter is incremented each time the BSC receives a PDTCH activation failure message from a BTS. This counter is incremented if the BSC does not receive a PDTCH channel activation acknowledge message from a BTS before the timer for PDTCH activation and connection acknowledgement expires.

Unit
Times

93-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

93.45 C901870045 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to BTS Connection Failure for Resource Request
Description
This counter counts connection failures that occur due to BTS connection failure during uplink TBF resource reallocation after the PS control plane receives a resource request message from a mobile station in the case of uplink EGPRS2-A TBF.

Measurement Point
l l This counter is incremented each time the PS control plane receives a connection failure message with the cause of BTS connection failure from the connection module. This counter is incremented if the BSC does not receive a connection success acknowledge message from the connection module before the timer for PDTCH activation and connection acknowledgement expires.

Unit
Times

93.46 C901870046 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Resource Request Caused by BIU Connection Failure
Description
This counter counts connection failures that occur due to BIU connection failure during uplink TBF resource reallocation after the PS control plane receives a resource request message from a mobile station in the case of uplink EGPRS2-A TBF.

Measurement Point
This counter is incremented each time the PS control plane receives a connection failure message with the cause of BIU connection failure from the connection module.

Unit
Times

93-37 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

93.47 C901870047 Number of Uplink EGPRS2-A TBF Reallocation Success of Channel Activation and Connection for Resource Request
Description
This counter counts the number of times that PDTCH activation and connection succeed during uplink TBF resource reallocation after the PS control plane receives a resource request message from a mobile station in the case of uplink EGPRS2-A TBF.

Measurement Point
This counter is incremented each time the PS control plane receives a channel activation acknowledge message from a BTS and a connection success acknowledge message from the connection module.

Unit
Times

93.48 C901870048 Number of Uplink EGPRS2-A TBF Reallocation Failure Due to Resource Request
Description
This counter counts the number of times that an uplink EGPRS2-A TBF reallocation fails due to a resource request.

Measurement Point
This counter is incremented each time the PS control plane, upon receiving a resource request, fails to obtain resources from the database.

Unit
Times

93.49 C901870049 Number of Uplink EGPRS2-A TBF Reallocation Success Due to Resource Request
Description
This counter counts the number of times that the PS control plane, upon receiving a resource request, successfully obtains resources from the database.
93-38 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

Measurement Point
This counter is incremented each time the PS control plane, upon receiving a resource request, successfully obtains resources from the database in the case of connection success or no connection required.

Unit
Times

93.50 C901870050 Number of Uplink EGPRS2-A TBF Release Due to Flush LLC
Description
This counter counts uplink EGPRS2-A TBF releases due to FLUSH LLC.

Measurement Point
This counter is incremented each time the PS control plane of BSC receives FLUSH message from SGSN and release is executed when UL EGPRS2-A TBF is established.

Unit
Times

93.51 C901870051 Number of Uplink EGPRS2-A TBF Release Due to Suspend Requests
Description
This counter counts uplink EGPRS2-A TBF releases due to suspend request.

Measurement Point
This counter is incremented each time PS control plane of BSC receives SUSPEND message from SGSN and release is executed when UL EGPRS2-A TBF is established.

Unit
Times

93-39 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

93.52 C901870052 Number of Uplink EGPRS2-A TBF Forced Release by CS

Description
This counter counts uplink EGPRS2-A TBF releases due to PDCH REL.

Measurement Point
This counter is incremented each time the PS control plane receives PDCH RELEASE message from the CS control plane in the case of uplink EGPRS2-A TBF.

Unit
Times

93.53 C901870053 Number of Uplink EGPRS2-A TBF Normal Release Due to User Plane Requests
Description
This counter counts uplink EGPRS2-A TBF releases due to MAC requested normal release.

Measurement Point
This counter is incremented each time the PS control plane receives NORMAL RELEASE REQUEST message, from the PS user plane in the case of uplink EGPRS2-A TBF.

Unit
Times

93.54 C901870054 Number of Uplink EGPRS2-A TBF Abnormal Release Due to Other Reason
Description
This counter counts uplink EGPRS2-A TBF releases due to MAC requested abnormal release.

Measurement Point
This counter is incremented each time the PS control plane receives ABNORMAL RELEASE REQUEST message, from the PS user plane in the case of uplink EGPRS2-A TBF.
93-40 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

Unit
Times

93.55 C901870055 Number of Uplink EGPRS2-A TBF Release Due to NSVC Problem
Description
This counter counts uplink EGPRS2-A TBF releases due to NSVC unavailability.

Measurement Point
This counter is incremented each time the PS control plane receives a release request message to release PS control plane module, which contains the release cause of NSVC unavailability, from the database in the case of uplink EGPRS2-A TBF.

Unit
Times

93.56 C901870056 Number of Uplink EGPRS2-A TBF Release Due to BVC Problem
Description
This counter counts uplink EGPRS2-A TBF releases due to BVC unavailability.

Measurement Point
This counter is incremented each time the RANPS module receives a release request message to release PS control plane module, which contains the release cause of BVC unavailability, from the database in the case of uplink EGPRS2-A TBF.

Unit
Times

93.57 C901870057 Number of Uplink EGPRS2-A TBF Release Due to Other Reason
Description
This counter counts uplink EGPRS2-A TBF releases due to the other reasons.

93-41 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
This counter is incremented each time the PS control plane receives a release request message , which contains the other release reasons, from the PS user plane in the case of uplink EGPRS2-A TBF.

Unit
Times

93.58 C901870058 Number of Uplink EGPRS2-A TBF Preempting Resource

Description
This counter counts the number of times that resource preemption occurs during uplink EGPRS2-A TBF.

Measurement Point
This counter is incremented each time TBF resource preemption occurs after successful resource request during uplink EGPRS2-A TBF establishment or resource adjustment.

Unit
Times

93.59 C901870059 Number of Instances Preempted by Uplink EGPRS2-A TBF

Description
This counter counts instances preempted by uplink EGPRS2-A TBF.

Measurement Point
This counter adds the number of preempted instances to the current counter value each time TBF resource preemption occurs after successful resource request during uplink EGPRS2-A TBF establishment or resource adjustment.

Unit
Times

93-42 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 93 Up Link EGPRS2A TBF Statistic

93.60 C901870060 Number of Uplink EGPRS2-A TBF Queuing Up for Resource

Description
This counter counts the number of times that uplink EGPRS2-A TBF queuing is required.

Measurement Point
This counter is incremented each time uplink TBF queuing is required for QoS rate guarantee after successful resource request during uplink EGPRS2-A TBF establishment or resource adjustment.

Unit
Times

93.61 C901870061 Number of Uplink EGPRS2-A TBF Successfully Getting Resource Through Queuing
Description
This counter counts the number of times that uplink EGPRS2-A TBF successfully queues up for resources.

Measurement Point
This counter is incremented each time an instance to be queued, upon allocating resources to the user plane, successfully registered to the database.

Unit
Times

93.62 C901870062 Number of Uplink EGPRS2-A TBF Released When Queuing Up for Resource
Description
This counter counts the number of times that uplink EGPRS2-A TBF is released during queuing.

Measurement Point
This counter is incremented each time the instance is still queuing for resources when uplink EGPRS2-A TBF is released.
93-43 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

93.63 C901870063 Times of Uplink EGPR2A TBF Requesting DLDC Resources

Description
This counter counts the number of times that a channel request requires allocation of DLDC resources during uplink EGPRS2A TBF establishment in a cell.

Measurement Point
This counter is incremented each time a channel request requires allocation of DLDC resources during uplink EGPRS2A TBF establishment.

Unit
Times

93.64 C901870064 Times of Allocating Uplink DLDC Resources for EGPRS2A TBF
Description
This counter counts the number of times that DLDC resources are allocated after successful channel request during uplink EGPRS2A TBF establishment in a cell.

Measurement Point
This counter is incremented each time DLDC resources are allocated after successful channel request during uplink EGPRS2A TBF establishment.

Unit
Times

93-44 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 94

PS Handover Cause Measurement

Table of Contents
Overview ..................................................................................................................94-1 C901880001 Number of handover attempts due to uplink received strength.............94-1 C901880002 Number of handover attempts due to downlink received strength ........94-2 C901880003 Number of handover attempts due to uplink quality .............................94-3 C901880004 Number of handover attempts due to downlink quality.........................94-4 C901880005 Number of handover attempts due to uplink interference .....................94-4 C901880006 Number of handover attempts due to downlink interference ................94-5 C901880007 Number of handover attempts due to PBGT ........................................94-6 C901880008 Number of handover attempts due to large TA.....................................94-6 C901880009 Number of handover attempts due to uplink break up quickly ..............94-7 C901880010 Number of handover attempts due to macro-micro switch ...................94-8 C901880011 Number of handover attempts due to high traffic..................................94-9 C901880012 Number of handover attempts due to a good standard level in FDD adjacent cell .............................................................................................................94-9 C901880013 Number of handover attempts due to a good standard level in TDD adjacent cell ...........................................................................................................94-10 C901880014 Number of handover attempts due to PCCN...................................... 94-11

94.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. Statistic unit in this measurement is cell.

94.2 C901880001 Number of handover attempts due to uplink received strength

Statistics object
BSC
94-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 shown in Figure 94-1.
Figure 94-1 Measurement Point of Number of handover attempts due to uplink received strength

Unit
Times

94.3 C901880002 Number of handover attempts due to 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 measurement point is A, as shown in Figure 94-2.

94-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 94 PS Handover Cause Measurement

Figure 94-2 Measurement Point of Number of handover attempts due to downlink received strength

Unit
Times

94.4 C901880003 Number of handover attempts due to 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 94-3.
Figure 94-3 Measurement Point of Number of handover attempts due to uplink quality

Unit
Times

94-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

94.5 C901880004 Number of handover attempts due 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 94-4.
Figure 94-4 Measurement Point of Number of handover attempts due to downlink quality

Unit
Times

94.6 C901880005 Number of handover attempts due to 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 decision. If the handover decision indicates that handover is required and the handover is
94-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 94 PS Handover Cause Measurement

due to uplink interference, the counter increments. The measurement point is A, as shown in Figure 94-5.
Figure 94-5 Measurement Point of Number of handover attempts due to uplink interference

Unit
Times

94.7 C901880006 Number of handover attempts due 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 is A, as shown in Figure 94-6.
Figure 94-6 Measurement Point of Number of handover attempts due to downlink interference

94-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

94.8 C901880007 Number of handover attempts due 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 94-7.
Figure 94-7 Measurement Point of Number of handover attempts due to PBGT

Unit
Times

94.9 C901880008 Number of handover attempts due to large TA

Statistics object
BSC
94-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 94 PS Handover Cause Measurement

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. The measurement point is A, as shown in Figure 94-8.
Figure 94-8 Measurement Point of Number of handover attempts due to large TA

Unit
Times

94.10 C901880009 Number of handover attempts due 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 decision. If the handover decision indicates that handover is required and the handover is due to uplink fast fading, the counter increments. The measurement point is A, as shown in Figure 94-9.

94-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 94-9 Measurement Point of Number of handover attempts due to uplink break up quickly

Unit
Times

94.11 C901880010 Number of handover attempts due 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 increments. The measurement point is A, as shown in Figure 94-10.
Figure 94-10 Measurement Point of Number of handover attempts due to macro-micro switch

94-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 94 PS Handover Cause Measurement

Unit
Times

94.12 C901880011 Number of handover attempts due 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 point is A, as shown in Figure 94-11.
Figure 94-11 Measurement Point of Number of handover attempts due to high traffic

Unit
Times

94.13 C901880012 Number of handover attempts due to a good standard level in FDD adjacent cell
Statistics object
BSC
94-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 shown in Figure 94-12.
Figure 94-12 Measurement Point of Number of handover attempts due to a good standard level in FDD adjacent cell

Unit
Times

94.14 C901880013 Number of handover attempts due 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 shown in Figure 94-13.

94-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 94 PS Handover Cause Measurement

Figure 94-13 Measurement Point of Number of handover attempts due to a good standard level in TDD adjacent cell

Unit
Times

94.15 C901880014 Number of handover attempts due 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 point is A, as shown in Figure 94-14.
Figure 94-14 Measurement Point of Number of handover attempts due to PCCN

Unit
Times
94-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

94-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95

PS General Handover Measurement

Table of Contents
Overview ..................................................................................................................95-2 C901890001 Number of synchronous handover executions .....................................95-2 C901890002 Number of successful synchronous handovers....................................95-3 C901890003 Number of pre-synchronous handover executions...............................95-4 C901890004 Number of successful pre-synchronous handovers .............................95-5 C901890005 Number of asynchronous handover executions ...................................95-6 C901890006 Number of successful asynchronous handovers..................................95-7 C901890007 Number of normal handover executions ..............................................95-8 C901890008 Number of successful normal handovers .............................................95-9 C901890009 Number of optimised handover executions ........................................95-10 C901890010 Number of successful optimised handovers....................................... 95-11 C901890011 Number of Intra-BSC inter-cell handover out attempts .......................95-12 C901890012 Number of Intra-BSC inter-cell handover out executions....................95-12 C901890013 Number of successful Intra-BSC inter-cell handover out ....................95-13 C901890014 Number of Inter-BSC handover out attempts .....................................95-14 C901890015 Number of Inter-BSC handover out executions..................................95-15 C901890016 Number of successful Inter-BSC handover out ..................................95-16 C901890017 Number of handover in attempts .......................................................95-17 C901890018 Number of handover in executions ....................................................95-17 C901890019 Number of successful handover in.....................................................95-18 C901890020 Number of Intra-cell handover attempts.............................................95-19 C901890021 Number of Intra-Cell handover executions.........................................95-19 C901890022 Number of successful Intra-cell handovers ........................................95-20 C901890023 Number of invalid Intra-cell handovers...............................................95-20 C901890024 Number of 2G to FDD handover attempts .........................................95-21 C901890025 Number of 2G to FDD handover executions ......................................95-21 C901890026 Number of successful 2G to FDD handovers.....................................95-22 C901890027 Number of 2G to TDD handover attempts .........................................95-23 C901890028 Number of 2G to TDD handover executions ......................................95-24 C901890029 Number of successful 2G to TDD handovers.....................................95-24 C901890030 Number of 3G to 2G handover attempts ............................................95-25 C901890031 Number of 3G to 2G handover executions.........................................95-26 C901890032 Number of successful 3G to 2G handovers .......................................95-27 C901890033 Number of T12 expiry........................................................................95-27
95-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901890034 Number of PCCF received ................................................................95-28 C901890035 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause Create PFC Failure...............................................................................95-29 C901890036 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause PS Handover Target not allowed ..........................................................95-29 C901890037 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause PS Handover not Supported in Target BSS or Target System ...............95-30 C901890038 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause other reasons........................................................................................95-31 C901890039 Number of failure in optimised handover due to failure alloc resource ..............................................................................................................................95-32 C901890040 Number of failure in optimised handover due to PS handover not supported in target cell ...........................................................................................95-33

95.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. Statistic unit in this measurement is cell.

95.2 C901890001 Number of synchronous handover 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 shown in Figure 95-1.

95-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

Figure 95-1 Measurement Point of Number of synchronous handover executions

Unit
Times

95.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 95-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 measurement point is A, as shown in Figure 95-3.

95-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 95-2 Measurement Point of Number of successful synchronous handovers - (1)

Figure 95-3 Measurement Point of Number of successful synchronous handovers - (2)

Unit
Times

95.4 C901890003 Number of pre-synchronous 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
95-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

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 measurement point is A, as shown in Figure 95-4.
Figure 95-4 Measurement Point of Number of pre-synchronous handover executions

Unit
Times

95.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, and the counter increments. The measurement point is A, as shown in Figure 95-5. 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 95-6.

95-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 95-5 Measurement Point of Number of pre-synchronous handover successes - (1)

Figure 95-6 Measurement Point of Number of pre-synchronous handover successes - (2)

Unit
Times

95.6 C901890005 Number of asynchronous handover 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
95-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

same site. This counter is used to find out the frequency of the asynchronous handover initiated by MS in the source cell. It is one of the parameters that evaluate the radio environment. When BSC sends the PS HANDOVER COMMAND message to MS, if the handover is asynchronous handover, then the counter increments. The measurement point is A, as shown in Figure 95-7.
Figure 95-7 Measurement Point of Number of asynchronous handover executions

Unit
Times

95.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 point is A, as shown in Figure 95-8. If the handover is asynchronous handover and is of optimized handover mode, then, after the new cell receives the first correct RLC/MAC block, the PS HANDOVER COMPLETE message is sent to SGSN, and the optimized handover complete command (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 95-9.

95-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 95-8 Measurement Point of Number of successful asynchronous handovers - (1)

Figure 95-9 Measurement Point of Number of successful asynchronous handovers - (2)

Unit
Times

95.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
95-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

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 95-10.
Figure 95-10 Measurement Point of Number of normal handover executions

Unit
Times

95.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, and the counter increments. The measurement point is A, as shown in Figure 95-11.

95-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 95-11 Measurement Point of Number of successful normal handovers

Unit
Times

95.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 increments. The measurement point is A, as shown in Figure 95-12.
Figure 95-12 Measurement Point of Number of optimised handover executions

95-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

Unit
Times

95.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 point is A, as shown in Figure 95-13.
Figure 95-13 Measurement Point of Number of successful optimised handovers

Unit
Times

95-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

95.12 C901890011 Number of Intra-BSC inter-cell 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 handover, then the counter increments. The measurement point is A, as shown in Figure 95-14.
Figure 95-14 Measurement Point of Number of Intra-BSC inter-cell outgoing handover attempts

Unit
Times

95.13 C901890012 Number of Intra-BSC inter-cell 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
95-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

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 handover, then the counter increments. The measurement point is A, as shown in Figure 95-15.
Figure 95-15 Measurement Point of Number of Intra-BSC inter-cell outgoing handover executions

Unit
Times

95.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 point is A, as shown in Figure 95-16. If the handover is intra-BSC inter-cell handover and is of optimized handover mode, then, after the new cell receives the first correct RLC/MAC block, the PS HANDOVER COMPLETE message is sent to SGSN, and the optimized handover complete command (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 95-17.
95-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 95-16 Measurement Point of Number of successful Intra-BSC inter-cell outgoing handovers - (1)

Figure 95-17 Measurement Point of Number of successful Intra-BSC inter-cell outgoing handovers - (2)

Unit
Times

95.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
95-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

handover attempt initiated by MS in the source cell. It is one of the parameters that evaluate the radio environment. When user plane receives the handover decision PSHO_PSCmd from control plane, if it requires to initiate inter-BSC handover, then the counter increments. The measurement point is A, as shown in Figure 95-18.
Figure 95-18 Measurement Point of Number of Inter-BSC outgoing handover attempts

Unit
Times

95.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 measurement point is A, as shown in Figure 95-19.

95-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 95-19 Measurement Point of Number of Inter-BSC outgoing handover executions

Unit
Times

95.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. The measurement point is A, as shown in Figure 95-20.
Figure 95-20 Measurement Point of Number of successful Inter-BSC outgoing handovers

Unit
Times
95-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

95.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 measurement point is A, as shown in Figure 95-21.
Figure 95-21 Measurement Point of Number of incoming handover attempts

Unit
Times

95.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 increments. The measurement point is A, as shown in Figure 95-22.

95-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 95-22 Measurement Point of Number of incoming handover executions

Unit
Times

95.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 95-23.
Figure 95-23 Measurement Point of Number of successful incoming handovers

95-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

Unit
Times

95.21 C901890020 Number of Intra-cell handover 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 shown in Figure 95-24.
Figure 95-24 Measurement Point of Number of Intra-cell handover attempts

Unit
Times

95.22 C901890021 Number of Intra-Cell handover executions

Statistics object
Cell

95-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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

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

95.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
95-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

95.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. The measurement point is A, as shown in Figure 95-25.
Figure 95-25 Measurement Point of Number of 2G to FDD handover attempts

Unit
Times

95.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
95-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 shown in Figure 95-26.
Figure 95-26 Measurement Point of Number of 2G to FDD handover executions

Unit
Times

95.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 initiated by MS. It is one of the parameters that evaluate the radio environment. When the source BSC receives the DELETE BSS PFC message from SGSN, it indicates that the handover is completed, if the handover is FDD handover, the counter increments. The measurement point is A, as shown in Figure 95-27.

95-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

Figure 95-27 Measurement Point of Number of successful 2G to FDD handovers

Unit
Times

95.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 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 TDD handover, the counter increments. The measurement point is A, as shown in Figure 95-28.
Figure 95-28 Measurement Point of Number of 2G to TDD handover attempts

95-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

95.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 shown in Figure 95-29.
Figure 95-29 Measurement Point of Number of 2G to TDD handover executions

Unit
Times

95.30 C901890029 Number of successful 2G to TDD handovers

Statistics object
BSC

95-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

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 initiated by MS. It is one of the parameters that evaluate the radio environment. When the source BSC receives the DELETE BSS PFC message from SGSN, it indicates that the handover is completed, if the handover is TDD handover, the counter increments. The measurement point is A, as shown in Figure 95-30.
Figure 95-30 Measurement Point of Number of successful 2G to TDD handovers

Unit
Times

95.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 measurement point is A, as shown in Figure 95-31.

95-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 95-31 Measurement Point of Number of 3G to 2G handover attempts

Unit
Times

95.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 95-32.
Figure 95-32 Measurement Point of Number of 3G to 2G handover executions

95-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

Unit
Times

95.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 increments. The measurement point is A, as shown in Figure 95-33.
Figure 95-33 Measurement Point of Number of successful 3G to 2G handovers

Unit
Times

95.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 counter increments. The measurement point is A, as shown in Figure 95-34.
95-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 95-34 Measurement Point of Number of T12 expiry

Unit
Times

95.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 increments. The measurement point is A, as shown in Figure 95-35.
Figure 95-35 Measurement Point of Number of PCCF received

Unit
Times

95-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

95.36 C901890035 Number of PS-HANDOVER-REQUIRED-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 measurement point is A, as shown in Figure 95-36.
Figure 95-36 Measurement Point of Number of PS-HANDOVER-REQUIRED-NACK messages received with cause Create PFC Failure

Unit
Times

95.37 C901890036 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause PS Handover Target not allowed
Statistics object
BSC

Description
This counter counts the number of received PS Handover Required Nack messages with the cause "PS Handover Target not allowed". This counter is used to find out the frequency
95-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

of handover failure due to "PS Handover Target not allowed". When BSC receives the PS Handover Required Nack message from SGSN with the cause of "PS Handover Target not allowed", the counter increments. The measurement point is A, as shown in Figure 95-37.
Figure 95-37 Measurement Point of Number of PS-HANDOVER-REQUIRED-NACK messages received with cause PS Handover Target not allowed

Unit
Times

95.38 C901890037 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause PS Handover not Supported in Target BSS or Target System
Statistics object
BSC

Description
This counter counts the number of received PS Handover Required Nack messages with the cause "PS Handover not Supported in Target BSS or Target System". This counter is used to find out the frequency of handover failure due to "PS Handover not Supported in Target BSS or Target System". When BSC receives the PS Handover Required Nack message from SGSN with the cause of "PS Handover not Supported in Target BSS or Target System", the counter increments. The measurement point is A, as shown in Figure 95-38.

95-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

Figure 95-38 Measurement Point of Number of PS-HANDOVER-REQUIRED-NACK messages received with cause PS Handover not Supported in Target BSS or Target System

Unit
Times

95.39 C901890038 Number of PS-HANDOVER-REQUIRED-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 95-39.
Figure 95-39 Measurement Point of Number of PS-HANDOVER-REQUIRED-NACK messages received with cause other reasons

95-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

95.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 measurement point is A, as shown in Figure 95-40.
Figure 95-40 Measurement Point of Number of failure in optimised handover due to resource allcoation failure

Unit
Times

95-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 95 PS General Handover Measurement

95.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 95-41.
Figure 95-41 Measurement Point of Number of failure in optimized handover due to PS handover not supported in target cell

95-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

95-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 96

IURG Measurement
Table of Contents
Overview ..................................................................................................................96-1 C901900001 Number of relocation requests (on Iur-g) .............................................96-1 C901900002 Number of relocation executions (on Iur-g) ..........................................96-2 C901900003 Number of relocation successes (on Iur-g) ..........................................96-4 C901900004 Number of relocation failures due to no valid radio resource (on Iur-g) .96-5 C901900005 Number of relocation failures due to no valid terrestrial circuit resource (on Iur-g)....................................................................................................96-6 C901900006 Number of relocation failures due to loss of UE handover complete message (on Iur-g) ...................................................................................................96-7 C901900007 Number of relocation failures due to MS returning to original channel (on Iur-g) ..................................................................................................................96-8 C901900008 Number of relocation failures due to other causes (on Iur-g)................96-9

96.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. Statistic unit in this measurement is BSC.

96.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 96-1. (DBS is the database subsystem of BSC software)

96-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 96-1 Measurement Point of Relocation (on Iur-g)

Unit
Times

96.3 C901900002 Number of relocation executions (on Iur-g)

Statistics object
BSC
96-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 96 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 96-2. (DBS is the database subsystem of BSC software)
Figure 96-2 Measurement Point of Relocation (on Iur-g)

Unit
Times

96-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

96.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 96-3. (DBS is the database subsystem of BSC software)

96-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 96 IURG Measurement

Figure 96-3 Measurement Point of Relocation (on Iur-g)

Unit
Times

96.5 C901900004 Number of relocation failures due to no valid radio resource (on Iur-g)
Statistics object
BSC
96-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
Radio resource request fails. The measurement point is A4, as shown in Figure 96-4. (DBS is the database subsystem of BSC software)
Figure 96-4 Measurement Point of Number of relocation failures due to no valid radio resource (on Iur-g)

Unit
Times

96.6 C901900005 Number of relocation failures due to 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 96-5. (DBS is the database subsystem of BSC software)

96-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 96 IURG Measurement

Figure 96-5 Measurement Point of Number of relocation failures due to no valid terrestrial circuit resource (on Iur-g)

Unit
Times

96.7 C901900006 Number of relocation failures due to 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 96-6. (DBS is the database subsystem of BSC software)

96-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 96-6 Measurement Point of Number of relocation failures due to loss of UE handover complete message (on Iur-g)

Unit
Times

96.8 C901900007 Number of relocation failures due to 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 96-7.
96-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 96 IURG Measurement

(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 96-7 Measurement Point of Number of relocation failures due to MS returning to original channel (on Iur-g)

Unit
Times

96.9 C901900008 Number of relocation failures due to 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

96-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

96-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 97

RTCP Measurement
Table of Contents
Overview ..................................................................................................................97-1 C901910001 local jitter (CS).....................................................................................97-1 C901910002 distant jitter (CS) .................................................................................97-2 C901910003 average one-way delay (CS) ...............................................................97-3 C901910004 maximal one-way delay (CS)...............................................................97-5 C901910005 local cumulative fraction lost (CS)........................................................97-6 C901910006 distant cumulative fraction lost (CS) ....................................................97-7 C901910007 local jitter (PS).....................................................................................97-9 C901910008 distant jitter (PS)................................................................................97-10 C901910009 average one-way delay (PS) ............................................................. 97-11 C901910010 maximal one-way delay (PS) .............................................................97-13 C901910011 local cumulative fraction lost (PS) ......................................................97-14 C901910012 distant cumulative fraction lost (PS)...................................................97-15

97.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. Statistic unit in this measurement is cell.

97.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)
97-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 97-1.
Figure 97-1 Measurement Point of local jitter (CS)

Unit
ms

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

97-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 97 RTCP Measurement

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 97-2.
Figure 97-2 Measurement Point of local jitter (CS)

Unit
ms

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

97-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. 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 97-3.
Figure 97-3 Measurement Point of average one-way delay (CS)

97-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 97 RTCP Measurement

Unit
ms

97.5 C901910004 maximal 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

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. 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. The counter's working flow is shown in Figure 97-4.

97-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 97-4 Measurement Point of maximal one-way delay (CS)

Unit
ms

97.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
97-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 97 RTCP Measurement

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) The counter's working flow is shown in Figure 97-5.
Figure 97-5 Measurement Point of local cumulative fraction lost (CS)

Unit

97.7 C901910006 distant cumulative fraction lost (CS)

Statistics object
CELL

97-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 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) C901910006 = 0; else C901910006 = 10000 udLoss/(udRcv + udLoss) The counter's working flow is shown in Figure 97-6.
Figure 97-6 Measurement Point of distant cumulative fraction lost (CS)

97-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 97 RTCP Measurement

Unit

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

97-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 97-7 Measurement Point of local jitter (PS)

Unit
ms

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

97-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 97 RTCP Measurement

Figure 97-8 Measurement Point of distant jitter (PS)

Unit
ms

97.10 C901910009 average one-way delay (PS)

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

97-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. 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 97-9.
Figure 97-9 Measurement Point of average one-way delay (PS)

97-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 97 RTCP Measurement

Unit
ms

97.11 C901910010 maximal one-way delay (PS)

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

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. 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. The counter's working flow is shown in Figure 97-10.

97-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 97-10 Measurement Point of maximal one-way delay (PS)

Unit
ms

97.12 C901910011 local cumulative fraction lost (PS)

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
97-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 97 RTCP Measurement

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) C901910011 = 0; else C901910011 = 10000 udLoss/(udRcv + udLoss) The counter's working flow is shown in Figure 97-11.
Figure 97-11 Measurement Point of local cumulative fraction lost (PS)

Unit

97.13 C901910012 distant cumulative fraction lost (PS)

Statistics object
CELL

97-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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. 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) C901910012 = 0; else C901910012 = 10000 udLoss/(udRcv + udLoss) The counter's working flow is shown in Figure 97-12.
Figure 97-12 Measurement Point of distant cumulative fraction lost (PS)

Unit

97-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 98

DSP Measurement
Table of Contents
Overview ..................................................................................................................98-1 C901920001 the times of loss of TRAU frame synchronization in BIPB ....................98-1

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

98.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. The measurement point is A1, as shown in Figure 98-1.

98-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 98-1 Measurement Point of the times of loss of TRAU frame synchronization in BIPB

Unit
Second

98-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 99

Access Control Measurement

Table of Contents
Overview ..................................................................................................................99-2 C901930001 Number of CS Call Denied for Lack of IPAbis BandWidth UpLink ........99-2 C901930002 Number of CS Call Denied for Lack of IPAbis BandWidth DownLink....99-3 C901930003 Number of PS Call Denied for Lack of IPAbis BandWidth UpLink ........99-3 C901930004 Number of PS Call Denied for Lack of IPAbis BandWidth DownLink ....99-4 C901930005 Number of Pushing Down Uplink BandWidth.......................................99-5 C901930006 Number of Pushing Down Downlink BandWidth .................................99-5 C901930007 Number of Pushing Up Uplink BandWidth ..........................................99-6 C901930008 Number of Pushing Up Downlink BandWidth.......................................99-7 C901930009 Peak value of allocated bandwidth uplink ............................................99-8 C901930010 Value of allocated bandwidth uplink .....................................................99-8 C901930011 Number of allocated bandwidth uplink samples ...................................99-9 C901930012 Peak value of allocated bandwidth downlink........................................99-9 C901930013 Value of allocated bandwidth downlink ..............................................99-10 C901930014 Number of allocated bandwidth downlink samples.............................99-10 C901930015 Value of available bandwidth uplink ................................................... 99-11 C901930016 Value of available bandwidth downlink............................................... 99-11 C901930017 Number of CS preempt PS because of Abis resource .......................99-12 C901930018 Number of CS allocate Abis resource ................................................99-12 C901930019 Number of PS allocate Abis resource ................................................99-13 C901930020 Number of PS restricted because of Abis resource............................99-13 C901930021 Number of PDCH allocation restricted because of Abis resource.......99-14 C901930022 Peak value of cell CS Abis bandwidth uplink .....................................99-14 C901930023 Peak value of PS Abis bandwidth uplink............................................99-15 C901930024 Value of CS Abis Bandwidth Uplink ...................................................99-15 C901930025 Number of CS Abis Bandwidth Uplink Samples .................................99-15 C901930026 Value of PS Abis Bandwidth Uplink ...................................................99-16 C901930027 Number of PS Abis Bandwidth Uplink Samples .................................99-16 C901930028 Peak Value of CS Abis Bandwidth Downlink ......................................99-17 C901930029 Peak value of PS Abis bandwidth downlink .......................................99-17 C901930030 Value of CS Abis Bandwidth Downlink...............................................99-18 C901930031 Number of CS Abis Bandwidth Downlink Samples ............................99-18 C901930032 Value of PS Abis Bandwidth Downlink ...............................................99-19 C901930033 Number of PS Abis Bandwidth Downlink Samples.............................99-19 C901930034 Number of CS Call Denied for Lack of IPAbis BandWidth UpLink But Preempt PS IPAbis Successfully ............................................................................99-20

99-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901930035 Number of CS Call Denied for Lack of IPAbis BandWidth DownLink But Preempt PS IPAbis Successfully ......................................................................99-20

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

99.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 is A, as shown in Figure 99-1.
Figure 99-1 Measurement Point of Number of CS Call Denied for Lack of IPAbis BandWidth UpLink

Unit
Times

99-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 99 Access Control Measurement

99.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. The measurement point is A, as shown in Figure 99-2.
Figure 99-2 Measurement Point of Number of CS Call Denied for Lack of IPAbis BandWidth DownLink

Unit
Times

99.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 is A, as shown in Figure 99-3.
99-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 99-3 Measurement Point of Number of PS Call Denied for Lack of IPAbis BandWidth UpLink

Unit
Times

99.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. The measurement point is A, as shown in Figure 99-4.
Figure 99-4 Measurement Point of Number of PS Call Denied for Lack of IPAbis BandWidth DownLink

Unit
Times

99-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 99 Access Control Measurement

99.6 C901930005 Number of Pushing Down Uplink BandWidth

Description
This counter counts the number of pushing down uplink bandwidth in the resource pool. When BSC control plane judges that the actual uplink bandwidth exceeds, which is the safe allocation upper limit about bandwidth at the resource pool, if the current theoretically allocated uplink bandwidth of resource pool is larger than available uplink bandwidth, BSC control plane sends the message of pushing down uplink bandwidth to BSC user plane, and the counter increments.

Usage
The counter is used to find out the frequency of pushing down uplink bandwidth in the resource pool. This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC control plane sends the message of pushing down uplink bandwidth. The measurement point is A, as shown in Figure 99-5.
Figure 99-5 Flow of Pushing Down Uplink Bandwidth in Resource Pool

Unit
Times

99.7 C901930006 Number of Pushing Down Downlink BandWidth

Description
This counter counts the number of pushing down downlink bandwidth in the resource pool. When BSC control plane judges that the actual downlink bandwidth exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool, if the current
99-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

theoretically allocated downlink bandwidth of resource pool is larger than available downlink bandwidth, BSC control plane sends the message of pushing down downlink bandwidth to BSC user plane, and the counter increments.

Usage
The counter is used to find out the frequency of pushing down downlink bandwidth in the resource pool. This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC control plane sends the message of pushing down downlink bandwidth. The measurement point is A, as shown in Figure 99-6.
Figure 99-6 Flow of Pushing Down Downlink Bandwidth

Unit
Times

99.8 C901930007 Number of Pushing Up Uplink BandWidth

Description
This counter counts the number of pushing up uplink bandwidth in the resource pool. When BSC control plane judges that the actual uplink bandwidth is lower than C3, which is the congestion pushing up limit, BSC control plane sends the message of pushing up uplink bandwidth to BSC user plane, and the counter increments.

Usage
The counter is used to find out the frequency of pushing up uplink bandwidth in the resource pool. This counter is supported in version V6.20.61 or later.

99-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 99 Access Control Measurement

Measurement Point
The counter counts when BSC control plane sends the message of pushing up uplink bandwidth. The measurement point is A, as shown in Figure 99-7.
Figure 99-7 Flow of Pushing Up Uplink Bandwidth in Resource Pool

Unit
Times

99.9 C901930008 Number of Pushing Up Downlink BandWidth

Description
This counter counts the number of pushing up downlink bandwidth in the resource pool. When BSC control plane judges that the actual downlink bandwidth is lower than C3, which is the congestion pushing up limit, BSC control plane sends the message of pushing up downlink bandwidth to BSC user plane, and the counter increments.

Usage
The counter is used to find out the frequency of pushing up downlink bandwidth in the resource pool. This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC control plane sends the message of pushing up downlink bandwidth. The measurement point is A, as shown in Figure 99-8.

99-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 99-8 Flow of Pushing Up Downlink Bandwidth in Resource Pool

Unit
Times

99.10 C901930009 Peak value of allocated bandwidth uplink

Description
This counter records the peak value of allocated uplink bandwidth in the resource pool, which is calculated every time when services occupy bandwidth.

Usage
None

Measurement Point
None

Unit
None

99.11 C901930010 Value of allocated bandwidth uplink

Description
The uplink bandwidth occupied by services in a measurement period (15 minutes) is accumulated. This counter records the sum value.

Usage
None

99-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 99 Access Control Measurement

Measurement Point
None

Unit
None

99.12 C901930011 Number of allocated bandwidth uplink samples

Description
The corresponding uplink bandwidth resources need be allocated and released at the start and end of each service. This counter counts the times of uplink services including allocation and release (namely, the number of occupied uplink bandwidth samples) in a measurement period.

Usage
None

Measurement Point
None

Unit
None

99.13 C901930012 Peak value of allocated bandwidth downlink

Description
This counter records the peak value of allocated downlink bandwidth in the resource pool, which is calculated every time when services occupy bandwidth.

Usage
None

Measurement Point
None

99-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
None

99.14 C901930013 Value of allocated bandwidth downlink

Description
The downlink bandwidth occupied by services in a measurement period (15 minutes) is accumulated. This counter records the sum value.

Usage
None

Measurement Point
None

Unit
None

99.15 C901930014 Number of allocated bandwidth downlink samples

Description
The corresponding downlink bandwidth resources need be allocated and released at the start and end of each service. This counter counts the times of downlink services including allocation and release (namely, the number of allocated downlink bandwidth samples) in a measurement period.

Usage
None

Measurement Point
None

Unit
None

99-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 99 Access Control Measurement

99.16 C901930015 Value of available bandwidth uplink

Description
This counter records the available uplink bandwidth in the resource pool. In the case of the IP resource pool, the available uplink bandwidth is the uplink bandwidth configured at the OMCR if the admission control switch is disabled. If the admission control switch is enabled, the available uplink bandwidth is the uplink bandwidth measured actually. In the case of the IPOE1 resource pool, the available uplink bandwidth is the available bandwidth of the ML-PPP link reported by the EUIP interface board if the admission control switch is enabled. If the admission control switch is disabled, the available uplink bandwidth is the uplink bandwidth configured at the OMCR.

Usage
None

Measurement Point
None

Unit
None

99.17 C901930016 Value of available bandwidth downlink

Description
This counter records the available downlink bandwidth in the resource pool. In the case of the IP resource pool, the available downlink bandwidth is the downlink bandwidth configured at the OMCR. In the case of the IPOE1 resource pool, the available downlink bandwidth is the available bandwidth of the ML-PPP link reported by the EUIP interface board if the admission control switch is enabled. If the admission control switch is disabled, the available downlink bandwidth is the downlink bandwidth configured at the OMCR.

Usage
None

Measurement Point
None

99-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
None

99.18 C901930017 Number of CS preempt PS because of Abis resource

Description
When the CS service channel cannot be allocated due to the Abis resource shortage, the PS service resource will be preempted. This counter increases by 1 when the PS service resource is preempted successfully.

Usage
None

Measurement Point
None

Unit
None

99.19 C901930018 Number of CS allocate Abis resource

Description
When requesting channel, each CS service requests certain Abis bandwidth. Full rate service requests 16 kbps Abis resource. Half rate service requests 10 kbps Abis resource. If the service is the first service over the carrier frequency, the bandwidth occupied by the packet header need be requested additionally. This counter increases by 1 when the CS service requests the Abis resource successfully.

Usage
None

Measurement Point
None

Unit
None

99-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 99 Access Control Measurement

99.20 C901930019 Number of PS allocate Abis resource

Description
When requesting channel, the PS service requests the corresponding Abis resource if it is found that the service is the first user service in the channel. This counter increases by 1 when the PS requests the Abis resource. Otherwise, the PS service need not request resource, and the counter is not updated.

Usage
None

Measurement Point
None

Unit
None

99.21 C901930020 Number of PS restricted because of Abis resource

Description
This counter counts the times that the PS coding mode cannot be allocated with the highest coding mode CS-4 (GPRS) or MCS-9 (EGPRS) due to Abis resource restriction (namely, bandwidth restriction for PS request).

Usage
None

Measurement Point
None

Unit
None

99-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

99.22 C901930021 Number of PDCH allocation restricted because of Abis resource

Description
This counter counts the times that the bandwidth allocated to the PS channel is restricted, namely, the times that the radio channel cannot be allocated based on the MS multiple-timeslot capability due to bandwidth restriction for PS request.

Usage
None

Measurement Point
None

Unit
None

99.23 C901930022 Peak value of cell CS Abis bandwidth uplink

Description
The MNIC board reports the Abis bandwidth once a second. This counter records the maximum value of the uplink CS Abis bandwidth in one granularity (15 minutes).

Usage
None

Measurement Point
None

Unit
None

99-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 99 Access Control Measurement

99.24 C901930023 Peak value of PS Abis bandwidth uplink

Description
The MNIC board reports the Abis bandwidth once a second. This counter records the maximum value of the uplink PS Abis bandwidth in one granularity (15 minutes).

Usage
None

Measurement Point
None

Unit
None

99.25 C901930024 Value of CS Abis Bandwidth Uplink

Description
The MNIC board reports the Abis bandwidth once a second. This counter records the sum value of all the uplink CS Abis bandwidth in one granularity (15 minutes) in the resource pool.

Usage
None

Measurement Point
None

Unit
None

99.26 C901930025 Number of CS Abis Bandwidth Uplink Samples

Description
The MNIC board reports the uplink CS Abis bandwidth once a second. This counter counts the times that the uplink CS Abis bandwidth is reported in 15 minutes.
99-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
None

99.27 C901930026 Value of PS Abis Bandwidth Uplink

Description
The MNIC board reports the Abis bandwidth once a second. This counter records the sum value of all the uplink PS Abis bandwidth in one granularity (15 minutes).

Usage
None

Measurement Point
None

Unit
None

99.28 C901930027 Number of PS Abis Bandwidth Uplink Samples

Description
The MNIC board reports the uplink PS Abis bandwidth once a second. This counter counts the times that the uplink PS Abis bandwidth is reported in one granularity (15 minutes).

Usage
None

Measurement Point
None

99-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 99 Access Control Measurement

Unit
None

99.29 C901930028 Peak Value of CS Abis Bandwidth Downlink

Description
The MNIC board reports the Abis bandwidth once a second. This counter records the maximum value of the downlink CS Abis bandwidth measured in one granularity (15 minutes).

Usage
None

Measurement Point
None

Unit
None

99.30 C901930029 Peak value of PS Abis bandwidth downlink

Description
The MNIC board reports the Abis bandwidth once a second. This counter records the maximum value of the downlink PS Abis bandwidth measured in one granularity (15 minutes).

Usage
None

Measurement Point
None

Unit
None

99-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

99.31 C901930030 Value of CS Abis Bandwidth Downlink

Description
The MNIC board reports the Abis bandwidth once a second. This counter records the sum value of all the downlink CS Abis bandwidth in one granularity (15 minutes) in the resource pool.

Usage
None

Measurement Point
None

Unit
None

99.32 C901930031 Number of CS Abis Bandwidth Downlink Samples

Description
The MNIC board reports the downlink CS Abis bandwidth once a second. This counter counts the times that the downlink CS Abis bandwidth is reported in 15 minutes.

Usage
None

Measurement Point
None

Unit
None

99-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 99 Access Control Measurement

99.33 C901930032 Value of PS Abis Bandwidth Downlink

Description
The MNIC board reports the Abis bandwidth once a second. This counter records the sum value of all the downlink PS Abis bandwidth in one granularity (15 minutes) in the resource pool.

Usage
None

Measurement Point
None

Unit
None

99.34 C901930033 Number of PS Abis Bandwidth Downlink Samples

Description
The MNIC board reports the downlink PS Abis bandwidth once a second. This counter counts the times that the downlink PS Abis bandwidth is reported in 15 minutes.

Usage
None

Measurement Point
None

Unit
None

99-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

99.35 C901930034 Number of CS Call Denied for Lack of IPAbis BandWidth UpLink But Preempt PS IPAbis Successfully
Description
This counter counts the times that CS service preempts the PS IP Abis resource successfully due to lack of the uplink IP Abis bandwidth during channel request. The counting criterion is not that the CS service is initiated successfully but that the Abis resource is preempted successfully.

Usage
None

Measurement Point
None

Unit
Second

99.36 C901930035 Number of CS Call Denied for Lack of IPAbis BandWidth DownLink But Preempt PS IPAbis Successfully
Description
This counter counts the times that CS service preempts the PS IP Abis resource successfully due to lack of the downlink IP Abis bandwidth during channel request. The counting criterion is not that the CS service is initiated successfully but that the Abis resource is preempted successfully.

Usage
None

Measurement Point
None

Unit
Second
99-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 100

Power Control Measurement

Table of Contents
Overview ................................................................................................................100-1 C901940001 The count of iBSC receiving power control indication from BTS.........100-2 C901940002 The count of channel downlink power exceeding TRX mean downlink power, when iBSC receives power control indication from BTS ..............................100-3 C901940003 The count of CS service channel allocation failure caused by power shortage .................................................................................................................100-4 C901940004 The count of CS timeslot allocation failure caused by power shortage .................................................................................................................100-5 C901940005 The count of PS service channel allocation failure caused by power shortage .................................................................................................................100-7 C901940006 The count of PS timeslot allocation failure caused by power shortage .................................................................................................................100-7 C901940007 The Count of CS Service Channel Allocation Failure Caused by PLMN Power Shortage...........................................................................................100-8 C901940008 The Count of CS Timeslot Allocation Failure Caused by PLMN Power Shortage ................................................................................................................100-8 C901940009 The Count of PS Service Channel Allocation Failure Caused by PLMN Power Shortage...........................................................................................100-8 C901940010 The Count of PS Timeslot Allocation Failure Caused by PLMN Power Shortage ................................................................................................................100-9 C901940011 The Count of Power Congestion Due to RRU Power Limit.................100-9 C901940012 Time of Power Congestion Due to RRU Power Limit .......................100-10 C901940013 The Count of Power Congestion Due to PLMN Power Limit ............100-10 C901940014 Time of Power Congestion Due to PLMN Power Limit .....................100-10 C901940015 The Count of PDTCH Power Decrease Due to Power Congestion... 100-11 C901940016 Time of PDTCH Power Decrease Due to Power Congestion ........... 100-11 C901940017 The Count of 8PSK Power Increase Due to Power Enough.............100-12 C901940018 Time of 8PSK Power Increase Due to Power Enough......................100-12

100.1 Overview
The principle of dynamic power sharing is: To better use the rated output power of the Power Amplifier (PA) of RRU, the BCCH carrier occupies fixed transmitting power, and other service carriers can dynamically share the transmitting power of RRU. Moreover, to facilitate observing the result of power sharing, several counters are added for power-sharing measurement.
100-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Statistic unit in the power-sharing measurement is cell. To use dynamic power sharing, the function of downlink dynamic power control must be enabled first. After services are accessed, the base station increases or decreases the downlink power according to the measurement report result.

100.2 C901940001 The count of iBSC receiving power control indication from BTS
Description
When iBSC receives the power control indication message (Abis PowerControl Indication) from the base station, if the message contains the downlink power adjustment information, the counter increments.

Usage
This counter is used to find out the frequency of downlink dynamic power control. This counter is supported in version V6.20.600f or later.

Measurement Point
When iBSC receives the power control indication message (Abis PowerControl Indication) from the base station, if the message contains the downlink power adjustment information, the counter increments. The measurement point is A1, as shown in Figure 100-1.
Figure 100-1 Power Sharing Counter 1

100-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 100 Power Control Measurement

100.3 C901940002 The count of channel downlink power exceeding TRX mean downlink power, when iBSC receives power control indication from BTS
Description
When iBSC receives the power control indication message (Abis PowerControl Indication) from the base station, if the following two conditions are satisfies, the counter increments: (1) The message contains the downlink power adjustment information. (2) The value of degraded dBs (0 dB ~ 30 dB) for the channel by downlink power control is smaller than the value of enhanced dBs (0 dB ~ 1.5 dB) for the carrier by the power level configured in OMCR.

Usage
This counter is used to find out whether the function of dynamic power sharing can make the power of service channel exceed the average power of service carrier, that is, exceed (RRU's total power - BCCH carrier's power) / number of service carriers. This counter is supported in version V6.20.600f or later.

Measurement Point
When iBSC receives the power control indication message (Abis PowerControl Indication) from the base station, if the following two conditions are satisfies, the counter increments: l The message contains the downlink power adjustment information. l The value of degraded dBs (0 dB ~ 30 dB) for the channel by downlink power control is smaller than the value of enhanced dBs (0 dB ~ 1.5 dB) for the carrier by the power level configured in OMCR. The measurement point is A1, as shown in Figure 100-2.
Figure 100-2 Flow of Reporting Power Control Indication Message

100-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

100.4 C901940003 The count of CS service channel allocation failure caused by power shortage
Description
During the process of assignment or handover, if iBSC fails to allocate CS service channel due to insufficient power of RRU, the counter increments.

Usage
This counter is used to find out the number of failures in allocating CS service channel due to insufficient power of RRU after the function of dynamic power sharing is enabled. This counter is supported in version V6.20.600f or later.

Measurement Point
During the process of assignment or handover, if iBSC fails to allocate CS service channel due to insufficient power of RRU, the counter increments. The measurement point is A1, as shown in Figure 100-3, Figure 100-4, and Figure 100-5.
Figure 100-3 Assignment Failure Process

Figure 100-4 Failure in Allocating Channel for Destination Cell of Internal Handover

100-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 100 Power Control Measurement

Figure 100-5 Failure in Allocating Channel for External Incoming Handover

100.5 C901940004 The count of CS timeslot allocation failure caused by power shortage
Description
When iBSC allocates CS service channel during the process of assignment or handover, if the function of dynamic power sharing is enabled, there might be several channels that fail to be allocated due to insufficient power of timeslots. The counter increments when a channel fails to be allocated due to insufficient power of timeslot.

Usage
This counter is used to find out the frequency of failing in allocating CS service channel due to insufficient power of RRU after the function of dynamic power sharing is enabled. This counter is supported in version V6.20.600f or later.

Measurement Point
When iBSC allocates CS service channel during the process of assignment or handover, if the function of dynamic power sharing is enabled, there might be several channels that fail to be allocated due to insufficient power of timeslots. The counter increments when a channel fails to be allocated due to insufficient power of timeslot. The measurement points are A1 and B1, as shown in Figure 100-6, Figure 100-7, and Figure 100-8.

100-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 100-6 C901940004a

Figure 100-7 C901940004b

Figure 100-8 C901940004c

100-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 100 Power Control Measurement

100.6 C901940005 The count of PS service channel allocation failure caused by power shortage
Description
After the dynamic power sharing function is enabled, when iBSC allocates TBF for PS service, if the PS channel allocation fails due to insufficient power of RRU, the counter increments.

Usage
This counter is used to find out the number of failures in allocating PS service channel due to insufficient power of RRU after the function of dynamic power sharing is enabled. This counter is supported in version V6.20.61 or later.

Measurement Point
After the dynamic power sharing function is enabled, when iBSC allocates TBF for PS service, if the PS channel allocation fails due to insufficient power of RRU, the counter increments.

100.7 C901940006 The count of PS timeslot allocation failure caused by power shortage
Description
After the dynamic power sharing function is enabled, when iBSC allocates TBF for PS service or during the process of requesting for DTM channel, there might be several PS channels that fail to be allocated due to insufficient power of RRU. The counter increments when a PS channel fails to be allocated.

Usage
This counter is used to find out the frequency of failing in allocating PS service channel or DTM channel due to insufficient power of RRU after the function of dynamic power sharing is enabled. This counter is supported in version V6.20.61 or later.

Measurement Point
After the dynamic power sharing function is enabled, when iBSC allocates TBF for PS service or during the process of requesting for DTM channel, there might be several PS channels that fail to be allocated due to insufficient power of RRU. The counter increments when a PS channel fails to be allocated.

100-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

100.8 C901940007 The Count of CS Service Channel Allocation Failure Caused by PLMN Power Shortage
Description
This counter counts CS traffic channel allocation failures due to PLMN admission control based on power sharing. This counter is not used in this version.

Measurement Point
None

Unit
Times

100.9 C901940008 The Count of CS Timeslot Allocation Failure Caused by PLMN Power Shortage
Description
This counter counts the number of times that a CS traffic channel is not selected due to PLMN admission control based on power sharing. This counter is not used in this version.

Measurement Point
None

Unit
Times

100.10 C901940009 The Count of PS Service Channel Allocation Failure Caused by PLMN Power Shortage
Description
This counter counts PS traffic channel allocation failures due to PLMN admission control based on power sharing.
100-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 100 Power Control Measurement

This counter is not used in this version.

Measurement Point
None

Unit
Times

100.11 C901940010 The Count of PS Timeslot Allocation Failure Caused by PLMN Power Shortage
Description
This counter counts the number of times that a PS traffic channel is not selected due to PLMN admission control based on power sharing. This counter is not used in this version.

Measurement Point
None

Unit
Times

100.12 C901940011 The Count of Power Congestion Due to RRU Power Limit
Description
This counter counts the number of times that all channels in a cell are congested due to RRU power limit.

Measurement Point
This counter is incremented upon channel allocation, release, refresh, power update, or power limit change.

Unit
Times

100-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

100.13 C901940012 Time of Power Congestion Due to RRU Power Limit

Description
This counter counts the duration of channel congestion due to RRU power limit in a cell.

Measurement Point
This counter is incremented upon channel allocation, release, refresh, power update, power limit change, or expiry of the OMS measurement period (15 minutes).

Unit
Second

100.14 C901940013 The Count of Power Congestion Due to PLMN Power Limit
Description
This counter counts the number of times that power congestion occurs due to PLMN power limit. This counter is not used in this version.

Measurement Point
None

Unit
Times

100.15 C901940014 Time of Power Congestion Due to PLMN Power Limit

Description
This counter counts the duration of power congestion due to PLMN power limit. This counter is not used in this version.

Measurement Point
None
100-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 100 Power Control Measurement

Unit
Second

100.16 C901940015 The Count of PDTCH Power Decrease Due to Power Congestion
Description
This counter counts the number of times that the PDTCH power is decreased due to power congestion in a cell.

Measurement Point
This counter is incremented each time the RANU, after returning the PD power decrease result, calls the DM_SETPDPWRCTRLRESULT interface.

Unit
Times

100.17 C901940016 Time of PDTCH Power Decrease Due to Power Congestion

Description
This counter counts the duration of PDTCH power decrease due to power congestion in a cell.

Measurement Point
This counter is incremented in the following cases: l l l l l The PS channel is released. The PS channel is refreshed. The PS channel is deleted after the dynamic channel changes from PS to CS in a specific bit map. The RANU calls the DM_SETPDPWRCTRLRESULT interface after returning the PD power decrease result. The OMS measurement period (15 minutes) expires.

Unit
Second

100-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

100.18 C901940017 The Count of 8PSK Power Increase Due to Power Enough
Description
This counter counts the number of times that the PD channel power is increased by 8PSK due to occupied power lower than 8PSK power limit in a cell.

Measurement Point
This counter is incremented each time the RANU calls the DM_8PSKPWRCHGRESULT interface upon reporting the 8PSK power increase result.

Unit
Times

100.19 C901940018 Time of 8PSK Power Increase Due to Power Enough

Description
This counter counts the duration of 8PSK power increase of PD channel due to occupied power lower than 8PSK power limit in a cell.

Measurement Point
This counter is incremented in the following cases: l l l l l The PS channel is released. The PS channel is refreshed. The PS channel is deleted after the dynamic channel changes from PS to CS in a specific bit map. The RANU calls the DM_8PSKPWRCHGRESULT interface after returning the 8PSK power increase result. The OMS measurement period (15 minutes) expires.

Unit
Second

100-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 101

PS Adjacent Cell Handover Measurement

Table of Contents
Overview ................................................................................................................101-2 C901950001 Number of handover attempts on the adjacent cell ............................101-2 C901950002 Number of successful handovers from selected cell to the adjacent cell .........................................................................................................................101-3 C901950003 Number of handover attempts from adjacent cell to the selected cell .101-4 C901950004 Number of successful handovers from adjacent cell to the selected cell .........................................................................................................................101-5 C901950005 Number of handover attempts from selected cell to the adjacent cell due to better uplink quality......................................................................................101-6 C901950006 Number of handover attempts from selected cell to the adjacent cell due to better downlink quality .................................................................................101-7 C901950007 Number of successful handovers from selected cell to the adjacent cell due to better uplink quality ...............................................................................101-9 C901950008 Number of successful handovers from selected cell to the adjacent cell due to better downlink quality .........................................................................101-10 C901950009 Number of handover attempts from selected cell to the adjacent cell due to better uplink strength ................................................................................. 101-11 C901950010 Number of handover attempts from selected cell to the adjacent cell due to better downlink strength.............................................................................101-12 C901950011 Number of successful handovers from selected cell to the adjacent cell due to better uplink strength ...........................................................................101-13 C901950012 Number of successful handovers from selected cell to the adjacent cell due to better downlink strength ......................................................................101-14 C901950013 Number of handover attempts from selected cell to the adjacent cell due to PBGT ........................................................................................................101-16 C901950014 Number of successful handovers from selected cell to the adjacent cell due to PBGT ..................................................................................................101-17 C901950015 Number of handover attempts from selected cell to the adjacent cell due to large TA.....................................................................................................101-18 C901950016 Number of successful handover from selected cell to the adjacent cell due to large TA.....................................................................................................101-19 C901950017 Number of handover attempts from selected cell to the adjacent cell due to high traffic..................................................................................................101-20

101-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C901950018 Number of successful handover from selected cell to the adjacent cell due to high traffic..................................................................................................101-21

101.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. Statistic unit in this measurement is cell.

101.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, as shown in Figure 101-1.
Figure 101-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 101-2.
101-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 101 PS Adjacent Cell Handover Measurement

Figure 101-2 Measurement Point of Number of handover attempts on the adjacent cell - (2)

Unit
Times

101.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 point is A, as shown in Figure 101-3.
Figure 101-3 Measurement Point of Number of successful handovers from selected cell to the adjacent cell - (1)

101-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

For SGSN-controlled external handover, when the source cell receives the release command issued by SGSN and if the release is due to handover success, then the counter increments. The measurement point is A, as shown in Figure 101-4.
Figure 101-4 Measurement Point of Number of successful handovers from selected cell to the adjacent cell - (2)

Unit
Times

101.4 C901950003 Number of handover attempts from 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 is A, as shown in Figure 101-5.

101-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 101 PS Adjacent Cell Handover Measurement

Figure 101-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 shown in Figure 101-6.
Figure 101-6 Measurement Point of Number of handover attempts from adjacent cell to the selected cell - (2)

Unit
Times

101.5 C901950004 Number of successful handovers 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.

101-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 shown in Figure 101-7.
Figure 101-7 Measurement Point of Number of successful handovers from adjacent cell to the selected cell - (1)

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 shown in Figure 101-8.
Figure 101-8 Measurement Point of Number of successful handovers from adjacent cell to the selected cell - (2)

Unit
Times

101.6 C901950005 Number of handover attempts from 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
101-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 101 PS Adjacent Cell Handover Measurement

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 counter increments. The measurement point is A, as shown in Figure 101-9.
Figure 101-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 increments. The measurement point is A, as shown in Figure 101-10.
Figure 101-10 Measurement Point of Number of handover attempts from selected cell to the adjacent cell due to better uplink quality - (2)

Unit
Times

101.7 C901950006 Number of handover attempts from selected cell to the adjacent cell due to better downlink quality
Statistics object
Cell
101-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to downlink qulaity. This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell due to downlink 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 downlink quality, the counter increments. The measurement point is A, as shown in Figure 101-11.
Figure 101-11 Measurement Point of Number of handover attempts from selected cell to the adjacent cell due to better downlink quality - (1)

For SGSN-controlled external handover, when the destination cell receives the handover request message from SGSN, if the handover is due to downlink quality, the counter increments. The measurement point is A, as shown in Figure 101-12.
Figure 101-12 Measurement Point of Number of handover attempts from selected cell to the adjacent cell due to better downlink quality - (2)

Unit
Times

101-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 101 PS Adjacent Cell Handover Measurement

101.8 C901950007 Number of successful handovers from selected cell to the adjacent cell due to better uplink quality
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 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 helps check the direction of handover between cells. For BSC-controlled inter-cell handover, when the source cell receives the handover completion message from the destination cell, if the handover is due to uplink quality, the counter increments. The measurement point is A, as shown in Figure 101-13.
Figure 101-13 Measurement Point of Number of successful handovers from selected cell to the adjacent cell due to better uplink quality - (1)

For SGSN-controlled external handover, when the source cell receives the release command issued by SGSN, if the release is due to handover success and the handover is due to uplink quality, the counter increments. The measurement point is A, as shown in Figure 101-14.
Figure 101-14 Measurement Point of Number of successful handovers from selected cell to the adjacent cell due to better uplink quality - (2)

101-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

101.9 C901950008 Number of successful handovers from selected cell to the adjacent cell due to better downlink quality
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 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. 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 downlink quality, the counter increments. The measurement point is A, as shown in Figure 101-15.
Figure 101-15 Measurement Point of Number of successful handovers from selected cell to the adjacent cell due to better downlink quality - (1)

For SGSN-controlled external handover, when the source cell receives the release command issued by SGSN, if the release is due to handover success and the handover is due to downlink quality, the counter increments. The measurement point is A, as shown in Figure 101-16.

101-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 101 PS Adjacent Cell Handover Measurement

Figure 101-16 Measurement Point of Number of successful handovers from selected cell to the adjacent cell due to better downlink quality - (2)

Unit
Times

101.10 C901950009 Number of handover attempts from selected cell to the adjacent cell due to better uplink strength
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 strength. This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell due to uplink strength. It helps check the direction of handover between cells. 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 strength, the counter increments. The measurement point is A, as shown in Figure 101-17.
Figure 101-17 Measurement Point of Number of handover attempts from selected cell to the adjacent cell due to better uplink strength - (1)

101-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

For SGSN-controlled external handover, when the destination cell receives the handover request message from SGSN, if the handover is due to uplink strength, the counter increments. The measurement point is A, as shown in Figure 101-18.
Figure 101-18 Measurement Point of Number of handover attempts from selected cell to the adjacent cell due to better uplink strength - (2)

Unit
Times

101.11 C901950010 Number of handover attempts from selected cell to the adjacent cell due to better downlink strength
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 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. 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 downlink strength, the counter increments. The measurement point is A, as shown in Figure 101-19.

101-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 101 PS Adjacent Cell Handover Measurement

Figure 101-19 Measurement Point of Number of handover attempts from selected cell to the adjacent cell due to better downlink strength - (1)

For SGSN-controlled external handover, when the destination cell receives the handover request message from SGSN, if the handover is due to downlink strength, the counter increments. The measurement point is A, as shown in Figure 101-20.
Figure 101-20 Measurement Point of Number of handover attempts from selected cell to the adjacent cell due to better downlink strength - (2)

Unit
Times

101.12 C901950011 Number of successful handovers from selected cell to the adjacent cell due to better uplink strength
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 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.
101-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

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 strength, the counter increments. The measurement point is A, as shown in Figure 101-21.
Figure 101-21 Measurement Point of Number of successful handovers from selected cell to the adjacent cell due to better uplink strength - (1)

For SGSN-controlled external handover, when the source cell receives the release command issued by SGSN, if the release is due to handover success and the handover is due to uplink strength, the counter increments. The measurement point is A, as shown in Figure 101-22.
Figure 101-22 Measurement Point of Number of successful handovers from selected cell to the adjacent cell due to better uplink strength - (2)

Unit
Times

101.13 C901950012 Number of successful handovers from selected cell to the adjacent cell due to better downlink strength
Statistics object
Cell

101-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 101 PS Adjacent Cell Handover Measurement

Description
This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to downlink strength. This counter is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell due to downlink strength. It helps check the direction of handover between cells. 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 downlink strength, the counter increments. The measurement point is A, as shown in Figure 101-23.
Figure 101-23 Measurement Point of Number of successful handovers from selected cell to the adjacent cell due to better downlink strength - (1)

For SGSN-controlled external handover, when the source cell receives the release command issued by SGSN, if the release is due to handover success and the handover is due to downlink strength, the counter increments. The measurement point is A, as shown in Figure 101-24.
Figure 101-24 Measurement Point of Number of successful handovers from selected cell to the adjacent cell due to better downlink strength - (2)

Unit
Times

101-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

101.14 C901950013 Number of handover attempts from selected cell to the adjacent cell due to PBGT
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 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. 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 PBGT, the counter increments. The measurement point is A, as shown in Figure 101-25.
Figure 101-25 Measurement Point of Number of handover attempts from selected cell to the adjacent cell due to PBGT - (1)

For SGSN-controlled external handover, when the destination cell receives the handover request message from SGSN, if the handover is due to PBGT, the counter increments. The measurement point is A, as shown in Figure 101-26.
Figure 101-26 Measurement Point of Number of handover attempts from selected cell to the adjacent cell due to PBGT - (2)

101-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 101 PS Adjacent Cell Handover Measurement

Unit
Times

101.15 C901950014 Number of successful handovers 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. 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 PBGT, the counter increments. The measurement point is A, as shown in Figure 101-27.
Figure 101-27 Measurement Point of Number of successful handovers from selected cell to the adjacent cell due to PBGT - (1)

For SGSN-controlled external handover, when the source cell receives the release command issued by SGSN, if the release is due to handover success and the handover is due to PBGT, the counter increments. The measurement point is A, as shown in Figure 101-28.

101-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 101-28 Measurement Point of Number of successful handovers from selected cell to the adjacent cell due to PBGT - (2)

Unit
Times

101.16 C901950015 Number of handover attempts from 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. 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 too large TA, the counter increments. The measurement point is A, as shown in Figure 101-29.
Figure 101-29 Measurement Point of Number of handover attempts from selected cell to the adjacent cell due to large TA - (1)

101-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 101 PS Adjacent Cell Handover Measurement

For SGSN-controlled external handover, when the destination cell receives the handover request message from SGSN, if the handover is due to too large TA, the counter increments. The measurement point is A, as shown in Figure 101-30.
Figure 101-30 Measurement Point of Number of handover attempts from selected cell to the adjacent cell due to large TA - (2)

Unit
Times

101.17 C901950016 Number of successful handover from selected cell to the adjacent cell due to large TA
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 too large TA. This counter is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell due to too large TA. It helps check the direction of handover between cells. 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 too large TA, the counter increments. The measurement point is A, as shown in Figure 101-31.

101-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 101-31 Measurement Point of Number of successful handover from selected cell to the adjacent cell due to large TA - (1)

For SGSN-controlled external handover, when the source cell receives the release command issued by SGSN, if the release is due to handover success and the handover is due to too large TA, the counter increments. The measurement point is A, as shown in Figure 101-32.
Figure 101-32 Measurement Point of Number of successful handover from selected cell to the adjacent cell due to large TA - (2)

Unit
Times

101.18 C901950017 Number of handover attempts from selected cell to the adjacent cell due to high traffic
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 heavy traffic. This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell due to too heavy traffic. It helps check the direction of handover between cells.

101-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 101 PS Adjacent Cell Handover Measurement

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 too heavy traffic, the counter increments. The measurement point is A, as shown in Figure 101-33.
Figure 101-33 Measurement Point of Number of handover attempts from selected cell to the adjacent cell due to high traffic - (1)

For SGSN-controlled external handover, when the destination cell receives the handover request message from SGSN, if the handover is due to too heavy traffic, the counter increments. The measurement point is A, as shown in Figure 101-34.
Figure 101-34 Measurement Point of Number of handover attempts from selected cell to the adjacent cell due to high traffic - (2)

Unit
Times

101.19 C901950018 Number of successful handover from selected cell to the adjacent cell due to high traffic
Statistics object
Cell
101-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Description
This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to too heavy traffic. This counter is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell due to too heavy traffic. It helps check the direction of handover between cells. 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 too heavy traffic, the counter increments. The measurement point is A, as shown in Figure 101-35.
Figure 101-35 Measurement Point of Number of successful handover from selected cell to the adjacent cell due to high traffic - (1)

For SGSN-controlled external handover, when the source cell receives the release command issued by SGSN, if the release is due to handover success and the handover is due to too heavy traffic, the counter increments. The measurement point is A, as shown in Figure 101-36.
Figure 101-36 Measurement Point of Number of successful handover from selected cell to the adjacent cell due to high traffic - (2)

Unit
Times

101-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 102

ACL Flow Statistic

Table of Contents
C901970001 ID of Application Type (0: ACCESS, 1: IPSEC, 2: PBR)....................102-2 C901970002 Action (NOT IPSEC, PASS=0, DISCARD=other; IPSEC, PASS=0 Or 3, DISCARD=1, ipsec=2;).......................................................................................102-2 C901970003 Min Value of Protocol ........................................................................102-3 C901970004 Max Value of Protocol........................................................................102-3 C901970005 Min Value of Source IP (Fragment 1).................................................102-3 C901970006 Min Value of Source IP (Fragment 2).................................................102-4 C901970007 Min Value of Source IP (Fragment 3).................................................102-4 C901970008 Min Value of Source IP (Fragment 4).................................................102-4 C901970009 Max Value of Source IP (Fragment 1)................................................102-5 C901970010 Max Value of Source IP (Fragment 2)................................................102-5 C901970011 Max Value of Source IP (Fragment 3) ................................................102-6 C901970012 Max Value of Source IP (Fragment 4)................................................102-6 C901970013 Min Value of Dest IP (Fragment 1).....................................................102-6 C901970014 Min Value of Dest IP (Fragment 2).....................................................102-7 C901970015 Min Value of Dest IP (Fragment 3).....................................................102-7 C901970016 Min Value of Dest IP (Fragment 4).....................................................102-7 C901970017 Max Value of Dest IP (Fragment 1)....................................................102-8 C901970018 Max Value of Dest IP (Fragment 2)....................................................102-8 C901970019 Max Value of Dest IP (Fragment 3)....................................................102-9 C901970020 Max Value of Dest IP (Fragment 4)....................................................102-9 C901970021 Min Value of Source Port. ..................................................................102-9 C901970022 Max Value of Source Port. ...............................................................102-10 C901970023 Min Value of Dest Port.....................................................................102-10 C901970024 Max Value of Dest Port....................................................................102-10 C901970025 Direction (1: IN; 2: OUT) ................................................................. 102-11 C901970026 Number of Packets Filtered (Low 32 bits) ........................................ 102-11 C901970027 Number of Packets Filtered (High 32 bits) .......................................102-12 C901970028 Number of Bytes Filtered (Low 32 bits)............................................102-12 C901970029 Number of Bytes Filtered (High 32 bits) ...........................................102-12

102-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

102.1 C901970001 ID of Application Type (0: ACCESS, 1: IPSEC, 2: PBR)

Description
This counter counts the number of ACL rules of each application type (0: ACCESS, 1: IPSEC, 2: PBR).

Usage
None

Measurement Point
None

Unit
None

102.2 C901970002 Action (NOT IPSEC, PASS=0, DISCARD=other; IPSEC, PASS=0 Or 3, DISCARD=1, ipsec=2;)
Description
This counter records the action of ACL rules of each application type (ACCESS, IPSEC, and PBR). NOT IPSEC, PASS=0, DISCARD=other; IPSEC, PASS=0 Or 3, DISCARD=1, ipsec=2.

Usage
None

Measurement Point
None

Unit
None

102-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 102 ACL Flow Statistic

102.3 C901970003 Min Value of Protocol

Description
This counter records the minimum value of the protocol in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.4 C901970004 Max Value of Protocol

Description
This counter records the maximum value of the protocol in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.5 C901970005 Min Value of Source IP (Fragment 1)

Description
This counter records the minimum value of the source IP (fragment 1) in ACL rules.

Usage
None

Measurement Point
None
102-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
None

102.6 C901970006 Min Value of Source IP (Fragment 2)

Description
This counter records the minimum value of the source IP (fragment 2) in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.7 C901970007 Min Value of Source IP (Fragment 3)

Description
This counter records the minimum value of the source IP (fragment 3) in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.8 C901970008 Min Value of Source IP (Fragment 4)

Description
This counter records the minimum value of the source IP (fragment 4) in ACL rules.

Usage
None
102-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 102 ACL Flow Statistic

Measurement Point
None

Unit
None

102.9 C901970009 Max Value of Source IP (Fragment 1)

Description
This counter records the maximum value of the source IP (fragment 1) in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.10 C901970010 Max Value of Source IP (Fragment 2)

Description
This counter records the maximum value of the source IP (fragment 2) in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

102.11 C901970011 Max Value of Source IP (Fragment 3)

Description
This counter records the maximum value of the source IP (fragment 3) in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.12 C901970012 Max Value of Source IP (Fragment 4)

Description
This counter records the maximum value of the source IP (fragment 4) in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.13 C901970013 Min Value of Dest IP (Fragment 1)

Description
This counter records the minimum value of the destination IP (fragment 1) in ACL rules.

Usage
None
102-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 102 ACL Flow Statistic

Measurement Point
None

Unit
None

102.14 C901970014 Min Value of Dest IP (Fragment 2)

Description
This counter records the minimum value of the destination IP (fragment 2) in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.15 C901970015 Min Value of Dest IP (Fragment 3)

Description
This counter records the minimum value of the destination IP (fragment 3) in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.16 C901970016 Min Value of Dest IP (Fragment 4)

Description
This counter records the minimum value of the destination IP (fragment 4) in ACL rules.
102-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
None

102.17 C901970017 Max Value of Dest IP (Fragment 1)

Description
This counter records the maximum value of the destination IP (fragment 1) in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.18 C901970018 Max Value of Dest IP (Fragment 2)

Description
This counter records the maximum value of the destination IP (fragment 2) in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 102 ACL Flow Statistic

102.19 C901970019 Max Value of Dest IP (Fragment 3)

Description
This counter records the maximum value of the destination IP (fragment 3) in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.20 C901970020 Max Value of Dest IP (Fragment 4)

Description
This counter records the maximum value of the destination IP (fragment 4) in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.21 C901970021 Min Value of Source Port.

Description
This counter records the minimum value of the source port in ACL rules.

Usage
None

Measurement Point
None
102-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
None

102.22 C901970022 Max Value of Source Port.

Description
This counter records the maximum value of the source port in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.23 C901970023 Min Value of Dest Port.

Description
This counter records the minimum value of the destination port in ACL rules.

Usage
None

Measurement Point
None

Unit
None

102.24 C901970024 Max Value of Dest Port.

Description
This counter records the maximum value of the destination port in ACL rules.

Usage
None
102-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 102 ACL Flow Statistic

Measurement Point
None

Unit
None

102.25 C901970025 Direction (1: IN; 2: OUT)

Description
This counter records the number of the in/out rules (1: IN; 2: OUT) in the ACL.

Usage
None

Measurement Point
None

Unit
None

102.26 C901970026 Number of Packets Filtered (Low 32 bits)

Description
This counter counts the number of filtered packets (low 32 bits).

Usage
None

Measurement Point
None

Unit
None

102-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

102.27 C901970027 Number of Packets Filtered (High 32 bits)

Description
This counter counts the number of filtered packets (high 32 bits).

Usage
None

Measurement Point
None

Unit
None

102.28 C901970028 Number of Bytes Filtered (Low 32 bits)

Description
This counter counts the number of filtered bytes (low 32 bits).

Usage
None

Measurement Point
None

Unit
None

102.29 C901970029 Number of Bytes Filtered (High 32 bits)

Description
This counter counts the number of filtered bytes (high 32 bits).

102-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 102 ACL Flow Statistic

Usage
None

Measurement Point
None

Unit
None

102-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

102-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103

LAPDm Measurement
Table of Contents
Overview ................................................................................................................103-2 C902000001 Number of Error Indications due to T200 expired on SDCCH ............103-3 C902000002 Number of Error Indications due to unsolicited message on SDCCH .103-3 C902000003 Number of Error Indications due to unsolicited DM response on SDCCH ..................................................................................................................103-4 C902000004 Number of Error Indications due to sequence error on SDCCH .........103-5 C902000005 Number of Error Indications due to frame content error on SDCCH ...103-6 C902000006 Number of Error Indications due to SABM command on SDCCH ......103-6 C902000007 Number of Error Indications due to T200 expired on TCH/F ..............103-7 C902000008 Number of Error Indications due to unsolicited message on TCH/F ...103-8 C902000009 Number of Error Indications due to unsolicited DM response on TCH/F ....................................................................................................................103-8 C902000010 Number of Error Indications due to sequence error on TCH/F ...........103-9 C902000011 Number of Error Indications due to frame content error on TCH/F ...103-10 C902000012 Number of Error Indications due to SABM command on TCH/F....... 103-11 C902000013 Number of Error Indications due to T200 expired on TCH/H ............ 103-11 C902000014 Number of Error Indications due to unsolicited message on TCH/H .103-12 C902000015 Number of Error Indications due to unsolicited DM response on TCH/H..................................................................................................................103-13 C902000016 Number of Error Indications due to sequence error on TCH/H .........103-13 C902000017 Number of Error Indications due to frame content error on TCH/H...103-14 C902000018 Number of Error Indications due to SABM command on TCH/H ......103-15 C902000019 Number of Release Indications due to T200 expired on SDCCH .....103-16 C902000020 Number of Release Indications due to unsolicited DM response on SDCCH ................................................................................................................103-16 C902000021 Number of Release Indications due to sequence error on SDCCH ..103-17 C902000022 Number of Release Indications due to T200 expired on TCH/F (signaling) ............................................................................................................103-18 C902000023 Number of Release Indications due to unsolicited DM response on TCH/F (signaling) .................................................................................................103-19 C902000024 Number of Release Indications due to sequence error on TCH/F (signaling) ............................................................................................................103-20 C902000025 Number of Release Indications due to T200 expired on TCH/F (speech) ...............................................................................................................103-21 C902000026 Number of Release Indications due to unsolicited DM response on TCH/F (speech)....................................................................................................103-21

103-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

C902000027 Number of Release Indications due to sequence error on TCH/F (speech) ...............................................................................................................103-22 C902000028 Number of Release Indications due to T200 expired on TCH/F (data) ...................................................................................................................103-23 C902000029 Number of Release Indications due to unsolicited DM response on TCH/F (data) ........................................................................................................103-24 C902000030 Number of Release Indications due to sequence error on TCH/F (data) ...................................................................................................................103-25 C902000031 Number of Release Indications due to T200 expired on TCH/H (signaling) ............................................................................................................103-26 C902000032 Number of Release Indications due to unsolicited DM response on TCH/H (signaling).................................................................................................103-26 C902000033 Number of Release Indications due to sequence error on TCH/H (signaling) ............................................................................................................103-27 C902000034 Number of Release Indications due to T200 expired on TCH/H (speech) ...............................................................................................................103-28 C902000035 Number of Release Indications due to unsolicited DM response on TCH/H (speech) ...................................................................................................103-29 C902000036 Number of Error Indications due to sequence error on TCH/H (speech) ...............................................................................................................103-30 C902000037 Number of Release Indications due to T200 expired on TCH/H (data) ...................................................................................................................103-31 C902000038 Number of Release Indications due to unsolicited DM response on TCH/H (data)........................................................................................................103-31 C902000039 Number of Release Indications due to sequence error on TCH/H (data) ...................................................................................................................103-32 C902000040 Number of Release Indications without Error Ind on SDCCH...........103-33 C902000041 Number of Release Indications without Error Ind on TCH/F (signaling) ............................................................................................................103-33 C902000042 Number of Release Indications without Error Ind on TCH/F (speech) ...............................................................................................................103-34 C902000043 Number of Release Indications without Error Ind on TCH/F (data)...103-34 C902000044 Number of Release Indications without Error Ind on TCH/H (signaling) ............................................................................................................103-35 C902000045 Number of Release Indications without Error Ind on TCH/H (speech) ...............................................................................................................103-35 C902000046 Number of Release Indications without Error Ind on TCH/H (data) ..103-36 C902000047 Number of Error Indications Due to Handover Access Level Low ....103-36

103.1 Overview
LAPDm measurement is used to find out the number of LAPDm-related processes occurred, such as BTS sending the ERROR INDICATION message and the RELEASE INDICATION message to BSC due to LAPDm's transceiving messages.

103-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

Statistic unit in this measurement is cell.

103.2 C902000001 Number of Error Indications due to T200 expired on SDCCH

Description
During the call process, LAPDm sends I frame, SAMB frame and DISC frame on SDCCH. If there is no response for a long time, LAPDm sends the ERROR INDICATION message to BSC, and the message contains the cause of "T200 expired".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "T200 expired". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-1.
Figure 103-1 Number of Error Indications due to T200 expired on SDCCH

The

Unit
Times

103.3 C902000002 Number of Error Indications due to unsolicited message on SDCCH

Description
During the call process, if LAPDm receives unexpected message on SDCCH, it will send the ERROR INDICATION message to BSC, and the message contains the cause of "unsolicited message".

103-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "unsolicited message". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-2.
Figure 103-2 Number of Error Indications due to unsolicited message on SDCCH

The

Unit
Times

103.4 C902000003 Number of Error Indications due to unsolicited DM response on SDCCH

Description
During the call process, if LAPDm receives unexpected DM response message on SDCCH, it will send the ERROR INDICATION message to BSC, and the message contains the cause of "unsolicited DM response".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "unsolicited DM response". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-3. The

103-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

Figure 103-3 Number of Error Indications due to unsolicited DM response on SDCCH

Unit
Times

103.5 C902000004 Number of Error Indications due to sequence error on SDCCH

Description
During the call process, if LAPDm receives message with incorrect sequence number on SDCCH, it will send the ERROR INDICATION message to BSC, and the message contains the cause of "sequence error".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "sequence error". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-4.
Figure 103-4 Number of Error Indications due to sequence error on SDCCH

The

Unit
Times

103-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

103.6 C902000005 Number of Error Indications due to frame content error on SDCCH
Description
During the call process, if LAPDm receives message with incorrect content on SDCCH, it will send the ERROR INDICATION message to BSC, and the message contains the cause of "frame content error".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "frame content error". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-5.
Figure 103-5 Number of Error Indications due to frame content error on SDCCH

The

Unit
Times

103.7 C902000006 Number of Error Indications due to SABM command on SDCCH

Description
During the call process, if LAPDm receives SABM frame after the SDCCH connection is established, LAPDm will send the ERROR INDICATION message to BSC, and the message contains the cause of "SABM command".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "SABM command". This counter is supported in version V6.20.61 or later.
103-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-6.
Figure 103-6 Number of Error Indications due to SABM command on SDCCH

The

Unit
Times

103.8 C902000007 Number of Error Indications due to T200 expired on TCH/F

Description
During the call process, LAPDm sends I frame, SAMB frame and DISC frame on TCH/F. If there is no response for a long time, LAPDm will send the ERROR INDICATION message to BSC, and the message contains the cause of "T200 expired".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "T200 expired". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-7.
Figure 103-7 Number of Error Indications due to T200 expired on TCH/F

The

103-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

103.9 C902000008 Number of Error Indications due to unsolicited message on TCH/F

Description
During the call process, if LAPDm receives unexpected message on TCH/F, it will send the ERROR INDICATION message to BSC, and the message contains the cause of "unsolicited message".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "unsolicited message". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-8.
Figure 103-8 Number of Error Indications due to unsolicited message on TCH/F

The

Unit
Times

103.10 C902000009 Number of Error Indications due to unsolicited DM response on TCH/F

Description
During the call process, if LAPDm receives unexpected DM response message on TCH/F, it will send the ERROR INDICATION message to BSC, and the message contains the cause of "unsolicited DM response".

103-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "unsolicited DM response". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-9.
Figure 103-9 C902000009

The

Unit
Times

103.11 C902000010 Number of Error Indications due to sequence error on TCH/F

Description
During the call process, if LAPDm receives message with incorrect sequence number on TCH/F, it will send the ERROR INDICATION message to BSC, and the message contains the cause of "sequence error".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "sequence error". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-10. The

103-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 103-10 Number of Error Indications due to sequence error on TCH/F

Unit
Times

103.12 C902000011 Number of Error Indications due to frame content error on TCH/F
Description
During the call process, if LAPDm receives message with incorrect content on TCH/F, it will send the ERROR INDICATION message to BSC, and the message contains the cause of "frame content error".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "frame content error". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-11.
Figure 103-11 Number of Error Indications due to frame content error on TCH/F

The

Unit
Times

103-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

103.13 C902000012 Number of Error Indications due to SABM command on TCH/F

Description
During the call process, if LAPDm receives SABM frame after the TCH/F connection is established, LAPDm will send the ERROR INDICATION message to BSC, and the message contains the cause of "SABM command".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "SABM command". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-12.
Figure 103-12 Number of Error Indications due to SABM command on TCH/F

The

Unit
Times

103.14 C902000013 Number of Error Indications due to T200 expired on TCH/H

Description
During the call process, LAPDm sends I frame, SAMB frame and DISC frame on TCH/H. If there is no response for a long time, LAPDm will send the ERROR INDICATION message to BSC, and the message contains the cause of "T200 expired".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "T200 expired". This counter is supported in version V6.20.61 or later.
103-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-13.
Figure 103-13 Number of Error Indications due to T200 expired on TCH/H

The

Unit
Times

103.15 C902000014 Number of Error Indications due to unsolicited message on TCH/H

Description
During the call process, if LAPDm receives unexpected message on TCH/H, it will send the ERROR INDICATION message to BSC, and the message contains the cause of "unsolicited message".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "unsolicited message". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-14.
Figure 103-14 Number of Error Indications due to unsolicited message on TCH/H

The

103-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

Unit
Times

103.16 C902000015 Number of Error Indications due to unsolicited DM response on TCH/H

Description
During the call process, if LAPDm receives unexpected DM response message on TCH/H, it will send the ERROR INDICATION message to BSC, and the message contains the cause of "unsolicited DM response".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "unsolicited DM response". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-15. The

Figure 103-15 Number of Error Indications due to unsolicited DM response on TCH/H

Unit
Times

103.17 C902000016 Number of Error Indications due to sequence error on TCH/H

Description
During the call process, if LAPDm receives message with incorrect sequence number on TCH/H, it will send the ERROR INDICATION message to BSC, and the message contains the cause of "sequence error".

103-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "sequence error". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-16.
Figure 103-16 Number of Error Indications due to sequence error on TCH/H

The

Unit
Times

103.18 C902000017 Number of Error Indications due to frame content error on TCH/H
Description
During the call process, if LAPDm receives message with incorrect content on TCH/H, it will send the ERROR INDICATION message to BSC, and the message contains the cause of "frame content error".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "frame content error". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-17. The

103-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

Figure 103-17 Number of Error Indications due to frame content error on TCH/H

Unit
Times

103.19 C902000018 Number of Error Indications due to SABM command on TCH/H

Description
During the call process, if LAPDm receives SABM frame after the TCH/H connection is established, LAPDm will send the ERROR INDICATION message to BSC, and the message contains the cause of "SABM command".

Usage
This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "SABM command". This counter is supported in version V6.20.61 or later.

Measurement Point
The counter counts when BSC receives the ERROR INDICATION message. measurement point is A, as shown in Figure 103-18.
Figure 103-18 Number of Error Indications due to SABM command on TCH/H

The

Unit
Times

103-15 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

103.20 C902000019 Number of Release Indications due to T200 expired on SDCCH

Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on SDCCH and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "T200 expired".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "T200 expired". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "T200 expired"). The measurement point is A, as shown in Figure 103-19.
Figure 103-19 Number of Release Indications due to T200 expired on SDCCH

Unit
Times

103.21 C902000020 Number of Release Indications due to unsolicited DM response on SDCCH

Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on SDCCH and is stable, BSC simultaneously receives the ERROR INDICATION message and the

103-16 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "unsolicited DM response".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "unsolicited DM response". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "unsolicited DM response"). The measurement point is A, as shown in Figure 103-20.
Figure 103-20 Number of Release Indications due to unsolicited DM response on SDCCH

Unit
Times

103.22 C902000021 Number of Release Indications due to sequence error on SDCCH

Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on SDCCH and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "sequence error".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "sequence error". This counter is supported in version V6.20.61 or later.

103-17 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "sequence error"). The measurement point is A, as shown in Figure 103-21.
Figure 103-21 Number of Release Indications due to sequence error on SDCCH

Unit
Times

103.23 C902000022 Number of Release Indications due to T200 expired on TCH/F (signaling)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/F and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "T200 expired".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "T200 expired". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "T200 expired"). The measurement point is A, as shown in Figure 103-22.

103-18 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

Figure 103-22 Number of Release Indications due to T200 expired on TCH/F (signaling)

Unit
Times

103.24 C902000023 Number of Release Indications due to unsolicited DM response on TCH/F (signaling)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/F and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "unsolicited DM response".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "unsolicited DM response". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "unsolicited DM response"). The measurement point is A, as shown in Figure 103-23.
Figure 103-23 Number of Release Indications due to unsolicited DM response on TCH/F (signaling)

103-19 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

103.25 C902000024 Number of Release Indications due to sequence error on TCH/F (signaling)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/F and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "sequence error".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "sequence error". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "sequence error"). The measurement point is A, as shown in Figure 103-24.
Figure 103-24 Number of Release Indications due to sequence error on TCH/F (signaling)

Unit
Times

103-20 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

103.26 C902000025 Number of Release Indications due to T200 expired on TCH/F (speech)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/F and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "T200 expired".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "T200 expired". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "T200 expired"). The measurement point is A, as shown in Figure 103-25.
Figure 103-25 Number of Release Indications due to T200 expired on TCH/F (speech)

Unit
Times

103.27 C902000026 Number of Release Indications due to unsolicited DM response on TCH/F (speech)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/F and is stable, BSC simultaneously receives the ERROR INDICATION message and the

103-21 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "unsolicited DM response".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "unsolicited DM response". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "unsolicited DM response"). The measurement point is A, as shown in Figure 103-26.
Figure 103-26 Number of Release Indications due to unsolicited DM response on TCH/F (speech)

Unit
Times

103.28 C902000027 Number of Release Indications due to sequence error on TCH/F (speech)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/F and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "sequence error".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "sequence error". This counter is supported in version V6.20.61 or later.
103-22 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "sequence error"). The measurement point is A, as shown in Figure 103-27.
Figure 103-27 Number of Release Indications due to sequence error on TCH/F (speech)

Unit
Times

103.29 C902000028 Number of Release Indications due to T200 expired on TCH/F (data)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/F and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "T200 expired".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "T200 expired". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "T200 expired"). The measurement point is A, as shown in Figure 103-28.

103-23 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 103-28 Number of Release Indications due to T200 expired on TCH/F (data)

Unit
Times

103.30 C902000029 Number of Release Indications due to unsolicited DM response on TCH/F (data)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/F and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "unsolicited DM response".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "unsolicited DM response". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "unsolicited DM response"). The measurement point is A, as shown in Figure 103-29.
Figure 103-29 Number of Release Indications due to unsolicited DM response on TCH/F (data)

103-24 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

Unit
Times

103.31 C902000030 Number of Release Indications due to sequence error on TCH/F (data)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/F and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "sequence error".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "sequence error". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "sequence error"). The measurement point is A, as shown in Figure 103-30.
Figure 103-30 Number of Release Indications due to sequence error on TCH/F (data)

Unit
Times

103-25 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

103.32 C902000031 Number of Release Indications due to T200 expired on TCH/H (signaling)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/H and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "T200 expired".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "T200 expired". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "T200 expired"). The measurement point is A, as shown in Figure 103-31.
Figure 103-31 Number of Release Indications due to T200 expired on TCH/H (signaling)

Unit
Times

103.33 C902000032 Number of Release Indications due to unsolicited DM response on TCH/H (signaling)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/H and is stable, BSC simultaneously receives the ERROR INDICATION message and the

103-26 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "unsolicited DM response".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "unsolicited DM response". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "unsolicited DM response"). The measurement point is A, as shown in Figure 103-32.
Figure 103-32 Number of Release Indications due to unsolicited DM response on TCH/H (signaling)

Unit
Times

103.34 C902000033 Number of Release Indications due to sequence error on TCH/H (signaling)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/H and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "sequence error".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "sequence error". This counter is supported in version V6.20.61 or later.
103-27 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "sequence error"). The measurement point is A, as shown in Figure 103-33.
Figure 103-33 Number of Release Indications due to sequence error on TCH/H (signaling)

Unit
Times

103.35 C902000034 Number of Release Indications due to T200 expired on TCH/H (speech)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/H and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "T200 expired".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "T200 expired". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "T200 expired"). The measurement point is A, as shown in Figure 103-34.

103-28 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

Figure 103-34 Number of Release Indications due to T200 expired on TCH/H (speech)

Unit
Times

103.36 C902000035 Number of Release Indications due to unsolicited DM response on TCH/H (speech)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/H and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "unsolicited DM response".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "unsolicited DM response". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "unsolicited DM response"). The measurement point is A, as shown in Figure 103-35.
Figure 103-35 Number of Release Indications due to unsolicited DM response on TCH/H (speech)

103-29 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Unit
Times

103.37 C902000036 Number of Error Indications due to sequence error on TCH/H (speech)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/H and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "sequence error".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "sequence error". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "sequence error"). The measurement point is A, as shown in Figure 103-36.
Figure 103-36 Number of Error Indications due to sequence error on TCH/H (speech)

Unit
Times

103-30 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

103.38 C902000037 Number of Release Indications due to T200 expired on TCH/H (data)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/H and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "T200 expired".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "T200 expired". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "T200 expired"). The measurement point is A, as shown in Figure 103-37.
Figure 103-37 Number of Release Indications due to T200 expired on TCH/H (data)

Unit
Times

103.39 C902000038 Number of Release Indications due to unsolicited DM response on TCH/H (data)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/H and is stable, BSC simultaneously receives the ERROR INDICATION message and the

103-31 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "unsolicited DM response".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "unsolicited DM response". This counter is supported in version V6.20.61 or later.

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "unsolicited DM response"). The measurement point is A, as shown in Figure 103-38.
Figure 103-38 Number of Release Indications due to unsolicited DM response on TCH/H (data)

Unit
Times

103.40 C902000039 Number of Release Indications due to sequence error on TCH/H (data)
Description
During the call process, BTS usually sends the ERROR INDICATION message to BSC before sending the RELEASE INDICATION message to BSC. When the call is on TCH/H and is stable, BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message from BTS, and the ERROR INDICATION message contains the cause of "sequence error".

Usage
This counter counts the number of RELEASE INDICATION messages, received by BSC from BTS, that are due to the cause of "sequence error". This counter is supported in version V6.20.61 or later.
103-32 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

Measurement Point
When the call is in stable status, the counter counts when BSC simultaneously receives the ERROR INDICATION message and the RELEASE INDICATION message (the ERROR INDICATION message contains the cause of "sequence error"). The measurement point is A, as shown in Figure 103-39.
Figure 103-39 Number of Release Indications due to sequence error on TCH/H (data)

Unit
Times

103.41 C902000040 Number of Release Indications without Error Ind on SDCCH

Description
This counter is incremented each time an Abis Rel Ind message is received in the case that no Abis Error Ind message is received when the SDCCH is occupied by an MS.

Usage
None

Measurement Point
None

Unit
Times

103.42 C902000041 Number of Release Indications without Error Ind on TCH/F (signaling)
Description
This counter is incremented each time an Abis Rel Ind message is received in the case that no Abis Error Ind message is received when the signaling TCH/F is occupied by an MS.
103-33 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Usage
None

Measurement Point
None

Unit
Times

103.43 C902000042 Number of Release Indications without Error Ind on TCH/F (speech)
Description
This counter is incremented each time an Abis Rel Ind message is received in the case that no Abis Error Ind message is received when the speech TCH/F is occupied by an MS.

Usage
None

Measurement Point
None

Unit
Times

103.44 C902000043 Number of Release Indications without Error Ind on TCH/F (data)
Description
This counter is incremented each time an Abis Rel Ind message is received in the case that no Abis Error Ind message is received when the data TCH/F is occupied by an MS.

Usage
None

Measurement Point
None
103-34 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 103 LAPDm Measurement

Unit
Times

103.45 C902000044 Number of Release Indications without Error Ind on TCH/H (signaling)
Description
This counter is incremented each time an Abis Rel Ind message is received in the case that no Abis Error Ind message is received when the signaling TCH/H is occupied by an MS.

Usage
None

Measurement Point
None

Unit
Times

103.46 C902000045 Number of Release Indications without Error Ind on TCH/H (speech)
Description
This counter is incremented each time an Abis Rel Ind message is received in the case that no Abis Error Ind message is received when the speech TCH/H is occupied by an MS.

Usage
None

Measurement Point
None

Unit
Times

103-35 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

103.47 C902000046 Number of Release Indications without Error Ind on TCH/H (data)
Description
This counter is incremented each time an Abis Rel Ind message is received in the case that no Abis Error Ind message is received when the data TCH/H is occupied by an MS.

Usage
None

Measurement Point
None

Unit
Times

103.48 C902000047 Number of Error Indications Due to Handover Access Level Low
Description
This counter counts the number of times that the target RANCS instance receives an ERR IND message with the reason value "0x11" when handover to the source cell is allowed.

Measurement Point
During an asynchronous handover, the BTS determines that no physical information message is to be sent during the handover when detecting that the level in the handover access message does not meet the handover condition. At the same time, the BTS sends an ERR IND message containing the reason value "0x11" to the BSC. This counter is incremented each time the target RANCS instance receives such an ERR IND message.

Unit
Number of times

103-36 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 104

Access Control Detailed Cause Measurement

Table of Contents
Overview ................................................................................................................104-1 C902010001 Number of PS Uplink BandWidth Allocated More than Overbooking..104-2 C902010002 Number of PS Uplink BandWidth Measured More than C2 ...............104-3 C902010003 Number of that Sum of PS Uplink BandWidth Measured and Current BandWidth Allocated More than C1........................................................................104-4 C902010004 Number of PS Downlink BandWidth Allocated More than Overbooking...........................................................................................................104-5 C902010005 Number of PS Downlink BandWidth Measured More than C2............104-6 C902010006 Number of that Sum of PS Downlink BandWidth Measured and Current BandWidth Allocated More than C1 ...........................................................104-7 C902010007 Number of CS Uplink BandWidth Allocated More than Overbooking .104-8 C902010008 Number of CS Uplink BandWidth Measured More than C2................104-9 C902010009 Number of that Sum of CS Uplink BandWidth Measured and Current BandWidth Allocated More than C1......................................................................104-10 C902010010 Number of CS Downlink BandWidth Allocated More than Overbooking......................................................................................................... 104-11 C902010011 Number of CS Downlink BandWidth Measured More than C2..........104-12 C902010012 Number of that Sum of CS Downlink BandWidth Measured and Current BandWidth Allocated More than C1 .........................................................104-13

104.1 Overview
Access control detailed cause measurement involves uplink/downlink CS and PS access process. Statistic unit in this measurement is cell. The measurement point of access control cause statistics for PS-bandwidth allocation is shown in Figure 104-1.

104-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 104-1 Access Control of PS-Bandwidth Allocation

The measurement point of access control cause statistics for CS-bandwidth allocation is shown in Figure 104-2.
Figure 104-2 Access Control of CS-Bandwidth Allocation

104.2 C902010001 Number of PS Uplink BandWidth Allocated More than Overbooking

Description
This counter counts the number of PS uplink bandwidth access rejects due to allocated uplink bandwidth exceeding OverBooking. When BSC has new PS service to be activated, if BSC control plane judges that the total current theoretically-allocated uplink bandwidth plus the theoretically-allocated uplink bandwidth needed by the service exceeds the predefined rated bandwidth of the resource pool, that is, OverBooking, the counter increments.

Usage
The counter is used to find out the frequency of allocated uplink bandwidth for PS service exceeding OverBooking. This counter is supported in version V6.20.61 or later.

104-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 104 Access Control Detailed Cause Measurement

Measurement Point
When BSC has new PS service to be activated, if BSC control plane judges that the allocated uplink bandwidth exceeds OverBooking, the counter counts. The measurement point is A, as shown in Figure 104-3.
Figure 104-3 Number of PS Uplink Bandwidth Allocated More than Overbooking

Unit
Times

104.3 C902010002 Number of PS Uplink BandWidth Measured More than C2

Description
This counter counts the number of PS uplink bandwidth access rejects due to actual uplink bandwidth exceeding C2, which is the safe allocation lower limit about bandwidth at the resource pool. When BSC has new PS service to be activated, if BSC control plane judges that the actual uplink bandwidth of the resource pool exceeds C2, which is the safe allocation lower limit about bandwidth at the resource pool, the counter increments.

Usage
This counter is used to find out the frequency of actual uplink bandwidth for PS service exceeding C2, which is the safe allocation lower limit about bandwidth at the resource pool. This counter is supported in version V6.20.61 or later.

Measurement Point
When BSC has new PS service to be activated, if BSC control plane judges that the actual uplink bandwidth of the resource pool exceeds C2, which is the safe allocation lower limit about bandwidth at the resource pool, the counter counts. The measurement point is A, as shown in Figure 104-4.

104-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 104-4 Number of PS Uplink Bandwidth Measured More than C2

Unit
Times

104.4 C902010003 Number of that Sum of PS Uplink BandWidth Measured and Current BandWidth Allocated More than C1
Description
This counter counts the number of PS uplink bandwidth access rejects due to actual uplink bandwidth plus the bandwidth allocated for the current service exceeding C1, which is the safe allocation upper limit about bandwidth at the resource pool. When BSC has new PS service to be activated, if the following two conditions are satisfied, the counter increments: l BSC control plane judges that the actual uplink bandwidth of the resource pool is smaller than C2, which is the safe allocation lower limit about bandwidth at the resource pool. l The actual uplink bandwidth of the resource pool plus theoretically-allocated uplink bandwidth for the service exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool.

Usage
This counter is used to find out the frequency of actual uplink bandwidth for PS service plus the bandwidth allocated for the service exceeding C1, which is the safe allocation upper limit about bandwidth at the resource pool. This counter is supported in version V6.20.61 or later.

Measurement Point
When BSC has new PS service to be activated, if BSC control plane judges that the actual uplink bandwidth plus the uplink bandwidth allocated for the service exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool, the counter counts. The measurement point is A, as shown in Figure 104-5.
104-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 104 Access Control Detailed Cause Measurement

Figure 104-5 Number of that Sum of PS Uplink Bandwidth Measured and Current Bandwidth Allocated More than C1

Unit
Times

104.5 C902010004 Number of PS Downlink BandWidth Allocated More than Overbooking

Description
This counter counts the number of PS downlink bandwidth access rejects due to allocated downlink bandwidth exceeding OverBooking. When BSC has new PS service to be activated, if BSC control plane judges that the total current theoretically-allocated downlink bandwidth plus the theoretically-allocated downlink bandwidth needed by the service exceeds the predefined rated bandwidth of the resource pool, that is, OverBooking, the counter increments.

Usage
The counter is used to find out the frequency of allocated downlink bandwidth for PS service exceeding OverBooking. This counter is supported in version V6.20.61 or later.

Measurement Point
When BSC has new PS service to be activated, if BSC control plane judges that the allocated downlink bandwidth exceeds OverBooking, the counter counts. The measurement point is A, as shown in Figure 104-6.

104-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 104-6 Number of PS Downlink Bandwidth Allocated More than Overbooking

Unit
Times

104.6 C902010005 Number of PS Downlink BandWidth Measured More than C2

Description
This counter counts the number of PS downlink bandwidth access rejects due to actual downlink bandwidth exceeding C2, which is the safe allocation lower limit about bandwidth at the resource pool. When BSC has new PS service to be activated, if BSC control plane judges that the actual downlink bandwidth of the resource pool exceeds C2, which is the safe allocation lower limit about bandwidth at the resource pool, the counter increments.

Usage
This counter is used to find out the frequency of actual downlink bandwidth for PS service exceeding C2, which is the safe allocation lower limit about bandwidth at the resource pool. This counter is supported in version V6.20.61 or later.

Measurement Point
When BSC has new PS service to be activated, if BSC control plane judges that the actual downlink bandwidth of the resource pool exceeds C2, which is the safe allocation lower limit about bandwidth at the resource pool, the counter counts. The measurement point is A, as shown in Figure 104-7.

104-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 104 Access Control Detailed Cause Measurement

Figure 104-7 Number of PS Downlink Bandwidth Measured More than C2

Unit
Times

104.7 C902010006 Number of that Sum of PS Downlink BandWidth Measured and Current BandWidth Allocated More than C1
Description
This counter counts the number of PS downlink bandwidth access rejects due to actual downlink bandwidth plus the bandwidth allocated for the current service exceeding C1, which is the safe allocation upper limit about bandwidth at the resource pool. When BSC has new PS service to be activated, if the following two conditions are satisfied, the counter increments: l BSC control plane judges that the actual downlink bandwidth of the resource pool is smaller than C2, which is the safe allocation lower limit about bandwidth at the resource pool. l The actual downlink bandwidth of the resource pool plus theoretically-allocated downlink bandwidth for the service exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool.

Usage
This counter is used to find out the frequency of actual downlink bandwidth for PS service plus the bandwidth allocated for the service exceeding C1, which is the safe allocation upper limit about bandwidth at the resource pool. This counter is supported in version V6.20.61 or later.

Measurement Point
When BSC has new PS service to be activated, if BSC control plane judges that the actual downlink bandwidth plus the downlink bandwidth allocated for the service exceeds C1,

104-7 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

which is the safe allocation upper limit about bandwidth at the resource pool, the counter counts. The measurement point is A, as shown in Figure 104-8.
Figure 104-8 Number of that Sum of PS Downlink Bandwidth Measured and Current Bandwidth Allocated More than C1

Unit
Times

104.8 C902010007 Number of CS Uplink BandWidth Allocated More than Overbooking

Description
This counter counts the number of CS uplink bandwidth access rejects due to allocated uplink bandwidth exceeding OverBooking. When BSC has new CS service to be activated, if BSC control plane judges that the total current theoretically-allocated uplink bandwidth plus the theoretically-allocated uplink bandwidth needed by the service exceeds the predefined rated bandwidth of the resource pool, that is, OverBooking, the counter increments.

Usage
The counter is used to find out the frequency of allocated uplink bandwidth for CS service exceeding OverBooking. This counter is supported in version V6.20.61 or later.

Measurement Point
When BSC has new CS service to be activated, if BSC control plane judges that the allocated uplink bandwidth exceeds OverBooking, the counter counts. The measurement point is A, as shown in Figure 104-9.

104-8 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 104 Access Control Detailed Cause Measurement

Figure 104-9 Number of CS Uplink Bandwidth Allocated More than Overbooking

Unit
Times

104.9 C902010008 Number of CS Uplink BandWidth Measured More than C2

Description
This counter counts the number of CS uplink bandwidth access rejects due to actual uplink bandwidth exceeding C2, which is the safe allocation lower limit about bandwidth at the resource pool. When BSC has new CS service to be activated, if BSC control plane judges that the actual uplink bandwidth of the resource pool exceeds C2, which is the safe allocation lower limit about bandwidth at the resource pool, the counter increments.

Usage
This counter is used to find out the frequency of actual uplink bandwidth for CS service exceeding C2, which is the safe allocation lower limit about bandwidth at the resource pool. This counter is supported in version V6.20.61 or later.

Measurement Point
When BSC has new CS service to be activated, if BSC control plane judges that the actual uplink bandwidth of the resource pool exceeds C2, which is the safe allocation lower limit about bandwidth at the resource pool, the counter counts. The measurement point is A, as shown in Figure 104-10.

104-9 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 104-10 Number of CS Uplink Bandwidth Measured More than C2

Unit
Times

104.10 C902010009 Number of that Sum of CS Uplink BandWidth Measured and Current BandWidth Allocated More than C1
Description
This counter counts the number of CS uplink bandwidth access rejects due to actual uplink bandwidth plus the bandwidth allocated for the current service exceeding C1, which is the safe allocation upper limit about bandwidth at the resource pool. When BSC has new CS service to be activated, if the following two conditions are satisfied, the counter increments: l BSC control plane judges that the actual uplink bandwidth of the resource pool is smaller than C2, which is the safe allocation lower limit about bandwidth at the resource pool. l The actual uplink bandwidth of the resource pool plus theoretically-allocated uplink bandwidth for the service exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool.

Usage
This counter is used to find out the frequency of actual uplink bandwidth for CS service plus the bandwidth allocated for the service exceeding C1, which is the safe allocation upper limit about bandwidth at the resource pool. This counter is supported in version V6.20.61 or later. When BSC has new CS service to be activated, if BSC control plane judges that the actual uplink bandwidth plus the uplink bandwidth allocated for the service exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool, the counter counts. The measurement point is A, as shown in Figure 104-11.

104-10 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 104 Access Control Detailed Cause Measurement

Figure 104-11 Number of that Sum of CS Uplink Bandwidth Measured and Current Bandwidth Allocated More than C1

Measurement Point Unit

Times

104.11 C902010010 Number of CS Downlink BandWidth Allocated More than Overbooking

Description
This counter counts the number of CS downlink bandwidth access rejects due to allocated downlink bandwidth exceeding OverBooking. When BSC has new CS service to be activated, if BSC control plane judges that the total current theoretically-allocated downlink bandwidth plus the theoretically-allocated downlink bandwidth needed by the service exceeds the predefined rated bandwidth of the resource pool, that is, OverBooking, the counter increments.

Usage
The counter is used to find out the frequency of allocated downlink bandwidth for CS service exceeding OverBooking. This counter is supported in version V6.20.61 or later.

Measurement Point
When BSC has new CS service to be activated, if BSC control plane judges that the allocated downlink bandwidth exceeds OverBooking, the counter counts. The measurement point is A, as shown in Figure 104-12.

104-11 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 104-12 Number of CS Downlink Bandwidth Allocated More than Overbooking

Unit
Times

104.12 C902010011 Number of CS Downlink BandWidth Measured More than C2

Description
This counter counts the number of CS downlink bandwidth access rejects due to actual downlink bandwidth exceeding C2, which is the safe allocation lower limit about bandwidth at the resource pool. When BSC has new CS service to be activated, if BSC control plane judges that the actual downlink bandwidth of the resource pool exceeds C2, which is the safe allocation lower limit about bandwidth at the resource pool, the counter increments.

Usage
This counter is used to find out the frequency of actual downlink bandwidth for CS service exceeding C2, which is the safe allocation lower limit about bandwidth at the resource pool. This counter is supported in version V6.20.61 or later.

Measurement Point
When BSC has new CS service to be activated, if BSC control plane judges that the actual downlink bandwidth of the resource pool exceeds C2, which is the safe allocation lower limit about bandwidth at the resource pool, the counter counts. The measurement point is A, as shown in Figure 104-13.

104-12 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 104 Access Control Detailed Cause Measurement

Figure 104-13 Number of CS Downlink Bandwidth Measured More than C2

Unit
Times

104.13 C902010012 Number of that Sum of CS Downlink BandWidth Measured and Current BandWidth Allocated More than C1
Description
This counter counts the number of CS downlink bandwidth access rejects due to actual downlink bandwidth plus the bandwidth allocated for the current service exceeding C1, which is the safe allocation upper limit about bandwidth at the resource pool. When BSC has new CS service to be activated, if the following two conditions are satisfied, the counter increments: l BSC control plane judges that the actual downlink bandwidth of the resource pool is smaller than C2, which is the safe allocation lower limit about bandwidth at the resource pool. l The actual downlink bandwidth of the resource pool plus theoretically-allocated downlink bandwidth for the service exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool.

Usage
This counter is used to find out the frequency of actual downlink bandwidth for CS service plus the bandwidth allocated for the service exceeding C1, which is the safe allocation upper limit about bandwidth at the resource pool. This counter is supported in version V6.20.61 or later.

Measurement Point
When BSC has new CS service to be activated, if BSC control plane judges that the actual downlink bandwidth plus the downlink bandwidth allocated for the service exceeds C1,

104-13 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

which is the safe allocation upper limit about bandwidth at the resource pool, the counter counts. The measurement point is A, as shown in Figure 104-14.
Figure 104-14 Number of that Sum of CS Downlink Bandwidth Measured and Current Bandwidth Allocated More than C1

Unit
Times

104-14 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 105

BSC Group Call Setup Measurement

Table of Contents
Overview ................................................................................................................105-1 C902020001 Number of VGCS setup attempts ......................................................105-1 C902020002 Number of VGCS setup success .......................................................105-2 C902020003 Number of VGCS setup failure ..........................................................105-3 C902020004 Number of VBS setup attempts .........................................................105-3 C902020005 Number of VBS setup success ..........................................................105-4 C902020006 Number of VBS setup failure .............................................................105-5

105.1 Overview
This measurement performs statistics for relevant performance indices during the setup process of VGCS service and VBS service, including the number of attempts, successes, and failures of service setup. Statistics object: BSC

105.2 C902020001 Number of VGCS setup attempts

Description
This counter counts the number of attempts of setting up VGCS. When BSC receives the VGCS SETUP message (indicating VGCS call), the counter increments. The measurement point is A1, as shown in Figure 105-1.

105-1 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 105-1 Establishing VGCS (Success)

This counter is supported in version V8.00.00 or later.

Unit
Times

Statistics Object
BSC

105.3 C902020002 Number of VGCS setup success

Description
This counter counts the number of successes in setting up VGCS. When BSC sends the VGCS SETUP ACKNOWLEDGE message (corresponding to VGCS call) to MSC, the counter increments. The measurement point is A2, as shown in Figure 105-2.
Figure 105-2 Establishing VGCS (Success)

This counter is supported in version V8.00.00 or later.

Unit
Times
105-2 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 105 BSC Group Call Setup Measurement

Statistics Object
BSC

105.4 C902020003 Number of VGCS setup failure

Description
This counter counts the number of failures in setting up VGCS. When BSC sends the VGCS SETUP REFUSE message (corresponding to VGCS call) to MSC, the counter increments. The measurement point is A1, as shown in Figure 105-3.
Figure 105-3 Establishing VGCS (Failure)

This counter is supported in version V8.00.00 or later.

Unit
Times

Statistics Object
BSC

105.5 C902020004 Number of VBS setup attempts

Description
This counter counts the number of attempts of setting up VBS. When BSC receives the VBS SETUP message (indicating VBS call), the counter increments. The measurement point is A1, as shown in Figure 105-4.

105-3 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

Figure 105-4 Establishing VBS (Success)

This counter is supported in version V8.00.00 or later.

Unit
Times

Statistics Object
BSC

105.6 C902020005 Number of VBS setup success

Description
This counter counts the number of BSC's successfully setting up VBS channel in a cell. When BSC sends the VBS SETUP ACKNOWLEDGE message (corresponding to VBS call) to MSC, the counter increments. The measurement point is A2, as shown in Figure 105-5.
Figure 105-5 Establishing VBS (Success)

This counter is supported in version V8.00.00 or later.

105-4 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 105 BSC Group Call Setup Measurement

Unit
Times

Statistics Object
BSC

105.7 C902020006 Number of VBS setup failure

Description
This counter counts the number of failures in setting up VBS. When BSC sends the VBS SETUP REFUSE message (corresponding to VBS call) to MSC, the counter increments. The measurement point is A1, as shown in Figure 105-6.
Figure 105-6 Establishing VBS (Failure)

This counter is supported in version V8.00.00 or later.

Unit
Times

Statistics Object
BSC

105-5 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

ZXG10 iBSC Performance Counter Reference

This page intentionally left blank.

105-6 SJ-20110531095035-015|2013-04-25 (R1.7) ZTE Proprietary and Confidential

Chapter 106

VGCS Measurement
Table of Contents
Overview ................................................................................................................106-2 C902030001 Number of VGCS assignment attempts .............................................106-2 C902030002 Number of VGCS assignment success..............................................106-3 C902030003 Number of VGCS assignment failure .................................................106-3 C902030004 Number of VGCS Inter-BSC outgoing handover attempts of Talker ...106-4 C902030005 Number of VGCS Inter-BSC outgoing handover execution of Talker..106-5 C902030006 Number of VGCS Inter-BSC outgoing handover success of Talker ....106-6 C902030007 Number of VGCS Inter-BSC outgoing handover failure of Talker .......106-7 C902030008 Number of VGCS Inter-BSC incoming handover attempts of Talker...106-8 C902030009 Number of VGCS Inter-BSC incoming handover execution of Talker .106-9 C902030010 Number of VGCS Inter-BSC incoming handover success of Talker..106-10 C902030011 Number of VGCS channel request attempts for NOTIFICATION RESPONSE of Listener........................................................................................106-10 C902030012 Number of VGCS channel request success for NOTIFICATION RESPONSE of Listener........................................................................................ 106-11 C902030013 Number of VGCS channel request failure for NOTIFICATION RESPONSE of Listener........................................................................................106-12 C902030014 Number of VGCS channel release for Listener detection .................106-13 C902030015 Number of Talker drops due to radio link failure ...............................106-14 C902030016 Number of Talker quit ..................................................