Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
ZTE CORPORATION ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P. R. China 518057 Tel: (86) 755 26771900 Fax: (86) 755 26770801 URL: http://ensupport.zte.com.cn E-mail: support@zte.com.cn
LEGAL INFORMATION Copyright 2006 ZTE CORPORATION. The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations. All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION or of their respective owners. This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the information contained herein. ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter herein. ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice. Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information. The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History Revison No. R1.3 R1.2 R1.1 R1.0 Revision Date 20110730 20110310 20101010 20100720 Revision Reason Updated to V6.20.614d Updated to V6.20.614c Updated to V6.20.614 First edition
Content
C900040013 Number of EGPRS DL TBF release due to instance suspension ...............................................21 C900040014 Number of EGPRS DL TBF release due to inner abnormal......................................................21 C900040015 Number of EGPRS DL signaling TBF establishment .......................................................22 C900040016 Number of EGPRS DL data TBF establishment .......................................................22 C900040017 Average number of GPRS DL TBF simultaneous establishment ...................................23 C900040018 Average number of EGPRS DL TBF simultaneous establishment ...................................23 C900040019 Number of GPRS UL data TBF establishment success on PACCH .................................................23 C900040020 Number of GPRS UL TBF release due to N3101 overflow .....................................................24 C900040021 Number of GPRS UL TBF release due to N3103 overflow .....................................................25 C900040022 Number of GPRS UL TBF forcing release by control plane.........................................................25 C900040023 Number of GPRS UL TBF release due to instance suspension ...............................................26 C900040024 Number of GPRS UL TBF release due to inner abnormal..............................................................26 C900040025 Number of GPRS UL signaling TBF establishment .......................................................27 C900040026 Number of GPRS UL data TBF establishment .......................................................29 C900040027 Number of EGPRS UL TBF establishment success on PACCH .................................................30 C900040028 Number of EGPRS UL TBF release due to N3101 overflow .....................................................31 C900040029 Number of EGPRS UL TBF release due to N3103 overflow .....................................................31 C900040030 Number of EGPRS UL TBF forcing release by control plane.........................................................32 C900040031 Number of EGPRS UL TBF release due to instance suspension ...............................................32 C900040032 Number of EGPRS UL TBF release due to inner abnormal......................................................33
C900040033 Number of EGPRS UL signaling TBF establishment .......................................................33 C900040034 Number of EGPRS UL data TBF establishment .......................................................33 C900040035 Average number of GPRS UL TBF simultaneous establishment ...................................34 C900040036 Average number of EGPRS UL TBF simultaneous establishment ...................................34 C900040037 Number of GPRS UL signaling TBF release due to N3101 overflow ...........................................35 C900040038 Number of GPRS UL signaling TBF release due to N3103 overflow ...........................................35 C900040039 Number of GPRS UL signaling TBF forcing release by control plane .........................................36 C900040040 Number of GPRS UL signaling TBF release due to instance suspension .....................................36 C900040041 Number of GPRS UL signaling TBF release due to inner abnormal ............................................36 C900040042 Number of EGPRS UL signaling TBF release due to N3101 overflow ...........................................37 C900040043 Number of EGPRS UL signaling TBF release due to N3103 overflow ...........................................37 C900040044 Number of EGPRS UL signaling TBF forcing release by control plane .........................................38 C900040045 Number of EGPRS UL signaling TBF release due to instance suspension .....................................38 C900040046 Number of EGPRS UL signaling TBF release due to inner abnormal ............................................38 C900040047 Number of EGPRS DL LLC frames ..................39 C900040048 Number of discarded EGPRS DL LLC frames due to buffer overflow ............................................39 C900040049 Number of discarded EGPRS DL LLC frames due to life time expiration .......................................40 C900040050 Number of discarded EGPRS DL LLC frames due to other reasons .............................................41 C900040051 Number of DL signaling LLC frames ...............41 C900040052 Number of discarded EGPRS DL signaling LLC frames due to buffer overflow............................42 C900040053 Number of discarded EGPRS DL signaling LLC frames due to life time expiration.......................43
C900040054 Number of discarded EGPRS DL signaling LLC frames due to other reasons .............................43 C900040055 Number of data blocks transmitted according to given Abis bandwidth .........................................44 C900040056 Bytes of effective upper layer protocol data sent on DL PDCH ..................................................44 C900040057 Bytes of effective upper layer protocol data received on UL PDCH ............................................45 C900040058 Bytes of LLC frame on GPRS UL data TBF ...........................................................................46 C900040059 Duration of GPRS UL data TBF ......................46 C900040060 Bytes of LLC frame on GPRS DL data TBF ...........................................................................48 C900040061 Duration of GPRS DL data TBF ......................48 C900040062 Number of effective data blocks received on GPRS UL TBF ........................................................49 C900040063 Number of NACK blocks received on GPRS UL TBF ................................................................50 C900040064 Number of effective data blocks sent on GPRS DL TBF .......................................................51 C900040065 Number of NACK blocks sent on GPRS DL TBF ....................................................................51 C900040066 Bytes of LLC frame on EGPRS UL data TBF ...........................................................................52 C900040067 Duration of EGPRS UL data TBF ....................53 C900040068 Bytes of LLC frame on EGPRS DL data TBF ...........................................................................54 C900040069 Duration of EGPRS DL data TBF ....................55 C900040070 Number of effective data blocks received on EGPRS UL TBF.......................................................56 C900040071 Number of NACK blocks received on EGPRS UL TBF ................................................................57 C900040072 Number of effective data blocks sent on EGPRS DL TBF ......................................................58 C900040073 Number of NACK blocks sent on EGPRS DL TBF ....................................................................58 C900040074 Number of GPRS DL LLC frames ....................59 C900040075 Number of discarded GPRS DL LLC frames due to buffer overflow ............................................60
C900040076 Number of discarded GPRS DL LLC frames due to life time expiration .......................................61 C900040077 Number of discarded GPRS DL LLC frames due to other reasons ..............................................61 C900040078 Number of DL dummy control blocks on PACCH .................................................................62 C900040079 Number of UL dummy control blocks on PACCH .................................................................63 C900040080 Number of DL RLC blocks on PACCH (excluding dummy block) .......................................63 C900040081 Number of DL RLC pending blocks in CS1 on PDTCH .................................................................64 C900040082 Number of DL RLC pending blocks in CS2 on PDTCH .................................................................65 C900040083 Number of DL RLC pending blocks in CS3 on PDTCH .................................................................65 C900040084 Number of DL RLC pending blocks in CS4 on PDTCH .................................................................66 C900040085 Number of DL RLC NACK blocks in CS1 on PDTCH .................................................................67 C900040086 Number of DL RLC NACK blocks in CS2 on PDTCH .................................................................67 C900040087 Number of DL RLC NACK blocks in CS3 on PDTCH .................................................................68 C900040088 Number of DL RLC NACK blocks in CS4 on PDTCH .................................................................69 C900040089 Number of DL RLC new blocks in CS1 on PDTCH .................................................................70 C900040090 Number of DL RLC new blocks in CS2 on PDTCH .................................................................70 C900040091 Number of DL RLC new blocks in CS3 on PDTCH .................................................................71 C900040092 Number of DL RLC new blocks in CS4 on PDTCH .................................................................72 C900040093 Number of UL RLC blocks excluding dummy blocks on PACCH ...................................................72 C900040094 Number of UL RLC pending blocks in CS1 on PDTCH .................................................................73 C900040095 Number of UL RLC pending blocks in CS2 on PDTCH .................................................................74
C900040096 Number of UL RLC pending blocks in CS3 on PDTCH .................................................................74 C900040097 Number of UL RLC pending blocks in CS4 on PDTCH .................................................................75 C900040098 Number of UL RLC NACK blocks in CS1 on PDTCH .................................................................76 C900040099 Number of UL RLC NACK blocks in CS2 on PDTCH .................................................................76 C900040100 Number of UL RLC NACK blocks in CS3 on PDTCH .................................................................77 C900040101 Number of UL RLC NACK blocks in CS4 on PDTCH .................................................................78 C900040102 Number of UL RLC new blocks in CS1 on PDTCH .................................................................79 C900040103 Number of UL RLC new blocks in CS2 on PDTCH .................................................................79 C900040104 Number of UL RLC new blocks in CS3 on PDTCH .................................................................80 C900040105 Number of UL RLC new blocks in CS4 on PDTCH .................................................................81 C900040106 Number of UL data blocks received on PDTCH .................................................................81 C900040107 Number of DL data blocks sent on PDTCH .................................................................82 C900040108 Number of GPRS DL TBF establishment requests ..............................................................82 C900040109 Number of GPRS DL TBF establishment failure due to database allocation failure ...................83 C900040110 Number of GPRS DL TBF resource reallocation requests due to UL TBF establishment ...........................................................................84 C900040111 Number of GPRS DL TBF resource reallocation failure of channel allocation due to UL TBF establishment ................................................85 C900040112 Number of GPRS DL TBF resource reallocation requests due to LLC transmission............86 C900040113 Number of GPRS DL TBF resource reallocation failure of channel allocation due to LLC transmission ........................................................86
C900040114 Number of EGPRS DL TBF establishment requests ..............................................................87 C900040115 Number of EGPRS DL TBF establishment failure due to database allocation failure ...................88 C900040116 Number of EGPRS DL TBF resource reallocation requests due to UL TBF establishment ...........................................................................89 C900040117 Number of EGPRS DL TBF resource reallocation failure of channel allocation due to UL TBF establishment ................................................90 C900040118 Number of EGPRS DL TBF resource reallocation requests due to LLC transmission............91 C900040119 Number of EGPRS DL TBF resource reallocation failure of channel allocation due to LLC transmission ........................................................91 C900040120 Number of GPRS UL TBF establishment requests ..............................................................92 C900040121 Number of GPRS UL TBF establishment failure due to database allocation failure ...................93 C900040122 Number of GPRS UL TBF resource reallocation requests due to DL TBF establishment ......................94 C900040123 Number of GPRS UL TBF resource reallocation failure of channel allocation due to DL TBF establishment .................................................95 C900040124 Number of GPRS UL TBF resource reallocation requests due to LLC transmission............96 C900040125 Number of GPRS UL TBF resource reallocation failure of channel allocation due to LLC transmission .........................................................96 C900040126 Number of GPRS UL TBF resource reallocation requests for resource request .................97 C900040127 Number of GPRS UL TBF resource reallocation failure due to database allocation failure for resource request...............................................98 C900040128 Number of EGPRS UL TBF establishment requests...............................................................99 C900040129 Number of EGPRS UL TBF establishment failure due to database allocation failure ...................99
C900040130 Number of EGPRS UL TBF resource reallocation requests due to DL TBF establishment ..................................................... 100 C900040131 Number of EGPRS UL TBF resource reallocation failure of channel allocation due to DL TBF establishment ............................................... 101 C900040132 Number of EGPRS UL TBF resource reallocation requests due to LLC transmission.......... 102 C900040133 Number of EGPRS UL TBF resource reallocation failure of channel allocation due to LLC transmission ....................................................... 102 C900040134 Number of EGPRS UL TBF resource reallocation requests for resource request ............... 103 C900040135 Number of EGPRS UL TBF resource reallocation failure due to database allocation failure for resource request............................................. 104 C900040136 Average number of available PDCH.............. 105 C900040137 Number of forcing conversation dynamic from PDCH to TCH by BSC .................................... 105 C900040138 Number of PDCH used by TBF in each cell .................................................................... 105 C900040139 Maximum number of used PDCH ................. 106 C900040140 Average number of used PDCH ................... 106 C900040141 Number of GPRS DL TBF establishment requests before T3192 expiration........................... 107 C900040142 Number of GPRS DL TBF establishment using existing DL TBF resource .............................. 108 C900040143 Number of GPRS DL TBF establishment requests on PACCH .............................................. 108 C900040144 Number of GPRS DL TBF establishment requests on CCCH/PCCCH ..................................... 109 C900040145 Number of EGPRS DL TBF establishment requests before T3192 expiration........................... 110 C900040146 Number of EGPRS DL TBF establishment using existing DL TBF resource .............................. 111 C900040147 Number of EGPRS DL TBF establishment requests on PACCH .............................................. 112 C900040148 Number of EGPRS DL TBF establishment requests on CCCH/PCCCH ..................................... 113
C900040149 Number of GPRS DL signaling TBF release due to N3105 overflow ......................................... 114 C900040150 Number of GPRS DL signaling TBF release due to other reasons ............................................ 115 C900040151 Number of GPRS DL signaling TBF forcing release by control plane ....................................... 115 C900040152 Number of GPRS DL signaling TBF release due to instance suspension ................................... 116 C900040153 Number of GPRS DL signaling TBF release due to inner abnormal .......................................... 117 C900040154 Number of EGPRS DL signaling TBF release due to N3105 overflow ......................................... 118 C900040155 Number of EGPRS DL signaling TBF release due to other reasons ............................................ 119 C900040156 Number of EGPRS DL signaling TBF forcing release by control plane ....................................... 120 C900040157 Number of EGPRS DL signaling TBF release due to instance suspension ................................... 120 C900040158 Number of EGPRS DL signaling TBF release due to inner abnormal .......................................... 121 C900040159 Number of GPRS UL TBF establishments in release state ....................................................... 122 C900040160 Number of GPRS UL TBF establishment with existing UL resource ............................................ 123 C900040161 Number of GPRS UL TBF establishment requests on PACCH .............................................. 124 C900040162 Number of EGPRS UL data TBF establishments on PACCH ..................................... 124 C900040163 Number of EGPRS UL TBF establishments in release state ....................................................... 125 C900040164 Number of EGPRS UL TBF establishment with existing UL resource...................................... 126 C900040165 Number of EGPRS UL TBF establishment requests on PACCH .............................................. 127 C900040166 Number of EGPRS UL TBF establishment requests on CCCH/PCCCH ..................................... 127 C900040167 Number of dynamic PDCH preemption for CS service .......................................................... 128 C900040168 Number of GPRS UL TBF establishment requests on CCCH/PCCCH ..................................... 129
C900040169 Number of GPRS DL TBF establishment requests on PACCH .............................................. 129 C900040170 Number of EGPRS DL TBF establishment requests on PACCH .............................................. 130 C900040171 Number of GPRS UL TBF establishment requests on PACCH .............................................. 130 C900040172 Number of DL RLC pending blocks in MCS1 on PDTCH ........................................................... 130 C900040173 Number of DL RLC pending blocks in MCS2 on PDTCH ........................................................... 131 C900040174 Number of DL RLC pending blocks in MCS3 on PDTCH ........................................................... 132 C900040175 Number of DL RLC pending blocks in MCS4 on PDTCH ........................................................... 133 C900040176 Number of DL RLC pending blocks in MCS5 on PDTCH ........................................................... 133 C900040177 Number of DL RLC pending blocks in MCS6 on PDTCH ........................................................... 134 C900040178 Number of DL RLC pending blocks in MCS7 on PDTCH ........................................................... 135 C900040179 Number of DL RLC pending blocks in MCS8 on PDTCH ........................................................... 135 C900040180 Number of DL RLC pending blocks in MCS9 on PDTCH ........................................................... 136 C900040181 Number of DL RLC NACK blocks in MCS1 on PDTCH ............................................................... 137 C900040182 Number of DL RLC NACK blocks in MCS2 on PDTCH ............................................................... 138 C900040183 Number of DL RLC NACK blocks in MCS3 on PDTCH ............................................................... 138 C900040184 Number of DL RLC NACK blocks in MCS4 on PDTCH ............................................................... 139 C900040185 Number of DL RLC NACK blocks in MCS5 on PDTCH ............................................................... 140 C900040186 Number of DL RLC NACK blocks in MCS6 on PDTCH ............................................................... 140 C900040187 Number of DL RLC NACK blocks in MCS7 on PDTCH ............................................................... 141 C900040188 Number of DL RLC NACK blocks in MCS8 on PDTCH ............................................................... 142
C900040189 Number of DL RLC NACK blocks in MCS9 on PDTCH ............................................................... 143 C900040190 Number of DL RLC new blocks in MCS1 on PDTCH ............................................................... 143 C900040191 Number of DL RLC new blocks in MCS2 on PDTCH ............................................................... 144 C900040192 Number of DL RLC new blocks in MCS3 on PDTCH ............................................................... 145 C900040193 Number of DL RLC new blocks in MCS4 on PDTCH ............................................................... 145 C900040194 Number of DL RLC new blocks in MCS5 on PDTCH ............................................................... 146 C900040195 Number of DL RLC new blocks in MCS6 on PDTCH ............................................................... 147 C900040196 Number of DL RLC new blocks in MCS7 on PDTCH ............................................................... 148 C900040197 Number of DL RLC new blocks in MCS8 on PDTCH ............................................................... 148 C900040198 Number of DL RLC new blocks in MCS9 on PDTCH ............................................................... 149 C900040199 Number of UL RLC pending blocks in MCS1 on PDTCH ........................................................... 150 C900040200 Number of UL RLC pending blocks in MCS2 on PDTCH ........................................................... 150 C900040201 Number of UL RLC pending blocks in MCS3 on PDTCH ........................................................... 151 C900040202 Number of UL RLC pending blocks in MCS4 on PDTCH ........................................................... 152 C900040203 Number of UL RLC pending blocks in MCS5 on PDTCH ........................................................... 153 C900040204 Number of UL RLC pending blocks in MCS6 on PDTCH ........................................................... 153 C900040205 Number of UL RLC pending blocks in MCS7 on PDTCH ........................................................... 154 C900040206 Number of UL RLC pending blocks in MCS8 on PDTCH ........................................................... 155 C900040207 Number of UL RLC pending blocks in MCS9 on PDTCH ........................................................... 155 C900040208 Number of UL RLC NACK blocks in MCS1 on PDTCH ............................................................... 156
C900040209 Number of UL RLC NACK blocks in MCS2 on PDTCH ............................................................... 157 C900040210 Number of UL RLC NACK blocks in MCS3 on PDTCH ............................................................... 158 C900040211 Number of UL RLC NACK blocks in MCS4 on PDTCH ............................................................... 158 C900040212 Number of UL RLC NACK blocks in MCS5 on PDTCH ............................................................... 159 C900040213 Number of UL RLC NACK blocks in MCS6 on PDTCH ............................................................... 160 C900040214 Number of UL RLC NACK blocks in MCS7 on PDTCH ............................................................... 160 C900040215 Number of UL RLC NACK blocks in MCS8 on PDTCH ............................................................... 161 C900040216 Number of UL RLC NACK blocks in MCS9 on PDTCH ............................................................... 162 C900040217 Number of UL RLC new blocks in MCS1 on PDTCH ............................................................... 163 C900040218 Number of UL RLC new blocks in MCS2 on PDTCH ............................................................... 163 C900040219 Number of UL RLC new blocks in MCS3 on PDTCH ............................................................... 164 C900040220 Number of UL RLC new blocks in MCS4 on PDTCH ............................................................... 165 C900040221 Number of UL RLC new blocks in MCS5 on PDTCH ............................................................... 165 C900040222 Number of UL RLC new blocks in MCS6 on PDTCH ............................................................... 166 C900040223 Number of UL RLC new blocks in MCS7 on PDTCH ............................................................... 167 C900040224 Number of UL RLC new blocks in MCS8 on PDTCH ............................................................... 168 C900040225 Number of UL RLC new blocks in MCS9 on PDTCH ............................................................... 168 C900040232 Accumulated throughput of UL GPRS TBF ................................................................... 169 C900040233 Accumulated throughput of DL GPRS TBF ................................................................... 170 C900040234 Accumulated throughput of UL EGPRS TBF ................................................................... 170
C900060018 Number of signaling TCH/F assignment failure for assignment .......................................... 201 C900060019 Number of voice TCH/F seizure attempts for assignment......................................................... 202 C900060020 Number of voice TCH/F seizure failure for assignment......................................................... 204 C900060021 Number of voice TCH/F seizure attempts for handover............................................................ 205 C900060022 Number of voice TCH/F seizure failure for handover............................................................ 208 C900060023 Number of TCH/F allocation success for assignment (speech version1) ............................... 209 C900060024 Number of TCH/F allocation failure due to channel activation failure for assignment (speech version1)............................................................ 210 C900060025 Number of TCH/F allocation success for assignment (speech version2) ............................... 211 C900060026 Number of TCH/F allocation success for assignment (speech version3) ............................... 212 C900060027 Number of TCH/F allocation failure due to channel activation failure for assignment (speech version3)............................................................ 214 C900060028 Number of voice TCH/F assignment success .............................................................. 215 C900060029 Number of voice TCH/F assignment failure for assignment .................................................... 216 C900060030 Number of data TCH/F seizure attempts for assignment......................................................... 217 C900060031 Number of data TCH/F seizure failure for assignment......................................................... 219 C900060032 Number of data TCH/F seizure attempts for handover............................................................ 220 C900060033 Number of data TCH/F seizure failure for handover............................................................ 223 C900060034 Number of data TCH/F allocation success for assignment......................................................... 224 C900060035 Number of data TCH/F allocation failure due to channel activation failure for assignment............. 225 C900060036 Number of data TCH/F assignment success .............................................................. 226
C900060037 Number of data TCH/F assignment failure ................................................................ 227 C900060038 Number of signaling TCH/H seizure attempts for assignment .................................................... 228 C900060039 Number of signaling TCH/H seizure failure for assignment .................................................... 229 C900060040 Number of signaling TCH/H seizure attempts for handover ....................................................... 230 C900060041 Number of signaling TCH/H seizure failure for handover ....................................................... 233 C900060042 Number of voice TCH/H seizure attempts for assignment......................................................... 234 C900060043 Number of voice TCH/H seizure failure for assignment......................................................... 236 C900060044 Number of voice TCH/H seizure attempts for handover............................................................ 237 C900060045 Number of voice TCH/H seizure failure for handover............................................................ 240 C900060046 Number of data TCH/H seizure attempts for assignment......................................................... 241 C900060047 Number of data TCH/H seizure failure for assignment......................................................... 243 C900060048 Number of data TCH/H seizure attempts for handover............................................................ 244 C900060049 Number of data TCH/H seizure failure for handover............................................................ 247 C900060050 Number of SAPI3 link establishment requests on SDCCH (MO-SM) ................................ 248 C900060051 Number of SAPI3 link establishment requests on SDCCH (MT-SM)................................. 250 C900060052 Number of SDCCH drops due to handover failure ................................................................ 251 C900060053 Number of SDCCH drops ............................ 253 C900060054 Number of TCH/F drops ............................. 254 C900060055 Number of TCH/H drops............................. 254 C900060056 Average number of idle TCH/F with interference band 1 ............................................. 255 C900060057 Average number of idle TCH/F with interference band 2 ............................................. 255
C900060058 Average number of idle TCH/F with interference band 3 ............................................. 255 C900060059 Average number of idle TCH/F with interference band 4 ............................................. 256 C900060060 Average number of idle TCH/F with interference band 5 ............................................. 256 C900060061 Average number of idle TCH/H with interference band 1 ............................................. 257 C900060062 Average number of idle TCH/H with interference band 2 ............................................. 257 C900060063 Average number of idle TCH/H with interference band 3 ............................................. 258 C900060064 Average number of idle TCH/H with interference band 4 ............................................. 258 C900060065 Average number of idle TCH/H with interference band 5 ............................................. 259 C900060066 Number of samples with UL RQ = 0 ............. 259 C900060067 Number of samples with UL RQ = 1 ............. 259 C900060068 Number of samples with UL RQ = 2 ............. 260 C900060069 Number of samples with UL RQ = 3 ............. 260 C900060070 Number of samples with UL RQ = 4 ............. 260 C900060071 Number of samples with UL RQ = 5 ............. 261 C900060072 Number of samples with UL RQ = 6 ............. 261 C900060073 Number of samples with UL RQ = 7 ............. 261 C900060074 Number of samples with DL RQ = 0............. 262 C900060075 Number of samples with DL RQ = 1............. 262 C900060076 Number of samples with DL RQ = 2............. 262 C900060077 Number of samples with DL RQ = 3............. 263 C900060078 Number of samples with DL RQ = 4............. 263 C900060079 Number of samples with DL RQ = 5............. 263 C900060080 Number of samples with DL RQ = 6............. 264 C900060081 Number of samples with DL RQ = 7............. 264 C900060082 Number of TCH/F handover attempts due to UL strength ........................................................ 264 C900060083 Number of TCH/F handover attempts due to DL strength ........................................................ 265 C900060084 Number of TCH/F handover attempts due to UL quality ........................................................... 266 C900060085 Number of TCH/F handover attempts due to DL quality........................................................... 266
C900060086 Number of TCH/F handover attempts due to UL interference ................................................... 267 C900060087 Number of TCH/F handover attempts due to DL interference ................................................... 268 C900060088 Number of TCH/F handover attempts due to good C/I............................................................. 268 C900060089 Number of TCH/F handover attempts due to bad C/I .............................................................. 269 C900060090 Number of TCH/F handover attempts due to PBGT ................................................................. 270 C900060091 Number of TCH/F handover attempts due to large TA ............................................................. 270 C900060092 Number of TCH/F handover attempts due to other reasons...................................................... 271 C900060093 Number of BSC-controlled inter-cell outgoing handover............................................................ 272 C900060094 Number of BSC-controlled inter-cell outgoing handover success ................................................ 273 C900060095 Number of MSC-controlled outgoing handover............................................................ 273 C900060096 Number of MSC-controlled outgoing handover success ................................................ 274 C900060097 Number of BSC-controlled inter-cell incoming handover .............................................. 275 C900060098 Number of BSC-controlled inter-cell incoming handover success................................... 276 C900060099 Number of MSC-controlled incoming handover............................................................ 276 C900060100 Number of MSC-controlled incoming handover due to forced release ............................. 277 C900060101 Number of MSC-controlled incoming handover due to queue ........................................ 278 C900060102 Number of MSC-controlled incoming handover success ................................................ 279 C900060103 Number of incoming handover from undefined layer (GSM900) to current layer(GSM1800) .................................................. 280 C900060104 Number of incoming handover success from undefined layer(GSM900) to current layer (GSM1800) ......................................................... 281
C900060105 Number of incoming handover from undefined layer (GSM1800) to current layer (GSM900)........................................................... 282 C900060106 Number of incoming handover success from undefined layer(GSM1800) to current layer(GSM900).................................................... 283 C900060107 Number of incoming handover from the same layer GSM900 to GSM1800 ........................... 284 C900060108 Number of incoming handover success from the same layer GSM900 to GSM1800 ..................... 284 C900060109 Number of incoming handover from GSM900 to GSM1800 from the upper layer .......................... 285 C900060110 Number of incoming handover success from GSM900 to GSM1800 in the upper layer ................. 286 C900060111 Number of incoming handover from GSM900 to GSM1800 in the lower layer .............................. 287 C900060112 Number of incoming handover success from GSM900 to GSM1800 in the lower layer .................. 288 C900060113 Number of incoming handover from GSM1800 to GSM900 from the same layer .............. 289 C900060114 Number of incoming handover success from GSM1800 to GSM900 from the same layer .............. 290 C900060115 Number of incoming handover from GSM1800 to GSM900 from the upper layer ............. 291 C900060116 Number of incoming handover success from GSM1800 to GSM900 from the upper layer ............. 292 C900060117 Number of incoming handover from GSM1800 to GSM900 from the lower layer .............. 293 C900060118 Number of incoming handover success from GSM1800 to GSM900 from the lower layer .............. 294 C900060119 Number of Intra-cell handover .................... 294 C900060120 Number of Intra-cell handover success ......... 295 C900060121 Maximum number of busy TCH/H ................ 296 C900060122 Average number of available SDCCH............ 297 C900060123 Average number of unavailable SDCCH ......... 297 C900060124 SDCCH busy time ..................................... 298 C900060125 Average number of available radio channel .............................................................. 299 C900060126 Average number of unavailable radio channel .............................................................. 300
C900060127 TCH/H busy time ...................................... 300 C900060128 Maximum number of busy TCH/F ................ 301 C900060129 TCH/F busy time ....................................... 302 C900060130 Number of healthy TRXs ............................ 303 C900060131 Number of CM service requests of MOC ......... 304 C900060132 Number of SAPI3 link establishment success on SDCCH (MT-SM) ............................................. 305 C900060133 Number of available defined SDCCH ............ 306 C900060134 Number of available defined TCH/F.............. 306 C900060135 Number of signaling TCH/H assignment failure ................................................................ 307 C900060136 Number of MOC access attempts................. 308 C900060137 Number of wireless access due to paging responses........................................................... 309 C900060138 Number of TCH/F allocation failure due to BTS connection failure for assignment (speech version1)............................................................ 310 C900060139 Number of TCH/F allocation failure due to BIU connection failure for assignment (speech version1)............................................................ 311 C900060140 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version1)............................................................ 312 C900060141 Number of TCH/F allocation failure due to channel activation failure for assignment (speech version2)............................................................ 313 C900060142 Number of TCH/F allocation failure due to BTS connection failure for assignment (speech version2)............................................................ 314 C900060143 Number of TCH/F allocation failure due to BIU connection failure for assignment (speech version2)............................................................ 315 C900060144 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version2)............................................................ 316 C900060145 Number of TCH/F allocation failure due to BTS connection failure for assignment (speech version3)............................................................ 317
C900060146 Number of TCH/F allocation failure due to BIU connection failure for assignment (speech version3)............................................................ 318 C900060147 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version3)............................................................ 319 C900060148 Number of data TCH/F allocation failure due to BTS connection failure for assignment) ............... 320 C900060149 Number of data TCH/F allocation failure due to BIU connection failure for assignment................. 320 C900060150 Number of data TCH/F allocation failure due to TCU connection failure for assignment ................ 321 C900060151 Number of voice TCH/H drops due to handover failure .................................................. 322 C900060152 Number of Abis interface paging command messages ........................................................... 324 C900060153 Number of Abis CS paging messages ........... 325 C900060154 Number of Abis PS paging messages ........... 325 C900060155 Number of available defined TCH/H ............. 326 C900060156 Number of TCH/F allocation failure due to channel activation failure for handover(speech version1)............................................................ 327 C900060157 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version1)............................................................ 328 C900060158 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version1)............................................................ 329 C900060159 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version1)............................................................ 330 C900060160 Number of TCH/F allocation failure due to channel activation failure for handover(speech version2)............................................................ 332 C900060161 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version2)............................................................ 333 C900060162 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version2)............................................................ 334
C900060163 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version2)............................................................ 335 C900060164 Number of TCH/F allocation failure due to channel activation failure for handover (speech version3)............................................................ 336 C900060165 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version3)............................................................ 338 C900060166 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version3)............................................................ 339 C900060167 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version3)............................................................ 340 C900060168 Number of Voice TCH/F handover success .............................................................. 341 C900060169 Number of data TCH/F allocation failure due to channel activation failure for handover................ 343 C900060170 Number of data TCH/F allocation failure due to BTS connection failure for handover ................... 344 C900060171 Number of data TCH/F allocation failure due to BIU connection failure for handover.................... 345 C900060172 Number of data TCH/F allocation failure due to TCU connection failure for handover ................... 346 C900060173 Number of data TCH/F handover success .............................................................. 347 C900060174 Number of signaling TCH/H allocation failure for assignment .................................................... 350 C900060175 Number of TCH/H allocation failure due to channel activation failure for assignment (speech version1)............................................................ 351 C900060176 Number of TCH/H allocation failure due to BTS connection failure for assignment (speech version1)............................................................ 352 C900060177 Number of TCH/H allocation failure due to BIU connection failure for assignment (speech version1)............................................................ 353
C900060178 Number of TCH/H allocation failure due to TCU connection failure for assignment (speech version1)............................................................ 354 C900060179 Number of TCH/H allocation failure due to channel activation failure for handover (speech version1)............................................................ 355 C900060180 Number of TCH/H allocation failure due to BTS connection failure for handover (speech version1)............................................................ 356 C900060181 Number of TCH/H allocation failure due to BIU connection failure for handover (speech version1)............................................................ 357 C900060182 Number of TCH/H allocation failure due to TCU connection failure for handover (speech version1)............................................................ 358 C900060183 Number of TCH/H allocation failure due to channel activation failure for assignment (speech version2)............................................................ 360 C900060184 Number of TCH/H allocation failure due to BTS connection failure for assignment (speech version2)............................................................ 361 C900060185 Number of TCH/H allocation failure due to BIU connection failure for assignment (speech version2)............................................................ 362 C900060186 Number of TCH/H allocation failure due to TCU connection failure for assignment (speech version2)............................................................ 363 C900060187 Number of TCH/H allocation failure due to channel activation failure for handover (speech version2)............................................................ 364 C900060188 Number of TCH/H allocation failure due to BTS connection failure for handover (speech version2)............................................................ 365 C900060189 Number of TCH/H allocation failure due to BIU connection failure for handover (speech version2)............................................................ 366 C900060190 Number of TCH/H allocation failure due to TCU connection failure for handover (speech version2)............................................................ 367
C900060191 Number of TCH/H allocation failure due to channel activation failure for assignment (speech version3)............................................................ 369 C900060192 Number of TCH/H allocation failure due to BTS connection failure for assignment (speech version3)............................................................ 370 C900060193 Number of TCH/H allocation failure due to BIU connection failure for assignment (speech version3)............................................................ 371 C900060194 Number of TCH/H allocation failure due to TCU connection failure for assignment (speech version3)............................................................ 372 C900060195 Number of TCH/H allocation failure due to channel activation failure for handover (speech version3)............................................................ 373 C900060196 Number of TCH/H allocation failure due to BTS connection failure for handover (speech version3)............................................................ 374 C900060197 Number of TCH/H allocation failure due to BIU connection failure for handover (speech version3)............................................................ 375 C900060198 Number of TCH/H allocation failure due to TCU connection failure for handover (speech version3)............................................................ 376 C900060199 Number of Voice TCH/H assignment success .............................................................. 378 C900060200 Number of Voice TCH/H assignment failure ................................................................ 379 C900060201 Number of Voice TCH/H handover success .............................................................. 380 C900060202 Number of data TCH/H allocation failure due to channel activation failure for assignment............. 383 C900060203 Number of data TCH/H allocation failure due to BTS connection failure for assignment ................ 384 C900060204 Number of data TCH/H allocation failure due to BIU connection failure for assignment................. 384 C900060205 Number of data TCH/H allocation failure due to TCU connection failure for assignment ................ 385 C900060206 Number of data TCH/H allocation failure due to channel activation failure for handover................ 386
C900060207 Number of data TCH/H allocation failure due to BTS connection failure for handover ................... 387 C900060208 Number of data TCH/H allocation failure due to BIU connection failure for handover.................... 388 C900060209 Number of data TCH/H allocation failure due to TCU connection failure for handover ................... 389 C900060210 Number of data TCH/H assignment success .............................................................. 390 C900060211 Number of data TCH/H assignment failure ................................................................ 392 C900060212 Number of data TCH/H handover success .............................................................. 392 C900060213 Number of BSC-controlled incoming handover due to forced release ............................. 395 C900060214 Number of BSC-controlled incoming handover due to queues ....................................... 396 C900060215 Number of BSC-controlled incoming handover due to forced handover .......................... 397 C900060216 Number of MSC-controlled incoming handover due to forced handover .......................... 398 C900060217 Number of unavailable defined TCH/H.......... 398 C900060218 Number of unavailable defined TCH/F .......... 399 C900060219 Number of signaling TCH/F drops due to handover failure .................................................. 400 C900060220 Number of voice TCH/F drops due to handover failure .................................................. 402 C900060221 Number of data TCH/F drops due to handover failure .................................................. 403 C900060222 Number of signaling TCH/H drops due to handover failure .................................................. 406 C900060223 Number of data TCH/H drops due to handover failure .................................................. 408 C900060224 Number of TCH/H handover attempts due to UL strength ........................................................ 410 C900060225 Number of TCH/H handover attempts due to DL strength ........................................................ 410 C900060226 Number of TCH/H handover attempts due to UL quality ........................................................... 411 C900060227 Number of TCH/H handover attempts due to DL quality........................................................... 412
C900060228 Number of TCH/H handover attempts due to UL interference ................................................... 412 C900060229 Number of TCH/H handover attempts due to DL interference ................................................... 413 C900060230 Number of TCH/H inter-subcell handover attempts due to good C/I ..................................... 414 C900060231 Number of TCH/H inter-subcell handover attempts due to bad C/I ....................................... 414 C900060232 Number of TCH/H handover attempts due to PBGT ................................................................. 415 C900060233 Number of TCH/H handover attempts due to large TA ............................................................. 416 C900060234 Number of TCH/H handover attempts due to other reasons...................................................... 417 C900060235 Number of signaling TCH/H assignment success .............................................................. 417 C900060236 Number of MOC access success .................. 418 C900060237 Number of dual band outgoing handover............................................................ 419 C900060238 Number of dual band outgoing handover success .............................................................. 420 C900060239 Number of dual band incoming handover............................................................ 421 C900060240 Number of dual band incoming handover success .............................................................. 421 C900060241 Number of SDCCH assignment attempts ............................................................ 422 C900060242 Number of SDCCH assignments success .............................................................. 423 C900060243 Number of SDCCH assignment failure .......... 424 C900060244 Number of voice TCH/F drops due to radio link failure .......................................................... 425 C900060245 Number of voice TCH/H drops due to radio link failure .......................................................... 426
C900090004 Number of SDCCH .................................... 430 C900090005 Radio capacity (call loss 1) ......................... 430 C900090006 Radio capacity (call loss 2) ......................... 431 C900090007 Radio capacity (based on TRX).................... 431 C900090008 Number of static PDTCH............................. 431 C900090009 Number of dynamic PDTCH ........................ 431
C901000033 Number of EGPRS DL TBF establishment execution on CCCH/PCCCH ................................... 451 C901000034 Number of EGPRS DL TBF establishment execution failure on CCCH/PCCCH due to polling failed ................................................................. 453 C901000035 Number of EGPRS DL TBF establishment execution success on CCCH/PCCCH due to polling succeeded .......................................................... 455 C901000036 Number of EGPRS DL TBF establishment success on CCCH/PCCCH ...................................... 457 C901000037 Number of EGPRS DL TBF normal release............................................................... 459 C901000045 Time of GPRS DL TBF connection ................ 460 C901000046 Time of EGPRS DL TBF connection............... 461 C901000047 Time of DL signaling TBF connection............ 461 C901000048 Max number of GPRS DL TBF simultaneous establishment ..................................................... 462 C901000050 Max number of EGPRS DL TBF simultaneous establishment ..................................................... 463 C901000052 Number of GPRS DL signaling TBF normal release............................................................... 463 C901000058 Number of EGPRS DL signaling TBF normal release............................................................... 464
C901010012 Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons .......... 473 C901010013 Number of GPRS UL TBF establishment success on CCCH/PCCCH ...................................... 474 C901010014 Number of GPRS UL TBF normal release............................................................... 476 C901010022 Number of EGPRS UL TBF resumption in extend uplink state .............................................. 477 C901010023 Number of EGPRS UL TBF resource reassign in delay uplink state............................................. 477 C901010027 Number of EGPRS establishment failure on PACCH due to time out ......................................... 478 C901010028 Number of EGPRS establishment failure on PACCH due to other reasons ................................. 479 C901010031 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to competition solving failed ................................................................. 480 C901010032 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to not receive resource request .............................................................. 481 C901010033 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons .......... 482 C901010034 Number of EGPRS UL TBF establishment success on CCCH/PCCCH ...................................... 482 C901010035 Number of EGPRS UL TBF normal release............................................................... 484 C901010043 Time of GPRS UL TBF connection................. 485 C901010044 Time of EGPRS UL TBF connection ............... 485 C901010045 Time of UL signaling TBF connection ............ 486 C901010046 Max number of GPRS UL TBF simultaneous establishment ..................................................... 486 C901010048 Max number of EGPRS UL TBF simultaneous establishment ..................................................... 487 C901010050 Number of GPRS UL signaling TBF normal release............................................................... 487 C901010056 Number of EGPRS UL signaling TBF normal release............................................................... 488
C901020001 Number of Kbytes of IP packet sent to BIPB .................................................................. 492 C901020002 Number of packets sent to BIPB.................. 492 C901020003 Number of Kbytes of IP packet received from BIPB........................................................... 493 C901020004 Number of packets received from BIPB ......... 494 C901020005 Number of Kbytes of IP packet sent to GIPB.................................................................. 494 C901020006 Number of packets sent to GIPB ................. 495 C901020007 Number of Kbytes of IP packet received from GIPB .......................................................... 496 C901020008 Number of packets received from GIPB ......... 496 C901020009 Number of Kbytes carried by EGPRS DL LLC frame................................................................. 497 C901020014 Number of Kbytes carried by DL signaling LLC frame........................................................... 498 C901020019 Number of Kbytes carried by UL LLC frame................................................................. 498 C901020020 Number of UL LLC frames .......................... 499 C901020021 Number of Bytes of GPRS DL TBF LLC frame................................................................. 500 C901020022 Number of Bytes of EGPRS DL TBF LLC frame................................................................. 500 C901020023 Number of Bytes of DL signaling TBF LLC frame................................................................. 501 C901020024 Number of Bytes of UL GPRS TBF LLC frame................................................................. 502 C901020025 Number of Bytes of EGPRS UL TBF LLC frame................................................................. 503 C901020026 Number of Bytes of UL signaling TBF LLC frame................................................................. 503 C901020031 Number of GPRS UL data TBF completion ......................................................... 504 C901020034 Number of GPRS DL data TBF completion ......................................................... 505 C901020041 Number of EGPRS UL data TBF completion ......................................................... 506 C901020044 Number of EGPRS DL data TBF completion ......................................................... 507
C901030158 Number of decrement of EGPRS DL coding mode ................................................................. 530 C901030159 Number of increment of EGPRS UL coding mode ................................................................. 531 C901030160 Number of decrement of EGPRS UL coding mode ................................................................. 532
C901040027 Sum of Abis TS used sampling .................... 547 C901040028 Number of Abis TS used sampling ............... 547 C901040029 Sum of PDCH used sampling ...................... 548 C901040030 Number of PDCH used sampling.................. 548 C901040031 Maximum value of Abis TS used to CS ......... 548 C901040032 Minimum value of Abis TS used to CS .......... 549 C901040033 Total value of the regular sampling used to CS ..................................................................... 549 C901040034 Number of sampling of CS.......................... 550 C901040035 Maximum value of Abis TS used to PS.......... 550 C901040036 Minimum value of Abis TS used to PS .......... 550 C901040037 Total value of the regular sampling used to PS ..................................................................... 551 C901040038 Number of sampling of PS .......................... 551 C901040039 MAX CS used number of exclusive ABIS .................................................................. 551 C901040040 MIN CS used number of exclusive ABIS ......... 552 C901040041 MAX PS used number of exclusive ABIS ......... 552 C901040042 MIN PS used number of exclusive ABIS ......... 552 C901040043 Average Number of GPRS User ................... 553 C901040044 Maximum number of GPRS User ................. 553 C901040045 Average Number of EGPRS User.................. 554 C901040046 Maximum number of EDGE User ................. 554 C901040047 Number of assigned uplink radio channels ............................................................ 554 C901040048 Number of assigned downlink radio channels ............................................................ 555 C901040049 Number of requested uplink radio channels ............................................................ 555 C901040050 Number of requested downlink radio channels ............................................................ 556 C901040051 Number of PS channel expand .................... 556 C901040052 Number of PS channel expand perform ......... 556 C901040053 Number of PS channel expand success ......... 557
C901050003 Number of assignment executions for voice channel due to forced release................................ 563 C901050004 Number of handover attempts for voice due to forced release ................................................. 564 C901050005 Number of handover executions for voice channel due to forced release................................ 565 C901050006 Number of assignments for voice channel due to queuing .................................................... 566 C901050007 Number of assignments for execution for voice channel due to queuing ................................ 567 C901050008 Duration of assignment success voice channel due to queuing ........................................ 568 C901050009 Number of assignments success for voice channel due to queuing ........................................ 569 C901050010 Number of assignments for directed retry attempts for voice channel.................................... 570 C901050011 Number of assignments for execution for voice channel due to directed retry ........................ 571 C901050012 Number of general assignments for execution for data ............................................... 572 C901050013 Number of assignments attempts for data due to forced release ........................................... 573 C901050014 Number of assignment executions for data due to forced release ........................................... 574 C901050015 Number of handover attempts for data due to forced release ................................................. 575 C901050016 Number of handover executions for data due to forced release ................................................. 576 C901050017 Number of assignments attempts for data due to queuing .................................................... 577 C901050018 Number of assignments for execution for data due to queuing............................................. 578 C901050019 Total duration of successful assignments for data due to queuing............................................. 579 C901050020 Number of assignments success for data due to queuing .................................................... 580 C901050021 Number of assignments attempts for data due to directed retry ............................................ 581 C901050022 Number of assignment executions for data due to directed retry ............................................ 582
C901050023 Number of assignment for retry attempts FDD cell for voice channel..................................... 583 C901050024 Number of assignment executions for data due to directed retry to FDD cell for voice channel .............................................................. 584 C901050025 Number of assignment for retry attempts FDD cell for data ................................................. 585 C901050026 Number of assignment executions for data due to directed retry to FDD cell for data ................ 586 C901050027 Number of assignment for retry attempts TDD cell for voice channel..................................... 587 C901050028 Number of assignment executions for data due to directed retry to TDD cell for voice channel .............................................................. 588 C901050029 Number of assignment for retry attempts TDD cell for data ................................................. 589 C901050030 Number of assignment executions for data due to directed retry to TDD cell for data ................ 590 C901050031 Assignment unsuccessful due to circuit obstruction ......................................................... 591 C901050032 Assignment unsuccessful due to circuit obstruction unmatched......................................... 592 C901050033 Assignment unsuccessful due to no valid radio resource ..................................................... 593 C901050034 Assignment unsuccessful due to other causes ............................................................... 594 C901050035 Number of assignments attempts due to forced release (emergency service)........................ 595 C901050036 Number of assignment executions channel due to forced release (emergency service) .............. 596 C901050037 Number of assignment attempts due to forced handover (emergency service)..................... 597 C901050038 Number of assignment executions channel due to forced handover (emergency service) ........... 598 C901050039 Number of assignments channel due to queuing (emergency service) ................................ 599 C901050040 Number of assignments for execution channel due to queuing (emergency service)........... 600 C901050041 Number of forced handover target not found (assignment forced handover) ............................... 601
C901050042 Number of send forced handover request to lower PRI user (assignment forced handover).......... 602 C901050043 Number of received failure from lower PRI user request resource for forced handover (assignment forced handover) ............................... 603 C901050044 Number of lower PRI user handover failure (assignment forced handover) ............................... 604 C901050045 Number of time out for wait resource (assignment forced handover) ............................... 605 C901050046 Number of forced release target not found (assignment forced release) .................................. 606 C901050047 Number of time out for wait resource (assignment forced release) .................................. 607 C901050048 Number of get before grab released channel (assignment forced handover) ............................... 608 C901050049 Number of get before grab released channel(assignment forced release) ....................... 609 C901050050 The count of Assignment using FULL IP A-Interface ......................................................... 610 C901050051 The count of Assignment using PCM over IP A-Interface ......................................................... 611 C901050052 The count of Assignment using PCM over TDM A-Interface ................................................. 612 C901050053 The count of Assignment Failure caused by "Requested Codec Type or Codec Configuration not supported" ......................................................... 613 C901050054 The count of Assignment Failure caused by "Requested Codec Type or Codec Configuration unavailable"........................................................ 614 C901050055 The count of Assignment Failure caused by "Requested A-Interface Type not supported" ........... 615 C901050056 The count of Assignment Failure caused by "Requested A-Interface Type unavailable" ............... 616 C901050057 The count of Assignment Failure caused by "Call Identifier already allocated" ........................... 617 C901050058 The count of Assignment Failure caused by "Requested Redundancy Level not supported" ......... 618 C901050059 The count of Assignment Failure caused by "Call Access Control" ............................................ 619
C901050060 Attempt Number of mode modify for assignment......................................................... 620 C901050061 Success Number of mode modify for assignment......................................................... 621 C901050062 Number of assignments for directed retry attempts for voice channel because of radio ............ 621 C901050063 Number of assignments for execution for voice channel due to directed retry because of radio.................................................................. 622 C901050064 Number of assignments for directed retry attempts for data channel because of radio ............. 623 C901050065 Number of assignments for execution for data channel due to directed retry because of radio.................................................................. 624
C901060013 Number of SDCCH handover attempts due to macro-micro switch ......................................... 638 C901060014 Number of SDCCH handover attempts due to MSC request .................................................. 639 C901060015 Number of SDCCH handover attempts due to traffic ............................................................. 640 C901060016 Number of SDCCH handover attempts due to large TA and wastage ....................................... 641 C901060017 Number of SDCCH handover attempts due to small TA and wastage ....................................... 642 C901060018 Number of SDCCH Handover attempt due to a preferable electricity level of 3G adjacent cell .................................................................... 643 C901060019 Number SDCCH handover attempts due to forced transfer .................................................... 643 C901060020 Number of SDCCH handover during assignment due to forced transfer.......................... 644 C901060021 Number of SDCCH handover during handover due to forced transfer ............................ 645 C901060022 Number of SDCCH handover attempts due to increased TA .................................................. 646 C901060023 Number of SDCCH handover attempts due to TA decrease .................................................... 647 C901060024 Number of SDCCH Handover attempt due to other factors ...................................................... 648 C901060035 Number of TCH/F handover attempts due to quick break up of UL ............................................ 649 C901060036 Number of TCH/F handover attempts due to macro-micro switch ............................................. 649 C901060037 Number of TCH/F handover attempts due to MSC request ....................................................... 650 C901060038 Number of TCH/F handover attempts due to traffic................................................................. 651 C901060039 Number of TCH/F handover attempts due to large TA and wastage ........................................... 652 C901060040 Number of TCH/F handover attempts due to small TA and wastage........................................... 653 C901060041 Number of TCH/F handover attempts due to preferable electricity level in 3G adjacent cell ......... 653
C901060042 Number of TCH/F handover attempts due to forced transfer .................................................... 654 C901060043 Number of TCH/F handover during assignment due to forced transfer.......................... 655 C901060044 Number of TCH/F handover attempts during handover due to forced transfer............................. 656 C901060045 Number of TCH/F handover attempts due to TA increase......................................................... 657 C901060046 Number of TCH/F handover attempts due to TA decrease ........................................................ 658 C901060058 Number of TCH/H handover attempts due to quick break up of UL ............................................ 659 C901060059 Number of TCH/H handover attempts due to macro-micro switch ............................................. 660 C901060060 Number of TCH/H handover attempts due to MSC request ....................................................... 660 C901060061 Number of TCH/H handover attempts due to traffic................................................................. 661 C901060062 Number of TCH/H handover attempts due to large TA and wastage ........................................... 662 C901060063 Number of TCH/H handover attempts due to small TA and wastage........................................... 663 C901060064 Number of TCH/H handover attempts due to a preferable electricity level in 3G adjacent cell .................................................................... 664 C901060065 Number of TCH/H handover attempts due to forced transfer .................................................... 665 C901060066 Number of TCH/H handover attempts during assignment due to forced transfer.......................... 665 C901060067 Number of TCH/H handover attempts during handover due to forced transfer............................. 667 C901060068 Number of TCH/H handover attempts during handover due to TA increase ................................. 668 C901060069 Number of TCH/H handover attempts during handover due to TA decrease ................................ 669 C901060070 Number of TCH/H handover attempts due to other reasons...................................................... 669 C901060071 Number of TCH/F handover attempts due to CS channel transfer ............................................. 670
C901060072 Number of TCH/H handover attempts due to CS channel transfer ............................................. 671 C901060073 Number of TCH/H handover attempts due to Fragment reorganization....................................... 672 C901060074 Number of TCH/F handover attempts due to energy conservation............................................. 673 C901060075 Number of TCH/F handover attempts due to energy conservation............................................. 674 C901060076 Number of TCH/F handover attempts due to CS channel is forced release.................................. 675 C901060077 Number of TCH/H handover attempts due to CS channel is forced release.................................. 676 C901060078 Number of TCH/F handover attempts due to FR to HR during cell busy...................................... 677 C901060079 Number of SDCCH handover attempts due to downlink rapid drop ......................................... 678 C901060080 Number of TCH/F handover attempts due to downlink rapid drop ............................................. 678 C901060081 Number of TCH/H handover attempts due to downlink rapid drop ............................................. 678 C901060082 Attempts of handover on TCH/F caused by power adjustment ............................................... 679 C901060083 Attempts of handover on TCH/H caused by power adjustment ............................................... 679 C901060084 Attempts of handover on TCH/F caused by local switch......................................................... 680 C901060085 Attempts of handover on TCH/H caused by local switch......................................................... 680 C901060086 Attempts of handover on TCH/F caused by reducing band resources of IPAbis.......................... 681 C901060087 Attempts of handover on TCH/H because of MASTERPWR_ALM from TRX.................................. 681 C901060088 Attempts of handover on TCH/F because of MASTERPWR_ALM from TRX.................................. 682 C901060089 Number of handover attempts due to directed retry for PBGT......................................... 683 C901060090 Number of SDCCH handover attempts due to DL quality rapid drop ........................................ 684 C901060091 Number of TCH/F handover attempts due to DL quality rapid drop............................................ 684
C901060092 Number of TCH/H handover attempts due to DL quality rapid drop............................................ 685
C901070023 Number of data TCH/F drops due to radio link failure .......................................................... 709 C901070024 Number of data TCH/F drops due to LAPD link failure .......................................................... 710 C901070025 Number of data TCH/F drops due to OMC-R forced release ..................................................... 711 C901070026 Number of data TCH/F drops due to forced release by other calls ........................................... 713 C901070028 Number of data TCH/F drops due to other failure ................................................................ 714 C901070029 Number of signaling TCH/H drops due to loss of contact with RANA ..................................... 715 C901070030 Number of signaling TCH/H drops due to radio link failure .................................................. 716 C901070031 Number of signaling TCH/H drops due to LAPD link failure .................................................. 717 C901070032 Number of signaling TCH/H drops due to OMC-R forced release........................................... 717 C901070033 Number of signaling TCH/H drops due to forced release by other calls.................................. 718 C901070035 Number of signaling TCH/H drops due to other failure........................................................ 719 C901070036 Number of voice TCH/H drops due to loss of contact with RANA ............................................... 720 C901070038 Number of voice TCH/H drops due to LAPD link failure .......................................................... 721 C901070039 Number of voice TCH/H drops due to OMC-R forced release ..................................................... 723 C901070040 Number of voice TCH/H drops due to forced release by other calls ........................................... 724 C901070042 Number of voice TCH/H drops due to other failure ................................................................ 725 C901070043 Number of data TCH/H drops due to loss of contact with RANA ............................................... 726 C901070044 Number of data TCH/H drops due to radio link failure .......................................................... 728 C901070045 Number of data TCH/H drops due to LAPD link failure .......................................................... 729 C901070046 Number of data TCH/H drops due to OMC-R forced release ..................................................... 730
C901070047 Number of data TCH/H drops due to forced release by other calls ........................................... 732 C901070049 Number of data TCH/H drops due to other failure ................................................................ 733 C901070053 Number of SDCCH link failures.................... 734 C901070054 Number of TCH/F link failures ..................... 735 C901070055 Number of TCH/H link failures..................... 737 C901070056 Number of RANA link releases due to other cause on SDCCH ................................................. 738 C901070057 Number of RANA link releases due to other cause on TCH/F ................................................... 739 C901070058 Number of RANA link releases due to other cause on TCH/H .................................................. 739 C901070059 Number of SDCCH short messages drops ................................................................. 740 C901070060 Number of TCH/F short messages drops ................................................................. 741 C901070061 Number of TCH/H short messages drops ................................................................. 741 C901070062 Number of TCH/F drops due to CS channel is forced release by PS ............................................ 742 C901070063 Number of TCH/H drops due to CS channel is forced release by PS ......................................... 742 C901070064 Number of SDCCH drops due to eMLPP forced handover .................................................. 743 C901070065 Number of signaling TCH/F drops due to eMLPP forced handover ........................................ 743 C901070066 Number of voice TCH/F drops due to eMLPP forced handover .................................................. 744 C901070067 Number of data TCH/F drops due to eMLPP forced handover .................................................. 745 C901070068 Number of sigaling TCH/H drops due to eMLPP forced handover ........................................ 746 C901070069 Number of voice TCH/H drops due to eMLPP forced handover .................................................. 746 C901070070 Number of data TCH/H drops due to eMLPP forced handover .................................................. 747 C901070071 Bad quality of UL receiving (On SDCCH) ............................................................. 748
C901070072 Bad quality of DL receiving (On SDCCH) ............................................................. 749 C901070073 Lower electrical level of UL (On SDCCH) ............................................................. 750 C901070074 Lower electrical level of DL (On SDCCH) ............................................................. 751 C901070075 Number of signaling drops due to TA too far (On SDCCH) ....................................................... 752 C901070076 Reasons of the other radios (On SDCCH) ............................................................. 753 C901070077 Bad quality of UL receiving (On TCH/F) ......... 754 C901070078 Bad quality of DL receiving (On TCH/F) ......... 755 C901070079 Lower electrical level of UL (On TCH/F) ......... 756 C901070080 Lower electrical level of DL (On TCH/F) ......... 757 C901070081 Number of signaling drops due to TA too far (On TCH/F) ......................................................... 758 C901070082 Reasons of the other radios (On TCH/F) ......... 759 C901070083 Bad quality of UL receiving (On TCH/H) ......... 761 C901070084 Bad quality of DL receiving (On TCH/H) ......... 762 C901070085 Lower electrical level of UL (On TCH/H) ......... 763 C901070086 Lower electrical level of DL (On TCH/H) ......... 764 C901070087 Number of signaling drops due to TA too far (On TCH/H) ........................................................ 765 C901070088 Reasons of the other radios (On TCH/H) .............................................................. 766 C901070089 The Count of Drop Call caused by "IP Resource Reset" .................................................. 767 C901070090 Number of FR_V1 radio link fail................... 768 C901070091 Number of FR_V2 radio link fail................... 768 C901070092 Number of FR_V3 radio link fail................... 768 C901070093 Number of HR_V1 radio link fail .................. 769 C901070094 Number of HR_V3 radio link fail .................. 769 C901070095 Number of signaling TCH/F drops due to BIPB Active/Standby Changeover........................... 770 C901070096 Number of voice TCH/F drops due to BIPB Active/Standby Changeover .................................. 770 C901070097 Number of data TCH/F drops due to BIPB Active/Standby Changeover .................................. 770 C901070098 Number of signaling TCH/H drops due to BIPB Active/Standby Changeover........................... 771
C901070099 Number of voice TCH/H drops due to BIPB Active/Standby Changeover .................................. 771 C901070100 Number of data TCH/H drops due to BIPB Active/Standby Changeover .................................. 771 C901070101 Number of SDCCH drops due to LAPD Active/Standby Changeover .................................. 772 C901070102 Number of voice TCH/F drops due to LAPD Active/Standby Changeover .................................. 772 C901070103 Number of data TCH/F drops due to LAPD Active/Standby Changeover .................................. 772 C901070104 Number of signaling TCH/F drops due to LAPD Active/Standby Changeover .......................... 773 C901070105 Number of voice TCH/H drops due to LAPD Active/Standby Changeover .................................. 773 C901070106 Number of data TCH/H drops due to LAPD Active/Standby Changeover .................................. 774 C901070107 Number of signaling TCH/H drops due to LAPD Active/Standby Changeover .......................... 774 C901070108 Number of voice TCH/F drops due to handover fail for power adjustment........................ 774 C901070109 Number of voice TCH/H drops due to handover fail for power adjustment........................ 775 C901070110 Number of SDCCH drops due to BIPB Active/Standby Changeover .................................. 775 C901070111 Number of SDCCH drops due to BTS failure ................................................................ 776 C901070112 Number of signaling TCH/F drops due to BTS failure ................................................................ 777 C901070113 Number of voice TCH/F drops due to BTS failure ................................................................ 778 C901070114 Number of data TCH/F drops due to BTS failure ................................................................ 779 C901070115 Number of signaling TCH/H drops due to BTS failure.......................................................... 780 C901070116 Number of voice TCH/H drops due to BTS failure ................................................................ 781 C901070117 Number of data TCH/H drops due to BTS failure ................................................................ 782 C901070118 Call Drop by Releasing Local Switch............. 783
C901090011 Number of BSC-controlled inter-cell incoming handover attempts ................................. 818 C901090013 Number of BSC-controlled incoming handover attempts due to forced release ................ 819 C901090015 Number of BSC-controlled incoming handover attempts due to queue ........................... 820 C901090017 Number of BSC-controlled incoming handover attempts due to forced handover ............. 821 C901090020 BSC-controlled incoming handover time due to queue ............................................................ 822 C901090021 Queue number of BSC-controlled incoming handover............................................................ 824 C901090022 BSC-controlled incoming handover success time due to queue ............................................... 826 C901090023 Number of BSC-controlled incoming handover success due to queue ............................. 827 C901090024 Number of MSC-controlled incoming handover attempts .............................................. 828 C901090025 Number of incoming handover failure due to circuit block ........................................................ 828 C901090026 Number of incoming handover failure due to circuit group mismatch ......................................... 829 C901090027 Number of incoming handover failure due to unavailable radio resource .................................... 830 C901090028 Number of incoming handover failure due to other factors ....................................................... 831 C901090030 Number of MSC-controlled incoming handover attempts due to forced release ................ 832 C901090032 Number of MSC-controlled incoming handover attempts due to queue ........................... 833 C901090034 Number of MSC-controlled incoming handover attempts due to forced handover ............. 834 C901090037 MSC-controlled incoming handover time due to queue ............................................................ 835 C901090038 Queue number of MSC-controlled incoming handover............................................................ 837 C901090039 MSC-controlled incoming handover success time due to queue ............................................... 839 C901090040 Number of MSC-controlled incoming handover success due to queue ............................. 840
C901090041 Number of incoming handover attempts from the same layer and frequency ........................ 841 C901090042 Number of incoming handover success from the same layer and frequency ............................... 842 C901090043 Number of outgoing handover attempts to the same layer and frequency ............................... 843 C901090044 Number of outgoing handover success to the same layer and frequency ............................... 844 C901090045 Number of incoming handover attempts from undefined layer to the same frequency............ 845 C901090046 Number of incoming handover success from undefined layer to the same frequency ................... 846 C901090047 Number of outgoing handover attempts from undefined layer to the same frequency............ 847 C901090048 Number of outgoing handover success from undefined layer to the same frequency ................... 848 C901090049 Number of incoming handover attempts from undefined layer (GSM900) to current layer (GSM1800) ......................................................... 849 C901090052 Number of outgoing handover attempts from current layer (GSM900) to undefined layer (GSM1800) ......................................................... 850 C901090053 Number of outgoing handover from current layer (GSM900) to undefined layer (GSM1800) ......... 851 C901090054 Number of outgoing handover success from current layer (GSM900) to undefined layer (GSM1800) ......................................................... 852 C901090055 Number of incoming handover attempts from undefined layer (GSM1800) to current layer (GSM900)........................................................... 853 C901090058 Number of outgoing handover attempts from undefined layer (GSM1800) to current layer (GSM900)........................................................... 854 C901090059 Number of outgoing handover from undefined layer (GSM1800) to current layer (GSM900)........................................................... 855 C901090060 Number of outgoing handover success from undefined layer (GSM1800) to current layer (GSM900)........................................................... 856
C901090061 Number of incoming handover attempts from upper layer to the same frequency ................. 857 C901090062 Number of incoming handover success from upper layer to the same frequency......................... 858 C901090063 Number of outgoing handover attempts from the same frequency to upper layer ................. 859 C901090064 Number of outgoing handover success from the same frequency to upper layer......................... 860 C901090065 Number of incoming handover attempts from lower layer to the same frequency.................. 861 C901090066 Number of incoming handover success from lower layer to the same frequency ......................... 862 C901090067 Number of outgoing handover attempts from the same frequency to lower layer.................. 863 C901090068 Number of outgoing handover success from the same frequency to lower layer ......................... 864 C901090069 Number of incoming handover attempts from the same layer GSM900 to GSM1800 .............. 865 C901090072 Number of outgoing handover attempts to the same layer GSM900 to GSM1800 ..................... 866 C901090073 Number of outgoing handover to the same layer GSM900 to GSM1800 ................................... 867 C901090074 Number of outgoing handover success to the same layer GSM900 to GSM1800 ..................... 867 C901090075 Number of incoming handover attempts from GSM900 to GSM1800 from the upper layer ............. 868 C901090078 Number of outgoing handover attempts from GSM900 to GSM1800 to the upper layer.......... 869 C901090079 Number of outgoing handover from GSM900 to GSM1800 to the upper layer.............................. 870 C901090080 Number of outgoing handover success from GSM900 to GSM1800 to the upper layer ................. 871 C901090081 Number of incoming handover attempts from GSM900 to GSM1800 from the lower layer .............. 872 C901090084 Number of outgoing handover attempts from GSM900 to GSM1800 from the lower layer .............. 873 C901090085 Number of outgoing handover from GSM900 to GSM1800 in the lower layer .............................. 874 C901090086 Number of outgoing handover success from GSM900 to GSM1800 in the lower layer .................. 875
C901090087 Number of incoming handover attempts from GSM1800 to GSM900 from the same layer .............. 876 C901090090 Number of outgoing handover attempts from GSM1800 to GSM900 from the same layer .............. 877 C901090091 Number of outgoing handover from GSM1800 to GSM900 from the same layer .............. 878 C901090092 Number of outgoing handover success from GSM1800 to GSM900 from the same layer .............. 879 C901090093 Number of incoming handover attempts from GSM1800 to GSM900 from the upper layer ............. 880 C901090096 Number of outgoing handover attempts from GSM1800 to GSM900 to the upper layer.......... 881 C901090097 Number of outgoing handover from GSM1800 to GSM900 to the upper layer ................. 882 C901090098 Number of outgoing handover success from GSM1800 to GSM900 to the upper layer ................. 883 C901090099 Number of incoming handover attempts from GSM1800 to GSM900 from the lower layer .............. 884 C901090102 Number of outgoing handover attempts from GSM1800 to GSM900 to the lower layer .......... 885 C901090103 Number of outgoing handover from GSM1800 to GSM900 to the lower layer.................. 886 C901090104 Number of outgoing handover success from GSM1800 to GSM900 to the lower layer.................. 887 C901090105 Number of intra-cell handover attempts ............................................................ 888 C901090108 Number of intra-cell inner-circle-to-outercircle handover attempts ...................................... 889 C901090109 Number of intra-cell inner-circle-to-outercircle handover success ........................................ 889 C901090110 Number of intra-cell outer-circle-to-innercircle handover attempts ...................................... 890 C901090111 Number of intra-cell outer-circle-to-innercircle handover success ........................................ 891 C901090112 Number of intra-cell inner-circle-to-innercircle handover attempts ...................................... 892 C901090113 Number of intra-cell inner-circle-to-innercircle handover success ........................................ 892 C901090114 Number of intra-cell outer-circle-to-outercircle handover attempts ...................................... 893
C901090115 Number of intra-cell outer-circle-to-outercircle handover success ........................................ 894 C901090116 Number of handover attempts from 2G to 3G..................................................................... 895 C901090117 Number of handover from 2G to 3G............. 895 C901090118 Number of handover success from 2G to 3G..................................................................... 896 C901090119 Number of handover attempts from 3G to 2G..................................................................... 897 C901090120 Number of handover from 3G to 2G............. 898 C901090121 Number of handover success from 3G to 2G..................................................................... 899 C901090122 Number of intra-cell handover attempts from TCH/F......................................................... 899 C901090123 Number of intra-cell TCH/F-to-TCH/F handover............................................................ 900 C901090124 Number of intra-cell TCH/F-to-TCH/F handover success ................................................ 901 C901090125 Number of intra-cell TCH/F-to-TCH/H handover............................................................ 902 C901090126 Number of intra-cell TCH/F-to-TCH/H handover success ................................................ 903 C901090127 Number of intra-cell handover attempts from TCH/H ........................................................ 903 C901090128 Number of intra-cell TCH/H-to-TCH/F handover............................................................ 904 C901090129 Number of intra-cell TCH/H-to-TCH/F handover success ................................................ 905 C901090130 Number of intra-cell TCH/H-to-TCH/H handover............................................................ 906 C901090131 Number of intra-cell TCH/H-to-TCH/H handover success ................................................ 907 C901090132 Number of inter-cell handover attempts from TCH/F......................................................... 908 C901090133 Number of inter-cell TCH/F-to-TCH/F handover............................................................ 909 C901090134 Number of inter-cell TCH/F-to-TCH/F handover success ................................................ 909 C901090135 Number of inter-cell TCH/F-to-TCH/H handover............................................................ 910
C901090136 Number of inter-cell TCH/F-to-TCH/H handover success ................................................ 911 C901090137 Number of inter-cell handover attempts from TCH/H ........................................................ 912 C901090138 Number of inter-cell TCH/H-to-TCH/F handover............................................................ 913 C901090139 Number of inter-cell TCH/H-to-TCH/F handover success ................................................ 914 C901090140 Number of inter-cell TCH/H-to-TCH/H handover............................................................ 915 C901090141 Number of inter-cell TCH/H-to-TCH/H handover success ................................................ 916 C901090142 Total dual-band outgoing handover attempts ............................................................ 917 C901090145 Number of dual band incoming handover attempts ............................................................ 918 C901090148 Number of intra-cell invalid handovers ......... 919 C901090149 Number of BSC-controlled inter-cell incoming handover attempts due to forced release (emergency service) ............................................ 920 C901090150 Number of BSC-controlled inter-cell incoming handover (forced release) (emergency service).............................................................. 921 C901090151 Number of BSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service) ............................................ 922 C901090152 Number of BSC-controlled inter-cell incoming handover (forced handover) (emergency service).............................................................. 923 C901090153 Number of BSC-controlled inter-cell incoming handover attempts due to queue (emergency service).............................................................. 924 C901090154 Number of BSC-controlled inter-cell incoming handover (queue) (emergency service) .................. 925 C901090155 Number of MSC-controlled incoming handover attempts due to forced release (emergency service) ............................................ 926 C901090156 Number of MSC-controlled incoming handover (forced release) (emergency service).............................................................. 927
C901090157 Number of MSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service) ............................................ 928 C901090158 Number of MSC-controlled incoming handover (forced release) (emergency service).............................................................. 929 C901090159 Number of MSC-controlled incoming handover attempts due to queue (emergency service).............................................................. 930 C901090160 Number of MSC-controlled incoming handover (queue) (emergency service) .................. 931 C901090161 Number of forced handover target not found (BSC-controlled inter-cell handover due to forced handover) .......................................................... 932 C901090162 Number of send forced handover request to lower PRI user (BSC-controlled inter-cell handover due to forced handover) ....................................... 933 C901090163 Number of recv failure from lower PRI user request resource for forced handover (BSC-controlled inter-cell handover due to forced handover) .......................................................... 934 C901090164 Number of lower PRI user handover failure (BSC-controlled inter-cell handover due to forced handover) .......................................................... 936 C901090165 Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced handover) ................................................. 937 C901090166 Number of forced release target not found (BSC-controlled inter-cell handover due to forced release) ............................................................. 938 C901090167 Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced release) .................................................... 939 C901090168 Number of HO Target not found (MSC-controlled incoming handover due to forced handover) .......................................................... 940 C901090169 Number of send forced handover request to lower PRI user (MSC-controlled incoming handover due to forced handover) ....................................... 941
C901090170 Number of failure to lower PRI user request resource for forced handover (MSC-controlled incoming handover due to forced handover) ............ 942 C901090171 Number of lower PRI user handover failure (MSC-controlled incoming handover due to forced handover) .......................................................... 942 C901090172 Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced handover) ................................................. 943 C901090173 Number of forced release target not found (MSC-controlled incoming handover due to forced release) ............................................................. 943 C901090174 Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced release) .................................................... 944 C901090175 Number of get before grab released channel (assignment forced handover) ............................... 945 C901090176 Number of get before grab released channel (assignment forced release) .................................. 945 C901090177 Number of handover attempts due to eMLPP forced handover .................................................. 946 C901090178 Number of handover due to eMLPP forced handover............................................................ 946 C901090179 Number of handover success due to eMLPP forced handover .................................................. 947 C901090180 Number of BSC-controlled inter-cell outgoing handover attempts between PLMN ......................... 947 C901090181 Number of BSC-controlled inter-cell outgoing handover between PLMN ...................................... 947 C901090182 Number of BSC-controlled inter-cell outgoing handover success between PLMN ........................... 948 C901090183 Number of MSC-controlled outgoing handover attempts between PLMN ......................... 948 C901090184 Number of MSC-controlled outgoing handover request fail between PLMN due to unknown reason .................................................. 948 C901090185 Number of MSC-controlled outgoing handover request fail between PLMN due to unavailable ground resource ................................ 949
C901090186 Number of MSC-controlled outgoing handover request fail between PLMN due to unavailable radio resource .................................... 950 C901090187 Number of MSC-controlled outgoing handover request fail between PLMN due to other reasons .............................................................. 950 C901090188 Number of MSC-controlled outgoing handover between PLMN ...................................... 951 C901090189 Number of MSC-controlled outgoing handover success between PLMN ........................... 952 C901090190 Number of BSC-controlled inter-cell incoming handover attempt between PLMN ............. 953 C901090191 Number of BSC-controlled inter-cell incoming handover between PLMN ......................... 953 C901090192 Number of BSC-controlled inter-cell incoming handover force-release attempt between PLMN ................................................................. 953 C901090193 Number of BSC-controlled inter-cell incoming handover between PLMN due to force release............................................................... 954 C901090194 Number of BSC-controlled inter-cell incoming handover queue attempt between PLMN ................. 954 C901090195 Number of BSC-controlled inter-cell incoming handover between PLMN due to queue ................... 954 C901090196 Number of BSC-controlled inter-cell incoming handover force-handover attempt between PLMN .................................................... 955 C901090197 Number of BSC-controlled inter-cell incoming handover between PLMN due to force handover............................................................ 955 C901090198 Number of BSC-controlled inter-cell incoming handover success between PLMN.............. 955 C901090199 Number of MSC-controlled incoming handover attempt between PLMN .......................... 956 C901090200 A interface incoming handover fail between PLMN due to circuit block...................................... 957 C901090201 A interface incoming handover fail between PLMN due to circuit unmatch ................................. 958 C901090202 A interface incoming handover fail between PLMN due to unavailable radio resource .................. 958
C901090203 A interface incoming handover fail between PLMN due to other reason..................................... 959 C901090204 Number of MSC-controlled incoming handover between PLMN ...................................... 959 C901090205 Number of MSC-controlled incoming handover force-release attempt between PLMN ................................................................. 959 C901090206 Number of MSC-controlled incoming handover between PLMN due to force release .......... 960 C901090207 Number of MSC-controlled incoming handover queue attempt between PLMN ................. 960 C901090208 Number of MSC-controlled incoming handover between PLMN due to queue ................... 961 C901090209 Number of MSC-controlled incoming handover force-handover attempt between PLMN ................................................................. 962 C901090210 Number of MSC-controlled incoming handover between PLMN due to force handover ......... 962 C901090211 Number of MSC-controlled incoming handover success between PLMN .......................... 963 C901090212 Number of handover due to Fragment reorganization..................................................... 963 C901090213 Number of handover success due to Fragment reorganization....................................... 963 C901090214 Number of handover attempt from AMR FR to AMR HR due to high load .................................. 964 C901090215 Number of handover from AMR FR to AMR HR due to high load ............................................. 965 C901090216 Number of handover success from AMR FR to AMR HR due to high load .................................. 966 C901090217 Number of handover attempt from FR to HR due to high load .................................................. 966 C901090218 Number of handover from FR to HR due to high load ............................................................ 967 C901090219 Number of handover success from FR to HR due to high load .................................................. 968 C901090220 Number of handover attempt from AMR HR to AMR FR due to bad quality ................................ 968 C901090221 Number of handover from AMR HR to AMR FR due to bad quality ........................................... 969
C901090222 Number of handover success from AMR HR to AMR FR due to bad quality ................................ 970 C901090223 Number of handover attempt from HR to FR due to bad quality ............................................... 970 C901090224 Number of handover from HR to FR due to bad quality ......................................................... 971 C901090225 Number of handover success from HR to FR due to bad quality ............................................... 972 C901090226 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM900 ......... 972 C901090227 Number of BSC-controlled inter-cell outgoing handover, from GSM900 to GSM900 ....................... 973 C901090228 Number of BSC-controlled inter-cell outgoing handover success, from GSM900 to GSM900 ........... 974 C901090229 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM1800 ........................................................... 975 C901090230 Number of BSC-controlled inter-cell outgoing handover, from GSM1800 to GSM1800 ................... 976 C901090231 Number of BSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM1800 ........................................................... 977 C901090232 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM1800 ........................................................... 978 C901090233 Number of BSC-controlled inter-cell outgoing handover, from GSM900 to GSM1800 ..................... 979 C901090234 Number of BSC-controlled inter-cell outgoing handover success, from GSM900 to GSM1800 ......... 980 C901090235 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM900 ............................................................. 981 C901090236 Number of BSC-controlled inter-cell outgoing handover, from GSM1800 to GSM900 ..................... 982 C901090237 Number of BSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM900 ......... 983 C901090238 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM900 ............................................................. 984
C901090239 Number of MSC-controlled inter-cell outgoing handover, from GSM900 to GSM900 .......... 985 C901090240 Number of MSC-controlled inter-cell outgoing handover success, from GSM900 to GSM900 ............................................................. 986 C901090241 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM1800 ........................................................... 987 C901090242 Number of MSC-controlled inter-cell outgoing handover, from GSM1800 to GSM1800 ................... 988 C901090243 Number of MSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM1800 ........................................................... 989 C901090244 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM1800 ........................................................... 990 C901090245 Number of MSC-controlled inter-cell outgoing handover, from GSM900 to GSM1800 ..................... 990 C901090246 Number of MSC-controlled inter-cell outgoing handover success, from GSM900 to GSM1800 ........................................................... 991 C901090247 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM900 ............................................................. 992 C901090248 Number of MSC-controlled inter-cell outgoing handover, from GSM1800 to GSM900 ..................... 993 C901090249 Number of MSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM900 ............................................................. 994
C901100005 Number of handover attempts from selected cell to the adjacent cell due to better UL quality.............................................................. 1001 C901100006 Number of handover attempts from selected cell to the adjacent cell due to better DL quality.............................................................. 1002 C901100007 Number of handover success from selected cell to the adjacent cell due to better UL quality.............................................................. 1003 C901100008 Number of handover success from selected cell to the adjacent cell due to better DL quality.............................................................. 1005 C901100009 Number of handover attempts from selected cell to the adjacent cell due to better UL strength. .......................................................... 1006 C901100010 Number of handover attempts from selected cell to the adjacent cell due to better DL strength. .......................................................... 1007 C901100011 Number of handover success from selected cell to the adjacent cell due to better UL strength. .......................................................... 1009 C901100012 Number of handover success from selected cell to the adjacent cell due to better DL strength. .......................................................... 1010 C901100013 Number of handover attempts from selected cell to the adjacent cell due to PBGT .................... 1011 C901100014 Number of handover success from selected cell to the adjacent cell due to PBGT .................... 1013 C901100015 Number of handover attempts from selected cell to the adjacent cell due to other factors. ......... 1014 C901100016 Number of successful handover from selected cell to the adjacent cell due to other factors. ............................................................ 1015 C901100017 Number of pingpong handover (handover to source cell)....................................................... 1017 C901100018 The max of RTD...................................... 1018 C901100019 The sum of RTD ...................................... 1019 C901100020 The number of RTD ................................. 1020
C901100026 Number of handover attempts from selected cell to the adjacent cell due to DL quality rapid drop ................................................................ 1020 C901100027 Number of handover success from selected cell to the adjacent cell due to DL quality rapid drop ................................................................ 1022
C901110022 Number of LMU Establishment access success ............................................................ 1035 C901110023 Number of accesses due to location update ............................................................. 1035 C901110024 Number of Access due to CM SERVICE REQ ................................................................. 1035 C901110026 Number of CM service requests of Emergency Call ................................................. 1036 C901110027 Number of CM service requests of SMS................................................................. 1036 C901110028 Number of CM service requests of Supplement ...................................................... 1037 C901110029 Number of CM service requests of LCS ................................................................. 1037 C901110031 Number of wireless access due to call re-establishments .............................................. 1037 C901110032 Number of wireless accesses due to IMSI detachment ...................................................... 1038 C901110033 Number of wireless accesses due to other causes ............................................................. 1038 C901110034 Number of access due to Notification response .......................................................... 1039 C901110035 Number of access due to Immediate setup ............................................................... 1040 C901110036 Number of access due to Talker indication ......................................................... 1041 C901110037 Number of access due to DATA Indication ......................................................... 1042 C901110038 Number of access due to priority uplink request ............................................................ 1043 C901110039 Number of access of CM service request of VGCS ............................................................... 1044 C901110040 Number of access of CM service request of VBS ................................................................. 1045
C901120003 Total value of UL quality level values in wireless channels .............................................. 1052 C901120004 Number of DL signal quality samples in wireless channels .............................................. 1052 C901120005 Level of worst DL signal quality in wireless channels .......................................................... 1052 C901120006 Total value of DL quality strength values in wireless channels .............................................. 1053 C901120007 Number of received UL signal strength samples in wireless channels............................... 1053 C901120008 Maximum received UL signal strength in wireless channels .............................................. 1054 C901120009 Minimum received UL signal strength in wireless channels .............................................. 1054 C901120010 Total value of UL signal strength in wireless channels .......................................................... 1055 C901120011 Number of received DL signal strength samples in wireless channels............................... 1055 C901120012 Maximum received DL signal strength in wireless channels .............................................. 1055 C901120013 Minimum DL received signal strength in radio channels................................................... 1056 C901120014 Total value of DL signal strength in wireless channels .......................................................... 1056 C901120015 Number of TA samples in wireless channels .......................................................... 1057 C901120016 Maximum TA in wireless channels.............. 1057 C901120017 Total number of TAs in wireless channels .......................................................... 1058 C901120018 Mean number of idle TCH/Fs with interference band 0 ........................................... 1058 C901120024 Mean number of idle TCH/Hs with interference band 0 ........................................... 1058 C901120030 Mean number of idle SDCCHs with interference band 0 ........................................... 1059 C901120031 Mean number of idle SDCCHs with interference band 1 ........................................... 1059 C901120032 Mean number of idle SDCCHs with interference band 2 ........................................... 1060
C901120033 Mean number of idle SDCCHs with interference band 3 ........................................... 1060 C901120034 Mean number of idle SDCCHs with interference band 4 ........................................... 1060 C901120035 Mean number of idle SDCCHs with interference band 5 ........................................... 1061 C901120052 Number of TFO initiations......................... 1061 C901120053 Number of using noise suppression ........... 1061 C901120054 Number of mode changes for establishing TFO ................................................................. 1062 C901120055 Number of mode changes for optimizing TFO ................................................................. 1062 C901120056 Number of active collection changes for establishing TFO ................................................ 1062 C901120057 Number of active collection changes for optimizing TFO .................................................. 1063 C901120058 Number of samples with voice quality is excellent .......................................................... 1063 C901120059 Number of samples with voice quality is good ................................................................ 1063 C901120060 Number of samples with voice quality is medium ........................................................... 1064 C901120061 Number of samples with voice quality is bad.................................................................. 1064 C901120062 Number of samples with voice quality is awfully ............................................................. 1065 C901120063 Number of uplink error frame on FR_V1.............................................................. 1065 C901120064 Total Number of uplink frame on FR_V1.............................................................. 1065 C901120065 Number of uplink error frame on FR_V2.............................................................. 1066 C901120066 Total Number of uplink frame on FR_V2.............................................................. 1066 C901120067 Number of uplink error frame on FR_V3.............................................................. 1066 C901120068 Total Number of uplink frame on FR_V3.............................................................. 1067 C901120069 Number of uplink error frame on HR_V1 ............................................................. 1067
C901120070 Total Number of uplink frame on HR_V1 ............................................................. 1067 C901120071 Number of uplink error frame on HR_V3 ............................................................. 1067 C901120072 Total Number of uplink frame on HR_V3 ............................................................. 1068 C901120073 Number of UL signal quality samples in radio channels on SDCCH ........................................... 1068 C901120074 Level of worst UL signal quality in radio channels on SDCCH ........................................... 1068 C901120075 Total value of UL quality level values in radio channels on SDCCH ........................................... 1069 C901120076 Number of DL signal quality samples in radio channels on SDCCH ........................................... 1069 C901120077 Level of worst DL signal quality in radio channels on SDCCH ........................................... 1070 C901120078 Total value of DL quality strength values in radio channels on SDCCH ................................... 1070 C901120079 Number of received UL signal strength samples in radio channels on SDCCH.................... 1071 C901120080 Maximum received UL signal strength in radio channels on SDCCH ................................... 1071 C901120081 Minimum received UL signal strength in radio channels on SDCCH ................................... 1072 C901120082 Total value of UL signal strength in radio channels on SDCCH ........................................... 1072 C901120083 Number of received DL signal strength samples in radio channels on SDCCH.................... 1073 C901120084 Maximum received DL signal strength in radio channels on SDCCH ................................... 1073 C901120085 Minimum DL received signal strength in radio channels on SDCCH ................................... 1074 C901120086 Total value of DL signal strength in radio channels on SDCCH ........................................... 1074 C901120087 Number of UL signal quality samples in radio channels on TCH................................................ 1075 C901120088 Level of worst UL signal quality in radio channels on TCH................................................ 1075 C901120089 Total value of UL quality level values in radio channels on TCH................................................ 1076
C901120090 Number of DL signal quality samples in radio channels on TCH................................................ 1076 C901120091 Level of worst DL signal quality in radio channels on TCH................................................ 1076 C901120092 Total value of DL quality strength values in radio channels on TCH........................................ 1077 C901120093 Number of received UL signal strength samples in radio channels on TCH ........................ 1077 C901120094 Maximum received UL signal strength in radio channels on TCH........................................ 1078 C901120095 Minimum received UL signal strength in radio channels on TCH........................................ 1078 C901120096 Total value of UL signal strength in radio channels on TCH................................................ 1079 C901120097 Number of received DL signal strength samples in radio channels on TCH ........................ 1079 C901120098 Maximum received DL signal strength in radio channels on TCH........................................ 1080 C901120099 Minimum DL received signal strength in radio channels on TCH........................................ 1080 C901120100 Total value of DL signal strength in radio channels on TCH................................................ 1081 C901120101 Number of samples with UL RQ = 0 on SDCCH............................................................. 1081 C901120102 Number of samples with UL RQ = 1 on SDCCH............................................................. 1082 C901120103 Number of samples with UL RQ = 2 on SDCCH............................................................. 1083 C901120104 Number of samples with UL RQ = 3 on SDCCH............................................................. 1083 C901120105 Number of samples with UL RQ = 4 on SDCCH............................................................. 1084 C901120106 Number of samples with UL RQ = 5 on SDCCH............................................................. 1085 C901120107 Number of samples with UL RQ = 6 on SDCCH............................................................. 1085 C901120108 Number of samples with UL RQ = 7 on SDCCH............................................................. 1086 C901120109 Number of samples with DL RQ = 0 on SDCCH............................................................. 1086
C901120110 Number of samples with DL RQ = 1 on SDCCH............................................................. 1087 C901120111 Number of samples with DL RQ = 2 on SDCCH............................................................. 1088 C901120112 Number of samples with DL RQ = 3 on SDCCH............................................................. 1088 C901120113 Number of samples with DL RQ = 4 on SDCCH............................................................. 1089 C901120114 Number of samples with DL RQ = 5 on SDCCH............................................................. 1090 C901120115 Number of samples with DL RQ = 6 on SDCCH............................................................. 1090 C901120116 Number of samples with DL RQ = 7 on SDCCH............................................................. 1091 C901120117 Number of samples with UL RQ = 0 on TCH ................................................................. 1092 C901120118 Number of samples with UL RQ = 1 on TCH ................................................................. 1092 C901120119 Number of samples with UL RQ = 2 on TCH ................................................................. 1093 C901120120 Number of samples with UL RQ = 3 on TCH ................................................................. 1094 C901120121 Number of samples with UL RQ = 4 on TCH ................................................................. 1094 C901120122 Number of samples with UL RQ = 5 on TCH ................................................................. 1095 C901120123 Number of samples with UL RQ = 6 on TCH ................................................................. 1096 C901120124 Number of samples with UL RQ = 7 on TCH ................................................................. 1096 C901120125 Number of samples with DL RQ = 0 on TCH ................................................................. 1097 C901120126 Number of samples with DL RQ = 1 on TCH ................................................................. 1097 C901120127 Number of samples with DL RQ = 2 on TCH ................................................................. 1098 C901120128 Number of samples with DL RQ = 3 on TCH ................................................................. 1099 C901120129 Number of samples with DL RQ = 4 on TCH ................................................................. 1099
C901120130 Number of samples with DL RQ = 5 on TCH ................................................................. 1100 C901120131 Number of samples with DL RQ = 6 on TCH ................................................................. 1101 C901120132 Number of samples with DL RQ = 7 on TCH ................................................................. 1101
C901130017 Handover attempts due to UL receiving strength of the full rate second sub cell ................ 1119 C901130018 Handover attempts due to DL receiving strength of the full rate second sub cell ................ 1120 C901130019 Handover attempts due to UL quality of the full rate second sub cell ...................................... 1121 C901130020 Handover attempts due to DL quality of the full rate second sub cell ...................................... 1121 C901130021 Handover attempts due to PBGT of the full rate second sub cell ........................................... 1122 C901130022 Handover attempts due to traffic of the full rate second sub cell ........................................... 1123 C901130023 Handover attempts due to UL interference of the full rate second sub cell (on TCH/F)............. 1124 C901130024 Handover attempts due to DL interference of the full rate second sub cell (on TCH/F)............. 1125 C901130025 Handover attempts due to good CI of the full rate second sub cell (on TCH/F)...................... 1126 C901130026 Handover attempts due to bad CI of the full rate second sub cell (on TCH/F) ........................... 1127 C901130027 Handover attempts due to path loss and too large TA of the full rate second sub cell (on TCH/F) ............................................................. 1128 C901130028 Handover attempts due to path loss and too small TA of the full rate second sub cell (on TCH/F) ............................................................. 1129 C901130029 Number of forced transfer handover attempts of the full rate second sub cell (on TCH/F) ............................................................. 1130 C901130030 Handover attempts due to other causes of the full rate second sub cell................................. 1131 C901130031 Handover attempts due to UL receiving strength of the half rate second sub cell ............... 1132 C901130032 Handover attempts due to DL receiving strength of the half rate second sub cell ............... 1133 C901130033 Handover attempts due to UL quality of the half rate second sub cell ..................................... 1134 C901130034 Handover attempts due to DL quality of the half rate second sub cell ..................................... 1135
C901130035 Handover attempts due to PBGT of the half rate second sub cell ........................................... 1136 C901130036 Handover attempts due to traffic of the half rate second sub cell ........................................... 1136 C901130037 Handover attempts due to UL interference of the half rate second sub cell ............................ 1137 C901130038 Handover attempts due to DL interference of the half rate second sub cell ............................ 1138 C901130039 Handover attempts due to C/I of the half rate second sub cell ........................................... 1139 C901130040 Handover attempts due to C/I of the half rate second sub cell ........................................... 1140 C901130041 Handover attempts due to path loss and too large TA of the half rate second sub cell................ 1141 C901130042 Handover attempts due to path loss and too small TA of the half rate second sub cell ............... 1142 C901130043 Number of forced transfer handover attempts of the half rate second sub cell............... 1143 C901130044 Handover attempts due to other causes of the half rate second sub cell................................ 1144 C901130045 Number of attempts of TCH/F seizure of the second sub cell (used for assignment) .................. 1145 C901130046 Number of TCH/F seizure success of the second sub cell (used for assignment) .................. 1146 C901130047 Number of TCH/F seizure failure of the second sub cell (used for assignment) .................. 1146 C901130048 Number of attempts of TCH/F seizure of the second sub cell (used for handover) ..................... 1147 C901130049 Number of TCH/F seizure success of the second sub cell (used for handover) ..................... 1148 C901130050 Number of TCH/F seizure failure of the second sub cell (used for handover) ..................... 1148 C901130051 Number of TCH/H seizure attempts of the second sub cell (used for assignment) .................. 1149 C901130052 Number of TCH/H seizure success of the second sub cell (used for assignment) .................. 1150 C901130053 Number of TCH/H seizure failure of the second sub cell (used for assignment) .................. 1151 C901130054 Number of TCH/H seizure attempts of the second sub cell (used for handover) ..................... 1151
C901130055 Number of TCH/H seizure success of the second sub cell (used for handover) ..................... 1152 C901130056 Number of TCH/H seizure failure of the second sub cell (used for handover) ..................... 1153 C901130057 Number of TCH/F call drops in the second sub cell ............................................................ 1153 C901130058 Number of TCH/H call drops in the second sub cell ............................................................ 1154 C901130059 TCH/F busy time in the second sub cell .................................................................. 1155 C901130060 TCH/H busy time in the second sub cell .................................................................. 1155 C901130061 Number of TCH/F assignment attempts of the second sub cell ............................................ 1156 C901130062 Number of TCH/F assignment success of the second sub cell.................................................. 1156 C901130063 Number of TCH/F handover attempts of the second sub cell.................................................. 1157 C901130064 Number of TCH/F handover success of the second sub cell.................................................. 1158 C901130065 Number of TCH/H assignment attempts of the second sub cell ............................................ 1158 C901130066 Number of TCH/H assignment success of the second sub cell.................................................. 1159 C901130067 Number of TCH/H handover attempts of the second sub cell.................................................. 1160 C901130068 Number of TCH/H handover success of the second sub cell.................................................. 1161 C901130069 TCH/F of the first sub cell seizure success when prefer the second sub cell (used for assignment) ..................................................... 1161 C901130070 TCH/F of the first sub cell seizure success when prefer the second sub cell (used for handover) ........................................................ 1162 C901130071 TCH/H of the first sub cell seizure success when prefer the second sub cell (used for assignment) ..................................................... 1162 C901130072 TCH/H of the first sub cell seizure success when prefer the second sub cell (used for handover) ........................................................ 1163
C901150002 Number of SAPI3 link establishments on SACCH/H (MO-SM) ............................................ 1189 C901150004 Number of SAPI3 link establishments on FACCH/F (MO-SM) ............................................. 1190 C901150005 Number of SAPI3 link establishments on FACCH/H (MO-SM)............................................. 1191 C901150006 Number of SAPI3 link establishment requests on SACCH/F (MT-SM) ............................ 1191 C901150007 Number of SAPI3 link establishment requests on SACCH/H (MT-SM)............................ 1192 C901150009 Number of SAPI3 link establishment requests on FACCH/F (MT-SM) ............................ 1193 C901150010 Number of SAPI3 link establishment requests on FACCH/H (MT-SM) ............................ 1194 C901150011 Number of successful SAPI3 link establishments on SACCH/F (MT-SM) ................... 1194 C901150012 Number of successful SAPI3 link establishments on SACCH/H (MT-SM)................... 1195 C901150014 Number of successful SAPI3 link establishments on FACCH/F (MT-SM).................... 1196 C901150015 Number of successful SAPI3 link establishments on FACCH/H (MT-SM) ................... 1197 C901150016 Number of DTAP messages used as SDCCH UL point-to-point short messages (SMs) ............... 1197 C901150017 Number of DTAP messages used as SDCCH DL point-to-point short messages (SMs) ............... 1199 C901150018 Number of DTAP messages on FACCH/F UL for point-to-point short messages ........................ 1201 C901150019 Number of DTAP messages on FACCH/F DL for point-to-point short messages ........................ 1202 C901150020 Number of DTAP messages on FACCH/H UL for point-to-point short messages ........................ 1202 C901150021 Number of DTAP messages on FACCH/H DL for point-to-point short messages ........................ 1203 C901150022 Number of DTAP messages on SACCH/F DL for point-to-point short messages ........................ 1203 C901150023 Number of DTAP messages on SACCH/F DL for point-to-point short messages ........................ 1205 C901150024 Number of DTAP messages on SACCH/H UL for point-to-point short messages ........................ 1206
C901150025 Number of DTAP messages on SACCH/H DL for point-to-point short messages ........................ 1208
C901160021 Number of packet power control/timing advance messages............................................. 1228 C901160022 Number of packet PSI status message......... 1229 C901160023 Number of packet serving cell data messages ......................................................... 1230 C901160024 Number of packet SI status messages......... 1231 C901160025 Number of packet timeslot reconfigure messages ......................................................... 1232 C901160026 Number of packet paging request message .......................................................... 1233 C901160027 Number of PSI message........................... 1234
C901170016 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to not receive PIA .................................................................. 1249 C901170017 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to UPPB-DSP congestion........................................................ 1250 C901170018 Number of GPRS DL TBF establishment failure on PACCH due to UPPB-DSP congestion ................ 1251 C901170019 Number of GPRS DL TBF establishment success on PCCCH/CCCH .................................... 1251 C901170020 Number of GPRS DL TBF establishment success on PACCH ............................................. 1252 C901170023 Number of GPRS DL TBF resource reallocation failure due to Abis congestion for UL TBF establishment ............................................. 1252 C901170024 Number of GPRS DL TBF resource reallocation failure due to RR congestion for UL TBF establishment ................................................... 1253 C901170025 Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment .................... 1254 C901170026 Number of GPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment ............................................. 1255 C901170027 Number of allocated PDCH for GPRS DL TBF resource reallocation due to UL TBF establishment ................................................... 1256 C901170028 Number of GPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment .................................... 1257 C901170029 Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment......................................... 1258 C901170030 Number of GPRS DL TBF resource reallocation failure due to BIU connection failure for UL TBF establishment......................................... 1259 C901170031 Number of GPRS DL TBF resource reallocation success of channel activate and connection for UL TBF establishment .................... 1260
C901170032 Number of GPRS DL TBF resource reallocation failure due to UL TBF establishment ..................... 1261 C901170033 Number of GPRS DL TBF resource reallocation success due to UL TBF establishment ................... 1261 C901170036 Number of GPRS DL TBF resource reallocation failure due to Abis congestion for LLC transmission ..................................................... 1262 C901170037 Number of GPRS DL TBF resource reallocation failure due to RR congestion for LLC transmission ..................................................... 1263 C901170038 Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission........................... 1264 C901170039 Number of GPRS DL TBF resource reallocation success of channel allocation due to LLC transmission ..................................................... 1265 C901170040 Number of allocated PDCH for GPRS DL TBF resource reallocation due to LLC transmission......... 1266 C901170041 Number of GPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission .......................................... 1267 C901170042 Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission ............................................... 1268 C901170043 Number of GPRS DL TBF resource reallocation failure due to BIU connection failure for LLC transmission ............................................... 1269 C901170044 Number of GPRS DL TBF resource reallocation success of channel activate and connection for LLC transmission........................... 1270 C901170045 Number of GPRS DL TBF resource reallocation failure due to LLC transmission ........... 1270 C901170046 Number of GPRS DL TBF resource reallocation success due to LLC transmission ......... 1271 C901170047 Number of GPRS DL TBF release due to flush LL.................................................................... 1271 C901170048 Number of GPRS DL TBF release due to GPRS suspend requests ...................................... 1272 C901170049 Number of GPRS DL TBF forcing release by CS ................................................................... 1272
C901170050 Number of GPRS DL TBF normal release due to user plane requests........................................ 1273 C901170051 Number of GPRS DL TBF abnormal release due to user plane requests.................................. 1274 C901170052 Number of GPRS DL TBF release due to NSVC unavailability............................................ 1274 C901170053 Number of GPRS DL TBF release due to BVC unavailability .................................................... 1275 C901170054 Number of GPRS DL TBF release due to other reasons.................................................... 1276 C901170055 Number of DL GPRS TBF grab resources ......................................................... 1276 C901170056 Number of grab instance by DL GPRS TBF ................................................................. 1277 C901170057 Number of DL GPRS TBF queuing .............. 1278 C901170058 Number of DL GPRS TBF queuing success ............................................................ 1278 C901170059 Number of DL GPRS TBF release TBF during queuing............................................................ 1279
C901180012 Number of EGPRS DL TBF establishment failure due to channel activate failed .................... 1290 C901180013 Number of EGPRS DL TBF establishment failure due to BTS connection failed...................... 1291 C901180014 Number of EGPRS DL TBF establishment failure due to BIU connection failed ...................... 1292 C901180015 Number of EGPRS DL TBF channel activate establishment success........................................ 1293 C901180016 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to not receive PIA .................................................................. 1294 C901180017 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to UPPB-DSP congestion........................................................ 1295 C901180018 Number of EGPRS DL TBF establishment failure on PACCH due to UPPB-DSP congestion........... 1295 C901180019 Number of EGPRS DL TBF establishment success on PCCCH/CCCH .................................... 1295 C901180020 Number of EGPRS DL TBF establishment success on PACCH ............................................. 1296 C901180023 Number of EGPRS DL TBF resource reallocation failure due to Abis congestion for UL TBF establishment ............................................. 1296 C901180024 Number of EGPRS DL TBF resource reallocation failure due to RR congestion for UL TBF establishment ................................................... 1297 C901180025 Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment .................... 1298 C901180026 Number of EGPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment ............................................. 1299 C901180027 Number of allocated PDCH for EGPRS DL TBF resource reallocation due to UL TBF establishment ................................................... 1300 C901180028 Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment .................................... 1301
C901180029 Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment......................................... 1302 C901180030 Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for UL TBF establishment......................................... 1303 C901180031 Number of EGPRS DL TBF resource reallocation success of channel activate and connection for UL TBF establishment .................... 1304 C901180032 Number of EGPRS DL TBF resource reallocation failure due to UL TBF establishment ............... 1304 C901180033 Number of EGPRS DL TBF resource reallocation success due to UL TBF establishment ............. 1305 C901180036 Number of EGPRS DL TBF resource reallocation failure due to Abis congestion for LLC transmission ..................................................... 1305 C901180037 Number of EGPRS DL TBF resource reallocation failure due to RR congestion for LLC transmission ..................................................... 1306 C901180038 Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission........................... 1307 C901180039 Number of EGPRS DL TBF resource reallocation success of channel allocation due to LLC transmission ..................................................... 1308 C901180040 Number of allocated PDCH for EGPRS DL TBF resource reallocation due to LLC transmission......... 1309 C901180041 Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission .......................................... 1310 C901180042 Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission ............................................... 1311 C901180043 Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for LLC transmission ............................................... 1312 C901180044 Number of EGPRS DL TBF resource reallocation success of channel activate and connection for LLC transmission........................... 1313
C901180045 Number of EGPRS DL TBF resource reallocation failure due to LLC transmission ........... 1314 C901180046 Number of EGPRS DL TBF resource reallocation success due to LLC transmission ......... 1314 C901180047 Number of EGPRS DL TBF release due to flush LL ............................................................ 1314 C901180048 Number of EGPRS DL TBF release due to EGPRS suspend requests .................................... 1315 C901180049 Number of EGPRS DL TBF forcing release by CS ................................................................... 1316 C901180050 Number of EGPRS DL TBF normal release due to user plane requests.................................. 1316 C901180051 Number of EGPRS DL TBF abnormal release due to user plane requests.................................. 1317 C901180052 Number of EGPRS DL TBF release due to NSVC unavailability............................................ 1318 C901180053 Number of EGPRS DL TBF release due to BVC unavailability .............................................. 1318 C901180054 Number of EGPRS DL TBF release due to other reasons.................................................... 1319 C901180055 Number of DL EGPRS TBF grab resources ......................................................... 1319 C901180056 Number of grab instance by DL EGPRS TBF ................................................................. 1320 C901180057 Number of DL EGPRS TBF queuing ............ 1321 C901180058 Number of DL EGPRS TBF queuing success ............................................................ 1321 C901180059 Number of DL EGPRS TBF release TBF during queuing............................................................ 1322
C901190006 Number of GPRS UL TBF establishment requests on PACCH ............................................ 1328 C901190007 Number of cell attempts for UL assignment due to ONE PHASE access................................... 1329 C901190008 Number of cell attempts for UL assignment due to single block packet access......................... 1330 C901190009 Number of cell attempts for UL assignment due to response paging ...................................... 1331 C901190010 Number of cell attempts for UL assignment due to cell updating ........................................... 1332 C901190011 Number of cell attempts for UL assignment due to mobility management............................... 1333 C901190012 Number of cell attempts for UL assignment due to TWO PHASE access .................................. 1333 C901190013 Number of cell attempts for UL assignment due to short access............................................ 1334 C901190015 Number of GPRS UL TBF establishment failure due to Abis congestion.............................. 1335 C901190016 Number of GPRS UL TBF establishment failure due to RR congestion................................ 1337 C901190017 Number of GPRS UL TBF establishment failure due to UPPB-DSP channel congestion.......... 1338 C901190018 Number of GPRS UL TBF establishment channel allocate success ..................................... 1340 C901190019 Number of cell success for GPRS UL assignment due to ONE PHASE access .................. 1341 C901190020 Number of cell success for GPRS UL assignment due to single block packet access......... 1343 C901190021 Number of cell success for GPRS UL assignment due to response paging ..................... 1343 C901190022 Number of cell success for GPRS UL assignment due to cell updating .......................... 1344 C901190023 Number of cell success for GPRS UL assignment due to mobility management .............. 1345 C901190024 Number of cell success for GPRS UL assignment due to TWO PHASE access ................. 1346 C901190025 Number of cell success for GPRS UL assignment due to short access ........................... 1347 C901190026 Number of allocated PDCH for GPRS UL TBF establishment ................................................... 1348
C901190027 Number of GPRS UL TBF establishment failure due to channel activate failed .................... 1350 C901190028 Number of GPRS UL TBF establishment failure due to BTS connection failed...................... 1351 C901190029 Number of GPRS UL TBF establishment failure due to BIU connection failed ...................... 1352 C901190030 Number of GPRS UL TBF channel activate establishment success........................................ 1352 C901190031 Number of GPRS UL TBF establishment failure due to not receive PIA .............................. 1353 C901190032 Number of GPRS UL TBF establisment failure on PCCCH/CCCH due to UPPB-DSP congestion........................................................ 1354 C901190033 Number of GPRS UL TBF establisment failure on PACCH due to UPPB-DSP congestion ................ 1355 C901190034 Number of GPRS UL TBF establishment success on PCCCH/CCCH .................................... 1355 C901190035 Number of GPRS UL TBF establishment success on PACCH ............................................. 1356 C901190038 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for DL TBF establishment ............................................. 1356 C901190039 Number of GPRS UL TBF resource reallocation failure due to RR congestion for DL TBF establishment ................................................... 1357 C901190040 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for DL TBF establishment .................... 1358 C901190041 Number of GPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment ............................................. 1359 C901190042 Number of allocated PDCH for GPRS UL TBF resource reallocation due to DL TBF establishment ................................................... 1360 C901190043 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for DL TBF establishment.................................... 1361 C901190044 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for DL TBF establishment......................................... 1362
C901190045 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for DL TBF establishment......................................... 1363 C901190046 Number of GPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment .................... 1364 C901190047 Number of GPRS UL TBF resourse reallocation failure due to DL TBF establishment ..................... 1365 C901190048 Number of GPRS UL TBF resourse reallocation success due to DL TBF establishment ................... 1365 C901190051 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission ..................................................... 1365 C901190052 Number of GPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission ..................................................... 1366 C901190053 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission........................... 1367 C901190054 Number of GPRS UL TBF resource reallocation success of channel allocation due to LLC transmission ..................................................... 1368 C901190055 Number of allocated PDCH for GPRS UL TBF resource reallocation due to LLC transmission......... 1369 C901190056 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for LLC transmission .......................................... 1370 C901190057 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for LLC transmission ............................................... 1371 C901190058 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for LLC transmission ............................................... 1372 C901190059 Number of GPRS UL TBF resourse reallocation success of channel activate for LLC transmission ..................................................... 1373 C901190060 Number of GPRS UL TBF resourse reallocation failure due to LLC transmission ........... 1373 C901190061 Number of GPRS UL TBF resourse reallocation success due to LLC transmission ......... 1374
C901190062 Number of GPRS UL TBF resource reallocation requests for resource request ............. 1374 C901190064 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for resource request ............................................... 1374 C901190065 Number of GPRS UL TBF resource reallocation failure due to RR congestion for resource request ............................................... 1375 C901190066 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for resource request........................... 1376 C901190067 Number of GPRS UL TBF resource reallocation success due to resource request ......... 1377 C901190068 Number of allocated PDCH for GPRS UL TBF resource reallocation due to resource request......... 1378 C901190069 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for resource request........................................... 1379 C901190070 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for resource request ............................................... 1380 C901190071 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for resource request ............................................... 1381 C901190072 Number of GPRS UL TBF resource reallocation success of channel activate and connection for resource request........................... 1382 C901190073 Number of GPRS UL TBF resourse reallocation failure due to resource request ........... 1383 C901190074 Number of GPRS UL TBF resourse reallocation success due to resource request ......... 1383 C901190075 Number of GPRS UL TBF release due to flush LL.................................................................... 1383 C901190076 Number of GPRS UL TBF release due to GPRS suspend requests ...................................... 1384 C901190077 Number of GPRS UL TBF forcing release by CS ................................................................... 1385 C901190078 Number of GPRS UL TBF normal release due to user plane requests........................................ 1385
C901190079 Number of GPRS UL TBF abnormal release due to user plane requests.................................. 1386 C901190080 Number of GPRS UL TBF release due to NSVC unavailability............................................ 1387 C901190081 Number of GPRS UL TBF release due to BVC unavailability .................................................... 1387 C901190082 Number of GPRS UL TBF release due to other reasons.................................................... 1388 C901190083 Number of UL GPRS TBF grab resources ......................................................... 1389 C901190084 Number of grab instance by UL GPRS TBF ................................................................. 1389 C901190085 Number of UL GPRS TBF queuing .............. 1390 C901190086 Number of UL GPRS TBF queuing success ............................................................ 1391 C901190087 Number of UL GPRS TBF release TBF during queuing............................................................ 1391
C901200012 Number of cell attempts for UL assignment due to TWO PHASE access .................................. 1401 C901200013 Number of cell attempts for UL assignment due to short access............................................ 1402 C901200015 Number of EGPRS UL TBF establishment failure due to Abis congestion.............................. 1403 C901200016 Number of EGPRS UL TBF establishment failure due to RR congestion................................ 1404 C901200017 Number of EGPRS UL TBF establishment failure due to UPPB-DSP channel congestion.......... 1406 C901200018 Number of EGPRS UL TBF establishment channel allocate success ..................................... 1407 C901200019 Number of cell success for EGPRS UL assignment due to ONE PHASE access .................. 1408 C901200020 Number of cell success for EGPRS UL assignment due to single block packet access......... 1410 C901200021 Number of cell success for EGPRS UL assignment due to response paging ..................... 1410 C901200022 Number of cell success for EGPRS UL assignment due to cell updating .......................... 1410 C901200023 Number of cell success for EGPRS UL assignment due to mobility management .............. 1411 C901200024 Number of cell success for EGPRS UL assignment due to TWO PHASE access ................. 1411 C901200025 Number of cell success for EGPRS UL assignment due to short access ........................... 1412 C901200026 Number of allocated PDCH for EGPRS UL TBF establishment ................................................... 1414 C901200027 Number of EGPRS UL TBF establishment failure due to channel activate failed .................... 1414 C901200028 Number of EGPRS UL TBF establishment failure due to BTS connection failed...................... 1415 C901200029 Number of EGPRS UL TBF establishment failure due to BIU connection failed ..................... 1416 C901200030 Number of EGPRS UL TBF channel activate establishment success........................................ 1417 C901200031 Number of EGPRS UL TBF establishment failure due to not receive PIA .............................. 1418
C901200032 Number of EGPRS UL TBF establishment failure on PCCCH/CCCH due to UPPB-DSP congestion........................................................ 1419 C901200033 Number of EGPRS UL TBF establishment failure on PACCH due to UPPB-DSP congestion........... 1420 C901200034 Number of EGPRS UL TBF establishment success on PCCCH/CCCH .................................... 1420 C901200035 Number of EGPRS UL TBF establishment success on PACCH ............................................. 1421 C901200038 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for DL TBF establishment ............................................. 1422 C901200039 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for DL TBF establishment ................................................... 1423 C901200040 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for DL TBF establishment .................... 1424 C901200041 Number of EGPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment ............................................. 1425 C901200042 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to DL TBF establishment ................................................... 1426 C901200043 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment.................................... 1427 C901200044 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for DL TBF establishment......................................... 1428 C901200045 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for DL TBF establishment......................................... 1429 C901200046 Number of EGPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment .................... 1430 C901200047 Number of EGPRS UL TBF resource reallocation failure due to DL TBF establishment ............... 1431 C901200048 Number of EGPRS UL TBF resource reallocation success due to DL TBF establishment ............. 1431
C901200051 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission ..................................................... 1431 C901200052 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission ..................................................... 1432 C901200053 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission........................... 1433 C901200054 Number of EGPRS UL TBF resource reallocation success of channel allocation due to LLC transmission ..................................................... 1434 C901200055 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to LLC transmission ....................................................................... 1435 C901200056 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for LLC transmission .......................................... 1436 C901200057 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for LLC transmission ............................................... 1437 C901200058 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for LLC transmission ............................................... 1438 C901200059 Number of EGPRS UL TBF resource reallocation success of channel activate for LLC transmission ..................................................... 1439 C901200060 Number of EGPRS UL TBF resource reallocation failure due to LLC transmission ........... 1440 C901200061 Number of EGPRS UL TBF resource reallocation success due to LLC transmission ......... 1440 C901200062 Number of EGPRS UL TBF resource reallocation requests for resource request ............. 1441 C901200064 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for resource request ............................................... 1441 C901200065 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for resource request ............................................... 1442
C901200066 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for resource request........................... 1443 C901200067 Number of EGPRS UL TBF resource reallocation success due to database allocation for resource request ............................................... 1444 C901200068 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to resource request......... 1445 C901200069 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for resource request........................................... 1446 C901200070 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for resource request ............................................... 1447 C901200071 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for resource request ............................................... 1448 C901200072 Number of EGPRS UL TBF resource reallocation success of channel activate and connection for resource request........................... 1449 C901200073 Number of EGPRS UL TBF resource reallocation failure due to resource request ........... 1450 C901200074 Number of EGPRS UL TBF resource reallocation success due to resource request ......... 1450 C901200075 Number of EGPRS UL TBF release due to flush LL ............................................................ 1451 C901200076 Number of EGPRS UL TBF release due to GPRS suspend requests ...................................... 1451 C901200077 Number of EGPRS UL TBF forcing release by CS ................................................................... 1452 C901200078 Number of EGPRS UL TBF normal release due to user plane requests.................................. 1453 C901200079 Number of EGPRS UL TBF abnormal release due to user plane requests.................................. 1453 C901200080 Number of EGPRS UL TBF release due to NSVC unavailability............................................ 1454 C901200081 Number of EGPRS UL TBF release due to BVC unavailability .............................................. 1455 C901200082 Number of EGPRS UL TBF release due to other reasons.................................................... 1455
C901200083 Number of UL EGPRS TBF grab resources ......................................................... 1456 C901200084 Number of grab instance by UL EGPRS TBF ................................................................. 1457 C901200085 Number of UL EGPRS TBF queuing ............ 1457 C901200086 Number of UL EGPRS TBF queuing success ............................................................ 1458 C901200087 Number of UL EGPRS TBF release TBF during queuing............................................................ 1459
C901210018 Number of Flush-LL received if UL/DL TBF exist ................................................................ 1475 C901210019 Number of Flush-LL received if DL TBF exist ................................................................ 1476 C901210020 Number of Flush-LL received if UL TBF exist ................................................................ 1477 C901210021 Number of reroute intra NSE .................... 1477 C901210022 Number of reroute inter NSE intra BSS cell .................................................................. 1478 C901210023 Number of reroute inter NSE inter BSS cell .................................................................. 1479 C901210024 LLC transfer bytes................................... 1479 C901210025 LLC transfer frames................................. 1480 C901210026 LLC transfer failed bytes .......................... 1480 C901210027 LLC transfer failed frames ........................ 1480 C901210028 LLC transfer failed num............................ 1481 C901210029 LLC transfer succeeded num..................... 1481 C901210030 LLC transfer via cell reselection................. 1482 C901210031 LLC transfer not via cell reselection ........... 1483 C901210032 LLC transfer fail Num via cell reselection........................................................ 1483 C901210033 LLC transfer fail Num not via cell reselection........................................................ 1484
C901220008 Number of wireless status PDU messages sent by BSC...................................................... 1491 C901220009 Number of wireless status messages sent by BSC due to losing wireless association with MS .................................................................. 1492 C901220010 Number of wireless status messages sent by BSC due to bad link quality ................................. 1493 C901220011 Number of wireless status messages sent by BSC due to cell reselection command ................... 1493 C901220012 Number of FLOW-CONTROL-BVC messages sent by BSC...................................................... 1494 C901220013 Number of FLOW-CONTROL-BVC-ACK messages received by BSC ................................. 1494 C901220014 Number of FLOW-CONTROL-MS messages sent by BSC...................................................... 1495 C901220015 Number of FLOW-CONTROL-MS-ACK messages received by BSC ................................. 1496 C901220016 Number of FLOW-CONTROL-PFC messages sent by BSC...................................................... 1497 C901220017 Number of FLOW-CONTROL-PFC-ACK messages received by BSC ................................. 1498 C901220018 Number of status messages sent by BSC ................................................................. 1499 C901220019 Number of status messages received by BSC ................................................................. 1500 C901220020 Number of status messages sent with BVCI Unknown .......................................................... 1501 C901220021 Number of Status messages sent with cell service congestion ............................................. 1501 C901220022 Number of status messages sent with protocol error.................................................... 1502 C901220023 Number of status messages sent with Processor overload............................................. 1502 C901220024 Number of status messages received with BVCI Unknown .................................................. 1502 C901220025 Number of status messages received with cell service congestion........................................ 1503 C901220026 Number of status messages received with protocol error.................................................... 1503
C901220027 Number of status messages received with processor overload ............................................ 1503 C901220028 Number of DOWNLOAD-BSS-PFC messages sent by BSC...................................................... 1504 C901220029 Number of BVCCREATE-BSS-PFC messages received by BSC ................................................ 1505 C901220030 Number of CREATE-BSS-PFC-ACK messages sent by BSC...................................................... 1505 C901220031 Number of CREATE-BSS-PFC-NACK messages sent by BSC ....................................... 1506 C901220032 Number of MODIFY-BSS-PFC messages sent by BSC............................................................. 1507 C901220033 Number of MODIFY-BSS-PFC-ACK messages received by BSC ................................................ 1508 C901220034 Number of DELETE-BSS-PFC messages received by BSC ................................................ 1509 C901220035 Number of DELETE-BSS-PFC-ACK messages sent by BSC...................................................... 1510 C901220036 Number of DELETE-BSS-PFC-REQ messages received by BSC ................................................ 1511 C901220037 Number of PS-HANDOVER-REQUIRED messages sent by BSC ....................................... 1511 C901220038 Number of PS-HANDOVER-REQUIRED-ACK messages received by BSC ................................. 1512 C901220039 Number of PS-HANDOVER-REQUIRED-NACK messages received by BSC ................................. 1513 C901220040 Number of PS-HANDOVER-REQUEST messages received by BSC ................................. 1514 C901220041 Number of PS-HANDOVER-REQUEST-ACK messages sent by BSC ....................................... 1515 C901220042 Number of PS-HANDOVER-REQUEST-NACK messages sent by BSC ....................................... 1516 C901220043 Number of PS-HANDOVER-COMPLETE messages sent by BSC ....................................... 1517 C901220044 Number of PS-HANDOVER-CANCEL messages sent by BSC ....................................... 1518 C901220045 Number of PS-HANDOVER-REQUEST messages with Service UTRAN CCO received by BSC ................................................................. 1519
C901220046 Number of CREATE-BSS-PFC messages with Service UTRAN CCO received by BSC ................... 1520
C901230022 Number of SDCCH call drops .................... 1539 C901230023 Number of SDCCH activation attempts (including handover) .......................................... 1541 C901230024 Number of SDCCH activation success (including handover) .......................................... 1541 C901230025 Number of SDCCH assignment attempts .......................................................... 1542 C901230026 Number of SDCCH assignment success ............................................................ 1543 C901230027 Number of samples with UL RQ = 0 ........... 1543 C901230028 Number of samples with UL RQ = 1 ........... 1544 C901230029 Number of samples with UL RQ = 2 ........... 1545 C901230030 Number of samples with UL RQ = 3 ........... 1545 C901230031 Number of samples with UL RQ = 4 ........... 1546 C901230032 Number of samples with UL RQ = 5 ........... 1546 C901230033 Number of samples with UL RQ = 6 ........... 1547 C901230034 Number of samples with UL RQ = 7 ........... 1547 C901230035 Number of samples with DL RQ = 0........... 1548 C901230036 Number of samples with DL RQ = 1........... 1548 C901230037 Number of samples with DL RQ = 2........... 1549 C901230038 Number of samples with DL RQ = 3........... 1550 C901230039 Number of samples with DL RQ = 4........... 1550 C901230040 Number of samples with DL RQ = 5........... 1551 C901230041 Number of samples with DL RQ = 6........... 1551 C901230042 Number of samples with DL RQ = 7........... 1552 C901230043 Mean number of idle TCH/Fs with interference band 0 ........................................... 1552 C901230044 Mean number of idle TCH/Fs with interference band 1 ........................................... 1553 C901230045 Mean number of idle TCH/Fs with interference band 2 ........................................... 1553 C901230046 Mean number of idle TCH/Fs with interference band 3 ........................................... 1554 C901230047 Mean number of idle TCH/Fs with interference band 4 ........................................... 1554 C901230048 Mean number of idle TCH/Fs with interference band 5 ........................................... 1554 C901230049 Mean number of idle TCH/Hs with interference band 0 ........................................... 1555
C901230050 Mean number of idle TCH/Hs with interference band 1 ........................................... 1555 C901230051 Mean number of idle TCH/Hs with interference band 2 ........................................... 1555 C901230052 Mean number of idle TCH/Hs with interference band 3 ........................................... 1556 C901230053 Mean number of idle TCH/Hs with interference band 4 ........................................... 1556 C901230054 Mean number of idle TCH/Hs with interference band 5 ........................................... 1557 C901230055 Mean number of idle SDCCHs with interference band 0 ........................................... 1557 C901230056 Mean number of idle SDCCHs with interference band 1 ........................................... 1557 C901230057 Mean number of idle SDCCHs with interference band 2 ........................................... 1558 C901230058 Mean number of idle SDCCHs with interference band 3 ........................................... 1558 C901230059 Mean number of idle SDCCHs with interference band 4 ........................................... 1558 C901230060 Mean number of idle SDCCHs with interference band 5 ........................................... 1559 C901230061 Number of TRX poweroff .......................... 1559 C901230062 Duration of TRX poweroff ......................... 1559 C901230063 Number of uplink error frame on FR_V1.............................................................. 1560 C901230064 Total Number of uplink frame on FR_V1.............................................................. 1560 C901230065 Number of uplink error frame on FR_V2.............................................................. 1560 C901230066 Total Number of uplink frame on FR_V2.............................................................. 1561 C901230067 Number of uplink error frame on FR_V3.............................................................. 1561 C901230068 Total Number of uplink frame on FR_V3.............................................................. 1561 C901230069 Number of uplink error frame on HR_V1 ............................................................. 1562 C901230070 Total Number of uplink frame on HR_V1 ............................................................. 1562
C901230071 Number of uplink error frame on HR_V3 ............................................................. 1562 C901230072 Total Number of uplink frame on HR_V3 ............................................................. 1563
C901240024 Maximum interference value..................... 1581 C901240025 Minimum interference value ..................... 1581 C901240026 Interference value................................... 1582 C901240027 Number of regular scanning and sampling of interference value.............................................. 1583 C901240028 Number of call drop................................. 1583 C901240029 Maximum value of path balance ................ 1584 C901240030 Minimum value of path balance................. 1584 C901240031 Value of path balance .............................. 1585 C901240032 Number of regular scanning and sampling of path balance ..................................................... 1586 C901240033 Value of UL loss ...................................... 1586 C901240034 Number of regular scanning and sampling of UL loss ............................................................. 1587 C901240035 Total value of DL loss............................... 1587 C901240036 Number of regular scanning and sampling of DL loss............................................................. 1588 C901240037 Number of drops due to the bad quality of UL receive ........................................................ 1589 C901240038 Number of drops due to the bad quality of DL receive ........................................................ 1590 C901240039 Number of drops due to the low electric level of UL ............................................................... 1592 C901240040 Number of drops due to the low electric level of DL ............................................................... 1594 C901240041 Number of drops due to the TA too far......... 1596 C901240042 Number of drops due to the other radio reasons ............................................................ 1598 C901240043 The valid time of the used voice channel ............................................................ 1600 C901240044 Number of activated voice channel ............ 1601
C901250011 Number of SDCCH allocation success for handover.......................................................... 1610 C901250012 Number of SDCCH allocation failure for handover.......................................................... 1611 C901250016 Number of SDCCH handover failure ........... 1612 C901250017 Number of SDCCH handover success ......... 1614 C901250018 Number of SDCCH handover failure with Reconnection .................................................... 1616 C901250019 Number of SDCCH handover failure without Reconnection .................................................... 1616 C901250020 Number of SDCCH assignment attempts (MOC).............................................................. 1617 C901250021 Number of successful SDCCH assignments (MOC).............................................................. 1618 C901250022 Number of unsuccessful SDCCH assignments (MOC).............................................................. 1619 C901250023 Number of SDCCH assignment attempts (MTC) .............................................................. 1620 C901250024 Number of successful SDCCH assignments (MTC) .............................................................. 1621 C901250025 Number of unsuccessful SDCCH assignments (MTC) .............................................................. 1622 C901250026 Number of SDCCH assignment attempts (call re-establishment) ....................................... 1623 C901250027 Number of successful SDCCH assignments (call re-establishment) ....................................... 1624 C901250028 Number of unsuccessful SDCCH assignments (call re-establishment) ....................................... 1625 C901250029 Number of SDCCH assignment attempts (emergency call) ............................................... 1626 C901250030 Number of successful SDCCH assignments (emergency call) ............................................... 1627 C901250031 Number of unsuccessful SDCCH assignments (emergency call) ............................................... 1628 C901250032 Number of SDCCH assignment attempts (LOC)............................................................... 1629 C901250033 Number of successful SDCCH assignments (LOC)............................................................... 1630 C901250034 Number of unsuccessful SDCCH assignments (LOC)............................................................... 1631
C901250035 Number of SDCCH assignment attempts (other cause) .................................................... 1632 C901250036 Number of successful SDCCH assignments (other cause) .................................................... 1633 C901250037 Number of unsuccessful SDCCH assignments (other cause) .................................................... 1634 C901250038 Count of USSD attempts to connect........... 1635 C901250039 Average dialoge time of USSD services ........................................................... 1636 C901250040 Dialog counts of USSD services................. 1636
C901260033 Number of TCH/F allocation success by BSC for handover (speech version 1) .......................... 1670 C901260038 Number of TCH/F allocation attempts for assignment (speech version 2) ............................ 1672 C901260044 Number of TCH/F allocation attempts by BSC for handover (speech version 2).................... 1674 C901260045 Number of TCH/F allocation success by BSC for handover (speech version 2) .......................... 1676 C901260050 Number of TCH/F allocation attempts by BSC for assignment (speech version 3)................. 1679 C901260056 Number of TCH/F allocation attempts by BSC for handover (speech version 3).................... 1680 C901260057 Number of TCH/F allocation success by BSC for handover (speech version 3) .......................... 1683 C901260062 Number of voice TCH/F assignment attempts by BSC............................................................. 1685 C901260065 Number of voice TCH/F handover attempts .......................................................... 1686 C901260067 Number of Voice TCH/F handover failure .............................................................. 1689 C901260068 Number of Voice TCH/F handover failure messages do not received by BSC........................ 1691 C901260070 Number of data TCH/F seizure success for assignment....................................................... 1692 C901260073 Number of data TCH/F seizure success for handover.......................................................... 1693 C901260075 Number of data TCH/F allocation attempts for assignment .................................................. 1696 C901260081 Number of data TCH/F allocation attempts by BSC for handover .......................................... 1697 C901260082 Number of data TCH/F allocation success for handover.......................................................... 1700 C901260087 Number of data TCH/F assignment attempts .......................................................... 1702 C901260090 Number of data TCH/F handover attempts .......................................................... 1703 C901260092 Number of data TCH/F handover failure .............................................................. 1706 C901260093 Number of data TCH/F handover failure messages do not received by BSC........................ 1708
C901260094 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 1)......................................................... 1709 C901260095 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 1) ............................................ 1710 C901260096 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 1)......................................................... 1711 C901260097 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 1) ............................................ 1712 C901260098 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 2)......................................................... 1713 C901260099 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 2) ............................................ 1714 C901260100 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 2)......................................................... 1715 C901260101 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 2) ............................................ 1717 C901260102 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 3)......................................................... 1718 C901260103 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 3) ............................................ 1719 C901260104 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 3)......................................................... 1720 C901260105 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 3) ............................................ 1722 C901260106 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 1) ............................................. 1723
C901260107 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 1)......................................................... 1724 C901260108 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 1)......................................................... 1725 C901260109 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 1)......................................................... 1726 C901260110 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 1)......................................................... 1727 C901260111 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 1)......................................................... 1728 C901260112 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 2) ............................................. 1729 C901260113 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 2)......................................................... 1730 C901260114 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 2)......................................................... 1731 C901260115 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 2)......................................................... 1732 C901260116 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 2)......................................................... 1733 C901260117 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 2)......................................................... 1734 C901260118 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 3) ............................................. 1735 C901260119 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 3)......................................................... 1736
C901260120 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 3)......................................................... 1737 C901260121 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 3)......................................................... 1738 C901260122 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 3)......................................................... 1739 C901260123 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 3)......................................................... 1740 C901260124 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (data) .............................................................. 1741 C901260125 Number of TCH/F allocation failure due to request UDP port failure for assignment (data) .............................................................. 1742 C901260126 Number of TCH/F allocation failure due to AIPB connection failure for assignment (data) .............................................................. 1742 C901260127 Number of TCH/F allocation failure due to request AIPB resource failure for handover (data) .............................................................. 1743 C901260128 Number of TCH/F allocation failure due to request UDP port failure for handover (data) ......... 1744 C901260129 Number of TCH/F allocation failure due to AIPB connection failure for handover (data) .......... 1745 C901260130 Number of assign TCH/F release by forced handover to forced handover source .................... 1746 C901260131 Number of assign TCH/F release by forced handover to queuing user ................................... 1746 C901260132 Number of restore TCH/F release by forced handover to DBS ............................................... 1747 C901260133 Number of assign TCHF release by forced release to forced release source .......................... 1747 C901260134 Number of assign TCH/F release by forced release to queuing user ...................................... 1748 C901260135 Number of restore TCH/F release by forced release to DBS .................................................. 1748
C901260136 Number of signaling TCH/F seizure failure for assignment (cause:Abis)................................ 1749 C901260137 Number of signaling TCH/F seizure failure for handover (cause:Abis)................................... 1750 C901260138 Number of voice TCH/F seizure failure for assignment (cause:Abis) .................................... 1750 C901260139 Number of voice TCH/F seizure failure for handover (cause:Abis ) ...................................... 1751 C901260140 Number of data TCH/F seizure failure for assignment (cause:Abis) .................................... 1751 C901260141 Number of data TCH/F seizure failure for handover (cause:Abis) ....................................... 1752 C901260142 Number of signaling TCH/F seizure failure for assignment (cause:radio resource).................. 1752 C901260143 Number of signaling TCH/F seizure failure for handover (cause:radio resource)..................... 1753 C901260144 Number of voice TCH/F seizure failure for assignment (cause:radio resource) ...................... 1753 C901260145 Number of voice TCH/F seizure failure for handover (cause:radio resource) ......................... 1754 C901260146 Number of data TCH/F seizure failure for assignment (cause:radio resource) ...................... 1754 C901260147 Number of data TCH/F seizure failure for handover (cause:radio resource) ......................... 1755 C901260148 Number of FR_V1 assignment attempts .......................................................... 1755 C901260149 Number of FR_V1 assignment success......... 1756 C901260150 Number of FR_V2 assignment attempts .......................................................... 1756 C901260151 Number of FR_V2 assignment success......... 1756 C901260152 Number of FR_V3 assignment attempts .......................................................... 1757 C901260153 Number of FR_V3 assignment success......... 1757 C901260154 Number of FR_V1 handover...................... 1758 C901260155 Number of FR_V1 handover success .......... 1758 C901260156 Number of FR_V2 handover...................... 1759 C901260157 Number of FR_V2 handover success .......... 1759 C901260158 Number of FR_V3 handover...................... 1760 C901260159 Number of FR_V3 handover success .......... 1760
C901260185 Resourse releasing of ordinary users due to being grabbed (TCH/F) ....................................... 1761 C901260186 Handover of ordinary users due to be grabbed (TCH/F) ............................................... 1762 C901260187 Number of Channel Request of priority users (TCH/F)............................................................ 1763 C901260188 Number of Successful Channel seize of priority users (TCH/F) ........................................ 1765 C901260189 Number of Successful grabbing channel of priority users (TCH/F) ........................................ 1766
C901270026 Number of TCH/H allocation attempts for assignment by BSC (speech version 1) ................. 1800 C901270027 Number of TCH/H allocation success for assignment (speech version1) ............................. 1801 C901270032 Number of TCH/H allocation attempts by BSC during handover (speech version 1)............... 1803 C901270033 Number of TCH/H allocation success during handover (speech version 1) ............................... 1805 C901270038 Number of TCH/H allocation attempts by BSC for assignment (speech version 2)................. 1807 C901270039 Number of TCH/H allocation success by BSC for assignment (speech version 2) ....................... 1809 C901270044 Number of TCH/H allocation attempts for handover by BSC (speech version 2) .................... 1810 C901270045 Number of TCH/H allocation success for handover (speech version 2) ............................... 1813 C901270050 Number of TCH/H allocation attempts for assignment (speech version 3) ............................ 1815 C901270051 Number of TCH/H allocation success for assignment (speech version 3) ............................ 1817 C901270056 Number of TCH/H allocation attempts by BSC for handover (speech version 3).................... 1818 C901270057 Number of TCH/H allocation success for handover (speech version 3) ............................... 1821 C901270062 Number of Voice TCH/H assignment attempts by BSC ............................................... 1823 C901270065 Number of Voice TCH/H handover attempts .......................................................... 1825 C901270067 Number of Voice TCH/H handover failure .............................................................. 1827 C901270068 Number of Voice TCH/H handover failure messages do not received by BSC........................ 1829 C901270070 Number of data TCH/H seizure success for assignment....................................................... 1830 C901270073 Number of data TCH/H seizure success for handover.......................................................... 1831 C901270075 Number of data TCH/H allocation attempts for assignment by BSC ....................................... 1834 C901270076 Number of data TCH/H allocation success for assignment....................................................... 1835
C901270081 Number of data TCH/H allocation attempts by BSC............................................................. 1837 C901270082 Number of data TCH/H allocation success for handover.......................................................... 1839 C901270087 Number of data TCH/H assignment attempts by BSC............................................................. 1842 C901270090 Number of data TCH/H handover attempts .......................................................... 1843 C901270092 Number of data TCH/H handover failure .............................................................. 1846 C901270093 Number of data TCH/H handover failure do not received by BSC........................................... 1847 C901270094 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 1)......................................................... 1849 C901270095 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 1) ............................................ 1850 C901270096 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 1)......................................................... 1851 C901270097 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 1) ............................................ 1852 C901270098 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 2)......................................................... 1854 C901270099 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 2) ............................................ 1855 C901270100 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 2)......................................................... 1856 C901270101 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 2) ............................................ 1857 C901270102 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 3)......................................................... 1859
C901270103 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 3) ............................................ 1860 C901270104 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 3)......................................................... 1861 C901270105 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 3) ............................................ 1862 C901270106 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 1) ............................................. 1863 C901270107 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 1)......................................................... 1864 C901270108 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 1)......................................................... 1865 C901270109 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 1)......................................................... 1866 C901270110 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 1)......................................................... 1867 C901270111 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 1)......................................................... 1868 C901270112 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 2) ............................................. 1869 C901270113 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 2)......................................................... 1870 C901270114 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 2)......................................................... 1871 C901270115 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 2)......................................................... 1872
C901270116 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 2)......................................................... 1873 C901270117 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 2)......................................................... 1874 C901270118 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 3) ............................................. 1875 C901270119 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 3)......................................................... 1876 C901270120 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 3)......................................................... 1877 C901270121 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 3)......................................................... 1878 C901270122 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 3)......................................................... 1879 C901270123 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 3)......................................................... 1880 C901270124 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (data) .............................................................. 1881 C901270125 Number of TCH/H allocation failure due to request UDP port failure for assignment (data) .............................................................. 1882 C901270126 Number of TCH/H allocation failure due to AIPB connection failure for assignment (data) .............................................................. 1882 C901270127 Number of TCH/H allocation failure due to request AIPB resource failure for handover (data) .............................................................. 1883 C901270128 Number of TCH/H allocation failure due to request UDP port failure for handover (data) ......... 1884 C901270129 Number of TCH/H allocation failure due to AIPB connection failure for handover (data) .......... 1885
C901270130 Number of assign TCH/H release by forced handover to forced handover source .................... 1886 C901270131 Number of assign TCH/H release by forced handover to queuing user ................................... 1886 C901270132 Number of restore TCH/H release by forced handover to DBS ............................................... 1887 C901270133 Number of assign TCH/H release by forced release to forced release source .......................... 1887 C901270134 Number of assign TCH/H release by forced release to queuing user ...................................... 1888 C901270135 Number of restore TCH/H release by forced release to DBS .................................................. 1888 C901270136 Number of signaling TCH/H seize failure for assign due to Abis lack ....................................... 1889 C901270137 Number of signaling TCH/H seize failure for handover due to Abis lack................................... 1889 C901270138 Number of voice TCH/H seizure failure for assignment (cause:Abis) .................................... 1890 C901270139 Number of voice TCH/H seizure failure for handover (cause:Abis ) ...................................... 1890 C901270140 Number of data TCH/H seizure failure for assignment (cause:Abis) .................................... 1891 C901270141 Number of data TCH/H seizure failure for handover (cause:Abis) ....................................... 1891 C901270142 Number of signaling TCH/H seize failure for assign due to radio resource lack ......................... 1892 C901270143 Number of signaling TCH/H seize failure for handover due to radio resource lack..................... 1892 C901270144 Number of voice TCH/H seizure failure for assignment (cause:radio resource) ...................... 1893 C901270145 Number of voice TCH/H seizure failure for handover (cause:radio resource) ......................... 1893 C901270146 Number of data TCH/H seizure failure for assignment (cause:radio resource) ...................... 1894 C901270147 Number of data TCH/H seizure failure for handover (cause:radio resource) ......................... 1894 C901270148 Number of HR_V1 assignment attempts .......................................................... 1895 C901270149 Number of HR_V1 assignment success ............................................................ 1895
C901270150 Number of HR_V3 assignment attempts .......................................................... 1895 C901270151 Number of HR_V3 assignment success ............................................................ 1896 C901270152 Number of HR_V1 handover ..................... 1896 C901270153 Number of HR_V1 handover success.......... 1897 C901270154 Number of HR_V3 handover ..................... 1897 C901270155 Number of HR_V3 handover success.......... 1898 C901270177 Resource releasing of ordinary users due to being grabbed (TCH/H) ...................................... 1898 C901270178 Handover of ordinary users due to being grabbed (TCH/H) ............................................... 1899 C901270179 Number of Channel Request of priority users (TCH/H) ........................................................... 1901 C901270180 Number of Successful Channel seize of priority users (TCH/H) ........................................ 1902 C901270181 Number of Successful grabbing channel of priority users (TCH/H) ........................................ 1903
C901280011 Number of UNIT DATA INDICATION messages ......................................................... 1916 C901280012 Number of CHANNEL ACTIVATION messages ......................................................... 1916 C901280013 Number of CHANNEL ACTIVATION ACK messages ......................................................... 1917 C901280014 Number of CHANNEL ACTIVATION Negative ACK messages .................................................. 1918 C901280015 Number of CONNECTION FAILURE INDICATION messages ....................................... 1918 C901280016 Number of DEACTIVATE SACCH messages ......................................................... 1919 C901280017 Number of ENCRYPTION COMMAND messages ......................................................... 1920 C901280018 Number of HANDOVER DETECTION messages ......................................................... 1920 C901280019 Number of MEASUREMENT RESULT messages ......................................................... 1921 C901280020 Number of MODE MODIFY REQUEST messages ......................................................... 1922 C901280021 Number of MODE MODIFY ACK messages ......................................................... 1923 C901280022 Number of MODE MODIFY NACK messages ......................................................... 1923 C901280023 Number of PHYSICAL CONTEXT REQUEST messages ......................................................... 1924 C901280024 Number of PHYSICAL CONTEXT CONFIRM messages ......................................................... 1925 C901280025 Number of RF CHANNEL RELEASE messages ......................................................... 1925 C901280026 Number of MS POWER CONTROL messages ......................................................... 1926 C901280027 Number of BS POWER CONTROL messages ......................................................... 1927 C901280028 Number of PREPROCESSED CONFIGURE messages ......................................................... 1927 C901280029 Number of PREPROCESSED MEASUREMENT RESULT messages ............................................. 1928 C901280030 Number of RF CHANNEL RELEASE ACK messages ......................................................... 1929
C901280031 Number of SACCH INFO MODIFY messages ......................................................... 1930 C901280032 Number of ABIS_PREPROC_ENHANCEMEAS_RESULT messages .................................... 1930 C901280033 Number of ABIS_ROUND_TRIP_DELAY_REPORT messages................................................. 1931 C901280034 Number of ABIS_PRE_HO_NOTIFY messages ......................................................... 1932 C901280035 Number of ABIS_BCCH_INFO messages ......................................................... 1932 C901280036 Number of ABIS_CCCH_LOAD_IND messages ......................................................... 1933 C901280037 Number of ABIS_CHL_RQD messages......... 1934 C901280038 Number of ABIS_DELETE_IND messages ......................................................... 1934 C901280039 Number of ABIS_PAGING_CMD messages ......................................................... 1935 C901280040 Number of ABIS_IMM_ASSIGN_CMD messages ......................................................... 1936 C901280041 Number of ABIS_SMS_BROADCAST_REQ messages ......................................................... 1936 C901280042 Number of ABIS_SMS_BROADCAST_CMD messages ......................................................... 1937 C901280043 Number of ABIS_CBCH_LOAD_IND messages ......................................................... 1938 C901280044 Number of ABIS_EGPRS_CHL_REQ messages ......................................................... 1938 C901280045 Number of ABIS_LOAD_CONTROL messages ......................................................... 1939 C901280046 Number of ABIS_END_LOAD_CONTROL messages ......................................................... 1940 C901280047 Number of ABIS_END_LOAD_CONTROL_ACK messages ......................................................... 1940 C901280048 Number of ABIS_PCCCH_LOAD_IND messages ......................................................... 1941 C901280049 Number of ABIS_RF_RESRC_IND messages ......................................................... 1942 C901280050 Number of ABIS_SACCH_FILLING messages ......................................................... 1942
C901280051 Number of ABIS_OVERLOAD messages ......................................................... 1943 C901280052 Number of ABIS_ERROR_REPORT messages ......................................................... 1944 C901280053 Number of ABIS_SYSINFO_REQ messages ......................................................... 1944 C901280054 Number of ABIS_SI_BC_END messages ......................................................... 1945 C901280055 Number of ABIS_SI_NACK messages......... 1946 C901280056 Number of ABIS_PWRCTRL_IND messages ......................................................... 1946 C901280057 Number of ABIS_SYSINFO_ACK messages ......................................................... 1947 C901280061 Number of ABIS_PACKET_PBCCH_INF messages ......................................................... 1948 C901280062 Number of ABIS_PACKET_CCCH_PARA messages ......................................................... 1948 C901280063 Number of ABIS_PACKET_PBCCH_PARA messages ......................................................... 1949 C901280064 Number of ABIS_PACKET_CHN_REQ messages ......................................................... 1950 C901280065 Number of ABIS_PACKET_PAGING_CMD messages ......................................................... 1950 C901280066 Number of ABIS_PACKET_IMM_ASSIGN_CMD messages......................................... 1951 C901280067 Number of ABIS_PACKET_CONNECT_FAIL_IND messages .................................. 1952 C901280068 Number of ABIS_PACKET_PRACH_OVERLOAD messages ................................................ 1952 C901280069 Number of ABIS_PACKET_PCH_OVERLOAD messages ......................................................... 1953 C901280070 Number of ABIS_PACKET_TA_REQUEST messages ......................................................... 1954 C901280071 Number of ABIS_PACKET_TA_REQUEST_ACK messages ......................................................... 1954 C901280072 Number of ABIS_PACKET_CHN_CONFIG_CHG messages ........................................... 1955 C901280073 Number of ABIS_PACKET_CHN_CONFIG_CHG_RESP messages .................................. 1956
C901280074 Number of ABIS_PACKET_PIA_DEL_IND messages ......................................................... 1956 C901280075 Number of ABIS_PACKET_SEND_PIA_IND messages ......................................................... 1957 C901280076 Number of ABIS_PACKET_CHN_CONFIG_REQ messages............................................ 1958 C901280077 Number of ABIS_EGPRS_PACKET_CHN_REQ messages ......................................................... 1958 C901280078 Number of ABIS_PS_CHANNEL_ACTIVE messages ......................................................... 1959 C901280079 Number of ABIS_PS_CHANNEL_ACTIVE_ACK messages ......................................................... 1960 C901280080 Number of ABIS_PS_CHANNEL_ACTIVE_NACK messages ........................................ 1960 C901280081 Number of ABIS_PS_CHANNEL_RELEASE messages ......................................................... 1961 C901280082 Number of ABIS_PS_CHANNEL_RELEASE_ACK messages ........................................ 1962 C901280083 Number of ABIS_PS_CHANNEL_RELEASE_NACK messages...................................... 1962 C901280084 Number of ABIS_PSCONN_CMM_REQ messages ......................................................... 1963 C901280085 Number of ABIS_PSCONN_CMM_ACK messages ......................................................... 1964 C901280086 Number of ABIS_PSCONN_CMM_NACK messages ......................................................... 1964 C901280087 Number of ABIS_GLOBAL_RESET messages ......................................................... 1965 C901280088 Number of ABIS_GLOBAL_RESET_ACK messages ......................................................... 1966 C901280089 Number of ABIS_GLOBAL_RESET_NACK messages ......................................................... 1966 C901280090 Number of ABIS_PACKET_UP_ASSIGN messages ......................................................... 1967 C901280091 Number of ABIS_PACKET_DOWN_ASSIGN messages ......................................................... 1968 C901280092 Number of ABIS_CSCONN_CMM_REQ messages ......................................................... 1968 C901280093 Number of ABIS_CSCONN_CMM_ACK messages ......................................................... 1969
C901280094 Number of ABIS_CSCONN_CMM_NACK messages ......................................................... 1970 C901280095 Number of ABIS_CCMCONN_CMM_REQ messages ......................................................... 1970 C901280096 Number of ABIS_CCMCONN_CMM_ACK messages ......................................................... 1971 C901280097 Number of ABIS_CCMCONN_CMM_NACK messages ......................................................... 1972 C901280098 Number ABIS_PACKET_ACCESS_REJ messages ......................................................... 1972 C901280099 Number of ABIS_PACKET_IMM_ASSIGN_CMD_NEW messages ................................ 1973 C901280100 Number of PACKET_DOWNLINK_ASSIGN messages ......................................................... 1974 C901280101 Number of PACKET_UPLINK_ASSIGN messages ......................................................... 1974 C901280102 Number of ABIS_PACKET_ACCESS_REJ_NEW messages.................................. 1975
C901290010 Number of wireless status messages sent by BSC due to Bad Link Quality................................ 1984 C901290011 Number of Wireless status messages sent by BSC due to Cell reselection command .............. 1984 C901290012 Number of FLOW-CONTROL-BVC messages sent by BSC...................................................... 1985 C901290013 Number of FLOW-CONTROL-BVC-ACK messages received by BSC ................................. 1985 C901290014 Number of FLOW-CONTROL-MS messages sent by BSC...................................................... 1986 C901290015 Number of FLOW-CONTROL-MS-ACK messages received by BSC ................................. 1987 C901290016 Number of FLOW-CONTROL-PFC messages sent by BSC...................................................... 1987 C901290017 Number of FLOW-CONTROL-PFC-ACK messages received by BSC ................................. 1988 C901290018 Number of Status messages sent by BSC ................................................................. 1989 C901290019 Number of Status messages received by BSC ................................................................. 1989 C901290020 Number of Status messages sent with BVCI Unknown .......................................................... 1990 C901290021 Number of Status messages sent with Cell service congestion ............................................. 1990 C901290022 Number of Status messages sent with protocol error.................................................... 1991 C901290023 Number of Status messages sent with Processor overload............................................. 1991 C901290024 Number of Status messages received with BVCI Unknown .................................................. 1991 C901290025 Number of Status messages received with Cell service congestion ....................................... 1992 C901290026 Number of Status messages received with protocol error.................................................... 1992 C901290027 Number of Status messages received with Processor overload............................................. 1992 C901290028 Number of DOWNLOAD-BSS-PFC messages sent by BSC...................................................... 1993 C901290029 Number of BVCCREATE-BSS-PFC messages received by BSC ................................................ 1993
C901290030 Number of CREATE-BSS-PFC-ACK messages sent by BSC...................................................... 1994 C901290031 Number of CREATE-BSS-PFC-NACK messages sent by BSC ....................................... 1995 C901290032 Number of MODIFY-BSS-PFC messages sent by BSC............................................................. 1995 C901290033 Number of MODIFY-BSS-PFC-ACK messages received by BSC ................................................ 1996 C901290034 Number of DELETE-BSS-PFC messages received by BSC ................................................ 1997 C901290035 Number of DELETE -BSS-PFC-ACK messages sent by BSC...................................................... 1997 C901290036 Number of DELETE -BSS-PFC-REQ messages received by BSC ................................................ 1998
C901300015 Number of blocking confirm messages send to opposite end by NS sub layer .......................... 2009 C901300016 Number of received blocking confirm messages sent by opposite end ........................... 2010 C901300017 Number of unblocking messages send to opposite end by NS sub layer .............................. 2010 C901300018 Number of received unblocking messages sent by opposite end.......................................... 2011 C901300019 Number of unblocking confirm messages send to opposite end by NS sub layer ................... 2012 C901300020 Number of received unblocking acknowledge messages replied by opposite end........................ 2012 C901300021 Number of abnormal cases in NS transmission due to network fault ........................ 2013 C901300022 Number of abnormal cases in NS transmission due to O&M interference .................. 2014 C901300023 Number of abnormal cases in NS transmission due to equipment fault..................... 2015 C901300024 Number of abnormal cases in NS transmission due to NSVC block .......................... 2015 C901300025 Number of abnormal cases in NS transmission due to unknown NSVC ..................... 2016 C901300026 Number of abnormal cases in NS transmission due to protocol error ....................... 2017 C901300027 Number of test failure (while over max) ............................................................... 2017 C901300028 Number of blocking procedure failure (after exceeding the maximum times)........................... 2018 C901300029 Number of unblocking procedure failure (after exceeding the maximum times) .................. 2019 C901300030 Number of congestion occurrence of level 1 ..................................................................... 2020 C901300031 Number of congestion recovery of level 1 ..................................................................... 2020 C901300032 Number of congestion occurrence of level 2 ..................................................................... 2021 C901300033 Number of congestion recovery of level 2 ..................................................................... 2021 C901300034 Number of congestion occurrence of level 3 ..................................................................... 2021
C901300035 Number of congestion recovery of level 3 ..................................................................... 2021 C901300036 Number of BECN..................................... 2022 C901300037 Number of FECN ..................................... 2022
C901310021 Number of PERFORM_LOCATION_RESPONSE message sent.................................................... 2039 C901310022 Number of PERFORM_LOCATION_ABORT message received .............................................. 2040 C901310023 Number of POSITION_COMMAND message sent................................................................. 2040 C901310024 Number of POSITION_RESPONSE message received ........................................................... 2041 C901310025 Number of status messages sent............... 2042 C901310026 Number of status messages received ......... 2042 C901310027 Number of status messages sent with BVCI Unknown .......................................................... 2043 C901310028 Number of status messages sent with cell service congestion ............................................. 2043 C901310029 Number of status messages sent with protocol error.................................................... 2044 C901310030 Number of status messages sent with processor overload ............................................ 2044 C901310031 Number of status messages sent with semantically incorrect PDU.................................. 2045 C901310032 Number of status messages sent with invalid mandatory information element........................... 2045 C901310033 Number of status messages sent with missing mandatory IE ........................................ 2046 C901310034 Number of status messages sent with missing conditional IE ........................................ 2046 C901310035 Number of status messages sent with unexpected conditional IE ................................... 2047 C901310036 Number of status messages sent with conditional IE error ............................................ 2047 C901310037 Number of status messages sent with protocol status incompatible error........................ 2048 C901310038 Number of status messages received with BVCI unknown .................................................. 2048 C901310039 Number of status messages received with cell service congestion........................................ 2049 C901310040 Number of status messages received with protocol error.................................................... 2049 C901310041 Number of status messages received with processor overload ............................................ 2049
C901310042 Number of status messages received with BVC blocking..................................................... 2050 C901310043 Number of status messages received with semantically incorrect PDU.................................. 2050 C901310044 Number of status messages received with invalid mandatory IE .......................................... 2051 C901310045 Number of status messages received with missing mandatory IE ........................................ 2051 C901310046 Number of status messages received with missing conditional IE ........................................ 2051 C901310047 Number of status messages received with unexpected conditional IE ................................... 2052 C901310048 Number of status messages received with conditional IE error ............................................ 2052 C901310049 Number of status messages received with protocol status incompatible error........................ 2053 C901310050 Number of status messages received with SGSN congestion ............................................... 2053
C901320011 Number of normal decrease of MS power due to UL signal quality ...................................... 2067 C901320012 Number of rapid decrease in MS power due to UL signal quality ............................................ 2068 C901320013 Number of normal increases of BS power due to DL signal quality ...................................... 2069 C901320014 Number of rapid increase in BTS power due to DL signal quality ............................................ 2070 C901320015 Number of normal decrease of BS power due to DL signal quality ...................................... 2071 C901320016 Number of rapid decrease in BTS power due to DL signal quality ............................................ 2072 C901320017 Total value of each result of regular scanning of MS utilization power ....................................... 2073 C901320018 Number of regular scanning and sampling of MS utilization power........................................... 2074 C901320019 Total value of each result of regular scanning of BS utilization power ....................................... 2075 C901320020 Number of regular scanning and sampling of BS utilization power ........................................... 2076 C901320021 Total value of power scans of DL signal level ................................................................ 2077 C901320022 Number of power scans of DL signal level ................................................................ 2078 C901320023 Total value of power scans of UL signal level ................................................................ 2079 C901320024 Number of power scans of UL signal level ................................................................ 2080 C901320025 Total value of power scans of DL signal quality ............................................................. 2081 C901320026 Number of power scans of DL signal quality ............................................................. 2082 C901320027 Total value of power scans of UL signal quality ............................................................. 2083 C901320028 Number of power scans of UL signal quality ............................................................. 2084 C901320029 Maximum value of UL signal level in regular scan ................................................................ 2085 C901320030 Minimum value of UL signal level in regular scan ................................................................ 2086
C901320031 Maximum value obtained in regular scan of DL signal level................................................... 2087 C901320032 Minimum value obtained in regular scan of DL signal level................................................... 2088 C901320033 Sum of Periodic BS Power (TCH/F) Search Result .............................................................. 2089 C901320034 Periodic BS Power (TCH/F) Search Times .............................................................. 2089 C901320035 Sum of Periodic BS Power (TCH/H) Search Result .............................................................. 2090 C901320036 Number of Periodic BS Power (TCH/H) Search ............................................................. 2090 C901320037 Sum of Periodic BS Power (SDCCH) Search Result .............................................................. 2091 C901320038 Number of Periodic BS Power (SDCCH) Search ............................................................. 2091 C901320039 Sum of Periodic DL Signal Level (TCH/F) Search Result.................................................... 2091 C901320040 Number of Periodic DL Signal Level (TCH/F) Search ............................................................. 2092 C901320041 Sum of Periodic DL Signal Level (TCH/H) Search Result.................................................... 2092 C901320042 Number of Periodic DL Signal Level (TCH/H) Search ............................................................. 2093 C901320043 Sum of Periodic DL Signal Level (SDCCH) Search Result.................................................... 2093 C901320044 Number of Periodic DL Signal Level (SDCCH) Search ............................................................. 2093
C901330006 Number of abnormal cases in NS transmission due to protocol error ....................... 2097 C901330007 Number of unsuccess test due to over max................................................................. 2098
C901340017 Number of status messages received by BSC ................................................................. 2110 C901340018 Number of status messages sent with BVCI Unknown .......................................................... 2111 C901340019 Number of status messages sent with cell service congestion ............................................. 2111 C901340020 Number of status messages sent with protocol error.................................................... 2112 C901340021 Number of status messages sent with Processor overload............................................. 2112 C901340022 Number of status messages received with BVCI Unknown .................................................. 2112 C901340023 Number of status messages received with cell service congestion........................................ 2113 C901340024 Number of status messages received with protocol error.................................................... 2113 C901340025 Number of status messages received with processor overload ............................................ 2114 C901340026 Number of DOWNLOAD-BSS-PFC messages sent by BSC...................................................... 2114 C901340027 Number of BVCCREATE-BSS-PFC messages received by BSC ................................................ 2115 C901340028 Number of CREATE-BSS-PFC-ACK messages sent by BSC...................................................... 2115 C901340029 Number of CREATE-BSS-PFC-NACK messages sent by BSC ....................................... 2116 C901340030 Number of MODIFY-BSS-PFC messages sent by BSC............................................................. 2117 C901340031 Number of MODIFY-BSS-PFC-ACK messages received by BSC ................................................ 2117 C901340032 Number of DELETE-BSS-PFC messages received by BSC ................................................ 2118 C901340033 Number of DELETE-BSS-PFC-ACK messages sent by BSC...................................................... 2119 C901340034 Number of DELETE-BSS-PFC-REQ messages received by BSC ................................................ 2119 C901340035 Number of PS-HANDOVER-REQUIRED messages sent by BSC ....................................... 2120 C901340036 Number of PS-HANDOVER-REQUIRED-ACK messages received by BSC ................................. 2120
C901340037 Number of PS-HANDOVER-REQUIRED-NACK messages received by BSC ................................. 2121 C901340038 Number of PS-HANDOVER-REQUEST messages received by BSC ................................. 2122 C901340039 Number of PS-HANDOVER-REQUEST-ACK messages sent by BSC ....................................... 2123 C901340040 Number of PS-HANDOVER-REQUEST-NACK messages sent by BSC ....................................... 2124 C901340041 Number of PS-HANDOVER-COMPLETE messages sent by BSC ....................................... 2125 C901340042 Number of PS-HANDOVER-CANCEL messages sent by BSC ....................................... 2126 C901340043 Number of PS-HANDOVER-REQUEST messages with Service UTRAN CCO received by BSC ................................................................. 2127 C901340044 Number of CREATE-BSS-PFC messages with Service UTRAN CCO received by BSC ................... 2128
C901350014 Number of BVC-UNBLOCK message sent................................................................. 2138 C901350015 Number of BVC-UNBLOCK-ACK message received ........................................................... 2138 C901350016 Number of BVC-RESET message sent......... 2139 C901350017 Number of BVC-RESET message received ........................................................... 2139 C901350018 Number of BVC-RESET-ACK message sent................................................................. 2140 C901350019 Number of BVC-RESET-ACK message received ........................................................... 2140 C901350020 Number of PERFORM LOCATION-REQUEST message received .............................................. 2141 C901350021 Number of PERFORM-LOCATION-RESPONSE message sent.................................................... 2141 C901350022 Number of PERFORM-LOCATION-ABORT message received .............................................. 2142 C901350023 Number of POSITION-COMMAND message sent................................................................. 2142 C901350024 Number of POSITION-RESPONSE message received ........................................................... 2143 C901350025 Number of status messages sent............... 2143 C901350026 Number of status messages received ......... 2144 C901350027 Number of status messages sent with BVCI Unknown .......................................................... 2144 C901350028 Number of status messages sent with cell service congestion ............................................. 2145 C901350029 Number of status messages sent with protocol error.................................................... 2145 C901350030 Number of status messages sent with processor overload ............................................ 2146 C901350031 Number of status messages sent with semantically incorrect PDU.................................. 2146 C901350032 Number of status messages sent with invalid mandatory information element........................... 2147 C901350033 Number of status messages sent with missing mandatory IE ........................................ 2147 C901350034 Number of status messages sent with missing conditional IE ........................................ 2148
C901350035 Number of status messages sent with unexpected conditional IE ................................... 2148 C901350036 Number of status messages sent with conditional IE error ............................................ 2149 C901350037 Number of status messages sent with protocol status incompatible error........................ 2149 C901350038 Number of status messages received with BVCI unknown .................................................. 2150 C901350039 Number of status messages received with cell service congestion........................................ 2150 C901350040 Number of status messages received with protocol error.................................................... 2150 C901350041 Number of status messages received with processor overload ............................................ 2151 C901350042 Number of status messages received with BVC blocking..................................................... 2151 C901350043 Number of status messages received with semantically incorrect PDU.................................. 2152 C901350044 Number of status messages received with invalid mandatory IE .......................................... 2152 C901350045 Number of status messages received with missing mandatory IE ........................................ 2153 C901350046 Number of status messages received with missing conditional IE ........................................ 2153 C901350047 Number of status messages received with unexpected conditional IE ................................... 2154 C901350048 Number of status messages received with conditional IE error ............................................ 2154 C901350049 Number of status messages received with protocol status incompatible error........................ 2155 C901350050 Number of status messages received with SGSN congestion ............................................... 2155
C901360004 Number of RESOURCE REQUEST messages ......................................................... 2162 C901360005 Number of RESOURCE INDICATION messages ......................................................... 2163 C901360006 Number of PAGING messages ................... 2164 C901360007 Number of CIPHER MODE COMMAND messages ......................................................... 2164 C901360008 Number of CIPHER MODE COMPLETE messages ......................................................... 2165 C901360009 Number of CIPHER MODE REJECT messages ......................................................... 2166 C901360010 Number of sent CLASSMARK UPDATE messages ......................................................... 2166 C901360011 Number of received CLASSMARK UPDATE messages ......................................................... 2167 C901360012 Number of QUEUING INDICATION messages ......................................................... 2167 C901360013 Number of COMPLETE LAYER 3 INFORMATION messages .................................... 2168 C901360014 Number of CLASSMARK REQUEST messages ......................................................... 2169 C901360015 Number of uplink LOAD INDICATION messages ......................................................... 2169 C901360016 Number of downlink LOAD INDICATION messages ......................................................... 2170 C901360017 Number of HANDOVER REQUEST messages ......................................................... 2171 C901360018 Number of HANDOVER REQUIRED messages ......................................................... 2171 C901360019 Number of HANDOVER COMMAND messages ......................................................... 2172 C901360020 Number of HANDOVER REQUEST ACK messages ......................................................... 2173 C901360021 Number of HANDOVER COMPLETE messages ......................................................... 2174 C901360022 Number of HANDOVER SUCCEEDED messages ......................................................... 2175 C901360023 Number of HANDOVER CANDIDATE ENQUIRE messages ......................................................... 2176
C901360024 Number of HANDOVER CANDIDATE RESPONSE messages ......................................... 2177 C901360025 Number of HANDOVER FAILURE messages ......................................................... 2177 C901360026 Number of HANDOVER PERFORMED messages ......................................................... 2178 C901360027 Number of HANDOVER REQUIRED REJECT messages ......................................................... 2179 C901360028 Number of HANDOVER DETECT messages ......................................................... 2179 C901360029 Number of CLEAR COMMAND messages ......................................................... 2180 C901360030 Number of CLEAR COMPLETE messages ......................................................... 2181 C901360031 Number of CLEAR REQUEST messages............................................................... 2181 C901360032 Number of SAPI "N" REJECT messages ......................................................... 2182 C901360033 Number of UL CONFUSION messages......... 2182 C901360034 Number of DL CONFUSION messages......... 2183 C901360035 Number of UL RESET messages ................ 2184 C901360036 Number of DL RESET messages ................ 2184 C901360037 Number of UL RESET ACKNOWLEDGE messages ......................................................... 2185 C901360038 Number of DL RESET ACKNOWLEDGE messages ......................................................... 2186 C901360039 Number of UL OVERLOAD messages .......... 2186 C901360040 Number of DL OVERLOAD messages .......... 2187 C901360041 Number of MSC INVOKE TRACE messages ......................................................... 2187 C901360042 Number of sent BSS INVOKE TRACE messages ......................................................... 2188 C901360043 Number of received BSS INVOKE TRACE messages ......................................................... 2189 C901360044 Number of sent CONNECTIONLESS INFORMATION messages .................................... 2189 C901360045 Number of received CONNECTIONLESS INFORMATION messages .................................... 2190 C901360046 Number of SUSPEND messages ................ 2190 C901360047 Number of RESUME messages .................. 2191
C901360048 Number of Common ID messages ............. 2192 C901360049 Number of LSA INFORMATION messages ......................................................... 2192 C901360050 Number of PERFORM LOCATION REQUEST messages ......................................................... 2193 C901360051 Number of PERFORM LOCATION RESPONSE messages ......................................................... 2193 C901360052 Number of PERFORM LOCATION ABORT messages ......................................................... 2194 C901360053 Number of sent BLOCK messages.............. 2194 C901360054 Number of received BLOCK ACK messages ......................................................... 2195 C901360055 Number of sent UNBLOCK messages ......... 2196 C901360056 Number of received UNBLOCK ACK messages ......................................................... 2197 C901360057 Number of received BLOCK messages......... 2197 C901360058 Number of sent BLOCK ACK messages......... 2198 C901360059 Number of received UNBLOCK messages ......................................................... 2199 C901360060 Number of sent UNBLOCK ACK messages ......................................................... 2199 C901360061 Number of UL RESET CIRCUIT messages ......................................................... 2200 C901360062 Number of DL RESET CIRCUIT messages ......................................................... 2201 C901360063 Number of UL RESET CIRCUIT ACK messages ......................................................... 2201 C901360064 Number of DL RESET CIRCUIT ACK messages ......................................................... 2202 C901360065 Number of UL CIRCUIT GROUP BLOCK messages ......................................................... 2203 C901360066 Number of DL CIRCUIT GROUP BLOCK messages ......................................................... 2203 C901360067 Number of UL CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages .................................. 2204 C901360068 Number of DL CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages .................................. 2205 C901360069 Number of UL CIRCUIT GROUP UNBLOCK messages ......................................................... 2205
C901360070 Number of DL CIRCUIT GROUP UNBLOCK messages ......................................................... 2206 C901360071 Number of UL CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE messages .................................. 2207 C901360072 Number of DL CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE messages .................................. 2208 C901360073 Number of UL UNEQUIPPED CIRCUIT messages ......................................................... 2208 C901360074 Number of DL UNEQUIPPED CIRCUIT messages ......................................................... 2209 C901360075 Number of CHANGE CIRCUIT messages ......................................................... 2210 C901360076 Number of CHANGE CIRCUIT ACK messages ......................................................... 2210 C901360077 Number of HANDOVER PERFORMED ACK messages ......................................................... 2211 C901360078 The count of Sending INTERNAL HANDOVER REQUIRED ........................................................ 2211 C901360079 The count of Receiving INTERNAL HANDOVER COMMAND ....................................... 2213 C901360080 The count of Receiving INTERNAL HANDOVER REJECT............................................ 2214 C901360081 Number of INTERNAL HANDOVER ENQUIRY messages ......................................................... 2214 C901360082 Number of UL RESET IP RESOURCE messages ......................................................... 2215 C901360083 Number of UL RESET IP RESOURCE ACKOWNLEDGE messages .................................. 2216 C901360084 Number of DL RESET IP RESOURCE messages ......................................................... 2216 C901360085 Number of DL RESET IP RESOURCE ACKNOWLEDGE messages .................................. 2217 C901360086 Number of Release Clear Request on SDCCH............................................................. 2218 C901360087 Number of Release Clear Request on TCH/F .............................................................. 2218 C901360088 Number of Release Clear Request on TCH/H.............................................................. 2218
C901370001 Number of UL DTAP messages .................. 2219 C901370002 Number of DL DTAP messages .................. 2220 C901370003 Number of UL BSSMAP messages .............. 2220 C901370004 Number of DL BSSMAP messages.............. 2221 C901370005 Number of DL BSSMAP messages received with error ......................................................... 2222 C901370006 Number of chosen for MSC Load share by NULL_NRI......................................................... 2222 C901370007 Number of chosen for MSC Load share by the NRI not in the MSC pool ................................ 2223
C901380017 The times of RTP multiplexing applied without RTP header compression ......................... 2235 C901380018 The times of RTP multiplexing applied with RTP header compression..................................... 2236 C901380019 Mean number of busy trunk circuits........... 2236 C901380020 Mean number of seizure UDP port ............. 2238
C901390017 Number of UL UNBLOCK GROUP CIRCUIT messages on Ater .............................................. 2247 C901390018 Number of DL UNBLOCK Ater GROUP CIRCUIT messages ............................................ 2248 C901390019 Number of UL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages ..................... 2248 C901390020 Number of DL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages ..................... 2248 C901390021 Number of UL UNEQUIPPED Ater CIRCUIT messages ......................................................... 2249 C901390022 Number of DL UNEQUIPPED Ater CIRCUIT messages ......................................................... 2249 C901390023 Number of UL BLOCK A CIRCUIT messages ......................................................... 2250 C901390024 Number of DL BLOCKING A CIRCUIT ACKNOWLEDGE messages .................................. 2250 C901390025 Number of UL UNBLOCK A CIRCUIT messages ......................................................... 2250 C901390026 Number of DL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages .................................. 2251 C901390027 Number of DL BLOCK A CIRCUIT messages ......................................................... 2251 C901390028 Number of UL BLOCKING A CIRCUIT ACKNOWLEDGE messages .................................. 2251 C901390029 Number of DL UNBLOCK A CIRCUIT messages ......................................................... 2252 C901390030 Number of UL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages .................................. 2252 C901390031 Number of UL BLOCK A CIRCUIT GROUP messages ......................................................... 2252 C901390032 Number of DL BLOCK A CIRCUIT GROUP messages ......................................................... 2253 C901390033 Number of UL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages .................................. 2253 C901390034 Number of DL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages .................................. 2253 C901390035 Number of UL UNBLOCK A CIRCUIT GROUP messages ......................................................... 2254 C901390036 Number of DL UNBLOCK A CIRCUIT GROUP messages ......................................................... 2254
C901390037 Number of UL UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages ....................... 2255 C901390038 Number of DL UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages ....................... 2255 C901390039 Number of UL UNEQUIPPED A CIRCUIT messages ......................................................... 2255 C901390040 Number of DL UNEQUIPPED A CIRCUIT messages ......................................................... 2256 C901390041 Number of UL Ater RESET messages.......... 2256 C901390042 Number of DL Ater RESET messages.......... 2256 C901390043 Number of UL Ater RESET ACKNOWLEDGE messages ......................................................... 2257 C901390044 Number of DL Ater RESET ACKNOWLEDGE messages ......................................................... 2257 C901390045 Number of UL Ater CONFUSION messages ......................................................... 2257 C901390046 Number of DL Ater CONFUSION messages ......................................................... 2258 C901390047 Number of RESOURCE REQUEST messages ......................................................... 2258 C901390048 Number of RESOURCE INDICATION messages ......................................................... 2258 C901390049 Number of RESOURCE NON-INDICATION messages ......................................................... 2259 C901390050 Number of resource release request messages ......................................................... 2259 C901390051 Number of resource release acknowledge messages ......................................................... 2260 C901390052 Number of resource failure messages......... 2260 C901390053 Number of TFO status messages ............... 2260 C901390054 Number of TFO common voice type messages ......................................................... 2261 C901390055 Number of TFO control messages .............. 2261
C901400005 Number of error SU due to CRC Error......... 2265 C901400006 Number of Other error ............................. 2266 C901400007 Number of Negative Acknowledgement Received .......................................................... 2266 C901400008 Octets of MSU Retransmitted .................... 2266 C901400009 Number of MSU Resend ........................... 2267 C901400010 Number of Align Error.............................. 2267 C901400011 Number of Error SU................................. 2267 C901400012 Number of MSU discarded due to congestion........................................................ 2268 C901400013 Number of SL failure due to Abnormal FIBR BSNR ............................................................... 2268 C901400014 Number of SL failure due to Excessive delay of ack .............................................................. 2268 C901400015 Number of SL failure due to Excessive error rate ................................................................. 2269 C901400016 Number of SL failure due to Excessive duration of congestion........................................ 2269
C901420006 Number of messages sent to ulp ............... 2278 C901420007 Bytes of messages sent to ulp .................. 2278 C901420008 Number of messages received from ulp .................................................................. 2278 C901420009 Bytes of messages received from .............. 2279 C901420010 Number of Congestion ............................. 2279 C901420011 Duration of congestion............................. 2279 C901420012 Chunk number of fast retransmission......... 2280 C901420013 Chunk number of time-out retransmission ................................................................. 2280 C901420014 RTT is lower than T1................................ 2280 C901420015 RTT is between T1 and T2 ........................ 2281 C901420016 RTT is higher than T2 .............................. 2281 C901420017 Number of network transmission dropped packets ............................................................ 2281 C901420018 Maximum delay of network transmission ................................................................. 2282 C901420019 Minimum delay of network transmission ................................................................. 2282 C901420020 Total delay of network transmission(high 4 bytes) .............................................................. 2283 C901420021 Total delay of network transmission(low 4 bytes) .............................................................. 2283 C901420022 Number of delay samples of network transmission ..................................................... 2283 C901420023 Maximum dithering of network transmission ..................................................... 2284 C901420024 Minimum dithering of network transmission ..................................................... 2284 C901420025 Total dithering of network transmission(high 4 bytes) ........................................................... 2285 C901420026 Total dithering of network transmission(low 4 bytes) ........................................................... 2285 C901420027 Number of dithering samples of network transmission ..................................................... 2286 C901420028 Chunks Lost On Send Dirction................... 2286 C901420029 Chunks Trans On Send Dirction ................. 2286 C901420030 Number of abort from peer....................... 2287 C901420031 Number of association break by retransmission .................................................. 2287
C901450018 Number of sampling of 8PSK-MEANBEP ................................................................. 2313 C901450019 Number of sampling of 8PSK-CV-BEP......... 2314 C901450020 Number of RLC uplink ACK TBF ................. 2315 C901450021 Number of RLC uplink NACK TBF ............... 2316 C901450022 Number of DL-UNITDATA messages with Service UTRAN CCO received by BSC ................... 2316 C901450023 Total Block Num...................................... 2317 C901450024 UL Idle Block Num .................................. 2317 C901450025 DL Idle Block Num .................................. 2317 C901450026 The max length of packet latency period in Abis ................................................................. 2317 C901450027 The min length of packet latency period in Abis ................................................................. 2318 C901450028 The average length of packet latency period in Abis ............................................................. 2318 C901450029 The latest length of packet latency period in Abis ................................................................. 2319 C901450030 The length of packet latency period between 0 and 20 ms (20 included) in Abis........................ 2319 C901450031 The length of packet latency period between 20 ms and 40 ms (40 included) in Abis ................. 2320 C901450032 The length of packet latency period between 40 ms and 60 ms (60 included) in Abis ................. 2320 C901450033 The length of packet latency period between 60 ms and 80 ms (80 included) in Abis ................. 2321 C901450034 The length of packet latency period between 80 ms and 100 ms (100 included) in Abis ............. 2321 C901450035 The length of packet latency period between 100 ms and 120 ms (120 included) in Abis............ 2322 C901450036 The length of packet latency period between 120 ms and 140 ms (140 included) in Abis............ 2322 C901450037 The length of packet latency period between 140 ms and 160 ms (160 included) in Abis............ 2323 C901450038 The length of packet latency period between 160 ms and 180 ms (180 included) in Abis............ 2323 C901450039 The length of packet latency period larger than 180 ms in Abis ........................................... 2324 C901450040 The max length of downlink packet latency period in Gb...................................................... 2324
C901450041 The min length of downlink packet latency period in Gb...................................................... 2324 C901450042 The average length of downlink packet latency period in Gb ........................................... 2325 C901450043 The length of downlink packet latency period between 0 and 100 ms (100 included) in Gb ......... 2325 C901450044 The length of downlink packet latency period between 100 ms and 200 ms (200 included) in Gb................................................................... 2326 C901450045 The length of downlink packet latency period between 200 ms and 300 ms (300 included) in Gb................................................................... 2326 C901450046 The length of downlink packet latency period between 300 ms and 400 ms (400 included) in Gb................................................................... 2327 C901450047 The length of downlink packet latency period between 400 ms and 600 ms (600 included) in Gb................................................................... 2327 C901450048 The length of downlink packet latency period between 600 ms and 1000 ms (1000 included) in Gb................................................................... 2328 C901450049 The length of downlink packet latency period larger than 1000 ms in Gb .................................. 2328 C901450050 The max length of uplink packet latency period in Gb...................................................... 2329 C901450051 The min length of uplink packet latency period in Gb...................................................... 2329 C901450052 The average length of uplink packet latency period in Gb...................................................... 2329 C901450053 LLC Stall Num ........................................ 2330 C901450054 MAC Resource Congestion ........................ 2330 C901450055 BSSGP Resource Congestion..................... 2330 C901450056 Number of Pushing Down Uplink BandWidth ....................................................................... 2331 C901450057 Number of Pushing Down Downlink BandWidth ....................................................... 2331 C901450058 Number of Pushing Up Uplink BandWidth........................................................ 2332 C901450059 Number of Pushing Up Downlink BandWidth........................................................ 2333
C901480010 Number of SNS-CONFIG initiated by SGSN received failed acknowledgements ....................... 2348 C901480011 Number of SNS-ADD initiated by BSC......... 2348 C901480012 Number of SNS-ADD initiated by BSC received successful acknowledgements................. 2349 C901480013 Number of SNS-ADD initiated by BSC received failed acknowledgements ....................... 2349 C901480014 Number of SNS-ADD initiated by BSC without response ............................................... 2350 C901480015 Number of SNS-ADD initiated by SGSN received successful acknowledgements................. 2350 C901480016 Number of SNS-ADD initiated by SGSN received failed acknowledgements ....................... 2351 C901480017 Number of SNS-DELETE initiated by BSC ................................................................. 2351 C901480018 Number of SNS-DELETE initiated by BSC received successful acknowledgements................. 2352 C901480019 Number of SNS-DELETE initiated by BSC received failed acknowledgements ....................... 2352 C901480020 Number of SNS-DELETE initiated by BSC without response ............................................... 2353 C901480021 Number of SNS-DELETE initiated by SGSN received successful acknowledgements................. 2353 C901480022 Number of SNS-DELETE initiated by SGSN received failed acknowledgements ....................... 2354 C901480023 Number of SNS-CHANGEWEIGHT initiated by BSC............................................................. 2354 C901480024 Number of SNS-CHANGEWEIGHT initiated by BSC received successful acknowledgements .......... 2355 C901480025 Number of SNS-CHANGEWEIGHT initiated by BSC received failed acknowledgements ............ 2355 C901480026 Number of SNS-CHANGEWEIGHT initiated by BSC without response .................................... 2356 C901480027 Number of SNS-CHANGEWEIGHT initiated by SGSN received successful acknowledgements......... 2356 C901480028 Number of SNS-CHANGEWEIGHT initiated by SGSN received failed acknowledgements .......... 2357
C901490002 Number of bytes sent to SGSN ................. 2359 C901490003 Number of PDU data sent by NS sub layer ................................................................ 2360 C901490004 Number of PDU data received by NS sub layer ................................................................ 2360 C901490005 Number of PDU data discarded by NS sub layer ................................................................ 2361
C901560003 Number of received IMSI when link establish .......................................................... 2397 C901560004 Number of RANCS module received IMSI when handover ................................................. 2398 C901560005 Number of mobile sent GTTP message under DTM mode ........................................................ 2398 C901560006 Number of BSC successfully sent GTTP message under DTM mode.................................. 2398 C901560007 Number of DTM attempts in mobile ........... 2399 C901560008 Number of DTM uplink attempt failure......... 2399 C901560009 Number of UL DTM database resource assignment success in dedicated mode ................ 2400 C901560010 Number of UL DTM database resource assignment failure in dedicated mode .................. 2400 C901560011 Number of handover(intra-cell) attempts due to UL DTM .................................................. 2401 C901560012 Number of handover(intra-cell) success due to uplink DTM.................................................... 2401 C901560013 Number of handover(intra-cell) failure due to uplink DTM.................................................... 2402 C901560014 Number of DTM failure due to handover.......................................................... 2402 C901560015 Number of UL DTM link establishment success ............................................................ 2402 C901560016 Attempt number of sending LLC packet on FACCH in dedicated mode .................................. 2403 C901560017 Number of successfully sent LLC packet on FACCH in dedicated mode .................................. 2403 C901560018 Attempt Number of DTM established due to SGSN sent LLC packets ...................................... 2404 C901560019 Number of DTM attempts failure ............... 2404 C901560020 Number of DL DTM resource assignment success ............................................................ 2405 C901560021 Number of DL DTM resource assignment failure .............................................................. 2405 C901560022 Number of handover(intra-cell) attempts due to DL DTM .................................................. 2406 C901560023 Number of successfully handover occurs due to DL DTM ........................................................ 2406
C901560024 Number of handover failure occurs due to DL DTM ............................................................ 2407 C901560025 Number of DL DTM failure occurs due to handover.......................................................... 2407 C901560026 Number of successfully DL DTM establishment ................................................... 2408
C901570023 Number of abnormal hop frame ................ 2419 C901570024 Number of normal hop frame.................... 2419 C901570025 Multi Channel Link Lose Frame.................. 2419 C901570026 No useful channel ................................... 2420 C901570027 Max Up Flow .......................................... 2420 C901570028 Max Down Flow ...................................... 2420 C901570029 Current Up Flow...................................... 2421 C901570030 Current Down Flow.................................. 2421
C901580017 Number of receiving location abort in PS ................................................................... 2435 C901580018 Number of TA Request in PS ..................... 2436 C901580019 Number of TA Response in PS ................... 2437 C901580020 Number of MS Position Command in PS ................................................................... 2437 C901580021 Number of MS Position Response in PS ................................................................... 2438 C901580022 Number of location success in PS .............. 2439 C901580023 Number of location failure due to abnormal status of Lb interface in PS ................................. 2439 C901580024 Number of location failure due to radio Timer expiration in PS ................................................. 2440 C901580025 Number of location failure due to Inter-CMP cell reselection in PS .......................................... 2441 C901580026 Number of sending LOCATION INFORMATION message to SMLC due to Intra-CMP cell reselection in PS................................................................ 2442 C901580027 Number of location failure due to location Timer expiration in PS ........................................ 2442 C901580028 Number of location failure due to other BSC's cause in PS .............................................. 2443
C901600004 Maximum of busy 16 K relay circuits of Ater interface........................................................... 2452 C901600005 Maximum of busy 8 K relay circuits of Ater interface........................................................... 2453 C901600006 Total busy time of 16 K relay circuits of Ater interface........................................................... 2455 C901600007 Total busy time of 8 K relay circuits of Ater interface........................................................... 2456
C901620009 Number of samples of UL RQ=1 and receive level between 16 and 20..................................... 2475 C901620010 Number of samples of UL RQ=1 and receive level between 21 and 30..................................... 2476 C901620011 Number of samples of UL RQ=1 and receive level between 31 and 40..................................... 2477 C901620012 Number of samples of UL RQ=1 and receive level between 41 and 63..................................... 2477 C901620013 Number of samples of UL RQ=2 and receive level between 0 and 10 ...................................... 2478 C901620014 Number of samples of UL RQ=2 and receive level between 11 and 15..................................... 2479 C901620015 Number of samples of UL RQ=2 and receive level between 16 and 20..................................... 2480 C901620016 Number of samples of UL RQ=2 and receive level between 21 and 30..................................... 2480 C901620017 Number of samples of UL RQ=2 and receive level between 31 and 40..................................... 2481 C901620018 Number of samples of UL RQ=2 and receive level between 41 and 63..................................... 2482 C901620019 Number of samples of UL RQ=3 and receive level between 0 and 10 ...................................... 2483 C901620020 Number of samples of UL RQ=3 and receive level between 11 and 15..................................... 2483 C901620021 Number of samples of UL RQ=3 and receive level between 16 and 20..................................... 2484 C901620022 Number of samples of UL RQ=3 and receive level between 21 and 30..................................... 2485 C901620023 Number of samples of UL RQ=3 and receive level between 31 and 40..................................... 2486 C901620024 Number of samples of UL RQ=3 and receive level between 41 and 63..................................... 2486 C901620025 Number of samples of UL RQ=4 and receive level between 0 and 10 ...................................... 2487 C901620026 Number of samples of UL RQ=4 and receive level between 11 and 15..................................... 2488 C901620027 Number of samples of UL RQ=4 and receive level between 16 and 20..................................... 2489 C901620028 Number of samples of UL RQ=4 and receive level between 21 and 30..................................... 2489
C901620029 Number of samples of UL RQ=4 and receive level between 31 and 40..................................... 2490 C901620030 Number of samples of UL RQ=4 and receive level between 41 and 63..................................... 2491 C901620031 Number of samples of UL RQ=5 and receive level between 0 and 10 ...................................... 2492 C901620032 Number of samples of UL RQ=5 and receive level between 11 and 15..................................... 2492 C901620033 Number of samples of UL RQ=5 and receive level between 16 and 20..................................... 2493 C901620034 Number of samples of UL RQ=5 and receive level between 21 and 30..................................... 2494 C901620035 Number of samples of UL RQ=5 and receive level between 31 and 40..................................... 2495 C901620036 Number of samples of UL RQ=5 and receive level between 41 and 63..................................... 2495 C901620037 Number of samples of UL RQ=6 and receive level between 0 and 10 ...................................... 2496 C901620038 Number of samples of UL RQ=6 and receive level between 11 and 15..................................... 2497 C901620039 Number of samples of UL RQ=6 and receive level between 16 and 20..................................... 2498 C901620040 Number of samples of UL RQ=6 and receive level between 21 and 30..................................... 2498 C901620041 Number of samples of UL RQ=6 and receive level between 31 and 40..................................... 2499 C901620042 Number of samples of UL RQ=6 and receive level between 41 and 63..................................... 2500 C901620043 Number of samples of UL RQ=7 and receive level between 0 and 10 ...................................... 2501 C901620044 Number of samples of UL RQ=7 and receive level between 11 and 15..................................... 2501 C901620045 Number of samples of UL RQ=7 and receive level between 16 and 20..................................... 2502 C901620046 Number of samples of UL RQ=7 and receive level between 21 and 30..................................... 2503 C901620047 Number of samples of UL RQ=7 and receive level between 31 and 40..................................... 2504 C901620048 Number of samples of UL RQ=7 and receive level between 41 and 63..................................... 2504
C901620049 Number of samples of DL RQ=0 and receive level between 0 and 10 ...................................... 2505 C901620050 Number of samples of DL RQ=0 and receive level between 11 and 15..................................... 2506 C901620051 Number of samples of DL RQ=0 and receive level between 16 and 20..................................... 2507 C901620052 Number of samples of DL RQ=0 and receive level between 21 and 30..................................... 2507 C901620053 Number of samples of DL RQ=0 and receive level between 31 and 40..................................... 2508 C901620054 Number of samples of DL RQ=0 and receive level between 41 and 63..................................... 2509 C901620055 Number of samples of DL RQ=1 and receive level between 0 and 10 ...................................... 2510 C901620056 Number of samples of DL RQ=1 and receive level between 11 and 15..................................... 2510 C901620057 Number of samples of DL RQ=1 and receive level between 16 and 20..................................... 2511 C901620058 Number of samples of DL RQ=1 and receive level between 21 and 30..................................... 2512 C901620059 Number of samples of DL RQ=1 and receive level between 31 and 40..................................... 2513 C901620060 Number of samples of DL RQ=1 and receive level between 41 and 63..................................... 2513 C901620061 Number of samples of DL RQ=2 and receive level between 0 and 10 ...................................... 2514 C901620062 Number of samples of DL RQ=2 and receive level between 11 and 15..................................... 2515 C901620063 Number of samples of DL RQ=2 and receive level between 16 and 20..................................... 2516 C901620064 Number of samples of DL RQ=2 and receive level between 21 and 30..................................... 2516 C901620065 Number of samples of DL RQ=2 and receive level between 31 and 40..................................... 2517 C901620066 Number of samples of DL RQ=2 and receive level between 41 and 63..................................... 2518 C901620067 Number of samples of DL RQ=3 and receive level between 0 and 10 ...................................... 2519 C901620068 Number of samples of DL RQ=3 and receive level between 11 and 15..................................... 2519
C901620069 Number of samples of DL RQ=3 and receive level between 16 and 20..................................... 2520 C901620070 Number of samples of DL RQ=3 and receive level between 21 and 30..................................... 2521 C901620071 Number of samples of DL RQ=3 and receive level between 31 and 40..................................... 2522 C901620072 Number of samples of DL RQ=3 and receive level between 41 and 63..................................... 2522 C901620073 Number of samples of DL RQ=4 and receive level between 0 and 10 ...................................... 2523 C901620074 Number of samples of DL RQ=4 and receive level between 11 and 15..................................... 2524 C901620075 Number of samples of DL RQ=4 and receive level between 16 and 20..................................... 2525 C901620076 Number of samples of DL RQ=4 and receive level between 21 and 30..................................... 2525 C901620077 Number of samples of DL RQ=4 and receive level between 31 and 40..................................... 2526 C901620078 Number of samples of DL RQ=4 and receive level between 41 and 63..................................... 2527 C901620079 Number of samples of DL RQ=5 and receive level between 0 and 10 ...................................... 2528 C901620080 Number of samples of DL RQ=5 and receive level between 11 and 15..................................... 2528 C901620081 Number of samples of DL RQ=5 and receive level between 16 and 20..................................... 2529 C901620082 Number of samples of DL RQ=5 and receive level between 21 and 30..................................... 2530 C901620083 Number of samples of DL RQ=5 and receive level between 31 and 40..................................... 2531 C901620084 Number of samples of DL RQ=5 and receive level between 41 and 63..................................... 2531 C901620085 Number of samples of DL RQ=6 and receive level between 0 and 10 ...................................... 2532 C901620086 Number of samples of DL RQ=6 and receive level between 11 and 15..................................... 2533 C901620087 Number of samples of DL RQ=6 and receive level between 16 and 20..................................... 2534 C901620088 Number of samples of DL RQ=6 and receive level between 21 and 30..................................... 2534
C901620089 Number of samples of DL RQ=6 and receive level between 31 and 40..................................... 2535 C901620090 Number of samples of DL RQ=6 and receive level between 41 and 63..................................... 2536 C901620091 Number of samples of DL RQ=7 and receive level between 0 and 10 ...................................... 2537 C901620092 Number of samples of DL RQ=7 and receive level between 11 and 15..................................... 2537 C901620093 Number of samples of DL RQ=7 and receive level between 16 and 20..................................... 2538 C901620094 Number of samples of DL RQ=7 and receive level between 21 and 30..................................... 2539 C901620095 Number of samples of DL RQ=7 and receive level between 31 and 40..................................... 2540 C901620096 Number of samples of DL RQ=7 and receive level between 41 and 63..................................... 2540
C901640004 Average length of PCH queue: 9*64 .......... 2553 C901640005 The percentage of PCH Blocks validly used ................................................................ 2554 C901640006 Number of paging messages seized by other hyper-priority messages while transmitting on PCH blocks .............................................................. 2554 C901640007 Number of paging messages retransmitted zero times ........................................................ 2554 C901640008 Number of paging messages retransmitted one times ......................................................... 2555 C901640009 Number of paging messages retransmitted two times ......................................................... 2555 C901640010 Number of paging messages retransmitted three times....................................................... 2555 C901640011 Numbers of paging messages retransmitted four times ........................................................ 2556
C901660007 Number of mobile support DTM EGPRS multi TS ability 11 ..................................................... 2569 C901660008 Number of mobile support extend DTM GPRS multi TS ability 5 ............................................... 2570 C901660009 Number of mobile support extend DTM GPRS multi TS ability 6 ............................................... 2571 C901660010 Number of mobile support extend DTM GPRS multi TS ability 9 ............................................... 2572 C901660011 Number of mobile support extend DTM GPRS multi TS ability 10 ............................................. 2573 C901660012 Number of mobile support extend DTM GPRS multi TS ability 11 ............................................. 2574 C901660013 Number of mobile support extend DTM EGPRS multi TS ability 5 ..................................... 2575 C901660014 Number of mobile support extend DTM EGPRS multi TS ability 6 ..................................... 2576 C901660015 Number of mobile support extend DTM EGPRS multi TS ability 9 ..................................... 2577 C901660016 Number of mobile support extend DTM EGPRS multi TS ability 10 ................................... 2578 C901660017 Number of mobile support extend DTM EGPRS multi TS ability 11 ................................... 2579 C901660018 Number of mobile of GPRS multi TS ability 1 ..................................................................... 2580 C901660019 Number of mobile of GPRS multi TS ability 2 ..................................................................... 2582 C901660020 Number of mobile of GPRS multi TS ability 3 ..................................................................... 2583 C901660021 Number of mobile of GPRS multi TS ability 4 ..................................................................... 2585 C901660022 Number of mobile of GPRS multi TS ability 5 ..................................................................... 2587 C901660023 Number of mobile of GPRS multi TS ability 6 ..................................................................... 2588 C901660024 Number of mobile of GPRS multi TS ability 7 ..................................................................... 2590 C901660025 Number of mobile of GPRS multi TS ability 8 ..................................................................... 2592 C901660026 Number of mobile of GPRS multi TS ability 9 ..................................................................... 2593
C901660027 Number of mobile of GPRS multi TS ability 10 ................................................................... 2595 C901660028 Number of mobile of GPRS multi TS ability 11 ................................................................... 2597 C901660029 Number of mobile of GPRS multi TS ability 12 ................................................................... 2598 C901660030 Number of mobile of GPRS multi TS ability 30 ................................................................... 2600 C901660031 Number of mobile of GPRS multi TS ability 31 ................................................................... 2602 C901660032 Number of mobile of GPRS multi TS ability 32 ................................................................... 2603 C901660033 Number of mobile of GPRS multi TS ability 33 ................................................................... 2605 C901660034 Number of mobile of GPRS multi TS ability 34 ................................................................... 2607 C901660035 Number of mobile of EGPRS multi TS ability 1 ..................................................................... 2608 C901660036 Number of mobile of EGPRS multi TS ability 2 ..................................................................... 2610 C901660037 Number of mobile of EGPRS multi TS ability 3 ..................................................................... 2612 C901660038 Number of mobile of EGPRS multi TS ability 4 ..................................................................... 2613 C901660039 Number of mobile of EGPRS multi TS ability 5 ..................................................................... 2615 C901660040 Number of mobile of EGPRS multi TS ability 6 ..................................................................... 2617 C901660041 Number of mobile of EGPRS multi TS ability 7 ..................................................................... 2618 C901660042 Number of mobile of EGPRS multi TS ability 8 ..................................................................... 2620 C901660043 Number of mobile of EGPRS multi TS ability 9 ..................................................................... 2622 C901660044 Number of mobile of EGPRS multi TS ability 10 ................................................................... 2623 C901660045 Number of mobile of EGPRS multi TS ability 11 ................................................................... 2625 C901660046 Number of mobile of EGPRS multi TS ability 12 ................................................................... 2627
C901660047 Number of mobile of EGPRS multi TS ability 30 ................................................................... 2628 C901660048 Number of mobile of EGPRS multi TS ability 31 ................................................................... 2630 C901660049 Number of mobile of EGPRS multi TS ability 32 ................................................................... 2632 C901660050 Number of mobile of EGPRS multi TS ability 33 ................................................................... 2633 C901660051 Number of mobile of EGPRS multi TS ability 34 ................................................................... 2635 C901660052 Number of mobile support FR ................... 2637 C901660053 Number of mobile support HR................... 2637 C901660054 Number of mobile support EFR ................. 2638 C901660055 Number of mobile support AMRFR ............. 2639 C901660056 Number of mobile support AMRHR............. 2639 C901660057 Number of mobile support wideband AMROFR ........................................................... 2640 C901660058 Number of mobile support wideband AMRFR ............................................................. 2641 C901660059 Number of mobile support wideband AMROHR .......................................................... 2642 C901660060 Number of mobile support AMROHR .......... 2643 C901660061 Number of mobile support extend uplink TBF ................................................................. 2644 C901660062 Number of mobile support NACC ............... 2645 C901660063 Number of mobile support GPRS extend dynamic allocation ............................................. 2646 C901660064 Number of mobile support EGPRS extend dynamic allocation ............................................. 2647 C901660065 Number of sampling received Classmark3....................................................... 2648 C901660066 Number of sampling received radio access ability .............................................................. 2649 C901660069 Num of MS supporting PS handover........... 2650 C901660070 The Number of MS which Support SAIC ................................................................ 2651 C901660071 The Number of MS which not Support SAIC ................................................................ 2652
C901670001 Duration of Signaling Link Out of Service ............................................................ 2654 C901670002 Number of Signaling Link Out of Service ............................................................ 2655 C901670003 Number of Message Signal Unit Sent ......... 2655 C901670004 Octets of SIF-SIO Sent ............................ 2655 C901670005 Number of Message Signal Unit Received .......................................................... 2656 C901670006 Octets of SIF-SIO Received ...................... 2656 C901670007 Peak Traffic of Signaling Link .................... 2656 C901670008 Peak Traffic Duration of Signaling Link......... 2657 C901670009 Number of Change Over on OMP ............... 2658 C901670010 Number of TFP Received .......................... 2658 C901670011 Rate of Mtp3 Link Occupy......................... 2658 C901670012 Number of SCCP Message Signal Unit Received .......................................................... 2659 C901670013 Number of SCCP Message Signal Unit Sent ................................................................ 2659 C901670014 Number of A2SP Message Signal Unit Received .......................................................... 2659 C901670015 Number of A2SP Message Signal Unit Sent ................................................................ 2660 C901670016 Number of Stm Message Signal Unit Received .......................................................... 2660 C901670017 Number of Stm Message Signal Unit Sent ................................................................ 2660 C901670018 Number of Sltm Message Signal Unit Received .......................................................... 2660 C901670019 Number of Sltm Message Signal Unit Sent ................................................................ 2661 C901670020 Octets of SCCP SIF-SIO Received .............. 2661 C901670021 Octets of SCCP SIF-SIO Sent .................... 2661 C901670022 Octets of MTP2 SIF-SIO Received .............. 2661 C901670023 Octets of MTP2 SIF-SIO Sent .................... 2662 C901670024 Octets of Stm SIF-SIO Received................ 2662 C901670025 Octets of Stm SIF-SIO Sent...................... 2662 C901670026 Octets of Sltm SIF-SIO Received ............... 2662 C901670027 Octets of Sltm SIF-SIO Sent ..................... 2663 C901670028 Number of message discarded due to Congestion ....................................................... 2663
C901670029 Number of restrictions Level 1 .................. 2663 C901670030 Number of restrictions Level 2 .................. 2663 C901670031 Number of restrictions Level 3 .................. 2664 C901670032 Duration of Restrictions Level 1................. 2664 C901670033 Duration of Restrictions Level 2................. 2664 C901670034 Duration of Restrictions Level 3................. 2665 C901670035 Duration of manual prohibition.................. 2665 C901670036 Number of local automatic change back ................................................................ 2665 C901670037 Number of SL restoration ......................... 2665 C901670038 Number of Local management inhibit......... 2666 C901670039 Duration of SL inhibition due to Local management actions.......................................... 2666 C901670040 Number of remote management inhibit .............................................................. 2666 C901670041 Duration of SL inhibition due to remote management actions.......................................... 2667 C901670042 Number of remote processor outage.......... 2667 C901670043 Duration of SL inhibition due to remote processor outage ............................................... 2667 C901670044 Number of sending unaccess messages ......................................................... 2668 C901670045 Number of sending flow-control discarded messages ......................................................... 2668 C901670046 Ten thousand multiple bandwidth occupancy rate on outgoing signaling link............................. 2668 C901670047 Ten thousand multiple bandwidth occupancy rate on incoming signaling link ........................... 2669 C901670048 Link type ............................................... 2670 C901670049 Number of TFA sent ................................ 2670 C901670050 Number of TFA received ........................... 2670 C901670051 Number of TFC sent ................................ 2670 C901670052 Number of TFC received........................... 2671 C901670053 Number of RST sent ................................ 2671 C901670054 Number of RST received .......................... 2671 C901670055 Number of TRA sent ................................ 2671 C901670056 Number of TRA received .......................... 2672 C901670057 Number of UPU sent ................................ 2672 C901670058 Number of UPU received .......................... 2672
C901680026 Number of Heartbeat message received ........................................................... 2683 C901680027 Number of HeartBeat Ack message sent................................................................. 2683 C901680028 Bytes of data message received ................ 2683 C901680029 Bytes of data message transmitted............ 2684 C901680030 Bytes of MGMT message sent ................... 2684 C901680031 Bytes of MGMT message received.............. 2684 C901680032 Counts of discarding messages by Flow Control............................................................. 2685 C901680033 Number of message discard controlled by license ............................................................. 2685 C901680034 Bytes of all message sent......................... 2685 C901680035 Bytes of all message received ................... 2686 C901680036 Number of ERROR message sent............... 2686 C901680037 Number of ERROR message received ......... 2686 C901680038 Number of NOTIFY message sent .............. 2686 C901680039 Number of NOTIFY message received......... 2687
C901690021 Number of LUDT Received ........................ 2695 C901690022 Number of LUDTS Sent ............................ 2696 C901690023 Number of LUDTS Received ...................... 2696 C901690024 Number of DT1 Received.......................... 2696 C901690025 Number of DT1 Sent................................ 2696 C901690026 Number of DT2 Received.......................... 2697 C901690027 Number of DT2 Sent................................ 2697 C901690028 Number of CONNECTREQ Sent.................. 2697 C901690029 Number of CONNECTCON Received............ 2697 C901690030 Number of CONNECTIND Received ............ 2698 C901690031 Number of CONNECTRES Sent .................. 2698 C901690032 Number of DISCONNECTREQ Sent............. 2698 C901690033 Number of DISCONNECTIND received......... 2698 C901690034 Number of CR Sent ................................. 2699 C901690035 Number of CR Received ........................... 2699 C901690036 Number of CC Sent ................................. 2699 C901690037 Number of CC Received ........................... 2699 C901690038 Number of UDT gtt.................................. 2699 C901690039 Number of UDTS gtt ................................ 2700 C901690040 Number of XUDT gtt ................................ 2700 C901690041 Number of XUDTS gtt .............................. 2700 C901690042 Number of LUDT gtt ................................ 2700 C901690043 Number of LUDTS gtt .............................. 2701 C901690044 Number of UDT gtt failure ........................ 2701 C901690045 Number of UDTS gtt failure ...................... 2701 C901690046 Number of XUDT gtt failure ...................... 2701 C901690047 Number of XUDTS gtt failure .................... 2702 C901690048 Number of LUDT gtt failure....................... 2702 C901690049 Number of LUDTS gtt failure..................... 2702 C901690050 Number of CR gtt.................................... 2702 C901690051 Number of CR gtt failure .......................... 2703 C901690052 Number of gtt Count ............................... 2703 C901690053 Number of gtt failure ............................... 2703 C901690054 Number of N_UnitDataReq LongUserData gtt failure .............................................................. 2703 C901690055 Number of UPU received .......................... 2704 C901690056 Number of SSA received .......................... 2704 C901690057 Number of SSA sent ................................ 2704 C901690058 Number of SST received .......................... 2704 C901690059 Number of SST sent ................................ 2705
C901710028 Number of DUPU message sent................. 2717 C901710029 Number of message discard controlled by license ............................................................. 2718 C901710030 Sending invalid stream ID ........................ 2718 C901710031 Sending refuse error, reason is management blocking ........................................................... 2718 C901710032 Sending required ASP ID.......................... 2719 C901710033 Sending invalid ASP ID ............................ 2719 C901710034 Sending invalid parameter value ............... 2719 C901710035 Sending parameter field error ................... 2719 C901710036 Sending unexpected parameter error......... 2720 C901710037 Sending destination status unknown.......... 2720 C901710038 Sending missing parameter error .............. 2720 C901710039 Sending no configured AS for ASP ............. 2720 C901710040 Receiving invalid stream ID ...................... 2721 C901710041 Receiving refuse error, reason is management blocking ........................................ 2721 C901710042 Receiving required ASP ID........................ 2721 C901710043 Receiving invalid ASP ID .......................... 2721 C901710044 Receiving invalid parameter value ............. 2722 C901710045 Receiving parameter field error ................. 2722 C901710046 Receiving unexpected parameter error................................................................ 2722 C901710047 Receiving destination status unknown......... 2722 C901710048 Receiving missing parameter error ............ 2723 C901710049 Receiving no configured AS for ASP ........... 2723
C901770020 Number of Heartbeat Ack Sent ................. 2740 C901770021 Number of Heartbeat Ack Received............ 2740 C901770022 Number of Abort Chunk Sent .................... 2740 C901770023 Number of Abort Chunk Received .............. 2741 C901770024 Number of Shutdown Chunk Sent.............. 2741 C901770025 Number of Shutdown Chunk Received......... 2741 C901770026 Number of Shutdown Ack Chunk Sent......... 2741 C901770027 Number of Shutdown Ack Chunk Received .......................................................... 2742 C901770028 Number of Shutdown Complete Sent ......... 2742 C901770029 Number of Shutdown Complete Received .......................................................... 2742 C901770030 Number of Error Chunk Sent .................... 2742 C901770031 Number of Error Chunk Received .............. 2743 C901770032 Number of ECNE Chunk Sent .................... 2743 C901770033 Number of ECNE Chunk Received .............. 2743 C901770034 Number of CWR Chunk Sent ..................... 2743 C901770035 Number of CWR Chunk Received ............... 2744 C901770036 Number of Error Packet Received .............. 2744 C901770037 Number of OOTB Chunk Received.............. 2744 C901770038 Number of ULP Sent Chunk Request in association alive ................................................ 2744 C901770039 Number of ULP Sent Chunk Request to SCTP OK in association alive ....................................... 2745 C901770040 Number of ULP Sent Chunk Request during a little time ....................................................... 2745 C901770041 Number of ULP Sent Chunk Request to SCTP OK during a little time ........................................ 2745 C901770042 Number of SCTP Sent Chunk Request to ULP ................................................................. 2746 C901770043 Number of Abort Request from ULP ........... 2746 C901770044 Number of Received Abort From Peer ......... 2746 C901770045 Number of Link Break for Retransfer.......... 2746
C901780005 Number of Association Accepted to ULP ................................................................. 2748 C901780006 Number of Association Restarted to ULP ................................................................. 2749 C901780007 Number of Association lost to ULP ............. 2749 C901780008 Number of Destroy instance ..................... 2749 C901780009 Number of Shutdown request from ULP ................................................................. 2749 C901780010 Number of Abort request from ULP ............ 2750
C901790019 VC-4 Remote Background Block Error Ratio (High-order path 2) ........................................... 2759 C901790020 VC-4 Remote Background Block Error Ratio (High-order path 3) ........................................... 2759 C901790021 VC-4 Remote Errored Second Ratio (High-order path 1) ........................................... 2759 C901790022 VC-4 Remote Errored Second Ratio (High-order path 2) ........................................... 2760 C901790023 VC-4 Remote Errored Second Ratio (High-order path 3) ........................................... 2760 C901790024 VC-4 Remote Errored Second (High-order path 1) ............................................................ 2760 C901790025 VC-4 Remote Errored Second (High-order path 2) ............................................................ 2761 C901790026 VC-4 Remote Errored Second (High-order path 3) ............................................................ 2761 C901790027 VC-4 Remote Severely Errored Second (High-order path 1) ........................................... 2761 C901790028 VC-4 Remote Severely Errored Second (High-order path 2) ........................................... 2762 C901790029 VC-4 Remote Severely Errored Second (High-order path 3) ........................................... 2762 C901790030 VC-4 Remote Unavailable Second (High-order path 1) ........................................... 2762 C901790031 VC-4 Remote Unavailable Second (High-order path 2) ........................................... 2763 C901790032 VC-4 Remote Unavailable Second (High-order path 3) ........................................... 2763 C901790033 B1(Regenerator Section) BIP-8 Background Block Error Ratio ............................................... 2763 C901790034 B1(Regenerator Section) BIP-8 Errored Second Ratio..................................................... 2764 C901790035 B1(Regenerator Section) BIP-8 Errored Second............................................................. 2764 C901790036 B1(Regenerator Section) BIP-8 Severely Errored Second ................................................. 2765 C901790037 B1(Regenerator Section) BIP-8 Unavailable Second............................................................. 2765 C901790038 B2(Multiplex Section) BIP-24 Background Block Error Ratio ............................................... 2765
C901790039 B2(Multiplex Section) BIP-24 Errored Second Ratio................................................................ 2766 C901790040 B2(Multiplex Section) BIP-24 Errored Second............................................................. 2766 C901790041 B2(Multiplex Section) BIP-24 Severely Errored Second ................................................. 2767 C901790042 B2(Multiplex Section) BIP-24 Unavailable Second............................................................. 2767 C901790043 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 1) ................................... 2767 C901790044 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 2) ................................... 2768 C901790045 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 3) ................................... 2768 C901790046 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 1) ........................................... 2769 C901790047 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 2) ........................................... 2769 C901790048 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 3) ........................................... 2769 C901790049 B3(VC-4) BIP-8 Errored Second (High-order path 1) ............................................................ 2770 C901790050 B3(VC-4) BIP-8 Errored Second (High-order path 2) ............................................................ 2770 C901790051 B3(VC-4) BIP-8 Errored Second (High-order path 3) ............................................................ 2770 C901790052 B3(VC-4) BIP-8 Severely Errored Second (High-order path 1) ........................................... 2771 C901790053 B3(VC-4) BIP-8 Severely Errored Second (High-order path 2) ........................................... 2771 C901790054 B3(VC-4) BIP-8 Severely Errored Second (High-order path 3) ........................................... 2771 C901790055 B3(VC-4) BIP-8 Unavailable Second (High-order path 1) ........................................... 2772 C901790056 B3(VC-4) BIP-8 Unavailable Second (High-order path 2) ........................................... 2772 C901790057 B3(VC-4) BIP-8 Unavailable Second (High-order path 3) ........................................... 2772 C901790058 LOF second ............................................ 2773
Overview.................................................................. 2775 C901800001 Frame type ............................................ 2776 C901800002 slip Duration ......................................... 2776 C901800003 Near end available Second ....................... 2776 C901800004 Near end unavailable Second.................... 2777 C901800005 Near end Errored Second ......................... 2777 C901800006 Near end Severely Errored Second ............ 2777 C901800007 Near end Background Block Error .............. 2778 C901800008 Frame Alignment Signal error ................... 2778 C901800009 Cyclic Redundancy Check 4 error .............. 2778 C901800010 Bit error rate(PPM) .................................. 2778 C901800011 Near end unavailable Second rate(One ten-thousandth) ................................................ 2779 C901800012 Near end Errored Second rate(One ten-thousandth) ................................................ 2779 C901800013 Near end Severely Errored Second rate(One ten-thousandth) ................................................ 2779 C901800014 Near end Background Block Error rate......... 2779 C901800015 far end available Second .......................... 2780 C901800016 far end unavailable Second ...................... 2780 C901800017 far end Errored Second ............................ 2780 C901800018 far end Severely Errored Second ............... 2781 C901800019 far end Background Block Error................. 2781 C901800020 E-Bit ERROR........................................... 2781 C901800021 far end unavailable Second rate(One ten-thousandth) ................................................ 2781 C901800022 far end Errored Second rate(One ten-thousandth) ................................................ 2782 C901800023 far end Severely Errored Second rate(One ten-thousandth) ................................................ 2782 C901800024 far end Background Block Error rate(One ten-thousandth) ................................................ 2782
C901810007 number of Near end Background Block Error................................................................ 2785 C901810008 number of Frame Alignment Signal error................................................................ 2786 C901810009 number of Cyclic Redundancy Check 6 error................................................................ 2786 C901810010 Bit error rate (PPM) ................................. 2786 C901810011 Near end unavailable Second rate(One ten-thousandth) ................................................ 2786 C901810012 Near end Errored Second rate (One ten-thousandth) ................................................ 2787 C901810013 Near end Severely Errored Second rate(One ten-thousandth) ............................................... 2787 C901810014 Near end Background Block Error rate......... 2787
C901830002 Total Num of DL AFS10.2k frame............... 2797 C901830003 Total Num of DL AFS7.95k frame............... 2797 C901830004 Total Num of DL AFS7.40k frame............... 2797 C901830005 Total Num of DL AFS6.70k frame............... 2798 C901830006 Total Num of DL AFS5.90k frame............... 2798 C901830007 Total Num of DL AFS5.15k frame............... 2799 C901830008 Total Num of DL AFS4.75k frame............... 2799 C901830009 Total Num of DL AHS7.95k frame .............. 2799 C901830010 Total Num of DL AHS7.40k frame .............. 2800 C901830011 Total Num of DL AHS6.70k frame .............. 2800 C901830012 Total Num of DL AHS5.90k frame .............. 2801 C901830013 Total Num of DL AHS5.15k frame .............. 2801 C901830014 Total Num of DL AHS4.75k frame .............. 2801 C901830015 Total Num of UL AFS12.2k frame............... 2802 C901830016 Total Num of UL AFS10.2k frame............... 2802 C901830017 Total Num of UL AFS7.95k frame............... 2803 C901830018 Total Num of UL AFS7.40k frame............... 2803 C901830019 Total Num of UL AFS6.70k frame............... 2803 C901830020 Total Num of UL AFS5.90k frame............... 2804 C901830021 Total Num of UL AFS5.15k frame............... 2804 C901830022 Total Num of UL AFS4.75k frame............... 2805 C901830023 Total Num of UL AHS7.95k frame .............. 2805 C901830024 Total Num of UL AHS7.40k frame .............. 2805 C901830025 Total Num of UL AHS6.70k frame .............. 2806 C901830026 Total Num of UL AHS5.90k frame .............. 2806 C901830027 Total Num of UL AHS5.15k frame .............. 2807 C901830028 Total Num of UL AHS4.75k frame .............. 2807
C901850012 receive broadcast packets high 32bits......... 2815 C901850013 receive multicast packets flag ................... 2815 C901850014 receive multicast packets low 32bits .......... 2816 C901850015 receive multicast packets high 32bits......... 2816 C901850016 receive CRC or align error packets flag.................................................................. 2816 C901850017 receive CRC or align error packets low 32bits .............................................................. 2817 C901850018 receive CRC or align error packets high 32bits .............................................................. 2817 C901850019 receive small than 64 bytes packets flag.................................................................. 2817 C901850020 receive small than 64 bytes packets low 32bits .............................................................. 2818 C901850021 receive small than 64 bytes packets high 32bits .............................................................. 2818 C901850022 receive large than 1518 bytes packets flag.................................................................. 2818 C901850023 receive large than 1518 bytes packets low 32bits .............................................................. 2819 C901850024 receive large than 1518 bytes packets high 32bits .............................................................. 2819 C901850025 The flag of received fragment packets......... 2819 C901850026 Number of fragment packets received (low 32 bit) ............................................................. 2820 C901850027 Number of received fragment packets (high 32 bit) ............................................................. 2820 C901850028 receive Jabber packets flag ...................... 2820 C901850029 receive Jabber packets low 32bits ............. 2821 C901850030 receive Jabber packets high 32bits ............ 2821 C901850031 receive Collision count flag ....................... 2821 C901850032 receive Collision count low 32bits .............. 2822 C901850033 receive Collision count high 32bits............. 2822 C901850034 receive 64 bytes packets flag.................... 2822 C901850035 receive 64 bytes packets low 32bits........... 2823 C901850036 receive 64 bytes packets high 32bits ......... 2823 C901850037 receive 65 to 127 bytes packets flag.......... 2823 C901850038 receive 65 to 127 bytes packets low 32bits .............................................................. 2824
C901850039 receive 65 to 127 bytes packets high 32bits .............................................................. 2824 C901850040 receive 128 to 255 bytes packets flag......... 2824 C901850041 receive 128 to 255 bytes packets low 32bits .............................................................. 2825 C901850042 receive 128 to 255 bytes packets high 32bits .............................................................. 2825 C901850043 receive 256 to 511 bytes packets flag......... 2825 C901850044 receive 256 to 511 bytes packets low 32bits .............................................................. 2826 C901850045 receive 256 to 511 bytes packets high 32bits .............................................................. 2826 C901850046 receive 512 to 1023 bytes packets flag.................................................................. 2826 C901850047 receive 512 to 1023 bytes packets low 32bits .............................................................. 2827 C901850048 receive 512 to 1023 bytes packets high 32bits .............................................................. 2827 C901850049 receive 1024 to 1518 bytes packets flag.................................................................. 2827 C901850050 receive 1024 to 1518 bytes packets low 32bits .............................................................. 2828 C901850051 receive 1024 to 1518 bytes packets high 32bits .............................................................. 2828 C901850052 send discard packets flag ......................... 2828 C901850053 send discard packets low 32bits ................ 2829 C901850054 send discard packets high 32bits............... 2829 C901850055 send packet bytes flag ............................. 2829 C901850056 send packet bytes low 32bits .................... 2830 C901850057 send packets bytes high 32bits ................. 2830 C901850058 send packets flag .................................... 2830 C901850059 send packets low 32bits ........................... 2831 C901850060 send packets high 32bits.......................... 2831 C901850061 send broadcast packets flag ..................... 2831 C901850062 send broadcast packets low 32bits ............ 2832 C901850063 send broadcast packets high 32bits ........... 2832 C901850064 send multicast packets flag ...................... 2832 C901850065 send multicast packets low 32bits ............. 2833 C901850066 send multicast packets high 32bits ............ 2833 C901850067 send CRC or Align error packets flag.......... 2833
C901850068 send CRC or Align error packets low 32bits .............................................................. 2834 C901850069 send CRC or Align error packets high 32bits .............................................................. 2834 C901850070 send small than 64 bytes packets flag......... 2834 C901850071 send small than 64 bytes packets low 32bits .............................................................. 2835 C901850072 send small than 64 bytes packets high 32bits .............................................................. 2835 C901850073 send large than 1518 bytes packets flag.................................................................. 2835 C901850074 send large than 1518 bytes packets low 32bits .............................................................. 2836 C901850075 send large than 1518 bytes packets high 32bits .............................................................. 2836 C901850076 The flag of sent fragment packets ............. 2836 C901850077 Number of sent fragment packets (low 32 bit) .................................................................. 2837 C901850078 Number of sent fragment packets (high 32 bit) .................................................................. 2837 C901850079 send Jabber packets flag.......................... 2837 C901850080 send Jabber packets low 32bits................. 2838 C901850081 send Jabber packets high 32bits ............... 2838 C901850082 send Collision count flag .......................... 2838 C901850083 send Collision count low 32bits ................. 2839 C901850084 send Collision count high 32bits ................ 2839 C901850085 send 64 bytes packets flag ....................... 2839 C901850086 send 64 bytes packets low 32bits .............. 2840 C901850087 send 64 bytes packets high 32bits............. 2840 C901850088 send 65 to 127 bytes packets flag ............. 2840 C901850089 send 65 to 127 bytes packets low 32bits .............................................................. 2841 C901850090 send 65 to 127 bytes packets high 32bits .............................................................. 2841 C901850091 send 128 to 255 bytes packets flag ........... 2841 C901850092 send 128 to 255 bytes packets low 32bits .............................................................. 2842 C901850093 send 128 to 255 bytes packets high 32bits .............................................................. 2842 C901850094 send 256 to 511 bytes packets flag ........... 2842
C901850095 send 256 to 511 bytes packets low 32bits .............................................................. 2843 C901850096 send 256 to 511 bytes packets high 32bits .............................................................. 2843 C901850097 send 512 to 1023 bytes packets flag.......... 2843 C901850098 send 512 to 1023 bytes packets low 32bits .............................................................. 2844 C901850099 send 512 to 1023 bytes packets high 32bits .............................................................. 2844 C901850100 send 1024 to 1518 bytes packets flag......... 2844 C901850101 send 1024 to 1518 bytes packets low 32bits .............................................................. 2845 C901850102 send 1024 to 1518 bytes packets high 32bits .............................................................. 2845 C901850103 Logic port type ....................................... 2845
C901880012 Number of handover attempts due to a good standard level in FDD adjacent cell ...................... 2855 C901880013 Number of handover attempts due to a good standard level in TDD adjacent cell ...................... 2856 C901880014 Number of handover attempts due to PCCN ............................................................... 2857
C901890017 Number of handover in attempts............... 2874 C901890018 Number of handover in executions ............ 2875 C901890019 Number of successful handover in ............. 2875 C901890020 Number of Intra-cell handover attempts .......................................................... 2876 C901890021 Number of Intra-Cell handover executions ........................................................ 2877 C901890022 Number of successful Intra-cell handovers ........................................................ 2877 C901890023 Number of invalid Intra-cell handovers ............................................................. 2877 C901890024 Number of 2G to FDD handover attempts .......................................................... 2878 C901890025 Number of 2G to FDD handover executions ........................................................ 2878 C901890026 Number of successful 2G to FDD handovers ........................................................ 2879 C901890027 Number of 2G to TDD handover attempts .......................................................... 2880 C901890028 Number of 2G to TDD handover executions ........................................................ 2880 C901890029 Number of successful 2G to TDD handovers ........................................................ 2881 C901890030 Number of 3G to 2G handover attempts .......................................................... 2882 C901890031 Number of 3G to 2G handover executions ........................................................ 2882 C901890032 Number of successful 3G to 2G handovers ........................................................ 2883 C901890033 Number of T12 expiry.............................. 2884 C901890034 Number of PCCF received......................... 2884 C901890035 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause Create PFC Failure ............................................................. 2885 C901890036 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause PS Handover Target not allowed ...................................................... 2886 C901890037 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause PS Handover not Supported in Target BSS or Target System ............ 2887
C901890038 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause other reasons ......... 2887 C901890039 Number of failure in optimised handover due to failure alloc resource ..................................... 2888 C901890040 Number of failure in optimised handover due to PS handover not supported in target cell ........... 2889
C901920001 the times of loss of TRAU frame synchronization in BIPB ...................................... 2917
C901940006 The count of PS timeslot allocation failure caused by power shortage .................................. 2933
C901950014 Number of successful handovers from selected cell to the adjacent cell due to PBGT......... 2952 C901950015 Number of handover attempts from selected cell to the adjacent cell due to large TA ................ 2953 C901950016 Number of successful handover from selected cell to the adjacent cell due to large TA ................................................................... 2954 C901950017 Number of handover attempts from selected cell to the adjacent cell due to high traffic ............. 2956 C901950018 Number of successful handover from selected cell to the adjacent cell due to high traffic............................................................... 2957
C902000014 Number of Error Indications due to unsolicited message on TCH/H ............................ 2969 C902000015 Number of Error Indications due to unsolicited DM response on TCH/H ....................... 2970 C902000016 Number of Error Indications due to sequence error on TCH/H ................................................. 2971 C902000017 Number of Error Indications due to frame content error on TCH/H ...................................... 2971 C902000018 Number of Error Indications due to SABM command on TCH/H........................................... 2972 C902000019 Number of Release Indications due to T200 expired on SDCCH ............................................. 2973 C902000020 Number of Release Indications due to unsolicited DM response on SDCCH ...................... 2973 C902000021 Number of Release Indications due to sequence error on SDCCH................................... 2974 C902000022 Number of Release Indications due to T200 expired on TCH/F (signaling) ............................... 2975 C902000023 Number of Release Indications due to unsolicited DM response on TCH/F (signaling)......... 2976 C902000024 Number of Release Indications due to sequence error on TCH/F (signaling) .................... 2976 C902000025 Number of Release Indications due to T200 expired on TCH/F (speech).................................. 2977 C902000026 Number of Release Indications due to unsolicited DM response on TCH/F (speech) .......... 2978 C902000027 Number of Release Indications due to sequence error on TCH/F (speech) ....................... 2979 C902000028 Number of Release Indications due to T200 expired on TCH/F (data) ..................................... 2979 C902000029 Number of Release Indications due to unsolicited DM response on TCH/F (data).............. 2980 C902000030 Number of Release Indications due to sequence error on TCH/F (data) .......................... 2981 C902000031 Number of Release Indications due to T200 expired on TCH/H (signaling) .............................. 2982 C902000032 Number of Release Indications due to unsolicited DM response on TCH/H (signaling)......... 2982 C902000033 Number of Release Indications due to sequence error on TCH/H (signaling) .................... 2983
C902000034 Number of Release Indications due to T200 expired on TCH/H (speech) ................................. 2984 C902000035 Number of Release Indications due to unsolicited DM response on TCH/H (speech).......... 2985 C902000036 Number of Error Indications due to sequence error on TCH/H (speech) .................................... 2985 C902000037 Number of Release Indications due to T200 expired on TCH/H (data)..................................... 2986 C902000038 Number of Release Indications due to unsolicited DM response on TCH/H (data) ............. 2987 C902000039 Number of Release Indications due to sequence error on TCH/H (data) .......................... 2988 C902000040 Number of Release Indications without Error Ind on SDCCH................................................... 2988 C902000041 Number of Release Indications without Error Ind on TCH/F (signaling) .................................... 2989 C902000042 Number of Release Indications without Error Ind on TCH/F (speech) ....................................... 2989 C902000043 Number of Release Indications without Error Ind on TCH/F (data)........................................... 2990 C902000044 Number of Release Indications without Error Ind on TCH/H (signaling) .................................... 2990 C902000045 Number of Release Indications without Error Ind on TCH/H (speech)....................................... 2990 C902000046 Number of Release Indications without Error Ind on TCH/H (data) .......................................... 2991
C902010006 Number of that Sum of PS Downlink BandWidth Measured and Current BandWidth Allocated More than C1 ...................................... 2999 C902010007 Number of CS Uplink BandWidth Allocated More than Overbooking ..................................... 3000 C902010008 Number of CS Uplink BandWidth Measured More than C2 .................................................... 3000 C902010009 Number of that Sum of CS Uplink BandWidth Measured and Current BandWidth Allocated More than C1............................................................ 3001 C902010010 Number of CS Downlink BandWidth Allocated More than Overbooking ...................................... 3002 C902010011 Number of CS Downlink BandWidth Measured More than C2...................................... 3003 C902010012 Number of that Sum of CS Downlink BandWidth Measured and Current BandWidth Allocated More than C1 ...................................... 3004
C902030008 Number of VGCS Inter-BSC incoming handover attempts of Talker................................ 3020 C902030009 Number of VGCS Inter-BSC incoming handover execution of Talker............................... 3021 C902030010 Number of VGCS Inter-BSC incoming handover success of Talker ................................. 3021 C902030011 Number of VGCS channel request attempts for NOTIFICATION RESPONSE of Listener .............. 3022 C902030012 Number of VGCS channel request success for NOTIFICATION RESPONSE of Listener .............. 3023 C902030013 Number of VGCS channel request failure for NOTIFICATION RESPONSE of Listener................... 3024 C902030014 Number of VGCS channel release for Listener detection .......................................................... 3025 C902030015 Number of Talker drops due to radio link failure .............................................................. 3026 C902030016 Number of Talker quit .............................. 3027 C902030017 Number of attempts for Listener uplink request ............................................................ 3027 C902030018 Number of VGCS Intra-BSC Inter-cell outgoing handover attempts of Talker................... 3028 C902030019 Number of VGCS Intra-BSC Inter-cell outgoing handover execution of Talker.................. 3029 C902030020 Number of VGCS Intra-BSC Inter-cell outgoing handover success of Talker .................... 3030 C902030021 Number of VGCS Intra-BSC Inter-cell outgoing handover failure of Talker ...................... 3031 C902030022 Number of VGCS Intra-BSC Inter-cell incoming handover attempts of Talker .................. 3032 C902030023 Number of VGCS Intra-BSC Inter-cell incoming handover execution of Talker ................. 3033 C902030024 Number of VGCS Intra-BSC Inter-cell incoming handover success of Talker .................... 3034 C902030025 Number of NCH overflow of VGCS ............. 3034 C902030026 Number of successes for Listener uplink request ............................................................ 3035 C902030027 Number of failures for Listener uplink request ............................................................ 3036
C902040001 Number of VBS assignment attempts......... 3038 C902040002 Number of VBS assignment success .......... 3039 C902040003 Number of VBS assignment failure ............ 3039 C902040004 Number of VBS Inter-BSC outgoing handover attempts of Talker................................ 3040 C902040005 Number of VBS Inter-BSC outgoing handover execution of Talker............................... 3041 C902040006 Number of VBS Inter-BSC outgoing handover success of Talker ................................. 3042 C902040007 Number of VBS Inter-BSC outgoing handover failure of Talker ................................... 3043 C902040008 Number of VBS Inter-BSC incoming handover attempts of Talker................................ 3044 C902040009 Number of VBS Inter-BSC incoming handover execution of Talker............................... 3045 C902040010 Number of VBS Inter-BSC incoming handover success of Talker ................................. 3046 C902040011 Number of VBS channel request attempts for NOTIFICATION RESPONSE of Listener .............. 3046 C902040012 Number of VBS channel request success for NOTIFICATION RESPONSE of Listener................... 3047 C902040013 Number of VBS channel request failure for NOTIFICATION RESPONSE of Listener................... 3048 C902040014 Number of VBS channel release for Listener detection .......................................................... 3049 C902040015 Number of VBS Intra-BSC Inter-cell outgoing handover attempts of Talker................................ 3050 C902040016 Number of VBS Intra-BSC Inter-cell outgoing handover execution of Talker............................... 3051 C902040017 Number of VBS Intra-BSC Inter-cell outgoing handover success of Talker ................................. 3052 C902040018 Number of VBS Intra-BSC Inter-cell outgoing handover failure of Talker ................................... 3053 C902040019 Number of VBS Intra-BSC Inter-cell incoming handover attempts of Talker .................. 3054 C902040020 Number of VBS Intra-BSC Inter-cell incoming handover execution of Talker ................. 3055 C902040021 Number of VBS Intra-BSC Inter-cell incoming handover success of Talker .................... 3056 C902040022 Number of NCH overflow of VBS ............... 3056
C902040023 Number of Talker drops due to radio link failure .............................................................. 3057
C902050020 Number of queuing execution due to inter-BSC incoming handover of Talker ................. 3078 C902050021 Number of queuing attempts due to Intra-BSC Inter-cell handover of Talker................. 3079 C902050022 Number of queuing execution due to Intra-BSC Inter-cell handover of Talker................. 3080
C902120012 Number of BSC-controlled incoming handover attempts due to forced release (On SDCCH) ........................................................... 3096 C902120013 Number of BSC-controlled incoming handover due to forced release (On SDCCH) ......... 3097 C902120014 Number of BSC-controlled incoming handover attempts due to queue (On SDCCH)......... 3098 C902120015 Number of BSC-controlled incoming handover due to queue (On SDCCH) .................... 3099 C902120016 Number of BSC-controlled incoming handover attempts due to forced handover (On SDCCH) ........................................................... 3100 C902120017 Number of BSC-controlled incoming handover due to forced handover (On SDCCH) ........................................................... 3101 C902120018 Number of BSC-controlled inter-cell incoming handover success (On SDCCH)............... 3102 C902120019 BSC-controlled incoming handover time due to queue (On SDCCH) ........................................ 3103 C902120020 Number of BSC-controlled incoming handover queue (On SDCCH) .............................. 3104 C902120021 BSC-controlled incoming handover success time due to queue (On SDCCH) ........................... 3106 C902120022 Number of BSC-controlled incoming handover success due to queue (On SDCCH)......... 3107 C902120023 Number of MSC-controlled incoming handover attempts (On SDCCH) .......................... 3108 C902120024 Number of incoming handover failure due to unavailable radio resource (On SDCCH) ................ 3108 C902120025 Number of incoming handover failure due to other factors (On SDCCH)................................... 3109 C902120026 Number of MSC-controlled incoming handover (On SDCCH) ....................................... 3110 C902120027 Number of MSC-controlled incoming handover attempts due to forced release (On SDCCH) ........................................................... 3111 C902120028 Number of MSC-controlled incoming handover due to forced release (On SDCCH) ......... 3112 C902120029 Number of MSC-controlled incoming handover attempts due to queue (On SDCCH)......... 3113
C902120030 Number of MSC-controlled incoming handover due to queue (On SDCCH) .................... 3114 C902120031 Number of MSC-controlled incoming handover attempts due to forced handover (On SDCCH) ........................................................... 3115 C902120032 Number of MSC-controlled incoming handover due to forced handover (On SDCCH) ........................................................... 3116 C902120033 Number of MSC-controlled incoming handover success (On SDCCH) ............................ 3117 C902120034 MSC-controlled incoming handover time due to queue (On SDCCH) ........................................ 3117 C902120035 Number of MSC-controlled incoming handover queue (On SDCCH) .............................. 3119 C902120036 MSC-controlled incoming handover success time due to queue (On SDCCH) ........................... 3121 C902120037 Number of MSC-controlled incoming handover success due to queue (On SDCCH)......... 3122
C902130010 The Failure Number of Establishing Local Switch (Inside Site Group/No answer from Site) ................................................................ 3130 C902130011 The Failure Number of Establishing Local Switch (Inside Site/Other Reason Fail).................. 3130 C902130012 The Failure Number of Establishing Local Switch (Inside Site Group/Other Reason Fail)......... 3131 C902130013 The Failure Number of Returning Normal Call (Abis unavailable).............................................. 3131 C902130014 The Failure Number of Returning Normal Call (Connect Fail) ................................................... 3132 C902130015 The Failure Number of Returning Normal Call (Ater unavailable) .............................................. 3133
C902430003 Number of handover attempts from selected cell to the adjacent 3G cell.................................. 3157 C902430004 Number of handovers from selected cell to the adjacent 3G cell ........................................... 3157 C902430005 Number of successful handovers from selected cell to the adjacent 3G cell ..................... 3158 C902430006 Number of handover attempts from selected cell to the adjacent 3G cell due to measurement result............................................................... 3158 C902430007 Number of handovers from selected cell to the adjacent 3G cell due to measurement result............................................................... 3159 C902430008 Number of successful handovers from selected cell to the adjacent 3G cell due to measurement result........................................... 3159 C902430009 Number of handover attempts from selected cell to the adjacent 3G cell due to traffic ............... 3160 C902430010 Number of handovers from selected cell to the adjacent 3G cell due to traffic ........................ 3160 C902430011 Number of successful handovers from selected cell to the adjacent 3G cell due to traffic............................................................... 3161 C902430012 Number of handover attempts from selected cell to the adjacent 3G cell due to saving call......... 3161 C902430013 Number of handovers from selected cell to the adjacent 3G cell due to saving call.................. 3162 C902430014 Number of successful handovers from selected cell to the adjacent 3G cell due to saving call .................................................................. 3162
Corresponding Relationship between Basic Measurement Counters and General Measurement Counters ............................... 3163 Glossary ...................................................... 3181
This manual explains the description, usage, and measurement point of each performance counter in ZXG10 iBSC Subsystem. It helps user analyze and locate faults through querying counters. System Engineer Testing Engineer Planning Engineer
Intended Audience
Section 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 Chapter 19, Sub Cell Statistics Chapter 20, MS TA Measurement Chapter 21, 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 Chapter 28, TRX Measurement
Summary 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. Introduces the detailed information about counters related to sub cell statistics. Introduces the detailed information about counters related to MS TA measurement. Introduces the detailed information about counters related to SAPI3 measurement. 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. Introduces the detailed information about counters related to TRX measurement.
ii
Section Chapter 29, Gb Interface Message Statistics Chapter 30, Timeslot Measurement Chapter 31, SDCCH Measurement Chapter 32, TCH/F Measurement Chapter 33, 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 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
Summary Introduces the detailed information about counters related to Gb interface message statistics. Introduces the detailed information about counters related to timeslot measurement. Introduces the detailed information about counters related to SDCCH measurement. Introduces the detailed information about counters related to TCH/F measurement. Introduces the detailed information about counters related to TCH/H 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. 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.
iii
Section Chapter 46, MTP2 Signaling Link Measurement Chapter 47, CPU/MEM Measurement Chapter 48, SCTP AS Measurement Chapter 49, IP Port Performance Statistics Chapter 50, GTRUNK Resource Statistics Chapter 51, Other Process Statistics Chapter 52, FR Carried Links Statistics Chapter 53, OMP PS Service Statistics Chapter 54, SNS on OMP Statistics Chapter 55, IPGB StrongARM NSVC Statistics Chapter 56, IPGB StrongARM Gb Statistics Chapter 57, 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
Summary Introduces the detailed information about counters related to MTP2 signaling link measurement. Introduces the detailed information about counters related to CPU/MEM measurement. Introduces the detailed information about counters related to SCTP AS measurement. 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. 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. 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. 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.
iv
Section Chapter 63, LAPD Measurement Chapter 64, LCS Measurement 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 LAPD measurement. Introduces the detailed information about counters related to LCS measurement. 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.
Section Chapter 78, M3UA AS Performance Statistics Chapter 79, Timer Statistics Chapter 80, Scheduling Performance Statistics Chapter 81, UB Memory Performance Statistics Chapter 82, Hardware and FLASH Performance Statistics 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 Chapter 90, UMAC Measurement Chapter 91, PS Handover Cause Measurement Chapter 92, PS General Handover Measurement Chapter 93, IURG Measurement Chapter 94, RTCP Measurement
Summary Introduces the detailed information about counters related to M3UA AS performance statistics. Introduces the detailed information about counters related to timer 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. 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. Introduces the detailed information about counters related to UMAC measurement. 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. Introduces the detailed information about counters related to RTCP measurement.
vi
Section Chapter 95, DSP Measurement Chapter 95, Access Control Measurement Chapter 97, Power Control Measurement Chapter 98, PS Adjacent Cell Handover Measurement Chapter 99, LAPDm Measurement Chapter 100, Access Control Detailed Cause Measurement Chapter 101, BSC Group Call Setup Measurement Chapter 102, VGCS Measurement Chapter 103, VBS Measurement Chapter 104, eMLPP Measurement Chapter 105, Flow Control Measurement Chapter 106, SDCCH General Handover Measurement Chapter 107, Local Switch Measurement Chapter 108, Adjacent 3G Cell Handover Measurement
Summary Introduces the detailed information about counters related to DSP measurement. Introduces the detailed information about counters related to access control measurement. Introduces the detailed information about counters related to power control measurement. Introduces the detailed information about counters related to PS adjacent cell handover measurement. Introduces the detailed information about counters related to LAPDm 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. Introduces the detailed information about counters related to VBS measurement. Introduces the detailed information about counters related to eMLPP measurement. 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. Introduces the detailed information about counters related to Adjacent 3G Cell Handover Measurement.
vii
viii
Chapter
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.
This counter counts the total number of bytes received from all BRCHs on FR sub-layer. This counter is used to find out the bytes received from BRCH and to observe BSC load status. FR accumulates all the bytes received from Gb interface BRCH. Byte
This counter counts the total number of bytes sent from all BRCHs on FR sub-layer.
This counter is used to find out the bytes sent from BRCH and to observe BSC load status. FR accumulates all the bytes sent from Gb interface BRCH. Byte
Chapter
C900040022 Number of GPRS UL TBF forcing release by control plane .........................................................................25 C900040023 Number of GPRS UL TBF release due to instance suspension .......................................................................26 C900040024 Number of GPRS UL TBF release due to inner abnormal .........................................................................26 C900040025 Number of GPRS UL signaling TBF establishment ...............................................................................27 C900040026 Number of GPRS UL data TBF establishment ...............................................................................29 C900040027 Number of EGPRS UL TBF establishment success on PACCH.........................................................................30 C900040028 Number of EGPRS UL TBF release due to N3101 overflow ...........................................................................31 C900040029 Number of EGPRS UL TBF release due to N3103 overflow ...........................................................................31 C900040030 Number of EGPRS UL TBF forcing release by control plane .........................................................................32 C900040031 Number of EGPRS UL TBF release due to instance suspension .............................................................32 C900040032 Number of EGPRS UL TBF release due to inner abnormal .........................................................................33 C900040033 Number of EGPRS UL signaling TBF establishment ...............................................................................33 C900040034 Number of EGPRS UL data TBF establishment ...............................................................................33 C900040035 Average number of GPRS UL TBF simultaneous establishment ..................................................................34 C900040036 Average number of EGPRS UL TBF simultaneous establishment ..................................................................34 C900040037 Number of GPRS UL signaling TBF release due to N3101 overflow .............................................................35 C900040038 Number of GPRS UL signaling TBF release due to N3103 overflow .............................................................35 C900040039 Number of GPRS UL signaling TBF forcing release by control plane ........................................................36 C900040040 Number of GPRS UL signaling TBF release due to instance suspension .......................................................36 C900040041 Number of GPRS UL signaling TBF release due to inner abnormal..............................................................36 C900040042 Number of EGPRS UL signaling TBF release due to N3101 overflow .............................................................37 C900040043 Number of EGPRS UL signaling TBF release due to N3103 overflow .............................................................37 C900040044 Number of EGPRS UL signaling TBF forcing release by control plane ........................................................38 C900040045 Number of EGPRS UL signaling TBF release due to instance suspension .......................................................38 C900040046 Number of EGPRS UL signaling TBF release due to inner abnormal..............................................................38 C900040047 Number of EGPRS DL LLC frames ......................39 C900040048 Number of discarded EGPRS DL LLC frames due to buffer overflow ..............................................................39 C900040049 Number of discarded EGPRS DL LLC frames due to life time expiration .........................................................40 C900040050 Number of discarded EGPRS DL LLC frames due to other reasons ...............................................................41 C900040051 Number of DL signaling LLC frames ...................41 C900040052 Number of discarded EGPRS DL signaling LLC frames due to buffer overflow .............................................42
C900040053 Number of discarded EGPRS DL signaling LLC frames due to life time expiration ........................................43 C900040054 Number of discarded EGPRS DL signaling LLC frames due to other reasons ...............................................43 C900040055 Number of data blocks transmitted according to given Abis bandwidth .........................................................44 C900040056 Bytes of effective upper layer protocol data sent on DL PDCH .....................................................................44 C900040057 Bytes of effective upper layer protocol data received on UL PDCH ...........................................................45 C900040058 Bytes of LLC frame on GPRS UL data TBF ..........46 C900040059 Duration of GPRS UL data TBF ..........................46 C900040060 Bytes of LLC frame on GPRS DL data TBF ..........48 C900040061 Duration of GPRS DL data TBF ..........................48 C900040062 Number of effective data blocks received on GPRS UL TBF ....................................................................49 C900040063 Number of NACK blocks received on GPRS UL TBF ................................................................................50 C900040064 Number of effective data blocks sent on GPRS DL TBF ............................................................................51 C900040065 Number of NACK blocks sent on GPRS DL TBF ......................................................................................51 C900040066 Bytes of LLC frame on EGPRS UL data TBF .........52 C900040067 Duration of EGPRS UL data TBF ........................53 C900040068 Bytes of LLC frame on EGPRS DL data TBF .........54 C900040069 Duration of EGPRS DL data TBF ........................55 C900040070 Number of effective data blocks received on EGPRS UL TBF ......................................................................56 C900040071 Number of NACK blocks received on EGPRS UL TBF ................................................................................57 C900040072 Number of effective data blocks sent on EGPRS DL TBF ............................................................................58 C900040073 Number of NACK blocks sent on EGPRS DL TBF ......................................................................................58 C900040074 Number of GPRS DL LLC frames........................59 C900040075 Number of discarded GPRS DL LLC frames due to buffer overflow ..............................................................60 C900040076 Number of discarded GPRS DL LLC frames due to life time expiration .........................................................61 C900040077 Number of discarded GPRS DL LLC frames due to other reasons ................................................................61 C900040078 Number of DL dummy control blocks on PACCH .............................................................................62 C900040079 Number of UL dummy control blocks on PACCH .............................................................................63 C900040080 Number of DL RLC blocks on PACCH (excluding dummy block)...................................................................63 C900040081 Number of DL RLC pending blocks in CS1 on PDTCH .............................................................................64 C900040082 Number of DL RLC pending blocks in CS2 on PDTCH .............................................................................65 C900040083 Number of DL RLC pending blocks in CS3 on PDTCH .............................................................................65 C900040084 Number of DL RLC pending blocks in CS4 on PDTCH .............................................................................66 C900040085 Number of DL RLC NACK blocks in CS1 on PDTCH .............................................................................67 C900040086 Number of DL RLC NACK blocks in CS2 on PDTCH .............................................................................67
C900040087 Number of DL RLC NACK blocks in CS3 on PDTCH .............................................................................68 C900040088 Number of DL RLC NACK blocks in CS4 on PDTCH .............................................................................69 C900040089 Number of DL RLC new blocks in CS1 on PDTCH .............................................................................70 C900040090 Number of DL RLC new blocks in CS2 on PDTCH .............................................................................70 C900040091 Number of DL RLC new blocks in CS3 on PDTCH .............................................................................71 C900040092 Number of DL RLC new blocks in CS4 on PDTCH .............................................................................72 C900040093 Number of UL RLC blocks excluding dummy blocks on PACCH ...............................................................72 C900040094 Number of UL RLC pending blocks in CS1 on PDTCH .............................................................................73 C900040095 Number of UL RLC pending blocks in CS2 on PDTCH .............................................................................74 C900040096 Number of UL RLC pending blocks in CS3 on PDTCH .............................................................................74 C900040097 Number of UL RLC pending blocks in CS4 on PDTCH .............................................................................75 C900040098 Number of UL RLC NACK blocks in CS1 on PDTCH .............................................................................76 C900040099 Number of UL RLC NACK blocks in CS2 on PDTCH .............................................................................76 C900040100 Number of UL RLC NACK blocks in CS3 on PDTCH .............................................................................77 C900040101 Number of UL RLC NACK blocks in CS4 on PDTCH .............................................................................78 C900040102 Number of UL RLC new blocks in CS1 on PDTCH .............................................................................79 C900040103 Number of UL RLC new blocks in CS2 on PDTCH .............................................................................79 C900040104 Number of UL RLC new blocks in CS3 on PDTCH .............................................................................80 C900040105 Number of UL RLC new blocks in CS4 on PDTCH .............................................................................81 C900040106 Number of UL data blocks received on PDTCH .............................................................................81 C900040107 Number of DL data blocks sent on PDTCH...........82 C900040108 Number of GPRS DL TBF establishment requests ......................................................................................82 C900040109 Number of GPRS DL TBF establishment failure due to database allocation failure ........................................83 C900040110 Number of GPRS DL TBF resource reallocation requests due to UL TBF establishment .................................84 C900040111 Number of GPRS DL TBF resource reallocation failure of channel allocation due to UL TBF establishment .........85 C900040112 Number of GPRS DL TBF resource reallocation requests due to LLC transmission.........................................86 C900040113 Number of GPRS DL TBF resource reallocation failure of channel allocation due to LLC transmission .............86 C900040114 Number of EGPRS DL TBF establishment requests .............................................................................87 C900040115 Number of EGPRS DL TBF establishment failure due to database allocation failure ........................................88 C900040116 Number of EGPRS DL TBF resource reallocation requests due to UL TBF establishment .................................89
C900040117 Number of EGPRS DL TBF resource reallocation failure of channel allocation due to UL TBF establishment .........90 C900040118 Number of EGPRS DL TBF resource reallocation requests due to LLC transmission.........................................91 C900040119 Number of EGPRS DL TBF resource reallocation failure of channel allocation due to LLC transmission .............91 C900040120 Number of GPRS UL TBF establishment requests ......................................................................................92 C900040121 Number of GPRS UL TBF establishment failure due to database allocation failure ........................................93 C900040122 Number of GPRS UL TBF resource reallocation requests due to DL TBF establishment ..................................94 C900040123 Number of GPRS UL TBF resource reallocation failure of channel allocation due to DL TBF establishment .........95 C900040124 Number of GPRS UL TBF resource reallocation requests due to LLC transmission.........................................96 C900040125 Number of GPRS UL TBF resource reallocation failure of channel allocation due to LLC transmission ..............96 C900040126 Number of GPRS UL TBF resource reallocation requests for resource request..............................................97 C900040127 Number of GPRS UL TBF resource reallocation failure due to database allocation failure for resource request ...............................................................................98 C900040128 Number of EGPRS UL TBF establishment requests .............................................................................99 C900040129 Number of EGPRS UL TBF establishment failure due to database allocation failure ........................................99 C900040130 Number of EGPRS UL TBF resource reallocation requests due to DL TBF establishment ................................ 100 C900040131 Number of EGPRS UL TBF resource reallocation failure of channel allocation due to DL TBF establishment ............................................................................. 101 C900040132 Number of EGPRS UL TBF resource reallocation requests due to LLC transmission....................................... 102 C900040133 Number of EGPRS UL TBF resource reallocation failure of channel allocation due to LLC transmission ............ 102 C900040134 Number of EGPRS UL TBF resource reallocation requests for resource request............................................ 103 C900040135 Number of EGPRS UL TBF resource reallocation failure due to database allocation failure for resource request ............................................................................. 104 C900040136 Average number of available PDCH.................. 105 C900040137 Number of forcing conversation dynamic from PDCH to TCH by BSC ....................................................... 105 C900040138 Number of PDCH used by TBF in each cell ......... 105 C900040139 Maximum number of used PDCH ..................... 106 C900040140 Average number of used PDCH ....................... 106 C900040141 Number of GPRS DL TBF establishment requests before T3192 expiration ................................................... 107 C900040142 Number of GPRS DL TBF establishment using existing DL TBF resource .................................................. 108 C900040143 Number of GPRS DL TBF establishment requests on PACCH....................................................................... 108 C900040144 Number of GPRS DL TBF establishment requests on CCCH/PCCCH.............................................................. 109 C900040145 Number of EGPRS DL TBF establishment requests before T3192 expiration ......................................... 110 C900040146 Number of EGPRS DL TBF establishment using existing DL TBF resource .................................................. 111
C900040147 Number of EGPRS DL TBF establishment requests on PACCH............................................................. 112 C900040148 Number of EGPRS DL TBF establishment requests on CCCH/PCCCH.................................................... 113 C900040149 Number of GPRS DL signaling TBF release due to N3105 overflow ........................................................... 114 C900040150 Number of GPRS DL signaling TBF release due to other reasons .............................................................. 115 C900040151 Number of GPRS DL signaling TBF forcing release by control plane ...................................................... 115 C900040152 Number of GPRS DL signaling TBF release due to instance suspension ..................................................... 116 C900040153 Number of GPRS DL signaling TBF release due to inner abnormal............................................................ 117 C900040154 Number of EGPRS DL signaling TBF release due to N3105 overflow ........................................................... 118 C900040155 Number of EGPRS DL signaling TBF release due to other reasons .............................................................. 119 C900040156 Number of EGPRS DL signaling TBF forcing release by control plane ...................................................... 120 C900040157 Number of EGPRS DL signaling TBF release due to instance suspension ..................................................... 120 C900040158 Number of EGPRS DL signaling TBF release due to inner abnormal............................................................ 121 C900040159 Number of GPRS UL TBF establishments in release state...................................................................... 122 C900040160 Number of GPRS UL TBF establishment with existing UL resource............................................................ 123 C900040161 Number of GPRS UL TBF establishment requests on PACCH....................................................................... 124 C900040162 Number of EGPRS UL data TBF establishments on PACCH....................................................................... 124 C900040163 Number of EGPRS UL TBF establishments in release state...................................................................... 125 C900040164 Number of EGPRS UL TBF establishment with existing UL resource ........................................................ 126 C900040165 Number of EGPRS UL TBF establishment requests on PACCH............................................................. 127 C900040166 Number of EGPRS UL TBF establishment requests on CCCH/PCCCH.................................................... 127 C900040167 Number of dynamic PDCH preemption for CS service ........................................................................... 128 C900040168 Number of GPRS UL TBF establishment requests on CCCH/PCCCH.............................................................. 129 C900040169 Number of GPRS DL TBF establishment requests on PACCH....................................................................... 129 C900040170 Number of EGPRS DL TBF establishment requests on PACCH............................................................. 130 C900040171 Number of GPRS UL TBF establishment requests on PACCH....................................................................... 130 C900040172 Number of DL RLC pending blocks in MCS1 on PDTCH ........................................................................... 130 C900040173 Number of DL RLC pending blocks in MCS2 on PDTCH ........................................................................... 131 C900040174 Number of DL RLC pending blocks in MCS3 on PDTCH ........................................................................... 132 C900040175 Number of DL RLC pending blocks in MCS4 on PDTCH ........................................................................... 133 C900040176 Number of DL RLC pending blocks in MCS5 on PDTCH ........................................................................... 133
C900040177 Number of DL RLC pending blocks in MCS6 on PDTCH ........................................................................... 134 C900040178 Number of DL RLC pending blocks in MCS7 on PDTCH ........................................................................... 135 C900040179 Number of DL RLC pending blocks in MCS8 on PDTCH ........................................................................... 135 C900040180 Number of DL RLC pending blocks in MCS9 on PDTCH ........................................................................... 136 C900040181 Number of DL RLC NACK blocks in MCS1 on PDTCH ........................................................................... 137 C900040182 Number of DL RLC NACK blocks in MCS2 on PDTCH ........................................................................... 138 C900040183 Number of DL RLC NACK blocks in MCS3 on PDTCH ........................................................................... 138 C900040184 Number of DL RLC NACK blocks in MCS4 on PDTCH ........................................................................... 139 C900040185 Number of DL RLC NACK blocks in MCS5 on PDTCH ........................................................................... 140 C900040186 Number of DL RLC NACK blocks in MCS6 on PDTCH ........................................................................... 140 C900040187 Number of DL RLC NACK blocks in MCS7 on PDTCH ........................................................................... 141 C900040188 Number of DL RLC NACK blocks in MCS8 on PDTCH ........................................................................... 142 C900040189 Number of DL RLC NACK blocks in MCS9 on PDTCH ........................................................................... 143 C900040190 Number of DL RLC new blocks in MCS1 on PDTCH ........................................................................... 143 C900040191 Number of DL RLC new blocks in MCS2 on PDTCH ........................................................................... 144 C900040192 Number of DL RLC new blocks in MCS3 on PDTCH ........................................................................... 145 C900040193 Number of DL RLC new blocks in MCS4 on PDTCH ........................................................................... 145 C900040194 Number of DL RLC new blocks in MCS5 on PDTCH ........................................................................... 146 C900040195 Number of DL RLC new blocks in MCS6 on PDTCH ........................................................................... 147 C900040196 Number of DL RLC new blocks in MCS7 on PDTCH ........................................................................... 148 C900040197 Number of DL RLC new blocks in MCS8 on PDTCH ........................................................................... 148 C900040198 Number of DL RLC new blocks in MCS9 on PDTCH ........................................................................... 149 C900040199 Number of UL RLC pending blocks in MCS1 on PDTCH ........................................................................... 150 C900040200 Number of UL RLC pending blocks in MCS2 on PDTCH ........................................................................... 150 C900040201 Number of UL RLC pending blocks in MCS3 on PDTCH ........................................................................... 151 C900040202 Number of UL RLC pending blocks in MCS4 on PDTCH ........................................................................... 152 C900040203 Number of UL RLC pending blocks in MCS5 on PDTCH ........................................................................... 153 C900040204 Number of UL RLC pending blocks in MCS6 on PDTCH ........................................................................... 153 C900040205 Number of UL RLC pending blocks in MCS7 on PDTCH ........................................................................... 154 C900040206 Number of UL RLC pending blocks in MCS8 on PDTCH ........................................................................... 155
C900040207 Number of UL RLC pending blocks in MCS9 on PDTCH ........................................................................... 155 C900040208 Number of UL RLC NACK blocks in MCS1 on PDTCH ........................................................................... 156 C900040209 Number of UL RLC NACK blocks in MCS2 on PDTCH ........................................................................... 157 C900040210 Number of UL RLC NACK blocks in MCS3 on PDTCH ........................................................................... 158 C900040211 Number of UL RLC NACK blocks in MCS4 on PDTCH ........................................................................... 158 C900040212 Number of UL RLC NACK blocks in MCS5 on PDTCH ........................................................................... 159 C900040213 Number of UL RLC NACK blocks in MCS6 on PDTCH ........................................................................... 160 C900040214 Number of UL RLC NACK blocks in MCS7 on PDTCH ........................................................................... 160 C900040215 Number of UL RLC NACK blocks in MCS8 on PDTCH ........................................................................... 161 C900040216 Number of UL RLC NACK blocks in MCS9 on PDTCH ........................................................................... 162 C900040217 Number of UL RLC new blocks in MCS1 on PDTCH ........................................................................... 163 C900040218 Number of UL RLC new blocks in MCS2 on PDTCH ........................................................................... 163 C900040219 Number of UL RLC new blocks in MCS3 on PDTCH ........................................................................... 164 C900040220 Number of UL RLC new blocks in MCS4 on PDTCH ........................................................................... 165 C900040221 Number of UL RLC new blocks in MCS5 on PDTCH ........................................................................... 165 C900040222 Number of UL RLC new blocks in MCS6 on PDTCH ........................................................................... 166 C900040223 Number of UL RLC new blocks in MCS7 on PDTCH ........................................................................... 167 C900040224 Number of UL RLC new blocks in MCS8 on PDTCH ........................................................................... 168 C900040225 Number of UL RLC new blocks in MCS9 on PDTCH ........................................................................... 168 C900040232 Accumulated throughput of UL GPRS TBF ......... 169 C900040233 Accumulated throughput of DL GPRS TBF ......... 170 C900040234 Accumulated throughput of UL EGPRS TBF ......... 170 C900040235 Accumulated throughput of DL EGPRS TBF ......... 171
Overview
PS basic measurement (Cell) involves the ordinary counters used to measure the PS service performance and status, such as the uplink (UL) /downlink (DL) TBF counter, the flow counter, the UL/DL PACCH counter, the UL/DL RLC counter, the UL/DL GPRS data counter, the UL/DL EGPRS data counter, and the PS resource counter. The measurement takes cell as the statistics unit.
10
This counter counts the number of successful DL GPRS TBF establishments on the UL/DL GPRS TBF PACCH. When the DL GPRS TBF is established on the UL/DL GPRS TBF PACCH and a message indicating assignment success is sent, this counter increments. The measurement points are A as shown in Figure 1 and Figure 2, and A2 as shown in Figure 3.
FIGURE 1 MEASUREMENT POINT OF NUMBER OF REQUESTS FOR ESTABLISHING GPRS DOWNLINK DATA TBF BEFORE T3192 OVERTIME
FIGURE 2 MEASUREMENT POINT OF NUMBER OF ESTABLISHED GPRS DOWNLINK DATA TBF USING EXISTING RESOURCES
11
FIGURE 3 MEASUREMENT POINT OF NUMBER OF REQUESTS FOR ESTABLISHING GPRS DOWNLINK DATA TBF ON UPLINK GPRS TBF PACCH
Unit
Times
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. The measurement point is A1, as shown in Figure 4.
12
FIGURE DUE TO
OF
NUMBER
OF
Unit
Times
When BSC is transmitting the last DL TBF RLC block, set FBI to 1, set RRBP to ask the MS to respond with a Packet Downlink Ack/Nack message, and at the same time, activate T3191. If the specified block receives the MS response, then T3191 will stop and the DL transmission ends normally. If T3191 overflows, then it is considered that the radio transmission fails and the DL TBF is released abnormally.
13
Measurement Point
NUMBER
OF
Unit
Times
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. When the user plane receives the release request from the control plane, this counter increments. The measurement point is A, as shown in Figure 6.
FIGURE 6 MEASUREMENT POINT RELEASE BY CONTROL PLANE
OF
Measurement Point
NUMBER
OF
14
Unit
Times
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. When the DL block assigning timer expires, this counter increments. The measurement point is A, as shown in Figure 7.
FIGURE DUE TO 7 MEASUREMENT POINT INSTANCE SUSPENSION
OF
Measurement Point
NUMBER
OF
Unit
Times
When the user plane is transmitting the DL TBF, if the message fails to be sent at the radio interface, the RLC instance fails to
15
be created, or the resource reassignment fails, the DL TBF will be released abnormally.
Measurement Point Unit
During the DL TBF transmission, if the message fails to be sent at the radio interface, the RLC instance fails to be created, or the resource reassignment fails, this counter increments. Times
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.
When the DL TBF is created successfully and the TBF type is GPRS signaling TBF, the counter increments. The measurement point is similar to those of C900040001 and C901000014. Times
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.
When the DL TBF is created successfully and the TBF type is GPRS data TBF, the counter increments. The measurement point is similar to those of C900040001 and C901000014. Times
16
This counter counts the number of successful DL EGPRS TBF establishments on the UL/DL EGPRS TBF PACCH. When the DL EGPRS TBF is established on the UL/DL EGPRS TBF PACCH and a message indicating assignment success is sent, this counter increments. The measurement points are A as shown in Figure 8 and Figure 9, and A2 as shown in Figure 10.
FIGURE 8 MEASUREMENT POINT OF NUMBER OF REQUESTS FOR ESTABLISHING GPRS DOWNLINK DATA TBF BEFORE T3192 OVERTIME
FIGURE 9 MEASUREMENT POINT OF NUMBER OF ESTABLISHED GPRS DOWNLINK DATA TBF USING EXISTING RESOURCES
17
FIGURE 10 MEASUREMENT POINT OF NUMBER OF REQUESTS FOR ESTABLISHING GPRS DOWNLINK DATA TBF ON UPLINK GPRS TBF PACCH
Unit
Times
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. The measurement point is A1, as shown in Figure 11.
18
FIGURE DUE TO
OF
NUMBER
OF
Unit
Times
When BSC is transmitting the last DL TBF RLC block, set FBI to 1, set RRBP to ask the MS to respond with a Packet Downlink Ack/Nack message, and at the same time, activate T3191. If the specified block receives the MS response, then T3191 will stop and the DL transmission ends normally. If T3191 overflows, then it is considered that the radio transmission fails and the DL TBF is released abnormally.
19
Measurement Point
NUMBER
OF
Unit
Times
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. When the user plane receives the release request from the control plane, this counter increments. The measurement point is A, as shown in Figure 13.
FIGURE 13 MEASUREMENT POINT RELEASE BY CONTROL PLANE
OF
Measurement Point
NUMBER
OF
20
Unit
Times
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. When the DL block assigning timer expires, this counter increments. The measurement point is A1, as shown in Figure 14.
FIGURE DUE TO 14 MEASUREMENT POINT INSTANCE SUSPENSION
OF
Measurement Point
NUMBER
OF
Unit
Times
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
21
be created, or the resource reassignment fails, the DL TBF will be released abnormally.
Measurement Point Unit
During the DL TBF transmission, if the message fails to be sent at the radio interface, the RLC instance fails to be created, or the resource reassignment fails, this counter increments. Times
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.
When the DL TBF is created successfully and the TBF type is signaling TBF, the counter increments. The measurement point is similar to those of C900040001 and C901000014. Times
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.
When the DL TBF is created successfully and the TBF type is data TBF, the counter increments. The measurement point is similar to those of C900040001 and C901000014. Times
22
This counter counts the average number of DL GPRS TBF establishments in a cell. The counter acquires the measurement value regularly. The number of GPRS TBFs existing in the cell is considered the average number. Times
This counter counts the average number of DL EGPRS TBF establishments in a cell. The counter acquires the measurement value regularly. The number of EGPRS TBFs existing in the cell is considered the average number. Times
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 GPRS UL TBF establishments on PACCH
Usage
23
Measurement Point
Unit
Times
After the UL TBF is established, MS will transmit data on the BSSassigned UL block. If the specified block of BSS fails to receive RLC block from MS, N3101 increments. Otherwise, N3101 will have a clear. When N3101 exceeds the maximum value, BSS will release UL TBF. The counter counts the number of abnormal releases of GPRS UL TBF due to N3101 overflow. The measurement point is N3101 overflow, as A shown in Figure 16.
FIGURE DUE TO 16 MEASUREMENT POINT N3101 OVERFLOW
OF
NUMBER
OF
Unit
Times
24
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 GPRS UL TBF due to N3103 overflow. The measurement point is N3103 overflow, as A shown in Figure 17.
FIGURE DUE TO 17 MEASUREMENT POINT N3103 OVERFLOW
OF
NUMBER
OF
Unit
Times
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 GPRS UL TBF due to release request from the control plane. The measurement point is arrival of the release request, as A shown in Figure 18.
25
OF
NUMBER
OF
Unit
Times
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 GPRS UL TBF due to suspension of the instance. The measurement point is that UPPB detects suspension of the instance, as A shown in Figure 19.
FIGURE DUE TO 19 MEASUREMENT POINT INSTANCE SUSPENSION
OF
NUMBER
OF
Unit
Times
26
The counter counts the number of abnormal releases of GPRS UL TBF due to internal error. The measurement point is abnormal UPPB suspension, as B shown in Figure 20.
FIGURE DUE TO 20 MEASUREMENT POINT INSTANCE SUSPENSION
OF
NUMBER
OF
Unit
Times
For different purpose, MS may establish two types of TBF: signaling TBF and data TBF. The counter counts the number of GPRS UL signaling TBF link establishments. The measurement point is that UPPB access type is signaling TBF. For all 1-step accesses, their type is considered signaling TBF, as A1 shown in Figure 21. For the 2-step accesses, the TBF type is detected as SIGNAL_TBF, as A1 shown in Figure 22.
27
OF
1-STEP ACCESS
28
OF
2-STEP ACCESS
Unit
Times
For different purpose, MS may establish two types of TBF: signaling TBF and data TBF. The counter counts the number of GPRS UL data TBF link establishments. The measurement point is when UPPB access type is data TBF. For example, the TBF type is detected as DATA_TBF, as A1 shown in Figure 23.
29
OF
2-STEP ACCESS
Unit
Times
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.
30
The counter counts the number of successful EGPRS UL TBF establishments on PACCH. The measurement point is A, as shown in Figure 24.
FIGURE 24 MEASUREMENT POINT OF NUMBER ESTABLISHMENT SUCCESS ON PACCH
OF
EGPRS UL TBF
Unit
Times
After the UL TBF is established, MS will transmit data on the BSSassigned UL block. If the specified block of BSS fails to receive RLC block from MS, N3101 increments. Otherwise, N3101 will have a clear. When N3101 exceeds the maximum value, BSS will release UL TBF. The counter counts the number of abnormal releases of EGPRS UL TBF due to N3101 overflow. The measurement point is when N3101 overflow. Times
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.
31
The counter counts the number of abnormal releases of EGPRS UL TBF due to N3103 overflow. The measurement point is when N3103 overflow. Times
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 EGPRS UL TBF due to release request from the control plane. The measurement point is arrival of the release request. Times
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 EGPRS UL TBF due to suspension of the instance. The measurement point is that UPPB detects suspension of the instance. Times
32
TBF is abnormally released due to UPPB internal error. The counter counts the number of abnormal releases of EGPRS UL TBF due to internal error. The measurement point is abnormal UPPB suspension. Times
For different purpose, MS may establish two types of TBF: signaling TBF and data TBF. The counter counts the number of EGPRS UL signaling TBF link establishments. The measurement point is that UPPB access type is signaling TBF. Times
For different purpose, MS may establish two types of TBF: signaling TBF and data TBF. The counter counts the number of EGPRS UL data TBF link establishments. The measurement point is that UPPB access type is data TBF. Times
33
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 This counter counts the average number of UL GPRS TBF establishing simultaneously. When UPPB receives the message informing UL GPRS TBF establishment, the number of TBFs is refreshed and the times of sampling accumulates. Times
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 This counter counts the average number of UL EGPRS TBF establishing simultaneously. When UPPB receives the message informing UL EGPRS TBF establishment, the number of TBFs is refreshed and the times of sampling accumulates. Times
34
After the UL TBF is established, MS will transmit data on the BSSassigned UL block. If the specified block of BSS fails to receive RLC block from MS, N3101 increments. Otherwise, N3101 will have a clear. When N3101 exceeds the maximum value, BSS will release UL TBF. The counter counts the number of abnormal releases of GPRS signaling UL TBF due to N3101 overflow. The measurement point is N3101 overflow. Times
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 GPRS signaling UL TBF due to N3103 overflow. The measurement point is N3103 overflow. Times
35
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 GPRS signaling UL TBF due to release request from the control plane. The measurement point is arrival of the release request. Times
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 GPRS signaling UL TBF due to suspension of the instance. The measurement point is that UPPB detects suspension of the instance. Times
36
The counter counts the number of abnormal releases of GPRS signaling UL TBF due to internal error. The measurement point is abnormal UPPB suspension. Times
After the UL TBF is established, MS will transmit data on the BSSassigned UL block. If the specified block of BSS fails to receive RLC block from MS, N3101 increments. Otherwise, N3101 will have a clear. When N3101 exceeds the maximum value, BSS will release UL TBF. The counter counts the number of abnormal releases of EGPRS signaling UL TBF due to N3101 overflow. The measurement point is N3101 overflow. Times
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 EGPRS signaling UL TBF due to N3103 overflow. The measurement point is N3103 overflow. Times
37
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 EGPRS signaling UL TBF due to release request from the control plane. The measurement point is arrival of the release request. Times
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 EGPRS signaling UL TBF due to suspension of the instance. The measurement point is that UPPB detects suspension of the instance. Times
38
The counter counts the number of abnormal releases of EGPRS signaling UL TBF due to internal error. The measurement point is abnormal UPPB suspension. Times
The DL GIPB sends DL UnitData to UPPB through IP packets. tQoSProfile Tbit in DL UnitData identifies whether data or signaling is transmitted. UPPB applies to CMP to establish DL TBF (radio access capacity to carry MS) and according to the CMP request, establishes EGPRS/GPRS TBF. The counter counts the number of EGPRS DL LLC frames. The measurement point is A, as shown in Figure 25.
FIGURE 25 MEASUREMENT POINT
OF
NUMBER
OF
Unit
Times
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. The counter counts the number of discarded EGPRS DL LLC frames due to buffer overflow.
Usage
39
Measurement Point
DISCARDED EGPRS DL
Unit
Times
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. The counter counts the number of discarded EGPRS DL LLC frames due to life time expiration. The measurement point is A, as shown in Figure 27.
FIGURE 27 MEASUREMENT POINT OF NUMBER LLC FRAMES DUE TO LIFE TIME EXPIRATION
OF
DISCARDED EGPRS DL
Unit
Times
40
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. The counter counts the number of discarded EGPRS DL LLC frames due to other reasons than the above two in C900040048 and C900040049. The measurement point is A, as shown in Figure 28.
FIGURE 28 MEASUREMENT POINT OF NUMBER LLC FRAMES DUE TO OTHER REASONS
OF
Usage
Measurement Point
DISCARDED EGPRS DL
Unit
Times
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
41
Measurement Point
NUMBER
OF
DL SIGNALING LLC
Unit
Times
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. The counter counts the number of discarded EGPRS DL signaling LLC frames due to buffer overflow. The measurement point is A, as shown in Figure 30.
FIGURE 30 MEASUREMENT POINT OF NUMBER OF DISCARDED EGPRS DL SIGNALING LLC FRAMES DUE TO BUFFER OVERFLOW
Unit
Times
42
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. The counter counts the number of discarded EGPRS DL signaling LLC frames due to life time expiration. The measurement point is A, as shown in Figure 31.
FIGURE 31 MEASUREMENT POINT OF NUMBER OF DISCARDED EGPRS DL SIGNALING LLC FRAMES DUE TO LIFE TIME EXPIRATION
Unit
Times
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. The counter counts the number of discarded EGPRS DL signaling LLC frames due to other reasons than the above two in C900040052 and C900040053.
Usage
43
Measurement Point
Unit
Times
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. The counter counts the number of data blocks transmitted according to given Abis bandwidth. 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. Times
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.
44
This counter performs statistics for LLC layer, and the statistic data contains LLC frame header.
Usage Measurement Point
The counter counts the bytes of effective upper layer protocol data sent on DL PDCH. The measurement point is A, as shown in Figure 33.
FIGURE 33 MEASUREMENT POINT OF TOTAL BYTES LAYER PROTOCOL DATA SENT ON DL PDCH
OF
EFFECTIVE UPPER
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.
The counter counts the bytes of effective upper layer protocol data received on UL PDCH. The measurement point is A, as shown in Figure 34.
FIGURE 34 MEASUREMENT POINT OF TOTAL BYTES LAYER PROTOCOL DATA RECEIVED ON UL PDCH
OF
EFFECTIVE UPPER
Unit
Byte
45
Related Features
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.
The counter counts the bytes carried by GPRS UL data TBF LLC frame. The measurement point is A, as shown in Figure 35.
FIGURE 35 MEASUREMENT POINT DATA TBF
OF
BYTES
OF
LLC FRAME
ON
GPRS UL
Unit
Byte
The duration starts when BSS receives the UL access from MS and ends when BSS receives the data block (CV=0) and all the other blocks have arrived. For extended UL TBF, the duration of extended uplink status is subtracted. The counter counts the duration of GPRS UL data TBF. The duration lasts from UPPBs reception of UL TBF establishment request to transmission of Packet Uplink Ack with FAI set. The measurement point is A, as shown in Figure 36. For extended UL TBF, the measurement point is A and B, as shown in Figure 37.
46
OF
DURATION
OF
OF
DURATION
OF
47
Unit
ms
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.
The counter counts the bytes of LLC frame on GPRS DL data TBF. The measurement point is A, as shown in Figure 38.
FIGURE 38 MEASUREMENT POINT DATA TBF
OF
BYTES
OF
LLC FRAME
ON
GPRS DL
Unit
Byte
The duration lasts from BSSs reception of the DL TBF establishment request to its reception of Packet Downlink Ack/EGPRS Packet Downlink Ack (Packet Control Ack in non-reply mode) with FAI=1 sent from MS, and the duration of downlink delay status is subtracted. The counter counts the duration of GPRS DL data TBF. The counter starts counting when UPPB receives DL TBF establishment request until BSS finishes sending all current data and MS
48
returns acknowledgement response for all. During the delay, after the new DL data from SGSN is received, data transmission is initiated again, and the counter restarts counting until the Packet Downlink Ack/EGPRS Packet Downlink Ack (Packet Control Ack in non-reply mode) with FAI=1 is received from MS. The measurement point is A and B, as shown in Figure 39.
FIGURE 39 MEASUREMENT POINT
OF
DURATION
OF
Unit
ms
During the TBF transmission, MS divides the UL LLC frame into RLC blocks and sends them to BSS. Only when BSS receives all these RLC blocks can it recompose the LLC frame. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
Usage
The counter counts the number of effective data blocks received on GPRS UL TBF.
49
Measurement Point
NUMBER
OF
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.
The counter counts the number of NACK blocks received on GPRS UL TBF Then counter increments when BSS correctly receives a NACK block. The measurement point is A, as shown in Figure 41.
FIGURE 41 MEASUREMENT ON GPRS UL TBF POINT
OF
NUMBER
OF
50
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.
The counter counts the number of effective data blocks sent on GPRS DL TBF Then counter increments when Packet DownLink Ack/EGPRS Packet Downlink Ack indicates that MS have correctly received the RLC block. The measurement point is A1, as shown in Figure 42.
FIGURE 42 MEASUREMENT POINT SENT ON GPRS DL TBF
OF
NUMBER
OF
During the TBF transmission, BSS divides the UL LLC frame into RLC blocks and sends them to MS. Only when MS correctly re-
51
ceives all these RLC blocks can it recompose the LLC frame. MS 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 Measurement Point
The counter counts the number of NACK blocks sent on GPRS DL TBF. Then counter increments when Packet DownLink Ack/EGPRS Packet Downlink Ack indicates that MS fails to receive the RLC block. The measurement point is A2, as shown in Figure 43.
FIGURE 43 MEASUREMENT POINT GPRS DL TBF
OF
NUMBER
OF
ON
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.
52
Measurement Point
BYTES
OF
LLC FRAME
ON
EGPRS
Unit
Byte
The duration starts when BSS receives the UL access from MS and ends when BSS receives the data block (CV=0) and all the other blocks have arrived. For extended UL TBF, the duration of extended uplink status is subtracted. The counter counts the duration of EGPRS UL data TBF. The duration lasts from UPPBs reception of UL TBF establishment request to transmission of Packet Uplink Ack with FAI=1. The measurement point is A, as shown in Figure 45. For extended UL TBF, the measurement point is A and B, as shown in Figure 46.
FIGURE 45 MEASUREMENT POINT
OF
DURATION
OF
53
OF
DURATION
OF
Unit
ms
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.
54
Measurement Point
BYTES
OF
LLC FRAME
ON
EGPRS
Unit
Byte
The duration lasts from BSSs reception of the DL TBF establishment request to its reception of Packet Downlink Ack/EGPRS Packet Downlink Ack (Packet Control Ack in non-reply mode) with FAI=1 sent from MS, and the duration of downlink delay status is subtracted. The counter counts the duration of EGPRS DL data TBF. The counter starts counting when UPPB receives DL TBF establishment request until BSS finishes sending all current data and MS returns acknowledgement response for all. During the delay, after the new DL data from SGSN is received, data transmission is initiated again, and the counter restarts counting until the Packet Downlink Ack/EGPRS Packet Downlink Ack (Packet Control Ack in non-reply mode) with FAI=1 is received from MS. The measurement point is A and B, as shown in Figure 48.
55
OF
DURATION
OF
Unit
ms
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.
56
Measurement Point
NUMBER
OF
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.
The counter counts the number of NACK blocks received on EGPRS UL TBF. Then counter increments when BSS correctly receives a NACK block. The measurement point is A, as shown in Figure 50.
FIGURE 50 MEASUREMENT ON EGPRS UL TBF POINT
OF
NUMBER
OF
57
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.
The counter counts the number of effective data blocks sent on EGPRS DL TBF. The counter increments when Packet DownLink Ack/EGPRS Packet Downlink Ack indicates that MS have correctly received the RLC block. The measurement point is A1, as shown in Figure 51.
FIGURE 51 MEASUREMENT POINT SENT ON EGPRS DL TBF
OF
NUMBER
OF
During the TBF transmission, BSS divides the UL LLC frame into RLC blocks and sends them to MS. Only when MS correctly re-
58
ceives all these RLC blocks can it recompose the LLC frame. MS informs BSS of the RLC block reception through Packet DownLink Ack/EGPRS Packet Downlink Ack. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
Usage Measurement Point
The counter counts the number of NACK blocks sent on EGPRS DL TBF. The counter increments when Packet DownLink Ack/EGPRS Packet Downlink Ack indicates that MS fails to receive the RLC block. The measurement point is A2, as shown in Figure 52.
FIGURE 52 MEASUREMENT POINT EGPRS DL TBF
OF
NUMBER
OF
ON
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. This counter counts the times that downlink LLC frames are sent in GPRS services. The counter is updated when the BSSGP module saves LLC frames. The measurement point is A, as shown in Figure 53.
59
OF
Unit
Times
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. This counter counts the failures to apply for dynamic memory for downlink LLC frames in GPRS services. The counter is updated when the BSSGP module saves LLC frames. The measurement point is A, as shown in Figure 54.
FIGURE 54 MEASUREMENT POINT OF DISCARDED DOWNLINK GPRS LLC FRAMES DUE TO BUFFER OVERFLOW
Unit
Times
60
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. The counter counts the times that the LLC Discard message is sent due to life time expiration in downlink GPRS services. The measurement point is A, as shown in Figure 55.
FIGURE 55 MEASUREMENT POINT OF DISCARDED DOWNLINK GPRS LLC FRAMES DUE TO LIFE TIME EXPIRATION
Unit
Times
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. This counter counts the discards of downlink LLC frames in GPRS services due to reasons other than buffer overflow. The counter is updated when the BSSGP module saves LLC frames. The measurement point is A, as shown in Figure 56.
61
OF
Unit
Times
If there is no other RLC/MAC block available in the network, BSS will transmit the DUMMY blocks to MS for UL transmission. The counter counts the number of DL dummy control blocks sent by BSC on PACCH in the packet transmission mode. If the DL control block sent from BTS to MS is a DL Dummy control block, the counter increments. The measurement point is A, as shown in Figure 57.
FIGURE 57 MEASUREMENT POINT BLOCKS ON PACCH
OF
NUMBER
OF
DL DUMMY CONTROL
Unit
Times
62
Similar to C900040078, this counter counts the number of UL dummy control blocks sent by BSC on PACCH in the packet transmission mode. If the DL control block sent from BTS to MS is an UL Dummy control block, the counter increments. The measurement point is A, as shown in Figure 58.
FIGURE 58 MEASUREMENT POINT BLOCKS ON PACCH
OF
Measurement Point
NUMBER
OF
UL DUMMY CONTROL
Unit
Times
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.
The counter counts the number of DL RLC blocks expect DUMMY blocks sent by BSC on PACCH. When BSC sends a DL control block (except DUMMY block) to MS through BTS, the counter increments. The measurement point is A, as shown in Figure 59.
63
OF
DL RLC BLOCKS
ON
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.
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of CS1. When BSC sends a pending RLC block whose coding method is CS1 to MS, the counter increments. The measurement point is A, as shown in Figure 60.
FIGURE 60 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
64
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.
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of CS2. 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 61.
FIGURE 61 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
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.
65
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 62.
FIGURE 62 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
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.
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of CS4. 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 63.
FIGURE 63 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
66
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.
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of CS1. When BSC sends retransmitted RLC block whose coding method is CS1 to MS via BTS, the counter increments. The measurement point is A, as shown in Figure 64.
FIGURE 64 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
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.
67
This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
Usage Measurement Point
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of CS2. 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 65.
FIGURE 65 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
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.
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of CS3. 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 66.
68
POINT
OF
NUMBER
OF
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.
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of CS4. 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 67.
FIGURE 67 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
69
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.
The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of CS1. 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 68.
FIGURE 68 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
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.
70
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 69.
FIGURE 69 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
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.
The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of CS3. 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 70.
FIGURE 70 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
71
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.
The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of CS4. 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 71.
FIGURE 71 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
This counter counts the number of UL RLC blocks except for DUMMY blocks sent from MS to BSC through BTS on PACCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
72
The counter counts the number of uplink RLC blocks expect DUMMY blocks received by BSC on PACCH. When BSC receives an UL control block (except the DUMMY block) from MS, the counter increments. The measurement point is A, as shown in Figure 72.
FIGURE 72 MEASUREMENT POINT OF NUMBER EXCLUDING DUMMY BLOCKS ON PACCH
OF
UL RLC BLOCKS
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.
This counter counts the number of useful UL CS1-coded pending RLC blocks received by BSC on PDTCH. When BSC receives CS1-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 73.
FIGURE 73 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
Unit
Times
73
Related Features
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.
This counter counts the number of useful UL CS2-coded pending RLC blocks received by BSC on PDTCH. When BSC receives CS2-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 74.
FIGURE 74 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
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.
74
This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
Usage Measurement Point
This counter counts the number of useful UL CS3-coded pending RLC blocks received by BSC on PDTCH. When BSC receives CS3-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 75.
FIGURE 75 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
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.
This counter counts the number of useful UL CS4-coded pending RLC blocks received by BSC on PDTCH. When BSC receives CS4-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 76.
FIGURE 76 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
75
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.
This counter counts the number of useful UL CS1-coded retransmitted RLC blocks received by BSC on PDTCH. When BSC receives CS1-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 77.
FIGURE 77 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
After receiving UL data block, BSC decides whether it is retransmitted RLC block, first-transmitted RLC block or pending RLC block.
76
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 Measurement Point
This counter counts the number of useful UL CS2-coded retransmitted RLC blocks received by BSC on PDTCH. When BSC receives CS2-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 78.
FIGURE 78 MEASUREMENT POINT ON PDTCH
OF
NUMBER
OF
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.
This counter counts the number of useful UL CS3-coded retransmitted RLC blocks received by BSC on PDTCH. When BSC receives CS3-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 79.
77
POINT
OF
NUMBER
OF
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.
This counter counts the number of useful UL CS4-coded retransmitted RLC blocks received by BSC on PDTCH. When BSC receives CS4-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 80.
FIGURE 80 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
78
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.
This counter counts the number of useful UL CS1-coded first-transmitted RLC blocks received by BSC on PDTCH. When BSC receives CS1-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 81.
FIGURE 81 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
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.
79
Measurement Point
When BSC receives CS2-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 82.
FIGURE 82 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
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.
This counter counts the number of useful UL CS3-coded first-transmitted RLC blocks received by BSC on PDTCH. When BSC receives CS3-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 83.
FIGURE 83 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
80
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.
This counter counts the number of useful UL CS4-coded first-transmitted RLC blocks received by BSC on PDTCH. When BSC receives CS4-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 84.
FIGURE 84 MEASUREMENT ON PDTCH POINT
OF
NUMBER
OF
When MS transmits UL RLC blocks to BSC through BTS, this counter counts the number of data blocks received by BSC, including the retransmitted RLC blocks, blocks to be confirmed and the firsttransmitted blocks.
81
This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
Usage Measurement Point Unit Related Features
The counter counts the number of data blocks received by UL PDTCH. When MS transmits an UL RLC block to BSC through BTS (including the retransmitted RLC blocks, blocks to be confirmed and the firsttransmitted blocks), this counter increments. Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode
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.
The counter counts the number of data blocks sent by DL PDTCH. 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. Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode
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). The counter collects information about the frequency of DL establishment requests received by PS control plane when BSC attempts to establish DL GPRS TBFs. This counter increments in the following two cases: When PS control plane receives a DL TBF establishment request from PS user plane, this counter increments.
Usage
Measurement Point
82
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
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. The counter collects information about the frequency of channel allocation failures when BSC attempts to establish GPRS DL TBFs. This counter increments in the following two cases: When PS control plane receives the DL TBF establishment request from PS user plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 85.
FIGURE 85 MEASUREMENT POINT OF ALLOCATION FAILURES RECEIVING DL TBF ESTABLISHMENT REQUEST
AFTER
When MS has already established an UL GPRS TBF and DL GPRS TBF is to be established, if PS control plane receives the DL TBF assignment message from PS user plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 86.
83
AFTER
Unit
Times
C900040110 Number of GPRS DL TBF resource reallocation requests due to UL TBF establishment
Description Usage Measurement Point
The counter counts the number of GPRS DL TBF resource reallocation requests due to UL TBF establishment. The counter collects information about the frequency of GPRS DL TBF resource reallocation requests. When MS has already established a DL GPRS TBF, if PS control plane receives an UL TBF assignment message from PS user plane, this counter increments. The measurement point is A, as shown in Figure 87.
FIGURE 87 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF RESOURCE REALLOCATION REQUESTS DUE TO UL TBF ESTABLISHMENT
Unit
Times
84
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. The counter collects information about the frequency of GPRS DL resource reallocation failures of channel allocation caused by failed UL TBF establishment allocation. 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 88.
FIGURE 88 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF RESOURCE REALLOCATION FAILURE OF CHANNEL ALLOCATION DUE TO UL TBF ESTABLISHMENT
Usage
Measurement Point
Unit
Times
85
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. This counter collects information about the frequency of resource reallocation requests received by PS control plane during the DL GPRS TBF transmission. 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 89.
FIGURE 89 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF RESOURCE REALLOCATION REQUESTS DUE TO LLC TRANSMISSION
Usage
Measurement Point
Unit
Times
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.
86
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. After PS control plane receives a resource reallocation request from PS user plane and applies to database for resources, if it fails to obtain the resources, this counter increments, as A shown in Figure 90.
FIGURE 90 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF RESOURCE REALLOCATION FAILURE OF CHANNEL ALLOCATION DUE TO LLC TRANSMISSION
Measurement Point
Unit
Times
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). The counter collects information about the frequency of DL establishment requests received by the control plane when BSC attempts to establish DL EGPRS TBFs. This counter increments in the following two cases: When PS control plane receives a DL TBF establishment request from PS user plane, this counter increments. 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.
Usage
Measurement Point
Unit
Times
87
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 RANPS applies to database for resources. It involves the number of allocation failures caused by PDCH, Abis, and PCU having no available resource or in abnormal status. The counter collects information about the frequency of channel allocation failures when BSC attempts to establish EGPRS DL TBFs and RANPS applies to database for resources. This counter increments in the following two cases: When PS control plane receives the DL TBF establishment request from PS user plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 91.
FIGURE 91 MEASUREMENT POINT OF ALLOCATION FAILURES RECEIVING DL TBF ESTABLISHMENT REQUEST
AFTER
Usage
Measurement Point
When UL EGPRS TBF exists and DL EGPRS TBF is to be established, if PS control plane receives the DL TBF assignment message from PS user plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 92.
FIGURE 92 MEASUREMENT POINT OF ALLOCATION FAILURES RECEIVING DL TBF ASSIGNMENT MESSAGE
AFTER
88
Unit
Times
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). The counter collects information about the frequency of EGPRS downlink TBF resource reallocation requests. 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 93.
FIGURE 93 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF RESOURCE REALLOCATION REQUESTS DUE TO UL TBF ESTABLISHMENT
Unit
Times
89
C900040117 Number of EGPRS DL TBF resource reallocation failure of channel allocation 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. The counter collects information about the frequency of EGPRS DL resource reallocation failures of channel allocation caused by failed UL TBF establishment allocation. 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 94.
FIGURE 94 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF RESOURCE REALLOCATION FAILURE OF CHANNEL ALLOCATION DUE TO UL TBF ESTABLISHMENT
Usage
Measurement Point
Unit
Times
90
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. This counter collects information about the frequency of resource reallocation requests received by PS control plane during the DL EGPRS TBF transmission. 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 95.
FIGURE 95 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF RESOURCE REALLOCATION REQUESTS DUE TO LLC TRANSMISSION
Usage
Measurement Point
Unit
Times
C900040119 Number of EGPRS DL TBF resource reallocation failure of channel allocation 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.
91
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. 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 96.
FIGURE 96 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF RESOURCE REALLOCATION FAILURE OF CHANNEL ALLOCATION DUE TO LLC TRANSMISSION
Measurement Point
Unit
Times
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). The counter collects information about the frequency of channel requests when MS attempts to establish GPRS services. This counter increments in the following three cases: When BSC receives a CCCH request originated by MS, this counter increments. When BSC receives a PCCCH request originated by MS, this counter increments. When BSC receives a PACCH request originated by MS and user plane sends a resource request to control plane, this counter increments.
Unit
Times
92
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. The counter collects information about the frequency of channel allocation failures when the system attempts to establish GPRS UL TBFs. This counter increments in the following three cases: 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 97.
FIGURE 97 MEASUREMENT POINT RECEIVING CCCH REQUEST
OF
Usage
Measurement Point
ALLOCATION FAILURES
AFTER
When PS control plane receives a PCCCH request from MS, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 98.
FIGURE 98 MEASUREMENT POINT RECEIVING PCCCH REQUEST
OF
ALLOCATION FAILURES
AFTER
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 99.
93
OF
Unit
Times
C900040122 Number of GPRS UL TBF resource reallocation requests due to DL TBF establishment
Description Usage Measurement Point
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 GPRS UL TBF resource reallocation requests. 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 100.
FIGURE 100 MEASUREMENT POINT OF NUMBER OF GPRS UL TBF RESOURCE REALLOCATION REQUESTS DUE TO DL TBF ESTABLISHMENT
Unit
Times
94
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. The counter collects information about the frequency of GPRS UL resource reallocation failures of channel allocation caused by failed DL TBF establishment allocation. 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 101.
FIGURE 101 MEASUREMENT POINT OF ALLOCATION FAILURES RECEIVING DL TBF ASSIGNMENT MESSAGE
AFTER
Usage
Measurement Point
Unit
Times
95
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. This counter collects information about the frequency of resource reallocation requests received by PS control plane during the UL GPRS TBF transmission. 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 102.
FIGURE 102 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF RESOURCE REALLOCATION REQUESTS DUE TO LLC TRANSMISSION
Usage
Measurement Point
Unit
Times
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.
96
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. 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 103.
FIGURE 103 MEASUREMENT POINT OF NUMBER RESOURCE REALLOCATION FAILURE OF CHANNEL TRANSMISSION
OF GPRS DL TBF ALLOCATION DUE TO
Measurement Point
LLC
Unit
Times
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. 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). When PS control plane receives a resource allocation request from PS user plane, this counter increments, as A shown in Figure 104.
Usage
Measurement Point
97
FIGURE 104 MEASUREMENT POINT OF NUMBER OF GPRS UL TBF RESOURCE REALLOCATION REQUESTS FOR RESOURCE REQUEST
Unit
Times
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. 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. 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 105.
FIGURE 105 FAILING
TO
Usage
Measurement Point
REQUEST
FOR
RESOURCE
FROM
DATABASE
Unit
Times
98
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). The counter collects information about the frequency of channel requests when MS attempts to establish EDGE services. This counter increments in the following three cases: 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
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. The counter collects information about the frequency of channel allocation failures when the system attempts to establish EGPRS UL TBFs. This counter increments in the following two cases: 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 106.
Usage
Measurement Point
99
FIGURE 106 MEASUREMENT POINT OF NUMBER OF EGPRS UPLINK TBF ESTABLISHMENT CHANNEL ALLOCATION FAILURES
When MS has already established a DL EGPRS TBF, if PS control plane receives an UL TBF assignment message from PS user plane, it will apply to database for resources. If it fails to obtain the resources, this counter increments. The measurement point is A, as shown in Figure 107.
FIGURE 107 MEASUREMENT POINT GPRS TBF EXISTS)
OF
Unit
Times
C900040130 Number of EGPRS UL TBF resource reallocation requests due to DL TBF establishment
Description Usage Measurement Point
The counter counts the number of EGPRS UL TBF resource reallocation requests due to DL TBF establishment. The counter collects information about the frequency of EGPRS UL TBF resource reallocation requests. 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 108.
100
FIGURE 108 MEASUREMENT POINT OF NUMBER OF GPRS UL TBF RESOURCE REALLOCATION REQUESTS DUE TO DL TBF ESTABLISHMENT
Unit
Times
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. The counter collects information about the frequency of EGPRS UL resource reallocation failures of channel allocation caused by failed DL TBF establishment allocation. 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 109.
FIGURE 109 MEASUREMENT POINT OF ALLOCATION FAILURES RECEIVING DL TBF ASSIGNMENT MESSAGE
AFTER
Usage
Measurement Point
Unit
Times
101
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. This counter collects information about the frequency of resource reallocation requests received by PS control plane during the UL EGPRS TBF transmission. When PS control plane receives a resource reallocation request from PS user plane, this counter increments, as A shown in Figure 110.
FIGURE 110 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF RESOURCE REALLOCATION REQUESTS DUE TO LLC TRANSMISSION
Usage
Measurement Point
Unit
Times
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.
102
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. 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 111.
FIGURE 111 MEASUREMENT POINT OF NUMBER RESOURCE REALLOCATION FAILURE OF CHANNEL TRANSMISSION
OF GPRS DL TBF ALLOCATION DUE TO
Measurement Point
LLC
Unit
Times
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. 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). When PS control plane receives a resource allocation request from PS user plane, this counter increments, as A shown in Figure 112.
Usage
Measurement Point
103
FIGURE 112 MEASUREMENT POINT OF NUMBER OF GPRS UL TBF RESOURCE REALLOCATION REQUESTS FOR RESOURCE REQUEST
Unit
Times
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. 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. 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 113.
FIGURE 113 FAILING
TO
Usage
Measurement Point
REQUEST
FOR
RESOURCE
FROM
DATABASE
Unit
Times
104
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. This counter is used to find out the number of available PDCH in the serving cell. The counter's value can be obtained by querying the database when periodic measurement data is reported. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
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. 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. The counter increments when dynamic PDCH is idle and the database starts reclaiming dynamic PDCH. Times ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-003 Full dynamic channel allocation on Um interface
Usage
This counter counts the sum of PDCH used by all TBF in the serving cell.
105
This counter is used to find out the condition of multi-timeslot allocation in the serving cell. The counter's value can be obtained by querying the database when periodic measurement data is reported. Times
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. 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. This counter increments in the following three cases: Request for database Release database Report periodic measurement data
Usage
Measurement Point
Unit
Times
This counter records the average number of used PDCH in a cell within the measurement period. 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. This counter increments in the following three cases: Request for database Release database Report periodic measurement data
Measurement Point
Unit
Times
106
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. This counter counts the number of times of establishing new DL TBF. 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 114.
FIGURE 114 MEASUREMENT POINT OF NUMBER OF GPRS DL TBF ESTABLISHMENT REQUESTS BEFORE T3192 EXPIRATION
Unit
Times
107
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. 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 115.
FIGURE 115 MEASUREMENT POINT OF GPRS DL TBF ESTABLISHMENT USING EXISTING DL TBF RESOURCE
Measurement Point
Unit
Times
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.
108
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
GPRS DL TBF
Unit
Times
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. Under MSs packet idle status, when BSC sends the request for DL resource to BSC control plane after receiving LLC frame from SGSN, the counter increments. The measurement point is as A1, as shown in Figure 117.
Measurement Point
109
OF
GPRS DL TBF
Unit
Times
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 118.
110
FIGURE 118 MEASUREMENT POINT OF NUMBER OF EGPRS DL TBF ESTABLISHMENT REQUESTS BEFORE T3192 EXPIRATION
Unit
Times
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. 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 119.
Measurement Point
111
FIGURE 119 MEASUREMENT POINT OF NUMBER OF EGPRS DL TBF ESTABLISHMENT USING EXISTING DL TBF RESOURCE
Unit
Times
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
GPRS DL TBF
Unit
Times
112
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. Under MSs packet idle status, when BSC sends the request for DL resource to BSC control plane after receiving LLC frame from SGSN, the counter increments. The measurement point is A1, as shown in Figure 121.
FIGURE 121 NORMAL CCCH/PCCCH DL TBF ESTABLISHMENT PROCESS
Measurement Point
Unit
Times
113
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. The measurement point is A1, as shown in Figure 122.
FIGURE 122 MEASUREMENT POINT OF NUMBER TBF RELEASE DUE TO N3105 OVERFLOW
OF
GPRS DL SIGNALING
Unit
Times
114
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. The measurement point is A1, as shown in Figure 123.
FIGURE 123 MEASUREMENT POINT DUE TO OTHER REASONS
OF
Measurement Point
NUMBER
OF
Unit
Times
When the user plane is transmitting the GPRS signaling DL TBF, if a release request comes from the control plane, then the GPRS signaling DL TBF will stop and be released abnormally.
115
Measurement Point
When the user plane receives the release request from the control plane, this counter increments. The measurement point is A, as shown in Figure 124.
FIGURE 124 MEASUREMENT POINT RELEASE BY CONTROL PLANE
OF
NUMBER
OF
Unit
Times
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. When the DL block assigning timer expires, this counter increments. The measurement point is A, as shown in Figure 125.
Measurement Point
116
OF
NUMBER
OF
Unit
Times
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. 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. Times
Measurement Point
Unit
117
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. The measurement point is A1, as shown in Figure 126.
FIGURE 126 MEASUREMENT POINT OF NUMBER TBF RELEASE DUE TO N3105 OVERFLOW
OF
EGPRS DL SIGNALING
Unit
Times
118
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
NUMBER
OF
Unit
Times
119
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. When the user plane receives the release request from the control plane, this counter increments. The measurement point is A, as shown in Figure 128.
FIGURE 128 MEASUREMENT POINT OF NUMBER FORCING RELEASE BY CONTROL PLANE
OF
Measurement Point
EGPRS DL TBF
Unit
Times
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. When the DL block assigning timer expires, this counter increments. The measurement point is A1, as shown in Figure 129.
Measurement Point
120
FIGURE DUE TO
OF
NUMBER
OF
Unit
Times
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. 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. Times
Measurement Point
Unit
121
If both MS and BSS support reestablishment in released state, BSS sets RRBP and sends Packet UL Ack message (FAI =1 and TBF Est = 1) to MS after receiving all RLC blocks from MS. If MS has no new data to send, MS returns Packet Ctrl Ack message to BSS. If MS has new data to send but no DL TBF is available, then TBF should be reestablished, with the following two cases to be considered: If system message indicates that Packet Control Ack is of AB mode, then MS sends Packet Control Ack message (Ctrl Ack bit is 00) to BSS, and BSS specifies single block resource for MS by Packet UL Assign message. Subsequent flow is same as that of TWO STEP access. If system message indicates that Packet Control Ack is of RLC/MAC mode, then MS sends Packet Resource Request message to BSS. Subsequent flow is same as that of TWO STEP access.
This counter records the number of reestablishment times of MS in released state. The measurement point is A, as shown in Figure 130 and Figure 131.
FIGURE 130 MEASUREMENT POINT ON NUMBER REESTABLISHMENTS IN RELEASED STATE (1)
OF
GPRS UL TBF
122
OF
GPRS UL TBF
Unit
Times
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. This counter records the number of reestablishing UL GPRS TBF in released state without having to request for resource. The measurement point is A, as shown in Figure 132.
FIGURE 132 MEASUREMENT POINT OF WITH EXISTING UL RESOURCE GPRS UL TBF ESTABLISHMENTS
Unit
Times
123
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 GPRS TBF on PACCH. The measurement point is A, as shown in Figure 133.
FIGURE 133 MEASUREMENT POINT OF NUMBER ESTABLISHING UL GPRS TBF ON PACCH
OF
REQUESTS
FOR
Unit
Times
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. This counter records the number of times of establishing EGPRS UL TBF on PACCH. When Packet DL Ack message with UL TBF establishment request is received, and the TBF type is EGPRS, the counter increments. Times
124
If both MS and BSS support reestablishment in released state, BSS sets RRBP and sends Packet UL Ack message (FAI =1 and TBF Est = 1) to MS after receiving all RLC blocks from MS. If MS has no new data to send, MS returns Packet Ctrl Ack message to BSS. If MS has new data to send but no DL TBF is available, then TBF should be reestablished, with the following two cases to be considered: If system message indicates that Packet Control Ack is of AB mode, then MS sends Packet Control Ack message (Ctrl Ack bit is 00) to BSS, and BSS specifies single block resource for MS by Packet UL Assign message. Subsequent flow is same as that of TWO STEP access. If system message indicates that Packet Control Ack is of RLC/MAC mode, then MS sends Packet Resource Request message to BSS. Subsequent flow is same as that of TWO STEP access.
This counter records the number of reestablishment times of MS in released state. The measurement point is A, as shown in Figure 134 and Figure 135.
FIGURE 134 MEASUREMENT POINT ON NUMBER REESTABLISHMENTS IN RELEASED STATE (1)
OF
EGPRS UL TBF
125
OF
EGPRS UL TBF
Unit
Times
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. This counter records the number of reestablishing UL EGPRS TBF in released state without having to request for resource. The measurement point is A, as shown in Figure 136.
FIGURE 136 MEASUREMENT POINT OF WITH EXISTING UL RESOURCE EGPRS UL TBF ESTABLISHMENTS
Unit
Times
126
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 EGPRS TBF on PACCH. The measurement point is A, as shown in Figure 137.
FIGURE 137 MEASUREMENT POINT OF NUMBER ESTABLISHING UL EGPRS TBF ON PACCH
OF
REQUESTS
FOR
Unit
Times
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. This counter records the number of requests for establishing EGPRS UL TBF on CCCH/PCCCH.
Usage
127
Measurement Point
EGPRS UL TBF
Unit
Times
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. 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. The counter increments when the following conditions are satisfied: When the service instance is performing CS service but fails to request for the radio channel The database initiates the dynamic PDCH collection
Usage
Measurement Point
Times ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-003 Full dynamic channel allocation on Um interface
128
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. This counter records the number of requests for establishing GPRS UL TBF on CCCH/PCCCH. The measurement point is A, as shown in Figure 139.
FIGURE 139 MEASUREMENT POINT OF NUMBER ESTABLISHMENT REQUESTS ON CCCH/PCCCH
OF
GPRS UL TBF
Unit
Times
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. This counter counts the number of requests to establish GPRS DL TBF on PACCH. When a request is sent to establish DL TBF on PACCH and the TBF type is GPRS, this counter increments. Times
129
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. This counter counts the number of requests to establish EGPRS DL TBF on PACCH. When a request is sent to establish DL TBF on PACCH and the TBF type is EGPRS, this counter increments. Times
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. This counter records the number of requests to establish GPRS UL TBF on PACCH. When Packet DL Ack message with UL TBF establishment request is received, and the TBF type is GPRS, this counter increments. Times
After BSC receives DownLink Ack message, it decides whether to send pending RLC block, to resend RLC block or to send new data
130
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 Measurement Point
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS1. 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 140.
FIGURE 140 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
DL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS2. 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 141.
131
OF
NUMBER
OF
DL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS3. 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 142.
FIGURE 142 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
DL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
132
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.
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS4. 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 143.
FIGURE 143 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
DL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
133
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 144.
FIGURE 144 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
DL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS6. 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 145.
FIGURE 145 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
DL RLC PENDING
134
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.
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS7. 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 146.
FIGURE 146 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
DL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
135
This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
Usage Measurement Point
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS8. 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 147.
FIGURE 147 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
DL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of DL pending RLC blocks sent on PDTCH, with coding method of MCS9. 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 148.
136
OF
NUMBER
OF
DL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS1. 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 149.
FIGURE 149 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
137
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.
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS2. 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 150.
FIGURE 150 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
138
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 151.
FIGURE 151 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS4. 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 152.
FIGURE 152 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
139
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.
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS5. 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 153.
FIGURE 153 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
140
This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
Usage Measurement Point
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS6. 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 154.
FIGURE 154 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS7. 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 155.
141
MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS8. 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 156.
FIGURE 156 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
142
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.
This counter counts the number of DL retransmitted RLC blocks sent on PDTCH, with coding method of MCS9. 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 157.
FIGURE 157 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
143
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 158.
FIGURE 158 MEASUREMENT POINT ON PDTCH
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of MCS2. 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 159.
FIGURE 159 MEASUREMENT POINT ON PDTCH
OF
NUMBER
OF
144
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.
The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of MCS3. 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 160.
FIGURE 160 MEASUREMENT POINT ON PDTCH
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
145
This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
Usage Measurement Point
The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of MCS4. 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 161.
FIGURE 161 MEASUREMENT POINT ON PDTCH
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of MCS5. 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 162.
146
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of MCS6. 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 163.
FIGURE 163 MEASUREMENT POINT ON PDTCH
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
147
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.
The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of MCS7. 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 164.
FIGURE 164 MEASUREMENT POINT ON PDTCH
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
148
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 165.
FIGURE 165 MEASUREMENT POINT ON PDTCH
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
The counter is used to review the status of DL first-transmitted RLC blocks sent by BSC on PDTCH, with coding method of MCS9. 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 166.
FIGURE 166 MEASUREMENT POINT ON PDTCH
OF
NUMBER
OF
149
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.
This counter counts the number of useful UL MCS1-coded pending RLC blocks received by BSC on PDTCH. When BSC receives MCS1-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 167.
FIGURE 167 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
UL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
150
This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
Usage Measurement Point
This counter counts the number of useful UL MCS2-coded pending RLC blocks received by BSC on PDTCH. When BSC receives MCS2-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 168.
FIGURE 168 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
UL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of useful UL MCS3-coded pending RLC blocks received by BSC on PDTCH. When BSC receives MCS3-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 169.
151
OF
NUMBER
OF
UL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of useful UL MCS4-coded pending RLC blocks received by BSC on PDTCH. When BSC receives MCS4-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 170.
FIGURE 170 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
UL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
152
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.
This counter counts the number of useful UL MCS5-coded pending RLC blocks received by BSC on PDTCH. When BSC receives MCS5-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 171.
FIGURE 171 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
UL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
153
Measurement Point
When BSC receives MCS6-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 172.
FIGURE 172 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
UL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of useful UL MCS7-coded pending RLC blocks received by BSC on PDTCH. When BSC receives MCS7-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 173.
FIGURE 173 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
UL RLC PENDING
154
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.
This counter counts the number of useful UL MCS8-coded pending RLC blocks received by BSC on PDTCH. When BSC receives MCS8-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 174.
FIGURE 174 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
UL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
155
This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
Usage Measurement Point
This counter counts the number of useful UL MCS9-coded pending RLC blocks received by BSC on PDTCH. When BSC receives MCS9-coded UL pending RLC block, the counter increments. The measurement point is A, as shown in Figure 175.
FIGURE 175 MEASUREMENT POINT BLOCKS ON PDTCH
OF
NUMBER
OF
UL RLC PENDING
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of useful UL MCS1-coded retransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS1-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 176.
156
MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of useful UL MCS2-coded retransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS2-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 177.
FIGURE 177 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
157
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.
This counter counts the number of useful UL MCS3-coded retransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS3-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 178.
FIGURE 178 MEASUREMENT POINT ON PDTCH
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
158
Measurement Point
When BSC receives MCS4-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 179.
FIGURE 179 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of useful UL MCS5-coded retransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS5-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 180.
FIGURE 180 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
159
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.
This counter counts the number of useful UL MCS6-coded retransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS6-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 181.
FIGURE 181 MEASUREMENT POINT ON PDTCH
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
160
This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
Usage Measurement Point
This counter counts the number of useful UL MCS7-coded retransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS7-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 182.
FIGURE 182 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of useful UL MCS8-coded retransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS8-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 183.
161
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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.
This counter counts the number of useful UL MCS9-coded retransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS9-coded UL retransmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 184.
FIGURE 184 MEASUREMENT POINT ON PDTCH
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
162
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 firsttransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
This counter counts the number of useful UL MCS1-coded firsttransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS1-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 185.
FIGURE 185 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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 firsttransmitted 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 firsttransmitted RLC blocks received by BSC on PDTCH.
163
Measurement Point
When BSC receives MCS2-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 186.
FIGURE 186 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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 firsttransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
This counter counts the number of useful UL MCS3-coded firsttransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS3-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 187.
FIGURE 187 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
164
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 firsttransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
This counter counts the number of useful UL MCS4-coded firsttransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS4-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 188.
FIGURE 188 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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 firsttransmitted RLC blocks received on PDTCH.
165
This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
Usage Measurement Point
This counter counts the number of useful UL MCS5-coded firsttransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS5-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 189.
FIGURE 189 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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 firsttransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
This counter counts the number of useful UL MCS6-coded firsttransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS6-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 190.
166
MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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 firsttransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
This counter counts the number of useful UL MCS7-coded firsttransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS7-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 191.
FIGURE 191 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
167
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 firsttransmitted RLC blocks received on PDTCH. This counter performs statistics for RLC layer, and the statistic result is the number of data blocks.
This counter counts the number of useful UL MCS8-coded firsttransmitted RLC blocks received by BSC on PDTCH. When BSC receives MCS8-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 192.
FIGURE 192 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
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 firsttransmitted 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 firsttransmitted RLC blocks received by BSC on PDTCH.
168
Measurement Point
When BSC receives MCS9-coded UL first-transmitted RLC block, the counter increments. The measurement point is A, as shown in Figure 193.
FIGURE 193 ON PDTCH MEASUREMENT POINT
OF
NUMBER
OF
Times ZGB-03-05-015 RLC Acknowledged/Unacknowledged Mode ZGO-03-05-001 Modulation and Coding Scheme #1~#9
This counter counts the total uplink GPRS throughput after the UPPB board receives uplink data blocks. When the URLC module of the UPPB board receives data blocks in extension status or transmission status changes to extension or delay status and when the TBF type is GPRS, the counter multiplies the throughput and transmission bytes of each uplink TBF. This counter counts the throughput of uplink GPRS TBF. The counter is updated when the URLC module receives uplink data blocks. The measurement point is A, as shown in Figure 194.
FIGURE 194 MEASUREMENT POINT
OF
Unit
kBps * kB
169
This counter counts the total downlink GPRS throughput after the UPPB board receives the Packet DownLink Ack message. After the DRLC module of the UPPB board receives the message, the counter multiplies the throughput and transmission bytes of each downlink TBF if the module changes from transmission status to delay status and the TBF type is GPRS. This counter counts the throughput of downlink GPRS TBF. The counter is updated when the DRLC module receives the Packet DownLink Ack message. The measurement point is A, as shown in Figure 195.
FIGURE 195 MEASUREMENT POINT
OF
Unit
kBps * kB
This counter counts the total uplink EGPRS throughput after the UPPB board receives uplink data blocks. When the URLC module of the UPPB board receives data blocks in extension status or transmission status changes to extension or delay status and when the TBF type is EGPRS, the counter multiplies the throughput and transmission bytes of each uplink TBF. This counter counts the throughput of uplink EGPRS TBF. The counter is updated when the URLC module receives uplink data blocks. The measurement point is A, as shown in Figure 196.
170
OF
Unit
kBps * kB
This counter counts the total downlink EGPRS throughput after the UPPB board receives the EGPRS Packet DownLink Ack message. After the DRLC module of the UPPB board receives the message, the counter multiplies the throughput and transmission bytes of each downlink TBF if the module changes from transmission status to delay status and the TBF type is EGPRS. This counter counts the throughput of downlink EGPRS TBF. The counter is updated when the DRLC module receives the EGPRS Packet DownLink Ack message. The measurement point is A, as shown in Figure 197.
FIGURE 197 MEASUREMENT POINT OF DOWNLINK EGPRS TBF THROUGHPUT
Unit
kBps * kB
171
172
Chapter
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.
This counter counts the average load of the main processor during measurement period. After a collection period ends, calculation will be executed according to the sampling load of the main processor. Percent
This counter counts the peak value of the main processor load during measurement period. The measurement point is the peak value of the sampling main processor load during collection period. Percent
173
174
Chapter
CS Basic Measurement
Table of Contents Overview........................................................................ 182 C900060001 Number of MTC access attempts ..................... 183 C900060002 Number of MTC access success ....................... 183 C900060003 Number of SDCCH seizure attempts for assignment ............................................................................. 184 C900060004 Number of SDCCH seizure success for assignment ............................................................................. 185 C900060005 Number of SDCCH seizure failure for assignment ............................................................................. 186 C900060006 Number of SDCCH seizure attempts for handover............................................................................. 187 C900060007 Number of SDCCH seizure failure for handover............................................................................. 189 C900060008 Number of SDCCH allocation success for assignment ............................................................................. 190 C900060009 Number of SDCCH allocation failure for assignment ............................................................................. 191 C900060010 Number of signaling TCH/F seizure attempts for assignment..................................................................... 192 C900060011 Number of signaling TCH/F seizure failure for assignment..................................................................... 193 C900060012 Number of signaling TCH/F seizure attempts for handover........................................................................ 194 C900060013 Number of signaling TCH/F seizure failure for handover........................................................................ 197 C900060014 Number of signaling TCH/F allocation success for assignment..................................................................... 198 C900060015 Number of signaling TCH/F allocation failure for assignment..................................................................... 198 C900060016 Number of signaling TCH/F allocation failure for handover........................................................................ 199 C900060017 Number of signaling TCH/F assignment success for assignment ................................................................ 200 C900060018 Number of signaling TCH/F assignment failure for assignment ................................................................ 201 C900060019 Number of voice TCH/F seizure attempts for assignment........................................................................ 202 C900060020 Number of voice TCH/F seizure failure for assignment........................................................................ 204 C900060021 Number of voice TCH/F seizure attempts for handover........................................................................ 205 C900060022 Number of voice TCH/F seizure failure for handover............................................................................. 208 C900060023 Number of TCH/F allocation success for assignment (speech version1).................................................... 209
175
C900060024 Number of TCH/F allocation failure due to channel activation failure for assignment (speech version1) ......... 210 C900060025 Number of TCH/F allocation success for assignment (speech version2).................................................... 211 C900060026 Number of TCH/F allocation success for assignment (speech version3).................................................... 212 C900060027 Number of TCH/F allocation failure due to channel activation failure for assignment (speech version3) ......... 214 C900060028 Number of voice TCH/F assignment success............................................................................... 215 C900060029 Number of voice TCH/F assignment failure for assignment..................................................................... 216 C900060030 Number of data TCH/F seizure attempts for assignment........................................................................ 217 C900060031 Number of data TCH/F seizure failure for assignment ............................................................................. 219 C900060032 Number of data TCH/F seizure attempts for handover............................................................................. 220 C900060033 Number of data TCH/F seizure failure for handover............................................................................. 223 C900060034 Number of data TCH/F allocation success for assignment........................................................................ 224 C900060035 Number of data TCH/F allocation failure due to channel activation failure for assignment ............................ 225 C900060036 Number of data TCH/F assignment success............................................................................... 226 C900060037 Number of data TCH/F assignment failure ......... 227 C900060038 Number of signaling TCH/H seizure attempts for assignment..................................................................... 228 C900060039 Number of signaling TCH/H seizure failure for assignment..................................................................... 229 C900060040 Number of signaling TCH/H seizure attempts for handover........................................................................ 230 C900060041 Number of signaling TCH/H seizure failure for handover........................................................................ 233 C900060042 Number of voice TCH/H seizure attempts for assignment........................................................................ 234 C900060043 Number of voice TCH/H seizure failure for assignment........................................................................ 236 C900060044 Number of voice TCH/H seizure attempts for handover........................................................................ 237 C900060045 Number of voice TCH/H seizure failure for handover............................................................................. 240 C900060046 Number of data TCH/H seizure attempts for assignment........................................................................ 241 C900060047 Number of data TCH/H seizure failure for assignment ............................................................................. 243 C900060048 Number of data TCH/H seizure attempts for handover............................................................................. 244 C900060049 Number of data TCH/H seizure failure for handover............................................................................. 247 C900060050 Number of SAPI3 link establishment requests on SDCCH (MO-SM) ............................................................. 248 C900060051 Number of SAPI3 link establishment requests on SDCCH (MT-SM).............................................................. 250 C900060052 Number of SDCCH drops due to handover failure ................................................................................ 251 C900060053 Number of SDCCH drops................................ 253 C900060054 Number of TCH/F drops ................................. 254 C900060055 Number of TCH/H drops................................. 254
176
C900060056 Average number of idle TCH/F with interference band 1 ........................................................................... 255 C900060057 Average number of idle TCH/F with interference band 2 ........................................................................... 255 C900060058 Average number of idle TCH/F with interference band 3 ........................................................................... 255 C900060059 Average number of idle TCH/F with interference band 4 ........................................................................... 256 C900060060 Average number of idle TCH/F with interference band 5 ........................................................................... 256 C900060061 Average number of idle TCH/H with interference band 1 ........................................................................... 257 C900060062 Average number of idle TCH/H with interference band 2 ........................................................................... 257 C900060063 Average number of idle TCH/H with interference band 3 ........................................................................... 258 C900060064 Average number of idle TCH/H with interference band 4 ........................................................................... 258 C900060065 Average number of idle TCH/H with interference band 5 ........................................................................... 259 C900060066 Number of samples with UL RQ = 0 ................. 259 C900060067 Number of samples with UL RQ = 1 ................. 259 C900060068 Number of samples with UL RQ = 2 ................. 260 C900060069 Number of samples with UL RQ = 3 ................. 260 C900060070 Number of samples with UL RQ = 4 ................. 260 C900060071 Number of samples with UL RQ = 5 ................. 261 C900060072 Number of samples with UL RQ = 6 ................. 261 C900060073 Number of samples with UL RQ = 7 ................. 261 C900060074 Number of samples with DL RQ = 0................. 262 C900060075 Number of samples with DL RQ = 1................. 262 C900060076 Number of samples with DL RQ = 2................. 262 C900060077 Number of samples with DL RQ = 3................. 263 C900060078 Number of samples with DL RQ = 4................. 263 C900060079 Number of samples with DL RQ = 5................. 263 C900060080 Number of samples with DL RQ = 6................. 264 C900060081 Number of samples with DL RQ = 7................. 264 C900060082 Number of TCH/F handover attempts due to UL strength ......................................................................... 264 C900060083 Number of TCH/F handover attempts due to DL strength ......................................................................... 265 C900060084 Number of TCH/F handover attempts due to UL quality ........................................................................... 266 C900060085 Number of TCH/F handover attempts due to DL quality ........................................................................... 266 C900060086 Number of TCH/F handover attempts due to UL interference .................................................................... 267 C900060087 Number of TCH/F handover attempts due to DL interference .................................................................... 268 C900060088 Number of TCH/F handover attempts due to good C/I ........................................................................ 268 C900060089 Number of TCH/F handover attempts due to bad C/I ................................................................................ 269 C900060090 Number of TCH/F handover attempts due to PBGT ............................................................................. 270 C900060091 Number of TCH/F handover attempts due to large TA ......................................................................... 270 C900060092 Number of TCH/F handover attempts due to other reasons.................................................................. 271 C900060093 Number of BSC-controlled inter-cell outgoing handover........................................................................ 272
177
C900060094 Number of BSC-controlled inter-cell outgoing handover success ............................................................ 273 C900060095 Number of MSC-controlled outgoing handover .............................................................................. 273 C900060096 Number of MSC-controlled outgoing handover success .......................................................................... 274 C900060097 Number of BSC-controlled inter-cell incoming handover........................................................................ 275 C900060098 Number of BSC-controlled inter-cell incoming handover success ............................................................ 276 C900060099 Number of MSC-controlled incoming handover............................................................................. 276 C900060100 Number of MSC-controlled incoming handover due to forced release ....................................................... 277 C900060101 Number of MSC-controlled incoming handover due to queue .................................................................. 278 C900060102 Number of MSC-controlled incoming handover success .......................................................................... 279 C900060103 Number of incoming handover from undefined layer (GSM900) to current layer(GSM1800) ........................ 280 C900060104 Number of incoming handover success from undefined layer(GSM900) to current layer (GSM1800) ............. 281 C900060105 Number of incoming handover from undefined layer (GSM1800) to current layer (GSM900) ....................... 282 C900060106 Number of incoming handover success from undefined layer(GSM1800) to current layer(GSM900) .............. 283 C900060107 Number of incoming handover from the same layer GSM900 to GSM1800 ............................................... 284 C900060108 Number of incoming handover success from the same layer GSM900 to GSM1800 ....................................... 284 C900060109 Number of incoming handover from GSM900 to GSM1800 from the upper layer.......................................... 285 C900060110 Number of incoming handover success from GSM900 to GSM1800 in the upper layer ............................. 286 C900060111 Number of incoming handover from GSM900 to GSM1800 in the lower layer .............................................. 287 C900060112 Number of incoming handover success from GSM900 to GSM1800 in the lower layer .............................. 288 C900060113 Number of incoming handover from GSM1800 to GSM900 from the same layer ........................................ 289 C900060114 Number of incoming handover success from GSM1800 to GSM900 from the same layer .......................... 290 C900060115 Number of incoming handover from GSM1800 to GSM900 from the upper layer........................................ 291 C900060116 Number of incoming handover success from GSM1800 to GSM900 from the upper layer ......................... 292 C900060117 Number of incoming handover from GSM1800 to GSM900 from the lower layer ........................................ 293 C900060118 Number of incoming handover success from GSM1800 to GSM900 from the lower layer .......................... 294 C900060119 Number of Intra-cell handover ........................ 294 C900060120 Number of Intra-cell handover success ............ 295 C900060121 Maximum number of busy TCH/H .................... 296 C900060122 Average number of available SDCCH................ 297 C900060123 Average number of unavailable SDCCH ............ 297 C900060124 SDCCH busy time ......................................... 298 C900060125 Average number of available radio channel ................................................................................ 299 C900060126 Average number of unavailable radio channel ................................................................................ 300
178
C900060127 TCH/H busy time .......................................... 300 C900060128 Maximum number of busy TCH/F .................... 301 C900060129 TCH/F busy time ........................................... 302 C900060130 Number of healthy TRXs ................................ 303 C900060131 Number of CM service requests of MOC............ 304 C900060132 Number of SAPI3 link establishment success on SDCCH (MT-SM).............................................................. 305 C900060133 Number of available defined SDCCH ................ 306 C900060134 Number of available defined TCH/F.................. 306 C900060135 Number of signaling TCH/H assignment failure ................................................................................ 307 C900060136 Number of MOC access attempts..................... 308 C900060137 Number of wireless access due to paging responses ......................................................................... 309 C900060138 Number of TCH/F allocation failure due to BTS connection failure for assignment (speech version1)............. 310 C900060139 Number of TCH/F allocation failure due to BIU connection failure for assignment (speech version1)............. 311 C900060140 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version1)............. 312 C900060141 Number of TCH/F allocation failure due to channel activation failure for assignment (speech version2) ......... 313 C900060142 Number of TCH/F allocation failure due to BTS connection failure for assignment (speech version2)............. 314 C900060143 Number of TCH/F allocation failure due to BIU connection failure for assignment (speech version2)............. 315 C900060144 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version2)............. 316 C900060145 Number of TCH/F allocation failure due to BTS connection failure for assignment (speech version3)............. 317 C900060146 Number of TCH/F allocation failure due to BIU connection failure for assignment (speech version3)............. 318 C900060147 Number of TCH/F allocation failure due to TCU connection failure for assignment (speech version3)............. 319 C900060148 Number of data TCH/F allocation failure due to BTS connection failure for assignment) ............................... 320 C900060149 Number of data TCH/F allocation failure due to BIU connection failure for assignment ................................ 320 C900060150 Number of data TCH/F allocation failure due to TCU connection failure for assignment ................................ 321 C900060151 Number of voice TCH/H drops due to handover failure ............................................................................ 322 C900060152 Number of Abis interface paging command messages............................................................................. 324 C900060153 Number of Abis CS paging messages ............... 325 C900060154 Number of Abis PS paging messages ............... 325 C900060155 Number of available defined TCH/H ................. 326 C900060156 Number of TCH/F allocation failure due to channel activation failure for handover(speech version1) ............. 327 C900060157 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version1)................ 328 C900060158 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version1)................ 329 C900060159 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version1)................ 330 C900060160 Number of TCH/F allocation failure due to channel activation failure for handover(speech version2) ............. 332 C900060161 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version2)................ 333
179
C900060162 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version2)................ 334 C900060163 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version2)................ 335 C900060164 Number of TCH/F allocation failure due to channel activation failure for handover (speech version3) ............ 336 C900060165 Number of TCH/F allocation failure due to BTS connection failure for handover (speech version3)................ 338 C900060166 Number of TCH/F allocation failure due to BIU connection failure for handover (speech version3)................ 339 C900060167 Number of TCH/F allocation failure due to TCU connection failure for handover (speech version3)................ 340 C900060168 Number of Voice TCH/F handover success ......... 341 C900060169 Number of data TCH/F allocation failure due to channel activation failure for handover ............................... 343 C900060170 Number of data TCH/F allocation failure due to BTS connection failure for handover ................................... 344 C900060171 Number of data TCH/F allocation failure due to BIU connection failure for handover ................................... 345 C900060172 Number of data TCH/F allocation failure due to TCU connection failure for handover ................................... 346 C900060173 Number of data TCH/F handover success ......... 347 C900060174 Number of signaling TCH/H allocation failure for assignment..................................................................... 350 C900060175 Number of TCH/H allocation failure due to channel activation failure for assignment (speech version1) ......... 351 C900060176 Number of TCH/H allocation failure due to BTS connection failure for assignment (speech version1)............. 352 C900060177 Number of TCH/H allocation failure due to BIU connection failure for assignment (speech version1)............. 353 C900060178 Number of TCH/H allocation failure due to TCU connection failure for assignment (speech version1)............. 354 C900060179 Number of TCH/H allocation failure due to channel activation failure for handover (speech version1) ............ 355 C900060180 Number of TCH/H allocation failure due to BTS connection failure for handover (speech version1)................ 356 C900060181 Number of TCH/H allocation failure due to BIU connection failure for handover (speech version1)................ 357 C900060182 Number of TCH/H allocation failure due to TCU connection failure for handover (speech version1)................ 358 C900060183 Number of TCH/H allocation failure due to channel activation failure for assignment (speech version2) ......... 360 C900060184 Number of TCH/H allocation failure due to BTS connection failure for assignment (speech version2)............. 361 C900060185 Number of TCH/H allocation failure due to BIU connection failure for assignment (speech version2)............. 362 C900060186 Number of TCH/H allocation failure due to TCU connection failure for assignment (speech version2)............. 363 C900060187 Number of TCH/H allocation failure due to channel activation failure for handover (speech version2) ............ 364 C900060188 Number of TCH/H allocation failure due to BTS connection failure for handover (speech version2)................ 365 C900060189 Number of TCH/H allocation failure due to BIU connection failure for handover (speech version2)................ 366 C900060190 Number of TCH/H allocation failure due to TCU connection failure for handover (speech version2)................ 367 C900060191 Number of TCH/H allocation failure due to channel activation failure for assignment (speech version3) ......... 369 C900060192 Number of TCH/H allocation failure due to BTS connection failure for assignment (speech version3)............. 370
180
C900060193 Number of TCH/H allocation failure due to BIU connection failure for assignment (speech version3)............. 371 C900060194 Number of TCH/H allocation failure due to TCU connection failure for assignment (speech version3)............. 372 C900060195 Number of TCH/H allocation failure due to channel activation failure for handover (speech version3) ............ 373 C900060196 Number of TCH/H allocation failure due to BTS connection failure for handover (speech version3)................ 374 C900060197 Number of TCH/H allocation failure due to BIU connection failure for handover (speech version3)................ 375 C900060198 Number of TCH/H allocation failure due to TCU connection failure for handover (speech version3)................ 376 C900060199 Number of Voice TCH/H assignment success............................................................................... 378 C900060200 Number of Voice TCH/H assignment failure ................................................................................ 379 C900060201 Number of Voice TCH/H handover success ......... 380 C900060202 Number of data TCH/H allocation failure due to channel activation failure for assignment ............................ 383 C900060203 Number of data TCH/H allocation failure due to BTS connection failure for assignment ................................ 384 C900060204 Number of data TCH/H allocation failure due to BIU connection failure for assignment ................................ 384 C900060205 Number of data TCH/H allocation failure due to TCU connection failure for assignment ................................ 385 C900060206 Number of data TCH/H allocation failure due to channel activation failure for handover ............................... 386 C900060207 Number of data TCH/H allocation failure due to BTS connection failure for handover ................................... 387 C900060208 Number of data TCH/H allocation failure due to BIU connection failure for handover ................................... 388 C900060209 Number of data TCH/H allocation failure due to TCU connection failure for handover ................................... 389 C900060210 Number of data TCH/H assignment success............................................................................... 390 C900060211 Number of data TCH/H assignment failure ......... 392 C900060212 Number of data TCH/H handover success ......... 392 C900060213 Number of BSC-controlled incoming handover due to forced release ....................................................... 395 C900060214 Number of BSC-controlled incoming handover due to queues ................................................................. 396 C900060215 Number of BSC-controlled incoming handover due to forced handover .................................................... 397 C900060216 Number of MSC-controlled incoming handover due to forced handover .................................................... 398 C900060217 Number of unavailable defined TCH/H.............. 398 C900060218 Number of unavailable defined TCH/F .............. 399 C900060219 Number of signaling TCH/F drops due to handover failure ................................................................... 400 C900060220 Number of voice TCH/F drops due to handover failure ............................................................................ 402 C900060221 Number of data TCH/F drops due to handover failure ............................................................................ 403 C900060222 Number of signaling TCH/H drops due to handover failure ................................................................... 406 C900060223 Number of data TCH/H drops due to handover failure ............................................................................ 408 C900060224 Number of TCH/H handover attempts due to UL strength ......................................................................... 410
181
C900060225 Number of TCH/H handover attempts due to DL strength ......................................................................... 410 C900060226 Number of TCH/H handover attempts due to UL quality ........................................................................... 411 C900060227 Number of TCH/H handover attempts due to DL quality ........................................................................... 412 C900060228 Number of TCH/H handover attempts due to UL interference .................................................................... 412 C900060229 Number of TCH/H handover attempts due to DL interference .................................................................... 413 C900060230 Number of TCH/H inter-subcell handover attempts due to good C/I .................................................... 414 C900060231 Number of TCH/H inter-subcell handover attempts due to bad C/I ...................................................... 414 C900060232 Number of TCH/H handover attempts due to PBGT ............................................................................. 415 C900060233 Number of TCH/H handover attempts due to large TA ......................................................................... 416 C900060234 Number of TCH/H handover attempts due to other reasons.................................................................. 417 C900060235 Number of signaling TCH/H assignment success............................................................................... 417 C900060236 Number of MOC access success ...................... 418 C900060237 Number of dual band outgoing handover .......... 419 C900060238 Number of dual band outgoing handover success............................................................................... 420 C900060239 Number of dual band incoming handover ......... 421 C900060240 Number of dual band incoming handover success............................................................................... 421 C900060241 Number of SDCCH assignment attempts .......... 422 C900060242 Number of SDCCH assignments success........... 423 C900060243 Number of SDCCH assignment failure .............. 424 C900060244 Number of voice TCH/F drops due to radio link failure ............................................................................ 425 C900060245 Number of voice TCH/H drops due to radio link failure ............................................................................ 426
Overview
CS basic measurement involves counters that are used to evaluate the circuit switching service performance and status. These counters are often used in measurement related to radio access, SDCCH, TCH, SAPI3, call drop, handover, Abis interface message statistics, and radio resource availability. The measurement takes cell as the statistics unit.
182
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. This counter is used to find out the frequency of channel request due to MTC. 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 198.
FIGURE 198 RADIO ACCESS FLOW
Unit
Times
This counter counts the number of MS successfully accessing the channel assigned in the immediate assignment message (the access reason is due to MTC). The counter increments when the following two conditions are satisfied: MS receives the IMM_ASS message from BSC and successfully accesses the channel.
183
This counter is used to find out the frequency of MS access success due to MTC. This counter counts when BSC receives the EST_IND message. The measurement point is A4, as shown in Figure 199.
FIGURE 199 RADIO ACCESS FLOW
Unit
Times
SDCCH channel allocation attempt is activated by the MS channel request message CHL_REQ. After BSC receives this message, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060004 accumulate simultaneously. C900060003 and
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).
184
Measurement Point
This counter counts when BSC completes requesting for channel (due to assignment) (C900060004 + C900060005). The measurement point is A1, as shown in Figure 200.
FIGURE 200 IMMEDIATE ASSIGNMENT FLOW
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. This counter counts the number of successful SDCCH channel occupations during assignment. This counter counts when BSC requests for channel (due to assignment) and occupies the channel successfully. The measurement point is A1, as shown in Figure 201.
185
SDCCH channel allocation attempt is activated by the MS channel request message CHL_REQ. After BSC receives this message, it attempts to allocate channel for the request. If allocation succeeds but occupation fails, this counter accumulates. If the request returns that the transceiver is faulty, this counter does not change. For failures in other cases, this counter accumulates.
This counter counts the number of SDCCH channel occupation failures during assignment. This counter counts when BSC requests for channel (due to assignment) but fails to occupy the channel. The measurement point is A1, as shown in Figure 202.
186
SDCCH channel allocation attempt is activated by the channel request message RADIO_APPLY from other channel instances. After BSC receives this message, it attempts to allocate channel for the request. If allocation and occupation succeed, C901250005 accumulate simultaneously. C900060006 and
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.
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.
187
Usage
This counter counts the number of SDCCH channel occupation attempts during handover, including the number of occupation success (C900060006) and the number of occupation failure (C900060007). BSC completes requesting for channel (due to handover), or BSC receives the internal message of waiting for resource successfully or waiting for resource failed (C901250005 + C900060007). The measurement point is B1 as shown in Figure 203 and C1 as shown in Figure 204.
FIGURE 203 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER)
Measurement Point
Unit
Times
188
Related Features
SDCCH channel allocation attempt is activated by the channel request message RADIO_APPLY from other channel instances. After BSC receives this message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates. 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.
Usage Measurement Point
This counter counts the number of SDCCH occupation failure. BSC requests for channel (due to handover) but fails to occupy the channel, or BSC fails to wait for internal resource. The measurement point is B1 as shown in Figure 205 and C1 as shown in Figure 206.
FIGURE 205 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER)
189
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. This counter counts the number of successful SDCCH channel allocations during assignment. 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 207.
190
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. This counter counts the number of SDCCH channel allocation failure during assignment. 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 208.
191
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). After BSC receives the channel request, it attempts to allocate channel for the request. If allocation and occupation succeed, C901260002 accumulate simultaneously. C900060010 and
Usage
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 209.
192
Times 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
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. 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 210.
193
Times 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
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. If allocation and occupation succeed, C901260005 accumulate simultaneously. C900060012 and
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.
Measurement Point
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.
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
194
point is C1 as shown in Figure 211 and Figure 212, and D1 as shown in Figure 213 and Figure 214.
FIGURE 211 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, TC IS INTERNAL)
FIGURE 212 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, CHANNEL TYPE CHANGED, TC IS EXTERNAL)
195
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation
196
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. 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.
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 215 and D1 as shown in Figure 216.
FIGURE 215 INTRA-BSC HANDOVER OCCUPATION FAILURE FLOW
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation
197
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 217.
FIGURE 217 IMMEDIATE ASSIGNMENT FLOW
Times ZGB-03-01-004 Immediate TCH Assignment ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
This counter counts the number of TCH/F channel allocation failures during signaling channel assignment.
198
After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F channel. If the channel activation fails due to receiving channel activation failure message, incorrect channel activation response message, T9103 timeout, channel instance being released or channel being released forcibly, this counter accumulates.
Measurement Point
BSC activates TCH/F channel due to assignment and uses it as signaling channel, but receives channel activation failure message, incorrect channel activation response message, T9103 being timeout, channel instance being released, or channel being forcibly released. The measurement point is A2, as shown in Figure 218.
FIGURE 218 IMMEDIATE ASSIGNMENT ALLOCATION FAILURE FLOW 2
Times ZGB-03-01-004 Immediate TCH Assignment ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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.
199
The measurement point is C3 as shown in Figure 219 and D3 as shown in Figure 220.
FIGURE 219 INTERNAL HANDOVER FAILURE FLOW 1 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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.
200
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 221.
FIGURE 221 IMMEDIATE ASSIGNMENT FLOW
Times ZGB-03-01-004 Immediate TCH Assignment ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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 222.
201
Times ZGB-03-01-004 Immediate TCH Assignment ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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. If allocation and occupation succeed, C901260021 accumulate simultaneously. C900060019 and
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.
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.
202
Measurement Point
BSC completes requesting for channel (due to assignment and the channel is used as voice channel), or BSC receives the internal message of waiting for resource successfully or waiting for resource failed (C901260021 + C900060020). The measurement point is B1, as shown in Figure 223 and Figure 224. .
FIGURE 223 COMMON ASSIGNMENT FLOW (TC IS INTERNAL)
Times 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
203
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. 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.
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 225.
FIGURE 225 COMMON ASSIGNMENT FAILURE FLOW 1 (TC IS INTERNAL)
Times 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
204
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. If allocation and occupation succeed, C901260024 accumulate simultaneously. C900060021 and
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.
Measurement Point
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.
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 226 and Figure 227, and D1 as shown in Figure 228 and Figure 229.
205
FIGURE 227 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, CHANNEL TYPE CHANGED, TC IS EXTERNAL)
206
Times 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
207
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. 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.
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 230 and D1 as shown in Figure 231.
FIGURE 230 INTRA-BSC HANDOVER OCCUPATION FAILURE FLOW
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation
208
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 232 and Figure 233.
FIGURE 232 COMMON ASSIGNMENT FLOW (TC IS INTERNAL)
209
Times ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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 234.
210
Times ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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 235 and Figure 236.
211
This counter counts the number of TCH/F channel being allocated successfully during voice channel assignment (speech version 3).
212
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 237 and Figure 238.
FIGURE 237 COMMON ASSIGNMENT FLOW (TC IS INTERNAL)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)
213
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 239.
FIGURE 239 COMMON ASSIGNMENT FAILURE FLOW 1 (TC IS INTERNAL)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)
214
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 240 and Figure 241.
FIGURE 240 COMMON ASSIGNMENT FLOW (TC IS INTERNAL)
215
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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 242.
216
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. If allocation and occupation succeed, C901260070 accumulate simultaneously. C900060030 and
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.
If the request returns that the transceiver is faulty, C900060030, C901260070, and C900060031 do not change.
217
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 243 and Figure 244.
FIGURE 243 COMMON ASSIGNMENT FLOW (TC IS INTERNAL)
Times 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
218
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. 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.
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 245.
FIGURE 245 COMMON ASSIGNMENT FAILURE FLOW 1 (TC IS INTERNAL)
Times 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
219
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. If allocation and occupation succeed, C901260073 accumulate simultaneously. C900060032 and
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.
Measurement Point
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.
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 246 and Figure 247, and D1 as shown in Figure 248 and Figure 249.
220
FIGURE 247 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, CHANNEL TYPE CHANGED, TC IS EXTERNAL)
221
Times 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
222
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. 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.
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 250 and D1 as shown in Figure 251.
FIGURE 250 INTRA-BSC HANDOVER OCCUPATION FAILURE FLOW
Times 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
223
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 252 and Figure 253.
FIGURE 252 COMMON ASSIGNMENT FLOW (TC IS INTERNAL)
224
Times ZGB-01-03-002 Data Traffic Channels ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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 254.
225
Times ZGB-01-03-002 Data Traffic Channels ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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 255 and Figure 256.
226
Times ZGB-01-03-002 Data Traffic Channels ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
This counter counts the number of failing to assign TCH/F channel as data channel.
227
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 257.
FIGURE 257 COMMON ASSIGNMENT FAILURE FLOW 4 (TC IS INTERNAL)
Times ZGB-01-03-002 Data Traffic Channels ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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. If allocation and occupation succeed, C901270002 accumulate simultaneously. C900060038 and
If the request returns that the transceiver is faulty, C900060038, C901270002, and C900060039 do not change.
228
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 258.
FIGURE 258 IMMEDIATE ASSIGNMENT FLOW
Times 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
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. 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
229
fails to wait for internal resource. The measurement point is A1, as shown in Figure 259.
FIGURE 259 IMMEDIATE ASSIGNMENT OCCUPATION FAILURE FLOW 1
Times 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
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. If allocation and occupation succeed, C901270005 accumulate simultaneously. C900060040 and
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.
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.
230
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 260 and Figure 261, and D1 as shown in Figure 262 and Figure 263.
FIGURE 260 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, TC IS INTERNAL)
FIGURE 261 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, CHANNEL TYPE CHANGED, TC IS EXTERNAL)
231
Times 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
232
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. 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.
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 264 and D1 as shown in Figure 265.
FIGURE 264 INTRA-BSC HANDOVER OCCUPATION FAILURE FLOW
Times 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
233
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. If allocation and occupation succeed, C901270021 accumulate simultaneously. C900060042 and
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.
Measurement Point
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.
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 266 and Figure 267.
234
Times 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
235
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. 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.
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 268.
FIGURE 268 COMMON ASSIGNMENT FAILURE FLOW 1 (TC IS INTERNAL)
Times 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
236
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. If allocation and occupation succeed, C901270024 accumulate simultaneously. C900060044 and
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.
Measurement Point
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.
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 269 and Figure 270, and D1 as shown in Figure 271 and Figure 272.
237
FIGURE 270 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, CHANNEL TYPE CHANGED, TC IS EXTERNAL)
238
Times 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
239
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. 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.
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 273 and D1 as shown in Figure 274.
FIGURE 273 INTRA-BSC HANDOVER OCCUPATION FAILURE FLOW
Times 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
240
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. If allocation and occupation succeed, C901270070 accumulate simultaneously. C900060046 and
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.
Measurement Point
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.
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 275 and Figure 276.
241
Times 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
242
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. 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.
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 277.
FIGURE 277 COMMON ASSIGNMENT FAILURE FLOW 1 (TC IS INTERNAL)
Times 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
243
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. If allocation and occupation succeed, C901270073 accumulate simultaneously. C900060048 and
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.
Measurement Point
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.
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 278 and Figure 279, and D1 as shown in Figure 280 and Figure 281.
244
FIGURE 279 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, CHANNEL TYPE CHANGED, TC IS EXTERNAL)
245
Times 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
246
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. 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.
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 282 and D1 as shown in Figure 283.
FIGURE 282 INTRA-BSC HANDOVER OCCUPATION FAILURE FLOW
Times 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
247
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. This counter is used to find out the frequency of SAPI 3 link establishment on SDCCH. This counter counts when BSC receives the EST_IND message (SAPI = 3) from BTS. The measurement point is B1, as shown in Figure 284.
248
249
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. This counter is used to find out the frequency of SAPI 3 link establishment request on SDCCH. This counter counts when BSC sends the EST_REQ message (SAPI = 3) to BTS and the short message link is not established between BSC and MS. The measurement point is D1, as shown in Figure 285.
250
This counter counts the number of call drops due to handover failure on SDCCH. Call drop occurs after MS requests for SDCCH successfully. If the problem is due to handover failure, this counter increments. Presently, reasons for handover failure include T3107 timeout, T3103 timeout and external handover timer timeout under the status of ASSIGNING.
251
T3107 indicates the duration from sending the intra-cell handover command ASSIGN_CMD to receiving the assignment completion message ASSIGN_COM. T3103 indicates the duration from sending the inter-cell handover command HOINTER_CMD to receiving the assignment completion message HOINTER_COM. The external handover timer indicates the duration from sending the inter-cell external handover command to receiving the handover completion message.
Usage Measurement Point
This counter is used to find out the frequency of call drop due to handover failure on SDCCH. SDCCH is activated after BSC initiates the handover flow. After that: If RANCS is in the status of RADIO_APPLY and sends the intracell handover command, then T3107 is started. If RANCS is in the status of ASSIGN and T3107 is timeout, then the counter increments. The measurement point is A, as shown in Figure 286.
FIGURE 286 CALL DROP HANDOVER
DUE TO
If RANCS is in the status of RADIO_APPLY and sends the intercell 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 287.
252
DUE TO
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.
This counter counts the number of call drops on SDCCH channel due to radio link failure, LAPD link break, or handover failure. Call drop occurs after MS requests for TCH/H channel successfully. The counter increments if call drop is due to the above causes. This counter is used to find out the frequency of call drop on SDCCH channel due to radio link failure, LAPD link break, or handover failure. This counter increments when call drop occurs on SDCCH channel due to radio link failure, LAPD link failure, or handover failure. Times ZGB-06-01-007 Cell Traffic Statistics
Usage
253
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. 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. The counter increments when call drop occurs on TCH/F channel due to radio link failure, LAPD link failure, or handover failure. Times ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
Usage
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. 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. The counter increments when call drop occurs on TCH/H channel due to radio link failure, LAPD link failure, or handover failure. Times ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
Usage
254
This counter counts the number of idle TCH/Fs with interference band 1 in the carrier. This counter is used to find out the number of idle TCH/Fs with interference band 1. This counter counts when querying the database periodically. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-001 Idle Channel Measurement
This counter counts the number of idle TCH/Fs with interference band 2 in the carrier. This counter is used to find out the number of idle TCH/Fs with interference band 2. This counter counts when querying the database periodically. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-001 Idle Channel Measurement
This counter counts the number of idle TCH/Fs with interference band 3 in the carrier.
255
This counter is used to find out the number of idle TCH/Fs with interference band 3. This counter counts when querying the database periodically. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-001 Idle Channel Measurement
This counter counts the number of idle TCH/Fs with interference band 4 in the carrier. This counter is used to find out the number of idle TCH/Fs with interference band 4. This counter counts when querying the database periodically. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-001 Idle Channel Measurement
This counter counts the number of idle TCH/Fs with interference band 5 in the carrier. This counter is used to find out the number of idle TCH/Fs with interference band 5. This counter counts when querying the database periodically. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-001 Idle Channel Measurement
256
This counter counts the number of idle TCH/Hs with interference band 1 in the carrier. This counter is used to find out the number of idle TCH/Hs with interference band 1. This counter counts when querying the database periodically. Times ZGO-01-01-001 Half Rate ZGO-03-02-001 Idle Channel Measurement ZGO-03-02-005 Dynamic Half Rate Allocation
This counter counts the number of idle TCH/Hs with interference band 2 in the carrier. This counter is used to find out the number of idle TCH/Hs with interference band 2. This counter counts when querying the database periodically. Times ZGO-01-01-001 Half Rate ZGO-03-02-001 Idle Channel Measurement ZGO-03-02-005 Dynamic Half Rate Allocation
257
This counter counts the number of idle TCH/Hs with interference band 3 in the carrier. This counter is used to find out the number of idle TCH/Hs with interference band 3. This counter counts when querying the database periodically. Times ZGO-01-01-001 Half Rate ZGO-03-02-001 Idle Channel Measurement ZGO-03-02-005 Dynamic Half Rate Allocation
This counter counts the number of idle TCH/Hs with interference band 4 in the carrier. This counter is used to find out the number of idle TCH/Hs with interference band 4. This counter counts when querying the database periodically. Times ZGO-01-01-001 Half Rate ZGO-03-02-001 Idle Channel Measurement ZGO-03-02-005 Dynamic Half Rate Allocation
258
This counter counts the number of idle TCH/Hs with interference band 5 in the carrier. This counter is used to find out the number of idle TCH/Hs with interference band 5. This counter counts when querying the database periodically. Times ZGO-01-01-001 Half Rate ZGO-03-02-001 Idle Channel Measurement ZGO-03-02-005 Dynamic Half Rate Allocation
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. This counter is used to count the number of samples with UL RQ = 0. The counter increments if UL RQ = 0 in the measurement report or preprocessing measurement report that BSC receives. Times
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. This counter is used to count the number of samples with UL RQ = 1. The counter increments if UL RQ = 1 in the measurement report or preprocessing measurement report that BSC receives.
259
Unit
Times
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. This counter is used to count the number of samples with UL RQ = 2. The counter increments if UL RQ = 2 in the measurement report or preprocessing measurement report that BSC receives. Times
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. This counter is used to count the number of samples with UL RQ = 3. The counter increments if UL RQ = 3 in the measurement report or preprocessing measurement report that BSC receives. Times
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. This counter is used to count the number of samples with UL RQ = 4. The counter increments if UL RQ = 4 in the measurement report or preprocessing measurement report that BSC receives. Times
260
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. This counter is used to count the number of samples with UL RQ = 5. The counter increments if UL RQ = 5 in the measurement report or preprocessing measurement report that BSC receives. Times
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. This counter is used to count the number of samples with UL RQ = 6. The counter increments if UL RQ = 6 in the measurement report or preprocessing measurement report that BSC receives. Times
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. This counter is used to count the number of samples with UL RQ = 7. The counter increments if UL RQ = 7 in the measurement report or preprocessing measurement report that BSC receives. Times
261
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. This counter is used to count the number of samples with DL RQ = 0. The counter increments if DL RQ = 0 in the measurement report or preprocessing measurement report that BSC receives. Times
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. This counter is used to count the number of samples with DL RQ = 1. The counter increments if DL RQ = 1 in the measurement report or preprocessing measurement report that BSC receives. Times
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. This counter is used to count the number of samples with DL RQ = 2. The counter increments if DL RQ = 2 in the measurement report or preprocessing measurement report that BSC receives. Times
262
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. This counter is used to count the number of samples with DL RQ = 3. The counter increments if DL RQ = 3 in the measurement report or preprocessing measurement report that BSC receives. Times
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. This counter is used to count the number of samples with DL RQ = 4. The counter increments if DL RQ = 4 in the measurement report or preprocessing measurement report that BSC receives. Times
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. This counter is used to count the number of samples with DL RQ = 5. The counter increments if DL RQ = 5 in the measurement report or preprocessing measurement report that BSC receives. Times
263
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. This counter is used to count the number of samples with DL RQ = 6. The counter increments if DL RQ = 6 in the measurement report or preprocessing measurement report that BSC receives. Times
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. This counter is used to count the number of samples with DL RQ = 7. The counter increments if DL RQ = 7 in the measurement report or preprocessing measurement report that BSC receives. Times
This counter counts the number of handover attempts due to UL receiving strength too low on TCH/F channel. 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. BSC performs handover decision after receiving measurement report on TCH/F channel. If handover decision succeeds and the handover is due to UL strength, this counter increments. The measurement point is A, as shown in Figure 288.
Measurement Point
264
Times ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
This counter counts the number of times of handover attempts due to DL receiving strength too low on TCH/F channel. 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. 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 289.
FIGURE 289 HANDOVER DECISION
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
265
This counter counts the number of handover attempts due to UL quality too poor on TCH/F channel. 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. 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 290.
FIGURE 290 HANDOVER DECISION
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
This counter counts the number of handover attempts due to DL quality too poor on TCH/F channel. 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. 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 291.
Measurement Point
266
Times ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
This counter counts the number of handover attempts due to UL interference too large on TCH/F channel. 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. 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 292.
FIGURE 292 HANDOVER DECISION
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
267
This counter counts the number of handover attempts due to DL interference too large on TCH/F channel. 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. 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 293.
FIGURE 293 HANDOVER DECISION
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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. 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. BSC performs handover decision after receiving measurement report on TCH/F channel. If handover decision succeeds and the
Usage
Measurement Point
268
handover is due to too large C/I ratio, this counter increments. The measurement point is A, as shown in Figure 294.
FIGURE 294 HANDOVER DECISION
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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. 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. 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 295.
FIGURE 295 HANDOVER DECISION
Usage
Measurement Point
269
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. 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. 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 296.
FIGURE 296 HANDOVER DECISION
Usage
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
This counter counts the number of MS handover attempts due to too large TA on TCH/F channel. Increasing TA indicates that MS is
270
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. 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 297.
FIGURE 297 HANDOVER DECISION
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGB-02-02-002 Basic Handover Decision Criteria ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
This counter counts the number of handover attempts due to any other reason beyond the handover reasons mentioned previously. This counter is used to find out the frequency of handover due to any other reason. 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 298.
FIGURE 298 HANDOVER DECISION
271
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
This counter counts the number of intra-BSC inter-cell handoverout executions. The execution here means the radio resource of target cell has been successfully requested, and system returns the message of radio resource available. 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. 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 299.
FIGURE 299 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER EXECUTION
Usage
Measurement Point
272
This counter counts the number of successful intra-BSC inter-cell outgoing handovers. This counter is used to find out the frequency of successful intraBSC inter-cell outgoing handover. It is one of the parameters that evaluate the handover situation. 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 300.
FIGURE 300 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER SUCCESS
Measurement Point
This counter counts the number of MSC-controlled inter-BSC outgoing handover executions.
273
Usage
This counter is used to find out the frequency of MSC-controlled inter-BSC outgoing handover execution, and it reflects the handover situation. 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 301.
FIGURE 301 MSC-CONTROLLED OUTGOING HANDOVER EXECUTION
Measurement Point
This counter counts the number of successful MSC-controlled inter-BSC outgoing handovers. This counter is used to find out the frequency of successful MSCcontrolled inter-BSC outgoing handover, and it reflects the handover situation. 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 302.
Measurement Point
274
This counter counts the number of BSC-controlled inter-cell incoming handover executions. 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. 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 303.
FIGURE 303 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER EXECUTION
Measurement Point
275
This counter counts the number of successful BSC-controlled intercell incoming handovers. This counter shows the frequency of successful BSC-controlled inter-cell incoming handover, and it reflects the handover situation. 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 304.
FIGURE 304 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER SUCCESS
This counter counts the number of MSC-controlled inter-BSC incoming handover executions. 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. After the target cell receives the handover request message issued by MSC, the counter increments if the channel is allocated and activated successfully. The measurement point is A, as shown in Figure 305.
Measurement Point
276
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. 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. The target cell receives the radio channel request message. If the request is due to MSC-controlled inter-BSC incoming handover and the target cell has no available radio channels, forced release is attempted. If the target cell receives the message of resource available returned by the forced release instance, the counter increments. The measurement point is A, as shown in Figure 306.
Usage
Measurement Point
277
Times ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-03-001 eMLPP
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. 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. The target cell receives the radio channel request message. If the request is due to MSC-controlled inter-BSC incoming handover and the target cell has no available radio channels, the target instance is added to the waiting queue. When the target cell receives the message of resource available, the counter increments. The measurement point is A, as shown in Figure 307.
FIGURE 307 QUEUING EXECUTION
Usage
Measurement Point
278
Times ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-03-001 eMLPP
This counter counts the number of successful MSC-controlled inter-BSC incoming handovers. This counter is used to find out the frequency of successful MSCcontrolled inter-BSC incoming handover, and it reflects the handover situation. 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 308.
FIGURE 308 MSC-CONTROLLED INCOMING HANDOVER SUCCESS
Measurement Point
279
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. 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. 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 309.
FIGURE 309 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER EXECUTION
Usage
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
280
C900060104 Number of incoming handover success from undefined layer(GSM900) to current layer (GSM1800)
Description
This counter counts the number of successful incoming handover from the undefined layer cell (GSM900) to the target cell (GSM1800) during BSC-controlled inter-cell handover. 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. 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 310.
FIGURE 310 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER SUCCESS
Usage
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
281
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. 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. When the target cell (GSM900) within BSC receives the channel activation response message, if the request is due to BSC-controlled inter-cell handover and the source cell (GSM1800) is the undefined layer cell, the counter increments. The measurement point is A, as shown in Figure 311.
FIGURE 311 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER EXECUTION
Usage
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
282
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. 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. 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 312.
FIGURE 312 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER SUCCESS
Usage
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
283
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. 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. When the target cell (GSM1800) receives the channel activation response message, if the request is due to BSC-controlled intercell handover and the source cell (GSM900) is in the same layer, the counter increments. The measurement point is A, as shown in Figure 313.
FIGURE 313 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER EXECUTION
Usage
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
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.
284
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. 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 314.
FIGURE 314 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER SUCCESS
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
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. 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. When the target cell (GSM1800) receives the channel activation response message, if the request is due to BSC-controlled intercell handover and the source cell (GSM900) is in the upper layer, the counter increments. The measurement point is A, as shown in Figure 315.
Usage
Measurement Point
285
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
C900060110 Number of incoming handover success from GSM900 to GSM1800 in 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. 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. 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 316.
FIGURE 316 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER SUCCESS
Usage
Measurement Point
286
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
C900060111 Number of incoming handover from GSM900 to GSM1800 in 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. 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. When the target cell (GSM1800) receives the channel activation response message, if the request is due to BSC-controlled intercell handover and the source cell (GSM900) is in the lower layer, the counter increments. The measurement point is A, as shown in Figure 317.
FIGURE 317 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER EXECUTION
Usage
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
287
C900060112 Number of incoming handover success from GSM900 to GSM1800 in 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. 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. 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 318.
FIGURE 318 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER SUCCESS
Usage
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
288
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. 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. 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 319.
FIGURE 319 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER EXECUTION
Usage
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
289
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. 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. 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 320.
FIGURE 320 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER SUCCESS
Usage
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
290
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. 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. 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 321.
FIGURE 321 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER EXECUTION
Usage
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
291
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. 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. 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 322.
FIGURE 322 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER SUCCESS
Usage
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
292
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. 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. 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 323.
FIGURE 323 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER EXECUTION
Usage
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
293
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. 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. 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 324.
FIGURE 324 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER SUCCESS
Usage
Measurement Point
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-05-02-010 Multi-band Networking ZGO-05-02-008 Multi-layer Cell Structure
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.
294
Usage
This counter is used to find out the frequency of MS-initiated intracell handover execution. It is one of the parameters that evaluate radio environment. It reflects the handover situation. 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 325.
FIGURE 325 INTRA-CELL HANDOVER EXECUTION
Measurement Point
This counter counts the number of successful intra-cell handovers which are initiated by MS in the source cell. This counter is used to find out the frequency of successful intracell handover. It is one of the parameters that evaluate handover. 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 326.
FIGURE 326 INTRA-CELL HANDOVER SUCCESS
295
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. The counter counts at the following three time points: After the TCH/H is occupied successfully, if the maximum number of busy TCH/Hs exceeds the counter's recorded value; Before the TCH/H is released, if the maximum number of busy TCH/Hs exceeds the counter's recorded value; When the system reports the periodical measurement data, if the maximum number of busy TCH/Hs exceeds the counter's recorded value.
Measurement Point
296
This counter counts the number of SDCCHs which can be assigned normally, including idle SDCCH and occupied SDCCH. This counter is used to find out the number of available SDCCHs in the current cell. 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 328.
FIGURE 328 REPORTING MEASUREMENT DATA
This counter counts the number of SDCCHs that can not be assigned normally, including those SDCCHs blocked due to various reasons. This counter is used to find out the number of unavailable SDCCHs to facilitate troubleshooting. 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 329.
297
This counter counts the busy time of SDCCHs, which reflects the traffic volume of SDCCH. 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. The counter counts at the following three time points: 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.
Measurement Point
The measurement formula is as follows: Measurement value = (Current time Last measurement time point) Number of MSs that are occupying the channels
298
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
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. 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. 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 331.
FIGURE 331 REPORTING MEASUREMENT DATA
Usage
Measurement Point
299
This counter counts the number of radio channels that can not be assigned normally, including those radio channels blocked due to various reasons. 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. 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 332.
FIGURE 332 REPORTING MEASUREMENT DATA
Usage
Measurement Point
This counter counts the busy time of TCH/Hs, which reflects the traffic volume of TCH/H. 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. The counter counts at the following three time points: 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.
Measurement Point
300
The measurement formula is as follows: Measurement value = (Current time Last measurement time point) Number of MSs that are occupying the channels The reported measurement value is accumulated by each measurement value. After each accumulation, the last measurement time point is updated to the current time. If a TCH/H is acquired successfully, Number of MSs that are occupying the channels increases by 1; if a TCH/H is released, Number of MSs that are occupying the channels decreases by 1.
Second ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-04-04-002 Intelligent TRX Shutdown
This counter counts the maximum number of occupied TCH/Fs in a cell during a measurement period. The system records the TCH/Fs occupied in the cell. If a TCH/F is successfully occupied, the number of occupied TCH/Fs increases by 1; if a TCH/F is released, the number of occupied TCH/Hs decreases by 1. After a TCH/F is occupied, before a TCH/F is released, or when the system reports the periodical measurement data, if this counter's value is less than the number of actual occupied TCH/Fs, this counter's value will be replaced by the actual number of occupied TCH/Fs. In consideration of the TCH/F channel occupation situation in the last measurement period, the number of occupied TCH/Fs is updated before the release of a TCH/F.
Usage
This counter is used to find out the maximum number of occupied TCH/Fs in a cell during a measurement period. The counter's value reflects the instantaneous occupation and the heaviest traffic of TCH/F.
301
Measurement Point
The counter counts at the following three time points: 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.
This counter counts the busy time of TCH/Fs, which reflects the traffic volume of TCH/F. 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. The counter counts at the following three time points: 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.
Measurement Point
302
The measurement formula is as follows: Measurement value = (Current time Last measurement time point) Number of MSs that are occupying the channels The reported measurement value is accumulated by each measurement value. After each accumulation, the last measurement time point is updated to the current time. If a TCH/F is acquired successfully, Number of MSs that are occupying the channels increases by 1; if a TCH/F is released, Number of MSs that are occupying the channels decreases by 1.
Second ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-04-04-002 Intelligent TRX Shutdown
This counter counts the number of the TRXs that can be used normally. This counter is used to find out the number of available TRXs and resource usage in the current cell to facilitate troubleshooting. 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 336.
FIGURE 336 REPORTING MEASUREMENT DATA
303
Unit
Times
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. This counter is used to find out the frequency of the access due to CM SERVICE REQ of MOC. This counter counts when BSC receives the EST_IND message. The measurement point is A4, as shown in Figure 337.
FIGURE 337 RADIO ACCESS FLOW
Unit
Times
304
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. This counter is used to find out the frequency of successful SAPI 3 link establishments on SDCCH. This counter counts when BSC receives the EST_CONF message (SAPI = 3) from BTS. The measurement point is D2, as shown in Figure 338.
FIGURE 338 IDLE-STATE MT SHORT MESSAGE FLOW
305
iBSC supports dynamic conversion of SDCCH and TCH. This counter counts the number of available SDCCH configured by OMCR in the current cell. This counter is used to find out the number of available SDCCH in the current cell to facilitate eliminating fault in the cell. 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 339.
FIGURE 339 REPORTING MEASUREMENT DATA
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. This counter is used to find out the number of available TCH/F in the current cell to facilitate eliminating fault in the cell. 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 340.
306
Times 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
This counter counts the number of failing to assign TCH/H channel as a signaling channel. 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. 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 341.
Measurement Point
307
Times ZGB-03-01-004 Immediate TCH Assignment ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
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. This counter is used to find out the frequency of channel requests due to the access cause MOC. 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 342.
308
Unit
Times
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. This counter is used to find out the frequency of the access due to paging responses. This counter counts when BSC receives the EST_IND message. The measurement point is A4, as shown in Figure 343.
309
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 344.
310
Times ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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 345.
311
Times ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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 346.
312
Times ZGB-01-01-001 Full Rate (FR) Speech Codec ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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 347.
313
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 348.
314
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 349.
FIGURE 349 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
315
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 350.
FIGURE 350 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
316
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 351.
FIGURE 351 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)
317
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 352.
FIGURE 352 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)
318
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 353.
FIGURE 353 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-01-01-003 Adaptive Multi-rate Codec (AMR)
319
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 354.
FIGURE 354 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
Times ZGB-01-03-002 Data Traffic Channels ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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.
320
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 355.
FIGURE 355 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
Times ZGB-01-03-002 Data Traffic Channels ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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 356.
321
Times ZGB-01-03-002 Data Traffic Channels ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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.
This counter is used to find out the frequency of call drop due to handover failure on TCH/H voice channel. TCH/H voice channel is activated after BSC initiates the handover flow. After that: If RANCS is in the status of RADIO_APPLY and sends the intracell handover command, then T3107 is started. If RANCS is in the status of ASSIGN and T3107 is timeout, then the counter increments. The measurement point is A, as shown in Figure 357.
322
DUE TO
If RANCS is in the status of RADIO_APPLY and sends the intercell 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 358.
FIGURE 358 CALL DROP HANDOVER
DUE TO
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 359.
323
DUE TO
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
This counter counts the number of paging command messages from A-interface. These messages are part of Abis interface messages sent from BSC. This counter is used to find out the frequency of transmitting paging command messages at Abis interface. These messages are from A-interface. When BSC sends ABIS_INTER_PAGING_CMD message to BTS, this counter increments. The measurement point is A, as shown in Figure 360.
FIGURE 360 MEASUREMENT POINT OF NUMBER MESSAGES SENT TO BTS FROM BSC
OF
Usage
Measurement Point
ABIS INTERFACE
324
This counter counts the number of CS paging command messages from Gb interface. These messages are part of Abis interface messages sent from BSC. This counter is used to find out the frequency of transmitting CS paging command messages at Abis interface. These messages are from Gb interface. When BSC sends ABIS_INTER_CSPAGING_CMD message to BTS, this counter increments. The measurement point is A, as shown in Figure 361.
FIGURE 361 MEASUREMENT POINT OF NUMBER MESSAGES SENT TO BTS FROM BSC
OF
Usage
Measurement Point
ABIS INTERFACE
This counter counts the number of PS paging command messages from Gb interface. These messages are part of Abis interface messages sent from BSC. This counter is used to find out the frequency of transmitting PS paging command messages at Abis interface. These messages are from Gb interface. When BSC sends ABIS_INTER_PSPAGING_CMD message to BTS, this counter increments. The measurement point is A, as shown in Figure 362.
Usage
Measurement Point
325
FIGURE 362 MEASUREMENT POINT OF NUMBER MESSAGES SENT TO BTS FROM BSC
OF
ABIS INTERFACE
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. 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. 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 363.
FIGURE 363 REPORTING MEASUREMENT DATA
Times 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
326
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 message, T9103 being timeout, channel instance being released or channel being forcibly released, this counter accumulates.
Measurement Point
BSC activates TCH/F channel as voice channel due to handover, but receives channel activation failure message, incorrect channel activation response message, T9103 being timeout, channel instance being released, or channel being forcibly released. The measurement point is C3 as shown in Figure 364 and D3 as shown in Figure 365.
FIGURE 364 INTERNAL HANDOVER FAILURE FLOW 1 (INTRA-CELL HANDOVER, TC IS INTERNAL)
327
Times 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
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 366 and D2 as shown in Figure 367.
328
Times 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
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.
329
Measurement Point
BSC uses TCH/F for handover, but receives connection failure message, incorrect connection response message, or timer timeout during BIU connection process. The measurement point is C2 as shown in Figure 368 and D2 as shown in Figure 369.
FIGURE 368 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times 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
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
330
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 370 and D2 as shown in Figure 371.
FIGURE 370 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times 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
331
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 372 and D3 as shown in Figure 373.
FIGURE 372 INTERNAL HANDOVER FAILURE FLOW 1 (INTRA-CELL HANDOVER, TC IS INTERNAL)
332
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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.
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 374 and D2 as shown in Figure 375.
333
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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). 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
334
during BIU connection process. The measurement point is C2 as shown in Figure 376 and D2 as shown in Figure 377.
FIGURE 376 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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.
335
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 378 and D2 as shown in Figure 379.
FIGURE 378 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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).
336
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 380 and D3 as shown in Figure 381.
FIGURE 380 INTERNAL HANDOVER FAILURE FLOW 1 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times 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)
337
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 382 and D2 as shown in Figure 383.
FIGURE 382 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times 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)
338
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.
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 384 and D2 as shown in Figure 385.
FIGURE 384 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times 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)
339
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). 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 386 and D2 as shown in Figure 387.
FIGURE 386 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times 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)
340
This counter counts the number of successful TCH/F channel handover during voice channel handover. When BSC detects the successful handover message sent by MS on newly-allocated TCH/F channel, this counter accumulates. The ASS_COM message indicates successful intra-cell handover, and the HO_COM message indicates successful inter-cell handover and external handover. For intra-cell handover and inter-cell handover, the counter accumulates on source instances. For external handover, the counter accumulates on target instances because the source instance is not under this BSC.
Measurement Point
The counter counts when BSC receives the ASS_COM/HO_COM message. The measurement point is C4 as shown in Figure 388 and Figure 389, and D4 as shown in Figure 390 and Figure 391.
FIGURE 388 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, TC IS INTERNAL)
341
FIGURE 389 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, CHANNEL TYPE CHANGED, TC IS EXTERNAL)
342
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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 392 and D3 as shown in Figure 393.
343
Times ZGB-01-03-002 Data Traffic Channels ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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.
344
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 394 and D2 as shown in Figure 395.
FIGURE 394 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times ZGB-01-03-002 Data Traffic Channels ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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 fails due to receiving BIU con-
345
nection 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 396 and D2 as shown in Figure 397.
FIGURE 396 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times ZGB-01-03-002 Data Traffic Channels ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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.
346
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 398 and D2 as shown in Figure 399.
FIGURE 398 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times ZGB-01-03-002 Data Traffic Channels ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
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
347
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 400 and Figure 401, and D4 as shown in Figure 402 and Figure 403.
FIGURE 400 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, TC IS INTERNAL)
FIGURE 401 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, CHANNEL TYPE CHANGED, TC IS EXTERNAL)
348
Times ZGB-01-03-002 Data Traffic Channels ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
349
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 404.
FIGURE 404 IMMEDIATE ASSIGNMENT ALLOCATION FAILURE FLOW 2
Times ZGB-03-01-004 Immediate TCH Assignment ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
350
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 405.
FIGURE 405 COMMON ASSIGNMENT FAILURE FLOW 1 (TC IS INTERNAL)
351
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 406.
FIGURE 406 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
352
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 407.
FIGURE 407 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
353
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 408.
FIGURE 408 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
354
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 409 and D3 as shown in Figure 410.
FIGURE 409 INTERNAL HANDOVER FAILURE FLOW 1 (INTRA-CELL HANDOVER, TC IS INTERNAL)
355
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
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.
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 411 and D2 as shown in Figure 412.
356
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
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). 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.
357
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 413 and D2 as shown in Figure 414.
FIGURE 413 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
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
358
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 415 and D2 as shown in Figure 416.
FIGURE 415 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
359
C900060183 Number of TCH/H allocation failure due to channel activation failure for assignment (speech version2)
Description
This counter counts the number of TCH/H channel allocation failure due to channel activation failure when assigning voice channel (using speech version 2). 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 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 417.
FIGURE 417 COMMON ASSIGNMENT FAILURE FLOW 1 (TC IS INTERNAL)
Times ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation
360
C900060184 Number of TCH/H allocation failure due to BTS connection failure for assignment (speech version2)
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 2). 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 418.
FIGURE 418 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
Times ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation
361
C900060185 Number of TCH/H allocation failure due to BIU connection failure for assignment (speech version2)
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 2). 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 419.
FIGURE 419 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
Times ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation
362
C900060186 Number of TCH/H allocation failure due to TCU connection failure for assignment (speech version2)
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 2). 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 420.
FIGURE 420 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
Times ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation
363
C900060187 Number of TCH/H allocation failure due to channel activation failure for handover (speech version2)
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 2). 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 421 and D3 as shown in Figure 422.
FIGURE 421 INTERNAL HANDOVER FAILURE FLOW 1 (INTRA-CELL HANDOVER, TC IS INTERNAL)
364
Times 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
C900060188 Number of TCH/H allocation failure due to BTS connection failure for handover (speech version2)
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 2). 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 423 and D2 as shown in Figure 424.
365
Times 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
C900060189 Number of TCH/H allocation failure due to BIU connection failure for handover (speech version2)
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 2). 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.
366
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 425 and D2 as shown in Figure 426.
FIGURE 425 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times 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
C900060190 Number of TCH/H allocation failure due to TCU connection failure for handover (speech version2)
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 2).
367
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 427 and D2 as shown in Figure 428.
FIGURE 427 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times 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
368
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 429.
FIGURE 429 COMMON ASSIGNMENT FAILURE FLOW 1 (TC IS INTERNAL)
Times ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation
369
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 430.
FIGURE 430 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
Times ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation
370
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 431.
FIGURE 431 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
Times ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation
371
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 432.
FIGURE 432 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
Times ZGO-01-01-001 Half Rate ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-005 Dynamic Half Rate Allocation
372
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 433 and D3 as shown in Figure 434.
FIGURE 433 INTERNAL HANDOVER FAILURE FLOW 1 (INTRA-CELL HANDOVER, TC IS INTERNAL)
373
Times 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
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 435 and D2 as shown in Figure 436.
374
Times 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
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.
375
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 437 and D2 as shown in Figure 438.
FIGURE 437 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times 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
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).
376
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 439 and D2 as shown in Figure 440.
FIGURE 439 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times 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
377
This counter counts the number of successful assignments of TCH/H as voice channel. 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 441 and Figure 442.
FIGURE 441 COMMON ASSIGNMENT FLOW (TC IS INTERNAL)
378
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
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 443.
379
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 444 and Figure 445, and D4 as shown in Figure 446 and Figure 447.
380
FIGURE 445 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, CHANNEL TYPE CHANGED, TC IS EXTERNAL)
381
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
382
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 message, T9103 being timeout, channel instance being released, or channel being forcibly released. The measurement point is B3, as shown in Figure 448.
FIGURE 448 COMMON ASSIGNMENT FAILURE FLOW 1 (TC IS INTERNAL)
383
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 449.
FIGURE 449 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
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.
384
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 450.
FIGURE 450 COMMON ASSIGNMENT FLOW 3 (TC IS INTERNAL)
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 451.
385
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 452 and D3 as shown in Figure 453.
386
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
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.
387
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 454 and D2 as shown in Figure 455.
FIGURE 454 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
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 fails due to receiving BIU con-
388
nection 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 456 and D2 as shown in Figure 457.
FIGURE 456 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
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.
389
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 458 and D2 as shown in Figure 459.
FIGURE 458 INTERNAL HANDOVER FAILURE FLOW 2 (INTRA-CELL HANDOVER, TC IS INTERNAL)
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
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
390
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 460 and Figure 461.
FIGURE 460 COMMON ASSIGNMENT FLOW (TC IS INTERNAL)
Times ZGB-06-01-007 Cell Traffic Statistics ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
391
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 462.
FIGURE 462 COMMON ASSIGNMENT FAILURE FLOW 4 (TC IS INTERNAL)
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
392
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 463 and Figure 464, and D4 as shown in Figure 465 and Figure 466.
FIGURE 463 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, TC IS INTERNAL)
FIGURE 464 INTERNAL HANDOVER FLOW (INTRA-CELL HANDOVER, CHANNEL TYPE CHANGED, TC IS EXTERNAL)
393
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
394
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. 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. 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 467.
FIGURE 467 FORCED RELEASE EXECUTION
Usage
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-03-001 eMLPP
395
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. 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. The target cell within BSC receives the radio channel request message. If the request is due to BSC-controlled inter-cell incoming handover and the target cell has no available radio channels, the target instance is added to the waiting queue. When the target cell receives the message of resource available, the counter increments. The measurement point is A2, as shown in Figure 468.
FIGURE 468 QUEUING EXECUTION
Usage
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-03-001 eMLPP
396
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. 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. 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 469.
FIGURE 469 FORCED HANDOVER EXECUTION
Usage
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-03-001 eMLPP
397
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. 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. 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 470.
FIGURE 470 FORCED HANDOVER EXECUTION
Usage
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGB-06-01-007 Cell Traffic Statistics ZGO-01-03-001 eMLPP
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.
398
This counter is used to find out the number of unavailable TCH/H channel in the current cell to facilitate eliminating the fault. 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 471.
FIGURE 471 REPORTING MEASUREMENT DATA
Times 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
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. This counter is used to find out the number of unavailable TCH/F channel in the current cell to facilitate eliminating the fault. 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 472.
FIGURE 472 REPORTING MEASUREMENT DATA
399
Times 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
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.
This counter is used to find out the frequency of call drop due to handover failure on TCH/F signaling channel. TCH/F signaling channel is activated after BSC initiates the handover flow. After that: If RANCS is in the status of RADIO_APPLY and sends the intracell handover command, then T3107 is started. If RANCS is in the status of ASSIGN and T3107 is timeout, then the counter increments. The measurement point is A, as shown in Figure 473.
FIGURE 473 CALL DROP HANDOVER
DUE TO
If RANCS is in the status of RADIO_APPLY and sends the intercell handover command, then T3103 is started. If RANCS is in the status of ASSIGN and T3103 is timeout, then the counter
400
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 475.
FIGURE 475 CALL DROP
DUE TO
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
401
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.
This counter is used to find out the frequency of call drop on TCH/F voice channel due to handover failure. TCH/F voice channel is activated after BSC initiates the handover flow. After that: If RANCS is in the status of RADIO_APPLY and sends the intracell handover command, then T3107 is started. If RANCS is in the status of ASSIGN and T3107 is timeout, then the counter increments. The measurement point is A, as shown in Figure 476.
FIGURE 476 CALL DROP HANDOVER
DUE TO
If RANCS is in the status of RADIO_APPLY and sends the intercell 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 477.
402
DUE TO
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 478.
FIGURE 478 CALL DROP
DUE TO
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
This counter counts the number of call drops on TCH/F data channel due to handover failure. Call drop occurs after MS requests for
403
TCH/F data channel successfully. The counter increments if call drop is due to handover failure. Presently, reasons for handover failure include T3107 timeout, T3103 timeout and external handover timer timeout under the status of ASSIGNING.
Usage Measurement Point
This counter is used to find out the frequency of call drop on TCH/F data channel due to handover failure. TCH/F data channel is activated after BSC initiates the handover flow. After that: If RANCS is in the status of RADIO_APPLY and sends the intracell handover command, then T3107 is started. If RANCS is in the status of ASSIGN and T3107 is timeout, then the counter increments. The measurement point is A, as shown in Figure 479.
FIGURE 479 CALL DROP HANDOVER
DUE TO
If RANCS is in the status of RADIO_APPLY and sends the intercell 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 480.
404
DUE TO
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 481.
FIGURE 481 CALL DROP
DUE TO
Times ZGB-01-03-002 Data Traffic Channels ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
405
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.
This counter is used to find out the frequency of call drop due to handover failure on TCH/H signaling channel. TCH/H signaling channel is activated after BSC initiates the handover flow. After that: If RANCS is in the status of RADIO_APPLY and sends the intracell handover command, then T3107 is started. If RANCS is in the status of ASSIGN and T3107 is timeout, then the counter increments. The measurement point is A, as shown in Figure 482.
FIGURE 482 CALL DROP HANDOVER
DUE TO
If RANCS is in the status of RADIO_APPLY and sends the intercell 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 483.
406
DUE TO
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 484.
FIGURE 484 CALL DROP
DUE TO
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
407
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.
This counter is used to find out the frequency of call drop due to handover failure on TCH/H data channel. TCH/H data channel is activated after BSC initiates the handover flow. After that: If RANCS is in the status of RADIO_APPLY and sends the intracell handover command, then T3107 is started. If RANCS is in the status of ASSIGN and T3107 is timeout, then the counter increments. The measurement point is A, as shown in Figure 485.
FIGURE 485 CALL DROP HANDOVER
DUE TO
If RANCS is in the status of RADIO_APPLY and sends the intercell 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 486.
408
DUE TO
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 487.
FIGURE 487 CALL DROP
DUE TO
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
409
This counter counts the number of handover attempts due to UL receiving strength too low on TCH/H channel. 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. BSC performs handover decision after receiving measurement report on TCH/H channel. If handover decision succeeds and the handover is due to UL strength, this counter increments. The measurement point is A, as shown in Figure 488.
FIGURE 488 HANDOVER DECISION
Measurement Point
Times 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
This counter counts the number of handover attempts due to DL receiving strength too low on TCH/H channel. 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. 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 489.
Measurement Point
410
Times 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
This counter counts the number of handover attempts due to UL quality too poor on TCH/H channel. 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. 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 490.
FIGURE 490 HANDOVER DECISION
Measurement Point
Times 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
411
This counter counts the number of handover attempts due to DL quality too poor on TCH/H channel. 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. 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 491.
FIGURE 491 HANDOVER DECISION
Measurement Point
Times 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
This counter counts the number of handover attempts due to UL interference too large on TCH/H channel. 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. 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 492.
Measurement Point
412
Times 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
This counter counts the number of handover attempts due to DL interference too large on TCH/H channel. 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. 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 493.
FIGURE 493 HANDOVER DECISION
Measurement Point
Times 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
413
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. 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. 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 494.
FIGURE 494 HANDOVER DECISION
Usage
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
This counter counts the number of MS handover attempts due to too low C/I ratio on TCH/H channel. The handover only occurs
414
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. 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 495.
FIGURE 495 HANDOVER DECISION
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
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. 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. 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 496.
Usage
Measurement Point
415
Times 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
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. 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. 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 497.
FIGURE 497 HANDOVER DECISION
Usage
Measurement Point
Times 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
416
This counter counts the number of handover attempts due to any other reason beyond the handover reasons mentioned previously. This counter is used to find out the frequency of handover due to any other reason. 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 498.
FIGURE 498 HANDOVER DECISION
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
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 499.
417
Times ZGB-03-01-004 Immediate TCH Assignment ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
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. This counter is used to find out the frequency of successful MS access due to MOC. The counter increments when BSC receives the EST_IND message. The measurement point is A4, as shown in Figure 500.
418
Unit
Times
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). 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. 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 501.
Usage
Measurement Point
419
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). This counter is used to find out the frequency of successful MSCcontrolled inter-BSC outgoing handover that is initiated by MS. The source cell and the target cell are of different frequency bands. BSC performs handover decision after receiving the measurement report sent by MS. If the decision indicates that inter-cell handover is necessary and if the current cell to which the handover is attempted is a cell under different BSC, then BSC sends the handover request A_HO_RQD to MSC to trigger inter-BSC handover. If MS accesses the target cell successfully, the source cell receives the release command issued by MSC, if the source cell and the target cell are of different frequency bands, then this counter increments. The measurement point is A, as shown in Figure 502.
FIGURE 502 MSC-CONTROLLED OUTGOING HANDOVER SUCCESS
Usage
Measurement Point
420
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). 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. 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 503.
FIGURE 503 MSC-CONTROLLED INCOMING HANDOVER EXECUTION
Usage
Measurement Point
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). 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. 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
Usage
Measurement Point
421
bands, then this counter increments. The measurement point is A, as shown in Figure 504.
FIGURE 504 MSC-CONTROLLED INCOMING HANDOVER SUCCESS
After BSC responds to the channel request to allocate and activate SDCCH channel successfully, BSC sends the IMM_ASS message to notify MS to use this channel. After MS receives this message, it sends SABM frame to BTS on SDCCH. BTS then sends the EST_IND message to BSC after receiving SABM frame. If BSC receives the correct EST_IND message within specified time, it indicates that the SDCCH channel assignment succeeds, C900060241 and C900060242 accumulate simultaneously. If BSC receives the incorrect EST_IND message or T3101 is timeout, it indicates that the SDCCH channel assignment fails, C900060241 and C900060243 accumulate simultaneously.
Usage
This counter counts the number of SDCCH channel assignment attempts when BSC sends the IMM_ASS message to notify MS to use the allocated SDCCH channel. The counter's value includes the number of assignment success (C900060242) and the number of assignment failure (C900060243). 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 505.
Measurement Point
422
After BSC responds to the channel request to allocate and activate SDCCH channel successfully, BSC sends the IMM_ASS message to notify MS to use this channel. After MS receives this message, it sends SABM frame to BTS on SDCCH. BTS then sends the EST_IND message to BSC after receiving SABM frame. If BSC receives the correct EST_IND message within specified time, it indicates that the SDCCH channel assignment succeeds, then this counter increments.
This counter counts the number of MS successfully accessing SDCCH channel when BSC sends the IMM_ASS message. 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 506.
423
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.
This counter counts the number of MS failing to access SDCCH channel when BSC sends the IMM_ASS message. 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 507.
424
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. This counter is used to learn the call drop frequency caused by raio link failure on TCH/F voice channel. 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 508.
425
BY
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.
426
This counter is used to learn the call drop frequency caused by raio link failure on TCH/H voice channel. 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 509.
FIGURE 509 CALL DROPS CAUSED ASSIGNMENT
BY
Times ZGB-06-01-001 Monitoring Um Interface ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
427
428
Chapter
Overview
Configuration management information basic measurement records the cell's basic configuration information of each measurement period. Statistic unit in this measurement is cell.
This counter records frequency bands set in the cell. Refer to configuration information for frequency band values. This counter is used to find out frequency bands set at specific time segment in the cell. None
429
This counter records the number of TRXs in the cell. This counter is used to find out the number of TRXs in the cell at specific time segment. Times
This counter records the number of voice channels in the cell. This counter is used to find out the number of voice channels in the cell at specific time segment. Times
This counter records the number of signaling channels in the cell. This counter is used to find out the number of signaling channels in the cell at specific time segment. Times
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. This counter is used to find out the cell's maximum traffic capacity in theory at specific time segment. Number of Erlangs 10000
Usage Unit
430
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. This counter is used to find out the cell's maximum traffic capacity in theory at specific time segment. Number of Erlangs 10000
Usage Unit
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. This counter is used to find out the cell's maximum traffic capacity in theory at specific time segment. Number of Erlangs 10000
Usage Unit
This counter records the number of static PDTCHs in the cell. This counter is used to find out the number of static PDTCHs in the cell at specific time segment. Times
This counter records the number of dynamic PDTCHs in the cell. This counter is used to find out the number of dynamic PDTCHs in the cell at specific time segment.
431
Unit
Times
432
Chapter
433
C901000048 Max number of GPRS DL TBF simultaneous establishment .................................................................... 462 C901000050 Max number of EGPRS DL TBF simultaneous establishment .................................................................... 463 C901000052 Number of GPRS DL signaling TBF normal release ............................................................................. 463 C901000058 Number of EGPRS DL signaling TBF normal release ............................................................................. 464
Overview
DL TBF process comprises establishment, transmission and release of the DL TBF. The establishment includes the DL TBF establishment on CCCH, PCCCH and PACCH. The release includes normal release and abnormal release of the DL TBF. Abnormal release is used to judge the running of PS service so as to make adjustment. DL transmission measurement mainly focuses on the connecting time of the DL TBF and the number of co-existing DL TBFs.
Number of GPRS DL TBF resumption in delay state This counter counts the number of retransmissions after the DL GPRS TBF finishes LLC frame transmission and receives new LLC frames. 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 510.
Measurement Point
434
FIGURE 510 - MEASUREMENT POINT OF NUMBER OF RESUMPTION FOR GPRS DL TBF IN DELAY STATE
C901000005 Number of GPRS DL TBF establishment failure on PACCH due to time out
Definition Description
Number of GPRS DL TBF establishment failure on PACCH due to time out In the UL transmission state, when SGSN DL LLC frame arrives, the DL TBF transmission should be established. If there is no reserved DL resource, the user plane will ask the control plane to allocate resource. This counter counts the number of non-responses from the control plane in this case.
435
Measurement Point
When the BSC sends DL Assign Request, the timer waiting for response is triggered. The counter increments if the timer expires. The measurement point is A, as shown in Figure 511.
FIGURE 511 NUMBER OF REQUEST FAILURES FOR ESTABLISHING GPRS ON PACCH (NO RESPONSE FROM CONTROL PLANE)
Unit
Times
C901000006 Number of GPRS DL TBF establishment failure on PACCH due to other reasons
Definition Description
Number of GPRS DL TBF establishment failure on PACCH due to other reasons 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. When PACCH fails to send the assignment messages or fails to create DL RLC instances, the counter increments. Times
436
C901000009 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to time out
Definition Description
Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to time out 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. 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 512 and Figure 513.
FIGURE 512 FAILURES FOR ESTABLISHING DL GPRS TBF ON CCCH/PCCCH (1)
Measurement Point
437
Unit
Times
C901000010 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to other reasons
Definition Description
Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to other reasons 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. 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. Times
Measurement Point
Unit
Number of GPRS DL TBF establishment execution on CCCH/PCCCH 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 assign-
438
ment, the user plane is informed too and it believes the DL TBF establishment has started.
Measurement Point
During the DL GRPS TBF establishment on CCCH/PCCCH, after the user plane sends the request to the control plane, receives the resource assignment message, successfully creates the DL RLC instance and sends the Packet Polling Request message to MS, this counter increments. The measurement point is A2, as shown inFigure 514 .
FIGURE 514 NORMAL ESTABLISHMENT OF DL GPRS TBF ON CCCH/PCCCH
In the DTM mode, this counter increments when the user plane receives the DTM sent message (the LLC frame has been sent). The measurement point is A, as shown in Figure 515.
FIGURE 515 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 516.
439
Unit
Times
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
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. 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 517. 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 518.
Measurement Point
440
FIGURE 517 MEASUREMENT POINT OF NUMBER OF TIMES FOR ESTABLISHING GPRS DL TBF WITH POLLING FAILED ON CCCH/PCCCH
FIGURE 518 MEASUREMENT POINT OF NUMBER OF TIMES FOR ESTABLISHING GPRS DL TBF WITH POLLING FAILED ON CCCH/PCCCH
Unit
Times
441
C901000013 Number of GPRS DL TBF 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
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.
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 519, A as shown in Figure 520, and A as shown in Figure 521.
442
443
Unit
Times
Number of Number of GPRS DL TBF establishment execution on CCCH/PCCCH DL TBF establishment success on CCCH/PCCCH 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 GPRS DL TBF establishment is also considered to be successful. If the assignment is on PCCCH, after the user plane sends the packet polling request message and receives the packet control ack message from MS, the counter increments. If the assignment is on CCCH, after the user plane receives the packet control ack message from MS and successfully sends the DL assignment message, the counter increments. In the DTM mode, when the user plane receives the DTM sent/assignment message from the control plane, the counter increments. The measurement points are A3 (PCCCH) and A4 (CCCH), as shown in Figure 522, A as shown in Figure 523, and A as shown in Figure 524.
Description
Measurement Point
444
445
Unit
Times
Number of Number of GPRS DL TBF establishment execution on CCCH/PCCCH DL TBF normal release 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. After the DL GPRS TBF transmits the last data block (FBI=1) and when BSC receives the last DL response message (FAI=1), this counter increments. The measurement points are A, as shown in Figure 525and Figure 526.
FIGURE 525 NORMAL RELEASE OF DL TBF
Description
Measurement Point
446
Unit
Times
Number of EGPRS DL TBF resumption in delay state This counter counts the number of retransmissions after the DL EGPRS TBF finishes LLC frame transmission and receives new LLC frames. After the DL EGPRS TBF transmits all LLC frames and before the DL RLC block with FBI = 1 is transmitted, if the DL TBF receives new LLC frames, this counter increments. The measurement point is A, as shown in Figure 527.
Measurement Point
447
FIGURE 527 - MEASUREMENT POINT OF NUMBER OF RESUMPTION FOR GPRS DL TBF IN DELAY STATE
C901000027 Number of EGPRS DL TBF establishment failure on PACCH due to time out
Definition Description
Number of EGPRS DL TBF establishment failure on PACCH due to time out 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.
448
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 528.
FIGURE 528 NUMBER OF REQUEST FAILURES FOR ESTABLISHING GPRS ON PACCH (NO RESPONSE FROM CONTROL PLANE)
Unit
Times
C901000028 Number of EGPRS DL TBF establishment failure on PACCH due to other reasons
Definition Description
Number of EGPRS DL TBF establishment failure on PACCH due to other reasons 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. When PACCH fails to send the assignment messages or fails to create DL RLC instances, the counter increments. Times
449
C901000031 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to time out
Definition Description
Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to time out 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. During the DL EGPRS TBF establishment on CCCH/PCCCH, if there is no radio resource assigned by the control plane within the specified time, this counter increments. The measurement points are A, as shown in Figure 529 and Figure 530.
FIGURE 529 FAILURES FOR ESTABLISHING DL GPRS TBF ON CCCH/PCCCH (1)
Measurement Point
450
Unit
Times
C901000032 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to other reasons
Definition Description
Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to other reasons 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. 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. Times
Measurement Point
Unit
Number of EGPRS DL TBF establishment execution on CCCH/PCCCH 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.
451
In the DTM mode, if the control plane has transmitted LLC frames through the dedicated channel or has transmitted the DTM assignment, the user plane is informed too and it believes the DL TBF establishment has started.
Measurement Point
During the DL EGRPS TBF establishment on CCCH/PCCCH, after the user plane sends the request to the control plane, receives the resource assignment message, successfully creates the DL RLC instance and sends the Packet Polling Request message to MS, this counter increments. The measurement point is A2, as shown in Figure 531.
FIGURE 531 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 532.
FIGURE 532 LLC FRAME TRANSMITS GTTP MESSAGE IN DTM MODE
452
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 533.
FIGURE 533 DTM ASSIGNMENT IN DTM MODE
Unit
Times
C901000034 Number of EGPRS DL TBF establishment execution failure on CCCH/PCCCH due to polling failed
Definition Description
Number of EGPRS DL TBF establishment execution failure on CCCH/PCCCH due to polling failed 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. 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 534. 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 535.
Measurement Point
453
FIGURE 534 MEASUREMENT POINT OF NUMBER OF TIMES FOR ESTABLISHING EGPRS DL TBF WITH POLLING FAILED ON CCCH/PCCCH
FIGURE 535 MEASUREMENT POINT OF NUMBER OF TIMES FOR ESTABLISHING EGPRS DL TBF WITH POLLING FAILED ON CCCH/PCCCH
Unit
Times
454
C901000035 Number of EGPRS DL TBF establishment execution success on CCCH/PCCCH due to polling succeeded
Definition Description
Number of EGPRS DL TBF establishment execution success on CCCH/PCCCH due to polling succeeded 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.
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 536, A as shown in Figure 537 and A as shown in Figure 538.
455
456
Unit
Times
Number of EGPRS DL TBF establishment success on CCCH/PCCCH 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. If the assignment is on PCCCH, after the user plane sends the packet polling request message and receives the packet control ack message from MS, the counter increments. If the assignment is on CCCH, after the user plane receives the packet control ack message from MS and successfully sends the DL assignment message, the counter increments. In the DTM mode, when the user plane receives the DTM sent/assignment message from the control plane, the counter increments. The measurement points are A3 (PCCCH) and A4 (CCCH), as shown in Figure 539, A as shown in Figure 540, and A as shown in Figure 541.
Measurement Point
457
458
Unit
Times
Number of EGPRS DL TBF normal release 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. After the DL EGPRS TBF transmits the last data block (FBI=1) and when BSC receives the last DL response message (FAI=1), this counter increments. The measurement points are A, as shown in Figure 542andFigure 543.
FIGURE 542 NORMAL RELEASE OF DL TBF
Measurement Point
459
Unit
Times
Time of GPRS DL TBF connection This counter counts the cumulated overall DL connecting time of GPRS TBF within a cell. (1) When GPRS TBF RLC transmission starts, this counter accumulates. (2) When GPRS TBF RLC transmission is released normally (in the acknowledged mode, BSC receives the response with FAI=1; or in the non-acknowledged mode, BSC receives the Packet Control Ack message), this counter accumulates. (3) When GPRS TBF RLC transmission is released abnormally (including N3105 overflow and T3191 timeout), this counter accumulates. (4) When the measurement value is acquired regularly, this 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 544.
460
Unit
Second
Time of EGPRS DL TBF connection This counter counts the cumulated overall DL connecting time of EGPRS TBF within a cell. The measurement point and the formulas are as shown in Figure 545. EGPRS TBF is the measurement prerequisite.
FIGURE 545 MEASUREMENT OF CUMULATED OVERALL DL CONNECTING TIME
Unit
Second
461
This counter counts the cumulated overall DL connecting time of signaling TBF within a cell. The measurement point and the formulas are as shown in Figure 546. Signaling TBF is the measurement prerequisite.
FIGURE 546 MEASUREMENT OF CUMULATED OVERALL DL CONNECTING TIME
Unit
Seconds
Max number of GPRS DL TBF simultaneous establishment The counter counts the maximum number of DL GPRS TBFs that are established simultaneously within a cell. When GPRS TBF RLC transmission starts, the GPRS TBFs in the cell increments by 1 and compares with the saved maximum value. When the measurement value is acquired regularly, compare the number of GPRS TBF in the cell with the saved maximum value.
For the measurement of number of GPRS TBFs in a cell, refer to Measurement Point of C901000045.
Unit
Times
462
Max number of EGPRS DL TBF simultaneous establishment The counter counts the maximum number of DL EGPRS TBFs that are established simultaneously within a cell. When EGPRS TBF RLC transmission starts, the EGPRS TBFs in the cell increments by 1 and compares with the saved maximum value. When the measurement value is acquired regularly, compare the number of EGPRS TBF in the cell with the saved maximum value.
For the measurement of number of EGPRS TBFs in a cell, refer to Measurement Point of C901000045.
Unit
Times
Number of GPRS DL signaling TBF normal release When the DL GPRS signaling TBF sends the last data block, it sets FBI to 1 and sets the RRBP bit to let MS send the DL response message. After BSC receives the last response message (FAI=1), it is considered that the DL transmission is executed normally. In the DTM mode, if the user plane receives the data sent message from the control plane, to keep measurement consistency, it is considered that the DL TBF is released normally. After the DL GPRS signaling TBF transmits the last data block (FBI=1) and when BSC receives the last DL response message (FAI=1), this counter increments. The measurement points are A, as shown in Figure 547and Figure 548.
Measurement Point
463
Unit
Times
Number of EGPRS DL signaling TBF normal release When the DL EGPRS signaling TBF sends the last data block, it sets FBI to 1 and sets the RRBP bit to let MS send the DL response message. After BSC receives the last response message (FAI=1), it is considered that the DL transmission is executed normally. In the DTM mode, if the user plane receives the data sent message from the control plane, to keep measurement consistency, it is considered that the DL EGPRS TBF is released normally.
464
Measurement Point
After the DL EGPRS signaling TBF transmits the last data block (FBI=1) and when BSC receives the last DL response message (FAI=1), this counter increments. The measurement points are A, as shown in Figure 549 and Figure 550.
FIGURE 549 NORMAL RELEASE OF DL TBF
Unit
Times
465
466
Chapter
467
C901010050 Number of GPRS UL signaling TBF normal release ............................................................................. 487 C901010056 Number of EGPRS UL signaling TBF normal release ............................................................................. 488
Overview
Uplink (UL) data TBF measurement mainly involves processes of establishing TBF, keeping TBF and releasing TBF on cells. The measurement takes cell as the statistics unit.
Number of GPRS UL TBF resumption in extend uplink state 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. This counter is used to record number of resumptions for GPRS UL TBF in extended UL state. This counter increments when a new data block is received in GPRS extended UL state. The measurement point is A, as shown in Figure 551.
468
FIGURE 551 MEASUREMENT POINT ON RECEIVING NEW DATA BLOCK IN GPRS EXTENDED UL STATE
Unit
Times
Number of GPRS UL TBF resource reassign in delay uplink state 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. This counter is used to record number of resource reassignment for GPRS UL TBF in delayed UL state. This counter increments when UPPB receives UL resource reassign for GPRS UL TBF in delayed UL state, A, as shown in Figure 552.
FIGURE 552 MEASUREMENT POINT ON RECEIVING RESOURCE REASSIGNMENT FOR GPRS UL TBF IN DELAYED UL STATE
469
Number of GPRS establishment failure on PACCH due to time out 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. This counter is used to record number of request failures caused by timeout for establishing GPRS on PACCH. The measurement point is A, as shown in Figure 553.
FIGURE 553 MEASUREMENT POINT ON NUMBER OF REQUEST FAILURES CAUSED BY TIMEOUT FOR ESTABLISHING GPRS ON PACCH GPRS
Unit
Times
Number of GPRS establishment failure on PACCH due to other reasons 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.
470
This counter is used to record number of request failures caused by other reasons for establishing GPRS on PACCH. This counter increments when the request for establishing GPRS on PACCH fails because of other reasons except timer is timeout. Times
C901010010 Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to competition solving failed
Definition Description
Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to competition solving failed When MS has new data to transmit but no corresponding UL/downlink TBF is available, MS initiates UL TBF establishment flow, depending on whether the cell configures PBCCH on CCCH/PCCCH. If two-step access is not compulsory at network side, in the case of request for one-step access, MS sends RLC block with TLLI or Packet Resource Request/ Additional MS Radio Access Capabilities on the UL block allocated after receiving assignment message from network so that solution by competition can be completed. Meanwhile, network sends Packet UL Ack with TLLI as well. After sending out assignment message, if network does not receive RLC block or Packet Resource Request/ Additional MS Radio Access Capabilities from MS till timeout, solution for one-step access by competition fails.
Usage
This counter is used to record number of failed GPRS UL TBF establishment on CCCH/PCCCH due to the failure of one-step success competition solution.
471
Measurement Point
C901010011 Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to not receive resource request
Definition Description
Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to not receive resource request 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.
472
Measurement Point
C901010012 Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons
Definition Description
Number of GPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons 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.
473
This counter is used to record number of failed GPRS UL TBF establishment on CCCH/PCCCH caused by any other reasons. 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. Times
Number of GPRS UL TBF establishment success on CCCH/PCCCH 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.
This counter is used to record number of successful GPRS UL TBF establishment on CCCH/PCCCH. This counter increments when GPRS UL TBF establishment on CCCH/PCCCH succeeds in the cases of both one-step access and two-step access. The measurement points are A, as shown in Figure 556 and Figure 557.
474
FIGURE 556 MEASUREMENT POINT ON NUMBER OF SUCCESSFUL GPRS UL TBF ESTABLISHMENT ON CCCH/PCCCH (I)
FIGURE 557 MEASUREMENT POINT ON NUMBER OF SUCCESSFUL GPRS UL TBF ESTABLISHMENT ON CCCH/PCCCH (II)
475
Unit
Times
Number of GPRS UL TBF normal release 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 GPRS UL TBF releases. The measurement point is A, as shown in Figure 558.
FIGURE 558 MEASUREMENT POINT ON NUMBER OF NORMAL GPRS UL TBF RELEASE
Unit
Times
476
Number of EGPRS UL TBF resumption in extend uplink state 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. This counter is used to record number of resumptions for EGPRS UL TBF in extended UL state. The measurement point is A, as shown in Figure 559.
FIGURE 559 MEASUREMENT POINT ON NUMBER OF RESUMPTIONS FOR EGPRS UL TBF IN EXTENDED UL STATE
Unit
Times
Number of EGPRS UL TBF resource reassign in delay uplink state If either MS or BSS does not support extended UL, after receiving RLC block (CV = 0) from MS, BSS will enter in delayed UL state, and meanwhile stop allocating blocks.
477
This counter is used to record number of resource reassignments for EGPRS UL TBF in delayed UL state. The measurement point is A, as shown in Figure 560.
FIGURE 560 MEASUREMENT POINT ON NUMBER OF RESOURCE REASSIGNMENTS FOR EGPRS UL TBF IN DELAYED UL STATE
Number of EGPRS establishment failure on PACCH due to time out 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. This counter is used to record number of request failures caused by timeout for establishing EGPRS on PACCH.
Usage
478
Measurement Point
Unit
Times
Number of EGPRS establishment failure on PACCH due to other reasons 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. This counter is used to record number of request failures caused by other reasons for establishing GPRS on PACCH. This counter increments when request for establishing EGPRS on PACCH fails because of other reasons except timer is timeout. Times
479
C901010031 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to competition solving failed
Definition Description
Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to competition solving failed 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.
This counter is used to record number of failed EGPRS UL TBF establishment on CCCH/PCCCH caused by competition solving failed. The measurement point is A, as shown in Figure 562.
FIGURE 562 MEASUREMENT POINT ON NUMBER OF ESTABLISHMENT FAILURES OF EGPRS UL TBF CAUSED BY COMPETITION SOLVING FAILED
480
C901010032 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to not receive resource request
Definition Description
Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to not receive resource request 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. The measurement point is A, as shown in Figure 563.
FIGURE 563 MEASUREMENT POINT ON NUMBER OF ESTABLISHMENT FAILURES OF EGPRS UL TBF CAUSED BY NOT RECEIVING RESOURCE REQUEST
Measurement Point
481
C901010033 Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons
Definition Description
Number of EGPRS UL TBF establishment failure on CCCH/PCCCH due to other reasons 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 Resource Request. After that, network assigns new resource for MS by Packet UL Assignment according to MSs wireless radio access capability.
This counter is used to record number of failed EGPRS UL TBF establishment on CCCH/PCCCH caused by any other reasons. 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. Times
Number of EGPRS UL TBF establishment success on CCCH/PCCCH 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.
482
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 Measurement Point
This counter is used to record number of successful EGPRS UL TBF establishment on CCCH/PCCCH. This counter increments when EGPRS UL TBF establishment on CCCH/PCCCH succeeds in the cases of both one-step access and two-step access. The measurement points are A, as shown in Figure 564 and Figure 565.
FIGURE 564 MEASUREMENT POINT ON NUMBER OF SUCCESSFUL EGPRS UL TBF ESTABLISHMENT ON CCCH/PCCCH (I)
483
FIGURE 565 MEASUREMENT POINT ON NUMBER OF SUCCESSFUL EGPRS UL TBF ESTABLISHMENT ON CCCH/PCCCH (II)
Unit
Times
Number of EGPRS UL TBF normal release 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 EGPRS UL TBF releases.
Usage
484
Measurement Point
Unit
Times
Time of GPRS UL TBF connection 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 GPRS TBF. The counter starts to accumulate when UPPB receives the UL GPRS TBF establishment indication, and stops when UL GPRS TBF on UPPB ends normally. Second
Time of EGPRS UL TBF connection MS establishes two types of TBF for different purposes. They are signaling TBF and data TBF.
485
This counter is used to find out cumulated overall UL connecting time of EGPRS TBF. The counter starts to accumulate when UPPB receives the UL EGPRS TBF establishment indication, and stops when UL EGPRS TBF on UPPB ends normally. Second
Time of UL signaling TBF connection 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 signaling TBF. The counter starts to accumulate when UPPB receives the UL signaling TBF establishment indication, and stops when UL signaling TBF on UPPB ends normally. Second
Max number of GPRS UL TBF simultaneous establishment 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. This counter is used to find out the maximum number of UL GPRS TBF established simultaneously within the measurement period. This counter increments when UPPB receives UL GPRS TBF establishment indication, and decrements when the UL GPRS TBF releases. Times
486
Max number of EGPRS UL TBF simultaneous establishment 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 This counter is used to find out the maximum number of UL EGPRS TBF established simultaneously within the measurement period. This counter increments when UPPB receives UL EGPRS TBF establishment indication, and decrements when the UL EGPRS TBF releases. Times
Number of GPRS UL signaling TBF normal release 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 GPRS signaling UL TBF releases.
Usage
487
Measurement Point
Unit
Times
Number of EGPRS UL signaling TBF normal release 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 EGPRS signaling UL TBF releases.
Usage
488
Measurement Point
Unit
Times
489
490
Chapter
Overview
Data flow measurement focuses on the flow related information, including the LLC frames, RLC blocks and TBF connecting time.
491
Number of Kbytes of IP packet sent to BIPB DSP on the DL UPPB board encodes RLC/MAC blocks to PCU frames without sync headers and sends the frames to BIPB through IP packets. BIPB adds them with sync headers and sends them to BTS. After the UL BIPB receives the PCU frames with sync headers (bearing RLC/MAC blocks) from BTS, it removes the headers and sends them to UPPB through IP packet. This counter counts the payload sent within iBSC. The counter counts the size of IP packets sent to BIPB. The measurement unit is Byte. The measurement point is A, as shown in Figure 569.
FIGURE 569 MEASUREMENT POINT OF SIZE OF IP PACKETS SENT TO BIPB
Unit
Byte
Number of packets sent to BIPB DSP on the DL UPPB board encodes RLC/MAC blocks to PCU frames without sync headers and sends the frames to BIPB through IP packets. BIPB adds them with sync headers and sends them to BTS. After the UL BIPB receives the PCU frames with sync headers (bearing RLC/MAC blocks) from BTS, it removes the headers and sends them to UPPB through IP packet. The counter counts the number of IP packets sent to BIPB.
Usage
492
Measurement Point
Unit
Times
Number of Kbytes of IP packet received from BIPB DSP on the DL UPPB board encodes RLC/MAC blocks to PCU frames without sync headers and sends the frames to BIPB through IP packets. BIPB adds them with sync headers and sends them to BTS. After the UL BIPB receives the PCU frames with sync headers (bearing RLC/MAC blocks) from BTS, it removes the headers and sends them to UPPB through IP packet. This counter counts the payload received within iBSC. The counter counts the size of IP packets received from BIPB. The measurement unit is Byte. The measurement point is A, as shown in Figure 571.
FIGURE 571 MEASUREMENT POINT OF SIZE OF IP PACKETS RECEIVED FROM BIPB
Unit
Byte
493
Number of packets received from BIPB DSP on the DL UPPB board encodes RLC/MAC blocks to PCU frames without sync headers and sends the frames to BIPB through IP packets. BIPB adds them with sync headers and sends them to BTS. After the UL BIPB receives the PCU frames with sync headers (bearing RLC/MAC blocks) from BTS, it removes the headers and sends them to UPPB through IP packet. The counter counts the number of packets received from BIPB. The measurement point is A, as shown in Figure 572.
FIGURE 572 MEASUREMENT POINT OF NUMBER OF IP PACKETS RECEIVED FROM BIPB
Unit
Times
Number of Kbytes of IP packet sent to GIPB The DL GIPB sends DL UnitData to UPPB through IP packets. After caching DL UnitData, UPPB divides it into RLC blocks and sends them to BTS through PCU frames. The UL UPPB decodes the received RLC blocks, composes UL UnitData, and sends it to GIPB through IP packet. This counter performs statistics for BSSGP layer, and the statistic data contains BSSGP header but does not contain IP header.
Usage
The counter counts the size of IP packets sent to GIPB. The measurement unit is Byte.
494
Measurement Point
Unit
Byte
Number of packets sent to GIPB The DL GIPB sends DL UnitData to UPPB through IP packets. After caching DL UnitData, UPPB divides it into RLC blocks and sends them to BTS through PCU frames. The UL UPPB decodes the received RLC blocks, composes UL UnitData, and sends it to GIPB through IP packet. The counter counts the number of IP packets sent to GIPB. The measurement point is A, as shown in Figure 574.
FIGURE 574 MEASUREMENT POINT OF NUMBER OF IP PACKETS SENT TO GIPB
Unit
Times
495
Number of Kbytes of IP packet received from GIPB The DL GIPB sends DL UnitData to UPPB through IP packets. After caching DL UnitData, UPPB divides it into RLC blocks and sends them to BTS through PCU frames. The UL UPPB decodes the received RLC blocks, composes UL UnitData, and sends it to GIPB through IP packet. This counter performs statistics for BSSGP layer, and the statistic data contains BSSGP header.
The counter counts the size of IP packets received from GIPB. The measurement unit is Byte. The measurement point is A, as shown in Figure 575.
FIGURE 575 MEASUREMENT POINT OF SIZE OF IP PACKETS RECEIVED FROM GIPB
Unit
Byte
Number of packets received from GIPB The DL GIPB sends DL UnitData to UPPB through IP packets. After caching DL UnitData, UPPB divides it into RLC blocks and sends them to BTS through PCU frames. The UL UPPB decodes the received RLC blocks, composes UL UnitData, and sends it to GIPB through IP packet. The counter counts the number of IP packets received from GIPB.
Usage
496
Measurement Point
Unit
Times
Number of Kbytes carried by EGPRS DL LLC frame 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.
The counter counts the number of Kbytes carried by DL EGPRS LLC frame. The measurement point is A, as shown in Figure 577.
FIGURE 577 MEASUREMENT POINT OF NUMBER OF KBYTES CARRIED BY DL EGPRS LLC FRAME
Unit
Byte
497
Number of Kbytes carried by DL signaling LLC frame 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.
The counter counts the number of Kbytes carried by DL signaling LLC frame. The measurement point is A, as shown in Figure 578.
FIGURE 578 MEASUREMENT POINT OF NUMBER OF KBYTES CARRIED BY DL SIGNALING LLC FRAME
Unit
Byte
Number of Kbytes carried by UL LLC frame 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
498
Measurement Point
Unit
Byte
Number of UL LLC frames The UL UPPB sends the composed LLC frames to GIPB through IP packet. This counter performs statistics for LLC layer, and the statistic result is the number of frames.
The counter counts the number of UL LLC frames. The measurement point is A, as shown in Figure 580.
FIGURE 580 MEASUREMENT POINT OF NUMBER OF UL LLC FRAMES
Unit
Times
499
Number of Bytes of GPRS DL TBF LLC frame 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.
The counter counts the number of bytes of DL GPRS TBF LLC frame. The measurement point is A, as shown in Figure 581.
FIGURE 581 MEASUREMENT POINT OF NUMBER OF BYTES OF DL GPRS TBF LLC FRAME
Unit
Byte
Number of Bytes of EGPRS DL TBF LLC frame UPPB divides the DL LLC frame into RLC blocks and sends them to MS. After correctly receiving those RLC blocks, MS will recompose
500
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.
Usage Measurement Point
The counter counts the number of bytes of DL EGPRS TBF LLC frame. The measurement point is A, as shown in Figure 582.
FIGURE 582 MEASUREMENT POINT OF NUMBER OF BYTES OF DL EGPRS TBF LLC FRAME
Unit
Byte
Number of Bytes of DL signaling TBF LLC frame 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.
Usage
The counter counts the number of bytes of DL signaling TBF LLC frame.
501
Measurement Point
Unit
Byte
Number of Bytes of UL GPRS TBF LLC frame 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.
The counter counts the number of bytes of UL GPRS TBF LLC frame. The measurement point is A, as shown in Figure 584.
FIGURE 584 MEASUREMENT POINT OF NUMBER OF BYTES OF UL GPRS TBF LLC FRAME
Unit
Byte
502
Number of Bytes of EGPRS UL TBF LLC frame 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.
The counter counts the number of bytes of UL EGPRS TBF LLC frame. The measurement point is A, as shown in Figure 585.
FIGURE 585 MEASUREMENT POINT OF NUMBER OF BYTES OF UL EGPRS TBF LLC FRAME
Unit
Byte
Number of Bytes of UL signaling TBF LLC frame 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.
503
Measurement Point
Unit
Byte
Number of GPRS UL data TBF completion 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. The counter counts the number of completion of GPRS UL data TBF.
Usage
504
Measurement Point
Unit
Times
Number of GPRS DL data TBF completion 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. The counter counts the number of completion of GPRS DL data TBF.
Usage
505
Measurement Point
Unit
Times
Number of EGPRS UL data TBF completion 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. The counter counts the number of completion of EGPRS UL data TBF.
Usage
506
Measurement Point
Unit
Times
Number of EGPRS DL data TBF completion 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. The counter counts the number of completion of EGPRS DL data TBF.
Usage
507
Measurement Point
Unit
Times
Number of Kbytes carried by GPRS DL LLC frame 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.
508
Measurement Point
Unit
Byte
509
510
Chapter
511
Overview
RLC blocks are classified into control block and data block based on the content. Data block includes RLC block waiting to be acknowledged (Pending block), retransmitted block (NACK block), and first-transmitted block (new blocks excluding retransmitted RLC block and pending RLC blocks). RLC coding scheme includes CS1 ~ CS4 and MCS1 ~ MCS9. Coding scheme is set at background and can be adjusted by BSC according to the link quality. UL /DL RLC statistics is used to find out the number of RLC blocks with different coding schemes received and sent by BSC as well as coding scheme adjustment times during transmission process. The measurement takes cell as the statistics unit. Figure 592 shows the measurement point of DL pending RLC block.
FIGURE 592 MEASUREMENT POINT OF DL PENDING RLC BLOCK
512
513
Bytes of GPRS DL RLC lost on PDTCH This counter is not used for the time being.
Bytes of EGPRS DL RLC lost on PDTCH This counter is not used for the time being.
Number of UL RLC Blocks lost MS sends UL RLC data block to BSC by BTS. The counter keeps record of the number of data blocks lost during packet transmission. This counter is used to find out the number of RLC data blocks lost on PDTCH. The counter increments when UL RLC data blocks from BTS get lost. The measurement point is A, as shown in Figure 598.
514
Unit
Times
Bytes of GPRS UL RLC lost on PDTCH 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. This counter is used to find out the number of CS-coded RLC bytes on UL PDTCH in non-ack mode. The counter increments when CS-coded UL RLC block from BTS gets lost. The measurement point is A, as shown in Figure 599.
FIGURE 599 MEASUREMENT POINT OF NUMBER OF UL RLC BLOCKS LOST
Unit
Byte
515
Bytes of EGPRS UL RLC lost on PDTCH 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. This counter is used to find out the number of MCS-coded RLC bytes on UL PDTCH in non-ack mode. The counter increments when MCS-coded UL RLC block from BTS gets lost. The measurement point is A, as shown in Figure 600.
FIGURE 600 MEASUREMENT POINT OF NUMBER OF UL RLC BLOCKS LOST
Unit
Byte
Number of standstill of GPRS UL TBF receiving window This counter counts the number of standstill of UL receiving window after UL GPRS TBF establishment. This counter is used to find out the number of standstill of UL GPRS TBF receiving window. 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 601.
516
FIGURE 601 MEASUREMENT POINT OF NUMBER OF STANDSTILL OF GPRS UL TBF RECEIVING WINDOW
Unit
Times
Number of standstill of EGPRS UL TBF receiving window This counter counts the number of standstill of UL receiving window after UL EGPRS TBF establishment. This counter is used to find out the number of standstill of UL EGPRS TBF receiving window. The counter increments when receiving window is found to come to a standstill in RLC layer after UL EGPRS TBF establishment. Times
Number of standstill of GPRS DL TBF sending window This counter counts the number of standstill of DL sending window after DL GPRS TBF establishment.
517
This counter is used to find out the number of standstill of DL GPRS TBF sending window. 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 602.
FIGURE 602 MEASUREMENT POINT OF NUMBER OF STANDSTILL OF GPRS DL TBF SENDING WINDOW
Unit
Times
Number of standstill of EGPRS DL TBF sending window This counter counts the number of standstill of DL sending window after DL EGPRS TBF establishment. This counter is used to find out the number of standstill of DL EGPRS TBF sending window. The counter increments when sending window is detected to standstill during RLC block sending to BTS from BSC. The measurement point is A, as shown in Figure 603.
518
FIGURE 603 MEASUREMENT POINT OF NUMBER OF STANDSTILL OF GPRS DL TBF SENDING WINDOW
Unit
Times
Number of increment of DL coding mode 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. This counter is used to find out the increase of DL RLC block coding scheme. The counter increments when coding scheme of DL RLC blocks sending to BTS from BSC is increased. The measurement point is A as shown in Figure 604 (for EDGE) and Figure 605 (for GPRS).
519
FIGURE 604 MEASUREMENT POINT OF NUMBER OF INCREMENT OF DL CODING MODE (EDGE RLC BLOCK)
FIGURE 605 MEASUREMENT POINT OF NUMBER OF INCREMENT OF DL CODING MODE (GPRS RLC BLOCK)
520
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. This counter is used to find out the decrease of DL RLC block coding scheme. The counter increments when coding scheme of DL RLC blocks sending to BTS from BSC is decreased. The measurement point is A as shown in Figure 606 (for EDGE) and Figure 607 (for GPRS).
FIGURE 606 MEASUREMENT POINT OF NUMBER OF INCREMENT OF DL CODING MODE (EDGE RLC BLOCK)
FIGURE 607 MEASUREMENT POINT OF NUMBER OF INCREMENT OF DL CODING MODE (GPRS RLC BLOCK)
521
Number of increment of UL coding mode BSC will adjust UL coding scheme based on measurement report when sending UL RLC blocks to BTS. This counter counts the number of UL coding scheme increase. This counter is used to find out the increase of UL RLC block coding scheme. The counter increments when coding scheme of UL RLC blocks is increased. The measurement point is A, as shown in Figure 608.
FIGURE 608 MEASUREMENT POINT OF NUMBER OF INCREMENT OF UL CODING MODE
Number of decrement of UL coding mode BSC will adjust UL coding scheme based on measurement report when sending UL RLC blocks to BTS. This counter counts the number of UL coding scheme decrease.
522
This counter is used to find out the decrease of UL RLC block coding scheme. 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 609.
FIGURE 609 MEASUREMENT POINT OF NUMBER OF INCREMENT OF UL CODING MODE
Number of conversion from GMSK to 8PSK This counter counts the number of the handover of modulation mode from GMSK to 8PSK. This counter is used to find out the number of the handover from GMSK to 8PSK of RLC data block . The counter increments When coding scheme of RLC block is changed from GMSK to 8PSK (MCS5~MCS9). The measurement point is A, as shown in Figure 610, Figure 611, and Figure 612.
523
FIGURE 610 MEASUREMENT POINT OF NUMBER OF INCREMENT OF DL CODING MODE (EDGE RLC BLOCK)
FIGURE 611 MEASUREMENT POINT OF NUMBER OF INCREMENT OF DL CODING MODE (GPRS RLC BLOCK)
524
Number of conversion from 8PSK to GMSK This counter counts the number of the handover of modulation mode from 8PSK to GMSK. This counter is used to find out the number of the handover from 8PSK to GMSK of RLC data block. The counter increments when coding scheme of RLC block is changed from 8PSK to GMSK (from MCS5~MCS9 to other). The measurement point is A, as shown in Figure 613, Figure 614, and Figure 615.
525
FIGURE 613 MEASUREMENT POINT OF NUMBER OF INCREMENT OF DL CODING MODE (EDGE RLC BLOCK)
FIGURE 614 MEASUREMENT POINT OF NUMBER OF INCREMENT OF DL CODING MODE (GPRS RLC BLOCK)
526
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. 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. 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 616.
Usage
Measurement Point
527
OF
Unit
Times
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. 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. When the coding mode of downlink RLC block sent to BTS from BSC is degraded, the counter increments. Times
Usage
When BSC receives the uplink RLC block, it adjusts the coding mode for RLC block according to the measurement report. This
528
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. 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 617.
FIGURE 617 MEASUREMENT POINT ADJUSTMENT
OF
Measurement Point
Unit
Times
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. 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. When the coding mode of uplink RLC block received by BSC is degraded, the counter increments. Times
Usage
529
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. 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. 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 618.
FIGURE 618 MEASUREMENT POINT CODING MODE ADJUSTMENT
OF
Usage
Measurement Point
Unit
Times
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.
530
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. When the coding mode of downlink RLC block sent to BTS from BSC is degraded, the counter increments. Times
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. 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. 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 619.
FIGURE 619 MEASUREMENT POINT ADJUSTMENT
OF
Usage
Measurement Point
Unit
Times
531
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. 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. When the coding mode of uplink RLC block received by BSC is degraded, the counter increments. Times
Usage
532
Chapter
10
533
C901040039 MAX CS used number of exclusive ABIS ........... 551 C901040040 MIN CS used number of exclusive ABIS............ 552 C901040041 MAX PS used number of exclusive ABIS ........... 552 C901040042 MIN PS used number of exclusive ABIS ............ 552 C901040043 Average Number of GPRS User ....................... 553 C901040044 Maximum number of GPRS User ..................... 553 C901040045 Average Number of EGPRS User...................... 554 C901040046 Maximum number of EDGE User ..................... 554 C901040047 Number of assigned uplink radio channels ......... 554 C901040048 Number of assigned downlink radio channels ............................................................................... 555 C901040049 Number of requested uplink radio channels ............................................................................... 555 C901040050 Number of requested downlink radio channels ............................................................................... 556 C901040051 Number of PS channel expand ........................ 556 C901040052 Number of PS channel expand perform ............ 556 C901040053 Number of PS channel expand success............. 557
Overview
Statistic counters are used to measure the PS resource usage in each cell, including number of usable PS channels, average and max number of busy PS channels, total busy time of PS channels, total time of PS channel congestion and using of PS channels. The measurement takes cell as the statistics unit.
This counter counts the maximum number of Abis TS used under TDM connection between cell and site during measurement period. The counter value reflects the instant Abis resource occupation and maximum busyness. This counter is used to find out the current cells requirements for Abis resource, which helps to adjust or expand Abis resource. Inquire the database when periodic measurement data report to get the counter value. Times
534
Average number of Abis TS used This counter counts the average number of Abis TS used under TDM connection between cell and site during measurement period. This counter is used to find out the Abis resource occupation by the current cell, which helps to adjust or expand Abis resource. Inquire the database when periodic measurement data report to get the counter value. Times
This counter counts the number of PDCHs that are not assigned normally, including blocked dynamic PDCHs due to various causes and static PDCHs. 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. Inquire the database when periodic measurement data report to get the counter value. Times
Usage
Number of available static PDCH iBSC supports dynamic wireless channels. This counter counts the number of available PDCHs configured through OMCR in the current cell. This counter is used to find out the number of available static PDCHs in the current cell, which helps to make troubleshooting. Inquire the database when periodic measurement data report to get the counter value. Times
535
Related Features
ZGB-03-02-005 GPRS-only (without voice) Timeslots Configurable ZGO-03-02-010 GPRS and EGPRS Channels Allocated Separately
Number of unavailable static PDCH iBSC supports dynamic wireless channels. This counter counts the number of unavailable PDCHs configured via OMCR in the current cell. This counter is used to find out the number of unavailable static PDCHs in the current cell, which helps to make troubleshooting. Inquire the database when periodic measurement data report to get the counter value. Times 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
Time of DL PDCH congestion This counter counts the time during which the service instance fails to apply DL PDCHs (namely the total time of DL PDCH congestion). If DL PDCH application fails, BSC records the congestion label and the time when congestion starts. If DL PDCH application succeeds, BSC clears the congestion label. When applying for DL PDCH, if the congestion label is set, the current time minus the congestion time of the previous record leaves the new congestion time. Before DL PDCH is released, if the congestion label is set, such calculation repeats. When getting the periodic measurement value, if the congestion label is set, such calculation repeats. The accumulation of these calculations makes the total time of DL PDCH congestion.
Usage
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.
536
Measurement Point
The measurement is taken at three time points listed below: Before DL PDCH attempts to occupy, if the congestion label is set, this counter calculates the congestion time and accumulates them. Before DL PDCH is released, if the congestion label is set, this counter calculates the congestion time and accumulates them. When reporting the measurement data periodically, if the congestion label is set, this counter calculates the congestion time and accumulates them.
Unit
Second
Time of UL PDCH congestion This counter counts the time during which the service instance fails to apply UL PDCHs (namely the total time of UL PDCH congestion). If UL PDCH application fails, BSC records the congestion label and the time when congestion starts. If UL PDCH application succeeds, BSC clears the congestion label. When applying for UL PDCH, if the congestion label is set, the current time minus the congestion time of the previous record leaves the new congestion time. Before UL PDCH is released, if the congestion label is set, such calculation repeats. When getting the periodic measurement value, if the congestion label is set, such calculation repeats. The accumulation of these calculations makes the total time of UL PDCH congestion.
Usage
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. The measurement is taken at three time points listed below: 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.
Measurement Point
Unit
Second
537
Time of PDCH used at least one UL /DL TBF exists 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. 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. The measurement is taken at three time points listed below: 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.
C901040012 Time of PDCH used at least one UL/DL EGPRS TBF exists
Definition Description
Time of PDCH used at least one UL /DL EGPRS TBF exists 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. 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. The measurement is taken at three time points listed below: 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.
Usage
Measurement Point
Unit
Second
538
Related Features
Time of PDCH used at least one DL TBF exists 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. 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. The measurement is taken at three time points listed below: 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.
Time of PDCH used at least one UL TBF exists 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. 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. The measurement is taken at three time points listed below: When PDCH resource is acquired successfully, this counter calculates and accumulates. When PDCH resource is released, this counter calculates and accumulates.
539
When reporting the measurement data periodically, this counter calculates and accumulates.
Number of immediate assignment on AGCH This counter counts the number of Imm Assign message sent on AGCH by BSC. This counter is used to find out the frequency of sending Imm Assign message on AGCH by BSC in the current cell. If BSC starts UL single block or UL TBF channel assignment, when non-DRX MS assigns DL TBF, the counter increments. The measurement points are A1 and A2 as shown in Figure 620 and Figure 621.
FIGURE 620 SENDING INSTANT ASSIGNMENT MESSAGE BY AGCH CHANNEL (1)
540
Unit
Times
Number of paging PS requests on PCH This counter counts the number of Paging PS message sent on PCH by BSC. This counter is used to find out the frequency of sending Paging PS message on PCH by BSC in the current cell. When BSC sends Paging PS message on PCH, the counter increments. The measurement point is A as shown in Figure 622.
FIGURE 622 SENDING PS PAGING BY PCH CHANNEL
541
Number of paging CS requests on PCH This counter counts the number of Paging CS message sent on PCH by BSC. This counter is used to find out the frequency of sending Paging CS message on PCH by BSC in the current cell. When BSC sends Paging CS message on PCH, the counter increments. The measurement point is A as shown in Figure 623.
FIGURE 623 SENDING CS PAGING BY PCH CHANNEL
Number of immediate assignment on PCH This counter counts the number of Imm Assign message sent on PCH by BSC. This counter is used to find out the frequency of sending Imm Assign message on PCH by BSC in the current cell. If BSC starts to establish DL TBF, when DRX MS sends Imm Assign message on PCH, the counter increments. The measurement point is A2, as shown in Figure 624.
542
Unit
Times
Number of immediate assignment on PAGCH This counter counts the number of Imm Assign message sent on PAGCH by BSC. This counter is used to find out the frequency of sendingImm Assign message on PAGCH by BSC in the current cell. If BSC starts UL single block or UL TBF channel assignment, when non-DRX MS assigns DL TBF, the counter increments. The measurement points are A1 and A2, as shown in Figure 625and Figure 626.
543
Unit
Times
Number of PS paging requests on PPCH This counter counts the number of Paging PS message sent on PPCH by BSC. This counter is used to find out the frequency of sending Paging PS message on PPCH by BSC in the current cell.
544
Measurement Point
When BSC sends Paging PS message on PPCH, the counter increments. The measurement point is A, as shown in Figure 627.
FIGURE 627 SENDING PS PAGING BY PCH CHANNEL
Number of CS paging requests on PPCH This counter counts the number of Paging CS message sent on PPCH by BSC. This counter is used to find out the frequency of sending Paging CS message on PPCH by BSC in the current cell. When BSC sends Paging CS message on PPCH, the counter increments. The measurement point is A, as shown in Figure 628.
FIGURE 628 SENDING CS PAGING BY PCH CHANNEL
545
Number of immediate assignment on PPCH This counter counts the number of Imm Assign message sent on PPCH by BSC. This counter is used to find out the frequency of sending Imm Assign message on PPCH by BSC in the current cell. 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 629.
FIGURE 629 SENDING ASSIGNMENT MESSAGE BY PAGCH CHANNEL
Unit
Times
This counter counts the number of EGPRS Packet Channel Request message or Packet Channel Request message received by BSC on PRACH.
546
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. 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 630.
FIGURE 630 NUMBER OF PACKET CHANNEL REQUESTS ON PRACH
Measurement Point
Unit
Times
Sum of Abis TS used sampling This counter counts the total number of used Abis TS under TDM connection between BSC and BS. This counter is used to find out the sum of Abis TS used sampling. It is one of the parameters to observe the Abis TS using. When the database of BSC starts to assign Abis TS, the counter accumulates. Times
Number of Abis TS used sampling This counter counts the number of Abis TS assignments by database. This counter is used to find out the frequency of Abis TS assignment sampling. It is one of the parameters to observe the Abis TS using.
547
When the database assigns Abis TS, the counter increments. Times
Sum of PDCH used sampling This counter counts the sum of PDCHs assigned by database when service processing module starts PS channel request. 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. When service processing module starts PS channel request and database assigns PDCH, the counter accumulates. Times
Number of PDCH used sampling This counter counts the number of PDCH assigning attempts by database when service processing module starts PS channel request. 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. When service processing module starts PS channel request and database assigns PDCH, the counter increments. Times
Usage
548
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. 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. The counter counts when CS user requests for the Abis resource successfully. Number of (TDM access)/kbps (IP access)
Minimum value of Abis TS used to CS 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. 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. The counter counts when CS user requests for the Abis resource successfully or releases the Abis resource successfully. Number of (TDM access)/kbps (IP access)
Total value of the regular sampling used to CS 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. This counter reflects the average occupation of Abis resource in CS service. The counter accumulates when CS user requests for the Abis resource successfully or releases the Abis resource successfully. Number of (TDM access)/kbps (IP access)
549
Number of sampling of CS 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. This counter reflects the average occupation of Abis resource in CS service. The counter accumulates when CS user requests for the Abis resource successfully or releases the Abis resource successfully. Number of (TDM access)/kbps (IP access)
Maximum value of Abis TS used to PS 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. 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. The counter counts when PS user requests for the Abis resource successfully. Number of (TDM access)/kbps (IP access)
Minimum value of Abis TS used to PS 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. 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. The counter counts when PS user requests for the Abis resource successfully or releases the Abis resource successfully.
550
Unit
Total value of the regular sampling used to PS 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. This counter reflects the average occupation of Abis resource in PS service. The counter accumulates when PS user requests for the Abis resource successfully or releases the Abis resource successfully. Number of (TDM access)/kbps (IP access)
Number of sampling of PS 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. This counter reflects the average occupation of Abis resource in PS service. The counter accumulates when PS user requests for the Abis resource successfully or releases the Abis resource successfully. Number of (TDM access)/kbps (IP access)
This counter counts the maximum number of Abis timeslots occupied by CS service in the cell. Upon the request of releasing CS
551
channel, the system checks the total number of Abis timeslots occupied by CS service in the cell. If the number is larger than the current value, then update the value.
Usage Measurement Point
This counter is used to find out the usage of Abis timeslots occupied by CS service in the cell. The counter counts upon channel conversion due to request of releasing CS channel and refreshing dynamic CS channel.
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. This counter is used to find out the usage of Abis timeslots occupied by CS service in the cell. The counter counts upon channel conversion due to request of releasing CS channel and refreshing dynamic CS channel.
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. This counter is used to find out the usage of Abis timeslots occupied by PS service in the cell. The counter counts upon channel conversion due to request of releasing PS channel and refreshing dynamic PS channel.
This counter counts the minimum number of Abis timeslots occupied by PS service in the cell. Upon the request of releasing PS channel, the system checks the total number of Abis timeslots oc-
552
cupied by PS service in the cell. If the number is less than the current value, then update the value.
Usage Measurement Point
This counter is used to find out the usage of Abis timeslots occupied by PS service in the cell. The counter counts upon channel conversion due to request of releasing PS channel and refreshing dynamic PS channel.
This counter counts the average number of GPRS users in the cell and site within the measurement period. This counter is used to find out the average number of GPRS users in current cell. 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. Times
Unit
This counter counts the maximum number of GPRS users in the cell and site within the measurement period. This counter is used to find out the maximum number of GPRS users in current cell within the measurement period. 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. Times
Unit
553
This counter counts the average number of EGPRS users in the cell and site within the measurement period. This counter is used to find out the maximum number of EGPRS users in current cell within the measurement period. 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. Times
Unit
This counter counts the maximum number of EDGE users in the cell and site within the measurement period. This counter is used to find out the maximum number of EDGE users in current cell within the measurement period. 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. Times
Unit
This counter counts the number of assigned uplink radio channels in the cell and site within the measurement period. This counter counts the number of assigned uplink radio channels in the cell and site within the measurement period.
554
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
This counter counts the number of assigned downlink radio channels in the cell and site within the measurement period. This counter counts the number of assigned downlink radio channels in the cell and site within the measurement period. 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 Times
Unit
This counter counts the number of requested uplink radio channels in the cell and site within the measurement period. This counter counts the number of requested uplink radio channels in the cell and site within the measurement period. Consistent with that for C901040047. Times
555
This counter counts the number of requested downlink radio channels in the cell and site within the measurement period. This counter counts the number of requested downlink radio channels in the cell and site within the measurement period. Consistent with that for C901040048. Times
This counter counts the number of attempts of channel expansion in PS service. 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. The counter counts when the RANUMC module receives the EV_DBS_PSCHANEXPAND message. Times
This counter counts the number of channel expansions in PS service. 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. This counter counts when the RANPS module receives the EV_RANUMC_PSCHANEXPAND message. Times
556
This counter counts the number of successful channel expansions in PS service. 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. This counter counts when the RANPS module successfully requests the resource for expansion from database. Times
557
558
Chapter
11
559
C901050022 Number of assignment executions for data due to directed retry .............................................................. 582 C901050023 Number of assignment for retry attempts FDD cell for voice channel ....................................................... 583 C901050024 Number of assignment executions for data due to directed retry to FDD cell for voice channel ..................... 584 C901050025 Number of assignment for retry attempts FDD cell for data .................................................................... 585 C901050026 Number of assignment executions for data due to directed retry to FDD cell for data .................................. 586 C901050027 Number of assignment for retry attempts TDD cell for voice channel ....................................................... 587 C901050028 Number of assignment executions for data due to directed retry to TDD cell for voice channel ..................... 588 C901050029 Number of assignment for retry attempts TDD cell for data .................................................................... 589 C901050030 Number of assignment executions for data due to directed retry to TDD cell for data .................................. 590 C901050031 Assignment unsuccessful due to circuit obstruction ............................................................................... 591 C901050032 Assignment unsuccessful due to circuit obstruction unmatched ............................................................... 592 C901050033 Assignment unsuccessful due to no valid radio resource......................................................................... 593 C901050034 Assignment unsuccessful due to other causes ........................................................................... 594 C901050035 Number of assignments attempts due to forced release (emergency service) ............................................. 595 C901050036 Number of assignment executions channel due to forced release (emergency service) ................................ 596 C901050037 Number of assignment attempts due to forced handover (emergency service) .......................................... 597 C901050038 Number of assignment executions channel due to forced handover (emergency service) ............................. 598 C901050039 Number of assignments channel due to queuing (emergency service) ........................................................ 599 C901050040 Number of assignments for execution channel due to queuing (emergency service) .................................. 600 C901050041 Number of forced handover target not found (assignment forced handover)........................................... 601 C901050042 Number of send forced handover request to lower PRI user (assignment forced handover)...................... 602 C901050043 Number of received failure from lower PRI user request resource for forced handover (assignment forced handover) ...................................................................... 603 C901050044 Number of lower PRI user handover failure (assignment forced handover) ............................................... 604 C901050045 Number of time out for wait resource (assignment forced handover)..................................................... 605 C901050046 Number of forced release target not found (assignment forced release) .................................................. 606 C901050047 Number of time out for wait resource (assignment forced release)........................................................ 607 C901050048 Number of get before grab released channel (assignment forced handover) ............................................... 608 C901050049 Number of get before grab released channel(assignment forced release) .................................................. 609 C901050050 The count of Assignment using FULL IP A-Interface ............................................................................... 610
560
C901050051 The count of Assignment using PCM over IP A-Interface ..................................................................... 611 C901050052 The count of Assignment using PCM over TDM A-Interface .................................................................... 612 C901050053 The count of Assignment Failure caused by "Requested Codec Type or Codec Configuration not supported" .......................................................................... 613 C901050054 The count of Assignment Failure caused by "Requested Codec Type or Codec Configuration unavailable" ............................................................................. 614 C901050055 The count of Assignment Failure caused by "Requested A-Interface Type not supported" ............................ 615 C901050056 The count of Assignment Failure caused by "Requested A-Interface Type unavailable" ................................ 616 C901050057 The count of Assignment Failure caused by "Call Identifier already allocated" .............................................. 617 C901050058 The count of Assignment Failure caused by "Requested Redundancy Level not supported" .......................... 618 C901050059 The count of Assignment Failure caused by "Call Access Control" ............................................................... 619 C901050060 Attempt Number of mode modify for assignment ............................................................................. 620 C901050061 Success Number of mode modify for assignment ............................................................................. 621 C901050062 Number of assignments for directed retry attempts for voice channel because of radio........................... 621 C901050063 Number of assignments for execution for voice channel due to directed retry because of radio..................... 622 C901050064 Number of assignments for directed retry attempts for data channel because of radio............................ 623 C901050065 Number of assignments for execution for data channel due to directed retry because of radio..................... 624
Overview
RMM assignment counter describers the assignment process. As many attempts can be made if no channel is available in the first assignment attempt, it is necessary to make a completed description of the whole assignment process instead of the assignment processes of TCH/F or TCH/H. These counters are used to analyze influences of forced release, queuing and directed retry, to assignment success rate from the viewpoint of calling.
561
Description
The way for BSC to get TCH in voice channel assignment process includes normal request, and queuing attempt or forced release if normal request is failed. This counter counts the number of general assignment executions for voice channel. 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. In voice channel assignment flow, the counter increments when source cell receives message that resource is available from target cell after sending channel request, and successfully sends assignment command. The measurement point is A, as shown in Figure 631.
FIGURE 631 MEASUREMENT POINT OF GENERAL ASSIGNMENT EXECUTIONS
Usage
Measurement Point
Unit
Times
Number of assignments attempts for voice due to forced release 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. This counter is used to find out the number of assignments for forced release attempts in MS accessing process. BSC fails in allocating channel due to no available resource. It releases other channels forcedly when the system allows. The counter increments when BSC fails in general voice channel assignment and the system allows forced release and finds a
562
proper instance of forcing release that sends forced release message to instance of forced release. The counter increments when BSC fails in general voice channel assignment and queuing attempt fails due to overtime and the system allows forced release and there is a proper instance of forced release that sends forced release message to instance of forced release. The measurement point is A, as shown in Figure 632.
C901050003 Number of assignment executions for voice channel due to forced release
Definition Description
Number of assignment executions for voice channel due to forced release 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. This counter is used to find out the number of assignment executions for voice channel due to forced release in MS accessing process.
Usage
563
Measurement Point
The counter increments if radio resource request fails in voice channel assignment, forced released can be carried out and instance of forcing release sends forced release message to instance of forced release, and resource available message is received and channel is obtained successfully. The measurement point is B, as shown in Figure 633.
FIGURE 633 MEASUREMENT
POINT OF ASSIGNMENT EXECUTIONS FOR VOICE CHANNEL DUE TO FORCED RELEASE
Number of handover attempts for voice due to forced release 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. This counter is used to find out the number of handover for forced release attempts for voice channel in MS accessing process. 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 634.
564
C901050005 Number of handover executions for voice channel due to forced release
Definition Description
Number of handover executions for voice channel due to forced release 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. This counter is used to find out the number of handover executions for voice channel due to forced release in MS accessing process. 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 635.
565
FIGURE 635 MEASUREMENT POINT OF HANDOVER EXECUTIONS FOR VOICE CHANNEL DUE TO FORCED RELEASE
Number of assignments for voice channel due to queuing 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. This counter is used to find out the number of assignments for queuing attempts for voice channel in MS accessing process. The counter increments when BSC fails in general voice channel assignment and the system allows queuing and the instance queues. The measurement point is A, as shown in Figure 636.
566
C901050007 Number of assignments for execution for voice channel due to queuing
Definition Description
Number of assignments for execution for voice channel due to queuing 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. 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 637.
Measurement Point
567
FOR
EXECUTION
FOR
Duration of assignment success voice channel due to queuing This counter counts the total duration of successful assignment for queuing voice channel in allocation process. The duration of successful assignment for queuing for voice channel is the time when channel is obtained minus the time when the instance began to queue. The counter accumulates the total durations of successful assignment for queuing for voice channel.
This counter is used to check the intra-cell queuing status and represents whether queuing can relieve traffic congestion effectively. 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 638.
568
FIGURE 638 MEASUREMENT POINT OF ASSIGNMENTS FOR EXECUTION FOR VOICE CHANNEL DUE TO QUEUING
Unit
Times
Number of assignments success for voice channel due to queuing This counter counts the number of successful assignments of queuing for voice channel. This counter is used to check the intra-cell queuing status and represents whether queuing can relieve traffic congestion effectively. 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 639.
569
FIGURE 639 MEASUREMENT POINT OF ASSIGNMENTS FOR EXECUTION FOR VOICE CHANNEL DUE TO QUEUING
Unit
Times
C901050010 Number of assignments for directed retry attempts for voice channel
Definition Description
Number of assignments for directed retry attempts for voice channel 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. 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. 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 640.
Usage
Measurement Point
570
OF
ASSIGNMENTS
FOR
DIRECTED RETRY
C901050011 Number of assignments for execution for voice channel due to directed retry
Definition Description Usage Measurement Point
Number of assignments for execution for voice channel due to directed retry This counter counts the number of assignments for execution for voice channel due to directed retry This counter is used to check the process and result of directed retry. The counter increments when directed retry is carried out and target cell obtains channel successfully and source cell receives radio resource available message from target cell in voice channel assignment process. The measurement point is B, as shown in Figure 641.
571
FIGURE 641 MEASUREMENT POINT OF ASSIGNMENTS VOICE CHANNEL DUE TO DIRECTED RETRY
FOR
EXECUTION
FOR
Number of general assignments for execution for data 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. 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. In data channel assignment flow, the counter increments when source cell receives resource is available message from target cell after sending channel request, and successfully sends assignment command. The measurement point is A, as shown in Figure 642.
Usage
Measurement Point
572
Unit
Times
Number of assignments attempts for data due to forced release 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. This counter is used to find out the number of assignments for forced release attempts in MS accessing process. BSC fails in allocating channel due to no available resource and releases other channel forcedly when the system allows. The counter increments when BSC fails in general data channel assignment and the system allows forced release and there is a proper instance of forcing release that sends forced release message to instance of forced release. The counter increments when BSC fails in general data channel assignment and queuing attempt fails due to overtime and the system allows forced release and finds a proper instance of forcing release that sends forced release message to instance of forced release. The measurement point is A, as shown in Figure 643.
573
Number of assignment executions for data due to forced release 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. This counter is used to find out the number of assignment executions for data channel due to forced release in MS accessing process. The counter increments if radio resource request fails in data channel assignment, forced released can be carried out and instance of forcing release sends forced release message to instance of forced release, and resource available message is received and channel is obtained successfully. The measurement point is B, as shown in Figure 644.
Usage
Measurement Point
574
FIGURE 644 MEASUREMENT POINT OF ASSIGNMENT EXECUTIONS CHANNEL DUE TO FORCED RELEASE
FOR
VOICE
Number of handover attempts for data due to forced release 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. This counter is used to find out the number of handover for forced release attempts for data channel in MS accessing process. The counter increments when BSC fails in general data channel assignment and the system allows forced release and there is proper instance of forcing release that sends forced release message to instance of forced release. The measurement point is A, as shown in Figure 645.
575
OF
HANDOVER
FOR
FORCED RELEASE
Number of handover executions for data due to forced release 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. This counter is used to find out the number of handover executions for data channel due to forced release in MS accessing process. The counter increments if radio resource request fails in data channel assignment, handover for data channel due to forced release can be carried out and instance of forcing handover sends forced handover message to instance of forced handover, and resource availablemessage is received and channel is obtained successfully. The measurement point is B, as shown in Figure 646.
576
FIGURE 646 MEASUREMENT POINT OF HANDOVER EXECUTIONS FOR VOICE CHANNEL DUE TO FORCED RELEASE
Number of assignments attempts for data due to queuing 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. This counter is used to find out the number of assignments for queuing attempts for data channel in MS accessing process. 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 647.
577
Number of assignments for execution for data due to queuing 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. The counter increments if radio resource request fails in data channel assignment, queuing can be carried out and instance of queuing receives resource available message and obtains channel successfully. The measurement point is B, as shown in Figure 648.
Measurement Point
578
FIGURE 648 MEASUREMENT POINT OF ASSIGNMENTS FOR EXECUTION FOR VOICE CHANNEL DUE TO QUEUING
Total duration of successful assignments for data due to queuing This counter counts the total duration of successful assignment for queuing for data channel in allocation process. The duration of successful assignment for queuing for data channel is the time when channel is obtained minus the time when the instance began to queue. The counter accumulates the total durations of successful assignment for queuing for data channel.
This counter is used to check the intra-cell queuing status and represents whether queuing can relieve traffic congestion effectively. 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 649.
579
FIGURE 649 MEASUREMENT POINT OF ASSIGNMENTS FOR EXECUTION FOR VOICE CHANNEL DUE TO QUEUING
Unit
Times
This counter counts the number of successful assignments of queuing for data channel. This counter is used to check the intra-cell queuing status and represents whether queuing can relieve traffic congestion effectively. The counter increments if radio resource request fails in data channel assignment, queuing can be carried out and instance of queuing receives resource available message and obtains channel successfully. The measurement point is B, as shown in Figure 650.
580
FIGURE 650 MEASUREMENT POINT OF ASSIGNMENTS FOR EXECUTION FOR VOICE CHANNEL DUE TO QUEUING
Unit
Times
Number of assignments attempts for data due to directed retry 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. 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. 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 651.
Usage
Measurement Point
581
OF
ASSIGNMENTS
FOR
DIRECTED RETRY
Number of assignment executions for data due to directed retry This counter counts the number of assignments for execution for data channel due to directed retry This counter is used to check the process and result of directed retry. The counter increments when directed retry is carried out and target cell successfully obtains channel and source cell receives radio resource available message from target cell in data channel assignment process. The measurement point is B, as shown in Figure 652.
582
FIGURE 652 MEASUREMENT POINT OF ASSIGNMENTS VOICE CHANNEL DUE TO DIRECTED RETRY
FOR
EXECUTION
FOR
C901050023 Number of assignment for retry attempts FDD cell for voice channel
Definition Description Usage
Number of assignment for retry attempts FDD cell for voice channel This counter counts the number of assignment for retry attempts FDD cell for voice channel. 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. The counter increments in voice channel assignment when source cell receives no available radio resource message from FDD cell and source cell supports directed retry and FDD cell that meets the directed retry demand can be found and Radio_App message is sent to FDD cell. The measurement point is A, as shown in Figure 653.
Measurement Point
583
OF
ASSIGNMENTS
FOR
DIRECTED RETRY
Times 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
C901050024 Number of assignment executions for data due to directed retry to FDD cell for voice channel
Definition Description Usage
Number of assignment executions for data due to directed retry to FDD cell for voice channel This counter counts the number of assignment executions due to directed retry to FDD cell for voice channel. 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. The counter increments in voice channel assignment when target cell in directed retry is FDD cell and successfully obtains channel and source cell receives resource available message from target cell. The measurement point is B, as shown in Figure 654.
Measurement Point
584
FIGURE 654 MEASUREMENT POINT OF ASSIGNMENTS VOICE CHANNEL DUE TO DIRECTED RETRY
FOR
EXECUTION
FOR
Times 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
C901050025 Number of assignment for retry attempts FDD cell for data
Definition Description Usage
Number of assignment for retry attempts FDD cell for data This counter counts the number of assignment for retry attempts FDD cell for data channel. 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. 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 655.
Measurement Point
585
OF
ASSIGNMENTS
FOR
DIRECTED RETRY
Times 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
C901050026 Number of assignment executions for data due to directed retry to FDD cell for data
Definition Description Usage
Number of assignment executions for data due to directed retry to FDD cell for data This counter counts the number of assignment executions due to directed retry to FDD cell for data channel. 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. The counter increments in data channel assignment when target cell in directed retry is FDD cell and successfully obtains channel and source cell receives radio resource available message from target cell. The measurement point is B, as shown in Figure 656.
Measurement Point
586
FIGURE 656 MEASUREMENT POINT OF ASSIGNMENTS VOICE CHANNEL DUE TO DIRECTED RETRY
FOR
EXECUTION
FOR
Times 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
C901050027 Number of assignment for retry attempts TDD cell for voice channel
Definition Description Usage
Number of assignment for retry attempts TDD cell for voice channel This counter counts the number of assignment for retry attempts TDD cell for voice channel. 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. 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 657.
Measurement Point
587
OF
ASSIGNMENTS
FOR
DIRECTED RETRY
Times ZGB-03-01-002 Directed Retry ZGO-02-02-014 IMSI Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing
C901050028 Number of assignment executions for data due to directed retry to TDD cell for voice channel
Definition Description Usage
Number of assignment executions for data due to directed retry to TDD cell for voice channel This counter counts the number of assignment executions due to directed retry to TDD cell for voice channel. 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. 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.
Measurement Point
588
FIGURE 658 MEASUREMENT POINT OF ASSIGNMENTS VOICE CHANNEL DUE TO DIRECTED RETRY
FOR
EXECUTION
FOR
Times ZGB-03-01-002 Directed Retry ZGO-02-02-014 IMSI Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing
C901050029 Number of assignment for retry attempts TDD cell for data
Definition Description Usage
Number of assignment for retry attempts TDD cell for data This counter counts the number of assignment for retry attempts TDD cell for data channel. 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. 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 659.
Measurement Point
589
OF
ASSIGNMENTS
FOR
DIRECTED RETRY
Times ZGB-03-01-002 Directed Retry ZGO-02-02-014 IMSI Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing
C901050030 Number of assignment executions for data due to directed retry to TDD cell for data
Definition Description Usage
Number of assignment executions for data due to directed retry to TDD cell for data This counter counts the number of assignment executions due to directed retry to TDD cell for data channel. 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. 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 660.
Measurement Point
590
FIGURE 660 MEASUREMENT POINT OF ASSIGNMENTS VOICE CHANNEL DUE TO DIRECTED RETRY
FOR
EXECUTION
FOR
Times ZGB-03-01-002 Directed Retry ZGO-02-02-014 IMSI Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing
Assignment unsuccessful due to circuit obstruction This counter counts the number of the assignment failure due to circuit obstruction on A-interface. 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. 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 661.
Measurement Point
591
DUE TO
Unit
Times
Assignment unsuccessful due to circuit obstruction unmatched This counter counts the number of assignment failure due to circuit unmatched on A-interface. 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. 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 662.
Measurement Point
592
DUE TO
Unit
Times
Assignment unsuccessful due to no valid radio resource This counter counts the number assignment failure due to no valid radio resource. 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. 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 663. Source cell sends channel request to target cell after receiving assignment request message; the counter increments if Radio_App is overtime due to no responding message. The measurement point is A, as shown inFigure 663.
Measurement Point
593
DUE TO
Unit
Times
Assignment unsuccessful due to other causes This counter counts the number assignment failure due to other causes on A-interface. 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. 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 664.
Measurement Point
594
DUE TO
Unit
Times
Number of assignment attempts due to forced release (emergency service) 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. 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. BSC fails to assign channel due to no available resource, if forced release is allowed, BSC will forcibly release other channels. During an emergency call, BSC fails to assign voice channel. If forced release is allowed and there is suitable forced release instance, then the counter increments when the forcing release instance sends the forced release message to the forced release instance. The measurement point is A, as shown in Figure 665.
Usage
Measurement Point
595
FIGURE 665 MEASUREMENT POINT OF NUMBER OF ASSIGNMENT ATTEMPTS DUE TO FORCED RELEASE (EMERGENCY SERVICE)
Unit
Times
C901050036 Number of assignment executions channel due to forced release (emergency service)
Definition Description
Number of assignment executions channel due to forced release (emergency service) BSC fails to assign voice channel due to no available resource, if it obtains needed channel within specified time after the forced release is performed, then the forced release is considered successful. If the call is an emergency call, the counter counts the number of successful forced releases (emergency service). 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. During the voice channel assignment process, if the radio resource request fails and forced release is allowed, the forcing release instance sends the forced release message to the forced release instance. If the message of resource available is received, then the resource is obtained successfully, and in this case, the counter increments. The measurement point is B, as shown in Figure 666.
Usage
Measurement Point
596
FIGURE 666 MEASUREMENT POINT OF NUMBER OF ASSIGNMENT ATTEMPTS DUE TO FORCED RELEASE (EMERGENCY SERVICE)
Unit
Times
Number of assignment attempts due to forced handover (emergency service) 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. 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. 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 667.
Usage
Measurement Point
597
OF
HANDOVER
FOR
FORCED RELEASE
Unit
Times
C901050038 Number of assignment executions channel due to forced handover (emergency service)
Definition Description
Number of assignment executions channel due to forced handover(emergency service) 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. 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. 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 668.
Usage
Measurement Point
598
FIGURE 668 MEASUREMENT POINT OF HANDOVER EXECUTIONS FOR VOICE CHANNEL DUE TO FORCED RELEASE
Unit
Times
Number of assignments channel due to queuing (emergency service) 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). This counter is used to find out the number of assignment attempts due to queuing during the MS access process of an emergency call. 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 669.
599
Unit
Times
C901050040 Number of assignments for execution channel due to queuing (emergency service)
Definition Description
Number of assignments for execution channel due to queuing (emergency service) 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). This counter is used to find out the number of successful assignments due to queuing during the MS access process of an emergency call. 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 670.
Usage
Measurement Point
600
FIGURE 670 MEASUREMENT POINT OF ASSIGNMENTS FOR EXECUTION FOR VOICE CHANNEL DUE TO QUEUING
Unit
Times
C901050041 Number of forced handover target not found (assignment forced handover)
Definition Description
Number of forced handover target not found (assignment forced handover) 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. 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. 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 671.
Usage
Measurement Point
601
FIGURE 671 MEASUREMENT POINT OF NUMBER OF FORCED HANDOVER TARGET NOT FOUND (ASSIGNMENT FORCED HANDOVER)
Unit
Times
C901050042 Number of send forced handover request to lower PRI user (assignment forced handover)
Definition Description
Number of send forced handover request to lower PRI user (assignment forced handover) 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. 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. 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 672.
Usage
Measurement Point
602
OF
HANDOVER
FOR
FORCED RELEASE
Unit
Times
C901050043 Number of received failure from lower PRI user request resource for forced handover (assignment forced handover)
Definition Description
Number of received failure from lower PRI user request resource for forced handover (assignment forced handover) 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. 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. When BSC fails to assign voice channel, if forced handover is allowed and there is suitable forcing handover instance, then the
Usage
Measurement Point
603
counter increments in the following case: the forcing handover instance sends the forced handover message to the forced handover instance and simultaneously receives the forced handover failure message which is due to resource request failure. The measurement point is B, as shown in Figure 673.
FIGURE 673 MEASUREMENT POINT OF NUMBER OF RECEIVING FORCED HANDOVER FAILURE MESSAGE FROM LOW PRIORITY USER DURING FORCED HANDOVER
Unit
Times
C901050044 Number of lower PRI user handover failure (assignment forced handover)
Definition Description
Number of lower PRI user handover failure (assignment forced handover) 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. 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.
Usage
604
Measurement Point
When BSC fails to assign voice channel, if forced handover is allowed and there is suitable forced handover target instance, then the counter increments in the following case: the forcing handover instance sends the forced handover message to the forced handover target instance and simultaneously receives the forced handover failure message which is due to handover execution failure. The measurement point is B, as shown in Figure 674.
FIGURE 674 MEASUREMENT POINT OF NUMBER OF RECEIVING FORCED HANDOVER FAILURE MESSAGE FROM LOW PRIORITY USER DURING FORCED HANDOVER
Unit
Times
C901050045 Number of time out for wait resource (assignment forced handover)
Definition Description
Number of time out for wait resource (assignment forced handover) 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. 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.
Usage
605
Measurement Point
When BSC fails to assign voice channel, if forced handover is allowed and there is suitable forced handover target instance, then the counter increments when the waiting for forced handover target instance resource is timeout. The measurement point is B, as shown in Figure 675.
FIGURE 675 MEASUREMENT POINT OF NUMBER OF TIMEOUT FOR WAIT RESOURCE (ASSIGNMENT FORCED HANDOVER)
Unit
Times
C901050046 Number of forced release target not found (assignment forced release)
Definition Description
Number of forced release target not found (assignment forced release) 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. 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. During an emergency call, BSC fails to assign voice channel. If forced release is allowed but there is no suitable forced release
Usage
Measurement Point
606
instance, then the counter increments. The measurement point is A, as shown in Figure 676.
FIGURE 676 MEASUREMENT POINT OF NUMBER OF FORCED RELEASE TARGET NOT FOUND (ASSIGNMENT FORCED RELEASE)
Unit
Times
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. 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. 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 677.
Usage
Measurement Point
607
FIGURE 677 MEASUREMENT POINT OF NUMBER OF TIMEOUT FOR WAIT RESOURCE (ASSIGNMENT FORCED RELEASE
Unit
Times
C901050048 Number of get before grab released channel (assignment forced handover)
Definition Description
Number of get before grab released channel (assignment forced handover) 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. 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. 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 678.
Usage
Measurement Point
608
FIGURE 678 MEASUREMENT POINT OF HANDOVER EXECUTIONS FOR VOICE CHANNEL DUE TO FORCED RELEASE
Unit
Times
Number of get before grab released channel (assignment forced release) 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). This counter is used to find out the number of successful assignments due to forced release during the MS access process. 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 679.
609
FIGURE 679 MEASUREMENT POINT OF NUMBER OF ASSIGNMENT ATTEMPTS DUE TO FORCED RELEASE (EMERGENCY SERVICE)
Unit
Times
CELL On the premise that the 3GPP IPA function is implemented, when MSC's assignment request, which is of voice type, data type, or fax service type, is received, the system selects A-interface transmission mode according to the assignment request's content. After MS assignment is completed, BSC decides the A-interface transmission mode for the service before sending the assignment completion message. If the A-interface transmission mode is all-IP A-interface transmission, the counter increments. The measurement point is A, as shown in Figure 680.
610
OF THE
COUNT
OF
Unit
Times
CELL On the premise that the 3GPP IPA function is implemented, when MSC's assignment request, which is of voice type, data type, or fax service type, is received, the system selects A-interface transmission mode according to the assignment request's content. After MS assignment is completed, BSC decides the A-interface transmission mode for the service before sending the assignment completion message. If the A-interface transmission mode is PCMoIP transmission, the counter increments. The measurement point is A, as shown in Figure 681.
611
OF THE
COUNT
OF
OVER
IP
Unit
Times
CELL On the premise that the 3GPP IPA function is implemented, when MSC's assignment request, which is of voice type, data type, or fax service type, is received, the system selects A-interface transmission mode according to the assignment request's content. After MS assignment is completed, BSC decides the A-interface transmission mode for the service before sending the assignment completion message. If the A-interface transmission mode is TDM transmission, the counter increments. The measurement point is A, as shown in Figure 682.
612
OF THE
COUNT
OF
OVER
TDM
Unit
Times
C901050053 The count of Assignment Failure caused by "Requested Codec Type or Codec Configuration not supported"
Statistics object Description
CELL On the premise that the 3GPP IPA function is implemented, when MSC's assignment request, which is of voice type, data type, or fax service type, is received, the system selects the voice version according to the field Codec List (MSC Preferred) in the assignment request. In the field Codec List (MSC Preferred), if the voice coding type or combination is not the voice version supported by BSC, then the assignment failure message is sent to MSC, and the counter increments. (At present, there is no voice coding type or combination not supported by BSC. Thus the counter does not have counting value. ) The measurement point is A, as shown in Figure 683.
613
FIGURE 683 MEASUREMENT POINT OF THE COUNT OF ASSIGNMENT FAILURE CAUSED CODEC TYPE OR CODEC CONFIGURATION NOT SUPPORTED"
BY
"REQUESTED
Unit
Times
C901050054 The count of Assignment Failure caused by "Requested Codec Type or Codec Configuration unavailable"
Statistics object Description
CELL On the premise that the 3GPP IPA function is implemented, when MSC's assignment request, which is of voice type, data type, or fax service type, is received, the system selects the voice version according to the field Codec List (MSC Preferred) in the assignment request. According to the voice coding type or combination in the field Codec List (MSC Preferred), if it fails to request corresponding radio channel (i.e. the radio channel type available in the current cell is not consistent with the requested channel type), then the assignment failure message is sent to MSC, and the counter increments. The measurement point is B, as shown in Figure 684.
614
FIGURE 684 MEASUREMENT POINT OF THE COUNT OF ASSIGNMENT FAILURE CAUSED CODEC TYPE OR CODEC CONFIGURATION UNAVAILABLE"
BY
"REQUESTED
Unit
Times
C901050055 The count of Assignment Failure caused by "Requested A-Interface Type not supported"
Statistics object Description
CELL On the premise that the 3GPP IPA function is implemented, when MSC's assignment request, which is of voice type, data type, or fax service type, is received, the system selects 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 685.
615
THE
COUNT
OF
BY
"REQUESTED
Unit
Times
C901050056 The count of Assignment Failure caused by "Requested A-Interface Type unavailable"
Statistics object Description
CELL On the premise that the 3GPP IPA function is implemented, when MSC's assignment request, which is of voice type, data type, or fax service type, is received, the system selects voice version as well as A-interface transmission mode according to the field Codec List (MSC Preferred) in the assignment request. After the system selects an A-interface transmission mode, if such a transmission mode can not be used in the current cases (for example, in the case of IP resource request failure or access failure), then the assignment failure message is sent to MSC, and the counter increments. The measurement point is C, as shown in Figure 686.
616
OF THE
COUNT
OF
BY
"REQUESTED
Unit
Times
C901050057 The count of Assignment Failure caused by "Call Identifier already allocated"
Statistics object Description
CELL On the premise that the 3GPP IPA function is implemented, when MSC's assignment request, which is of voice type, data type, or fax service type, is received, the system selects voice version as well as A-interface transmission mode according to the field Codec List (MSC Preferred) in the assignment request. If the system uses all-IP A-interface transmission, it is necessary to check whether there are any same Call IDs of IP calls. If there are, then the assignment failure message is sent to MSC, and the counter increments. The measurement point is A, as shown in Figure 687.
617
OF THE
COUNT
OF
BY
"CALL
Unit
Times
C901050058 The count of Assignment Failure caused by "Requested Redundancy Level not supported"
Statistics object Description
CELL 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 688.
618
THE
COUNT
OF
BY
"REQUESTED
Unit
Times
CELL On the premise that the 3GPP IPA function is implemented, when MSC's assignment request, which is of voice type, data type, or fax service type, is received, the system requests radio channel according to the assignment request. If the database returns the message that radio channel request fails due to insufficient Abis resource, then the assignment failure message is sent to MSC, and the counter increments. The measurement point is C, as shown in Figure 689.
619
OF THE
COUNT
OF
BY
"CALL
Unit
Times
This counter counts the number of attempts for mode modification. This counter counts the number of attempts for mode modification in the process of assignment. 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. Times
Unit
620
This counter counts the number of successes for mode modification. This counter counts the number of successes for mode modification in the process of assignment. 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. Times
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 690.
621
OF
NUMBER
OF
DIRECTED RETRIES
DUE
Times Cell
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 691.
622
Times Cell
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 692.
623
OF
NUMBER
OF
DIRECTED RETRIES
DUE
Times Cell
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 693.
624
Times Cell
625
626
Chapter
12
627
C901060022 Number of SDCCH handover attempts due to increased TA .................................................................. 646 C901060023 Number of SDCCH handover attempts due to TA decrease ........................................................................ 647 C901060024 Number of SDCCH Handover attempt due to other factors .................................................................. 648 C901060035 Number of TCH/F handover attempts due to quick break up of UL ........................................................ 649 C901060036 Number of TCH/F handover attempts due to macro-micro switch ......................................................... 649 C901060037 Number of TCH/F handover attempts due to MSC request .......................................................................... 650 C901060038 Number of TCH/F handover attempts due to traffic ................................................................................. 651 C901060039 Number of TCH/F handover attempts due to large TA and wastage....................................................... 652 C901060040 Number of TCH/F handover attempts due to small TA and wastage ...................................................... 653 C901060041 Number of TCH/F handover attempts due to preferable electricity level in 3G adjacent cell ..................... 653 C901060042 Number of TCH/F handover attempts due to forced transfer ................................................................ 654 C901060043 Number of TCH/F handover during assignment due to forced transfer ...................................................... 655 C901060044 Number of TCH/F handover attempts during handover due to forced transfer ........................................ 656 C901060045 Number of TCH/F handover attempts due to TA increase ......................................................................... 657 C901060046 Number of TCH/F handover attempts due to TA decrease ........................................................................ 658 C901060058 Number of TCH/H handover attempts due to quick break up of UL ........................................................ 659 C901060059 Number of TCH/H handover attempts due to macro-micro switch ......................................................... 660 C901060060 Number of TCH/H handover attempts due to MSC request ................................................................... 660 C901060061 Number of TCH/H handover attempts due to traffic............................................................................. 661 C901060062 Number of TCH/H handover attempts due to large TA and wastage....................................................... 662 C901060063 Number of TCH/H handover attempts due to small TA and wastage ...................................................... 663 C901060064 Number of TCH/H handover attempts due to a preferable electricity level in 3G adjacent cell ...................... 664 C901060065 Number of TCH/H handover attempts due to forced transfer ................................................................ 665 C901060066 Number of TCH/H handover attempts during assignment due to forced transfer......................................... 665 C901060067 Number of TCH/H handover attempts during handover due to forced transfer ........................................ 667 C901060068 Number of TCH/H handover attempts during handover due to TA increase ............................................. 668 C901060069 Number of TCH/H handover attempts during handover due to TA decrease ............................................ 669 C901060070 Number of TCH/H handover attempts due to other reasons.................................................................. 669 C901060071 Number of TCH/F handover attempts due to CS channel transfer .............................................................. 670 C901060072 Number of TCH/H handover attempts due to CS channel transfer .............................................................. 671
628
C901060073 Number of TCH/H handover attempts due to Fragment reorganization .................................................. 672 C901060074 Number of TCH/F handover attempts due to energy conservation ............................................................ 673 C901060075 Number of TCH/F handover attempts due to energy conservation ............................................................ 674 C901060076 Number of TCH/F handover attempts due to CS channel is forced release .................................................. 675 C901060077 Number of TCH/H handover attempts due to CS channel is forced release .................................................. 676 C901060078 Number of TCH/F handover attempts due to FR to HR during cell busy ...................................................... 677 C901060079 Number of SDCCH handover attempts due to downlink rapid drop ......................................................... 678 C901060080 Number of TCH/F handover attempts due to downlink rapid drop ......................................................... 678 C901060081 Number of TCH/H handover attempts due to downlink rapid drop ......................................................... 678 C901060082 Attempts of handover on TCH/F caused by power adjustment ..................................................................... 679 C901060083 Attempts of handover on TCH/H caused by power adjustment ........................................................... 679 C901060084 Attempts of handover on TCH/F caused by local switch ............................................................................ 680 C901060085 Attempts of handover on TCH/H caused by local switch ............................................................................ 680 C901060086 Attempts of handover on TCH/F caused by reducing band resources of IPAbis ........................................ 681 C901060087 Attempts of handover on TCH/H because of MASTERPWR_ALM from TRX ............................................. 681 C901060088 Attempts of handover on TCH/F because of MASTERPWR_ALM from TRX.................................................... 682 C901060089 Number of handover attempts due to directed retry for PBGT................................................................. 683 C901060090 Number of SDCCH handover attempts due to DL quality rapid drop ............................................................ 684 C901060091 Number of TCH/F handover attempts due to DL quality rapid drop ............................................................ 684 C901060092 Number of TCH/H handover attempts due to DL quality rapid drop ............................................................ 685
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.
629
Number of handover attempts due to directed retry During the process of MS requests channel, if radio resource is congested, then it will attempt to request an available channel from adjacent cell for this call. This is called direct retry, which is a kind of handover. This counter counts the number of handover attempts due to direct retry. 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. 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 694.
FIGURE 694 DIRECTED RETRY JUDGMENT
Usage
Measurement Point
630
Number of SDCCH handover attempts due to UL received strength This counter counts the number of handover attempts due to too low uplink received strength (on SDCCH). 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. 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 695.
FIGURE 695 HANDOVER DECISION
Measurement Point
Number of SDCCH handover attempts due to DL received strength This counter counts the number of handover attempts due to too low downlink received strength (on SDCCH). 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. BSC carries out handover judgment after receiving SDDCH measurement report; the counter increments if judgment result is yes
Measurement Point
631
and handover cause is downlink signal strength. The measurement point is A, as shown in Figure 696.
FIGURE 696 HANDOVER DECISION
Number of SDCCH Handover attempt due to UL quality. This counter counts the number of handover attempts due to too bad uplink quality (on SDCCH). 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. 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 697.
FIGURE 697 HANDOVER DECISION
Measurement Point
632
Number of SDCCH Handover attempt due to DL quality. This counter counts the number of handover attempts due to too bad downlink quality (on SDCCH). 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. 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 698.
FIGURE 698 HANDOVER DECISION
Measurement Point
Number of SDCCH handover attempts due to UL interference. This counter counts the number of handover attempts due to too high uplink interference (on SDCCH). 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. 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 699.
Measurement Point
633
Number of SDCCH handover attempts due to DL interference. This counter counts the number of handover attempts due to too high downlink interference (on SDCCH). 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. 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 700.
FIGURE 700 HANDOVER DECISION
Measurement Point
634
Number of SDCCH inter-subcell handover attempts due to good C/I This counter counts the number of handover attempts due to too high C/I RATIO (on SDCCH). This handover only happens in subcell configuration and C/I algorithm is used; MS is handed over from first cell to second cell. 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. 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 701.
FIGURE 701 HANDOVER DECISION
Usage
Measurement Point
635
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. 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. 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 702.
FIGURE 702 HANDOVER DECISION
Usage
Measurement Point
Number SDCCH of handover attempts due to PBGT 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. 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. 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 703.
Usage
Measurement Point
636
Number of SDCCH handover attempts due to large TA 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. 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. 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 704.
FIGURE 704 HANDOVER DECISION
Usage
Measurement Point
637
Number of SDCCH handover attempts due to quick break up of UL 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. 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. 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 705.
FIGURE 705 HANDOVER DECISION
Usage
Measurement Point
Times ZGO-02-02-004 SDCCH/SDCCH Handover ZGO-02-02-006 Rapid Level Drop Handover ZGO-02-02-015 Enhanced Cell Reselection Procedure
Number of SDCCH handover attempts due to macro-micro switch. 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.
638
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. 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 706.
FIGURE 706 HANDOVER DECISION
Measurement Point
Times ZGO-02-02-001 Handover between Macro- and Micro-cells ZGO-02-02-004 SDCCH/SDCCH Handover
Number of SDCCH handover attempts due to MSC request. 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. 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. BSC carries out handover judgment after receiving HO_ENQUIRY message sent by MSC; the counter increments if judgment result is yes. The measurement point is A, as shown inFigure 707.
Usage
Measurement Point
639
Number of SDCCH handover attempts due to traffic. 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. 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. BSC carries out handover judgment after receiving SDCCH traffic alarm, the counter increments if judgment result is yes. The measurement point is A, as shown in Figure 708. DBS, UMC and RANCS are all instances of BSC and they take part in handover due to traffic.
Usage
Measurement Point
640
Times ZGO-02-02-004 SDCCH/SDCCH Handover ZGO-02-02-007 Traffic Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing
Number of SDCCH handover attempts due to large TA and wastage. This counter counts the number of handover attempts due to large TA and wastage (on SDCCH). This handover only happens in subcell configuration and TA & PassLoss algorithm is used; when both TA and PassLoss are higher than set threshold, MS is handed over from second cell to first cell. 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. 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 709.
Usage
Measurement Point
641
Number of SDCCH handover attempts due to small TA and wastage. This counter counts the number of handover attempts due to small TA and wastage (on SDCCH). This handover only happens in subcell configuration and TA & PassLoss algorithm is used; when both TA and PassLoss are lower than set threshold, MS is handed over from first cell to second cell. 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. 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 710.
FIGURE 710 HANDOVER DECISION
Usage
Measurement Point
642
C901060018 Number of SDCCH Handover attempt due to a preferable electricity level of 3G adjacent cell
Definition Description Usage
Number of SDCCH handover attempt due to a preferable electricity level of FDD adjacent cell. This counter counts the number of handover attempts due to a good standard level in FDD adjacent cell (on SDCCH). 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. 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 711.
FIGURE 711 HANDOVER DECISION
Measurement Point
Times ZGO-02-02-004 SDCCH/SDCCH Handover ZGO-02-03-002 GSM/WCDMA Interworking ZGO-02-03-003 GERAN/UTRAN Load Sharing
Number SDCCH handover attempts due to forced transfer. This counter counts the number of forced transfer handover attempts (on SDCCH). If the TCH utilizing rate of the present cell reaches a set percentage of the threshold, BSC will try to handover
643
subscriber whose path loss and TA are small from the present cell to some set cells. This kind of handover is called forced transfer handover.
Usage
This counter is used to find out frequency of forced transfer handover attempts (on SDCCH); its value can represent the present cells channel utilizing status and traffic sharing status. 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 712.
FIGURE 712 HANDOVER DECISION
Measurement Point
Number of SDCCH handover during assignment due to forced transfer. 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. 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. 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
Usage
Measurement Point
644
forced handover instance is SDCCH. The measurement point is A, as shown in Figure 713.
FIGURE 713 FORCED HANDOVER JUDGMENT
Number of SDCCH handover during handover due to forced transfer. This counter counts the number of forced handovers during handover (on SDCCH).
645
Usage
This counter is used to find out frequency of forced handovers during handover (on SDCCH); its value can represent the present cells TCH utilizing status and traffic sharing status. BSC has no available TCH to allocate during the handover process and it carries out forced handover judgment; the counter increments if judgment result is yes and the channel type of forced handover instance is SDCCH. The measurement point is A, as shown in Figure 714.
FIGURE 714 FORCED HANDOVER JUDGMENT
Measurement Point
Number of SDCCH handover attempts due to increased TA. This counter counts the number of handover attempts due to increased TA (on SDCCH). This handover only happens in expanding cell configuration, present BSC version does not use expanded cell
646
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 Measurement Point
This counter is used to find out frequency of MS handover from second cell to first cell in sub-cell. 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 715.
FIGURE 715 HANDOVER DECISION
Number of SDCCH handover attempts due to TA decrease. 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. This counter is used to find out frequency of MS handover from first cell to second cell in sub-cell. 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 716.
647
Number of SDCCH Handover attempt due to other factors. This counter counts the number of handover attempts due to any other reason except reasons mentioned above (on SDCCH). This counter is used to find out frequency of handover attempts due to any other reason (on SDCCH). 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 717.
FIGURE 717 HANDOVER DECISION
648
Number of TCH/F handover attempts due to quick break up of UL. 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. 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. 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 718.
FIGURE 718 HANDOVER DECISION
Usage
Measurement Point
Times 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
Number of TCH/F handover attempts due to macro-micro switch. 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.
649
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. 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 719.
FIGURE 719 HANDOVER DECISION
Measurement Point
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-02-02-001 Handover between Macro- and Micro-cells
Number of TCH/F handover attempts due to MSC request. 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. 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. BSC carries out handover judgment after receiving HO_ENQUIRY message sent by MSC; the counter increments if judgment result is yes. The measurement point is A, as shown in Figure 720.
Usage
Measurement Point
650
Number of TCH/F handover attempts due to traffic. 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. 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. BSC carries out handover judgment after receiving TCH/F traffic alarm, the counter increments if judgment result is yes. The measurement point is A, as shown in Figure 721.
FIGURE 721 TRAFFIC HANDOVER
Usage
Measurement Point
651
Times 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
Number of TCH/F handover attempts due to large TA and wastage. This counter counts the number of handover attempts due to large TA and wastage (on TCH/F). This handover only happens in subcell configuration and TA & PassLoss algorithm is used; when both TA and PassLoss are higher than set threshold, MS is handed over from second cell to first cell. 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. 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 722.
FIGURE 722 HANDOVER DECISION
Usage
Measurement Point
652
Number of TCH/F handover attempts due to small TA and wastage. This counter counts the number of handover attempts due to small TA and wastage (on TCH/F). This handover only happens in subcell configuration and TA & PassLoss algorithm is used; when both TA and PassLoss are lower than set threshold, MS is handed over from first cell to second cell. 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. 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 723.
FIGURE 723 HANDOVER DECISION
Usage
Measurement Point
C901060041 Number of TCH/F handover attempts due to preferable electricity level in 3G adjacent cell
Definition Description
Number of TCH/F handover attempts due to preferable electricity level in 3G adjacent cell. This counter counts the number of handover attempts due to a good standard level in 3G adjacent cell (on TCH/F).
653
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. 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 724.
FIGURE 724 HANDOVER DECISION
Measurement Point
Times 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
Number of TCH/F handover attempts due to forced transfer. 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. 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. BSC carries out handover judgment after receiving TCH/F measurement report; the counter increments if judgment result is yes and handover cause is forced transfer handover attempts (on TCH/F). The measurement point is A, as shown in Figure 725.
Usage
Measurement Point
654
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-02-02-003 Directed-Shift Handover
Number of TCH/F handover during assignment due to forced transfer. 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. 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. 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 726.
Usage
Measurement Point
655
C901060044 Number of TCH/F handover attempts during handover due to forced transfer
Definition Description Usage
Number of TCH/F handover attempts during handover due to forced transfer. This counter counts the number of forced handovers during handover (on TCH/F). 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. 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
Measurement Point
656
Number of TCH/F handover attempts due to TA increase. 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. This counter is used to find out frequency of MS handover from second cell to first cell in sub-cell.
Usage
657
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 728.
FIGURE 728 HANDOVER DECISION
Number of TCH/F handover attempts due to TA decrease. 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. This counter is used to find out frequency of MS handover from first cell to second cell in sub-cell. 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 729.
FIGURE 729 HANDOVER DECISION
658
Number of TCH/H handover attempts due to quick break up of UL. 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. 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. 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 730.
FIGURE 730 HANDOVER DECISION
Usage
Measurement Point
Times 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
659
Number of TCH/H handover attempts due to macro-micro switch. 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. 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. 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 731.
FIGURE 731 HANDOVER DECISION
Usage
Measurement Point
Times ZGO-01-01-001 Half Rate ZGO-02-02-001 Handover between Macro- and Micro-cells ZGO-03-02-005 Dynamic Half Rate Allocation
Number of TCH/H handover attempts due to MSC request. 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.
660
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. BSC carries out handover judgment after receiving HO_ENQUIRY message sent by MSC; the counter increments if judgment result is yes. The measurement point is A, as shown in Figure 732.
FIGURE 732 HO_ENQUIRY HANDOVER
Measurement Point
Number of TCH/H handover attempts due to traffic. 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. 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. BSC carries out handover judgment after receiving TCH/H traffic alarm, the counter increments if judgment result is yes. The measurement point is A, as shown in Figure 733.
Usage
Measurement Point
661
Times ZGO-01-01-001 Half Rate ZGO-02-02-007 Traffic Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing ZGO-03-02-005 Dynamic Half Rate Allocation
Number of TCH/H handover attempts due to large TA and wastage. This counter counts the number of handover attempts due to large TA and wastage (on TCH/H). This handover only happens in subcell configuration and TA & PassLoss algorithm is used; when both TA and PassLoss are higher than set threshold, MS is handed over from second cell to first cell. 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. 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 734.
Usage
Measurement Point
662
Number of TCH/H handover attempts due to small TA and wastage. This counter counts the number of handover attempts due to small TA and wastage (on TCH/H). This handover only happens in subcell configuration and TA & PassLoss algorithm is used; when both TA and PassLoss are lower than set threshold, MS is handed over from first cell to second cell. 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. 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 735.
FIGURE 735 HANDOVER DECISION
Usage
Measurement Point
663
C901060064 Number of TCH/H handover attempts due to a preferable electricity level in 3G adjacent cell
Definition Description Usage
Number of TCH/H handover attempts due to a preferable electricity level in 3G adjacent cell. This counter counts the number of handover attempts due to a good standard level in 3G adjacent cell (on TCH/H). 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. 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 736.
FIGURE 736 HANDOVER DECISION
Measurement Point
Times 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
664
Number of TCH/H handover attempts due to forced transfer. 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. 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. BSC carries out handover judgment after receiving TCH/H measurement report; the counter increments if judgment result is yes and handover cause is forced transfer handover attempts (on TCH/H). The measurement point is A, as shown in Figure 737.
FIGURE 737 HANDOVER DECISION
Usage
Measurement Point
Times ZGO-01-01-001 Half Rate ZGO-02-02-003 Directed-Shift Handover ZGO-03-02-005 Dynamic Half Rate Allocation
C901060066 Number of TCH/H handover attempts during assignment due to forced transfer
Definition
665
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. 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. 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 738.
FIGURE 738 FORCED HANDOVER JUDGMENT
Usage
Measurement Point
666
C901060067 Number of TCH/H handover attempts during handover due to forced transfer
Definition Description Usage
Number of TCH/H handover attempts during handover due to forced transfer. This counter counts the number of forced handovers during handover (on TCH/H). 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. 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 739.
FIGURE 739 FORCED HANDOVER JUDGMENT
Measurement Point
667
Number of TCH/H handover attempts during handover due to TA increase. 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. This counter is used to find out frequency of MS handover from second cell to first cell in sub-cell. 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 740.
FIGURE 740 HANDOVER DECISION
668
Number of TCH/H handover attempts during handover due to TA decrease. 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. This counter is used to find out frequency of MS handover from first cell to second cell in sub-cell. 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 741.
FIGURE 741 HANDOVER DECISION
669
This counter counts the number of handover attempts due to other reasons except for those reasons mentioned above. This counter is used to find out handover frequency due to other reasons. 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 742.
FIGURE 742 HANDOVER DECISION
Unit
Times
Number of TCH/F handover attempts due to CS channel transfer 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. This counter is used to find out handover frequency due to CS channel transfer on TCH/F. 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 743.
670
Number of TCH/H handover attempts due to CS channel transfer 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. This counter is used to find out handover frequency due to CS channel handover on TCH/H by BSC. 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 744.
671
Number of TCH/H handover attempts due to Fragment reorganization 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. This counter is used to find out handover frequency due to combining two half-rate channel on TCH/H by BSC. New call service instance does not apply for full-rate channel, or due to other call service released, fragment reorganization is issued to do intra-cell handover. It will combine two half-rate service into one timeslot. The couner increments while one full-rate channel is idle. The measurement point is A, as shown in Figure 745.
672
Number of TCH/F handover attempts due to energy conservation 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. This counter is used to find out handover frequency due to energy conservation on TCH/F by BSC. 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 746.
673
Number of TCH/F handover attempts due to energy conservation 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. This counter is used to find out handover frequency due to energy conservation on TCH/H by BSC. 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 747.
674
Number of TCH/F handover attempts due to CS channel is forced release 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. This counter is used to find out handover frequency due to CS service seizured by PS on TCH/F. 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 748.
675
Number of TCH/H handover attempts due to CS channel is forced release 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. This counter is used to find out handover frequency due to CS service seizured by PS on TCH/H. 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 749.
676
Number of TCH/F handover attempts due to FR to HR during cell busy This counter counts the number of handover attempts due to FR transferred to HR on busy, it can connect more services. This counter is used to find out handover frequency due to FR transferred to HR on busy. N/A Times
677
This counter counts the number of handover attempts due to too high downlink level on SDCCH. This counter measures the frequency of handover due to the downlink level on SDCCH. The higher value indicates the higher downlink level on SDCCH. 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. Times
This counter counts the number of handover attempts due to too high downlink level on TCH/F. 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. 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. Times
This counter counts the number of handover attempts due to too high downlink level on TCH/H. 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.
678
This counter increments if the handover decision is done after receiving the measurement report on TCH/H by BSC and the handover is caused by the rapid downlink drop. Times
After the dynamic power sharing function is enabled, iBSC performs real-time monitoring for the power usage of each RRU's timeslots. When a channel is allocated, the power it uses is registered; when the channel is released, the power it uses is also released. When the base station reports downlink dynamic power control result, the power the channel uses is refreshed. When iBSC detects the power a RRU's timeslot currently uses reaches the threshold of power congestion control, it selects a CS service and performs outgoing handover for it towards other timeslot of the cell or towards other cell. If the service is occupying TCH/F, the counter increments. This counter is supported in version V6.20.61 or later.
This counter is used to find out the frequency of FR service handover due to RRU power congestion. 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.
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
679
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. 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.
Measurement Point
The counter counts when the local switch initiates FR service handover. This counter is supported in version V6.20.614a. Times Cell
The counter counts when the local switch initiates HR service handover. This counter is supported in version V6.20.614a. Times
Unit
680
Statistics Object
Cell
After the service module receives the FR-to-HR handover request message from the RANUMC module, this counter counts the number of attempts of FR-to-HR handover. As shown in Figure 750, after the EV_FR_Ho_HR message is received, the system judges whether the handover condition is satisfied. If handover is allowed, the counter counts.
FIGURE 750 HANDOVER ATTEMPT IPABIS
DUE TO
OF
Times Cell
After the service module receives the traffic-migration handover request message from the DBS module, this counter counts the number of attempts of FR handover. As shown in Figure 751, after the EV_DBS_CS_MOV message is received, the system judges whether the handover condition is satisfied. If handover is allowed, the counter counts.
681
TRAFFIC-MIGRATION HANDOVER
DUE TO
MASTERPWR_ALM
Times Cell
After the service module receives the traffic-migration handover request message from the DBS module, this counter counts the number of attempts of HR handover. As shown in Figure 752, after the EV_DBS_CS_MOV message is received, the system judges whether the handover condition is satisfied. If handover is allowed, the counter counts.
FIGURE 752 FROM TRX TRAFFIC-MIGRATION HANDOVER
DUE TO
MASTERPWR_ALM
Times
682
Statistics Object
Cell
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 753.
FIGURE 753 NUMBER OF ASSIGNMENT EXECUTIONS DUE TO DIRECTED RETRY
Times
683
Statistics Object
Cell
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 754.
FIGURE 754 HANDOVER DECISION
Times Cell
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.
684
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 755.
FIGURE 755 HANDOVER DECISION
Times Cell
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 756.
FIGURE 756 HANDOVER DECISION
Times Cell
685
686
Chapter
13
687
C901070026 Number of data TCH/F drops due to forced release by other calls .......................................................... 713 C901070028 Number of data TCH/F drops due to other failure ................................................................................ 714 C901070029 Number of signaling TCH/H drops due to loss of contact with RANA ........................................................... 715 C901070030 Number of signaling TCH/H drops due to radio link failure ...................................................................... 716 C901070031 Number of signaling TCH/H drops due to LAPD link failure ...................................................................... 717 C901070032 Number of signaling TCH/H drops due to OMC-R forced release ................................................................. 717 C901070033 Number of signaling TCH/H drops due to forced release by other calls ....................................................... 718 C901070035 Number of signaling TCH/H drops due to other failure ............................................................................ 719 C901070036 Number of voice TCH/H drops due to loss of contact with RANA................................................................ 720 C901070038 Number of voice TCH/H drops due to LAPD link failure ............................................................................ 721 C901070039 Number of voice TCH/H drops due to OMC-R forced release ................................................................. 723 C901070040 Number of voice TCH/H drops due to forced release by other calls .......................................................... 724 C901070042 Number of voice TCH/H drops due to other failure ................................................................................ 725 C901070043 Number of data TCH/H drops due to loss of contact with RANA................................................................ 726 C901070044 Number of data TCH/H drops due to radio link failure ............................................................................ 728 C901070045 Number of data TCH/H drops due to LAPD link failure ............................................................................ 729 C901070046 Number of data TCH/H drops due to OMC-R forced release ................................................................. 730 C901070047 Number of data TCH/H drops due to forced release by other calls .......................................................... 732 C901070049 Number of data TCH/H drops due to other failure ................................................................................ 733 C901070053 Number of SDCCH link failures........................ 734 C901070054 Number of TCH/F link failures ......................... 735 C901070055 Number of TCH/H link failures ........................ 737 C901070056 Number of RANA link releases due to other cause on SDCCH ...................................................................... 738 C901070057 Number of RANA link releases due to other cause on TCH/F........................................................................ 739 C901070058 Number of RANA link releases due to other cause on TCH/H ....................................................................... 739 C901070059 Number of SDCCH short messages drops ......... 740 C901070060 Number of TCH/F short messages drops........... 741 C901070061 Number of TCH/H short messages drops .......... 741 C901070062 Number of TCH/F drops due to CS channel is forced release by PS ........................................................ 742 C901070063 Number of TCH/H drops due to CS channel is forced release by PS ........................................................ 742 C901070064 Number of SDCCH drops due to eMLPP forced handover........................................................................ 743 C901070065 Number of signaling TCH/F drops due to eMLPP forced handover .............................................................. 743 C901070066 Number of voice TCH/F drops due to eMLPP forced handover .............................................................. 744
688
C901070067 Number of data TCH/F drops due to eMLPP forced handover .............................................................. 745 C901070068 Number of sigaling TCH/H drops due to eMLPP forced handover .............................................................. 746 C901070069 Number of voice TCH/H drops due to eMLPP forced handover .............................................................. 746 C901070070 Number of data TCH/H drops due to eMLPP forced handover .............................................................. 747 C901070071 Bad quality of UL receiving (On SDCCH)........... 748 C901070072 Bad quality of DL receiving (On SDCCH)........... 749 C901070073 Lower electrical level of UL (On SDCCH)........... 750 C901070074 Lower electrical level of DL (On SDCCH)........... 751 C901070075 Number of signaling drops due to TA too far (On SDCCH) ......................................................................... 752 C901070076 Reasons of the other radios (On SDCCH).......... 753 C901070077 Bad quality of UL receiving (On TCH/F) ............ 754 C901070078 Bad quality of DL receiving (On TCH/F) ............ 755 C901070079 Lower electrical level of UL (On TCH/F) ............ 756 C901070080 Lower electrical level of DL (On TCH/F) ............ 757 C901070081 Number of signaling drops due to TA too far (On TCH/F) ........................................................................... 758 C901070082 Reasons of the other radios (On TCH/F) ........... 759 C901070083 Bad quality of UL receiving (On TCH/H)............ 761 C901070084 Bad quality of DL receiving (On TCH/H) ........... 762 C901070085 Lower electrical level of UL (On TCH/H)............ 763 C901070086 Lower electrical level of DL (On TCH/H)............ 764 C901070087 Number of signaling drops due to TA too far (On TCH/H) .......................................................................... 765 C901070088 Reasons of the other radios (On TCH/H)........... 766 C901070089 The Count of Drop Call caused by "IP Resource Reset"............................................................................ 767 C901070090 Number of FR_V1 radio link fail....................... 768 C901070091 Number of FR_V2 radio link fail....................... 768 C901070092 Number of FR_V3 radio link fail....................... 768 C901070093 Number of HR_V1 radio link fail ...................... 769 C901070094 Number of HR_V3 radio link fail ...................... 769 C901070095 Number of signaling TCH/F drops due to BIPB Active/Standby Changeover .............................................. 770 C901070096 Number of voice TCH/F drops due to BIPB Active/Standby Changeover ................................................. 770 C901070097 Number of data TCH/F drops due to BIPB Active/Standby Changeover ................................................. 770 C901070098 Number of signaling TCH/H drops due to BIPB Active/Standby Changeover .............................................. 771 C901070099 Number of voice TCH/H drops due to BIPB Active/Standby Changeover ................................................. 771 C901070100 Number of data TCH/H drops due to BIPB Active/Standby Changeover ................................................. 771 C901070101 Number of SDCCH drops due to LAPD Active/Standby Changeover ................................................. 772 C901070102 Number of voice TCH/F drops due to LAPD Active/Standby Changeover ................................................. 772 C901070103 Number of data TCH/F drops due to LAPD Active/Standby Changeover ................................................. 772 C901070104 Number of signaling TCH/F drops due to LAPD Active/Standby Changeover .............................................. 773 C901070105 Number of voice TCH/H drops due to LAPD Active/Standby Changeover ................................................. 773 C901070106 Number of data TCH/H drops due to LAPD Active/Standby Changeover ................................................. 774
689
C901070107 Number of signaling TCH/H drops due to LAPD Active/Standby Changeover .............................................. 774 C901070108 Number of voice TCH/F drops due to handover fail for power adjustment.................................................. 774 C901070109 Number of voice TCH/H drops due to handover fail for power adjustment.................................................. 775 C901070110 Number of SDCCH drops due to BIPB Active/Standby Changeover ................................................. 775 C901070111 Number of SDCCH drops due to BTS failure ................................................................................ 776 C901070112 Number of signaling TCH/F drops due to BTS failure ............................................................................ 777 C901070113 Number of voice TCH/F drops due to BTS failure ................................................................................ 778 C901070114 Number of data TCH/F drops due to BTS failure ................................................................................ 779 C901070115 Number of signaling TCH/H drops due to BTS failure ............................................................................ 780 C901070116 Number of voice TCH/H drops due to BTS failure ................................................................................ 781 C901070117 Number of data TCH/H drops due to BTS failure ................................................................................ 782 C901070118 Call Drop by Releasing Local Switch................. 783
Overview
Channels that take part in the measurement statistic include SDCCH, TCH/F and TCH/H. Service types include signaling, voice and data. Counted call drop causes include RMM losses contact with SMM, BTS radio link failure, LAPD link failure, OMCR forced release, forced release by other calls, handover failure, as well as other failure. The measurement takes cell as the statistics unit.
Number of SDCCH drops due to loss of contact with RANA 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. This counter is used to find out the frequency of failures due to loss of contact with SMM. The counter counts the number of failures due to loss of contact with SMM in the following two cases:
690
After link between RANCS and RANA has been established on SDCCH, heartbeat handshake is carried out. If RANCS or RANA can not receive heartbeat message from each other during 4 unit time, then it is regarded as link failure and the counter increments; meanwhile, BSC release the channel and instance, the measurement point is A1, as shown in Figure 757.
FIGURE 757 CALL DROP DUE TO A-INTERFACE FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
RANCS forwards EST_IND message to RANA after receiving it on SDCCH; if no link establishment message on A-interface from RANA is received, the counter increments; meanwhile, BSC release the channel and instance, the measurement point is A2, as shown in Figure 757.
Unit
Times
Number of SDCCH drops due to radio link failure 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. This counter is used to find out the frequency of call drop due to radio link failures (On SDCCH).
DicatiOn
The counter increments when BSC receives CONNectiOn FAILure INmessage on Abis interface on SDCCH. The measurement point is A, as shown in Figure 758.
691
FIGURE 758 CALL DROP DUE TO RADIO LINK FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
Number of SDCCH drops due to LAPD link failure 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. This counter is used to find out the frequency of call drop due to LAPD link failures (On SDCCH). The counter increments when BSC receives DLREL_IND message from LAPD on SDCCH. The measurement point is A, as shown in Figure 759.
692
FIGURE 759 CALL DROP DUE TO LAPD LINK FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
Unit
Times
Number of SDCCH drops due to OMC-R forced release 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. This counter is used to find out the frequency of call drop due to OMC-R forced releases (on SDCCH). The counter increments when BSC receives OMC-R forced release message from database on SDCCH. The measurement point is A, as shown in Figure 760.
693
FIGURE 760 CALL DROP DUE TO OMC-R FORCED RELEASE IN IMMEDIATE ASSIGNMENT PROCESS
Unit
Times
Number of SDCCH drops due to forced release by other calls 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. This counter is used to find out the frequency of call drop due to forced releases by other calls (On SDCCH). The counter increments when BSC receives forced release message from other calls on SDCCH. The measurement point is A, as shown inFigure 761.
694
FIGURE 761 CALL DROP DUE TO FORCED RELEASE BY OTHER CALLS IN IMMEDIATE ASSIGNMENT PROCESS
Unit
Times
Number of SDCCH drops due to other failure This counter counts the number of call drop due to other failures (On SDCCH). The counter increments if the phenomenon that call drops after MS has obtained SDCCH is caused by other failures except the causes mentioned above (loss of contact with RANA, radio link failure, LAPD link failure, OMCR forced release, forced release by other calls, handover failure). At present, other failure causes are that T3107 is overtime under ASSIGN status, timer that waits for access is overtime and forced release caused by other faults, which include resource fault, BTS turnover, and AIPB fault.
This counter is used to find out the frequency of call drop due to other failures (On SDCCH). The counter increments when T3107 is overtime under ASSIGN status on SDCCH, or when timer that waits for access is overtime or forced release caused by other faults. The measurement point is A, as shown in Figure 762.
695
OF
TWAITMSACCESS OVERTIME
Unit
Times
C901070008 Number of signaling TCH/F drops due to loss of contact with RANA
Definition Description
Number of signaling TCH/F drops due to loss of contact with RANA 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. This counter is used to find out the frequency of failures due to RANCS losing contact with RANA (on TCH/F signaling channel). The counter counts the number of failures due to loss of contact with RANA (On TCH/F signaling) in the following two cases: 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 763. 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; mean-
696
while, BSC releases the channel and instance, the measurement point is A2, as shown inFigure 763.
FIGURE 763 CALL DROP DUE TO A-INTERFACE FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
Number of signaling TCH/F drops due to radio link failure 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. This counter is used to find out the frequency of call drop due to radio link failures (On TCH/F signaling).
DicatiOn
The counter increments when BSC receives CONNectiOn FAILure INmessage on Abis interface on TCH/F signaling channel. The measurement point is A, as shown inFigure 764.
697
FIGURE 764 CALL DROP DUE TO RADIO LINK FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
Times 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
Number of signaling TCH/F drops due to LAPD link failure 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. This counter is used to find out the frequency of call drop due to LAPD link failures (on TCH/F signaling channel). 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 765.
698
FIGURE 765 CALL DROP DUE TO LAPD LINK FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
Number of signaling TCH/F drops due to OMC-R forced release 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. This counter is used to find out the frequency of call drop due to OMC-R forced releases (on TCH/F signaling channel). 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 766.
699
FIGURE 766 CALL DROP DUE TO OMC-R FORCED RELEASE IN IMMEDIATE ASSIGNMENT PROCESS
C901070012 Number of signaling TCH/F drops due to forced release by other calls
Definition Description
Number of signaling TCH/F drops due to forced release by other calls 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. This counter is used to find out the frequency of call drop due to forced releases by other calls (on TCH/F signaling channel). The counter increments when BSC receives forced release message from other calls on TCH/F signaling channel. The measurement point is A, as shown in Figure 767.
700
FIGURE 767 CALL DROP DUE TO FORCED RELEASE BY OTHER CALLS IN IMMEDIATE ASSIGNMENT PROCESS
Number of signaling TCH/F drops due to other failure This counter counts the number of call drop due to other 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 other failures except the causes mentioned above (loss of contact with RANA, radio link failure, LAPD link failure, OMCR forced release, forced release by other calls, handover failure). At present, other failure causes are that T3107 is overtime under ASSIGN status, timer that waits for access is overtime and forced release caused by other faults, which include resource fault, BTS turnover, and AIPB fault.
This counter is used to find out the frequency of call drop due to other failures (on TCH/F signaling channel). The counter increments when T3107 is overtime under ASSIGN status on TCH/F, or when timer that waits for access is overtime or forced release caused by other faults. The measurement point is A, as shown in Figure 768.
701
OF
TWAITMSACCESS OVERTIME
C901070015 Number of voice TCH/F drops due to loss of contact with RANA
Definition Description
Number of voice TCH/F drops due to loss of contact with RANA 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). This counter is used to find out the frequency of failures due to RANCS losing contact with RANA (on TCH/F voice channel). The counter counts the number of failures due to loss of contact with RANA (on TCH/F voice channel) in the following two cases: 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. 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;
702
meanwhile, BSC releases the channel and instance, the measurement point is A, as shown in Figure 769.
FIGURE 769 CALL DROP DUE TO A-INTERFACE FAILURE IN ASSIGNMENT PROCESS
Number of voice TCH/F drops due to LAPD link failure 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. This counter is used to find out the frequency of call drop due to LAPD link failures (on TCH/F voice channel).
Usage
703
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 770.
FIGURE 770 CALL DROP DUE TO LAPD LINK FAILURE IN ASSIGNMENT PROCESS
Number of voice TCH/F drops due to OMC-R forced release This counter counts the number of call drop due to OMC-R forced releases (on TCH/F voice channel). The counter increments if the
704
phenomenon that call drops after MS has obtained TCH/F voice channel is caused by OMC-R forced releases.
Usage Measurement Point
This counter is used to find out the frequency of call drop due to OMC-R forced releases (on TCH/F voice channel). 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 771.
FIGURE 771 CALL DROP DUE TO OMC-R FORCED RELEASE IN ASSIGNMENT PROCESS
705
C901070019 Number of voice TCH/F drops due to forced release by other calls
Definition Description
Number of voice TCH/F drops due to forced release by other calls 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. This counter is used to find out the frequency of call drop due to forced releases by other calls (on TCH/F voice channel). 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 772.
FIGURE 772 CALL DROP DUE TO FORCED RELEASE BY OTHER CALLS IN ASSIGNMENT PROCESS
Unit
Times
706
Related Features
Number of voice TCH/F drops due to other failure This counter counts the number of call drop due to other failures (on TCH/F voice channel). It indicates the call drop case at call establishment phase due to assignment failure. The counter increments if the phenomenon that call drops after MS has obtained TCH/F voice channel is caused by other failures except the causes mentioned above (loss of contact with RANA, radio link failure, LAPD link failure, OMCR forced release, forced release by other calls, handover failure). At present, other failure causes are that T3107 is overtime under ASSIGN status, timer that waits for access is overtime and forced release caused by other faults, which include resource fault, BTS turnover, and AIPB fault. This counter does not count the call drops due to intra-cell handover failure.
This counter is used to find out the frequency of call drop due to other failures (on TCH/F voice channel). The counter increments when T3107 is overtime under ASSIGN status on TCH/F, or when timer that waits for access is overtime or forced release caused by other faults. The measurement point is A, as shown in Figure 773.
FIGURE 773 MEASUREMENT POINT
OF
TWAITMSACCESS OVERTIME
707
C901070022 Number of data TCH/F drops due to loss of contact with RANA
Definition Description
Number of data TCH/F drops due to loss of contact with RANA 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). This counter is used to find out the frequency of failures due to RANCS losing contact with RANA (on TCH/F data channel). The counter counts the number of failures due to loss of contact with RANA (on TCH/F data channel) in the following two cases: 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 774. 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.
708
Number of data TCH/F drops due to radio link failure 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. This counter is used to find out the frequency of call drop due to radio link failures (on TCH/F data channel). The counter increments when BSC receives CONNectiOn FAILure INmessage on Abis interface on TCH/F data channel. The measurement point is A, as shown in Figure 775.
DicatiOn
709
FIGURE 775 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT PROCESS
Times 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
Number of data TCH/F drops due to LAPD link failure This counter counts the number of call drop due to LAPD link failures (on TCH/F data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F data channel is caused by LAPD link failures.
710
This counter is used to find out the frequency of call drop due to LAPD link failures (on TCH/F data channel). 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 776.
FIGURE 776 CALL DROP DUE TO LAPD LINK FAILURE IN ASSIGNMENT PROCESS
711
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. This counter is used to find out the frequency of call drop due to OMC-R forced releases (on TCH/F data channel). 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 777.
FIGURE 777 CALL DROP DUE TO OMC-R FORCED RELEASE IN ASSIGNMENT PROCESS
712
C901070026 Number of data TCH/F drops due to forced release by other calls
Definition Description
Number of data TCH/F drops due to forced release by other calls 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. This counter is used to find out the frequency of call drop due to forced releases by other calls (on TCH/F data channel). 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 778.
FIGURE 778 CALL DROP DUE TO FORCED RELEASE BY OTHER CALLS IN ASSIGNMENT PROCESS
Unit
Times
713
Related Features
Number of data TCH/F drops due to other failure This counter counts the number of call drop due to other failures (on TCH/F data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/F data channel is caused by other failures except the causes mentioned above (loss of contact with RANA, radio link failure, LAPD link failure, OMCR forced release, forced release by other calls, handover failure). At present, other failure causes are that T3107 is overtime under ASSIGN status, timer that waits for access is overtime and forced release caused by other faults, which include resource fault, BTS turnover, and AIPB fault.
This counter is used to find out the frequency of call drop due to other failures (on TCH/F data channel). The counter increments when T3107 is overtime under ASSIGN status on TCH/F, or when timer that waits for access is overtime or forced release caused by other faults. The measurement point is A, as shown in Figure 779.
FIGURE 779 MEASUREMENT POINT
OF
TWAITMSACCESS OVERTIME
714
C901070029 Number of signaling TCH/H drops due to loss of contact with RANA
Definition Description
Number of signaling TCH/H drops due to loss of contact with RANA 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). This counter is used to find out the frequency of failures due to RANCS losing contact with RANA (on TCH/H signaling channel). The counter counts the number of failures due to loss of contact with RANA (on TCH/H signaling channel) in the following two cases: 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 780. 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 780.
FIGURE 780 CALL DROP DUE TO A-INTERFACE FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
715
Number of signaling TCH/H drops due to radio link failure 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. This counter is used to find out the frequency of call drop due to radio link failures (on TCH/H signaling channel). The counter increments when BSC receives CONNectiOn FAILure INmessage on Abis interface on TCH/H signaling channel. The measurement point is A, as shown in Figure 781.
DicatiOn
FIGURE 781 CALL DROP DUE TO RADIO LINK FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
Times 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
716
Number of signaling TCH/H drops due to LAPD link failure 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. This counter is used to find out the frequency of call drop due to LAPD link failures (on TCH/H signaling channel). 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 782.
FIGURE 782 CALL DROP DUE TO LAPD LINK FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
717
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. This counter is used to find out the frequency of call drop due to OMC-R forced releases (on TCH/H signaling channel). 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 783.
FIGURE 783 CALL DROP DUE TO OMC-R FORCED RELEASE IN IMMEDIATE ASSIGNMENT PROCESS
C901070033 Number of signaling TCH/H drops due to forced release by other calls
Definition Description
Number of signaling TCH/H drops due to forced release by other calls 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. This counter is used to find out the frequency of call drop due to forced releases by other calls (on TCH/H signaling channel).
Usage
718
Measurement Point
The counter increments when BSC receives forced release message from other calls on TCH/H signaling channel. The measurement point is A, as shown in Figure 784.
FIGURE 784 CALL DROP DUE TO FORCED RELEASE BY OTHER CALLS IN IMMEDIATE ASSIGNMENT PROCESS
Number of signaling TCH/H drops due to other failure This counter counts the number of call drop due to other 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 other failures except the causes mentioned above (loss of contact with RANA, radio link failure, LAPD link failure, OMCR forced release, forced release by other calls, handover failure). At present, other failure causes are that T3107 is overtime under ASSIGN status, timer that waits for access is overtime and forced release caused by other faults, which include resource fault, BTS turnover, and AIPB fault.
This counter is used to find out the frequency of call drop due to other failures (on TCH/H signaling channel). The counter increments when T3107 is overtime under ASSIGN status on TCH/H, or when timer that waits for access is overtime or forced release caused by other faults. The measurement point is A, as shown in Figure 785.
719
OF
TWAITMSACCESS OVERTIME
C901070036 Number of voice TCH/H drops due to loss of contact with RANA
Definition Description
Number of voice TCH/H drops due to loss of contact with RANA 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). This counter is used to find out the frequency of failures due to RANCS losing contact with RANA (on TCH/H voice channel). The counter counts the number of failures due to loss of contact with RANA (on TCH/H voice channel) in the following two cases: 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.
720
RANCS forwards EST_INDmessage to RANA after receiving it on TCH/H voice channel; if no link establishment message on A-interface from RANA is received, the counter increments; meanwhile, BSC releases the channel and instance, the measurement point is A, as shown in Figure 786.
FIGURE 786 CALL DROP DUE TO A-INTERFACE FAILURE IN ASSIGNMENT PROCESS
Number of voice TCH/H drops due to LAPD link failure This counter counts the number of call drop due to LAPD link failures (on TCH/H voice channel). The counter increments if the
721
phenomenon that call drops after MS has obtained TCH/H voice channel is caused by LAPD link failures.
Usage Measurement Point
This counter is used to find out the frequency of call drop due to LAPD link failures (on TCH/H voice channel). 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 787.
FIGURE 787 CALL DROP DUE TO LAPD LINK FAILURE IN ASSIGNMENT PROCESS
722
Number of voice TCH/H drops due to OMC-R forced release 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. This counter is used to find out the frequency of call drop due to OMC-R forced releases (on TCH/H voice channel). 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 788.
FIGURE 788 CALL DROP DUE TO OMC-R FORCED RELEASE IN ASSIGNMENT PROCESS
Unit
Times
723
Related Features
C901070040 Number of voice TCH/H drops due to forced release by other calls
Definition Description
Number of voice TCH/H drops due to forced release by other calls 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. This counter is used to find out the frequency of call drop due to forced releases by other calls (on TCH/H voice channel). 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 789.
724
FIGURE 789 CALL DROP DUE TO FORCED RELEASE BY OTHER CALLS IN ASSIGNMENT PROCESS
Number of voice TCH/H drops due to other failure This counter counts the number of call drop due to other failures (on TCH/H voice channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H voice channel is caused by other failures except the causes mentioned above (loss
725
of contact with RANA, radio link failure, LAPD link failure, OMCR forced release, forced release by other calls, handover failure). At present, other failure causes are that T3107 is overtime under ASSIGN status, timer that waits for access is overtime and forced release caused by other faults, which include resource fault, BTS turnover, and AIPB fault.
Usage Measurement Point
This counter is used to find out the frequency of call drop due to other failures (on TCH/H voice channel). The counter increments when T3107 is overtime under ASSIGN status on TCH/H, or when timer that waits for access is overtime or forced release caused by other faults. The measurement point is A, as shown in Figure 790.
FIGURE 790 MEASUREMENT POINT
OF
TWAITMSACCESS OVERTIME
C901070043 Number of data TCH/H drops due to loss of contact with RANA
Definition Description
Number of data TCH/H drops due to loss of contact with RANA 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
726
TCH/H data channel is caused by failures due to RANCS losing contact with RANA (on TCH/H data channel).
Usage Measurement Point
This counter is used to find out the frequency of failures due to RANCS losing contact with RANA (on TCH/H data channel). The counter counts the number of failures due to loss of contact with RANA (on TCH/H data channel) in the following two cases: 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 791.
FIGURE 791 CALL DROP DUE TO A-INTERFACE FAILURE IN ASSIGNMENT PROCESS
727
Number of data TCH/H drops due to radio link failure 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. This counter is used to find out the frequency of call drop due to radio link failures (on TCH/H data channel). The counter increments when BSC receives CONNectiOn FAILure INmessage on Abis interface on TCH/H data channel. The measurement point is A, as shown in Figure 792.
DicatiOn
FIGURE 792 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT PROCESS
Unit
Times
728
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
Number of data TCH/H drops due to LAPD link failure 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. This counter is used to find out the frequency of call drop due to LAPD link failures (on TCH/H data channel). 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 793.
729
FIGURE 793 CALL DROP DUE TO LAPD LINK FAILURE IN ASSIGNMENT PROCESS
Number of data TCH/H drops due to OMC-R forced release 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.
730
This counter is used to find out the frequency of call drop due to OMC-R forced releases (on TCH/H data channel). The counter increments when BSC receives OMCR forced release message from database on TCH/H data channel. The measurement point is A, as shown in Figure 794.
FIGURE 794 CALL DROP DUE TO OMC-R FORCED RELEASE IN ASSIGNMENT PROCESS
731
C901070047 Number of data TCH/H drops due to forced release by other calls
Definition Description
Number of data TCH/H drops due to forced release by other calls 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. This counter is used to find out the frequency of call drop due to forced releases by other calls (on TCH/H data channel). 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 795.
FIGURE 795 CALL DROP DUE TO FORCED RELEASE BY OTHER CALLS IN ASSIGNMENT PROCESS
Unit
Times
732
Related Features
Number of data TCH/H drops due to other failure This counter counts the number of call drop due to other failures (on TCH/H data channel). The counter increments if the phenomenon that call drops after MS has obtained TCH/H data channel is caused by other failures except the causes mentioned above (loss of contact with RANA, radio link failure, LAPD link failure, OMCR forced release, forced release by other calls, handover failure). At present, other failure causes are that T3107 is overtime under ASSIGN status, timer that waits for access is overtime and forced release caused by other faults, which include resource fault, BTS turnover, and AIPB fault.
This counter is used to find out the frequency of call drop due to other failures (on TCH/H data channel). The counter increments when T3107 is overtime under ASSIGN status on TCH/H, or when timer that waits for access is overtime or forced release caused by other faults. The measurement point is A, as shown in Figure 796.
FIGURE 796 MEASUREMENT POINT
OF
TWAITMSACCESS OVERTIME
Unit
Times
733
Related Features
Number of SDCCH link failures 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. This counter is used to find out the frequency of SDCCH link failures. The counter counts the number of abnormal release flow launched by RANA to RANCS due to SCCP link failure on SDCCH, including the following cases: T9105 is overtime, the measurement point is A2, as shown in Figure 797.
FIGURE 797 CALL DROP DUE TO SCCP FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
734
T9104 is overtime and the number of maximum failure times is reached, the measurement point is A3, as shown in Figure 797. T9101 is overtime, the measurement point is A4, as shown in Figure 797. After RANA process has been established, EST_IND message sent by MS or handover request sent by MSC is not received within the set time, the measurement point is A1, as shown in Figure 797. BSC receives MSC reset message. CONNECT_ID requested by RANA is failed. BSC receives link release command from MSC.
Unit
Times
Number of TCH/F link failures 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. This counter is used to find out the frequency of TCH/F link failures. 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: T9105 is overtime, the measurement point is A2, as shown in Figure 798.
735
FIGURE 798 CALL DROP DUE TO SCCP FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
T9104 is overtime and the number of maximum failure times is reached, the measurement point is A3, as shown in Figure 798. T9101 is overtime, the measurement point is A4, as shown inFigure 798. 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 798. BSC receives MSC reset message. CONNECT_ID requested by RANA is failed. BSC receives link release command from MSC.
Unit Related Features
736
Number of TCH/H link failures 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. This counter is used to find out the frequency of TCH/H link failures. 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: T9105 is overtime, the measurement point is A2, as shown in Figure 799.
FIGURE 799 CALL DROP DUE TO SCCP FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
T9104 is overtime and the number of maximum failure times is reached, the measurement point is A3, as shown in Figure 799. T9101 is overtime, the measurement point is A4, as shown in Figure 799.
737
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 799. BSC receives MSC reset message. CONNECT_ID requested by RANA is failed. BSC receives link release command from MSC.
Unit Related Features
Number of RANA link releases due to other cause on SDCCH 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. This counter is used to find out the frequency of RANA link releases by other cause on SDCCH. The counter increments when the content of HO_REQ message is incorrect. The measurement point is A2, as shown in Figure 800.
FIGURE 800 CALL DROP DUE TO INTER-BSC HANDOVER FAILURE
Unit
Times
738
Number of RANA link releases due to other cause on TCH/F 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. This counter is used to find out the frequency of RANA link releases by other cause on TCH/F. The counter increments when the content of HO_REQ message is incorrect. The measurement point is A2, as shown in Figure 801.
FIGURE 801 CALL DROP DUE TO INTER-BSC HANDOVER FAILURE
Number of RANA link releases due to other cause on TCH/H 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. This counter is used to find out the frequency of RANA link releases by other cause on TCH/H.
Usage
739
Measurement Point
The counter increments when the content of HO_REQ message is incorrect. The measurement point is A2, as shown in Figure 802.
FIGURE 802 CALL DROP DUE TO INTER-BSC HANDOVER FAILURE
Number of SDCCH short messages drops 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. This counter is used to find out the frequency of SDCCH short messages drops. The counter increments when call drops due to radio link failure or LAPD link release or handover failure while doing short message service. Times
740
Number of TCH/F short messages drops 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. This counter is used to find out the frequency of TCH/F short messages drops. The counter increments when call drops due to radio link failure or LAPD link release or handover failure while doing short message service. Times ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-005 Dynamic Half Rate Allocation
Number of TCH/H short messages drops 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. This counter is used to find out the frequency of TCH/H short messages drops. The counter increments when call drops due to radio link failure or LAPD link release or handover failure while doing short message service. Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
741
Number of TCH/F drops due to CS channel is forced release by PS 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. 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. The counter increments when call drops due to TCH/F channel request failure when CS service is forcedly released due to PS service. Times ZGO-03-02-004 HR Concentration
Usage
Number of TCH/H drops due to CS channel is forced release by PS 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. 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. The counter increments when call drops due to TCH/H channel request failure when CS service is forcedly released due to PS service. Times ZGO-03-02-004 HR Concentration
Usage
742
Number of SDCCH drops due to eMLPP forced handover 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. This counter is used to find out the frequency of call drop on SDCCH due to eMLPP forced handover. The counter counts when T3107 and T3103 are timeout under ASSIGN status on SDCCH. The measurement point is A, as shown in Figure 803.
FIGURE EMLPP 803 MEASUREMENT POINT OF NUMBER OF SDCCH DROPS DUE TO FORCED HANDOVER
Unit
Times
Number of signaling TCH/F drops due to eMLPP forced handover 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. This counter is used to find out the frequency of call drop on signaling TCH/F due to eMLPP forced handover
Usage
743
Measurement Point
The counter counts when T3107 and T3103 are timeout under ASSIGN status on signaling TCH/F. The measurement point is A, as shown in Figure 804.
FIGURE EMLPP 804 MEASUREMENT POINT OF NUMBER OF SDCCH DROPS DUE TO FORCED HANDOVER
Unit
Times
Number of voice TCH/F drops due to eMLPP forced handover 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. This counter is used to find out the frequency of call drop on voice TCH/F due to eMLPP forced handover. The counter counts when T3107 and T3103 are timeout under ASSIGN status on voice TCH/F. The measurement point is A, as shown in Figure 805.
744
FIGURE EMLPP
Unit
Times
Number of data TCH/F drops due to eMLPP forced handover 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. This counter is used to find out the frequency of call drop on data TCH/F due to eMLPP forced handover. The counter counts when T3107 and T3103 are timeout under ASSIGN status on data TCH/F. The measurement point is A, as shown in Figure 806.
FIGURE EMLPP 806 MEASUREMENT POINT OF NUMBER OF SDCCH DROPS DUE TO FORCED HANDOVER
745
Unit
Times
Number of signaling TCH/H drops due to eMLPP forced handover 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. This counter is used to find out the frequency of call drop on signaling TCH/H due to eMLPP forced handover. 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 807.
FIGURE EMLPP 807 MEASUREMENT POINT OF NUMBER OF SDCCH DROPS DUE TO FORCED HANDOVER
Unit
Times
Number of voice TCH/H drops due to eMLPP forced handover This counter counts the number of call drops on voice TCH/H due to eMLPP forced handover. After MS obtains voice TCH/H, call drop
746
occurs. If the problem is caused by eMLPP forced handover, the counter increments.
Usage Measurement Point
This counter is used to find out the frequency of call drop on voice TCH/H due to eMLPP forced handover. 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 808.
FIGURE EMLPP 808 MEASUREMENT POINT OF NUMBER OF SDCCH DROPS DUE TO FORCED HANDOVER
Unit
Times
Number of data TCH/H drops due to eMLPP forced handover 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. This counter is used to find out the frequency of call drop on data TCH/H due to eMLPP forced handover. The counter counts when T3107 and T3103 are timeout under ASSIGN status on data TCH/H. The measurement point is A, as shown in Figure 809.
747
FIGURE EMLPP
Unit
Times
Bad quality of UL receiving (On SDCCH) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on SDCCH. The measurement point is A, as shown in Figure 810.
DicatiOn
Usage
Measurement Point
748
FIGURE 810 CALL DROP DUE TO RADIO LINK FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
Unit
Times
Bad quality of DL receiving (On SDCCH) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on SDCCH. The measurement point is A, as shown in Figure 811.
DicatiOn
Usage
Measurement Point
749
FIGURE 811 CALL DROP DUE TO RADIO LINK FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
Unit
Times
Lower electrical level of UL (On SDCCH) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on SDCCH. The measurement point is A, as shown in Figure 812.
DicatiOn
Usage
Measurement Point
750
FIGURE 812 CALL DROP DUE TO RADIO LINK FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
Unit
Times
Lower electrical level of DL (On SDCCH) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on SDCCH. The measurement point is A, as shown in Figure 813.
DicatiOn
Usage
Measurement Point
751
FIGURE 813 CALL DROP DUE TO RADIO LINK FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
Unit
Times
Number of signaling drops due to TA too far (On SDCCH) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on SDCCH. The measurement point is A, as shown in Figure 814.
DicatiOn
752
FIGURE 814 CALL DROP DUE TO RADIO LINK FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
Unit
Times
Reasons of the other radios (On SDCCH) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on SDCCH. The measurement point is A, as shown in Figure 815.
DicatiOn
753
FIGURE 815 CALL DROP DUE TO RADIO LINK FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
Unit
Times
Bad quality of UL receiving (On TCH/F) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INDimessage at Abis interface on TCH/F. The measurement point is A, as shown in Figure 816.
catiOn
Usage
Measurement Point
754
FIGURE 816 CALL DROP DUE TO RADIO LINK FAILURE IN IMMEDIATE ASSIGNMENT PROCESS
Unit
Times
Bad quality of DL receiving (On TCH/F) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INDimessage at Abis interface on TCH/F. The measurement point is A, as shown in Figure 817.
catiOn
Usage
Measurement Point
755
FIGURE 817 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT PROCESS
Unit
Times
Lower electrical level of UL (On TCH/F) 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. 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.
Usage
756
Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on TCH/F. The measurement point is A, as shown in Figure 818.
DicatiOn
FIGURE 818 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT PROCESS
Unit
Times
Lower electrical level of DL (On TCH/F) 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.
757
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. The counter counts when BSC receives the CONNectiOn FAILure INDimessage at Abis interface on TCH/F. The measurement point is A, as shown in Figure 819.
catiOn
Measurement Point
FIGURE 819 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT PROCESS
Unit
Times
758
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. 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. The counter counts when BSC receives the CONNectiOn FAILure INDimessage at Abis interface on TCH/F. The measurement point is A, as shown in Figure 820.
catiOn
FIGURE 820 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT PROCESS
Unit
Times
759
Description
This counter counts the number of call drops on TCH/F due to radio link failure. After MS obtains TCH/F, call drop occurs. If the problem is not due to the above five causes (i.e. bad uplink receiving quality, bad downlink receiving quality, low uplink receiving level, low downlink receiving level, and TA being too far), the counter increments. 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. The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on TCH/F. The measurement point is A, as shown in Figure 821.
DicatiOn
FIGURE 821 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT PROCESS
Unit
Times
760
Bad quality of UL receiving (On TCH/H) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on TCH/H. The measurement point is A, as shown in Figure 822.
DicatiOn
Usage
Measurement Point
FIGURE 822 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT PROCESS
Unit
Times
761
Bad quality of DL receiving (On TCH/H) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on TCH/H. The measurement point is A, as shown in Figure 823.
DicatiOn
Usage
Measurement Point
FIGURE 823 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT PROCESS
Unit
Times
762
Lower electrical level of UL (On TCH/H) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on TCH/H. The measurement point is A, as shown in Figure 824.
DicatiOn
Usage
Measurement Point
FIGURE 824 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT PROCESS
Unit
Times
763
Lower electrical level of DL (On TCH/H) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on TCH/H. The measurement point is A, as shown in Figure 825.
DicatiOn
Usage
Measurement Point
FIGURE 825 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT PROCESS
Unit
Times
764
Number of signaling drops due to TA too far (On TCH/H) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on TCH/H. The measurement point is A, as shown in Figure 826.
DicatiOn
FIGURE 826 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT PROCESS
Unit
Times
765
Reasons of the other radios (On TCH/H) 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INmessage at Abis interface on TCH/H. The measurement point is A, as shown in Figure 827.
DicatiOn
FIGURE 827 CALL DROP DUE TO RADIO LINK FAILURE IN ASSIGNMENT PROCESS
Unit
Times
766
CELL On the premise that the 3GPP IPA function is implemented, during the IP resource resetting process (initiated at MSC or at BSC), BSC releases relevant calls when it receives the IP resource resetting request or the IP resource resetting response from MSC. The counter increments upon each released call. The measurement point is A, as shown in Figure 828.
OF THE
COUNT
OF
BY
Unit
Times
767
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. 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. When BSC receives the AbisConnectFailureIndication message from BTS, if the voice version used is full-rate voice version 1, then the counter counts. Times
Usage
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. 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. When BSC receives the AbisConnectFailureIndication message from BTS, if the voice version used is full-rate voice version 2, then the counter counts. Times
Usage
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. 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.
Usage
768
When BSC receives the AbisConnectFailureIndication message from BTS, if the voice version used is full-rate voice version 3, then the counter counts. Times
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. 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. When BSC receives the AbisConnectFailureIndication message from BTS, if the voice version used is half-rate voice version 1, then the counter counts. Times
Usage
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. 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. When BSC receives the AbisConnectFailureIndication message from BTS, if the voice version used is half-rate voice version 3, then the counter counts. Times
Usage
769
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. Times Cell
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. Times Cell
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. Times
Unit
770
Statistics Object
Cell
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. Times Cell
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. Times Cell
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is FORCE_REL_BIPBEXCH.
771
Times Cell
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. Times Cell
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. Times Cell
The counter counts when the EV_RANUMC_REL_CMD message is received and the cause is CAUSE_LAPDEXCH.
772
Times Cell
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. Times Cell
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. Times
Unit
773
Statistics Object
Cell
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. Times Cell
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. Times Cell
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
774
handover is executed. If the handover fails and if the current channel is FR, the counter increments. This counter is supported in version V6.20.611f.
Unit Statistics Object
Times Cell
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. Times Cell
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. Times
Unit
775
Statistics Object
Cell
This counter counts the number of call drops on SDCCH due to BTS fault. The counter has two measurement points: When BSC receives the ConnectionFailure message and the cause is "O&M intervention", if the service is on SDCCH, the counter increments. The measurement point is A, as shown in Figure 829.
FIGURE 829 CALL DROP FAULT
DURING
IMMEDIATE ASSIGNMENT
DUE TO
BTS
When BSC receives the O&M status report message from BTS and the cause is BTS being blocked due to fault, the service being affected should be released. If the service being affected is on SDCCH, the counter increments. This counter is supported in version V6.20.614b.
Unit
Times
776
Statistics Object
Cell
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 830. 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.
FIGURE 830 CALL DROP FAULT
DURING
IMMEDIATE ASSIGNMENT
DUE TO
BTS
Times
777
Statistics Object
Cell
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 831.
FIGURE 831 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.
778
Times Cell
This counter counts the number of call drops on data 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 data TCH/F, the counter increments. The measurement point is A, as shown in Figure 832. 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 832 CALL DROP
DURING
ASSIGNMENT
DUE TO
BTS FAULT
779
Times Cell
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 833. 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.
780
DURING
ASSIGNMENT
DUE TO
BTS FAULT
Times Cell
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 834. When BSC receives the O&M status report message from BTS and the cause is BTS being blocked due to fault, the service being af-
781
fected should be released. If the service being affected is on voice TCH/H, the counter increments.
FIGURE 834 CALL DROP
DURING
ASSIGNMENT
DUE TO
BTS FAULT
Times Cell
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 835.
782
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.
FIGURE 835 CALL DROP
DURING
ASSIGNMENT
DUE TO
BTS FAULT
Times Cell
This counter counts the number of call drops due to failure in releasing local switch. In normal cases, the call should return to the normal call status after the local switch is released. However, if fault occurs during the release, such as failure in requesting TC resource or connection failure when TC is external, the no-voice problem will occur. In such cases, the service module will release
783
the call and consider it as a call drop due to failure in releasing local switch. This counter is supported in version V6.20.614c.
Unit Statistics Object
Times Cell
784
Chapter
14
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.
785
Description
This counter counts the maximum number of busy SDCCHs in the cell within measurement period; its value represents SDDCH instantaneous occupation status and the busiest extent. System records SDCCH occupation number in cells. The occupation number increments after SDCCH has been occupied successfully; the occupation number decrements before SDCCH has been released. The counter value updates as occupation number if BSC judges that the counter value is smaller than the occupation number after SDCCH has been occupied successfully and before SDCCH has been released, as well as when measurement data are reported periodically. Update occupation number before SDCCH has been released is because SDCCH status in the previous measurement period has been taken into account.
Usage
This counter is used to find out the busy extent of SDCCH in cells, its value can be used as the reference for whether to increase SDCCH. The counter counts in the following three cases: The counter updates if the maximum busy number exceeds the recorded value after SDCCH has been occupied successfully; 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 836.
FIGURE 836 REPORTING MEASUREMENT DATA
Measurement Point
Unit
Times
786
Average processor load. 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. This counter is used to find out the busy extent of SDCCH in cells, its value can be used as the reference for whether to increase SDCCH. The counter counts when measurement data are reported periodically. The measurement point is A, as shown in Figure 837.
FIGURE 837 REPORTING MEASUREMENT DATA
Usage
Measurement Point
Unit
Times
SDCCH congestion time This counter counts the total time of SDCCH congestion. BSC sets congestion mark when SDCCH request fails, and the start of congestion time is recorded. BSC clear congestion mark when SDCCH request succeeds. If congestion mark is set when requiring SDCCH, then this period
787
of congestion time is to use the present time minus the previous recorded congestion time. If congestion mark is set before SDCCH has been released or when measurement values are reported periodically, the congestion time is calculated. The sum of each congestion time is the total time of SDCCH congestion.
Usage
This counter is used to find out the busy extent of SDCCH in cells, its value can be used as the reference for whether to increase SDCCH. The counter counts in the following three cases: 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 838.
FIGURE 838 REPORTING MEASUREMENT DATA
Measurement Point
Unit
Second
Number of unavailable defined SDCCH iBSC supports dynamic transform between SDCCH and TCH. This counter counts the number of unavailable static SDCCH configured by present cell through OMCR.
788
This counter is used to find out the unavailability of SDCCH in the present cell for eliminating cell failures. The counter value is inquired from database when periodical measurement data are reported. The measurement point is A, as shown in Figure 839.
FIGURE 839 REPORTING MEASUREMENT DATA
Maximum number of busy radio channel 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. 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. The counter value is inquired from database when periodical measurement data are reported. The measurement point is A, as shown in Figure 840.
Usage
Measurement Point
789
Average number of busy radio channel 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. 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. The counter value is inquired from database when periodical measurement data are reported. The measurement point is A, as shown in Figure 841.
Usage
Measurement Point
790
Average number of busy TCH/H 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. 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. 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 842.
Usage
Measurement Point
791
Times 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
TCH/H busy time (SpeechVer1). This counter counts the total TCH/H busy time (SpeechVer1) in cells; its value represents traffic on TCH/H (SpeechVer1). 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. The counter counts in the following three cases: 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 843.
Measurement Point
792
The measurement formula is: (Present time previous measurement time) Number of MS that are occupying channels The reported measurement value is the accumulation of each measurement value. After each accumulation, the previous measurement time is updated as the present time. The number of MS that are occupying channels increments when TCH/H is obtained successfully after accumulation. The number of MS that are occupying channels decrements when TCH/H is released after accumulation.
Unit Related Features
Second 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
TCH/H busy time(SpeechVer3). This counter counts the total TCH/H busy time (SpeechVer3) in cells; its value represents traffic on TCH/H (SpeechVer3). 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. The counter counts in the following three cases: The counter counts time and accumulates when TCH/H is obtained successfully
Measurement Point
793
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 844.
FIGURE 844 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 Related Features
Second 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
TCH/H congestion time This counter counts the total TCH/H congestion time.
794
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 Measurement Point
This counter is used to find out the busy extent of TCH/H in cells, its value can be used as the reference for whether to increase TCH/H. The counter counts in the following three cases: 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. 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 845.
FIGURE 845 REPORTING MEASUREMENT DATA
Second 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
795
Average number of busy TCH/F 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. 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. 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 846.
FIGURE 846 REPORTING MEASUREMENT DATA
Usage
Measurement Point
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-003 Full dynamic channel allocation on Um interface
TCH/F busy time (SpeechVer1) This counter counts the total TCH/F busy time (SpeechVer1) in cells; its value represents traffic on TCH/F (SpeechVer1).
796
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. The counter counts in the following three cases: 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 847.
FIGURE 847 REPORTING MEASUREMENT DATA
Measurement Point
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 Related Features
Second 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
797
TCH/F busy time (SpeechVer2) This counter counts the total TCH/F busy time (SpeechVer2) in cells; its value represents traffic on TCH/F (SpeechVer2). 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. The counter counts in the following three cases: 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 848.
FIGURE 848 REPORTING MEASUREMENT DATA
Measurement Point
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
798
Related Features
ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-003 Full dynamic channel allocation on Um interface
TCH/F busy time(SpeechVer3) This counter counts the total TCH/F busy time (SpeechVer3) in cells; its value represents traffic on TCH/F (SpeechVer3). 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. The counter counts in the following three cases: 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 849.
FIGURE 849 REPORTING MEASUREMENT DATA
Measurement Point
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
799
measurement time is updated as the present time. The number of MS that are occupying channels increments when TCH/F is obtained successfully after accumulation. The number of MS that are occupying channels decrements when TCH/F is released after accumulation.
Unit Related Features
Second 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
TCH/F congestion time This counter counts the total time of TCH/F congestion. BSC sets congestion mark when TCH/F request fails, and the start 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.
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. The counter counts in the following three cases: 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 850.
800
Second ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-003 Full dynamic channel allocation on Um interface
Number of TRX s This counter counts the total number of TRXs in all status configured in the cell. This counter is used to find out the configured TRX number and resource utilizing status in the present cell. The counter value is inquired from database when periodical measurement data are reported. The measurement point is A, as shown in Figure 851.
801
Unit
Times
Reserved TCH/F busy time 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. This counter is used to find out the utilizing status of reserved TCH/F to facilitate the configuration adjustment of reserved TCH/F. The counter counts in the following three cases: The counter counts when reserved TCH/F is obtained successfully The counter counts when reserved TCH/F is released; The counter counts when measurement values are reported periodically. The measurement point is A, as shown in Figure 852.
802
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
This counter counts the maximum number of TCHs being occupied during the measurement period. The system records the number of TCHs being occupied in the cell. After a TCH is occupied successfully, the counter increments; after a TCH is released, the counter decrements. After TCH is successfully occupied or before TCH is released or when the measurement data is reported periodically, if BSC finds that the counter's value is smaller than the number of TCHs actually being occupied, then the counter's value is updated to be the actual number of TCHs being occupied. Considering the TCH usage in the last measurement period, the number of TCH being occupied is updated before TCH is released.
803
Measurement Point
The counter counts at the following time points. 1. After TCH is occupied successfully, if the maximum number of busy TCHs exceeds the recorded value, the counter counts. 2. Before TCH is released, if the maximum number of busy TCHs exceeds the recorded value, the counter counts. 3. When the measurement data is reported periodically, if the maximum number of busy TCHs exceeds the recorded value, the counter counts. Times
Unit
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. 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. When the confirmation message (tGetCellDownTimeAck.wResult) of cell's interruption duration obtained from database is true, the counter counts. Second
Usage
804
Chapter
15
805
C901090034 Number of MSC-controlled incoming handover attempts due to forced handover ....................................... 834 C901090037 MSC-controlled incoming handover time due to queue ............................................................................ 835 C901090038 Queue number of MSC-controlled incoming handover............................................................................. 837 C901090039 MSC-controlled incoming handover success time due to queue .................................................................. 839 C901090040 Number of MSC-controlled incoming handover success due to queue....................................................... 840 C901090041 Number of incoming handover attempts from the same layer and frequency ........................................... 841 C901090042 Number of incoming handover success from the same layer and frequency................................................. 842 C901090043 Number of outgoing handover attempts to the same layer and frequency................................................. 843 C901090044 Number of outgoing handover success to the same layer and frequency................................................. 844 C901090045 Number of incoming handover attempts from undefined layer to the same frequency ............................... 845 C901090046 Number of incoming handover success from undefined layer to the same frequency .................................. 846 C901090047 Number of outgoing handover attempts from undefined layer to the same frequency ............................... 847 C901090048 Number of outgoing handover success from undefined layer to the same frequency .................................. 848 C901090049 Number of incoming handover attempts from undefined layer (GSM900) to current layer (GSM1800) ......... 849 C901090052 Number of outgoing handover attempts from current layer (GSM900) to undefined layer (GSM1800) ......... 850 C901090053 Number of outgoing handover from current layer (GSM900) to undefined layer (GSM1800)............................ 851 C901090054 Number of outgoing handover success from current layer (GSM900) to undefined layer (GSM1800) ............. 852 C901090055 Number of incoming handover attempts from undefined layer (GSM1800) to current layer (GSM900) ......... 853 C901090058 Number of outgoing handover attempts from undefined layer (GSM1800) to current layer (GSM900) ......... 854 C901090059 Number of outgoing handover from undefined layer (GSM1800) to current layer (GSM900) ....................... 855 C901090060 Number of outgoing handover success from undefined layer (GSM1800) to current layer (GSM900) ............ 856 C901090061 Number of incoming handover attempts from upper layer to the same frequency..................................... 857 C901090062 Number of incoming handover success from upper layer to the same frequency ........................................ 858 C901090063 Number of outgoing handover attempts from the same frequency to upper layer .......................................... 859 C901090064 Number of outgoing handover success from the same frequency to upper layer .......................................... 860 C901090065 Number of incoming handover attempts from lower layer to the same frequency ..................................... 861 C901090066 Number of incoming handover success from lower layer to the same frequency ..................................... 862 C901090067 Number of outgoing handover attempts from the same frequency to lower layer........................................... 863 C901090068 Number of outgoing handover success from the same frequency to lower layer........................................... 864 C901090069 Number of incoming handover attempts from the same layer GSM900 to GSM1800 ................................. 865
806
C901090072 Number of outgoing handover attempts to the same layer GSM900 to GSM1800 ....................................... 866 C901090073 Number of outgoing handover to the same layer GSM900 to GSM1800 ....................................................... 867 C901090074 Number of outgoing handover success to the same layer GSM900 to GSM1800 ....................................... 867 C901090075 Number of incoming handover attempts from GSM900 to GSM1800 from the upper layer ......................... 868 C901090078 Number of outgoing handover attempts from GSM900 to GSM1800 to the upper layer ............................. 869 C901090079 Number of outgoing handover from GSM900 to GSM1800 to the upper layer ............................................. 870 C901090080 Number of outgoing handover success from GSM900 to GSM1800 to the upper layer ............................. 871 C901090081 Number of incoming handover attempts from GSM900 to GSM1800 from the lower layer .......................... 872 C901090084 Number of outgoing handover attempts from GSM900 to GSM1800 from the lower layer .......................... 873 C901090085 Number of outgoing handover from GSM900 to GSM1800 in the lower layer .............................................. 874 C901090086 Number of outgoing handover success from GSM900 to GSM1800 in the lower layer .............................. 875 C901090087 Number of incoming handover attempts from GSM1800 to GSM900 from the same layer .......................... 876 C901090090 Number of outgoing handover attempts from GSM1800 to GSM900 from the same layer .......................... 877 C901090091 Number of outgoing handover from GSM1800 to GSM900 from the same layer ............................................ 878 C901090092 Number of outgoing handover success from GSM1800 to GSM900 from the same layer .......................... 879 C901090093 Number of incoming handover attempts from GSM1800 to GSM900 from the upper layer ......................... 880 C901090096 Number of outgoing handover attempts from GSM1800 to GSM900 to the upper layer ............................. 881 C901090097 Number of outgoing handover from GSM1800 to GSM900 to the upper layer ............................................... 882 C901090098 Number of outgoing handover success from GSM1800 to GSM900 to the upper layer ............................. 883 C901090099 Number of incoming handover attempts from GSM1800 to GSM900 from the lower layer .......................... 884 C901090102 Number of outgoing handover attempts from GSM1800 to GSM900 to the lower layer.............................. 885 C901090103 Number of outgoing handover from GSM1800 to GSM900 to the lower layer................................................ 886 C901090104 Number of outgoing handover success from GSM1800 to GSM900 to the lower layer.............................. 887 C901090105 Number of intra-cell handover attempts ........... 888 C901090108 Number of intra-cell inner-circle-to-outer-circle handover attempts .......................................................... 889 C901090109 Number of intra-cell inner-circle-to-outer-circle handover success ............................................................ 889 C901090110 Number of intra-cell outer-circle-to-inner-circle handover attempts .......................................................... 890 C901090111 Number of intra-cell outer-circle-to-inner-circle handover success ............................................................ 891 C901090112 Number of intra-cell inner-circle-to-inner-circle handover attempts .......................................................... 892 C901090113 Number of intra-cell inner-circle-to-inner-circle handover success ............................................................ 892
807
C901090114 Number of intra-cell outer-circle-to-outer-circle handover attempts .......................................................... 893 C901090115 Number of intra-cell outer-circle-to-outer-circle handover success ............................................................ 894 C901090116 Number of handover attempts from 2G to 3G................................................................................. 895 C901090117 Number of handover from 2G to 3G................. 895 C901090118 Number of handover success from 2G to 3G................................................................................. 896 C901090119 Number of handover attempts from 3G to 2G................................................................................. 897 C901090120 Number of handover from 3G to 2G................. 898 C901090121 Number of handover success from 3G to 2G................................................................................. 899 C901090122 Number of intra-cell handover attempts from TCH/F ............................................................................ 899 C901090123 Number of intra-cell TCH/F-to-TCH/F handover............................................................................. 900 C901090124 Number of intra-cell TCH/F-to-TCH/F handover success .......................................................................... 901 C901090125 Number of intra-cell TCH/F-to-TCH/H handover............................................................................. 902 C901090126 Number of intra-cell TCH/F-to-TCH/H handover success .......................................................................... 903 C901090127 Number of intra-cell handover attempts from TCH/H............................................................................ 903 C901090128 Number of intra-cell TCH/H-to-TCH/F handover............................................................................. 904 C901090129 Number of intra-cell TCH/H-to-TCH/F handover success .......................................................................... 905 C901090130 Number of intra-cell TCH/H-to-TCH/H handover............................................................................. 906 C901090131 Number of intra-cell TCH/H-to-TCH/H handover success .......................................................................... 907 C901090132 Number of inter-cell handover attempts from TCH/F ............................................................................ 908 C901090133 Number of inter-cell TCH/F-to-TCH/F handover............................................................................. 909 C901090134 Number of inter-cell TCH/F-to-TCH/F handover success .......................................................................... 909 C901090135 Number of inter-cell TCH/F-to-TCH/H handover............................................................................. 910 C901090136 Number of inter-cell TCH/F-to-TCH/H handover success .......................................................................... 911 C901090137 Number of inter-cell handover attempts from TCH/H............................................................................ 912 C901090138 Number of inter-cell TCH/H-to-TCH/F handover............................................................................. 913 C901090139 Number of inter-cell TCH/H-to-TCH/F handover success .......................................................................... 914 C901090140 Number of inter-cell TCH/H-to-TCH/H handover............................................................................. 915 C901090141 Number of inter-cell TCH/H-to-TCH/H handover success .......................................................................... 916 C901090142 Total dual-band outgoing handover attempts ........................................................................... 917 C901090145 Number of dual band incoming handover attempts ........................................................................... 918 C901090148 Number of intra-cell invalid handovers ............. 919
808
C901090149 Number of BSC-controlled inter-cell incoming handover attempts due to forced release (emergency service) .............................................................................. 920 C901090150 Number of BSC-controlled inter-cell incoming handover (forced release) (emergency service) ................... 921 C901090151 Number of BSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service) ............................................................................... 922 C901090152 Number of BSC-controlled inter-cell incoming handover (forced handover) (emergency service) ................ 923 C901090153 Number of BSC-controlled inter-cell incoming handover attempts due to queue (emergency service).......... 924 C901090154 Number of BSC-controlled inter-cell incoming handover (queue) (emergency service) .............................. 925 C901090155 Number of MSC-controlled incoming handover attempts due to forced release (emergency service)............. 926 C901090156 Number of MSC-controlled incoming handover (forced release) (emergency service) ................................. 927 C901090157 Number of MSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service) .............................................................................. 928 C901090158 Number of MSC-controlled incoming handover (forced release) (emergency service) ................................. 929 C901090159 Number of MSC-controlled incoming handover attempts due to queue (emergency service)........................ 930 C901090160 Number of MSC-controlled incoming handover (queue) (emergency service) ............................................ 931 C901090161 Number of forced handover target not found (BSC-controlled inter-cell handover due to forced handover) ........................................................................... 932 C901090162 Number of send forced handover request to lower PRI user (BSC-controlled inter-cell handover due to forced handover) ............................................................. 933 C901090163 Number of recv failure from lower PRI user request resource for forced handover (BSC-controlled inter-cell handover due to forced handover) ..................................... 934 C901090164 Number of lower PRI user handover failure (BSC-controlled inter-cell handover due to forced handover) ........................................................................... 936 C901090165 Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced handover) ........................................................................... 937 C901090166 Number of forced release target not found (BSCcontrolled inter-cell handover due to forced release) ............ 938 C901090167 Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced release) ............................................................................ 939 C901090168 Number of HO Target not found (MSC-controlled incoming handover due to forced handover)........................ 940 C901090169 Number of send forced handover request to lower PRI user (MSC-controlled incoming handover due to forced handover) ............................................................. 941 C901090170 Number of failure to lower PRI user request resource for forced handover (MSC-controlled incoming handover due to forced handover) .......................................... 942 C901090171 Number of lower PRI user handover failure (MSC-controlled incoming handover due to forced handover) ........................................................................... 942
809
C901090172 Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced handover) ........................................................................... 943 C901090173 Number of forced release target not found (MSC-controlled incoming handover due to forced release) ............................................................................ 943 C901090174 Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced release) ............................................................................ 944 C901090175 Number of get before grab released channel (assignment forced handover) ............................................... 945 C901090176 Number of get before grab released channel (assignment forced release) .................................................. 945 C901090177 Number of handover attempts due to eMLPP forced handover .............................................................. 946 C901090178 Number of handover due to eMLPP forced handover............................................................................. 946 C901090179 Number of handover success due to eMLPP forced handover .............................................................. 947 C901090180 Number of BSC-controlled inter-cell outgoing handover attempts between PLMN ..................................... 947 C901090181 Number of BSC-controlled inter-cell outgoing handover between PLMN .................................................. 947 C901090182 Number of BSC-controlled inter-cell outgoing handover success between PLMN ....................................... 948 C901090183 Number of MSC-controlled outgoing handover attempts between PLMN ................................................... 948 C901090184 Number of MSC-controlled outgoing handover request fail between PLMN due to unknown reason .............. 948 C901090185 Number of MSC-controlled outgoing handover request fail between PLMN due to unavailable ground resource .................................................................................... 949 C901090186 Number of MSC-controlled outgoing handover request fail between PLMN due to unavailable radio resource ........................................................................... 950 C901090187 Number of MSC-controlled outgoing handover request fail between PLMN due to other reasons .................. 950 C901090188 Number of MSC-controlled outgoing handover between PLMN ................................................................ 951 C901090189 Number of MSC-controlled outgoing handover success between PLMN ..................................................... 952 C901090190 Number of BSC-controlled inter-cell incoming handover attempt between PLMN....................................... 953 C901090191 Number of BSC-controlled inter-cell incoming handover between PLMN .................................................. 953 C901090192 Number of BSC-controlled inter-cell incoming handover force-release attempt between PLMN.................... 953 C901090193 Number of BSC-controlled inter-cell incoming handover between PLMN due to force release ...................... 954 C901090194 Number of BSC-controlled inter-cell incoming handover queue attempt between PLMN ............................. 954 C901090195 Number of BSC-controlled inter-cell incoming handover between PLMN due to queue ............................... 954 C901090196 Number of BSC-controlled inter-cell incoming handover force-handover attempt between PLMN................. 955 C901090197 Number of BSC-controlled inter-cell incoming handover between PLMN due to force handover ................... 955 C901090198 Number of BSC-controlled inter-cell incoming handover success between PLMN ....................................... 955
810
C901090199 Number of MSC-controlled incoming handover attempt between PLMN ................................................... 956 C901090200 A interface incoming handover fail between PLMN due to circuit block.................................................. 957 C901090201 A interface incoming handover fail between PLMN due to circuit unmatch ............................................. 958 C901090202 A interface incoming handover fail between PLMN due to unavailable radio resource .............................. 958 C901090203 A interface incoming handover fail between PLMN due to other reason................................................. 959 C901090204 Number of MSC-controlled incoming handover between PLMN ................................................................ 959 C901090205 Number of MSC-controlled incoming handover force-release attempt between PLMN ................................. 959 C901090206 Number of MSC-controlled incoming handover between PLMN due to force release .................................... 960 C901090207 Number of MSC-controlled incoming handover queue attempt between PLMN ........................................... 960 C901090208 Number of MSC-controlled incoming handover between PLMN due to queue ............................................. 961 C901090209 Number of MSC-controlled incoming handover force-handover attempt between PLMN .............................. 962 C901090210 Number of MSC-controlled incoming handover between PLMN due to force handover ................................. 962 C901090211 Number of MSC-controlled incoming handover success between PLMN .................................................... 963 C901090212 Number of handover due to Fragment reorganization ............................................................................ 963 C901090213 Number of handover success due to Fragment reorganization................................................................. 963 C901090214 Number of handover attempt from AMR FR to AMR HR due to high load .................................................. 964 C901090215 Number of handover from AMR FR to AMR HR due to high load .............................................................. 965 C901090216 Number of handover success from AMR FR to AMR HR due to high load .................................................. 966 C901090217 Number of handover attempt from FR to HR due to high load .................................................................... 966 C901090218 Number of handover from FR to HR due to high load............................................................................... 967 C901090219 Number of handover success from FR to HR due to high load .................................................................... 968 C901090220 Number of handover attempt from AMR HR to AMR FR due to bad quality ................................................ 968 C901090221 Number of handover from AMR HR to AMR FR due to bad quality ........................................................... 969 C901090222 Number of handover success from AMR HR to AMR FR due to bad quality ................................................ 970 C901090223 Number of handover attempt from HR to FR due to bad quality ................................................................. 970 C901090224 Number of handover from HR to FR due to bad quality ........................................................................... 971 C901090225 Number of handover success from HR to FR due to bad quality ................................................................. 972 C901090226 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM900 ..................... 972 C901090227 Number of BSC-controlled inter-cell outgoing handover, from GSM900 to GSM900................................... 973 C901090228 Number of BSC-controlled inter-cell outgoing handover success, from GSM900 to GSM900 ....................... 974
811
C901090229 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM1800.................. 975 C901090230 Number of BSC-controlled inter-cell outgoing handover, from GSM1800 to GSM1800 ............................... 976 C901090231 Number of BSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM1800 ................... 977 C901090232 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM1800 ................... 978 C901090233 Number of BSC-controlled inter-cell outgoing handover, from GSM900 to GSM1800 ................................. 979 C901090234 Number of BSC-controlled inter-cell outgoing handover success, from GSM900 to GSM1800 ..................... 980 C901090235 Number of BSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM900 ................... 981 C901090236 Number of BSC-controlled inter-cell outgoing handover, from GSM1800 to GSM900 ................................. 982 C901090237 Number of BSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM900 ..................... 983 C901090238 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM900 ..................... 984 C901090239 Number of MSC-controlled inter-cell outgoing handover, from GSM900 to GSM900................................... 985 C901090240 Number of MSC-controlled inter-cell outgoing handover success, from GSM900 to GSM900 ....................... 986 C901090241 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM1800.................. 987 C901090242 Number of MSC-controlled inter-cell outgoing handover, from GSM1800 to GSM1800 ............................... 988 C901090243 Number of MSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM1800 ................... 989 C901090244 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM900 to GSM1800 ................... 990 C901090245 Number of MSC-controlled inter-cell outgoing handover, from GSM900 to GSM1800 ................................. 990 C901090246 Number of MSC-controlled inter-cell outgoing handover success, from GSM900 to GSM1800 ..................... 991 C901090247 Number of MSC-controlled inter-cell outgoing handover attempts, from GSM1800 to GSM900 ................... 992 C901090248 Number of MSC-controlled inter-cell outgoing handover, from GSM1800 to GSM900 ................................. 993 C901090249 Number of MSC-controlled inter-cell outgoing handover success, from GSM1800 to GSM900 ..................... 994
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.
812
Number of BSC-controlled inter-cell outgoing handover attempts This counter counts the Number of BSC-controlled inter-cell outgoing handover attempts originated from the source cell by MS. 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. 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 853.
FIGURE 853 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER ATTEMPT
Measurement Point
Number of MSC-controlled outgoing handover attempts This counter counts the number of MSC-controlled inter-BSC outgoing handover attempts originated from the source cell by MS.
813
Usage
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. 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 854.
FIGURE 854 MSC-CONTROLLED OUTGOING HANDOVER ATTEMPTS
Measurement Point
C901090005 Number of MSC-controlled outgoing handover request failures due to unclear factors
Definition Description
Number of MSC-controlled outgoing handover request failures due to unclear factors 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. 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. 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
Usage
Measurement Point
814
before the protection timer expires, the counter increments. The measurement point is A, as shown in Figure 855.
FIGURE 855 MSC-CONTROLLED OUTGOING HANDOVER REQUEST FAILURES DUE TO UNCLEAR FACTORS
C901090006 Number of MSC-controlled outgoing handover request failures due to unavailable ground resource
Definition Description
Number of MSC-controlled outgoing handover request failures due to unavailable ground resource 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. 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. 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 856.
Usage
Measurement Point
815
C901090007 Number of MSC-controlled outgoing handover request failures due to unavailable radio resource
Definition Description
Number of MSC-controlled outgoing request failures due to unavailable radio resource 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. 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. 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 857.
Usage
Measurement Point
816
C901090008 Number of MSC-controlled outgoing handover request failures due to other factors
Definition Description
Number of MSC-controlled outgoing handover request failures due to other factors 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. 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. 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 858.
Usage
Measurement Point
817
Number of BSC-controlled inter-cell incoming handover attempts This counter counts the Number of BSC-controlled inter-cell incoming handover attempts from MS to target cell. 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. 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 859.
FIGURE 859 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Measurement Point
818
Number of BSC-controlled incoming handover attempts due to forced release This counter counts the number of forced release attempts originated by target cell due to unavailable radio resource during the process of MS -originated BSC-controlled inter-cell incoming handover. When target instance fails to allocate the channel, forced release attempts could be originated referring to the MS priority and MSC & BSC settings. 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. When intra-BSC target cell receives the wireless channel application request, if the application cause is BSC-controlled inter-cell incoming handover and wireless channel is unavailable to target cell, forced release attempt decision starts. If forced release attempt is feasible, the counter increments before the target cell sends forced release message to the instance that is to be released. The measurement point is A, as shown in Figure 860.
FIGURE 860 FORCED RELEASE ATTEMPTS
Usage
Measurement Point
819
Number of BSC-controlled incoming handover attempts due to queue 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. 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. 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 861.
FIGURE 861 QUEUING ATTEMPTS
Usage
Measurement Point
820
Number of BSC-controlled incoming handover attempts due to forced handover 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. 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. When intra-BSC target cell receives the wireless channel application request, if the application cause is BSC-controlled intercell incoming handover and wireless channel is unavailable to target cell, forced-handover attempt decision starts. If forced-handover attempt is feasible, the counter increments before the target cell sends forced-handover message to the instance that is to be forced. The measurement point is A, as shown inFigure 862.
FIGURE 862 FORCED-HANDOVER ATTEMPTS
Usage
Measurement Point
821
BSC-controlled incoming handover time due to queue 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. 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. Under the condition that database acquires resource via dynamic channel conversion or MS releases resource and queuing instance receives usable message, if the application cause is BSC-controlled incoming handover, the queuing time accumulates. The measurement point is A, as shown in Figure 863.
FIGURE 863 EXECUTION IN QUEUING
Usage
Measurement Point
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 864.
822
During the process of instance queuing, when the instance is released due to some causes, if the application cause is BSCcontrolled incoming handover, the queuing time accumulates. The measurement point is A, as shown in Figure 865.
FIGURE 865 INSTANCE RELEASE DURING QUEUING
823
Queue number of BSC-controlled incoming handover This counter counts the total queue number of calls that participate in BSC-controlled intra-cell incoming handover. 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. 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 866.
FIGURE 866 EXECUTION IN QUEUING
Measurement Point
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 867.
824
During the process of instance queuing, when the instance is released due to certain causes, if the application cause is BSCcontrolled incoming handover, the counter increments. The measurement point is A, as shown in Figure 868.
FIGURE 868 INSTANCE RELEASE DURING QUEUING
825
BSC-controlled incoming handover success time due to queue This counter counts the total time of calls that participate in successful BSC-controlled intra-cell incoming handover due to queue and acquiring resource. 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. 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 BSC-controlled incoming handover, the queuing time accumulates. The measurement point is A, as shown in Figure 869.
FIGURE 869 EXECUTION IN QUEUING
Usage
Measurement Point
826
Number of BSC-controlled incoming handover success due to queue This counter counts the total number of calls that participate in BSC-controlled intra-cell incoming handover due to queue and successfully acquiring resource. 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. 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 BSCcontrolled incoming handover, the counter increments. The measurement point is A, as shown in Figure 870.
FIGURE 870 EXECUTION IN QUEUING
Usage
Measurement Point
827
Number of MSC-controlled incoming handover attempts This counter counts the number of MSC-originated inter-BSC incoming handover attempts. 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. When the target cell receives the channel application, if the application cause is external incoming handover, the counter increments. The measurement point is A, as shown in Figure 871.
FIGURE 871 MSC-CONTROLLED INCOMING HANDOVER ATTEMPTS
Measurement Point
Number of incoming handover failure due to circuit block This counter counts the number of unsuccessful MSC-originated inter-BSC incoming handover due to ground circuit block.
828
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. 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 872.
FIGURE 872 UNSUCCESSFUL MSC-CONTROLLED EXTERNAL INCOMING HANDOVER
Measurement Point
Number of incoming handover failure due to circuit group mismatch This counter counts the number of unsuccessful MSC-originated inter-BSC incoming handover due to ground circuit group mismatch. 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. 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 873.
Measurement Point
829
Number of incoming handover failure requests due to unavailable radio resource This counter counts the number of unsuccessful MSC-originated inter-BSC incoming handover due to unavailable radio resource. This counter is used to find out the frequency of unsuccessful MSCoriginated inter-BSC incoming handover due to unavailable radio resource, and is used to observe the external handover flow. 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 874.
Measurement Point
830
Number of incoming handover failure due to other factors 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. This counter is used to find out the frequency of unsuccessful MSCoriginated inter-BSC incoming handover due to other factors, and is used to observe the external handover flow. 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 875.
FIGURE 875 UNSUCCESSFUL MSC-CONTROLLED EXTERNAL INCOMING HANDOVER
Usage
Measurement Point
831
Number of MSC-controlled incoming handover attempts due to forced release 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. 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. 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 876.
FIGURE 876 FORCED RELEASE ATTEMPTS
Usage
Measurement Point
Unit
Times
832
Related Features
Number of MSC-controlled incoming handover attempts due to queue 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. 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. 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, 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 877.
FIGURE 877 QUEUING ATTEMPTS
Usage
Measurement Point
833
ZGO-01-03-001 eMLPP
Number of MSC-controlled incoming handover attempts due to forced handovers 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. 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. 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 878.
FIGURE 878 FORCED-HANDOVER ATTEMPTS
Usage
Measurement Point
834
MSC-controlled incoming handover time due to queue This counter counts the total time of call queuing that participate in MSC-controlled intra-cell incoming handover due to queue. 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. Under the condition that database acquires resource via dynamic channel conversion or MS releases resource, and queuing instance receives usable message, if the application cause is MSC-controlled incoming handover, the queuing time accumulates. The measurement point is A, as shown in Figure 879.
FIGURE 879 EXECUTION IN QUEUING
Measurement Point
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 880.
835
During the process of instance queuing, when the instance is released due to some causes, if the application cause is MSCcontrolled incoming handover, the queuing time accumulates. The measurement point is A, as shown in Figure 881.
FIGURE 881 INSTANCE RELEASE DURING QUEUING
836
Queue number of MSC-controlled incoming handover This counter counts the total queue number of calls that participate in BSC-controlled intra-cell incoming handover. 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. 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 882.
FIGURE 882 EXECUTION IN QUEUING
Measurement Point
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 883.
837
During the process of instance queuing, when the instance is released due to some causes, if the application cause is MSCcontrolled incoming handover, the counter increments. The measurement point is A, as shown in Figure 884.
FIGURE 884 INSTANCE RELEASE DURING QUEUING
838
MSC-controlled incoming handover success time due to queue This counter counts the total time of calls that participate in successful MSC-controlled intra-cell incoming handover due to queue and acquiring resource. 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. 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 885.
FIGURE 885 EXECUTION IN QUEUING
Usage
Measurement Point
839
Number of MSC-controlled incoming handover success due to queue This counter counts the total number of calls that participate in MSC-controlled intra-cell incoming handover due to queue and successfully acquires resource. 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. 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 MSCcontrolled incoming handover, the counter increments. The measurement point is A, as shown in Figure 886.
FIGURE 886 EXECUTION IN QUEUING
Usage
Measurement Point
840
C901090041 Number of incoming handover attempts from the same layer and frequency
Definition Description
Number of incoming handover attempts from the same layer and frequency This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell receives from the same layer and frequency. 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. 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 887.
FIGURE 887 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Usage
Measurement Point
841
C901090042 Number of incoming handover success from the same layer and frequency
Definition Description
Number of incoming handover success from the same layer and frequency This counter counts the number of successful BSC-controlled intercell incoming handover the target cell receives from the same layer and frequency. 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. When intra-BSC target cell receives the handover completed message, if the application cause is BSC-controlled inter-cell handover and the source cell is at the same layer and frequency, the counter increments. The measurement point is A, as shown inFigure 888.
FIGURE 888 SUCCESSFUL BSC-CONTROLLED INTER-CELL INCOMING HANDOVER
Usage
Measurement Point
842
C901090043 Number of outgoing handover attempts to the same layer and frequency
Definition Description
Number of outgoing handover attempts to the same layer and frequency This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the target cell sends to the same layer and frequency. 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. 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 889.
FIGURE 889 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER ATTEMPT
Usage
Measurement Point
843
C901090044 Number of outgoing handover success to the same layer and frequency
Definition Description
Number of outgoing handover success to the same layer and frequency This counter counts the number of successful BSC-controlled intercell outgoing handover the target cell sends to the same layer and frequency. This counter is used to find out the frequency of successful BSCcontrolled outgoing handover to the same layer and frequency, which helps to make the network planning. 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 890.
FIGURE 890 SUCCESSFUL BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER
Usage
Measurement Point
844
C901090045 Number of incoming handover attempts from undefined layer to the same frequency
Definition Description
Number of incoming handover attempts from undefined layer to the same frequency This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell receives from undefined layer to the same frequency. 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. 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 891.
FIGURE 891 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Usage
Measurement Point
845
C901090046 Number of incoming handover success from undefined layer to the same frequency
Definition Description
Number of incoming handover success from undefined layer to the same frequency This counter counts the number of successful BSC-controlled inter-cell incoming handover the target cell receives from undefined layer to the same frequency. 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. 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 892.
FIGURE 892 SUCCESSFUL BSC-CONTROLLED INTER-CELL INCOMING HANDOVER
Usage
Measurement Point
846
C901090047 Number of outgoing handover attempts from undefined layer to the same frequency
Definition Description
Number of outgoing handover attempts from undefined layer to the same frequency This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell sends from undefined layer to the same frequency. 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. 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 893.
FIGURE 893 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER ATTEMPT
Usage
Measurement Point
847
C901090048 Number of outgoing handover success from undefined layer to the same frequency
Definition Description
Number of outgoing handover success from undefined layer to the same frequency This counter counts the number of successful BSC-controlled intercell outgoing handover the source cell sends from undefined layer to the same frequency. This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from undefined layer to the same frequency, which helps to make the network planning. 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 894.
FIGURE 894 SUCCESSFUL BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER
Usage
Measurement Point
848
C901090049 Number of incoming handover attempts from undefined layer (GSM900) to current layer (GSM1800)
Definition Description
Number of incoming handover attempts from undefined layer (GSM900) to current layer (GSM1800) This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM1800) receives from undefined layer (GSM900). 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. 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 895.
FIGURE 895 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Usage
Measurement Point
849
C901090052 Number of outgoing handover attempts from current layer (GSM900) to undefined layer (GSM1800)
Definition Description
Number of outgoing handover attempts from current layer (GSM900) to undefined layer (GSM1800) This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM900) sends to undefined layer (GSM1800). 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. 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 896.
FIGURE 896 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER ATTEMPT
Usage
Measurement Point
850
C901090053 Number of outgoing handover from current layer (GSM900) to undefined layer (GSM1800)
Definition Description
Number of outgoing handover from current layer (GSM900) to undefined layer (GSM1800) This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to undefined layer (GSM1800). 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. 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 897.
FIGURE 897 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER EXECUTION FLOW
Usage
Measurement Point
851
C901090054 Number of outgoing handover success from current layer (GSM900) to undefined layer (GSM1800)
Definition Description
Number of outgoing handover success from current layer (GSM900) to undefined layer (GSM1800) 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). This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from undefined layer to the same frequency (GSM900) to current layer (GSM1800), which helps to make the network planning. 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 898.
FIGURE 898 SUCCESSFUL BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER
Usage
Measurement Point
852
C901090055 Number of incoming handover attempts from undefined layer (GSM1800) to current layer (GSM900)
Definition Description
Number of incoming handover attempts from undefined layer (GSM1800) to current layer (GSM900) This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM900) receives from undefined layer (GSM1800). 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. 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 899.
FIGURE 899 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Usage
Measurement Point
853
C901090058 Number of outgoing handover attempts from undefined layer (GSM1800) to current layer (GSM900)
Definition Description
Number of outgoing handover attempts from undefined layer (GSM1800) to current layer (GSM900) This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM1800) sends to undefined layer (GSM900). 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. 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 900.
FIGURE 900 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER ATTEMPT
Usage
Measurement Point
854
C901090059 Number of outgoing handover from undefined layer (GSM1800) to current layer (GSM900)
Definition Description
Number of outgoing handover from undefined layer (GSM1800) to current layer (GSM900) This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends to undefined layer (GSM900). 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. 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 901.
FIGURE 901 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER EXECUTION FLOW
Usage
Measurement Point
855
C901090060 Number of outgoing handover success from undefined layer (GSM1800) to current layer (GSM900)
Definition Description
Number of outgoing handover success from undefined layer (GSM1800) to current layer (GSM900) 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). This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from undefined layer to the same frequency (GSM1800) to current layer (GSM900), which helps to make the network planning. 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 902.
FIGURE 902 SUCCESSFUL BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER
Usage
Measurement Point
856
C901090061 Number of incoming handover attempts from upper layer to the same frequency
Definition Description
Number of incoming handover attempts from upper layer to the same frequency This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell receives from upper layer to the same frequency. 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. 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 903.
FIGURE 903 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Usage
Measurement Point
857
C901090062 Number of incoming handover success from upper layer to the same frequency
Definition Description
Number of incoming handover success from upper layer to the same frequency This counter counts the number of successful BSC-controlled intercell incoming handover the target cell receives from upper layer to the same frequency. 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. 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 904.
FIGURE 904 SUCCESSFUL BSC-CONTROLLED INTER-CELL INCOMING HANDOVER
Usage
Measurement Point
858
C901090063 Number of outgoing handover attempts from the same frequency to upper layer
Definition Description
Number of outgoing handover attempts from the same frequency to upper layer This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell sends from upper layer to the same frequency. 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. 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 905.
FIGURE 905 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER ATTEMPT
Usage
Measurement Point
859
C901090064 Number of outgoing handover success from the same frequency to upper layer
Definition Description
Number of outgoing handover success from the same frequency to upper layer This counter counts the number of successful BSC-controlled intercell outgoing handover the source cell sends from upper layer to the same frequency. This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from upper layer to the same frequency, which helps to make the network planning. 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 906.
FIGURE 906 SUCCESSFUL BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER
Usage
Measurement Point
860
C901090065 Number of incoming handover attempts from lower layer to the same frequency
Definition Description
Number of incoming handover attempts from lower layer to the same frequency This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell receives from lower layer to the same frequency. 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. 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 907.
FIGURE 907 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Usage
Measurement Point
861
C901090066 Number of incoming handover success from lower layer to the same frequency
Definition Description
Number of incoming handover success from lower layer to the same frequency This counter counts the number of successful BSC-controlled intercell incoming handover the target cell receives from lower layer to the same frequency. 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. 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 908.
FIGURE 908 SUCCESSFUL BSC-CONTROLLED INTER-CELL INCOMING HANDOVER
Usage
Measurement Point
862
C901090067 Number of outgoing handover attempts from the same frequency to lower layer
Definition Description
Number of outgoing handover attempts from the same frequency to lower layer This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell sends from the same frequency to lower layer. 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. 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 909.
FIGURE 909 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER ATTEMPT
Usage
Measurement Point
863
C901090068 Number of outgoing handover success from the same frequency to lower layer
Definition Description
Number of outgoing handover success from the same frequency to lower layer This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell sends from the same frequency to lower layer. This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from the same frequency to lower layer, which helps to make the network planning. 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 910.
FIGURE 910 SUCCESSFUL BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER
Usage
Measurement Point
864
C901090069 Number of incoming handover attempts from the same layer GSM900 to GSM1800
Definition Description
Number of incoming handover attempts from the same layer GSM900 to GSM1800 This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM1800) receives from the same layer (GSM900). 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. 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 911.
FIGURE 911 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Usage
Measurement Point
865
C901090072 Number of outgoing handover attempts to the same layer GSM900 to GSM1800
Definition Description
Number of outgoing handover attempts to the same layer GSM900 to GSM1800 This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM900) sends to the same layer (GSM1800). 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. 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 912.
FIGURE 912 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER ATTEMPT
Usage
Measurement Point
866
Number of outgoing handover to the same layer GSM900 to GSM1800 This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to the same layer (GSM1800). 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. 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 913.
FIGURE 913 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER EXECUTION FLOW
Usage
Measurement Point
C901090074 Number of outgoing handover success to the same layer GSM900 to GSM1800
Definition
867
Description
This counter counts the number of successful BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to the same layer and frequency (GSM1800). This counter is used to find out the frequency of successful BSCcontrolled outgoing handover to the same layer and frequency from GSM900 to GSM1800, which helps to make the network planning. 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 914.
FIGURE 914 SUCCESSFUL BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER
Usage
Measurement Point
C901090075 Number of incoming handover attempts from GSM900 to GSM1800 from the upper layer
Definition Description
Number of incoming handover attempts from GSM900 to GSM1800 from the upper layer This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM1800) receives from upper layer (GSM900). 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.
Usage
868
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 915.
FIGURE 915 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
C901090078 Number of outgoing handover attempts from GSM900 to GSM1800 to the upper layer
Definition Description
Number of outgoing handover attempts from GSM900 to GSM1800 to the upper layer This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM900) sends to upper layer (GSM1800). 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. 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 916.
Usage
Measurement Point
869
C901090079 Number of outgoing handover from GSM900 to GSM1800 to the upper layer
Definition Description
Number of outgoing handover from GSM900 to GSM1800 to the upper layer This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to upper layer (GSM1800). 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. 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 917.
Usage
Measurement Point
870
C901090080 Number of outgoing handover success from GSM900 to GSM1800 to the upper layer
Definition Description
Number of outgoing handover success from GSM900 to GSM1800 to the upper layer This counter counts the number of successful BSC-controlled intercell outgoing handover the source cell (GSM900) sends from upper layer to the same frequency (GSM1800). This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from upper layer to the same frequency from GSM900 to GSM1800, which helps to make the network planning. 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 918.
Usage
Measurement Point
871
C901090081 Number of incoming handover attempts from GSM900 to GSM1800 from the lower layer
Definition Description
Number of incoming handover attempts from GSM900 to GSM1800 from the lower layer This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM1800) receives from lower layer (GSM900). 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. 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 919.
Usage
Measurement Point
872
C901090084 Number of outgoing handover attempts from GSM900 to GSM1800 from the lower layer
Definition Description
Number of outgoing handover attempts from GSM900 to GSM1800 from the lower layer This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM900) sends to lower layer (GSM1800). 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. 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 920.
Usage
Measurement Point
873
C901090085 Number of outgoing handover from GSM900 to GSM1800 in the lower layer
Definition Description
Number of outgoing handover from GSM900 to GSM1800 in the lower layer This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM900) sends to lower layer (GSM1800). 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. 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 921.
Usage
Measurement Point
874
C901090086 Number of outgoing handover success from GSM900 to GSM1800 in the lower layer
Definition Description
Number of outgoing handover success from GSM900 to GSM1800 in the lower layer This counter counts the number of successful BSC-controlled intercell outgoing handover the source cell (GSM900) sends from the same frequency to lower layer (GSM1800). This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from the same frequency to lower layer from GSM900 to GSM1800, which helps to make the network planning. 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 922.
Usage
Measurement Point
875
C901090087 Number of incoming handover attempts from GSM1800 to GSM900 from the same layer
Definition Description
Number of incoming handover attempts from GSM1800 to GSM900 from the same layer This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM900) receives from the same layer (GSM1800). 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. 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 923.
Usage
Measurement Point
876
C901090090 Number of outgoing handover attempts from GSM1800 to GSM900 from the same layer
Definition Description
Number of outgoing handover attempts from GSM1800 to GSM900 from the same layer This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM1800) sends to the same layer (GSM900). 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. 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 924.
Usage
Measurement Point
877
C901090091 Number of outgoing handover from GSM1800 to GSM900 from the same layer
Definition Description
Number of outgoing handover from GSM1800 to GSM900 from the same layer This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends to the same layer (GSM900). 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. 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 925.
Usage
Measurement Point
878
C901090092 Number of outgoing handover success from GSM1800 to GSM900 from the same layer
Definition Description
Number of outgoing handover success from GSM1800 to GSM900 from the same layer This counter counts the number of successful BSC-controlled intercell outgoing handover the source cell (GSM1800) sends to the same layer and frequency (GSM900). This counter is used to find out the frequency of successful BSCcontrolled outgoing handover to the same layer and frequency and from GSM1800 to GSM900, which helps to make the network planning. 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 926.
Usage
Measurement Point
879
C901090093 Number of incoming handover attempts from GSM1800 to GSM900 from the upper layer
Definition Description
Number of incoming handover attempts from GSM1800 to GSM900 from the upper layer This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM900) receives from upper layer (GSM1800). 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. 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 927.
Usage
Measurement Point
880
C901090096 Number of outgoing handover attempts from GSM1800 to GSM900 to the upper layer
Definition Description
Number of outgoing handover attempts from GSM1800 to GSM900 to the upper layer This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM1800) sends to upper layer (GSM900). 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. 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 928.
Usage
Measurement Point
881
C901090097 Number of outgoing handover from GSM1800 to GSM900 to the upper layer
Definition Description
Number of outgoing handover from GSM1800 to GSM900 to the upper layer This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends to upper layer (GSM900). 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. 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 929.
Usage
Measurement Point
882
C901090098 Number of outgoing handover success from GSM1800 to GSM900 to the upper layer
Definition Description
Number of outgoing handover success from GSM1800 to GSM900 to the upper layer 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). This counter is used to find out the frequency of successful BSCcontrolled outgoing handover from upper layer to the same frequency and from GSM1800 to GSM900, which helps to make the network planning. 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 930.
Usage
Measurement Point
883
C901090099 Number of incoming handover attempts from GSM1800 to GSM900 from the lower layer
Definition Description
Number of incoming handover attempts from GSM1800 to GSM900 from the lower layer This counter counts the number of BSC-controlled inter-cell incoming handover attempts the target cell (GSM900) receives from lower layer (GSM1800). 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. 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 931.
Usage
Measurement Point
884
C901090102 Number of outgoing handover attempts from GSM1800 to GSM900 to the lower layer
Definition Description
Number of outgoing handover attempts from GSM1800 to GSM900 to the lower layer This counter counts the number of BSC-controlled inter-cell outgoing handover attempts the source cell (GSM1800) sends to lower layer (GSM900). 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. 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 932.
Usage
Measurement Point
885
C901090103 Number of outgoing handover from GSM1800 to GSM900 to the lower layer
Definition Description
Number of outgoing handover from GSM1800 to GSM900 to the lower layer This counter counts the number of BSC-controlled inter-cell outgoing handover the source cell (GSM1800) sends to lower layer (GSM900). 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. 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 933.
Usage
Measurement Point
886
C901090104 Number of outgoing handover success from GSM1800 to GSM900 to the lower layer
Definition Description
Number of outgoing handover success from GSM1800 to GSM900 to the lower layer This counter counts the number of successful BSC-controlled intercell outgoing handover the source cell (GSM1800) sends from the same frequency to lower layer (GSM900). 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. 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 934.
Usage
Measurement Point
887
Number of intra-cell handover attempts This counter counts the number of intra-cell handover attempts originated from the source cell by MS. 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. 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 935.
FIGURE 935 INTRA-CELL HANDOVER ATTEMPT
Measurement Point
888
Number of intra-cell inner-circle-to-outer-circle handover attempts This counter counts the number of inner-circle-to-outer-circle handover attempts originated by MS when configuring the sub cell. 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. 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 936.
FIGURE 936 INTRA-CELL HANDOVER ATTEMPT
Measurement Point
Number of intra-cell inner-circle-to-outer-circle handover success This counter counts the number of successful inner-circle-to-outercircle handovers originated by MS when configuring the sub cell. This counter is used to find out the frequency of successful intersub cell inner-circle-to-outer-circle handovers. During handover, if the source instance receives the handover completed message from the target instance, and the application
889
cause is inner-circle-to-outer-circle handover, the counter increments. The measurement point is A, as shown in Figure 937.
FIGURE 937 SUCCESSFUL INTRA-CELL HANDOVER
Number of intra-cell outer-circle-to-inner-circle handover attempts This counter counts the number of outer-circle-to-inner-circle handover attempts originated by MS when configuring the sub cell. 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. 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 938.
FIGURE 938 INTRA-CELL HANDOVER ATTEMPT
Measurement Point
890
Number of intra-cell outer-circle-to-inner-circle handover success This counter counts the number of successful outer-circle-to-inner-circle handovers originated by MS when configuring the sub cell. This counter is used to find out the frequency of successful intersub cell outer-circle-to-inner-circle handovers, and is to find out the success ratio of intra-sub cell handovers. 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 939.
FIGURE 939 SUCCESSFUL INTRA-CELL HANDOVER
Usage
Measurement Point
891
Number of intra-cell inner-circle-to-inner-circle handover attempts This counter counts the number of inner-circle-to-inner-circle handover attempts originated by MS when configuring the sub cell. 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. 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 940.
FIGURE 940 INTRA-CELL HANDOVER ATTEMPT
Measurement Point
Number of intra-cell inner-circle-to-inner-circle handover success This counter counts the number of successful inner-circle-to-innercircle handovers originated by MS when configuring the sub cell. This counter is used to find out the frequency of successful intersub cell inner-circle-to-inner-circle handovers. During handover, if the source instance receives the handover completed message from the target instance, and the application
892
cause is inner-circle-to-inner-circle handover, the counter increments. The measurement point is A, as shown in Figure 941.
FIGURE 941 SUCCESSFUL INTRA-CELL HANDOVER
Number of intra-cell outer-circle-to-outer-circle handover attempts This counter counts the number of outer-circle-to-outer-circle handover attempts originated by MS when configuring the sub cell. 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. 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 942.
Measurement Point
893
Number of intra-cell outer-circle-to-outer-circle handover success This counter counts the number of successful outer-circle-to-outer-circle handovers originated by MS when configuring the sub cell. This counter is used to find out the frequency of successful intersub cell outer-circle-to-outer-circle handovers. 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 943.
FIGURE 943 SUCCESSFUL INTRA-CELL HANDOVER
Unit
Times
894
Related Features
Number of handover attempts from 2G to 3G This counter counts the number of inter-system 2G to 3G handover attempts originated by MS. 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. 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 944.
FIGURE 944 MSC-CONTROLLED OUTGOING HANDOVER ATTEMPTS
Measurement Point
895
Description Usage
This counter counts the number of inter-system 2G to 3G handover originated by MS. 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. 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 945.
FIGURE 945 MSC-CONTROLLED OUTGOING HANDOVER
Measurement Point
Number of handover success from 2G to 3G This counter counts the number of successful inter-system 2G to 3G handovers originated by MS. 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. 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 946.
Measurement Point
896
Number of handover attempts from 3G to 2G This counter counts the number of inter-system 3G to 2G handover attempts originated by MS. 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. When 2G cell receives the channel application request, if the application cause is external incoming handover and the source cell is 3G cell, the counter increments. The measurement point is A, as shown inFigure 947.
Measurement Point
897
Number of handover from 3G to 2G This counter counts the number of inter-system 3G to 2G outgoing handover originated by MS. 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. 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 948.
FIGURE 948 MSC-CONTROLLED INCOMING HANDOVER
Measurement Point
Unit
Times
898
Related Features
Number of handover success from 3G to 2G This counter counts the number of successful inter-system 3G to 2G incoming handover originated by MS. 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. When 2G cell receives the handover completed message, if the application cause is MSC-controlled inter-BSC incoming handover and the source cell is 3G cell, the counter increments. The measurement point is A, as shown in Figure 949.
FIGURE 949 MSC-CONTROLLED INCOMING HANDOVER SUCCESS
Measurement Point
Number of intra-cell handover attempts from TCH/F This counter counts the number of intra-cell incoming handover attempts from TCH/F originated by MS. This counter is used to find out the frequency of intra-cell incoming handover attempts from TCH/F. It is one of the parameters to measure the wireless environment.
899
Measurement Point
When BSC receives the channel application request, if the application cause is intra-cell handover, and the source channel is TCH/F, the counter increments. The measurement point is A, as shown in Figure 950.
FIGURE 950 INTRA-CELL INCOMING HANDOVER ATTEMPT
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
Number of intra-cell TCH/F-to-TCH/F handover This counter counts the number of intra-cell TCH/F-to-TCH/F incoming handover originated by MS. This counter is used to find out the frequency of intra-cell TCH/Fto-TCH/F incoming handover attempts. It is one of the parameters to measure the wireless environment. 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 951.
Measurement Point
900
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
Number of intra-cell TCH/F-to-TCH/F handover success This counter counts the number of successful intra-cell TCH/F-toTCH/F incoming handover originated by MS. 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. 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 952.
FIGURE 952 SUCCESSFUL INTRA-CELL HANDOVER
Measurement Point
Unit
Times
901
Related Features
ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
Number of intra-cell TCH/F-to-TCH/H handover This counter counts the number of intra-cell TCH/F-to-TCH/H incoming handover originated by MS. This counter is used to find out the frequency of intra-cell TCH/Fto-TCH/H incoming handover attempts. It is one of the parameters to measure the wireless environment. 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 953.
FIGURE 953 INTRA-CELL INCOMING HANDOVER
Measurement Point
Times 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
902
Number of intra-cell TCH/F-to-TCH/H handover success This counter counts the number of successful intra-cell TCH/F-toTCH/H incoming handover originated by MS. 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. 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 954.
FIGURE 954 SUCCESSFUL INTRA-CELL HANDOVER
Measurement Point
Times 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
Number of intra-cell handover attempts from TCH/H This counter counts the number of intra-cell incoming handover attempts from TCH/H originated by MS.
903
Usage
This counter is used to find out the frequency of intra-cell incoming handover attempts from TCH/H. It is one of the parameters to measure the wireless environment. 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 955.
FIGURE 955 INTRA-CELL INCOMING HANDOVER ATTEMPT
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
Number of intra-cell TCH/H-to-TCH/F handover This counter counts the number of intra-cell TCH/H-to-TCH/F incoming handover originated by MS. This counter is used to find out the frequency of intra-cell TCH/Hto-TCH/F incoming handover attempts. It is one of the parameters to measure the wireless environment. 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 956.
Measurement Point
904
Times 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
Number of intra-cell TCH/H-to-TCH/F handover success This counter counts the number of successful intra-cell TCH/H-toTCH/F incoming handover originated by MS. 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. 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 957.
Measurement Point
905
Times 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
Number of intra-cell TCH/H-to-TCH/H handover This counter counts the number of intra-cell TCH/H-to-TCH/H incoming handover originated by MS. This counter is used to find out the frequency of intra-cell TCH/Hto-TCH/H incoming handover attempts. It is one of the parameters to measure the wireless environment. 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 958.
Measurement Point
906
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
Number of intra-cell TCH/H-to-TCH/H handover success This counter counts the number of successful intra-cell TCH/H-toTCH/H incoming handover originated by MS. 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. 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 959.
FIGURE 959 SUCCESSFUL INTRA-CELL HANDOVER
Measurement Point
907
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
Number of inter-cell handover attempts from TCH/F This counter counts the number of inter-cell incoming handover attempts from TCH/F originated by MS. 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. 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 960.
FIGURE 960 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
908
Number of inter-cell TCH/F-to-TCH/F handover This counter counts the number of inter-cell TCH/F-to-TCH/F incoming handover originated by MS. This counter is used to find out the frequency of inter-cell TCH/Fto-TCH/F incoming handover attempts. It is one of the parameters to measure the wireless environment. 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 961.
FIGURE 961 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
Number of inter-cell TCH/F-to-TCH/F handover success This counter counts the number of successful inter-cell TCH/F-toTCH/F incoming handover originated by MS.
909
Usage
This counter is used to find out the frequency of successful inter-cell TCH/F-to-TCH/F incoming handover. It is one of the parameters to measure the wireless environment. 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 962.
FIGURE 962 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER
Measurement Point
Times ZGB-02-02-001 Basic Handover ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
Number of inter-cell TCH/F-to-TCH/H handover This counter counts the number of inter-cell TCH/F-to-TCH/H incoming handover originated by MS. This counter is used to find out the frequency of inter-cell TCH/Fto-TCH/H incoming handover attempts. It is one of the parameters to measure the wireless environment. 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 963.
Measurement Point
910
Times 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
Number of inter-cell TCH/F-to-TCH/H handover success This counter counts the number of successful inter-cell TCH/F-toTCH/H incoming handover originated by MS. 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. 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 964.
Measurement Point
911
Times 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
Number of inter-cell handover attempts from TCH/H This counter counts the number of inter-cell incoming handover attempts from TCH/H originated by MS. 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. 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 965.
Measurement Point
912
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
Number of inter-cell TCH/H-to-TCH/F handover This counter counts the number of inter-cell TCH/H-to-TCH/F incoming handover originated by MS. This counter is used to find out the frequency of inter-cell TCH/Hto-TCH/F incoming handover attempts. It is one of the parameters to measure the wireless environment. 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 966.
Measurement Point
913
Times 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
Number of inter-cell TCH/H-to-TCH/F handover success This counter counts the number of successful inter-cell TCH/H-toTCH/F incoming handover originated by MS. 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. 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 967.
Measurement Point
914
Times 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
Number of inter-cell TCH/H-to-TCH/H handover This counter counts the number of inter-cell TCH/H-to-TCH/H incoming handover originated by MS. This counter is used to find out the frequency of inter-cell TCH/Hto-TCH/H incoming handover attempts. It is one of the parameters to measure the wireless environment. 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 968.
Measurement Point
915
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
Number of inter-cell TCH/H-to-TCH/H handover success This counter counts the number of successful inter-cell TCH/H-toTCH/H incoming handover originated by MS. 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. 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 969.
Measurement Point
916
Times ZGB-02-02-001 Basic Handover ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
Total dual band outgoing handover attempts 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. 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. 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 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 970.
Usage
Measurement Point
917
Unit
Times
Total dual band incoming handover attempts 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. 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. When the target cell receives the channel application request, if the application cause is external incoming handover, and the source cell and the target cell that are at different bands, the counter increments. The measurement point is A, as shown in Figure 971.
Usage
Measurement Point
918
Unit
Times
Number of intra-cell invalid handovers 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. 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. 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 972.
Usage
Measurement Point
919
C901090149 Number of BSC-controlled inter-cell incoming handover attempts due to forced release (emergency service)
Definition Description
Number of BSC-controlled inter-cell incoming handover attempts due to forced release (emergency service) 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. 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. Intra-BSC target cell receives radio channel request to determine whether to do forced release attempt if the request reason is BSCcontrolled inter-cell incoming handover and the target cell has not available radio channel. This counter increments before target cell sends forced release message to forced release instance. The measurement point is A shown in Figure 973.
Usage
Measurement Point
920
Unit
Times
C901090150 Number of BSC-controlled inter-cell incoming handover (forced release) (emergency service)
Definition Description
Number of BSC-controlled inter-cell incoming handover (forced release) (emergency service) 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. 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. 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 974.
Usage
Measurement Point
921
Unit
Times
C901090151 Number of BSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service)
Definition Description
Number of BSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service) This counter counts the number of forced handover attempts due to unavailable radio resource in target cell in the process of BSCcontrolled inter-cell incoming handover initiated by a MS on emergency service. 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. 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 975.
Usage
Measurement Point
922
Unit
Times
C901090152 Number of BSC-controlled inter-cell incoming handover (forced handover) (emergency service)
Definition Description
Number of BSC-controlled inter-cell incoming handover (forced handover) (emergency service) 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. 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. Intra-BSC target cell receives radio channel request and adds it into a queue after sending forced handover message to forced handover instance if the request reason is BSC-controlled inter-cell incoming handover and the target cell has not available radio channel. This counter increments if target cell receives available resource message. The measurement point is A2, as shown in Figure 976.
Usage
Measurement Point
923
Unit
Times
C901090153 Number of BSC-controlled inter-cell incoming handover attempts due to queue (emergency service)
Definition Description
Number of BSC-controlled inter-cell incoming handover attempts due to queue (emergency service) 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. 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. Intra-BSC target cell receives radio channel request to determine whether to do queue if the request reason is BSC-controlled intercell incoming handover and the target cell has not available radio
Usage
Measurement Point
924
channel. This counter increments if target cell adds target instance into a queue. The measurement point is A, as shown in Figure 977.
FIGURE 977 QUEUING ATTEMPTS
Unit
Times
Number of BSC-controlled inter-cell incoming handover (queue) (emergency service) 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. This counter counts the frequency of queue occurred during BSCcontrolled inter-cell incoming handover initiated by a MS. It can reflect the handover process. 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 978.
Usage
Measurement Point
925
Unit
Times
C901090155 Number of MSC-controlled incoming handover attempts due to forced release (emergency service)
Definition Description
Number of MSC-controlled incoming handover attempts due to forced release (emergency service) 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.
926
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. Target cell receives radio channel request to determine whether to do forced release attempt if the request reason is MSC-controlled inter-BSC incoming handover and the target cell has not available radio channel. This counter increments before target cell sends forced release message to forced release instance. The measurement point is A shown in Figure 979.
FIGURE 979 MSC-CONTROLLED FORCED RELEASE ATTEMPT ON INCOMING HANDOVER
Measurement Point
Unit
Times
Number of MSC-controlled incoming handover (forced release) (emergency service) 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. 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. 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 980.
Usage
Measurement Point
927
Unit
Times
C901090157 Number of MSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service)
Definition Description
Number of MSC-controlled inter-cell incoming handover attempts due to forced handover (emergency service) This counter counts the number of forced handover attempts due to unavailable radio resource in target cell in the process of MSCcontrolled inter-BSC incoming handover initiated by a MS on emergency service. 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. 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 981.
Usage
Measurement Point
928
Unit
Times
Number of MSC-controlled incoming handover (forced release) (emergency service) 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. 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. 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 982.
Usage
Measurement Point
929
Unit
Times
C901090159 Number of MSC-controlled incoming handover attempts due to queue (emergency service)
Definition Description
Number of MSC-controlled incoming handover attempts due to queue (emergency service) 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. 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. Target cell receives radio channel request to determine whether to do a queue if the request reason is MSC-controlled inter-BSC incoming handover and the target cell has not available radio channel. This counter increments if target cell adds target instance into a queue. The measurement point is A, as shown in Figure 983.
Usage
Measurement Point
930
Unit
Times
Number of MSC-controlled incoming handover (queue) (emergency service) 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. This counter counts the frequency of queue occurred during BSCcontrolled inter-BSC incoming handover initiated by a MS. It can reflect the handover process. 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 984.
Usage
Measurement Point
931
Unit
Times
C901090161 Number of forced handover target not found (BSC-controlled inter-cell handover due to forced handover)
Definition Description
Number of forced handover target not found (BSC-controlled intercell handover due to forced handover) 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. 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. Intra-BSC target cell receives radio channel request if the request reason is BSC-controlled inter-cell incoming handover and the target cell has not available radio channel. This counter increments if the forced handover target is not found after initiating forced handover attempt. The measurement point is A, as shown inFigure 985.
Usage
Measurement Point
932
FIGURE 985 FORCED HANDOVER TARGET NOT FOUND (BSC-CONTROLLED INTER-CELL HANDOVER DUE TO FORCED HANDOVER)
Unit
Times
C901090162 Number of send forced handover request to lower PRI user (BSC-controlled inter-cell handover due to forced handover)
Definition Description
Number of send forced handover request to lower PRI user (BSC-controlled inter-cell handover due to forced handover) 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. 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. 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
Usage
Measurement Point
933
initiating forced handover attempt. The measurement point is A, as shown in Figure 986.
FIGURE 986 SEND FORCED HANDOVER REQUEST TO LOWER PRI USER (BSC-CONTROLLED INTER-CELL HANDOVER DUE TO FORCED HANDOVER)
Unit
Times
C901090163 Number of recv failure from lower PRI user request resource for forced handover (BSC-controlled 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) 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
Description
934
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. 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 987.
FIGURE 987 RECV FAILURE FROM LOWER PRI USER REQUEST RESOURCE FOR FORCED HANDOVER (BSC-CONTROLLED INTER-CELL HANDOVER DUE TO FORCED HANDOVER)
Measurement Point
Unit
Times
935
C901090164 Number of lower PRI user handover failure (BSC-controlled inter-cell handover due to forced handover)
Definition Description
Number of lower PRI user handover failure (BSC-controlled intercell handover due to forced handover) 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. 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. 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 988.
Usage
Measurement Point
936
FIGURE 988 RECV FAILURE FROM LOWER PRI USER REQUEST RESOURCE FOR FORCED HANDOVER (BSC-CONTROLLED INTER-CELL HANDOVER DUE TO FORCED HANDOVER)
Unit
Times
C901090165 Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced handover)
Definition Description
Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced handover) 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. 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.
Usage
937
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 989.
FIGURE 989 - HIGH PRI USER TIME OUT FOR WAIT RESOURCE (BSC-CONTROLLED INTER-CELL HANDOVER DUE TO FORCED HANDOVER)
Unit
Times
C901090166 Number of forced release target not found (BSC-controlled inter-cell handover due to forced release)
Definition Description
Number of forced release target not found (BSC-controlled intercell handover due to forced release) 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.
938
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. 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 990.
FIGURE 990 FORCED RELEASE TARGET NOT FOUND (BSC-CONTROLLED INTER-CELL HANDOVER DUE TO FORCED RELEASE)
Measurement Point
Unit
Times
C901090167 Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced release)
Definition Description
Number of high PRI user time out for wait resource (BSC-controlled inter-cell handover due to forced release) 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. This counter counts the frequency of timeout for waiting resource while initiating forced release during BSC-controlled inter-cell in-
Usage
939
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 991.
FIGURE 991 HIGH PRI USER TIME OUT FOR WAIT RESOURCE (BSC-CONTROLLED INTER-CELL HANDOVER DUE TO FORCED RELEASE)
Unit
Times
C901090168 Number of HO Target not found (MSC-controlled incoming handover due to forced handover)
Definition Description
Number of HO Target not found (MSC-controlled incoming handover due to forced handover) This counter counts the number of HO Target not found (MSCcontrolled incoming handover due to forced handover)
940
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. 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.
Measurement Point
Unit
Times
C901090169 Number of send forced handover request to lower PRI user (MSC-controlled incoming handover due to forced handover)
Definition Description
Number of send forced handover request to lower PRI user (MSC-controlled incoming handover due to forced handover) This counter counts the number of sending forced handover request to lower PRI user (MSC-controlled incoming handover due to forced handover). 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. 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.
Usage
Measurement Point
Unit
Times
941
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) This counter counts the number of failure to lower PRI user request resource for forced handover (MSC-controlled incoming handover due to forced handover). 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. This counter increments if BSC receives forced handover failure and incoming handover fails due to failure of resource request. Times
Description
Usage
C901090171 Number of lower PRI user handover failure (MSC-controlled incoming handover due to forced handover)
Definition Description
Number of lower PRI user handover failure (MSC-controlled incoming handover due to forced handover) This counter counts the number of handover failure to lower PRI user for forced handover (MSC-controlled incoming handover due to forced handover). 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.
Usage
942
This counter increments if BSC receives forced handover failure and incoming handover fails due to failure of forced handover. Times
C901090172 Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced handover)
Definition Description
Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced handover) This counter counts the number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced handover). 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. This counter increments if the timer of waiting for resource after initiating forced handover. Times
Usage
C901090173 Number of forced release target not found (MSC-controlled incoming handover due to forced release)
Definition Description
Number of forced release target not found (MSC-controlled incoming handover due to forced release) This counter counts the number of forced release target not found (MSC-controlled incoming handover due to forced handover).
943
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. 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.
Measurement Point
Unit
Times
C901090174 Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced release)
Definition Description
Number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced release) This counter counts the number of high PRI user time out for wait resource (MSC-controlled incoming handover due to forced release). 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. This counter increments if the timer of waiting for resource is timeout after initiating forced release. Times
Usage
944
C901090175 Number of get before grab released channel (assignment forced handover)
Definition Description Usage
Number of get before grab released channel (assignment forced handover) This counter counts the number of getting previous grab released channel (assignment forced handover). This counter counts the frequency of getting the channel released by grabbing on forced handover. It is one of parameters to measure radio environment. This counter increments if BSC receives effective messages in resource message on forced handover and the messages hold database resource. Times
C901090176 Number of get before grab released channel (assignment forced release)
Definition Description Usage
Number of get before grab released channel (assignment forced release) This counter counts the number of getting previous grab released channel (assignment forced release). This counter counts the frequency of getting the channel released by grabbing on forced release. It is one of parameters to measure radio environment. This counter increments if BSC receives effective messages in resource message on forced release and the messages hold database resource. Times
945
Number of handover attempts due to eMLPP forced handover This counter counts the number of handover attempts due to eMLPP forced handover. This counter counts the frequency of handover attempts due to eMLPP forced handover. It is one of parameters to measure radio environment. This counter increments if it is forced handover on intra-cell handover. This counter increments if it is forced handover based on hierarchy and frequency relationship on BSC-controlled inter-cell or MSCcontrolled outgoing handover.
Measurement Point
Unit
Times
Number of handover due to eMLPP forced handover This counter counts the number of handover due to eMLPP forced handover. This counter counts the frequency of handover due to eMLPP forced handover. It is one of parameters to measure radio environment. 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
946
Number of handover success due to eMLPP forced handover This counter counts the number of handover success due to eMLPP forced handover. This counter counts the frequency of handover success due to eMLPP forced handover. It is one of parameters to measure radio environment. 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.
Measurement Point
Unit
Times
947
C901090184 Number of MSC-controlled outgoing handover request fail between PLMN due to unknown reason
This counter is not used for the time being.
948
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. 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. 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 992.
Usage
Measurement Point
Unit
Times
949
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.
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. This counter is used to find out the frequency of failure of MSCcontrolled inter-PLMN outgoing handover request initiated by MS due to other reasons. It also helps study the condition of handover initiated by MSC. This counter is supported in version V6.20.200a or above. When MSC receives the handover request rejection message from BSC, it queries the rejection cause. If the rejection cause is not CAUSE_REQ_CIC_UNAVAIL or CAUSE_NO_RR_AVAIL, then the counter counts. Times
Usage
Measurement Point
Unit
950
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. 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. 1. When BSC receives the command Clear Cmd from A-interface, if the cause in this command is CAUSE_HO_SUCCESSFUL, then the counter counts. 2. The counter counts when BSC fails to wait for the handover response message returned from MS. The measurement point is shown in Figure 993.
Usage
Measurement Point
3. When the timer THoOutgo is timeout, if there is no abnormal release, the counter counts. The measurement point is shown in Figure 994.
951
AND
NO ABNORMAL
Unit
Times
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. This counter is used to find out the number of successful MSCcontrolled inter-PLMN outgoing handovers. It also helps study the handover initiated by MSC. This counter is supported in version V6.20.200a or above. When BSC receives the command Clear Cmd from MSC, the timer THOOUTGO is timeout. If the cause in the command Clear Cmd is CAUSE_HO_SUCCESSFUL, then the counter counts. Times
Usage
952
C901090192 Number of BSC-controlled inter-cell incoming handover force-release attempt between PLMN
This counter is not used for the time being.
953
C901090193 Number of BSC-controlled inter-cell incoming handover between PLMN due to force release
This counter is not used for the time being.
C901090194 Number of BSC-controlled inter-cell incoming handover queue attempt between PLMN
This counter is not used for the time being.
C901090195 Number of BSC-controlled inter-cell incoming handover between PLMN due to queue
This counter is not used for the time being.
954
C901090196 Number of BSC-controlled inter-cell incoming handover force-handover attempt between PLMN
This counter is not used for the time being.
C901090197 Number of BSC-controlled inter-cell incoming handover between PLMN due to force handover
This counter is not used for the time being.
955
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. 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. 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 995.
FIGURE 995 MSC-CONTROLLED INTER-PLMN INCOMING HANDOVER FLOW
Usage
Measurement Point
Unit
Times
956
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. This counter is used to find out the number of A-interface interPLMN incoming handover failures due to circuit's being blocked. It also helps study the handover initiated by MSC. This counter is supported in version V6.20.200a or above. 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 996.
Usage
Measurement Point
Unit
Times
957
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 interPLMN handover, then the counter increments. This counter is used to find out the number of A-interface interPLMN incoming handover failures due to circuit mismatching. It also helps study the handover initiated by MSC. This counter is supported in version V6.20.200a or above. When MSC receives the Handover Failure message, if the handover failiure cause in this message is CAUSE_CIRCUIT_POOL_MISMATCH and the handover is inter-PLMN handover, then the counter counts. Times
Usage
Measurement Point
Unit
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. 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. 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
Usage
Measurement Point
958
Times
C901090203 A interface incoming handover fail between PLMN due to other reason
This counter is not used for the time being.
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. This counter is used to find out the number of attempts of MSCcontrolled inter-PLMN incoming handover force-release. It also helps study the inter-PLMN incoming handover force-release initiated by MSC. This counter is supported in version V6.20.200a or above.
Usage
959
When BSC receives the command HoReq from MSC, if no radio resource is available and forced release is allowed, then the counter counts. Times
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. 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. When BSC receives the command HoReq from MSC, if the CS instance carries the RADIO_AVAILABLE message and forced release is allowed, then the counter counts. Times
Usage
This counter counts the number of attempts of MSC-controlled inter-PLMN incoming handover queuing. When BSC receives the command Ho Req from MSC, it sends the command Chan Act to BTS. If channel requests fails but queuing is allowed, the counter increments. This counter is used to find out the number of attempts of MSC-controlled inter-PLMN incoming handover queuing. It also
Usage
960
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 997.
FIGURE 997 INTER-MSC HANDOVER
Unit
Times
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. 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. 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.
Usage
Measurement Point
961
Unit
Times
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. This counter is used to find out the number of attempts of MSCcontrolled inter-PLMN incoming handover force-handover. It also helps study the inter-PLMN incoming handover, which is initiated by MSC, in case of no channel resource. This counter is supported in version V6.20.200a or above. When BSC receives the command Ho Req from MSC, it sends the command Chan Act to BTS. If no channel request fails but forced handover is allowed, then the counter counts. Times
Usage
C901090210 Number of MSC-controlled incoming handover between PLMN due to force handover
This counter is not used for the time being.
962
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. 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. When Rancs receives the CS service migration sent from DBS, if byCsMoveCause == HR_DEFRAG, then the counter counts. Times
Usage
This counter counts the number of successful handovers due to HR fragment reorganization in the cell. When BSC receives the CS service migration command from DBS, it sends the command Chan Act to BTS. After the command Chan Act Ack is received, if byCsMoveCause == HR_DEFRAG, then the counter increments. 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.
Usage
963
Measurement Point
When BSC receives the CS service migration command from DBS, it sends the command Chan Act to BTS. After the command Chan Act Ack is received, if the assignment at Um interface succeeds and byCsMoveCause == HR_DEFRAG, then the counter counts. The measurement point is A1, as shown in Figure 998.
FIGURE 998 HANDOVER SUCCESS
DUE TO
CS SERVICE MIGRATION
Unit
Times
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 999.
964
Times Cell
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 1000.
FIGURE 1000 INTRA-CELL HANDOVER FLOW
Times
965
Statistics Object
Cell
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 1001.
FIGURE 1001 INTRA-CELL HANDOVER FLOW
Times Cell
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 1002.
966
Times Cell
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 1003.
FIGURE 1003 INTRA-CELL HANDOVER FLOW
Times
967
Statistics Object
Cell
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 1004.
FIGURE 1004 INTRA-CELL HANDOVER FLOW
Times Cell
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 intracell handover from AMR HR to AMR FR is reached, the intra-cell handover attempt from AMR HR to AMR FR is initiated, and the counter increments. The measurement point is A1, as shown in Figure 1005.
968
Times Cell
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 1006.
FIGURE 1006 INTRA-CELL HANDOVER FLOW
Times
969
Statistics Object
Cell
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 1007.
FIGURE 1007 INTRA-CELL HANDOVER FLOW
Times Cell
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 1008.
970
Times Cell
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 1009.
FIGURE 1009 INTRA-CELL HANDOVER FLOW
Times
971
Statistics Object
Cell
When the intra-cell handover from HR to FR is caused due to bad quality, if the MS successfully performs handover to the new channel and the handover completion message is sent, the counter increments. The measurement point is A3, as shown in Figure 1010.
FIGURE 1010 INTRA-CELL HANDOVER FLOW
Times Cell
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 1011.
972
Times Cell
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 1012.
973
Times Cell
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 1013.
974
Times Cell
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 1014.
975
Times Cell
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 1015.
976
Times Cell
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 1016.
977
Times Cell
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 1017.
978
Times Cell
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 1018.
979
Times Cell
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 1019.
980
Times Cell
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 1020.
981
Times Cell
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 1021.
982
Times Cell
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 1022.
983
Times Cell
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 1023.
984
Times Cell
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 1024.
FIGURE 1024 INTER-BSC INTER-CELL HANDOVER FLOW
985
Times Cell
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 1025.
FIGURE 1025 INTER-BSC INTER-CELL HANDOVER FLOW
Times
986
Statistics Object
Cell
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 1026.
FIGURE 1026 INTER-BSC INTER-CELL HANDOVER FLOW
Times
987
Statistics Object
Cell
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 1027.
FIGURE 1027 INTER-BSC INTER-CELL HANDOVER FLOW
Times
988
Statistics Object
Cell
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 1028.
FIGURE 1028 INTER-BSC INTER-CELL HANDOVER FLOW
Times
989
Statistics Object
Cell
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 1029.
FIGURE 1029 INTER-BSC INTER-CELL HANDOVER FLOW
Times Cell
During the process of inter-BSC inter-cell handover, the source BSC receives the HANDOVER COMMAND message from MSC. If
990
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 1030.
FIGURE 1030 INTER-BSC INTER-CELL HANDOVER FLOW
Times Cell
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 1031.
991
Times Cell
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 1032.
FIGURE 1032 INTER-BSC INTER-CELL HANDOVER FLOW
992
Times Cell
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 1033.
FIGURE 1033 INTER-BSC INTER-CELL HANDOVER FLOW
Times
993
Statistics Object
Cell
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 1034.
FIGURE 1034 INTER-BSC INTER-CELL HANDOVER FLOW
Times Cell
994
Chapter
16
995
Overview
Adjacent cell handover counter is used to record the number of outgoing handover or incoming handover so as to find out the handover between the cell and its adjacent cell which lays a basis for configuration of adjacent cell and improves service quality of the cell through handover. The measurement takes cell as the statistics unit.
Number of handover attempts on the adjacent cell. This counter counts the number of attempts of handover from the selected cell to the adjacent cell. 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. 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 1035.
FIGURE 1035 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER ATTEMPT
Measurement Point
When external handover happens inside one MSC, and source cell sends handover request message to MSC, the counter increments. The measurement point is A, as shown in Figure 1036.
996
C901100002 Number of handover success from selected cell to the adjacent cell.
Definition Usage
This counter counts the number of success of handover from the selected cell to the adjacent cell. 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. 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 1037.
Measurement Point
997
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 1038.
FIGURE 1038 SUCCESSFUL MSC-CONTROLLED OUTGOING HANDOVER
C901100003 Number of handover attempts from adjacent cell to the selected cell.
Definition
998
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. 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 1039.
FIGURE 1039 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Measurement Point
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 1040.
FIGURE 1040 MSC-CONTROLLED INCOMING HANDOVER ATTEMPTS
999
C901100004 Number of handover success from adjacent cell to the selected cell.
Definition Usage
This counter counts the number of successful handover from the adjacent cell to the selected cell. 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. 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 1041.
FIGURE 1041 SUCCESSFUL BSC-CONTROLLED INTER-CELL INCOMING HANDOVER
Measurement Point
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 1042.
FIGURE 1042 MSC-CONTROLLED INCOMING HANDOVER SUCCESS
1000
C901100005 Number of handover attempts from selected cell to the adjacent cell due to better UL quality.
Definition Usage
Number of handover attempts from selected cell to the adjacent cell due to better UL quality 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. 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 1043.
FIGURE 1043 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Measurement Point
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 1044.
1001
C901100006 Number of handover attempts from selected cell to the adjacent cell due to better DL quality.
Definition Usage
Number of handover attempts from selected cell to the adjacent cell due to better DL quality 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. 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 1045.
Measurement Point
1002
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 1046.
FIGURE 1046 MSC-CONTROLLED INCOMING HANDOVER ATTEMPTS
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.
1003
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. 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 1047.
FIGURE 1047 SUCCESSFUL BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER
Measurement Point
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 1048.
FIGURE 1048 SUCCESSFUL MSC-CONTROLLED OUTGOING HANDOVER
1004
C901100008 Number of handover success from selected cell to the adjacent cell due to better DL quality.
Definition Usage
Number of handover success from selected cell to the adjacent cell due to better DL quality 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. 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 1049.
FIGURE 1049 SUCCESSFUL BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER
Measurement Point
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 1050.
1005
C901100009 Number of handover attempts from selected cell to the adjacent cell due to better UL strength.
Definition Usage
Number of handover attempts from selected cell to the adjacent cell due to better UL strength. 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. 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 1051.
Measurement Point
1006
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 1052
FIGURE 1052 MSC-CONTROLLED INCOMING HANDOVER ATTEMPTS
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.
1007
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. 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 1053.
FIGURE 1053 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Measurement Point
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 1054.
FIGURE 1054 MSC-CONTROLLED INCOMING HANDOVER ATTEMPTS
1008
C901100011 Number of handover success from selected cell to the adjacent cell due to better UL strength.
Definition Usage
Number of successful handover from selected cell to the adjacent cell due to better UL strength 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. 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 1055.
FIGURE 1055 SUCCESSFUL BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER
Measurement Point
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 1056.
1009
C901100012 Number of handover success from selected cell to the adjacent cell due to better DL strength.
Definition Usage
Number of successful handover from the selected cell to the adjacent cell due to better DL strength 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. 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 1057.
Measurement Point
1010
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 1058.
FIGURE 1058 SUCCESSFUL MSC-CONTROLLED OUTGOING HANDOVER
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
1011
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. 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 1059.
FIGURE 1059 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPTS
Measurement Point
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 1060.
FIGURE 1060 MSC-CONTROLLED INCOMING HANDOVER ATTEMPTS
1012
C901100014 Number of handover success from selected cell to the adjacent cell due to PBGT
Definition Usage
Number of handover success from selected cell to the adjacent cell due to better PBGT 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. 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 1061.
FIGURE 1061 SUCCESSFUL BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER
Measurement Point
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 1062.
1013
C901100015 Number of handover attempts from selected cell to the adjacent cell due to other factors.
Definition Usage
Number of handover attempts from the selected cell to the adjacent cell due to other factors. 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. 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 1063.
Measurement Point
1014
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 1064.
FIGURE 1064 MSC-CONTROLLED INCOMING HANDOVER ATTEMPTS
Unit
Times
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
1015
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. 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 1065.
FIGURE 1065 SUCCESSFUL BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER
Measurement Point
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 1066.
FIGURE 1066 SUCCESSFUL MSC-CONTROLLED OUTGOING HANDOVER
Unit
Times
1016
Number of pingpong handover (handover to source cell) 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. This counter is used to find out the number of MS's attempting pingpong handover due to network coverage problems or inappropriate parameter setting. For BSC-controlled inter-cell handover, the counter increments when the source cell sends the radio channel request message to the destination cell. The measurement point is A, as shown in Figure 1067.
FIGURE 1067 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER ATTEMPT
Usage
Measurement Point
For MSC-controlled external handover, the counter increments when the souce cell sends the handover request message to MSC. The measurement point is A, as shown in Figure 1068.
1017
Unit
Times
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. This counter is used to find out the maximum reference time difference between two cells. This counter is supported in version V6.20.210a or above. When BSC receives the Assign Complete message, if it contains the mobile time difference, then the counter counts. The measurement point is A1, as shown in Figure 1069.
Usage
Measurement Point
1018
Unit
Second
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. 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. When BSC receives the Assign Complete message from MS, if it contains the mobile time difference, then the counter counts. Times
Usage
1019
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. 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. When BSC receives the Assign Complete message from MS, if it contains the mobile time difference, then the counter counts. Times
Usage
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. For BSC-controlled inter-cell handover, the counter increments when the source cell sends the radio channel request message to the destination cell. The measurement point is A, as shown in Figure 1070. For MSC-controlled external handover, the counter increments when the source cell sends the handover request message to MSC. The measurement point is A, as shown in Figure 1071.
1020
Times
1021
Statistics Object
Cell
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. 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 1072. 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 1073.
OF
OF
1022
Times Cell
1023
1024
Chapter
17
1025
C901110031 Number of wireless access due to call re-establishments ..................................................................... 1037 C901110032 Number of wireless accesses due to IMSI detachment ..................................................................... 1038 C901110033 Number of wireless accesses due to other causes ......................................................................... 1038 C901110034 Number of access due to Notification response ......................................................................... 1039 C901110035 Number of access due to Immediate setup ........................................................................... 1040 C901110036 Number of access due to Talker indication ............................................................................. 1041 C901110037 Number of access due to DATA Indication......... 1042 C901110038 Number of access due to priority uplink request ........................................................................... 1043 C901110039 Number of access of CM service request of VGCS........................................................................... 1044 C901110040 Number of access of CM service request of VBS ............................................................................. 1045
Overview
Radio access counter is mainly used to observe MS radio random access process as the reference of radio access parameter adjustment, signaling channel allocation strategy, etc. Several possible causes of radio access are listed here. Access statistics related to GPRS is not listed here but in the category of other access request temporarily. The number of access request is that of receiving Channel Required message; the number of successful access process is that of sending Immediate Assignment message. The slot-aloha protocol used in radio access allows many access requests in one access. We can use the percentage of the number of successful access process to the number of access request to describe access success rate. This value represents signaling channel congestion extent. The percentage of the number of successful access to the number of access request represents the collision status in radio access request. If this value is low, we shall consider factors such as the interval between access requests, and check whether it is reasonable. The measurement takes cell as the statistics unit. Radio access flow and related counters locations are shown in Figure 1074.
1026
Number of invalid access requests 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. This counter is used to find out the frequency of invalid access request. 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 . Times
1027
Description
This counter counts the Number of MOC access success for processes. The counter increments when BSC allows MS to be accessed into the network due to MOC attempts and accepts channel request sent by MS and allocates and activates channel successfully. Meanwhile, BSC sends message IMM_ASS to MS. This counter is used to find out the frequency of successful random access processes due to MOC attempts. The counter increments when channel is activated successfully. The measurement point is A3, as shown in Figure Radio Access Process . Times
Number of MTC access success for processes 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. This counter is used to find out the frequency of successful random access processes due to MTC attempts. The counter increments when channel is activated successfully. The measurement point is A3, as shown in Figure Radio Access Process. Times
Number of call re-establishment access attempts 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. This counter is used to find out the frequency of random access attempts due to call re-establishment.
Usage
1028
The counter increments when MS requires channel from BSC and TA does not exceed the scope. The measurement point is A1, as shown in Figure Radio Access Process. Times
Number of call re-establishment access success for processes This counter counts the Number of call re-establishment access success for processes. The counter increments when BSC allows MS to be accessed into the network due to call re-establishment and accepts channel request sent by MS and allocates and activates channel successfully. Meanwhile, BSC sends IMM_ASS message to MS. This counter is used to find out the frequency of random access processes due to call re-establishment. The counter increments when channel is activated successfully. The measurement point is A3, as shown in Figure Radio Access Process. Times
Number of call re-establishment access success. 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. This counter is used to find out the frequency of successful access of call re-establishment. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times
1029
Number of emergency calls access attempts 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. This counter is used to find out the frequency of random access attempts due to emergency calls. The counter increments when MS requires channel from BSC and TA does not exceed the scope. The measurement point is A1, as shown in Figure Radio Access Process. Times ZGB-01-03-001 Emergency Call Handling
Number of emergency calls access success for processes 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. This counter is used to find out the frequency of random access processes due to emergency calls. The counter increments when channel is activated successfully. The measurement point is A3, as shown in Figure Radio Access Process. Times ZGB-01-03-001 Emergency Call Handling
1030
Number of emergency calls access success 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. This counter is used to find out the frequency of successful access of emergency calls. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times ZGB-01-03-001 Emergency Call Handling
Number of LOC access attempts 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. This counter is used to find out the frequency of random access attempts due to LOC. The counter increments when MS requires channel from BSC and TA does not exceed the scope. The measurement point is A1, as shown in Figure Radio Access Process. Times
1031
Description
This counter counts the number of successful random access processes due to LOC. The counter increments when BSC allows MS to be accessed into the network due to emergency calls and accepts channel request sent by MS and allocates and activates channel successfully. Meanwhile, BSC sends IMM_ASS message to MS. This counter is used to find out the frequency of random access processes due to LOC. The counter increments when channel is activated successfully. The measurement point is A3, as shown in Figure Radio Access Process. Times
Number of LOC access success 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. This counter is used to find out the frequency of LOC access success. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times
Number of other causes access attempts 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. This counter is used to find out the frequency of random access attempts due to other causes. 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.
1032
Unit
Times
Number of successful random access processes for other causes 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. This counter is used to find out the frequency of random access processes due to other causes. The counter increments when channel is activated successfully. The measurement point is A3, as shown in Figure Radio Access Process. Times
Number of other causes access success 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. This counter is used to find out the frequency of other successful access requests. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times
1033
Number of LMU Establishment Access attempts 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. This counter is used to find out the frequency of LMU establishment access request. The counter increments when MS requires channel from BSC and TA does not exceed the scope. The measurement point is A1, as shown in Figure Radio Access Process. Times
Number of LMU Establishment access success for processes 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. This counter is used to find out the frequency of LMU establishment access request successfully. The counter increments when channel is activated successfully. The measurement point is A3, as shown in Figure Radio Access Process. Times
1034
Number of LMU Establishment access success 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. This counter is used to find out the frequency of LMU establishment access successfully. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times
Number of wireless accesses due to location update 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. This counter is used to find out the frequency of radio channel accesses due to location update. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times
1035
Description
This counter counts the Number of Access due to CM SERVICE REQ. The counter increments when the access cause in Layer3 information carried in EST_IND message received by BSC is CM SERVICE REQ. This counter is used to find out the frequency of access caused by CM SERVICE REQ. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times
Number of access of CM SERVICE REQ's emergency call 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. This counter is used to find out the frequency of access of CM SERVICE REQ's emergency call. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times ZGB-01-03-001 Emergency Call Handling
Number of access of SMS's CM SERVICE REQ 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. This counter is used to find out the frequency of access of SMS's CM SERVICE REQ. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times
1036
Number of access of supplement's CM SERVICE REQ 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. This counter is used to find out the frequency of access of supplement's CM SERVICE REQ. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times
Number of access of LCS's CM SERVICE REQ 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. This counter is used to find out the frequency of access of LCS's CM SERVICE REQ. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times
Number of wireless accesses due to call re-establishments This counter counts the Number of wireless accesses due to call re-establishments. The counter increments when the access cause
1037
This counter is used to find out the frequency of radio channel accesses due to call re-establishments. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times
Number of wireless accesses due to IMSI detachment 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. This counter is used to find out the frequency of radio channel accesses due to IMSI detachment. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times
Number of wireless accesses due to other causes 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. This counter is used to find out the frequency of radio channel accesses due to other causes. The counter increments when BSC receives EST_IND message. The measurement point is A4, as shown in Figure Radio Access Process. Times
1038
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 1075.
FIGURE 1075 RADIO ACCESS PROCESS
Times
1039
Statistics Object
Cell
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 1076.
FIGURE 1076 RADIO ACCESS PROCESS
Times
1040
Statistics Object
Cell
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 1077.
FIGURE 1077 RADIO ACCESS PROCESS
Times
1041
Statistics Object
Cell
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 1078.
FIGURE 1078 RADIO ACCESS PROCESS
Times
1042
Statistics Object
Cell
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 1079.
FIGURE 1079 RADIO ACCESS PROCESS
Times
1043
Statistics Object
Cell
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 1080.
FIGURE 1080 RADIO ACCESS PROCESS
Times
1044
Statistics Object
Cell
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 1081.
FIGURE 1081 RADIO ACCESS PROCESS
Times Cell
1045
1046
Chapter
18
Radio Measurement
Table of Contents Overview...................................................................... 1050 C901120001 Number of UL signal quality samples in wireless channels ...................................................................... 1051 C901120002 Level of worst UL signal quality in wireless channels ............................................................................. 1051 C901120003 Total value of UL quality level values in wireless channels ...................................................................... 1052 C901120004 Number of DL signal quality samples in wireless channels ...................................................................... 1052 C901120005 Level of worst DL signal quality in wireless channels ............................................................................. 1052 C901120006 Total value of DL quality strength values in wireless channels ................................................................ 1053 C901120007 Number of received UL signal strength samples in wireless channels ....................................................... 1053 C901120008 Maximum received UL signal strength in wireless channels ...................................................................... 1054 C901120009 Minimum received UL signal strength in wireless channels ...................................................................... 1054 C901120010 Total value of UL signal strength in wireless channels ...................................................................... 1055 C901120011 Number of received DL signal strength samples in wireless channels ....................................................... 1055 C901120012 Maximum received DL signal strength in wireless channels ...................................................................... 1055 C901120013 Minimum DL received signal strength in radio channels ...................................................................... 1056 C901120014 Total value of DL signal strength in wireless channels ...................................................................... 1056 C901120015 Number of TA samples in wireless channels ............................................................................. 1057 C901120016 Maximum TA in wireless channels.................. 1057 C901120017 Total number of TAs in wireless channels......... 1058 C901120018 Mean number of idle TCH/Fs with interference band 0 ......................................................................... 1058 C901120024 Mean number of idle TCH/Hs with interference band 0 ......................................................................... 1058 C901120030 Mean number of idle SDCCHs with interference band 0 ......................................................................... 1059 C901120031 Mean number of idle SDCCHs with interference band 1 ......................................................................... 1059 C901120032 Mean number of idle SDCCHs with interference band 2 ......................................................................... 1060 C901120033 Mean number of idle SDCCHs with interference band 3 ......................................................................... 1060
1047
C901120034 Mean number of idle SDCCHs with interference band 4 ......................................................................... 1060 C901120035 Mean number of idle SDCCHs with interference band 5 ......................................................................... 1061 C901120052 Number of TFO initiations............................. 1061 C901120053 Number of using noise suppression ............... 1061 C901120054 Number of mode changes for establishing TFO ............................................................................. 1062 C901120055 Number of mode changes for optimizing TFO ............................................................................. 1062 C901120056 Number of active collection changes for establishing TFO ................................................................... 1062 C901120057 Number of active collection changes for optimizing TFO ........................................................................ 1063 C901120058 Number of samples with voice quality is excellent ............................................................................. 1063 C901120059 Number of samples with voice quality is good............................................................................ 1063 C901120060 Number of samples with voice quality is medium ....................................................................... 1064 C901120061 Number of samples with voice quality is bad ............................................................................. 1064 C901120062 Number of samples with voice quality is awfully............................................................................. 1065 C901120063 Number of uplink error frame on FR_V1 ......... 1065 C901120064 Total Number of uplink frame on FR_V1 ......... 1065 C901120065 Number of uplink error frame on FR_V2 ......... 1066 C901120066 Total Number of uplink frame on FR_V2 ......... 1066 C901120067 Number of uplink error frame on FR_V3 ......... 1066 C901120068 Total Number of uplink frame on FR_V3 ......... 1067 C901120069 Number of uplink error frame on HR_V1......... 1067 C901120070 Total Number of uplink frame on HR_V1 ......... 1067 C901120071 Number of uplink error frame on HR_V3......... 1067 C901120072 Total Number of uplink frame on HR_V3 ......... 1068 C901120073 Number of UL signal quality samples in radio channels on SDCCH ....................................................... 1068 C901120074 Level of worst UL signal quality in radio channels on SDCCH .................................................................... 1068 C901120075 Total value of UL quality level values in radio channels on SDCCH ....................................................... 1069 C901120076 Number of DL signal quality samples in radio channels on SDCCH ....................................................... 1069 C901120077 Level of worst DL signal quality in radio channels on SDCCH .................................................................... 1070 C901120078 Total value of DL quality strength values in radio channels on SDCCH ....................................................... 1070 C901120079 Number of received UL signal strength samples in radio channels on SDCCH ............................................ 1071 C901120080 Maximum received UL signal strength in radio channels on SDCCH ....................................................... 1071 C901120081 Minimum received UL signal strength in radio channels on SDCCH ....................................................... 1072 C901120082 Total value of UL signal strength in radio channels on SDCCH.............................................................. 1072 C901120083 Number of received DL signal strength samples in radio channels on SDCCH ............................................ 1073 C901120084 Maximum received DL signal strength in radio channels on SDCCH ....................................................... 1073 C901120085 Minimum DL received signal strength in radio channels on SDCCH ....................................................... 1074
1048
C901120086 Total value of DL signal strength in radio channels on SDCCH.............................................................. 1074 C901120087 Number of UL signal quality samples in radio channels on TCH ........................................................... 1075 C901120088 Level of worst UL signal quality in radio channels on TCH......................................................................... 1075 C901120089 Total value of UL quality level values in radio channels on TCH ........................................................... 1076 C901120090 Number of DL signal quality samples in radio channels on TCH ........................................................... 1076 C901120091 Level of worst DL signal quality in radio channels on TCH......................................................................... 1076 C901120092 Total value of DL quality strength values in radio channels on TCH ........................................................... 1077 C901120093 Number of received UL signal strength samples in radio channels on TCH ................................................ 1077 C901120094 Maximum received UL signal strength in radio channels on TCH ........................................................... 1078 C901120095 Minimum received UL signal strength in radio channels on TCH ........................................................... 1078 C901120096 Total value of UL signal strength in radio channels on TCH .................................................................. 1079 C901120097 Number of received DL signal strength samples in radio channels on TCH ................................................ 1079 C901120098 Maximum received DL signal strength in radio channels on TCH ........................................................... 1080 C901120099 Minimum DL received signal strength in radio channels on TCH ........................................................... 1080 C901120100 Total value of DL signal strength in radio channels on TCH .................................................................. 1081 C901120101 Number of samples with UL RQ = 0 on SDCCH............................................................................. 1081 C901120102 Number of samples with UL RQ = 1 on SDCCH............................................................................. 1082 C901120103 Number of samples with UL RQ = 2 on SDCCH............................................................................. 1083 C901120104 Number of samples with UL RQ = 3 on SDCCH............................................................................. 1083 C901120105 Number of samples with UL RQ = 4 on SDCCH............................................................................. 1084 C901120106 Number of samples with UL RQ = 5 on SDCCH............................................................................. 1085 C901120107 Number of samples with UL RQ = 6 on SDCCH............................................................................. 1085 C901120108 Number of samples with UL RQ = 7 on SDCCH............................................................................. 1086 C901120109 Number of samples with DL RQ = 0 on SDCCH............................................................................. 1086 C901120110 Number of samples with DL RQ = 1 on SDCCH............................................................................. 1087 C901120111 Number of samples with DL RQ = 2 on SDCCH............................................................................. 1088 C901120112 Number of samples with DL RQ = 3 on SDCCH............................................................................. 1088 C901120113 Number of samples with DL RQ = 4 on SDCCH............................................................................. 1089 C901120114 Number of samples with DL RQ = 5 on SDCCH............................................................................. 1090 C901120115 Number of samples with DL RQ = 6 on SDCCH............................................................................. 1090
1049
C901120116 Number of samples with DL RQ = 7 on SDCCH............................................................................. 1091 C901120117 Number of samples with UL RQ = 0 on TCH ............................................................................. 1092 C901120118 Number of samples with UL RQ = 1 on TCH ............................................................................. 1092 C901120119 Number of samples with UL RQ = 2 on TCH ............................................................................. 1093 C901120120 Number of samples with UL RQ = 3 on TCH ............................................................................. 1094 C901120121 Number of samples with UL RQ = 4 on TCH ............................................................................. 1094 C901120122 Number of samples with UL RQ = 5 on TCH ............................................................................. 1095 C901120123 Number of samples with UL RQ = 6 on TCH ............................................................................. 1096 C901120124 Number of samples with UL RQ = 7 on TCH ............................................................................. 1096 C901120125 Number of samples with DL RQ = 0 on TCH ............................................................................. 1097 C901120126 Number of samples with DL RQ = 1 on TCH ............................................................................. 1097 C901120127 Number of samples with DL RQ = 2 on TCH ............................................................................. 1098 C901120128 Number of samples with DL RQ = 3 on TCH ............................................................................. 1099 C901120129 Number of samples with DL RQ = 4 on TCH ............................................................................. 1099 C901120130 Number of samples with DL RQ = 5 on TCH ............................................................................. 1100 C901120131 Number of samples with DL RQ = 6 on TCH ............................................................................. 1101 C901120132 Number of samples with DL RQ = 7 on TCH ............................................................................. 1101
Overview
Cell radio measurement items mainly include UL/DL quality, signal strength, TA, interference band and RQ value of radio channels. The UL/DL quality, signal strength, TA and RQ value are counted after measurement report or pre-processing measurement report sent by BTS is received; BSC updates interference band status in database after receiving measurement report or pre-processing measurement report. The value of interference band can be inquired in database when periodical measurement is reported. The measurement takes cell as the statistics unit.
1050
Number of UL signal quality samples in radio channels 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. This counter is used to find out the frequency of UL signal quality samples in radio channels. The counter increments when BSC receives UL measurement report or pre-processing measurement report. Times
Level of worst UL signal quality in radio channels 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. This counter is used to find out status of the level of the worst UL signal quality in radio channels. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
1051
Total value of UL quality level values in radio channels 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. This counter is used to find out status of total value of UL quality level values in radio channels. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
Number of DL signal quality samples in radio channels 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. This counter is used to find out the frequency of DL signal quality samples in radio channels. The counter increments when BSC receives DL measurement report or pre-processing measurement report. Times
1052
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. This counter is used to find out status of the level of the worst DL signal quality in radio channels. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
Total value of DL quality level values in radio channels 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. This counter is used to find out status of total value of DL quality level values in radio channels. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
Number of received UL signal strength samples in radio channels 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. This counter is used to find out frequency of received UL signal strength samples in radio channels.
Usage
1053
The counter increments when BSC receives UL measurement report or pre-processing measurement report. Times
Maximum received UL signal strength in radio channels 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. This counter is used to find out status of maximum received UL signal strength in radio channels. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
Minimum received UL signal strength in radio channels 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. This counter is used to find out status of minimum received UL signal strength in radio channels. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
1054
Total value of UL signal strength in radio channels This counter counts the number of total value of UL signal strength in radio channels in radio measurement reports. The counter accumulates values of UL signal strength in radio channels in UL measurement report or pre-processing measurement report received by BSC. This counter is used to find out status of total value of UL signal strength in radio channels. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
Number of received DL signal strength samples in radio channels 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. This counter is used to find out frequency of received DL signal strength samples in radio channels. The counter increments when BSC receives DL measurement report or pre-processing measurement report. Times
1055
Description
This counter counts the maximum received DL signal strength in radio channels in DL measurement report. If the DL signal strength in radio channel in DL measurement report or pre-processing measurement report received by BSC is higher than the recorded highest DL signal strength, then the new highest DL signal strength will be recorded. This counter is used to find out status of maximum received DL signal strength in radio channels. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
Minimum DL received signal strength in radio channels 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. This counter is used to find out status of minimum received DL signal strength in radio channels. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
Total value of DL signal strength in radio channels 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. This counter is used to find out status of total value of DL signal strength in radio channels.
Usage
1056
The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
Number of TA samples in radio channels 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. This counter is used to find out frequency of TA samples in radio channels. The counter increments when BSC receives measurement report or pre-processing measurement report. Times
Maximum TA in radio channels 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. This counter is used to find out status of maximum TA in radio channels. The counter counts when BSC receives measurement report or pre-processing measurement report. Second
1057
Total number of TAs in radio channels 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. This counter is used to find out status of total value of TA in radio channels. The counter counts when BSC receives measurement report or pre-processing measurement report. Second
Mean number of idle TCH/Fs with interference band 0 This counter counts the mean number of idle TCH/Fs with interference band 0. This counter is used to find out number of idle TCH/Fs with interference band 0. The counter increments when timed database inquiry is carried out. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-001 Idle Channel Measurement
Mean number of idle TCH/Hs with interference band 0. This counter counts the mean number of idle TCH/Hs with interference band 0.
1058
This counter is used to find out number of idle TCH/Hs with interference band 0. The counter increments when timed database inquiry is carried out. Times ZGO-01-01-001 Half Rate ZGO-03-02-001 Idle Channel Measurement ZGO-03-02-005 Dynamic Half Rate Allocation
Mean number of idle SDCCHs with interference band 0 This counter counts the mean number of idle SDCCHs with interference band 0. This counter is used to find out number of idle SDCCHs with interference band 0. The counter increments when timed database inquiry is carried out. Times ZGO-03-02-001 Idle Channel Measurement
Mean number of idle SDCCHs with interference band 1 This counter counts the mean number of idle SDCCHs with interference band 1. This counter is used to find out number of idle SDCCHs with interference band 1. The counter increments when timed database inquiry is carried out. Times ZGO-03-02-001 Idle Channel Measurement
1059
Mean number of idle SDCCHs with interference band 2 This counter counts the mean number of idle SDCCHs with interference band 2. This counter is used to find out number of idle SDCCHs with interference band 2. The counter increments when timed database inquiry is carried out. Times ZGO-03-02-001 Idle Channel Measurement
Mean number of idle SDCCHs with interference band 3 This counter counts the mean number of idle SDCCHs with interference band 3. This counter is used to find out number of idle SDCCHs with interference band 3. The counter increments when timed database inquiry is carried out. Times ZGO-03-02-001 Idle Channel Measurement
Mean number of idle SDCCHs with interference band 4. This counter counts the mean number of idle SDCCHs with interference band 4.
1060
This counter is used to find out number of idle SDCCHs with interference band 4. The counter increments when timed database inquiry is carried out. Times ZGO-03-02-001 Idle Channel Measurement
Mean number of idle SDCCHs with interference band 5 This counter counts the mean number of idle SDCCHs with interference band 5. This counter is used to find out number of idle SDCCHs with interference band 5. The counter increments when timed database inquiry is carried out. Times ZGO-03-02-001 Idle Channel Measurement
Number of TFO initiations This counter counts the number of TFOs established by BSC. When the RANCS service process of BSC receives TFO status message and TFO has been established, the counter increments. Times ZGO-04-02-006 TFO
1061
Description
Number of mode changes for establishing TFO This counter does not count for the time being. ZGO-04-02-006 TFO
Number of mode changes for optimizing TFO This counter does not count for the time being. ZGO-04-02-006 TFO
Number of active collection changes for establishing TFO This counter does not count for the time being. ZGO-04-02-006 TFO
1062
Number of active collection changes for optimizing TFO This counter does not count for the time being. ZGO-04-02-006 TFO
Number of samples with voice quality is excellent 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. This counter is used to find out the UL voice quality on the radio channel. When BSCreceives the UL measurement report, preprocessing measurement report, or enhanced preprocessing measurement report, if the voice quality is excellent, the counter increments. Times
Number of samples with voice quality is good 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. This counter is used to find out the UL voice quality on the radio channel.
Usage
1063
When BSC receives the UL measurement report, preprocessing measurement report, or enhanced preprocessing measurement report, if the voice quality is good, the counter increments. Times
Number of samples with voice quality is medium 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. This counter is used to find out the UL voice quality on the radio channel. When BSC receives the UL measurement report, preprocessing measurement report, or enhanced preprocessing measurement report, if the voice quality is medium, the counter increments. Times
Number of samples with voice quality is bad 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. This counter is used to find out the UL voice quality on the radio channel. When BSC receives the UL measurement report, preprocessing measurement report, or enhanced preprocessing measurement report, if the voice quality is bad, the counter increments. Times
1064
Number of samples with voice quality is awfully 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. This counter is used to find out the UL voice quality on the radio channel. When BSC receives the UL measurement report, preprocessing measurement report, or enhanced preprocessing measurement report, if the voice quality is awful, the counter increments. Times
This counter counts the number of uplink error frames of full-rate version 1. 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. The counter's value is obtained from the periodic measurement report.
Measurement Point
This counter counts the number of uplink frames of full-rate version 1. This counter is used to find out the number of uplink voice frames of full-rate version 1. The counter increments every 20 ms. The counter's value is obtained from the periodic measurement report.
1065
This counter counts the number of uplink error frames of full-rate version 2. 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. The counter's value is obtained from the periodic measurement report.
Measurement Point
This counter counts the number of uplink voice frames of full-rate version 2. This counter is used to find out the number of uplink voice frames of full-rate version 2. The counter increments every 20 ms. The counter's value is obtained from the periodic measurement report.
This counter counts the number of uplink error frames of full-rate version 3. 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. The counter's value is obtained from the periodic measurement report.
Measurement Point
1066
This counter counts the number of uplink voice frames of full-rate version 3. This counter is used to find out the number of uplink voice frames of full-rate version 3. The counter increments every 20 ms. The counter's value is obtained from the periodic measurement report.
This counter counts the number of uplink error frames of half-rate version 1. 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. The counter's value is obtained from the periodic measurement report.
Measurement Point
This counter counts the number of uplink voice frames of half-rate version 1. This counter is used to find out the number of uplink voice frames of half-rate version 1. The counter increments every 20 ms. The counter's value is obtained from the periodic measurement report.
This counter counts the number of uplink error frames of half-rate version 3.
1067
Usage
This counter is used to find out the number of incorrect uplink voice frames of half-rate version 3. The counter increments when uplink decoding error occurs. The counter's value is obtained from the periodic measurement report.
Measurement Point
This counter counts the number of uplink voice frames of half-rate version 3. This counter is used to find out the number of uplink voice frames of half-rate version 3. The counter increments every 20 ms. The counter's value is obtained from the periodic measurement report.
Number of UL signal quality samples in radio channels on SDCCH 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. This counter is used to find out the frequency of UL signal quality samples in radio channels on SDCCH. The counter increments when BSC receives UL measurement report or pre-processing measurement report. Times
1068
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. This counter is used to find out status of the level of the worst UL signal quality in radio channels on SDCCH. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
Total value of UL quality level values in radio channels on SDCCH 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. This counter is used to find out status of total value of UL quality level values in radio channels on SDCCH. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
Number of DL signal quality samples in radio channels on SDCCH 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. This counter is used to find out the frequency of DL signal quality samples in radio channels on SDCCH.
Usage
1069
The counter increments when BSC receives DL measurement report or pre-processing measurement report. Times
Level of worst DL signal quality in radio channels on SDCCH 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. This counter is used to find out status of the level of the worst DL signal quality in radio channels on SDCCH. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
Total value of DL quality level values in radio channels on SDCCH 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. This counter is used to find out status of total value of DL quality level values in radio channels on SDCCH. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
1070
Number of received UL signal strength samples in radio channels on SDCCH 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. This counter is used to find out frequency of received UL signal strength samples in radio channels on SDCCH. The counter increments when BSC receives UL measurement report or pre-processing measurement report. Times
Maximum received UL signal strength in radio channels on SDCCH 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 preprocessing measurement report received by BSC is higher than the recorded highest UL signal strength, then the new highest UL signal strength will be recorded. This counter is used to find out status of maximum received UL signal strength in radio channels on SDCCH. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
1071
Minimum received UL signal strength in radio channels on SDCCH 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 preprocessing measurement report received by BSC is lower than the recorded lowest UL signal strength, then the new lowest UL signal strength will be recorded. This counter is used to find out status of minimum received UL signal strength in radio channels on SDCCH. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
Total value of UL signal strength in radio channels on SDCCH 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. This counter is used to find out status of total value of UL signal strength in radio channels on SDCCH. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
1072
Number of received DL signal strength samples in radio channels on SDCCH 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. This counter is used to find out frequency of received DL signal strength samples in radio channels on SDCCH. The counter increments when BSC receives DL measurement report or pre-processing measurement report. Times
Maximum received DL signal strength in radio channels on SDCCH 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 preprocessing measurement report received by BSC is higher than the recorded highest DL signal strength, then the new highest DL signal strength will be recorded. This counter is used to find out status of maximum received DL signal strength in radio channels on SDCCH. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
1073
Minimum DL received signal strength in radio channels on SDCCH 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 preprocessing measurement report received by BSC is lower than the recorded lowest DL signal strength, then the new lowest DL signal strength will be recorded. This counter is used to find out status of minimum received DL signal strength in radio channels on SDCCH. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
Total value of DL signal strength in radio channels on SDCCH 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. This counter is used to find out status of total value of DL signal strength in radio channels on SDCCH. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
1074
Number of UL signal quality samples in radio channels on TCH 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. This counter is used to find out the frequency of UL signal quality samples in radio channels on TCH. The counter increments when BSC receives UL measurement report or pre-processing measurement report. Times
Level of worst UL signal quality in radio channels on TCH 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. This counter is used to find out status of the level of the worst UL signal quality in radio channels on TCH. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
1075
Total value of UL quality level values in radio channels on TCH 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. This counter is used to find out status of total value of UL quality level values in radio channels on TCH. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
Number of DL signal quality samples in radio channels on TCH 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. This counter is used to find out the frequency of DL signal quality samples in radio channels on TCH. The counter increments when BSC receives DL measurement report or pre-processing measurement report. Times
1076
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. This counter is used to find out status of the level of the worst DL signal quality in radio channels on TCH. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
Total value of DL quality level values in radio channels on TCH 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. This counter is used to find out status of total value of DL quality level values in radio channels on TCH. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
Number of received UL signal strength samples in radio channels on TCH 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.
1077
This counter is used to find out frequency of received UL signal strength samples in radio channels on TCH. The counter increments when BSC receives UL measurement report or pre-processing measurement report. Times
Maximum received UL signal strength in radio channels on TCH 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. This counter is used to find out status of maximum received UL signal strength in radio channels on TCH. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
Minimum received UL signal strength in radio channels on TCH 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. This counter is used to find out status of minimum received UL signal strength in radio channels on TCH. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
1078
Total value of UL signal strength in radio channels on TCH 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. This counter is used to find out status of total value of UL signal strength in radio channels on TCH. The counter counts when BSC receives UL measurement report or pre-processing measurement report. None
Number of received DL signal strength samples in radio channels on TCH 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. This counter is used to find out frequency of received DL signal strength samples in radio channels on TCH. The counter increments when BSC receives DL measurement report or pre-processing measurement report. Times
1079
Maximum received DL signal strength in radio channels on TCH 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 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. This counter is used to find out status of maximum received DL signal strength in radio channels on TCH. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
Minimum DL received signal strength in radio channels on TCH 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. This counter is used to find out status of minimum received DL signal strength in radio channels on TCH. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
1080
Total value of DL signal strength in radio channels on TCH 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. This counter is used to find out status of total value of DL signal strength in radio channels on TCH. The counter counts when BSC receives DL measurement report or pre-processing measurement report. None
Number of samples with UL RQ = 0 on SDCCH BTS measures the level, quality, and interference of UL signal received in channel, and reports it to BSC, in combination with measurement report of DL signal reported by MS. Interval between BTS measurement and report is consistent with that of MS, that is, one measurement report is reported to BSC per 480 ms. Measurement mechanism of following counter C901120101 ~ C901120116 is same as that of this measurement value. This measurement value is the sample number with UL RQ = 0 in measurement report.
Measurement Point
BSC receives the measurement report submitted by BTS, if UL RQ=0 in measurement report, this counter increments. The measurement point is A, as shown in Figure 1082.
1081
THE
Unit
Times
Number of samples with UL RQ = 1 on SDCCH This measurement value is the sample number with UL RQ=1 in measurement report. 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 1083.
FIGURE 1083 - BSC RECEIVES BY BTS
THE
Unit
Times
1082
Number of samples with UL RQ = 2 on SDCCH This measurement value is the sample number with UL RQ=2 in measurement report. 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 1084.
FIGURE 1084 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with UL RQ = 3 on SDCCH This measurement value is the sample number with UL RQ=3 in measurement report. 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 1085.
1083
THE
Unit
Times
Number of samples with UL RQ = 4 on SDCCH This measurement value is the sample number with UL RQ=4 in measurement report. 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 1086.
FIGURE 1086 - BSC RECEIVES BY BTS
THE
Unit
Times
1084
Number of samples with UL RQ = 5 on SDCCH This measurement value is the sample number with UL RQ=5 in measurement report. 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 1087.
FIGURE 1087 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with UL RQ = 6 on SDCCH This measurement value is the sample number with UL RQ=6 in measurement report. 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 1088.
1085
THE
Unit
Times
This measurement value is the sample number with UL RQ=7 in measurement report. 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 1089.
FIGURE 1089 BSC RECEIVES BTS
THE
BY
Unit
Times
1086
This measurement value is the sample number with DL RQ=1 in measurement report. 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 1090.
FIGURE 1090 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with DL RQ = 1 on SDCCH This measurement value is the sample number with DL RQ=1 in measurement report. 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 1091.
FIGURE 1091 - BSC RECEIVES BY BTS
THE
Unit
Times
1087
Number of samples with DL RQ = 2 on SDCCH This measurement value is the sample number with DL RQ=2 in measurement report. 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 1092.
FIGURE 1092 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with DL RQ = 3 on SDCCH This measurement value is the sample number with DL RQ=3 in measurement report. 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 1093.
1088
THE
Unit
Times
Number of samples with DL RQ = 4 on SDCCH This measurement value is the sample number with DL RQ=4 in measurement report. 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 1094.
FIGURE 1094 - BSC RECEIVES BY BTS
THE
Unit
Times
1089
Number of samples with DL RQ = 5 on SDCCH This measurement value is the sample number with DL RQ=5 in measurement report. 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 1095.
FIGURE 1095 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with DL RQ = 6 on SDCCH This measurement value is the sample number with DL RQ=6 in measurement report. 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 1096.
1090
THE
Unit
Times
Number of samples with DL RQ = 7 on SDCCH This measurement value is the sample number with DL RQ=7 in measurement report. BSC receives the measurement report submitted by BTS, if DL RQ = 7 in measurement report, this counter increments. The measurement point is A, as shown in Figure 1097.
FIGURE 1097 - BSC RECEIVES BY BTS
THE
Unit
Times
1091
Number of samples with UL RQ = 0 on TCH 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 1098.
FIGURE 1098 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with UL RQ = 1 on TCH This measurement value is the sample number with UL RQ=1 in measurement report. 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 1099.
1092
THE
Unit
Times
Number of samples with UL RQ = 2 on TCH This measurement value is the sample number with UL RQ=2 in measurement report. 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 1100.
FIGURE 1100 - BSC RECEIVES BY BTS
THE
Unit
Times
1093
Number of samples with UL RQ = 3 on TCH This measurement value is the sample number with UL RQ=3 in measurement report. 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 1101.
FIGURE 1101 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with UL RQ = 4 on TCH This measurement value is the sample number with UL RQ=4 in measurement report. 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 1102.
1094
THE
Unit
Times
Number of samples with UL RQ = 5 on TCH This measurement value is the sample number with UL RQ=5 in measurement report. 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 1103.
FIGURE 1103 - BSC RECEIVES BY BTS
THE
Unit
Times
1095
Number of samples with UL RQ = 6 on TCH This measurement value is the sample number with UL RQ=6 in measurement report. 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 1104.
FIGURE 1104 - BSC RECEIVES BY BTS
THE
Unit
Times
This measurement value is the sample number with UL RQ=7 in measurement report. 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 1105.
FIGURE 1105 BSC RECEIVES BTS
THE
BY
1096
Unit
Times
Number of samples with DL RQ = 0 on TCH This measurement value is the sample number with DL RQ=1 in measurement report. 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 1106.
FIGURE 1106 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with DL RQ = 1 on TCH This measurement value is the sample number with DL RQ=1 in measurement report. 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 1107.
1097
THE
Unit
Times
Number of samples with DL RQ = 2 on TCH This measurement value is the sample number with DL RQ=2 in measurement report. 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 1108.
FIGURE 1108 - BSC RECEIVES BY BTS
THE
Unit
Times
1098
Number of samples with DL RQ = 3 on TCH This measurement value is the sample number with DL RQ=3 in measurement report. 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 1109.
FIGURE 1109 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with DL RQ = 4 on TCH This measurement value is the sample number with DL RQ=4 in measurement report. 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 1110.
1099
THE
Unit
Times
Number of samples with DL RQ = 5 on TCH This measurement value is the sample number with DL RQ=5 in measurement report. 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 1111.
FIGURE 1111 - BSC RECEIVES BY BTS
THE
Unit
Times
1100
Number of samples with DL RQ = 6 on TCH This measurement value is the sample number with DL RQ=6 in measurement report. 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 1112.
FIGURE 1112 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with DL RQ = 7 on TCH This measurement value is the sample number with DL RQ=7 in measurement report. 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 1113.
1101
THE
Unit
Times
1102
Chapter
19
1103
C901130023 Handover attempts due to UL interference of the full rate second sub cell (on TCH/F).................................. 1124 C901130024 Handover attempts due to DL interference of the full rate second sub cell (on TCH/F).................................. 1125 C901130025 Handover attempts due to good CI of the full rate second sub cell (on TCH/F)....................................... 1126 C901130026 Handover attempts due to bad CI of the full rate second sub cell (on TCH/F) ............................................. 1127 C901130027 Handover attempts due to path loss and too large TA of the full rate second sub cell (on TCH/F) ............ 1128 C901130028 Handover attempts due to path loss and too small TA of the full rate second sub cell (on TCH/F) ............ 1129 C901130029 Number of forced transfer handover attempts of the full rate second sub cell (on TCH/F) ............................ 1130 C901130030 Handover attempts due to other causes of the full rate second sub cell .................................................. 1131 C901130031 Handover attempts due to UL receiving strength of the half rate second sub cell ........................................ 1132 C901130032 Handover attempts due to DL receiving strength of the half rate second sub cell ........................................ 1133 C901130033 Handover attempts due to UL quality of the half rate second sub cell ....................................................... 1134 C901130034 Handover attempts due to DL quality of the half rate second sub cell ....................................................... 1135 C901130035 Handover attempts due to PBGT of the half rate second sub cell ............................................................. 1136 C901130036 Handover attempts due to traffic of the half rate second sub cell ............................................................. 1136 C901130037 Handover attempts due to UL interference of the half rate second sub cell ................................................. 1137 C901130038 Handover attempts due to DL interference of the half rate second sub cell ................................................. 1138 C901130039 Handover attempts due to C/I of the half rate second sub cell ............................................................. 1139 C901130040 Handover attempts due to C/I of the half rate second sub cell ............................................................. 1140 C901130041 Handover attempts due to path loss and too large TA of the half rate second sub cell............................ 1141 C901130042 Handover attempts due to path loss and too small TA of the half rate second sub cell ........................... 1142 C901130043 Number of forced transfer handover attempts of the half rate second sub cell............................................ 1143 C901130044 Handover attempts due to other causes of the half rate second sub cell ................................................. 1144 C901130045 Number of attempts of TCH/F seizure of the second sub cell (used for assignment) .................................. 1145 C901130046 Number of TCH/F seizure success of the second sub cell (used for assignment)......................................... 1146 C901130047 Number of TCH/F seizure failure of the second sub cell (used for assignment)......................................... 1146 C901130048 Number of attempts of TCH/F seizure of the second sub cell (used for handover) ..................................... 1147 C901130049 Number of TCH/F seizure success of the second sub cell (used for handover) ........................................... 1148 C901130050 Number of TCH/F seizure failure of the second sub cell (used for handover) ........................................... 1148 C901130051 Number of TCH/H seizure attempts of the second sub cell (used for assignment) .................................. 1149 C901130052 Number of TCH/H seizure success of the second sub cell (used for assignment)......................................... 1150
1104
C901130053 Number of TCH/H seizure failure of the second sub cell (used for assignment)......................................... 1151 C901130054 Number of TCH/H seizure attempts of the second sub cell (used for handover) ..................................... 1151 C901130055 Number of TCH/H seizure success of the second sub cell (used for handover) ........................................... 1152 C901130056 Number of TCH/H seizure failure of the second sub cell (used for handover) ........................................... 1153 C901130057 Number of TCH/F call drops in the second sub cell .............................................................................. 1153 C901130058 Number of TCH/H call drops in the second sub cell .............................................................................. 1154 C901130059 TCH/F busy time in the second sub cell .......... 1155 C901130060 TCH/H busy time in the second sub cell.......... 1155 C901130061 Number of TCH/F assignment attempts of the second sub cell ............................................................. 1156 C901130062 Number of TCH/F assignment success of the second sub cell .................................................................. 1156 C901130063 Number of TCH/F handover attempts of the second sub cell .................................................................. 1157 C901130064 Number of TCH/F handover success of the second sub cell .................................................................. 1158 C901130065 Number of TCH/H assignment attempts of the second sub cell ............................................................. 1158 C901130066 Number of TCH/H assignment success of the second sub cell ............................................................. 1159 C901130067 Number of TCH/H handover attempts of the second sub cell .................................................................. 1160 C901130068 Number of TCH/H handover success of the second sub cell .................................................................. 1161 C901130069 TCH/F of the first sub cell seizure success when prefer the second sub cell (used for assignment) ............... 1161 C901130070 TCH/F of the first sub cell seizure success when prefer the second sub cell (used for handover) .................. 1162 C901130071 TCH/H of the first sub cell seizure success when prefer the second sub cell (used for assignment) ............... 1162 C901130072 TCH/H of the first sub cell seizure success when prefer the second sub cell (used for handover) .................. 1163
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.
1105
Number of available TCH/Fs in the second sub cell This counter counts the number of available TCH/F channels in the second sub cell. 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. Call database interface to count promptly. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-05-02-009 Concentric Circle Technology
Number of unavailable TCH/Fs in the second sub cell This counter counts the number of unavailable TCH/F channels in the second sub cell. 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. Call database interface to count promptly. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-05-02-009 Concentric Circle Technology
1106
Number of available TCH/Hs in the second sub cell This counter counts the number of available TCH/H channels in the second sub cell. 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. Call database interface to count promptly. Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-05-02-009 Concentric Circle Technology
Number of unavailable TCH/Hs in the second sub cell This counter counts the number of unavailable TCH/H channels in the second sub cell. 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. Call database interface to count promptly. Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-05-02-009 Concentric Circle Technology
1107
C901130005 Number of handover attempts from the first sub cell to the second sub cell
Definition Description Usage
Number of handover attempts from the first sub cell to the second sub cell This counter counts the number of intra-cell handover attempts from the first sub cell to the second sub cell. 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. When BSC receives measurement reports from MS, it makes handover decision. If it is decided to do intra-cell handover, and current sub cell is the first sub cell, and if handover reason is 'too small Ta&PassLoss' or 'too large C/I', this counter increments. The measurement point is A, as shown inFigure 1114 .
FIGURE 1114 - INTRA-CELL HANDOVER ATTEMPT
Measurement Point
1108
C901130006 Number of handover execution from the first sub cell to the second sub cell
Definition Description Usage
Number of handover execution from the first sub cell to the second sub cell This counter counts the number of intra-cell handover execution from the first sub cell to the second sub cell. 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. During inter-sub-cell handover within a cell, this counter increments when following conditions are met: The channel of target sub cell is successfully activated Current channel is in the second sub cell Source channel is in the first sub cell
Measurement Point
1109
C901130007 Number of handover success from the first sub cell to the second sub cell
Definition Description Usage
Number of handover success from the first sub cell to the second sub cell This counter counts the number of intra-cell handover success from the first sub cell to the second sub cell. 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. During inter-sub-cell handover within a cell, target sub cell will receive handover completion message, indicating that MS successfully accesses to new channel. If target channel is in the second sub cell, and source channel is in the first sub cell, this counter increments. The measurement point is A, as shownFigure 1116 .
FIGURE 1116 - SUCCESSFUL INTRA-CELL HANDOVER
Measurement Point
1110
C901130008 Number of handover attempts from the second sub cell to the first sub cell
Definition Description Usage
Number of handover attempts from the second sub cell to the first sub cell This counter counts the number of intra-cell handover attempts from the second sub cell to the first sub cell. 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. 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 1117.
FIGURE 1117 - INTRA-CELL HANDOVER ATTEMPT
Measurement Point
1111
C901130009 Number of handover execution from the second sub cell to the first sub cell
Definition Description Usage
Number of handover execution from the second sub cell to the first sub cell This counter counts the number of intra-cell handover execution from the second sub cell to the first sub cell. 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. During inter-sub-cell handover within a cell, this counter increments when following conditions are met: The channel of target sub cell is successfully activated Current channel is in the second sub cell Source channel is in the first sub cell
Measurement Point
1112
C901130010 Number of handover success from the second sub cell to the first sub cell
Definition Description Usage
Number of handover success from the second sub cell to the first sub cell This counter counts the number of intra-cell successful handover from the second sub cell to the first sub cell. 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. During inter-sub-cell handover within a cell, this counter increments when following conditions are met: Target sub cell receives handover completion message Target channel is in the first sub cell Source channel is in the second sub cell
Measurement Point
1113
Number of handover attempts in the second sub cell This counter counts the number of intra-cell handover attempts within the second sub cell. 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. 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 1120.
FIGURE 1120 - INTRA-CELL HANDOVER ATTEMPT
Measurement Point
Number of handover execution in the second sub cell This counter counts the number of intra-cell handover execution within the second sub cell. 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.
1114
Measurement Point
During inter-sub-cell handover within a cell, this counter increments when following conditions are met: The channel of target sub cell is successfully activated 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
Number of handover success in the second sub cell This counter counts the number of intra-cell handover success within the second sub cell. 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. During inter-sub-cell handover within a cell, this counter increments when following conditions are met: Target sub cell receives handover completion message Target channel is in the second sub cell Source channel is in the first sub cells
Measurement Point
1115
C901130014 Number of outgoing inter-cell handover attempts of the second sub cell
Definition Description Usage
Number of outgoing inter-cell handover attempts of the second sub cell This counter counts the number of inter-cell handover attempts originated from the second sub cell. 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. When BSC receives measurement reports from MS, it makes handover decision. If it is decided to do inter-cell handover, and source cell is the second sub cell, this counter increments. The measurement point is A, as shown in Figure 1123.
FIGURE 1123 - INTRA-CELL HANDOVER ATTEMPT
Measurement Point
1116
C901130015 Number of outgoing inter-cell handover execution of the second sub cell
Definition Description Usage
Number of outgoing inter-cell handover success of the second sub cell This counter counts the Number of handover success inter-cell originated from the second sub cell. 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. During inter-sub-cell handover within a cell, source instance receives the handover completion message returned from target instance, indicating the MS has accessed to target channel. If source sub cell is the second sub cell, this counter increments. The measurement point is A, as shown in Figure 1124.
FIGURE 1124 - INTER-CELL HANDOVER EXECUTION
Measurement Point
1117
C901130016 Number of outgoing inter-cell handover success of the second sub cell
Definition Description Usage
Number of outgoing inter-cell handover success of the second sub cell This counter counts the number of handover success inter-cell originated from the second sub cell. 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. During inter-sub-cell handover within a cell, source instance receives the handover completion message returned from target instance, indicating the MS has accessed to target channel. If source sub cell is the second sub cell, this counter increments. The measurement point is A, as shown in Figure 1125.
FIGURE 1125 - SUCCESSFUL INTRA-CELL HANDOVER
Measurement Point
1118
C901130017 Handover attempts due to UL receiving strength of the full rate second sub cell
Definition Description
Handover attempts due to UL receiving strength of the full rate second sub cell 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by UL strength Current channel is full rate one
Usage
Measurement Point
1119
C901130018 Handover attempts due to DL receiving strength of the full rate second sub cell
Definition Description
Handover attempts due to DL receiving strength of the full rate second sub cell 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Handover is caused by DL strength Source sub cell is the second sub cell Current channel is full rate one
Usage
Measurement Point
1120
C901130019 Handover attempts due to UL quality of the full rate second sub cell
Definition Description
Handover attempts due to UL quality of the full rate second sub cell 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Handover is caused by UL quality Source sub cell is the second sub cell Current channel is full rate one
Usage
Measurement Point
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
1121
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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Handover is caused by DL quality Source sub cell is the second sub cell Current channel is full rate one
Usage
Measurement Point
C901130021 Handover attempts due to PBGT of the full rate second sub cell
Definition Description Usage
Handover attempts due to PBGT of the full rate second sub cell This counter counts the number of handover attempts, caused by PBGT and originated from full rate channel in the second sub cell. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Handover is caused by PBGT
Measurement Point
1122
Source sub cell is the second sub cell Current channel is full rate one
C901130022 Handover attempts due to traffic of the full rate second sub cell
Definition Description Usage
Handover attempts due to traffic of the full rate second sub cell This counter counts the number of handover attempts, caused by traffic and originated from full rate channel in the second sub cell. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: 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
Measurement Point
1123
Times ZGO-02-02-007 Traffic Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing ZGO-05-02-009 Concentric Circle Technology
C901130023 Handover attempts due to UL interference of the full rate second sub cell (on TCH/F)
Definition Description
Handover attempts due to UL interference of the full rate second sub cell (on TCH/F) This counter counts the number of handover attempts, caused by UL interference and originated from full rate channel in the second sub cell. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Handover is caused by traffic Source sub cell is the second sub cell Current channel is full rate one
Usage
Measurement Point
1124
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-05-02-009 Concentric Circle Technology
C901130024 Handover attempts due to DL interference of the full rate second sub cell (on TCH/F)
Definition Description
Handover attempts due to DL interference of the full rate second sub cell (on TCH/F) This counter counts the number of handover attempts, caused by DL interference and originated from full rate channel in the second sub cell. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by DL interference Current channel is full rate one
Usage
Measurement Point
1125
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-05-02-009 Concentric Circle Technology
C901130025 Handover attempts due to good CI of the full rate second sub cell (on TCH/F)
Definition Description
Handover attempts due to good CI of the full rate second sub cell (on TCH/F) 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by too good C/I Current channel is full rate one
Usage
Measurement Point
1126
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-05-02-009 Concentric Circle Technology
C901130026 Handover attempts due to bad CI of the full rate second sub cell (on TCH/F)
Definition Description
Handover attempts due to bad C/I of the full rate second sub cell (on TCH/F) 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by too bad C/I Current channel is full rate one
Usage
Measurement Point
1127
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-05-02-009 Concentric Circle Technology
C901130027 Handover attempts due to path loss and too large TA of the full rate second sub cell (on TCH/F)
Definition Description
Handover attempts due to path loss and too large GSMBSS-TA of the full rate second sub cell (on TCH/F) 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: 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
Usage
Measurement Point
1128
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology
C901130028 Handover attempts due to path loss and too small TA of the full rate second sub cell (on TCH/F)
Definition Description
Handover attempts due to path loss and too small GSMBSS-TA of the full rate second sub cell (on TCH/F) 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by too small path loss and TA Current channel is full rate one
Usage
Measurement Point
1129
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology
C901130029 Number of forced transfer handover attempts of the full rate second sub cell (on TCH/F)
Definition Description
Number of forced transfer handover attempts of the full rate second sub cell (on TCH/F) This counter counts the number of handover attempts, caused by forced transfer handover and originated from full rate channel in the second sub cell 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by forced transfer Current channel is full rate one
Usage
Measurement Point
1130
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-02-02-003 Directed-Shift Handover ZGO-05-02-009 Concentric Circle Technology
C901130030 Handover attempts due to other causes of the full rate second sub cell
Definition Description
Handover attempts due to other causes of the full rate second sub cell 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by other reasons Current channel is full rate one
Usage
Measurement Point
1131
Times 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
C901130031 Handover attempts due to UL receiving strength of the half rate second sub cell
Definition Description
Handover attempts due to UL receiving strength of the half rate second sub cell 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by UL strength Current channel is half rate one
Usage
Measurement Point
1132
C901130032 Handover attempts due to DL receiving strength of the half rate second sub cell
Definition Description
Handover attempts due to DL receiving strength of the half rate second sub cell 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by DL strength Current channel is half rate one
Usage
Measurement Point
1133
C901130033 Handover attempts due to UL quality of the half rate second sub cell
Definition Description
Handover attempts due to UL quality of the half rate second sub cell 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by UL quality Current channel is full rate one
Usage
Measurement Point
1134
C901130034 Handover attempts due to DL quality of the half rate second sub cell
Definition Description
Handover attempts due to DL quality of the half rate second sub cell 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by DL quality Current channel is half rate one
Usage
Measurement Point
1135
C901130035 Handover attempts due to PBGT of the half rate second sub cell
Definition Description Usage
Handover attempts due to PBGT of the half rate second sub cell This counter counts the number of handover attempts, caused by PBGT and originated from half rate channel in the second sub cell. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by PBGT Current channel is half rate one
Measurement Point
C901130036 Handover attempts due to traffic of the half rate second sub cell
Definition Description
Handover attempts due to traffic of the half rate second sub cell This counter counts the number of handover attempts, caused by traffic and originated from half rate channel in the second sub cell.
1136
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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by traffic Current channel is half rate one
Measurement Point
Times ZGO-02-02-007 Traffic Based Handover ZGO-02-03-003 GERAN/UTRAN Load Sharing ZGO-05-02-009 Concentric Circle Technology
C901130037 Handover attempts due to UL interference of the half rate second sub cell
Definition Description
Handover attempts due to UL interference of the half rate second sub cell This counter counts the number of handover attempts, caused by UL interference and originated from half rate channel in the second sub cell. 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.
Usage
1137
Measurement Point
Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by UL interference Current channel is full rate one
C901130038 Handover attempts due to DL interference of the half rate second sub cell
Definition Description
Handover attempts due to DL interference of the half rate second sub cell (on TCH/F) This counter counts the number of handover attempts, caused by DL interference and originated from half rate channel in the second sub cell. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by DL interference Current channel is half rate one
Usage
Measurement Point
1138
C901130039 Handover attempts due to C/I of the half rate second sub cell
Definition Description
Handover attempts due to C/I of the half rate second sub cell 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by too good C/I Current channel is full rate one
Usage
Measurement Point
1139
C901130040 Handover attempts due to C/I of the half rate second sub cell
Definition Description
Handover attempts due to C/I of the half rate second sub cell 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by too bad C/I Current channel is full rate one
Usage
Measurement Point
1140
C901130041 Handover attempts due to path loss and too large TA of the half rate second sub cell
Definition Description
Handover attempts due to path loss and too large GSMBSS-TA of the half rate second sub cell 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by too large path loss and TA Current channel is full rate one
Usage
Measurement Point
1141
C901130042 Handover attempts due to path loss and too small TA of the half rate second sub cell
Definition Description
Handover attempts due to path loss and too small GSMBSS-TA of the half rate second sub cell (on TCH/F) 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. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by too small path loss and TA Current channel is full rate one
Usage
Measurement Point
1142
C901130043 Number of forced transfer handover attempts of the half rate second sub cell
Definition Description
Number of forced transfer handover attempts of the half rate second sub cell (on TCH/F) This counter counts the number of handover attempts, caused by forced transfer handover and originated from half rate channel in the second sub cell. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by forced transfer Current channel is half rate one
Usage
Measurement Point
1143
C901130044 Handover attempts due to other causes of the half rate second sub cell
Definition Description
Handover attempts due to other causes of the half rate second sub cell This counter counts the number of handover attempts, caused by other causes and originated from half rate channel in the second sub cell. 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. Make handover decision after BSC receives measurement reports. This counter increments when following conditions are met: Decision is made Source sub cell is the second sub cell Handover is caused by other reasons Current channel is half rate one
Usage
Measurement Point
Times 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
1144
C901130045 Number of attempts of TCH/F seizure of the second sub cell (used for assignment)
Definition Description Usage
Number of attempts of TCH/F seizure of the second sub cell (used for assignment). This counter counts the number of seizure attempts in TCH/F channel in the second sub cell. 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 points of this counter include two types. When successfully applying for channel, if channel type is TCH/F, and application reason is assignment, this counter increments. Successful application includes:
Measurement Point
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
Times 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
1145
C901130046 Number of TCH/F seizure success of the second sub cell (used for assignment)
Definition Description Usage
Number of TCH/F seizure success of the second sub cell (used for assignment) This counter counts the number of successful seizure in TCH/F channel in the second sub cell. 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. This counter increments when following conditions are met: Successfully applying for channel Channel type is TCH/F Application reason is assignment
Measurement Point
Successful application includes: successful resource application; resource acquisition by queuing, seizure, or dynamic channel conversion.
Unit Related Features
Times 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
C901130047 Number of TCH/F seizure failure of the second sub cell (used for assignment)
Definition Description Usage
Number of TCH/F seizure failure of the second sub cell (used for assignment) This counter counts the number of seizure failure in TCH/F channel in the second sub cell. 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.
1146
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: 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
Times 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
C901130048 Number of attempts of TCH/F seizure of the second sub cell (used for handover)
Description Usage
This counter counts the number of seizure attempts in TCH/F channel in the second sub cell. 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 points of this counter include two types. When channel is successfully applied, if channel type is TCH/F, and application reason is handover, this counter increments. Successful application includes: successful resource application; resource acquisition by queuing, seizure, or dynamic channel conversion. When channel application is failed, if channel type is TCH/F, and application reason is handover, this counter increments. Failure reasons of application channel include:
Measurement Point
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.
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-002 Enhancement on Channel Allocation ZGO-04-02-005 Co-BCCH
1147
C901130049 Number of TCH/F seizure success of the second sub cell (used for handover)
Definition Description Usage
Number of TCH/F seizure success of the second sub cell (used for handover) This counter counts the number of successful seizure in TCH/F channel in the second sub cell. 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. This counter increments when following conditions are met: Channel is successfully applied Channel type is TCH/F Application reason is handover
Measurement Point
Successful application includes: successful resource application; resource acquisition by queuing, seizure, or dynamic channel conversion.
Unit Related Features
Times 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
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)
1148
Description Usage
This counter counts the number of seizure failure in TCH/F channel in the second sub cell. 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. When channel application is failed, if channel type is TCH/F, and application reason is handover, this counter increments. Failure reasons of application channel include: Receive release command while waiting for resource state Failed to configure instance number while seizing channel Timeout while queuing or seizure, or waiting for resource timer No available radio resource
Measurement Point
Successful application includes: successful resource application; resource acquisition by queuing, seizure, or dynamic channel conversion.
Unit Related Features
Times 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
C901130051 Number of TCH/H seizure attempts of the second sub cell (used for assignment)
Definition Description Usage
Number of TCH/H seizure attempts of the second sub cell (used for assignment) This counter counts the number of seizure attempts in TCH/H channel in the second sub cell. 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 points of this counter include two types: 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:
Measurement Point
1149
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
Times 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
C901130052 Number of TCH/H seizure success of the second sub cell (used for assignment)
Definition Description Usage
Number of TCH/H seizure success of the second sub cell (used for assignment) This counter counts the number of successful seizure in TCH/H channel in the second sub cell. 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. 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. Times 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
Measurement Point
1150
C901130053 Number of TCH/H seizure failure of the second sub cell (used for assignment)
Definition Description Usage
Number of TCH/H seizure failure of the second sub cell (used for assignment) This counter counts the number of seizure failure in TCH/F channel in the second sub cell. 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. 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
Measurement Point
Times 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
C901130054 Number of TCH/H seizure attempts of the second sub cell (used for handover)
Definition Description Usage
Number of TCH/H seizure attempts of the second sub cell (used for handover) This counter counts the number of seizure attempts in TCH/H channel in the second sub cell. 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.
1151
Measurement Point
Measurement points of this counter include two types: 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. 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
Times 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
C901130055 Number of TCH/H seizure success of the second sub cell (used for handover)
Definition Description Usage
Number of TCH/H seizure success of the second sub cell (used for handover) This counter counts the number of successful seizure in TCH/H channel in the second sub cell. 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. 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. Times ZGO-01-01-001 Half Rate ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-005 Dynamic Half Rate Allocation
Measurement Point
1152
C901130056 Number of TCH/H seizure failure of the second sub cell (used for handover)
Definition Description Usage
Number of TCH/H seizure failure of the second sub cell (used for handover) This counter counts the number of seizure failure in TCH/H channel in the second sub cell. 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. 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
Measurement Point
Times 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
Number of TCH/F call drops in the second sub cell This counter counts the number of call drops in TCH/F channel in the second sub cell.
1153
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. During call drops, if current channel is TCH/F, this counter increments. Call drops include following cases: After handover and deliver assignment command in cell, call drops occur due to 3107 timer timeout After inter-cell handover delivers handover command, call 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
Measurement Point
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology
Number of TCH/H call drops in the second sub cell This counter counts the number of call drops in TCH/H channel in the second sub cell. 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. During call drops, if current channel is TCH/H, this counter increments. Call drops include following cases: After handover and deliver assignment command in cell, call drops occur due to 3107 timer timeout After inter-cell handover delivers handover command, call 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
Measurement Point
Times 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
1154
TCH/F busy time in the second sub cell This counter counts the seizure time in TCH/F channel in the second sub cell. 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. This counter will count at following two cases: When seize or release TCH/F channel within a cell. Seizure channel means successful application of radio resource for database. Channel release means two cases: instance release caused by different reasons and release while waiting resource timer timeout. When promptly report measurement data.
Measurement Point
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-04-02-005 Co-BCCH ZGO-05-02-009 Concentric Circle Technology
TCH/H busy time in the second sub cell This counter counts the seizure time in TCH/H channel in the second sub cell. 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. This counter will count at following two cases: When seize or release TCH/F channel within a cell. Seizure channel means successful application of radio resource for database. Channel release means two cases: instance release caused by different reasons and release while waiting resource timer timeout. When promptly report measurement data.
Measurement Point
Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-04-02-005 Co-BCCH
1155
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. 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. 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. 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. Times
Usage
Measurement Point
Unit
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 be-
1156
ing timeout, if the sub cell ID is 2, the channel is full-rate channel, and the channel request is due to assignment, then the counter increments.
Usage
This counter is used to find out the number of 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. 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. Times
Measurement Point
Unit
This counter counts the number of attempts of TCH/F handover of the second sub cell. In the WaitAccess status, when BSC receives the release command, the Um interface assignment completion message or handover completion message, or the message of waiting for MS access being timeout, if the sub cell ID is 2, the channel is full-rate channel, and the channel request is due to intra-cell handover, inter-cell handover, external incoming handover, or internal directed retry, then the counter increments. 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. 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, intercell 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.
Usage
Measurement Point
1157
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
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. 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. 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. Times
Usage
Measurement Point
Unit
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 be-
1158
ing 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. 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. 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. Times
Measurement Point
Unit
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. 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. 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.
Usage
Measurement Point
1159
Unit
Times
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. 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. 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, intercell 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. Times
Usage
Measurement Point
Unit
1160
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. 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. 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. Times
Usage
Measurement Point
Unit
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. 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.
Usage
1161
In the RadioApply status, when BSC requests radio resource from DBS, if the request succeeds and the following conditions are satisfied, the counter counts: the sub cell selection mode is the second cell being preferred, the sub cell ID is 1, the channel is full-rate channel, and the channel request is due to assignment. Times
Unit
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. 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. 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. Times
Usage
Measurement Point
Unit
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 as-
1162
signment). When BSC requests radio resource from DBS, if the request succeeds and the following conditions are satisfied, the counter increments: the sub cell selection mode is the second cell being preferred, the sub cell ID is 1, the channel is 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. 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. Times
Measurement Point
Unit
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 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. 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. 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. Times
Usage
Measurement Point
Unit
1163
1164
Chapter
20
MS TA Measurement
Table of Contents Overview...................................................................... 1165 C901140001 Number of TA=0 ......................................... 1166 C901140002 Number of 0<TA<= 2.................................. 1166 C901140003 Number of 2<TA<=4................................... 1167 C901140004 Number of 4<TA<=6................................... 1167 C901140005 Number of 6<TA<=8................................... 1168 C901140006 Number of 8<TA<=10 ................................. 1168 C901140007 Number of 10<TA<=12 ............................... 1169 C901140008 Number of 12<TA<=14 ............................... 1170 C901140009 Number of 14<TA<=16 ............................... 1170 C901140010 Number of 16<TA<=18 ............................... 1171 C901140011 Number of 18<TA<=20 ............................... 1171 C901140012 Number of 20<TA<=22 ............................... 1172 C901060013 Number of 22<TA<=24 ............................... 1172 C901140014 Number of 24<TA<=26 ............................... 1173 C901140015 Number of 26<TA<=28 ............................... 1174 C901140016 Number of 28<TA<=30 ............................... 1174 C901140017 Number of 30<TA<=32 ............................... 1175 C901140018 Number of 32<TA<=34 ............................... 1175 C901140019 Number of 34<TA<=36 ............................... 1176 C901140020 Number of 36<TA<=38 ............................... 1177 C901140021 Number of 38<TA<=40 ............................... 1177 C901140022 Number of 40<TA<=42 ............................... 1178 C901140023 Number of 42<TA<=44 ............................... 1178 C901140024 Number 44<TA<=46 ................................... 1179 C901140025 Number of 46<TA<=48 ............................... 1180 C901140026 Number of 48<TA<=50 ............................... 1180 C901140027 Number of 50<TA<=52 ............................... 1181 C901140028 Number of 52<TA<=54 ............................... 1181 C901140029 Number of 54<TA<=56 ............................... 1182 C901140030 Number of 56<TA<=58 ............................... 1183 C901140031 Number of 58<TA<=60 ............................... 1183 C901140032 Number of 60<TA<=63 ............................... 1184 C901140033 Number of TA>63 ....................................... 1184
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.
1165
This counter counts the number of times of TA=0 in the MS measurement reports. 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. This counter increments when BSC receives the MS measurement report with TA=0. The measurement point is A, as shown in Figure 1154.
FIGURE 1154 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 0<TA<= 2 This counter counts the number of times of 0<TA<=2. This counter is used to find out the frequency of 0<TA<=2 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 0<TA<=2. The measurement point is A, as shown in Figure 1155.
FIGURE 1155 MS MEASUREMENT REPORT
Measurement Point
1166
Chapter 20 MS TA Measurement
Unit
Times
Number of 2<TA<=4. This counter counts the number of times of 2<TA<=4 in the MS measurement reports. This counter is used to find out the frequency of 2<TA<=4 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 2<TA<=4. The measurement point is A, as shown inFigure 1156.
FIGURE 1156 - MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 4<TA<=6. This counter counts the number of times of 4<TA<=6 in the MS measurement reports. This counter is used to find out the frequency of 4<TA<=6 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 4<TA<=6. The measurement point is A, as shown in Figure 1157.
Measurement Point
1167
Unit
Times
Number of 6<TA<=8. This counter counts the number of times of 6<TA<=8 in the MS measurement reports. This counter is used to find out the frequency of 6<TA<=8 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 6<TA<=8. The measurement point is A, as shown in Figure 1158.
FIGURE 1158 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 8<TA<=10. This counter counts the number of times of 8<TA<=10 in the MS measurement reports.
1168
Chapter 20 MS TA Measurement
Usage
This counter is used to find out the frequency of 8<TA<=10 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 8<TA<=10. The measurement point is A, as shown in Figure 1159.
FIGURE 1159 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 10<TA<=12. This counter counts the number of times of 10<TA<=12 in the MS measurement reports. This counter is used to find out the frequency of 10<TA<=12 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 10<TA<=12. The measurement point is A, as shown in Figure 1160.
FIGURE 1160 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
1169
This counter counts the number of times of 12<TA<=14 in the MS measurement reports. This counter is used to find out the frequency of 12<TA<=14 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 12<TA<=14. The measurement point is A, as shown in Figure 1161.
FIGURE 1161 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
This counter counts the number of times of 14<TA<=16 in the MS measurement reports. This counter is used to find out the frequency of 14<TA<=16 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 14<TA<=16. The measurement point is A, as shown in Figure 1162.
FIGURE 1162 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
1170
Chapter 20 MS TA Measurement
Number of 16<TA<=18. This counter counts the number of times of 16<TA<=18 in the MS measurement reports. This counter is used to find out the frequency of 16<TA<=18 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 16<TA<=18. The measurement point is A, as shown in Figure 1163.
FIGURE 1163 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 18<TA<=20. This counter counts the number of times of 18<TA<=20 in the MS measurement reports. This counter is used to find out the frequency of 18<TA<=20 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 18<TA<=20. The measurement point is A, as shown in Figure 1164.
Measurement Point
1171
Unit
Times
Number of 20<TA<=22. This counter counts the number of times of 20<TA<=22 in the MS measurement reports. This counter is used to find out the frequency of 20<TA<=22 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 20<TA<=22. The measurement point is A, as shown in Figure 1165.
FIGURE 1165 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 22<TA<=24. This counter counts the number of times of 22<TA<=24 in the MS measurement reports.
1172
Chapter 20 MS TA Measurement
Usage
This counter is used to find out the frequency of 22<TA<=24 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 22<TA<=24. The measurement point is A, as shown in Figure 1166.
FIGURE 1166 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 24<TA<=26. This counter counts the number of times of 24<TA<=26 in the MS measurement reports. This counter is used to find out the frequency of 24<TA<=26 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 24<TA<=26. The measurement point is A, as shown in Figure 1167.
FIGURE 1167 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
1173
Number of 26<TA<=28. This counter counts the number of times of 26<TA<=28 in the MS measurement reports. This counter is used to find out the frequency of 26<TA<=28 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 26<TA<=28. The measurement point is A, as shown in Figure 1168.
FIGURE 1168 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 28<TA<=30. This counter counts the number of times of 28<TA<=30 in the MS measurement reports. This counter is used to find out the frequency of 28<TA<=30 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 28<TA<=30. The measurement point is A, as shown in Figure 1169.
Measurement Point
1174
Chapter 20 MS TA Measurement
Unit
Times
Number of 30<TA<=32. This counter counts the number of times of 30<TA<=32 in the MS measurement reports. This counter is used to find out the frequency of 30<TA<=32 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 30<TA<=32. The measurement point is A, as shown in Figure 1170.
FIGURE 1170 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 32<TA<=34. This counter counts the number of times of 32<TA<=34 in the MS measurement reports.
1175
Usage
This counter is used to find out the frequency of 32<TA<=34 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 32<TA<=34. The measurement point is A, as shown in Figure 1171.
FIGURE 1171 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 34<TA<=36. This counter counts the number of times of 34<TA<=36 in the MS measurement reports. This counter is used to find out the frequency of 34<TA<=36 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 34<TA<=36. The measurement point is A, as shown in Figure 1172.
FIGURE 1172 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
1176
Chapter 20 MS TA Measurement
Number of 36<TA<=38. This counter counts the number of times of 36<TA<=38 in the MS measurement reports. This counter is used to find out the frequency of 36<TA<=38 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 36<TA<=38. The measurement point is A, as shown in Figure 1173.
FIGURE 1173 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 38<TA<=40 This counter counts the number of times of 38<TA<=40 in the MS measurement reports. This counter is used to find out the frequency of 38<TA<=40 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 38<TA<=40. The measurement point is A, as shown in Figure 1174.
Measurement Point
1177
Unit
Times
Number of 40<TA<=42. This counter counts the number of times of 40<TA<=42 in the MS measurement reports. This counter is used to find out the frequency of 40<TA<=42 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 40<TA<=42. The measurement point is A, as shown in Figure 1175.
FIGURE 1175 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 42<TA<=44. This counter counts the number of times of 42<TA<=44 in the MS measurement reports.
1178
Chapter 20 MS TA Measurement
Usage
This counter is used to find out the frequency of 42<TA<=44 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 42<TA<=44. The measurement point is A, as shown in Figure 1176.
FIGURE 1176 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 44<TA<=46. This counter counts the number of times of 44<TA<=46 in the MS measurement reports. This counter is used to find out the frequency of 44<TA<=46 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 44<TA<=46. The measurement point is A, as shown in Figure 1177.
FIGURE 1177 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
1179
Number of 46<TA<=48. This counter counts the number of times of 46<TA<=48 in the MS measurement reports. This counter is used to find out the frequency of 46<TA<=48 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 46<TA<=48. The measurement point is A, as shown in Figure 1178.
FIGURE 1178 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 48<TA<=50. This counter counts the number of times of 48<TA<=50 in the MS measurement reports. This counter is used to find out the frequency of 48<TA<=50 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 48<TA<=50. The measurement point is A, as shown in Figure 1179.
Measurement Point
1180
Chapter 20 MS TA Measurement
Unit
Times
Number of 50<TA<=52. This counter counts the number of times of 50<TA<=52 in the MS measurement reports. This counter is used to find out the frequency of 50<TA<=52 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 50<TA<=52. The measurement point is A, as shown in Figure 1180.
FIGURE 1180 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 52<TA<=54. This counter counts the number of times of 52<TA<=54 in the MS measurement reports.
1181
Usage
This counter is used to find out the frequency of 52<TA<=54 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 52<TA<=54. The measurement point is A, as shown in Figure 1181.
FIGURE 1181 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 54<TA<=56. This counter counts the number of times of 54<TA<=56 in the MS measurement reports. This counter is used to find out the frequency of 54<TA<=56 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 54<TA<=56. The measurement point is A, as shown in Figure 1182.
FIGURE 1182 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
1182
Chapter 20 MS TA Measurement
Number of 56<TA<=58. This counter counts the number of times of 56<TA<=58 in the MS measurement reports. This counter is used to find out the frequency of 56<TA<=58 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 56<TA<=58. The measurement point is A, as shown in Figure 1183.
FIGURE 1183 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of 58<TA<=60 This counter counts the number of times of 58<TA<=60 in the MS measurement reports. This counter is used to find out the frequency of 58<TA<=60 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 58<TA<=60. The measurement point is A, as shown in Figure 1184.
Measurement Point
1183
Unit
Times
Number of 60<TA<=63. This counter counts the number of times of 60<TA<=63 in the MS measurement reports. This counter is used to find out the frequency of 60<TA<=63 in the MS measurement reports. It can be one of the parameters that are used to evaluate the cell radio environment. This counter increments when BSC receives the MS measurement report with 60<TA<=63. The measurement point is A, as shown in Figure 1185.
FIGURE 1185 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
Number of TA > 63 This counter counts the number of times of TA>63 in the MS measurement reports.
1184
Chapter 20 MS TA Measurement
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. This counter increments when BSC receives the MS measurement report with TA>63. The measurement point is A, as shown in Figure 1186.
FIGURE 1186 MS MEASUREMENT REPORT
Measurement Point
Unit
Times
1185
1186
Chapter
21
SAPI3 Measurement
Table of Contents Overview...................................................................... 1188 C901150001 Number of SAPI3 link establishments on SACCH/F (MO-SM)......................................................... 1188 C901150002 Number of SAPI3 link establishments on SACCH/H (MO-SM) ........................................................ 1189 C901150004 Number of SAPI3 link establishments on FACCH/F (MO-SM) ......................................................... 1190 C901150005 Number of SAPI3 link establishments on FACCH/H (MO-SM)......................................................... 1191 C901150006 Number of SAPI3 link establishment requests on SACCH/F (MT-SM) ......................................................... 1191 C901150007 Number of SAPI3 link establishment requests on SACCH/H (MT-SM)......................................................... 1192 C901150009 Number of SAPI3 link establishment requests on FACCH/F (MT-SM).......................................................... 1193 C901150010 Number of SAPI3 link establishment requests on FACCH/H (MT-SM) ......................................................... 1194 C901150011 Number of successful SAPI3 link establishments on SACCH/F (MT-SM)..................................................... 1194 C901150012 Number of successful SAPI3 link establishments on SACCH/H (MT-SM) .................................................... 1195 C901150014 Number of successful SAPI3 link establishments on FACCH/F (MT-SM) ..................................................... 1196 C901150015 Number of successful SAPI3 link establishments on FACCH/H (MT-SM)..................................................... 1197 C901150016 Number of DTAP messages used as SDCCH UL point-to-point short messages (SMs)................................ 1197 C901150017 Number of DTAP messages used as SDCCH DL point-to-point short messages (SMs)................................ 1199 C901150018 Number of DTAP messages on FACCH/F UL for point-to-point short messages......................................... 1201 C901150019 Number of DTAP messages on FACCH/F DL for point-to-point short messages......................................... 1202 C901150020 Number of DTAP messages on FACCH/H UL for point-to-point short messages......................................... 1202 C901150021 Number of DTAP messages on FACCH/H DL for point-to-point short messages......................................... 1203 C901150022 Number of DTAP messages on SACCH/F DL for point-to-point short messages......................................... 1203 C901150023 Number of DTAP messages on SACCH/F DL for point-to-point short messages......................................... 1205 C901150024 Number of DTAP messages on SACCH/H UL for point-to-point short messages......................................... 1206 C901150025 Number of DTAP messages on SACCH/H DL for point-to-point short messages......................................... 1208
1187
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.
Number of SAPI3 link establishments on SACCH/F (MO-SM) 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. This counter is used to find out the frequency of SAPI3 link establishments on SACCH/F. This counter counts the number of BSC receiving EST_IND message sent by BTS with SAPI=3. The measurement point is A, as shown inFigure 1187.
1188
OF
MO SHORT MESSAGES
DURING
CONVERSATION
Number of SAPI3 link establishments on SACCH/H (MO-SM) 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. This counter is used to find out the frequency of SAPI3 link establishments on SACCH/H. 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 1188.
1189
OF
MO SHORT MESSAGES
DURING
CONVERSATION
Number of SAPI3 link establishments on FACCH/F (MO-SM) 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. This counter is used to find out the frequency of SAPI3 link establishments on FACCH/F. This counter is not realized at present in the system. Times ZGB-01-03-003 Short Message Service (SMS)
1190
Number of SAPI3 link establishments on FACCH/H (MO-SM) 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. This counter is used to find out the frequency of SAPI3 link establishments on FACCH/H. This counter is not realized at present in the system. Times ZGB-01-03-003 Short Message Service (SMS)
Number of SAPI3 link establishments on SACCH/F (MT-SM) 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. This counter is used to find out the frequency of SAPI3 link establishment requests on SACCH/F. This counter counts the number of BSC sending EST_REQ message to BTS with SAPI=3 while the short message link between BSC and MS is not established. The measurement point is C1, as shown in Figure 1189.
1191
OF
MT SHORT MESSAGE
DURING
CONVERSATION
Number of SAPI3 link establishments on SACCH/H (MT-SM) 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. This counter is used to find out the frequency of SAPI3 link establishment requests on SACCH/H. This counter counts the number of BSC sending EST_REQ message to BTS with SAPI=3 while the short message link between BSC and MS is not established. The measurement point is C1, as shown in Figure 1190.
1192
OF
MT SHORT MESSAGE
DURING
CONVERSATION
Number of SAPI3 link establishments on FACCH/F (MT-SM) 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. This counter is used to find out the frequency of SAPI3 link establishments on FACCH/F. This counter is not realized at present in the system. Times
1193
Related Features
Number of SAPI3 link establishments on FACCH/H (MT-SM) 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. This counter is used to find out the frequency of SAPI3 link establishments on FACCH/H. This counter is not realized at present in the system. Times ZGB-01-03-003 Short Message Service (SMS)
Number of successful SAPI3 link establishments on SACCH/F (MTSM) 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. This counter is used to find out the frequency of successful SAPI3 link establishments on SACCH/F. This counter counts the number of BSC receiving EST_IND message send by BTS with SAPI=3. The measurement point is C2, as shown in Figure 1191.
1194
OF
MT SHORT MESSAGE
DURING
CONVERSATION
Number of SAPI3 link establishments on SACCH/H (MT-SM) 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. This counter is used to find out the frequency of SAPI3 link establishment requests on SACCH/H. This counter counts the number of BSC sending EST_CONF message send by BTS with SAPI=3 while the short message link between BSC and MS is not established. The measurement point is C2, as shown inFigure 1192 .
1195
OF
MT SHORT MESSAGE
DURING
CONVERSATION
Number of successful SAPI3 link establishments on FACCH/F (MTSM) 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. This counter is used to find out the frequency of SAPI3 link establishment requests on SACCH/F. This counter is not realized at present in the system. Times
1196
Related Features
Number of successful SAPI3 link establishments on FACCH/H (MTSM) 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. This counter is used to find out the frequency of successful SAPI3 link establishments on FACCH/H. This counter is not realized at present in the system. Times ZGB-01-03-003 Short Message Service (SMS)
C901150016 Number of DTAP messages used as SDCCH UL point-to-point short messages (SMs)
Definition Description Usage Measurement Point
Number of DTAP messages used as SDCCH UL point-to-point short messages (SMs) This counter counts the number of DTAP packet sent by MS to the network side through SDCCH. This counter is used to find out the frequency of DTAP message of point-to-point message on SDCCH UL. This counter counts the number of BSC receiving DTAP packet sent by BTS on SDCCH with SAPI=3. The measurement points are D4 and D5 as shown inFigure 1193 , and B2 and B5 as shown inFigure 1194 .
1197
OF
MT SHORT MESSAGE
IN
IDLE STATUS
1198
OF
MO SHORT MESSAGE
IN
IDLE STATUS
C901150017 Number of DTAP messages used as SDCCH DL point-to-point short messages (SMs)
Definition Description Usage
Number of DTAP messages used as SDCCH DL point-to-point short messages (SMs) This counter counts the number of DTAP packet sent by network to MS through SDCCH . This counter is used to find out the frequency of DTAP message of point-to-point message on SDCCH DL.
1199
Measurement Point
This counter counts the number of BSC receiving DTAP packet toBTS on SDCCH with SAPI=3. The measurement points are D3 and D6 as shown inFigure 1195 , and B3 and B4 as shown in Figure 1196.
FIGURE 1195 - FLOW
OF
MT SHORT MESSAGE
IN
IDLE STATUS
1200
OF
MO SHORT MESSAGE
IN
IDLE STATUS
Number of DTAP messages on FACCH/F UL for point-to-point short messages This counter counts the number of DTAP packet sent by MS to network side through FACCH/F.
1201
This counter is used to find out the frequency of DTAP message of point-to-point short messages on FACCH/F UL. This counter is not realized at present in the system. Times ZGB-01-03-003 Short Message Service (SMS)
Number of DTAP messages on FACCH/F DL for point-to-point short messages. This counter counts the number of DTAP packet of short messages sent by network side to MS through FACCH/F. This counter is used to find out the frequency of DTAP message of point-to-point short messages on FACCH/F UL. This counter is not realized at present in the system. Times ZGB-01-03-003 Short Message Service (SMS)
Number of DTAP messages on FACCH/H UL for point-to-point short messages. This counter counts the number of DTAP packet of short messages sent by MS to network side through FACCH/H.
1202
This counter is used to find out the frequency of DTAP message of point-to-point short messages on FACCH/H UL. This counter is not realized at present in the system. Times ZGB-01-03-003 Short Message Service (SMS)
Number of DTAP messages on FACCH/H DL for point-to-point short messages. This counter counts the number of DTAP packet of short messages sent by network side to MS through FACCH/H. This counter is used to find out the frequency of DTAP message of point-to-point short messages on FACCH/H DL. This counter is not realized at present in the system. Times ZGB-01-03-003 Short Message Service (SMS)
Number of DTAP messages on SACCH/F UL for point-to-point short messages. This counter counts the number of DTAP packet of short messages sent by network side to MS through SACCH/F.
1203
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. 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 1197, and A2 and A5 as shown inFigure 1198 .
FIGURE 1197 - FLOW
OF
MT SHORT MESSAGE
DURING
CONVERSATION
1204
OF
MO SHORT MESSAGES
DURING
CONVERSATION
Number of DTAP messages on SACCH/F DL for point-to-point short messages. This counter counts the number of DTAP packet of short messages sent by network side to MS through SACCH/F. This counter is used to find out the frequency of DTAP message of point-to-point short messages on SACCH/F DL.
1205
This counter is not realized at present in the system. Times ZGB-01-03-003 Short Message Service (SMS)
Number of DTAP messages on SACCH/H UL for point-to-point short messages This counter counts the number of DTAP packet sent by MS to network side through SACCH/H. This counter is used to find out the frequency of DTAP message of point-to-point short messages on SACCH/H UL. 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 1199 , and A2 and A5 as shown in Figure 1200.
1206
1207
Number of DTAP messages on SACCH/H DL for point-to-point short messages. This counter counts the number of DTAP packet of short messages sent by network side to MS through SACCH/H. This counter is used to find out the frequency of DTAP message of point-to-point short messages on SACCH/H DL. This counter counts the number of BSC sending DTAP packet to BTS on SACCH/H withSAPI=3. The measurement points are C3 and C6 as shown in Figure 1201, and A3 and A4 as shown inFigure 1202.
FIGURE 1201 - FLOW
OF
MT SHORT MESSAGE
DURING
CONVERSATION
1208
OF
MO SHORT MESSAGES
DURING
CONVERSATION
1209
1210
Chapter
22
1211
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.
Number of Packet access reject message When MS sends packet resource request to BSC through BTS, BSC will return packet UL assignment to MS or packet access reject on PACCH. This counter counts the number of BSC sending the packet access reject messages on PACCH.
This counter is used to check the packet access reject messages sent by BSC in packet transmission mode. When the UPPB of BSC sends packet access reject messages to MS, the counter increments. The measurement point is A2, as shown inFigure 1203 .
FIGURE 1203 - MEASUREMENT POINT PACKET ACCESS REJECT
OF
AND
Unit
Times
1212
Number of Packet access reject message When MS sends packet resource request to BSC through BTS, BSC will return packet UL assignment to MS or packet access reject on PACCH. This counter counts the number of BSC sending the packet access reject messages on PACCH.
This counter is used to check the packet access reject messages sent by BSC in packet transmission mode. When the UPPB of BSC receives packet resource request messages, the counter increments. The measurement point is A1, as shown inFigure 1204 .
FIGURE 1204 - MEASUREMENT POINT PACKET ACCESS REJECT
OF
AND
Unit
Times
Number of Packet UL Assignment message Packet UL assignment can be sent on both PCCCH and PACCH. When established for TBF double steps, the first packet UL assignment needs to be sent on PCCH, other packet UL assignments such as DL TBF or resource redistribution initiated by MS will be sent on PACCH by BSC.
1213
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 1205.
FIGURE 1205 - MEASUREMENT
OF
Unit
Times
Number of Additional MS access capabilities messages. This counter counts the number of additional MS access capabilities messages received by BSC on PACCH in packet transmission mode. This counter is used to check the packet access reject messages sent by BSC in packet transmission mode. 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 1206.
1214
Unit
Times
Number of packet DL assignment messages. This counter counts the number of packet DL assignment messages sent by BSC on PACCH in packet transmission mode. When the type of DL control block sent by BSC is packet DL assignment, the counter increments. The measurement point is A, as shown inFigure 1207 .
1215
ON
PACCH
IN
Unit
Times
Number of packet TBF release messages This counter counts the number of packet TBF release messages on PACCH sent by BSC. When the type of DL control block sent by BSC is packet TBF release, the counter increments. The measurement point is A, as shown inFigure 1208.
1216
ON
PACCH
IN
Unit
Times
Number of packet DL Ack/Nack messages. After TBF is established and DL RLC set RRBP on sending data block, MS sends packet DL Ack/Nack messages on PACCH. This counter counts the number of packet DL Ack/Nack messages received by BSC on PACCH in packet transmission mode.
Measurement Point
When the type of UL control block sent by BSC is packet DL Ack/Nack, the counter increments. The measurement points are A, A1, as shown inFigure 1209 .
1217
ON
Unit
Times
Number of EGPRS Packet DL Ack/Nack messages. After TBF is established and DL RLC set RRBP on sending data block, MS sends packet DL Ack/Nack messages on PACCH. This counter counts the number of EGPRS packet DL Ack/Nack messages received by BSC on PACCH in EGPRS packet transmission mode.
Measurement Point
When the type of UL control block sent by BSC is EGPRS packet DL Ack/Nack, the counter increments. The measurement points are A and A1, as shown inFigure 1210.
1218
ON
PACCH
IN
Unit
Times
Number of Packet UL Ack/Nack message This counter counts the number of packet UL Ack/Nack messages sent by BSC on PACCH in packet transmission mode. 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 1211 .
1219
ON
PACCH
Unit
Times
Number of Packet Control Acknowledgement message This counter counts the number of packet control acknowledgement messages received by BSC on PACCH in packet transmission mode. When the type of UL control block received by BSC is packet control acknowledgement, the counter increments. The measurement point is B, as shown inFigure 1212.
Measurement Point
1220
ON
PACCH
Unit
Times
Number of Packet Cell Change Continue message If MS intends to handoff from service cell to destination cell, it will initiate packet cell change notification to BSC to request the system message of destination under the condition that the network and MS support NACC. After BSC receives packet cell change messages, it will send packet cell change continues messages to MS on PACCH or packet cell changes command to inform MS to switch to the new cell. This counter counts the number of packet cell change continues messages sent by BSC on PACCH.
Measurement Point
BSC initiates timer after receiving PACKET NEIGHBOR CELL CHANGE NOTIIf it receives the packet system message of destination cell in the defined time, BSC send PACK NEIGHBOR CELL DATA, then send PACKET CELL CHANGE CONTINUES, the counter increments. The measurement point is A3, as shown inFigure 1213.
FICATION.
1221
OF
PACKET-CELL-CHANGE-RELATED
BSC initiates timer after receiving the PACKET NEIGHBOR CELL CHANGE NOTIFICATION message. If timer times out and doesnt receive the packet system message of destination cell, BSC sends the PACK CELL CHANGE CONTINUE message directly, the counter increments. The measurement point is A1, as shown inFigure 1214 .
FIGURE 1214 - MEASUREMENT POINT COUNTER (II)
OF
PACKET-CELL-CHANGE-RELATED
Unit
Times
1222
Number of Packet Cell Change Failure message After BSC sends packet cell change command to MS, BTS initiates packet cell change failure to BSC to indicate that the cell fails to change command. This counter counts the number of packet cell change failure messages received by BSC on PACCH in packet transmission mode.
Measurement Point
When the type of UL control block sent by BSC is packet cell change failure, the counter increments. The measurement point is A3, as shown inFigure 1215 .
FIGURE 1215 - MEASUREMENT POINT OF AND PACKET CELL CHANGE FAILURE PACKET CELL CHANGE ORDER
Unit
Times
1223
Description
If MS intends to handoff from service cell to destination cell, it will initiate packet cell change notification to BSC to request the system message of destination under the condition that the network and MS support NACC. This counter counts the number of packet cell change notification messages received by BSC on PACCH in packet transmission mode.
Measurement Point
When the type of UL control block received by BSC is packet cell change notification, the counter increments. The measurement point is A1, as shown inFigure 1216.
FIGURE 1216 - MEASUREMENT POINT COUNTER (I)
OF
PACKET-CELL-CHANGE-RELATED
Unit
Times
Number of Packet Cell Change Order message 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. When BSC sends packet cell change order messages, the counter increments. The measurement point is A2, as shown inFigure 1217.
Measurement Point
1224
Unit
Times
Number of packet mobile TBF status messages This counter counts the number of packet mobile TBF status messages sent by BSC on PACCH in packet service. 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 1218.
1225
- MEASUREMENT POINT
OF
Unit
Times
Number of packet neighbor cell data messages. If MS sends change notification to neighboring cell in support of NACC, BSC will send packet neighboring cell data to MS through BTS. This counter counts the number of packet neighboring cell data 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 1219.
1226
OF
PACKET-CELL-CHANGE-RELATED
Unit
Times
Number of packet PDCH release messages. This counter counts the number of packet PDCH release messages sent by BSC on PACCH. When the type of DL control block sent by BSC is packet PDCH release, the counter increments. Times
1227
This counter counts the number of packet polling request messages sent by BSC on PACCH in packet transmission mode. When the type of DL control block sent by BSC is packet polling request, counter increments. The measurement point is A, as shown inFigure 1220 .
FIGURE 1220 - MEASUREMENT POINT POLLING
OF
Unit
Times
Number of packet power control/timing advance messages. This counter counts the number of packet power control/timing advance messages sent by BSC on PACCH. When the type of DL control block sent by BSC is packet power control/timing advance message, counter increments. The measurement point is A, as shown inFigure 1221.
1228
OF
Unit
Times
Number of packet PSI status messages. In order to obtain the packet system messages of serving cell, MS initiates packet PSI status messages to BSC through BTS to indicate that MS has been received the packet system messages. This counter counts the number of packet PSI status messages received by BSC on PACCH.
Measurement Point
When the type of UL control block sent by BSC is packet PSI Status message, counter increments. The measurement point is A1, as shown inFigure 1222.
1229
OF
PACKET-SERVICE-CELL-DATA-
Unit
Times
Number of packet serving cell data messages. 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. This counter is used to check packet serving cell data messages sent by BSC on PACCH. When the type of DL control block sent by BSC is packet serving cell data messages, the counter increments. The measurement point is A2, as shown inFigure 1223 .
1230
OF
PACKET-SERVICE-CELL-DATA-
Unit
Times
Number of packet SI status messages. In order to obtain the system messages of serving cell, MS initiates packet SI status message to BSC through BTS to indicate that MS has been received the packet system messages. This counter counts the number of packet SI status messages received by BSC on PACCH.
Measurement Point
When the type of UL control block sent by BSC is packet SI status message, counter increments. The measurement point is A1, as shown inFigure 1224.
1231
OF
PACKET-SERVICE-CELL-DATA-
Unit
Times
Number of packet timeslot reconfigure messages. Packet timeslot reconfigure is used to assign UL and DL resource link. This counter counts the number of packet timeslot reconfigure messages sent by BSC on PACCH.
Measurement Point
When the type of DL control block sent by BSC is packet timeslot reconfigure messages, counter increments. The measurement point is A, as shown inFigure 1225 andFigure 1226 .
1232
ON
PACCH
UNDER
DL
ON
PACCH
UNDER
UL
Unit
Times
1233
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 1227 .
FIGURE 1227 - MEASUREMENT POINT REQUEST MESSAGE
OF
Number of packet PSI message. This counter counts the number of PSI messages sent by BSC on PACCH in packet service. When the type of DL control block sent by BSC to MS through BTS is packet system message, the counter increments. The measurement point is A, as shown inFigure 1228.
1234
OF
Unit
Times
1235
1236
Chapter
23
1237
C901170025 Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment .................................................................. 1254 C901170026 Number of GPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment ........................................................................... 1255 C901170027 Number of allocated PDCH for GPRS DL TBF resource reallocation due to UL TBF establishment ................ 1256 C901170028 Number of GPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment ........................................................................... 1257 C901170029 Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment ........................................................................... 1258 C901170030 Number of GPRS DL TBF resource reallocation failure due to BIU connection failure for UL TBF establishment ........................................................................... 1259 C901170031 Number of GPRS DL TBF resource reallocation success of channel activate and connection for UL TBF establishment....................................................................... 1260 C901170032 Number of GPRS DL TBF resource reallocation failure due to UL TBF establishment ................................. 1261 C901170033 Number of GPRS DL TBF resource reallocation success due to UL TBF establishment ............................... 1261 C901170036 Number of GPRS DL TBF resource reallocation failure due to Abis congestion for LLC transmission ............ 1262 C901170037 Number of GPRS DL TBF resource reallocation failure due to RR congestion for LLC transmission .............. 1263 C901170038 Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission ........................................................................ 1264 C901170039 Number of GPRS DL TBF resource reallocation success of channel allocation due to LLC transmission......... 1265 C901170040 Number of allocated PDCH for GPRS DL TBF resource reallocation due to LLC transmission ...................... 1266 C901170041 Number of GPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission ............................................................................. 1267 C901170042 Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission ............................................................................. 1268 C901170043 Number of GPRS DL TBF resource reallocation failure due to BIU connection failure for LLC transmission ............................................................................. 1269 C901170044 Number of GPRS DL TBF resource reallocation success of channel activate and connection for LLC transmission ............................................................................. 1270 C901170045 Number of GPRS DL TBF resource reallocation failure due to LLC transmission........................................ 1270 C901170046 Number of GPRS DL TBF resource reallocation success due to LLC transmission ...................................... 1271 C901170047 Number of GPRS DL TBF release due to flush LL ............................................................................... 1271 C901170048 Number of GPRS DL TBF release due to GPRS suspend requests .......................................................... 1272 C901170049 Number of GPRS DL TBF forcing release by CS............................................................................... 1272 C901170050 Number of GPRS DL TBF normal release due to user plane requests ....................................................... 1273
1238
C901170051 Number of GPRS DL TBF abnormal release due to user plane requests.................................................... 1274 C901170052 Number of GPRS DL TBF release due to NSVC unavailability ................................................................ 1274 C901170053 Number of GPRS DL TBF release due to BVC unavailability ................................................................ 1275 C901170054 Number of GPRS DL TBF release due to other reasons........................................................................ 1276 C901170055 Number of DL GPRS TBF grab resources......... 1276 C901170056 Number of grab instance by DL GPRS TBF......... 1277 C901170057 Number of DL GPRS TBF queuing .................. 1278 C901170058 Number of DL GPRS TBF queuing success......... 1278 C901170059 Number of DL GPRS TBF release TBF during queuing ....................................................................... 1279
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.
Number of GPRS DL TBF establishment requests on CCCH/PCCCH. This counter counts the number of DL establishment requests received by control plane when BSC initially attempts to establish GPRS 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 GPRS DL TBF. When RANPS module receives the DL request (EV_RANUMC_DLASS_REQ) sent from RANUMC module, the counter increments. The measurement point is A, as shown in Figure 1229.
FIGURE 1229 - DL REQUEST
Usage
Measurement Point
1239
Unit
Times
Number of GPRS DL TBF establishment requests on PACCH. This counter counts the number of establishing GPRS 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 GPRS UL TBF.
EV_MAC_DL_ASSIGN_REQ
After MS has established GPRS UL TBF, RANPS module receives message sent from RANU module, the counter increments. The measurement point is A, as shown inFigure 1230.
Unit
Times
No statistics temporarily.
1240
C901170005 Number of GPRS DL TBF establishment failure due to not support DTM
Description
No statistics temporarily.
Number of GPRS DL TBF establishment failure due to Abis congestion. 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. 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. The measurement is taken at two time points listed below: After RANPS module receives DL request message (EV_RANUMC_DLASS_REQ) sent from RANUMC module, if resource application fails and the cause of failure is Abis congestion, the counter increments. The measurement point is A, as shown inFigure 1231 .
FIGURE 1231 - DATABASE APPLICATION FAILURE CONGESTION (I)
DUE TO
Usage
Measurement Point
ABIS
1241
After MS establishes GPRS UL TBF, RANPS module receives message sent from RANU module, if resource application fails and the cause of failure is Abis congestion, the counter increments. The measurement point is A, as shown inFigure 1232 .
EV_MAC_DL_ASSIGN_REQ
DUE TO
ABIS
Number of GPRS DL TBF establishment failure due to RR congestion. 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. There are three causes for RR congestion: MS per channel (number of MS reaches the peak in each channel), TAI/TFI (no TAI or TFI) and no PDCH (no PS channel). This counter is used to find out the frequency of failures that RANPS applies to database for resource and the cause of failures is RR congestion when BSC attempts to establish GPRS DL TBF. The measurement is taken at two time points listed below: After RANPS module receives DL request message (EV_RANUMC_DLASS_REQ) sent from RANUMC module, if resource application fails and the cause of failure is RR congestion, the counter increments. The measurement point is A, as shown inFigure 1233.
Usage
Measurement Point
1242
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 1234.
FIGURE 1234 - DATABASE APPLICATION FAILURE DUE TO RR CONGESTION (II)
C901170009 Number of GPRS DL TBF establishment failure due to UPPB-DSP channel congestion
Definition
1243
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. This counter is used to find out the frequency of failures that RANPS applies to database for resource and the cause of failures is UPPBDSP channel congestion when BSC attempts to establish GPRS DL TBF. The measurement is taken at two time points listed below: After
EV_RANUMC_DLASS_REQ
Usage
Measurement Point
module receives DL request message sent from RANUMC module, if resource application fails and the cause of failure is UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown inFigure 1235.
FIGURE 1235 - DATABASE APPLICATION FAILURE CHANNEL CONGESTION (I)
DUE TO
RANPS
UPPB-DSP
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 UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown inFigure 1236.
FIGURE 1236 - DATABASE APPLICATION FAILURE CHANNEL CONGESTION (II)
DUE TO
UPPB-DSP
1244
Number of GPRS DL TBF establishment channel allocate success This counter counts the number of channel allocate success applied by RANPS when BSC attempts to establish GPRS DL TBF. This counter is used to find out the frequency of successful resource application that RANPS sends when BSC attempts to establish GPRS DL TBF. 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 1237.
FIGURE 1237 - SUCCESSFUL RESOURCE APPLICATION
Measurement Point
Number of allocated PDCH for GPRS DL TBF establishment. This counter counts the number of successful allocated PDCH when BSC attempts to establish GPRS DL TBF. This counter is used to find out the number of successful allocated PDCH when BSC attempts to establish GPRS DL TBF.
1245
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 1238.
FIGURE 1238 - SUCCESSFUL RESOURCE APPLICATION
Unit
Times
C901170012 Number of GPRS DL TBF establishment failure due to channel activate failed
Definition Description Usage
Number of GPRS DL TBF establishment failure due to channel activate failed This counter counts the number of PDCH activate failure when BSC establishes GPRS DL TBF. 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). The measurement is taken at two time points listed below: When BSC receives PDCH activation failure message reported by BTS, the counter increments. The measurement point is A, as shown inFigure 1239.
Measurement Point
1246
If 'wait for PDCH activate & connection response' timer expires, and BSC has not received PDCH activate response message reported by BTS, the counter increments.
Unit
Times
C901170013 Number of GPRS DL TBF establishment failure due to BTS connection failed
Definition Description Usage
Number of GPRS DL TBF establishment failure due to BTS connection failed. This counter counts the number of connection failure due to BTS connection failed when BSC establishes GPRS DL TBF. 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). The measurement is taken at two time points listed below: If RANPS module receives connection failed message reported by connection module, and the cause of failure is BTS connection failed, the counter increments. The measurement point is A, as shown inFigure 1240.
FIGURE 1240 - CONNECTION FAILED DUE TO BTS CONNECTION FAILURE
Measurement Point
1247
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
C901170014 Number of GPRS DL TBF establishment failure due to BIU connection failed
Definition Description Usage
Number of GPRS DL TBF establishment failed due to BIU connection failure. This counter counts the number of connection failure due to BIU connection failed when BSC establishes GPRS DL TBF. 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). 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 1241.
FIGURE 1241 - CONNECTION FAILED DUE TO BIU CONNECTION FAILURE
Measurement Point
Unit
Times
1248
Number of GPRS DL TBF channel activate establishment success. This counter counts the number of channel activate establishment success when BSC establishes GPRS DL TBF. This counter is used to find out the frequency of channel activate establishment success when BSC establishes GPRS DL TBF. When RANPS module receives channel activate response message reported by BTS and connection success response message reported by connection module, the counter increments. The measurement point is A as shown inFigure 1242.
FIGURE 1242 - DL GPRS TBF ESTABLISHES CHANNEL ACTIVATION AND ACCESS SUCCESS
Unit
Times
C901170016 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to not receive PIA
Definition Description
Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to not receive PIA This counter counts the number of DL immediate assignment message sending failures when BSC establishes GPRS DL TBF.
1249
Usage
This counter is used to find out the frequency of DL immediate assignment message sending failures when BSC establishes GPRS DL TBF. The measurement is taken at two time points listed below: 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 1243.
FIGURE 1243 - IMMEDIATE ASSIGNMENT SENDING FAILURE
Measurement Point
If 'wait for immediate assignment sending indication' timer expires, and BSC has not received immediate assignment sending message, the counter increments.
Unit
Times
C901170017 Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to UPPB-DSP congestion
Definition Description Related Features
Number of GPRS DL TBF establishment failure on CCCH/PCCCH due to UPPB-DSP congestion. No statistics for this counter is meaningless to GPRS DL TBF. ZGO-03-02-002 Enhancement on Channel Allocation
1250
C901170018 Number of GPRS DL TBF establishment failure on PACCH due to UPPB-DSP congestion
Definition Description Related Features
Number of GPRS DL TBF establishment failure on PACCH due to UPPB-DSP congestion. No statistics for this counter is meaningless to GPRS DL TBF. ZGO-03-02-002 Enhancement on Channel Allocation
Number of GPRS DL TBF establishment success on PCCCH/CCCH. This counter counts the number of successful DL immediate assignment message sending when BSC establishes GPRS DL TBF. This counter is used to find out the frequency of GPRS DL TBF establishment success. 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 1244.
FIGURE 1244 - SUCCESSFUL IMMEDIATE ASSIGNMENT SENDING
Unit
Times
1251
C901170023 Number of GPRS DL TBF resource reallocation failure due to Abis congestion for UL TBF establishment
Definition Description
Number of GPRS DL TBF resource reallocation failure due to Abis congestion for UL TBF establishment. 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. This counter is used to find out the frequency of GPRS DL TBF resource reallocation failure due to Abis congestion. MS has established GPRS DL TBF, and after RANPS module receives message sent from RANU module, if resource application fails due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 1245 .
EV_MAC_UL_ASSIGN_REQ
1252
FIGURE 1245 - RESOURCE APPLICATION FAILURE DUE TO ABIS CONGESTION (ASSIGNED BY UL)
C901170024 Number of GPRS DL TBF resource reallocation failure due to RR congestion for UL TBF establishment
Description Definition
Number of GPRS DL TBF resource reallocation failure due to RR congestion for UL TBF establishment. 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).
This counter is used to find out the frequency of GPRS DL TBF resource reallocation failure due to RR congestion. MS has established GPRS DL TBF, and after RANPS module receives 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 1246.
EV_MAC_UL_ASSIGN_REQ
1253
C901170025 Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment
Definition Description
Number of GPRS DL TBF resource reallocation failure due to UPPBDSP channel congestion for UL TBF establishment 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. This counter is used to find out the frequency of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion.
EV_MAC_UL_ASSIGN_REQ
MS has established GPRS DL TBF, and after RANPS module receives message sent from RANU module, if resource application fails due to UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown in Figure 1247.
1254
FIGURE 1247 - RESOURCE APPLICATION FAILURE DUE TO UPPB-DSP CHANNEL CONGESTION (ASSIGNED BY UL)
C901170026 Number of GPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment
Definition Description
Number of GPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment. After MS establishes GPRS 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 GPRS DL TBF resource reallocation success.
EV_MAC_UL_ASSIGN_REQ
MS has established GPRS DL TBF, and after RANPS module receives message sent from RANU module, if resource application succeeds, the counter increments. The measurement point is A, as shown inFigure 1248.
1255
C901170027 Number of allocated PDCH for GPRS DL TBF resource reallocation due to UL TBF establishment
Definition Description Usage Measurement Point
Number of allocated PDCH for GPRS DL TBF resource reallocation due to UL TBF establishment. This counter counts the number of successfully allocated PDCH when GPRS DL TBF resource is reallocated. This counter is used to find out the number of successfully allocated PDCH when GPRS DL TBF resource is reallocated. MS has established GPRS DL TBF, and after RANPS module receives message sent from RANU module, when resource application succeeds, the counter accumulates the PDTCH number. The measurement point is A, as shown inFigure 1249.
EV_MAC_UL_ASSIGN_REQ
1256
C901170028 Number of GPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment
Definition Description Usage Measurement Point
Number of GPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment This counter counts the number of PDCH activate failure during the process of GPRS DL TBF resource reallocation. This counter is used to find out the frequency of PDCH activate failure during the process of GPRS DL TBF resource reallocation. The measurement is taken at two time points listed below: When BSC receives PDCH activate failure message reported by BTS, the counter increments. The measurement point is A, as shown in Figure 1250.
1257
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
C901170029 Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment
Definition Description
Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment This counter counts the number of connection failure due to BTS connection failure during the process of GPRS DL TBF resource reallocation. 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. The measurement is taken at two time points listed below: 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 1251.
Usage
Measurement Point
1258
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
C901170030 Number of GPRS DL TBF resource reallocation failure due to BIU connection failure for UL TBF establishment
Definition Description
Number of GPRS DL TBF resource reallocation failure due to BIU connection failure for UL TBF establishment This counter counts the number of connection failure due to BIU connection failure during the process of GPRS 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 GPRS DL TBF resource reallocation. 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 1252.
Usage
Measurement Point
1259
Unit
Times
C901170031 Number of GPRS DL TBF resource reallocation success of channel activate and connection for UL TBF establishment
Definition Description Usage Measurement Point
Number of GPRS DL TBF resource reallocation success of channel activate and connection for UL TBF establishment This counter counts the number of channel activate success during the process of GPRS DL TBF resource reallocation. This counter is used to find out the frequency of channel activate success during the process of GPRS DL TBF resource reallocation. 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 1253.
1260
Unit
Times
C901170032 Number of GPRS DL TBF resource reallocation failure due to UL TBF establishment
Definition Description
Number of GPRS DL TBF resource reallocation failure due to UL TBF establishment. No statistics for this counter is meaningless to GPRS DL TBF.
C901170033 Number of GPRS DL TBF resource reallocation success due to UL TBF establishment
Definition Description
Number of GPRS DL TBF resource reallocation success due to UL TBF establishment. No statistics for this counter is meaningless to GPRS DL TBF.
1261
C901170036 Number of GPRS DL TBF resource reallocation failure due to Abis congestion for LLC transmission
Definition Description
Number of GPRS DL TBF resource reallocation failure due to Abis congestion for LLC transmission. 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). 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). 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 1254.
FIGURE 1254 - RESOURCE APPLICATION FAILURE DUE TO ABIS CONGESTION (RESOURCE ADJUSTMENT)
Usage
Measurement Point
1262
C901170037 Number of GPRS DL TBF resource reallocation failure due to RR congestion for LLC transmission
Definition Description
Number of GPRS DL TBF resource reallocation failure due to RR congestion for LLC transmission. 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).
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 1255.
FIGURE 1255 - RESOURCE APPLICATION FAILURE DUE TO RR CONGESTION (RESOURCE ADJUSTMENT)
1263
C901170038 Number of GPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission
Definition Description
Number of GPRS DL TBF resource reallocation failure due to UPPBDSP channel congestion for LLC transmission. 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). 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). 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 1256.
FIGURE 1256 - RESOURCE APPLICATION FAILURE DUE TO UPPB-DSP CHANNEL CONGESTION (RESOURCE ADJUSTMENT)
Usage
Measurement Point
1264
C901170039 Number of GPRS DL TBF resource reallocation success of channel allocation due to LLC transmission
Definition Description
Number of GPRS DL TBF resource reallocation success of channel allocation due to LLC transmission. 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. This counter is used to find out the frequency of resource reallocation success after RANPS receives resource adjustment request during GPRS DL TBF transmission. 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 1257.
FIGURE 1257 SUCCESSFUL RESOURCE APPLICATION (RESOURCE ADJUSTMENT)
Usage
Measurement Point
1265
C901170040 Number of allocated PDCH for GPRS DL TBF resource reallocation due to LLC transmission
Definition Description
Number of allocated PDCH for GPRS DL TBF resource reallocation due to LLC transmission. 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. This counter is used to find out the number of successfully allocated PDCH after RANPS receives resource adjustment request during GPRS DL TBF transmission. 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 1258.
FIGURE 1258 - SUCCESSFUL RESOURCE APPLICATION (RESOURCE ADJUSTMENT)
Usage
Measurement Point
1266
C901170041 Number of GPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission
Definition Description
Number of GPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission. This counter counts the number of PDCH activate failure after BSC receives resource adjustment request during GPRS DL TBF transmission. This counter is used to find out the frequency of PDCH activate failure after BSC receives resource adjustment request during GPRS DL TBF transmission. The measurement is taken at two time points listed below: When BSC receives PDCH activate failure message reported by BTS, the counter increments. The measurement point is A, as shown in Figure 1259.
FIGURE 1259 - PDCH ACTIVATION FAILURE
Usage
Measurement Point
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
1267
C901170042 Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission
Definition Description
Number of GPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission. This counter counts the number of connection failure due to BTS connection failure after BSC receives resource adjustment request during GPRS DL TBF transmission. 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 is taken at two time points listed below: 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 1260.
FIGURE 1260 - CONNECTION FAILED DUE TO BTS CONNECTION FAILURE
Usage
Measurement Point
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
1268
C901170043 Number of GPRS DL TBF resource reallocation failure due to BIU connection failure for LLC transmission
Definition Description
Number of GPRS DL TBF resource reallocation failure due to BIU connection failure for LLC transmission. This counter counts the number of connection failure due to BIU connection failure after BSC receives resource adjustment request during GPRS 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 GPRS DL TBF transmission. 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 1261.
FIGURE 1261 - CONNECTION FAILED DUE TO BIU CONNECTION FAILURE
Usage
Measurement Point
Unit
Times
1269
C901170044 Number of GPRS DL TBF resource reallocation success of channel activate and connection for LLC transmission
Definition Description
Number of GPRS DL TBF resource reallocation success of channel activate and connection for LLC transmission This counter counts the number of channel activate success after BSC receives resource adjustment request during GPRS DL TBF transmission. This counter is used to find out the frequency of channel activate success after BSC receives resource adjustment request during GPRS DL TBF transmission. 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 1262.
FIGURE 1262 - SUCCESSFUL ACTIVATION AND CONNECTION
Usage
Measurement Point
Unit
Times
C901170045 Number of GPRS DL TBF resource reallocation failure due to LLC transmission
Definition
1270
Description
C901170046 Number of GPRS DL TBF resource reallocation success due to LLC transmission
Definition Description
Number of GPRS DL TBF resource reallocation success due to LLC transmission. No statistics for this counter is meaningless to GPRS DL TBF.
Number of GPRS DL TBF release due to flush LL. This counter counts the number of GPRS DL TBF release due to flush LL. This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests due to flush LL received by RANPS. 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 1263.
FIGURE 1263 - RELEASE REQUEST DUE TO FLUSH LL
Unit
Times
1271
Number of GPRS DL TBF release due to GPRS suspend requests. This counter counts the number of GPRS DL TBF release due to GPRS suspend requests. This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests due to suspend requests received by RANPS. 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 1264.
FIGURE 1264 - RELEASE REQUEST DUE TO SUSPEND REQUEST
Unit
Times
Number of GPRS DL TBF forcing release by CS. This counter counts the number of GPRS DL TBF forcing release by CS due to PDCH REL. This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests (EV_RANCCM_PDCH_REL) received by RANPS. 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 1265.
1272
Unit
Times
C901170050 Number of GPRS DL TBF normal release due to user plane requests
Definition Description Usage
Number of GPRS DL TBF normal release due to user plane requests. This counter counts the number of GPRS DL TBF normal release due to normal Release Request by MAC. 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. 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 1266.
FIGURE 1266 - RELEASE REQUEST DUE TO NORMAL RELEASE REQUEST BY MAC
Measurement Point
Unit
Times
1273
C901170051 Number of GPRS DL TBF abnormal release due to user plane requests
Definition Description Usage
Number of GPRS DL TBF abnormal release due to user plane requests. This counter counts the number of GPRS DL TBF abnormal release due to abnormal Release Request by MAC. 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. 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 1267.
FIGURE 1267 - RELEASE REQUEST DUE TO ABNORMAL RELEASE REQUEST BY MAC
Measurement Point
Unit
Times
Number of GPRS DL TBF release due to NSVC unavailability. This counter counts the number of GPRS DL TBF release due to NSVC unavailability. This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests due to NSVC unavailability received by RANPS.
1274
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 1268.
FIGURE 1268 - RELEASE REQUEST DUE TO NSVC UNAVAILABILITY
Unit
Times
Number of GPRS DL TBF release due to BVC unavailability. This counter counts the number of GPRS DL TBF release due to BVC unavailability. This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests due to BVC unavailability received by RANPS. 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 1269 .
FIGURE 1269 - RELEASE REQUEST DUE TO BVC UNAVAILABILITY
Unit
Times
1275
Number of GPRS DL TBF release due to other reasons. This counter counts the number of GPRS DL TBF release due to other reasons. This counter is used to find out the frequency of GPRS DL TBF forcing Release Requests due to other reasons received by RANPS. When RANPS module receives Release Request message (EV_RANUMC_REL_CMD) reported by RANUMC, if the reason of release is others, and GPRS DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 1270.
FIGURE 1270 - RELEASE REQUEST DUE TO OTHER REASONS
Unit
Times
Number of DL GPRS TBF grab resources. This counter counts the number of DL GPRS TBF grab resources. This counter is used to find out the frequency for DL GPRS TBF grabbing other TBF resource. This counter increments while DL GPRS TBF is established during resource adjustment, resource request is successful, and other TBF resource is grabbed. Measurement point is A as shown in Figure 1271.
1276
Number of grab instance by DL GPRS TBF This counter counts the number of grab instance by DL GPRS TBF. This counter is used to find out the frequency for DL GPRS TBF grabbing other TBF resource. 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 1272.
FIGURE 1272 - DL GPRS RESOURCE REQUEST SUCCESS
1277
Number of DL GPRS TBF queuing. This counter counts the number of DL GPRS TBF queuing. This counter is used to find out the frequency for DL GPRS TBF queuing. 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 1273.
FIGURE 1273 - DL GPRS RESOURCE REQUEST SUCCESS
Number of DL GPRS TBF queuing success. This counter counts the number of DL GPRS TBF queuing success. This counter is used to find out the frequency for DL GPRS TBF queuing success. This counter increments while DL GPRS TBF is established during resource adjustment, the instance to be queued successfully assigns resource for user plane, and database is successfully registered. Measurement point is A as shown in Figure 1274.
1278
Number of DL GPRS TBF release TBF during queuing. This counter counts the number of DL GPRS TBF release during queuing. This counter is used to find out the frequency for DL GPRS TBF release during queuing. This counter increments while DL GPRS TBF is released and instance still in queuing state. The measurement point is A as shown inFigure 1275.
FIGURE 1275 - RELEASE DL GPRS TBF
1279
1280
Chapter
24
1281
C901180025 Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment .................................................................. 1298 C901180026 Number of EGPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment ........................................................................... 1299 C901180027 Number of allocated PDCH for EGPRS DL TBF resource reallocation due to UL TBF establishment ............. 1300 C901180028 Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment ........................................................................... 1301 C901180029 Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment ........................................................................... 1302 C901180030 Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for UL TBF establishment ........................................................................... 1303 C901180031 Number of EGPRS DL TBF resource reallocation success of channel activate and connection for UL TBF establishment....................................................................... 1304 C901180032 Number of EGPRS DL TBF resource reallocation failure due to UL TBF establishment ................................. 1304 C901180033 Number of EGPRS DL TBF resource reallocation success due to UL TBF establishment ............................... 1305 C901180036 Number of EGPRS DL TBF resource reallocation failure due to Abis congestion for LLC transmission ............ 1305 C901180037 Number of EGPRS DL TBF resource reallocation failure due to RR congestion for LLC transmission .............. 1306 C901180038 Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission ............................................................................. 1307 C901180039 Number of EGPRS DL TBF resource reallocation success of channel allocation due to LLC transmission......... 1308 C901180040 Number of allocated PDCH for EGPRS DL TBF resource reallocation due to LLC transmission.................... 1309 C901180041 Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission ............................................................................. 1310 C901180042 Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission ............................................................................. 1311 C901180043 Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for LLC transmission ............................................................................. 1312 C901180044 Number of EGPRS DL TBF resource reallocation success of channel activate and connection for LLC transmission ............................................................................. 1313 C901180045 Number of EGPRS DL TBF resource reallocation failure due to LLC transmission........................................ 1314 C901180046 Number of EGPRS DL TBF resource reallocation success due to LLC transmission ...................................... 1314 C901180047 Number of EGPRS DL TBF release due to flush LL ............................................................................... 1314 C901180048 Number of EGPRS DL TBF release due to EGPRS suspend requests .......................................................... 1315 C901180049 Number of EGPRS DL TBF forcing release by CS............................................................................... 1316 C901180050 Number of EGPRS DL TBF normal release due to user plane requests ....................................................... 1316
1282
C901180051 Number of EGPRS DL TBF abnormal release due to user plane requests.................................................... 1317 C901180052 Number of EGPRS DL TBF release due to NSVC unavailability ................................................................ 1318 C901180053 Number of EGPRS DL TBF release due to BVC unavailability ................................................................ 1318 C901180054 Number of EGPRS DL TBF release due to other reasons........................................................................ 1319 C901180055 Number of DL EGPRS TBF grab resources......... 1319 C901180056 Number of grab instance by DL EGPRS TBF ............................................................................. 1320 C901180057 Number of DL EGPRS TBF queuing ................ 1321 C901180058 Number of DL EGPRS TBF queuing success............................................................................. 1321 C901180059 Number of DL EGPRS TBF release TBF during queuing ....................................................................... 1322
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.
Number of EGPRS DL TBF establishment requests on CCCH/PCCCH. This counter counts the number of DL establishment requests received by control plane when BSC initially attempts to establish EGPRS 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 EGPRS DL TBF. When RANPS module receives the DL request (EV_RANUMC_DLASS_REQ) sent from RANUMC module, the counter increments. This measurement point is A, as shown in Figure 1276.
Usage
Measurement Point
1283
Unit
Times
Number of EGPRS DL TBF establishment requests on PACCH. This counter counts the number of establishing EGPRS 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 EGPRS UL TBF.
EV_MAC_DL_ASSIGN_REQ
After MS has established EGPRS UL TBF, RANPS module receives message sent from RANU module, the counter increments. This measurement point is A, as shown inFigure 1277.
Unit
Times
1284
C901180005 Number of EGPRS DL TBF establishment failure due to not support DTM
Definition Description
Number of EGPRS DL TBF establishment failure due to not support DTM. No statistics temporarily.
Number of EGPRS DL TBF establishment failure due to Abis congestion. 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 EGPRS DL TBF. 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 EGPRS DL TBF. The measurement is taken at two time points listed below: After RANPS module receives DL request message (EV_RANUMC_DLASS_REQ) sent from RANUMC module, if resource
Usage
Measurement Point
1285
application fails and the cause of failure is Abis congestion, the counter increments. The measurement point is A, as shown in Figure 1278.
FIGURE 1278 - DATABASE APPLICATION FAILURE DUE TO ABIS CONGESTION (I)
After MS establishes EGPRS UL TBF, RANPS module receives message sent from RANU module, if resource application fails and the cause of failure is Abis congestion, the counter increments. The measurement point is A, as shown in Figure 1279.
EV_MAC_DL_ASSIGN_REQ
1286
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. There are three causes for RR congestion: MS per channel (number of MS reaches the peak in each channel), TAI/TFI (no TAI or TFI) and no PDCH (no PS channel). This counter is used to find out the frequency of failures that RANPS 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 RANPS applies to database for resource and the cause of failures is RR congestion when BSC attempts to establish GPRS DL TBF. The measurement is taken at two time points listed below: After RANPS module receives DL request message (EV_RANUMC_DLASS_REQ) sent from RANUMC module, if resource application fails and the cause of failure is RR congestion, the counter increments. The measurement point is A, as shown inFigure 1280.
FIGURE 1280 - DATABASE APPLICATION FAILURE DUE TO RR CONGESTION (I)
Measurement Point
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 1281.
FIGURE 1281 - DATABASE APPLICATION FAILURE DUE TO RR CONGESTION (II)
1287
C901180009 Number of EGPRS DL TBF establishment failure due to UPPB-DSP channel congestion
Definition Description
Number of EGPRS DL TBF establishment failure due to UPPB-DSP channel congestion. 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 EGPRS DL TBF. This counter is used to find out the frequency of failures that RANPS applies to database for resource and the cause of failures is UPPBDSP channel congestion when BSC attempts to establish EGPRS DL TBF. The measurement is taken at two time points listed below: After RANPS module receives DL request message (EV_RANUMC_DLASS_REQ) sent from RANUMC module, if resource application fails and the cause of failure is UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown inFigure 1282.
FIGURE 1282 - DATABASE APPLICATION FAILURE CHANNEL CONGESTION (I)
DUE TO
Usage
Measurement Point
UPPB-DSP
After MS establishes EGPRS UL TBF, RANPS module receives message sent from RANU module, if resource application fails and the cause of failure is UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown inFigure 1283.
EV_MAC_DL_ASSIGN_REQ
1288
DUE TO
UPPB-DSP
Number of EGPRS DL TBF establishment channel allocate success. This counter counts the number of channel allocate success applied by RANPS when BSC attempts to establish EGPRS DL TBF. This counter is used to find out the frequency of successful resource application that RANPS sends when BSC attempts to establish EGPRS DL TBF. 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 1284.
FIGURE 1284 - SUCCESSFUL RESOURCE APPLICATION
Measurement Point
Unit
Times
1289
Related Features
Number of allocated PDCH for EGPRS DL TBF establishment. This counter counts the number of successful allocated PDCH when BSC attempts to establish EGPRS DL TBF. This counter is used to find out the number of successful allocated PDCH when BSC attempts to establish EGPRS DL TBF. module receives DL request message sent from RANUMC module, when resource application succeeds, the counter accumulates the PDCH number. The measurement point is A, as shown inFigure 1285.
EV_RANUMC_DLASS_REQ
After
RANPS
C901180012 Number of EGPRS DL TBF establishment failure due to channel activate failed
Definition Description
Number of EGPRS DL TBF establishment failure due to channel activate failed. This counter counts the number of PDCH activate failure when BSC establishes EGPRS DL TBF.
1290
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). The measurement is taken at two time points listed below: When BSC receives PDCH activation failure message reported by BTS, the counter increments. The measurement point is A, as shown inFigure 1286.
FIGURE 1286 - PDCH ACTIVATION FAILURE
Measurement Point
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
C901180013 Number of EGPRS DL TBF establishment failure due to BTS connection failed
Definition Description Usage
Number of EGPRS DL TBF establishment failed due to BTS connection failure. This counter counts the number of connection failure due to BTS connection failed when BSC establishes EGPRS DL TBF. 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). The measurement is taken at two time points listed below: 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 1287.
Measurement Point
1291
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
C901180014 Number of EGPRS DL TBF establishment failure due to BIU connection failed
Definition Description Usage
Number of EGPRS DL TBF establishment failed due to BIU connection failure. This counter counts the number of connection failure due to BIU connection failed when BSC establishes EGPRS DL TBF. 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). 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 1288.
Measurement Point
1292
Unit
Times
Number of EGPRS DL TBF channel activate establishment success. This counter counts the number of channel activate establishment success when BSC establishes EGPRS DL TBF. This counter is used to find out the frequency of channel activate establishment success when BSC establishes EGPRS DL TBF. 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 1289.
FIGURE 1289 - IMMEDIATE ASSIGNMENT SENDING FAILURE
Unit
Times
1293
C901180016 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to not receive PIA
Definition Description Usage
Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to not receive PIA This counter counts the number of DL immediate assignment message sending failures when BSC establishes EGPRS DL TBF. This counter is used to find out the frequency of DL immediate assignment message sending failures when BSC establishes EGPRS DL TBF. The measurement is taken at two time points listed below: 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 1290.
FIGURE 1290 - SUCCESSFUL IMMEDIATE ASSIGNMENT SENDING
Measurement Point
If 'wait for immediate assignment sending indication' timer expires, and BSC has not received immediate assignment sending message, the counter increments.
Unit
Times
1294
C901180017 Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to UPPB-DSP congestion
Definition Description
Number of EGPRS DL TBF establishment failure on CCCH/PCCCH due to UPPB-DSP congestion. No statistics for this counter is meaningless to EGPRS DL TBF.
C901180018 Number of EGPRS DL TBF establishment failure on PACCH due to UPPB-DSP congestion
Definition Description
Number of EGPRS DL TBF establishment failure on PACCH due to UPPB-DSP congestion. No statistics for this counter is meaningless to EGPRS DL TBF.
Number of EGPRS DL TBF establishment success on PCCCH/CCCH. This counter counts the number of successful DL immediate assignment message sendings when BSC establishes EGPRS DL TBF. This counter is used to find out the frequency of EGPRS DL TBF establishment success.
1295
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 inFigure 1291.
FIGURE 1291 - RESOURCE APPLICATION FAILURE DUE TO ABIS CONGESTION (ASSIGNED BY UL)
Unit
Times
C901180023 Number of EGPRS DL TBF resource reallocation failure due to Abis congestion for UL TBF establishment
Definition
1296
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. This counter is used to find out the frequency of EGPRS DL TBF establishment success. MS has established EGPRS DL TBF, and after RANPS module receives EV_MAC_UL_ASSIGN_REQ message sent from RANU module, if resource application fails due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 1292.
FIGURE 1292 - RESOURCE APPLICATION FAILURE DUE TO ABIS CONGESTION (ASSIGNED BY UL)
C901180024 Number of EGPRS DL TBF resource reallocation failure due to RR congestion for UL TBF establishment
Definition Description
Number of EGPRS DL TBF resource reallocation failure due to RR congestion for UL TBF establishment. 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.
1297
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
This counter is used to find out the frequency of EGPRS DL TBF resource reallocation failure due to RR congestion. MS has established EGPRS DL TBF, and after RANPS module receives EV_MAC_UL_ASSIGN_REQ message sent from RANU module, if resource application fails due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 1293.
FIGURE 1293 - RESOURCE APPLICATION FAILURE DUE TO RR CONGESTION (ASSIGNED BY UL)
C901180025 Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment
Definition Description
Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for UL TBF establishment 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.
1298
This counter is used to find out the frequency of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion. MS has established EGPRS DL TBF, and after RANPS module receives EV_MAC_UL_ASSIGN_REQ message sent from RANU module, if resource application fails due to UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown inFigure 1294.
FIGURE 1294 - RESOURCE APPLICATION FAILURE DUE TO UPPB-DSP CONGESTION (ASSIGNED BY UL)
C901180026 Number of EGPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment
Definition Description
Number of EGPRS DL TBF resource reallocation success of channel allocation due to UL TBF establishment After MS establishes EGPRS 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 EGPRS DL TBF resource reallocation success. MS has established EGPRS DL TBF, and after RANPS module receives EV_MAC_UL_ASSIGN_REQ message sent from RANU module, if resource application succeeds, the counter increments. The measurement point is A, as shown in Figure 1295.
1299
C901180027 Number of allocated PDCH for EGPRS DL TBF resource reallocation due to UL TBF establishment
Definition Description Usage Measurement Point
Number of allocated PDCH for EGPRS DL TBF resource reallocation due to UL TBF establishment. This counter counts the number of successfully allocated PDCH when EGPRS DL TBF resource is reallocated. This counter is used to find out the number of successfully allocated PDCH when EGPRS DL TBF resource is reallocated. MS has established EGPRS DL TBF, and after RANPS module receives EV_MAC_UL_ASSIGN_REQ message sent from RANU module, when resource application succeeds, the counter accumulates the PDTCH number. The measurement point is A, as shown inFigure 1296.
1300
C901180028 Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment
Definition Description Usage Measurement Point
Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for UL TBF establishment This counter counts the number of PDCH activate failure during the process of EGPRS DL TBF resource reallocation. This counter is used to find out the frequency of PDCH activate failure during the process of EGPRS DL TBF resource reallocation. The measurement is taken at two time points listed below: 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.
1301
Unit
Times
C901180029 Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment
Definition Description
Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for UL TBF establishment This counter counts the number of connection failure due to BTS connection failure during the process of EGPRS DL TBF resource reallocation. 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. The measurement is taken at two time points listed below: 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 1298.
FIGURE 1298 - CONNECTION FAILED DUE TO BTS CONNECTION FAILURE
Usage
Measurement Point
1302
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
C901180030 Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for UL TBF establishment
Definition Description
Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for UL TBF establishment. This counter counts the number of connection failure due to BIU connection failure during the process of EGPRS 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 EGPRS DL TBF resource reallocation. 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 1299.
FIGURE 1299 - CONNECTION FAILED DUE TO BIU CONNECTION FAILURE
Usage
Measurement Point
Unit
Times
1303
C901180031 Number of EGPRS DL TBF resource reallocation success of channel activate and connection for UL TBF establishment
Definition Description Usage Measurement Point
Number of EGPRS DL TBF resource reallocation success of channel activate and connection for UL TBF establishment This counter counts the number of channel activate success during the process of EGPRS DL TBF resource reallocation. This counter is used to find out the frequency of channel activate success during the process of EGPRS DL TBF resource reallocation. 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 1300.
FIGURE 1300 - SUCCESSFUL ACTIVATION AND CONNECTION
Unit
Times
C901180032 Number of EGPRS DL TBF resource reallocation failure due to UL TBF establishment
Definition Description
Number of EGPRS DL TBF resource reallocation failure due to UL TBF establishment. No statistics for this counter is meaningless to EGPRS DL TBF.
1304
Related Features
C901180033 Number of EGPRS DL TBF resource reallocation success due to UL TBF establishment
Definition Description Related Features
Number of EGPRS DL TBF resource reallocation success due to UL TBF establishment. No statistics for this counter is meaningless to EGPRS DL TBF. ZGO-03-02-002 Enhancement on Channel Allocation
C901180036 Number of EGPRS DL TBF resource reallocation failure due to Abis congestion for LLC transmission
Definition Description
Number of EGPRS DL TBF resource reallocation failure due to Abis congestion for LLC transmission. During EGPRS 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 EGPRS 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 RANPS receives resource adjustment request during EGPRS DL TBF transmission (the cause of database application failure is Abis congestion). 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 1301 .
Usage
Measurement Point
1305
FIGURE 1301 - RESOURCE APPLICATION FAILURE DUE TO ABIS CONGESTION (RESOURCE ADJUSTMENT)
C901180037 Number of EGPRS DL TBF resource reallocation failure due to RR congestion for LLC transmission
Definition Description
Number of EGPRS DL TBF resource reallocation failure due to RR congestion for LLC transmission. During EGPRS 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 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 RANPS receives resource adjustment request during EGPRS DL TBF transmission (the cause of database application failure is RR congestion). 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 inFigure 1302 .
Measurement Point
1306
C901180038 Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission
Definition Description
Number of EGPRS DL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission. During EGPRS 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 EGPRS 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 RANPS receives resource adjustment request during EGPRS DL TBF transmission (the cause of database application failure is UPPB-DSP channel congestion). 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 inFigure 1303.
Usage
Measurement Point
1307
FIGURE 1303 - RESOURCE APPLICATION FAILURE DUE TO UPPB-DSP CHANNEL CONGESTION (RESOURCE ADJUSTMENT)
C901180039 Number of EGPRS DL TBF resource reallocation success of channel allocation due to LLC transmission
Definition Description
Number of EGPRS DL TBF resource reallocation success of channel allocation due to LLC transmission. During EGPRS 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 receiving the message. This counter counts the number of resource reallocation success after RANPS receives resource adjustment request during EGPRS DL TBF transmission. This counter is used to find out the frequency of resource reallocation success after RANPS receives resource adjustment request during EGPRS DL TBF transmission. 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 1304.
Usage
Measurement Point
1308
C901180040 Number of allocated PDCH for EGPRS DL TBF resource reallocation due to LLC transmission
Definition Description
Number of allocated PDCH for EGPRS DL TBF resource reallocation due to LLC transmission. During EGPRS 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 EGPRS DL TBF transmission. This counter is used to find out the number of successfully allocated PDCH after RANPS receives resource adjustment request during EGPRS DL TBF transmission. 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 inFigure 1305.
Usage
Measurement Point
1309
C901180041 Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission
Definition Description
Number of Number of EGPRS DL TBF resource reallocation failure due to channel activate failure for LLC transmission. This counter counts the number of PDCH activate failure after BSC receives resource adjustment request during EGPRS DL TBF transmission. This counter is used to find out the frequency of PDCH activate failure after BSC receives resource adjustment request during EGPRS DL TBF transmission. The measurement is taken at two time points listed below: When BSC receives PDCH activate failure message reported by BTS, the counter increments. The measurement point is A, as shown inFigure 1306.
Usage
Measurement Point
1310
If 'wait for PDCH activate & connection response' timer expires, and BSC has not received PDCH activate response message reported by BTS, the counter increments.
C901180042 Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission
Definition Description
Number of EGPRS DL TBF resource reallocation failure due to BTS connection failure for LLC transmission. This counter counts the number of connection failure due to BTS connection failure after BSC receives resource adjustment request during EGPRS DL TBF transmission. 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. The measurement is taken at two time points listed below: 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 1307.
Usage
Measurement Point
1311
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
C901180043 Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for LLC transmission
Definition Description
Number of EGPRS DL TBF resource reallocation failure due to BIU connection failure for LLC transmission. This counter counts the number of connection failure due to BIU connection failure after BSC receives resource adjustment request during EGPRS 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 EGPRS DL TBF transmission. 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 1308.
Usage
Measurement Point
1312
Unit
Times
C901180044 Number of EGPRS DL TBF resource reallocation success of channel activate and connection for LLC transmission
Definition Description
Number of EGPRS DL TBF resource reallocation success of channel activate and connection for LLC transmission This counter counts the number of channel activate success after BSC receives resource adjustment request during EGPRS DL TBF transmission. This counter is used to find out the frequency of channel activate success after BSC receives resource adjustment request during EGPRS DL TBF transmission. 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 1309.
FIGURE 1309 - SUCCESSFUL ACTIVATION AND CONNECTION
Usage
Measurement Point
1313
Unit
Times
C901180045 Number of EGPRS DL TBF resource reallocation failure due to LLC transmission
Definition Description Related Features
Number of EGPRS DL TBF resource reallocation failure due to LLC transmission. No statistics for this counter is meaningless to EGPRS DL TBF. ZGO-03-02-002 Enhancement on Channel Allocation
C901180046 Number of EGPRS DL TBF resource reallocation success due to LLC transmission
Definition Description Related Features
Number of EGPRS DL TBF resource reallocation success due to LLC transmission. No statistics for this counter is meaningless to EGPRS DL TBF. ZGO-03-02-002 Enhancement on Channel Allocation
Number of EGPRS DL TBF release due to flush LL. This counter counts the number of EGPRS DL TBF release due to flush LL. This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests due to flush LL received by RANPS.
1314
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 EGPRS DL TBF exists, the counter increments. The measurement point is A, as shown in Figure 1310.
FIGURE 1310 - RELEASE REQUEST DUE TO FLUSH LL
Unit
Times
Number of EGPRS DL TBF release due to EGPRS suspend requests. This counter counts the number of EGPRS DL TBF release due to EGPRS suspend requests. This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests due to suspend requests received by RANPS. When RANPS module receives Release Request message (EV_RANUMC_REL_CMD) reported by RANUMC, if the cause of release is SUSPEND, and EGPRS DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 1311.
FIGURE 1311 - RELEASE REQUEST DUE TO SUSPEND REQUEST
Measurement Point
Unit
Times
1315
Number of EGPRS DL TBF forcing release by CS. This counter counts the number of EGPRS DL TBF forcing release by CS due to PDCH REL. This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests (EV_RANCCM_PDCH_REL) received by RANPS. When RANPS module receives Release Request message (EV_RANCCM_PDCH_REL) reported by RANCCM module, if EGPRS DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 1312.
FIGURE 1312 - RELEASE REQUEST DUE TO PDCH REL
Unit
Times
C901180050 Number of EGPRS DL TBF normal release due to user plane requests
Definition Description Usage
Number of EGPRS DL TBF normal release due to user plane requests. This counter counts the number of EGPRS DL TBF abnormal release due to abnormal Release Request by MAC. 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 RANPS. 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 EGPRS DL TBF exists,
Measurement Point
1316
BY
Unit
Times
C901180051 Number of EGPRS DL TBF abnormal release due to user plane requests
Definition Description Usage
Number of EGPRS DL TBF abnormal release due to user plane requests This counter counts the number of EGPRS DL TBF abnormal release due to abnormal Release Request by MAC. 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 RANPS. 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 EGPRS DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 1314.
FIGURE 1314 - RELEASE REQUEST BY MAC
DUE TO
Measurement Point
Unit
Times
1317
Number of EGPRS DL TBF release due to NSVC unavailability. This counter counts the number of EGPRS DL TBF release due to NSVC unavailability. This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests due to NSVC unavailability received by RANPS. When RANPS module receives Release Request message (EV_RANUMC_REL_CMD) reported by RANUMC, if the cause of release is NSVC unavailability, and EGPRS DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 1315.
FIGURE 1315 - RELEASE REQUEST
DUE TO
Measurement Point
NVSC UNAVAILABILITY
Unit
Times
Number of EGPRS DL TBF release due to BVC unavailability. This counter counts the number of EGPRS DL TBF release due to BVC unavailability. This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests due to BVC unavailability received by RANPS. When RANPS module receives Release Request message (EV_RANUMC_REL_CMD) reported by RANUMC, 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 1316.
Measurement Point
1318
Unit
Times
Number of EGPRS DL TBF release due to other reasons. This counter counts the number of EGPRS DL TBF release due to other reasons. This counter is used to find out the frequency of EGPRS DL TBF forcing Release Requests due to other reasons received by RANPS. When RANPS module receives Release Request message (EV_RANUMC_REL_CMD) reported by RANUMC, if the reason of release is others, and EGPRS DL TBF exists, the counter increments. The measurement point is A, as shown inFigure 1317 .
FIGURE 1317 - RELEASE REQUEST DUE TO OTHER REASONS
Unit
Times
This counter counts the number of downlink EGRPS TBF's grabbing resources.
1319
The counter is used to find out the frequency of downlink EGPRS TBF grabbing other TBF resources. During the downlink EGPRS TBF establishment and resource adjustment process, if the resource request succeeds and the other TBF resources is grabbed, the counter increments. The measurement point is A, as shown in Figure 1318.
FIGURE 1318 DOWNLINK EGPRS REQUESTING RESOURCE SUCCESSFULLY
This counter counts the number of instances grabbed by downlink EGRPS TBF. The counter is used to find out the frequency of downlink EGPRS TBF grabbing other TBF resources. During the downlink EGPRS TBF establishment and resource adjustment process, if the resource request succeeds and the other TBF resources is grabbed, the counter counts the number of grabbed instances. The measurement point is A, as shown in Figure 1319.
FIGURE 1319 DOWNLINK EGPRS REQUESTING RESOURCE SUCCESSFULLY
1320
This counter counts the number of downlink EGRPS TBF's queuing. The counter is used to find out the frequency of downlink EGPRS TBF's queuing. 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 1320.
FIGURE 1320 DOWNLINK EGPRS REQUESTING RESOURCE SUCCESSFULLY
This counter counts the number of downlink EGRPS TBF's queuing success. The counter is used to find out the frequency of downlink EGPRS TBF's queuing success. 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,
1321
This counter counts the number of downlink EGRPS TBF's releasing TBF during queuing. The counter is used to find out the frequency of downlink EGPRS TBF's releasing TBF during queuing. 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 1322.
FIGURE 1322 RELEASING DOWNLINK EGPRS TBF
1322
Chapter
25
1323
C901190024 Number of cell success for GPRS UL assignment due to TWO PHASE access .............................................. 1346 C901190025 Number of cell success for GPRS UL assignment due to short access........................................................ 1347 C901190026 Number of allocated PDCH for GPRS UL TBF establishment .................................................................. 1348 C901190027 Number of GPRS UL TBF establishment failure due to channel activate failed.......................................... 1350 C901190028 Number of GPRS UL TBF establishment failure due to BTS connection failed ........................................... 1351 C901190029 Number of GPRS UL TBF establishment failure due to BIU connection failed ........................................... 1352 C901190030 Number of GPRS UL TBF channel activate establishment success ........................................................... 1352 C901190031 Number of GPRS UL TBF establishment failure due to not receive PIA.................................................... 1353 C901190032 Number of GPRS UL TBF establisment failure on PCCCH/CCCH due to UPPB-DSP congestion ....................... 1354 C901190033 Number of GPRS UL TBF establisment failure on PACCH due to UPPB-DSP congestion ................................ 1355 C901190034 Number of GPRS UL TBF establishment success on PCCCH/CCCH............................................................ 1355 C901190035 Number of GPRS UL TBF establishment success on PACCH..................................................................... 1356 C901190038 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for DL TBF establishment ........................................................................... 1356 C901190039 Number of GPRS UL TBF resource reallocation failure due to RR congestion for DL TBF establishment......... 1357 C901190040 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for DL TBF establishment .................................................................. 1358 C901190041 Number of GPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment ........................................................................... 1359 C901190042 Number of allocated PDCH for GPRS UL TBF resource reallocation due to DL TBF establishment................ 1360 C901190043 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for DL TBF establishment ........................................................................... 1361 C901190044 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for DL TBF establishment ........................................................................... 1362 C901190045 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for DL TBF establishment ........................................................................... 1363 C901190046 Number of GPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment....................................................................... 1364 C901190047 Number of GPRS UL TBF resourse reallocation failure due to DL TBF establishment ................................. 1365 C901190048 Number of GPRS UL TBF resourse reallocation success due to DL TBF establishment ............................... 1365 C901190051 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission ............ 1365 C901190052 Number of GPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission .............. 1366 C901190053 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission ........................................................................ 1367
1324
C901190054 Number of GPRS UL TBF resource reallocation success of channel allocation due to LLC transmission......... 1368 C901190055 Number of allocated PDCH for GPRS UL TBF resource reallocation due to LLC transmission ...................... 1369 C901190056 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for LLC transmission ............................................................................. 1370 C901190057 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for LLC transmission ............................................................................. 1371 C901190058 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for LLC transmission ............................................................................. 1372 C901190059 Number of GPRS UL TBF resourse reallocation success of channel activate for LLC transmission................ 1373 C901190060 Number of GPRS UL TBF resourse reallocation failure due to LLC transmission........................................ 1373 C901190061 Number of GPRS UL TBF resourse reallocation success due to LLC transmission ...................................... 1374 C901190062 Number of GPRS UL TBF resource reallocation requests for resource request.......................................... 1374 C901190064 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for resource request ............ 1374 C901190065 Number of GPRS UL TBF resource reallocation failure due to RR congestion for resource request .............. 1375 C901190066 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for resource request ........................................................................... 1376 C901190067 Number of GPRS UL TBF resource reallocation success due to resource request ...................................... 1377 C901190068 Number of allocated PDCH for GPRS UL TBF resource reallocation due to resource request ...................... 1378 C901190069 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for resource request ........................................................................ 1379 C901190070 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for resource request ........................................................................ 1380 C901190071 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for resource request ........................................................................ 1381 C901190072 Number of GPRS UL TBF resource reallocation success of channel activate and connection for resource request ........................................................................... 1382 C901190073 Number of GPRS UL TBF resourse reallocation failure due to resource request ........................................ 1383 C901190074 Number of GPRS UL TBF resourse reallocation success due to resource request ...................................... 1383 C901190075 Number of GPRS UL TBF release due to flush LL ............................................................................... 1383 C901190076 Number of GPRS UL TBF release due to GPRS suspend requests .......................................................... 1384 C901190077 Number of GPRS UL TBF forcing release by CS............................................................................... 1385 C901190078 Number of GPRS UL TBF normal release due to user plane requests ....................................................... 1385 C901190079 Number of GPRS UL TBF abnormal release due to user plane requests.................................................... 1386 C901190080 Number of GPRS UL TBF release due to NSVC unavailability ................................................................ 1387
1325
C901190081 Number of GPRS UL TBF release due to BVC unavailability .................................................................... 1387 C901190082 Number of GPRS UL TBF release due to other reasons........................................................................ 1388 C901190083 Number of UL GPRS TBF grab resources......... 1389 C901190084 Number of grab instance by UL GPRS TBF......... 1389 C901190085 Number of UL GPRS TBF queuing .................. 1390 C901190086 Number of UL GPRS TBF queuing success......... 1391 C901190087 Number of UL GPRS TBF release TBF during queuing ....................................................................... 1391
Overview
UL GPRS data TBF statistics collects the information about the establishment, maintain and release of UL GPRS TBF. The statistic unit is cell.
Number of GPRS UL TBF establishment requests on CCCH. This counter counts the number of channel requests on CCCH when MS using GPRS service. This counter is used to find out the frequency of channel requests on CCCH when MS attempts using GPRS service. When BSC receives channel requests on CCCH from MS, the counter increments. The measurement point is A, as shown inFigure 1323.
1326
Usage
Times
Number of EGPRS UL TBF establishment requests on CCCH. This counter is not meaningful in UL GPRS TBF and is not used.
Number of GPRS UL TBF establishment requests on PCCCH. This counter counts the number of packet channel requests on PCCCH when MS attempts using GPRS service. This counter is used to find out the frequency of channel requests on PCCCH when MS attempts using GPRS service. When BSC receives channel requests on PCCCH from MS, the counter increments. The measurement point is A, as shown inFigure 1324.
1327
Unit
Times
Number of EGPRS UL TBF establishment requests on PCCCH. This counter is not meaningful in UL GPRS TBF statistic, and is not used.
Number of GPRS UL TBF establishment requests on PACCH. The counter counts the number of UL GPRS TBF establishment attempts on PACCH. 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.
1328
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 1325 .
FIGURE 1325 - PACKET CHANNEL REQUEST
Unit
Times
C901190007 Number of cell attempts for UL assignment due to ONE PHASE access
Definition Description
Number of cell attempts for UL assignment due to ONE PHASE access 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. This counter is used to find out the number of UL GPRS TBF establishment attempts due to one phase access. The counter accumulates at the following two time points: If BSC receives channel requests from MS on CCCH due to one phase access, the counter increments. The measurement point is A, as shown inFigure 1326.
1329
ON
CCCH
DUE TO
ONE PHASE
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 1327.
FIGURE 1327 - PACKET CHANNEL REQUESTS PHASE ACCESS
ON
CCCH
DUE TO
ONE
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.
1330
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. 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. If BSC receives channel requests on PCCCH from MS due to single block packet access. The measurement point is A, as shown inFigure 1328.
FIGURE 1328 - CHANNEL REQUEST
DUE TO
Usage
Measurement Point
Unit
Times
Number of cell attempts for UL assignment due to response paging. This counter counts the number of packet channel requests when MS attempting UL GPRS TBF establishment due to response paging. This counter is used to find out the number of packet channel requests when MS attempting UL GPRS TBF establishment due to response paging. When BSC receives channel requests on PCCCH from MS due to response paging, the counter increments. The measurement point is A, as shown inFigure 1329.
Usage
Measurement Point
1331
Unit
Times
Number of cell attempts for UL assignment due to cell updating. This counter counts the number of packet channel requests when MS attempting UL GPRS TBF establishment due to cell update. This counter is used to find out the number of packet channel requests when MS attempting UL GPRS TBF establishment due to cell update. When BSC receives channel requests on PCCCH from MS duet to cell update, the counter increments. The measurement point is A, as shown inFigure 1330 .
FIGURE 1330 - CHANNEL REQUESTS
DUE TO
Measurement Point
CELL UPDATE
Unit
Times
1332
Number of cell attempts for UL assignment due to mobility management The counter counts the number of packet channel requests on PCCCH when MS attempting UL GPRS TBF establishment due to mobile management. This counter is used to find out the number of packet channel requests when MS attempting UL GPRS TBF establishment due to mobile management. 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 1331.
FIGURE 1331 - CHANNEL REQUEST DUE TO MOBILE MANAGEMENT
Usage
Measurement Point
Unit
C901190012 Number of cell attempts for UL assignment due to TWO PHASE access
Number of cell attempts for UL assignment due to TWO PHASE access 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. This counter is used to find out the number of UL GPRS TBF establishment attempts due to two phase access.
Definition Description
Usage
1333
Measurement Point
The counter accumulates at the following two time points: 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 1332.
FIGURE 1332 - 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 1333.
FIGURE 1333 - PACKET CHANNEL REQUESTS ON PCCCH DUE TO TWO PHASE ACCESS
1334
Description
This counter counts the number of packet channel requests on PCCCH when MS attempting UL GPRS TBF establishment due to short access. This counter is used to find out the number of UL GPRS TBF establishment attempts due to short access. If BSC receives packet channel requests on PCCCH from MS on PCCCH due to short access, the counter increments. The measurement point is A, as shown inFigure 1334.
FIGURE 1334 - PACKET CHANNEL REQUESTS ON PCCCH DUE TO SHORT ACCESS
Unit
Times
Number of GPRS UL TBF establishment failure due to Abis congestion. The counter records the number of DB resource application failure when attempting UL GPRS TBF establishment due to Abis congestion. This counter is used to find out the number of DB resource application failure when attempting UL GPRS TBF establishment due to Abis congestion. The counter accumulates at the following three time points: If PS control plane receives channel requests from MS on CCCH and fails to apply for DB resource due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 1335.
Usage
Measurement Point
1335
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 1336.
FIGURE 1336 - 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 1337.
FIGURE 1337 - DB RESOURCE REQUESTS FAILURE DUE TO ABIS CONGESTION (DL GPRS TBF ALREADY ESTABLISHED)
1336
Number of GPRS UL TBF establishment failure due to RR congestion. 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. This counter is used to find out the number of DB resource application failure when attempting UL GPRS TBF establishment due to RR congestion. The counter accumulates at the following three time points: If PS control plane receives channel requests from MS on CCCH and fails to apply for DB resource due to RR congestion, the counter increments. The measurement point is A, as shown inFigure 1338.
FIGURE 1338 - DB RESOURCE REQUESTS FAILURE DUE TO RR CONGESTION (CCCH)
Usage
Measurement Point
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 1339.
1337
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 1340.
FIGURE 1340 - DB RESOURCE REQUESTS FAILURE DUE TO ABIS CONGESTION (DL GPRS TBF ALREADY ESTABLISHED)
C901190017 Number of GPRS UL TBF establishment failure due to UPPB-DSP channel congestion
Definition
1338
Description
The counter records the number of DB resource application failure when attempting UL GPRS TBF establishment due to UPPB-DSP channel congestion. 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. The counter accumulates at the following three time points: If PS control plane receives channel requests from MS on CCCH and fails to apply for DB resource due to UPPB-DSP channel congestion, the counter increments. The measurement point is A, as shown in Figure 1341.
FIGURE 1341 DB RESOURCE REQUESTS FAILURE DUE TO UPPB-DSP CHANNEL CONGESTION (CCCH)
Usage
Measurement Point
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 1342.
FIGURE 1342 - 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 1343.
1339
FIGURE 1343 - DB RESOURCE REQUESTS FAILURE DUE TO DPPB-DSP CONGESTION (DL GPRS TBF ALREADY ESTABLISHED)
Number of GPRS UL TBF establishment channel allocate success. This counter counts the number of DB resource request successes when attempting UL GPRS TBF establishment. This counter is used to find out the number of DB resource request successes when attempting UL GPRS TBF establishment. The counter accumulates at the following three time points: 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 1344.
1340
If PS control panel receives channel requests from MS on PCCCH and succeed in applying for DB resource, the counter increments. The measurement point is A, as shown inFigure 1345.
FIGURE 1345 - DB RESOURCE REQUEST SUCCESSES (PCCCH)
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.
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.
1341
This counter counts the number of successful UL GPRS TBF establishment due to one phase access. This counter is used to find out the number of UL GPRS TBF establishment successes due to one phase access. The counter accumulates at the following three time points: 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 1346.
FIGURE 1346 - 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 1347.
FIGURE 1347 - 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.
1342
C901190020 Number of cell success for GPRS UL assignment due to single block packet access
Definition Description Usage Measurement Point
Number of cell success for GPRS UL assignment due to single block packet access. The counter counts the number of successful UL GPRS TBF establishment due to single block packet access. This counter is used to find out the number of successful UL GPRS TBF establishment due to single block packet access. 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 1348.
FIGURE 1348 - CHANNEL REQUESTS SUCCESSES DUE TO SINGLE BLOCK PACKET ACCESS
Unit
Times
C901190021 Number of cell success for GPRS UL assignment due to response paging
Definition
1343
The counter counts the number of successful UL GPRS TBF establishment due to response paging. This counter is used to find out the number of successful UL GPRS TBF establishment due to response paging. 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 1349.
FIGURE 1349 - DB RESOURCE REQUEST SUCCESSES DUE TO RESPONSE PAGING
Unit
Times
C901190022 Number of cell success for GPRS UL assignment due to cell updating
Definition Description Usage Measurement Point
Number of cell success for GPRS UL assignment due to cell updation. The counter counts the number of successful UL GPRS TBF establishment due to cell update This counter is used to find out the number of successful UL GPRS TBF establishment due to cell update. 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 1350.
1344
Unit
Times
C901190023 Number of cell success for GPRS UL assignment due to mobility management
Definition Description Usage Measurement Point
Number of cell success for GPRS UL assignment due to mobility management. The counter counts the number of successful UL GPRS TBF establishment due to mobile management. This counter is used to find out the number of successful UL GPRS TBF establishment due to mobile management. 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 1351.
FIGURE 1351 - DB RESOURCE REQUEST SUCCESSES DUE TO MOBILE MANAGEMENT (PCCCH)
1345
Unit
Times
C901190024 Number of cell success for GPRS UL assignment due to TWO PHASE access
Definition Description Usage Measurement Point
Number of cell success for GPRS UL assignment due to TWO PHASE access. This counter counts the number of successful UL GPRS TBF establishment due to two phase access. This counter is used to find out the number of successful UL GPRS TBF establishment due to two phase access. The counter accumulates at the following two time points: 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 1352.
FIGURE 1352 - DB RESOURCE REQUEST SUCCESSES DUE TO TWO PHASE ACCESS (CCCH)
If BSC receives channel requests from MS on PCCCH due to two phase access and DB resource request succeeds, the counter increments. The measurement point is A, as shown inFigure 1353.
1346
FIGURE 1353 - DB RESOURCE REQUEST SUCCESSES ON PCCCH DUE TO TWO PHASE ACCESS
C901190025 Number of cell success for GPRS UL assignment due to short access
Definition Description Usage Measurement Point
Number of cell success for GPRS UL assignment due to short access. This counter counts the number of successful UL GPRS TBF establishment due to short access. This counter is used to find out the number of successful UL GPRS TBF establishment due to short access. The counter accumulates at the following two time points: 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 1354.
1347
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
Number of allocated PDCH for GPRS UL TBF establishment. This counter counts the number of successfully assigned PDTCH when UL GPRS TBF successfully established. This counter is used to find out the number of successfully assigned PDTCH when UL GPRS TBF successfully established. The counter accumulates at the following three time points: 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 1355.
1348
When PS control plane receives packet channel requests on PCCCH from MS, the counter increments. The measurement point is A, as shown inFigure 1356.
FIGURE 1356 - 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.
1349
C901190027 Number of GPRS UL TBF establishment failure due to channel activate failed
Definition Description Usage
Number of GPRS UL TBF establishment failure due to channel activate failed. This counter counts the number of PDTCH activate failure when establishing UL GPRS TBF. 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). The counter accumulates at the following two time points: When BSC receives PDTCH channel activate failure message reported by BTS, the counter increments. The measurement point is A, as shown inFigure 1357.
FIGURE 1357 - PDCH ACTIVATION FAILURE
Measurement Point
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
1350
C901190028 Number of GPRS UL TBF establishment failure due to BTS connection failed
Definition Description Usage
Number of GPRS UL TBF establishment failure due to BTS connection failed. This counter counts the number of failure to establish UL GPRS TBF due to BTS connection failure. 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. The counter accumulates at the following two time points: 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 1358.
FIGURE 1358 - CONNECTION FAILED DUE TO BTS CONNECTION FAILURE
Measurement Point
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
1351
C901190029 Number of GPRS UL TBF establishment failure due to BIU connection failed
Definition Description Usage
Number of GPRS UL TBF establishment failure due to BIU connection failed. This counter counts the number of failure to establish UL GPRS TBF due to BIU connection failure. 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. 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 1359.
FIGURE 1359 - CONNECTION FAILED DUE TO BIU CONNECTION FAILURE
Measurement Point
Usage
Times
1352
This counter counts the number of channel activate and connection successes when establishing UL GPRS TBF. This counter is used to find out the number of channel activate and connection successes when establishing UL GPRS TBF. 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 1360.
FIGURE 1360 - RESOURCE APPLICATION FAILURE DUE TO ABIS CONGESTION (RESOURCE ADJUSTMENT)
Unit
Times
C901190031 Number of GPRS UL TBF establishment failure due to not receive PIA
Definition Description Usage
Number of GPRS UL TBF establishment failure due to not receive PIA. This counter counts the number of failure to send immediate assignment message to MS when establishing UL GPRS TBF. This counter is used to find out the number of failure to send immediate assignment message to MS when establishing UL GPRS TBF. The counter accumulates at the following two time points: 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.
Measurement Point
1353
Usage
Times
C901190032 Number of GPRS UL TBF establisment failure on PCCCH/CCCH due to UPPB-DSP congestion
Definition Description Usage Measurement Point
Number of GPRS UL TBF establishment failure on PCCCH/CCCH due to UPPB-DSP congestion. This counter counts the number of failure to establish UL GPRS TBF. This counter is used to find out the number of failure to establish UL GPRS TBF. 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 1361 .
FIGURE 1361 - UL GPRS TBF ESTABLISHMENT ON PCCCH/CCCH
Unit
Times
1354
C901190033 Number of GPRS UL TBF establisment failure on PACCH due to UPPB-DSP congestion
Definition Description
Number of GPRS UL TBF establishment failure on PACCH due to UPPB-DSP congestion. This counter is not used currently.
Number of GPRS UL TBF establishment success on PCCCH/CCCH This counter counts the number of successful UL GPRS TBF establishment and receiving MS TLL1. This counter is used to find out the number of successful UL GPRS TBF establishment and receiving MS TLL1. The counter accumulates at the following two time points: 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 1362.
FIGURE 1362 - UL ONE-PHASE-ACCESS RESOURCE ASSIGNMENT SUCCESSES
1355
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 1363 .
FIGURE 1363 - UL TWO-PHASE-ACCESS SINGLE BLOCK ASSIGNMENT SUCCESSES
Unit
Times
Number of GPRS UL TBF establishment success on PACCH. This counter is not used currently.
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.
1356
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. This counter is used to find out the number of UL GPRS TBF reallocation failure due to Abis congestion. In the situation when UL GPRS TBF is established, PS control plane receives DL assignment request message from PS user plane, and DB resource request fails due to Abis congestion, the counter increments. The measurement point is A, as shown inFigure 1364 .
FIGURE 1364 - DATABASE APPLICATION FAILURE DUE TO ABIS CONGESTION
C901190039 Number of GPRS UL TBF resource reallocation failure due to RR congestion for DL TBF establishment
Definition Description
Number of GPRS UL TBF resource reallocation failure due to RR congestion for DL TBF establishment. 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.
1357
This counter is used to find out the number of UL GPRS TBF reallocation failure due to RR congestion. 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 1365.
FIGURE 1365 - DATABASE APPLICATION FAILURE
DUE TO
RR CONGESTION
C901190040 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for DL TBF establishment
Definition Description
Number of GPRS UL TBF resource reallocation failure due to UPPB -DSP channel congestion for DL TBF establishment. 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. This counter is used to find out the number of UL GPRS TBF reallocation failure due to UPPB-DSP channel congestion. 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 1366.
1358
DUE TO
UPPB-DSP
C901190041 Number of GPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment
Definition Description Usage Measurement Point
Number of GPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment. The counter records the number of successful DL TBF establishment on PACCH when UL GPRS TBF is already established. This counter is used to find out the number of DL GPRS TBF reallocation successes. 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 1367.
FIGURE 1367 SUCCESSFUL RESOURCE APPLICATION
1359
C901190042 Number of allocated PDCH for GPRS UL TBF resource reallocation due to DL TBF establishment
Definition Description Usage Measurement Point
Number of allocated PDCH for GPRS UL TBF resource reallocation success due to DL TBF establishment. The counter records the number of successful allocated PDTCH when UL GPRS TBF is successfully reallocated. This counter is used to find out the number of successful allocated PDTCH when UL GPRS TBF is successfully reallocated. 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 1368.
FIGURE 1368 - SUCCESSFUL RESOURCE APPLICATION
1360
C901190043 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for DL TBF establishment
Definition Description Usage Measurement Point
Number of GPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment. The counter records the number of PDTCH activate failure during UL GPRS TBF resource reallocation. This counter is used to find out the number of PDTCH activate failure during UL GPRS TBF resource reallocation. The measurement is taken at two time points listed below: When BSC receives PDTCH channel activate failure message from BTS, the counter increments. The measurement point is A, as shown inFigure 1369 .
FIGURE 1369 - PDTCH ACTIVATION FAILURE
When 'Wait for PDTCH channel activation and connection response' timer times out, and BSC fails to receive PDTCH channel activate response message from BTS, the counter increments.
Unit
Times
1361
C901190044 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for DL TBF establishment
Definition Description Usage Measurement Point
Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for DL TBF establishment. The counter records the number of BTS connection failure during UL GPRS TBF resource reallocation. This counter is used to find out the number of BTS connection failure during UL GPRS TBF resource reallocation. The measurement is taken at two time points listed below: 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 1370 .
FIGURE 1370 - 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
1362
C901190045 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for DL TBF establishment
Definition Description Usage Measurement Point
Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for DL TBF establishment. The counter records the number of BIU connection failure during UL GPRS TBF resource reallocation. This counter is used to find out the number of BIU connection failure during UL GPRS TBF resource reallocation. When PS control plane receives connection failure message from connection module due to BIU connection failure, the counter increments. The measurement point is A, as shown inFigure 1371.
FIGURE 1371 - CONNECTION FAILED DUE TO BIU CONNECTION FAILURE
Unit
Times
1363
C901190046 Number of GPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment
Definition Description Usage Measurement Point
Number of GPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment The counter records the number of channel activate and connection successes during UL GPRS TBF resource reallocation. This counter is used to find out the number of channel activate and connection successes during UL GPRS TBF resource reallocation. 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 1372.
FIGURE 1372 - RESOURCE APPLICATION FAILURE DUE TO ABIS CONGESTION (RESOURCE ADJUSTMENT)
Unit
Times
1364
C901190047 Number of GPRS UL TBF resourse reallocation failure due to DL TBF establishment
Definition Description Related Features
Number of GPRS UL TBF resource reallocation failure due to DL TBF establishment. This counter is not used currently. ZGO-03-02-002 Enhancement on Channel Allocation
C901190048 Number of GPRS UL TBF resourse reallocation success due to DL TBF establishment
Definition Description Related Features
Number of GPRS UL TBF resource reallocation success due to DL TBF establishment. This counter is not used currently. ZGO-03-02-002 Enhancement on Channel Allocation
C901190051 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission
Definition Description
Number of GPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission 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
1365
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. 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 1373.
FIGURE 1373 - RESOURCE APPLICATION FAILURE DUE TO ABIS CONGESTION
Measurement Point
C901190052 Number of GPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission
Definition Description
Number of GPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission 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.
1366
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. 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 1374 .
FIGURE 1374 - RESOURCE APPLICATION FAILURE DUE TO RR CONGESTION (RESOURCE ADJUSTMENT)
Measurement Point
C901190053 Number of GPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission
Definition Description
Number of GPRS UL TBF resource reallocation failure due to UPPBDSP channel congestion for LLC transmission. 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. This counter is used to find out DB resource request failure due to UPPB-DSP channel congestion after PS control plane receiving
Usage
1367
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 1375.
FIGURE 1375 - RESOURCE APPLICATION FAILURE DUE TO UPPPB-DSP CHANNEL CONGESTION (RESOURCE ADJUSTMENT)
C901190054 Number of GPRS UL TBF resource reallocation success of channel allocation due to LLC transmission
Definition Description
Number of GPRS UL TBF resource reallocation success of channel allocation due to LLC transmission 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. 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. 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 1376.
Usage
Measurement Point
1368
C901190055 Number of allocated PDCH for GPRS UL TBF resource reallocation due to LLC transmission
Definition Description
Number of allocated PDTCH for GPRS UL TBF resource reallocation due to LLC transmission. 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. This counter is used to find out the number of successful allocated PDTCH when UL GPRS TBF is successfully reallocated. 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 1377.
FIGURE 1377 - RELEASE REQUEST DUE TO FLUSH LL
Unit
Times
1369
Related Features
C901190056 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for LLC transmission
Definition Description
Number of GPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment The counter records the number of PDTCH activate failure after BSC receiving resource reallocation request during UL GPRS TBF resource reallocation. This counter is used to find out the number of PDTCH activate failure during UL GPRS TBF resource reallocation. The counter accumulates at the following two time points: When BSC receives PDTCH channel activate failure message from BTS, the counter increments. The measurement point is A, as shown inFigure 1378.
FIGURE 1378 - 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
1370
C901190057 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for LLC transmission
Definition Description
Number of GPRS UL TBF resource reallocation failure due to BTS connection failure for LLC transmission The counter records the number of connection failure due to BTS connection failure after BSC receiving resource reallocation request during UL GPRS TBF transmission. This counter is used to find out the number of BTS connection failure during UL GPRS TBF resource transmission. The counter accumulates at the following two time points: 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 1379.
FIGURE 1379 - 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
1371
C901190058 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for LLC transmission
Definition Description Usage Measurement Point
Number of GPRS UL TBF resource reallocation failure due to BIU connection failure for LLC transmission. The counter records the number of BIU connection failure during UL GPRS TBF transmission. This counter is used to find out the number of BIU connection failure during UL GPRS TBF transmission. 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 1380.
FIGURE 1380 - CONNECTION FAILED
DUE TO
Unit
Times
1372
C901190059 Number of GPRS UL TBF resourse reallocation success of channel activate for LLC transmission
Definition Description Usage Measurement Point
Number of GPRS UL TBF resource reallocation success of channel activate for LLC transmission. The counter records the number of channel activate and connection successes during UL GPRS TBF transmission. This counter is used to find out the number of channel activate and connection successes during UL GPRS TBF tranmission. 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 1381.
FIGURE 1381 - SUCCESSFUL ACTIVATION AND CONNECTION
Unit
Times
C901190060 Number of GPRS UL TBF resourse reallocation failure due to LLC transmission
Definition Description Related Features
Number of GPRS UL TBF resource reallocation failure due to LLC transmission. This counter is not used currently. ZGO-03-02-002 Enhancement on Channel Allocation
1373
C901190061 Number of GPRS UL TBF resourse reallocation success due to LLC transmission
Definition Description Related Features
Number of GPRS UL TBF resource reallocation success due to LLC transmission. This counter is not used currently. ZGO-03-02-002 Enhancement on Channel Allocation
C901190062 Number of GPRS UL TBF resource reallocation requests for resource request
Definition Description
Number of GPRS UL TBF resource reallocation requests for resource request. This counter is not used currently.
C901190064 Number of GPRS UL TBF resource reallocation failure due to Abis congestion for resource request
Definition Description
Number of GPRS UL TBF resource reallocation failure due to Abis congestion for resource request 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. This counter is used to find out the number of DB resource request failure after PS control plane receives resource request from MS
Usage
1374
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 1382.
FIGURE 1382 - DB RESOURCE REQUESTS FAILURE DUE TO ABIS CONGESTION (RESOURCE REQUEST)
C901190065 Number of GPRS UL TBF resource reallocation failure due to RR congestion for resource request
Definition Description
Number of GPRS UL TBF resource reallocation failure due to RR congestion for resource request. 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).
1375
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 1383.
FIGURE 1383 - DB RESOURCE REQUESTS FAILURE DUE TO RR CONGESTION
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. 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). 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 1384.
Usage
Measurement Point
1376
DUE TO
UPPB-DSP
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. 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). 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 1385.
FIGURE 1385 DB RESOURCE REQUESTS SUCCESSES (RESOURCE REQUEST)
Usage
Measurement Point
1377
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. 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). 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 1386.
FIGURE 1386 DB RESOURCE REQUESTS SUCCESSES (RESOURCE REQUEST)
Usage
Measurement Point
1378
C901190069 Number of GPRS UL TBF resourse reallocation failure due to channel activate failure for resource request
Definition Description
Number of GPRS UL TBF resource reallocation failure due to channel activate failure for resource request. The counter records the number of PDTCH activate failure during UL GPRS TBF resource reallocation after PS control plane receives resource request message. 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). The counter accumulates at the following two time points: When BSC receives PDTCH channel activate failure message from BTS, the counter increments. The measurement point is A, as shown inFigure 1387.
FIGURE 1387 - PDTCH ACTIVATION FAILURE
Usage
Measurement Point
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
1379
C901190070 Number of GPRS UL TBF resourse reallocation failure due to BTS connection failure for resource request
Definition Description
Number of GPRS UL TBF resource reallocation failure due to BTS connection failure for resource request. 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. 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). The counter accumulates at the following two time points: 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 1388 .
FIGURE 1388 - CONNECTION FAILED DUE TO BTS CONNECTION FAILURE
Usage
Measurement Point
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
1380
C901190071 Number of GPRS UL TBF resourse reallocation failure due to BIU connection failure for resource request
Definition Description
Number of GPRS UL TBF resource reallocation failure due to BIU connection failure for resource request 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. 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). 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 1389.
FIGURE 1389 - CONNECTION FAILED DUE TO BIU CONNECTION FAILURE
Usage
Measurement Point
Unit
Times
1381
C901190072 Number of GPRS UL TBF resource reallocation success of channel activate and connection for resource request
Definition Description
Number of GPRS UL TBF resource reallocation success of channel activate and connection for resource request 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. 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). 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 1390.
FIGURE 1390 - RESOURCE APPLICATION FAILURE DUE TO ABIS CONGESTION (RESOURCE ADJUSTMENT)
Usage
Measurement Point
Unit
Times
1382
C901190073 Number of GPRS UL TBF resourse reallocation failure due to resource request
Definition Description Related Features
Number of GPRS UL TBF resource reallocation failure due to resource request. This counter is not used currently. ZGO-03-02-002 Enhancement on Channel Allocation
C901190074 Number of GPRS UL TBF resourse reallocation success due to resource request
Definition Description Related Features
Number of GPRS UL TBF resource reallocation failure due to reallocation success due to resource request. This counter is not used currently. ZGO-03-02-002 Enhancement on Channel Allocation
Number of GPRS UL TBF release due to flush LL. This counter counts the number of UL GPRS TBF release after PS control plane receiving request due to flush LL. This counter is used to find out the number of UL GPRS TBF release after PS control plane receiving request due to flush LL. 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 1391.
1383
Unit
Times
Number of GPRS UL TBF release due to GPRS suspend requests. This counter counts the number of UL GPRS TBF release after PS control plane receiving request due to GPRS suspend requests. This counter is used to find out the number of UL GPRS TBF release due to GPRS suspend requests. 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 1392.
FIGURE 1392 - RELEASE REQUEST
DUE TO
SUSPEND REQUEST
Unit
Times
1384
Number of GPRS UL TBF forcing release by CS. This counter counts the number of UL GPRS TBF forcing release by CS. This counter is used to find out the number of UL GPRS TBF forcing release by CS. 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 1393.
FIGURE 1393 - RELEASE REQUEST
DUE TO
PDCH REL
Unit
Times
C901190078 Number of GPRS UL TBF normal release due to user plane requests
Definition Description Usage Measurement Point
Number of GPRS UL TBF normal release due to user plane requests. This counter counts the number of UL GPRS TBF normal release due to user plane requests. This counter is used to find out the number of UL GPRS TBF normal release due to user plane requests. 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 1394.
1385
Unit
Times
C901190079 Number of GPRS UL TBF abnormal release due to user plane requests
Definition Description Usage Measurement Point
Number of GPRS UL TBF abnormal release due to user plane requests. This counter counts the number of UL GPRS TBF abnormal release due to user plane requests. This counter is used to find out the number of UL GPRS TBF abnormal release due to user plane requests. When PS control plane receives ABNORMAL RELEASE REQUEST message from PS user plane when UL GPRS TBF exists, the counter increments. The measurement point is A, as shown inFigure 1395.
FIGURE 1395 - RELEASE REQUEST BY MAC
DUE TO
Unit
Times
1386
Number of GPRS UL TBF release due to NSVC unavailability. This counter counts the number of UL GPRS TBF release due to NSVC unavailability. This counter is used to find out the number of UL GPRS TBF release after receiving forcing release request due to NSVC unavailability. 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 1396.
FIGURE 1396 - RELEASE REQUEST
DUE TO
NVSC UNAVAILABILITY
Unit
Times
Number of GPRS UL TBF release due to BVC unavailability. This counter counts the number of UL GPRS TBF release due to BVC unavailability. This counter is used to find out the number of UL GPRS TBF release after receiving forcing release request due to BVC unavailability. 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 1397.
1387
Unit
Times
Number of GPRS UL TBF release due to other reasons. This counter counts the number of UL GPRS TBF forcing release due to other reasons. This counter is used to find out the number of UL GPRS TBF release after receiving forcing release request due to other reasons. When PS control plane receives release message due to other reasons when UL GPRS TBF exists, the counter increments. The measurement point is A, as shown inFigure 1398.
FIGURE 1398 - CHANNEL REQUEST
Unit
Times
1388
Number of UL GPRS TBF grab resources. This counter counts the number of UL GPRS TBF grab resources. This counter is used to find out the frequency for UL GPRS TBF grabbing other TBF. 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 1399.
FIGURE 1399 - UL GPRS RESOURCE REQUEST SUCCESS
Number of grab instance by UL GPRS TBF. This counter counts the number of grab instance by UL GPRS TBF. This counter is used to find out the frequency for UL GPRS TBF grabbing other TBF resource. 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 1400.
1389
Number of UL GPRS TBF queuing. This counter counts the number of UL GPRS TBF queuing. This counter is used to find out the frequency for UL GPRS TBF grabbing other TBF resource. 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 1401.
FIGURE 1401 - UL GPRS RESOURCE REQUEST SUCCESS
1390
Number of UL GPRS TBF queuing success. This counter counts the number of UL GPRS TBF queuing success. This counter is used to find out the frequency for UL GPRS TBF queuing success. This counter increments while UL GPRS TBF is established during resource adjustment, the instance to be queued successfully assigns resource for user plane, and database is successfully registered. Measurement point is A as shown inFigure 1402.
FIGURE 1402 - RESOURCE ASSIGNMENT SUCCESS
Number of UL GPRS TBF release TBF during queuing. This counter counts the number of UL GPRS TBF release during queuing. This counter is used to find out the frequency for UL GPRS TBF release during queuing. This counter increments while UL GPRS TBF is released and instance still in queuing state. The measurement point is A as shown inFigure 1403.
1391
1392
Chapter
26
1393
C901200024 Number of cell success for EGPRS UL assignment due to TWO PHASE access .............................................. 1411 C901200025 Number of cell success for EGPRS UL assignment due to short access........................................................ 1412 C901200026 Number of allocated PDCH for EGPRS UL TBF establishment ............................................................... 1414 C901200027 Number of EGPRS UL TBF establishment failure due to channel activate failed.......................................... 1414 C901200028 Number of EGPRS UL TBF establishment failure due to BTS connection failed ........................................... 1415 C901200029 Number of EGPRS UL TBF establishment failure due to BIU connection failed .......................................... 1416 C901200030 Number of EGPRS UL TBF channel activate establishment success....................................................... 1417 C901200031 Number of EGPRS UL TBF establishment failure due to not receive PIA.................................................... 1418 C901200032 Number of EGPRS UL TBF establishment failure on PCCCH/CCCH due to UPPB-DSP congestion ................... 1419 C901200033 Number of EGPRS UL TBF establishment failure on PACCH due to UPPB-DSP congestion ............................ 1420 C901200034 Number of EGPRS UL TBF establishment success on PCCCH/CCCH............................................................ 1420 C901200035 Number of EGPRS UL TBF establishment success on PACCH..................................................................... 1421 C901200038 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for DL TBF establishment ........................................................................... 1422 C901200039 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for DL TBF establishment......... 1423 C901200040 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for DL TBF establishment .................................................................. 1424 C901200041 Number of EGPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment ........................................................................... 1425 C901200042 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to DL TBF establishment ............. 1426 C901200043 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment ........................................................................... 1427 C901200044 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for DL TBF establishment ........................................................................... 1428 C901200045 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for DL TBF establishment ........................................................................... 1429 C901200046 Number of EGPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment....................................................................... 1430 C901200047 Number of EGPRS UL TBF resource reallocation failure due to DL TBF establishment ................................. 1431 C901200048 Number of EGPRS UL TBF resource reallocation success due to DL TBF establishment ............................... 1431 C901200051 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission ............ 1431 C901200052 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission .............. 1432 C901200053 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission ............................................................................. 1433
1394
C901200054 Number of EGPRS UL TBF resource reallocation success of channel allocation due to LLC transmission......... 1434 C901200055 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to LLC transmission ................... 1435 C901200056 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for LLC transmission ............................................................................. 1436 C901200057 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for LLC transmission ............................................................................. 1437 C901200058 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for LLC transmission ............................................................................. 1438 C901200059 Number of EGPRS UL TBF resource reallocation success of channel activate for LLC transmission................ 1439 C901200060 Number of EGPRS UL TBF resource reallocation failure due to LLC transmission........................................ 1440 C901200061 Number of EGPRS UL TBF resource reallocation success due to LLC transmission ...................................... 1440 C901200062 Number of EGPRS UL TBF resource reallocation requests for resource request.......................................... 1441 C901200064 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for resource request ............ 1441 C901200065 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for resource request .............. 1442 C901200066 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for resource request ........................................................................... 1443 C901200067 Number of EGPRS UL TBF resource reallocation success due to database allocation for resource request ........................................................................ 1444 C901200068 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to resource request.................... 1445 C901200069 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for resource request ........................................................................... 1446 C901200070 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for resource request ........................................................................... 1447 C901200071 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for resource request ........................................................................... 1448 C901200072 Number of EGPRS UL TBF resource reallocation success of channel activate and connection for resource request ........................................................................... 1449 C901200073 Number of EGPRS UL TBF resource reallocation failure due to resource request ........................................ 1450 C901200074 Number of EGPRS UL TBF resource reallocation success due to resource request ...................................... 1450 C901200075 Number of EGPRS UL TBF release due to flush LL ............................................................................... 1451 C901200076 Number of EGPRS UL TBF release due to GPRS suspend requests .......................................................... 1451 C901200077 Number of EGPRS UL TBF forcing release by CS............................................................................... 1452 C901200078 Number of EGPRS UL TBF normal release due to user plane requests ....................................................... 1453 C901200079 Number of EGPRS UL TBF abnormal release due to user plane requests.................................................... 1453
1395
C901200080 Number of EGPRS UL TBF release due to NSVC unavailability ................................................................ 1454 C901200081 Number of EGPRS UL TBF release due to BVC unavailability ................................................................ 1455 C901200082 Number of EGPRS UL TBF release due to other reasons........................................................................ 1455 C901200083 Number of UL EGPRS TBF grab resources......... 1456 C901200084 Number of grab instance by UL EGPRS TBF ............................................................................. 1457 C901200085 Number of UL EGPRS TBF queuing ................ 1457 C901200086 Number of UL EGPRS TBF queuing success............................................................................. 1458 C901200087 Number of UL EGPRS TBF release TBF during queuing ....................................................................... 1459
Overview
UL EGPRS data TBF statistics collects the information about the establishment, maintain and release of UL EGPRS TBF. The statistic unit is cell.
Number of GPRS UL TBF establishment requests on CCCH This counter is not used currently.
Number of EGPRS UL TBF establishment requests on CCCH. This counter counts the number of EGPRS channel requests on CCCH when MS using EGPRS service.
1396
This counter is used to find out the frequency of channel requests on CCCH when MS attempts using EGPRS service. When BSC receives channel requests on CCCH from MS, the counter increments. The measurement point is A, as shown inFigure 1404.
FIGURE 1404 - EGPRS CHANNEL REQUEST
Number of GPRS UL TBF establishment requests on PCCCH. The counter is not used.
Number of EGPRS UL TBF establishment requests on PCCCH. This counter counts the number of packet channel requests on PCCCH when MS attempts using EGPRS service.
1397
This counter is used to find out the frequency of channel requests on PCCCH when MS attempts using EGPRS service. When BSC receives channel requests on PCCCH from MS, the counter increments. The measurement point is A, as shown in Figure 1405.
FIGURE 1405 - EGPRS PACKET CHANNEL REQUEST
Unit
Times
Number of GPRS UL TBF establishment requests on PACCH. The counter counts the number of UL EGPRS TBF establishment attempts on PACCH. 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. 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 1406.
Measurement Point
1398
Unit
Times
C901200007 Number of cell attempts for UL assignment due to ONE PHASE access
Definition Description
Number of cell attempts for UL assignment due to ONE PHASE access. 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. This counter is used to find out the number of UL EGPRS TBF establishment attempts due to one phase access. The counter accumulates at the following two time points: If BSC receives channel requests from MS on CCCH due to one phase access, the counter increments. The measurement point is A, as shown inFigure 1407 .
FIGURE 1407 - EGPRS CHANNEL REQUESTS ON CCCH DUE TO ONE PHASE ACCESS
If BSC receives EGPRS Packet channel request from MS on PCCCH due to one phase access, the counter increments. The measurement point is A, as shown in Figure 1408.
1399
FIGURE 1408 - EGPRS PACKET CHANNEL REQUESTS ON CCCH DUE TO ONE PHASE ACCESS
Times ZGB-03-05-007 One Phase Access ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
C901200008 Number of cell attempts for UL assignment due to single block packet access
Definition Description Related Features
Number of cell attempts for UL assignment due to single block packet access This counter is not used currently. ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
Number of cell attempts for UL assignment due to response paging. This counter is not used currently. ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
1400
Number of cell attempts for UL assignment due to cell updating. This counter is not used currently. ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
Number of cell attempts for UL assignment due to mobility management The counter is not used currently. ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
C901200012 Number of cell attempts for UL assignment due to TWO PHASE access
Definition Description
Number of cell attempts for UL assignment due to TWO PHASE access. 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. This counter is used to find out the number of UL EGPRS TBF establishment attempts due to two phase access. The counter accumulates at the following two time points: If BSC receives EGPRS channel requests from MS on CCCH due to two phase access, the counter increments. The measurement point is A, as shown in Figure 1409.
1401
FIGURE 1409 - EGPRS CHANNEL REQUESTS ON CCCH DUE TO TWO PHASE ACCESS
If BSC receives EGPRS Packet channel request from MS on CCCH due to one phase access, the counter increments. The measurement point is A, as shown inFigure 1410.
FIGURE 1410 - EGPRS PACKET CHANNEL REQUESTS ON PCCCH DUE TO TWO PHASE ACCESS
Number of cell attempts for UL assignment due to short access. 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. This counter is used to find out the number of UL EGPRS TBF establishment attempts due to short access. The counter accumulates at the following two time points: 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 1411.
1402
If BSC receives EGPRS Packet channel request from MS on PCCCH due to short access, the counter increments. The measurement point is A, as shown in Figure 1412.
FIGURE 1412 - EGPRS PACKET CHANNEL REQUESTS ON PCCCH DUE TO SHORT ACCESS
Number of EGPRS UL TBF establishment failure due to Abis congestion. The counter records the number of DB resource application failure when attempting UL EGPRS TBF establishment due to Abis congestion. This counter is used to find out the number of DB resource application failure when attempting UL EGPRS TBF establishment due to Abis congestion.
Usage
1403
Measurement Point
The counter accumulates at the following two time points: 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 1413.
FIGURE 1413 - 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 1414 .
FIGURE 1414 - DB RESOURCE REQUESTS FAILURE DUE TO ABIS CONGESTION (DL GPRS TBF ALREADY ESTABLISHED)
Times ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
1404
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. This counter is used to find out the number of DB resource application failure when attempting UL EGPRS TBF establishment due to RR congestion. The counter accumulates at the following two time points: If PS control plane receives EGPRS channel request from MS on CCCH or EGPRS Packet channel request on PCCCH and fails to apply for DB resource due to RR congestion, the counter increments. The measurement point is A, as shown Figure 1415.
FIGURE 1415 - DB RESOURCE REQUESTS FAILURE DUE TO RR CONGESTION (EGPRS)
Usage
Measurement Point
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 1416.
FIGURE 1416 - DB RESOURCE REQUESTS FAILURE DUE TO ABIS CONGESTION (DL GPRS TBF ALREADY ESTABLISHED)
Times ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
1405
C901200017 Number of EGPRS UL TBF establishment failure due to UPPB-DSP channel congestion
Definition Description
Number of EGPRS UL TBF establishment failure due to UPPB-DSP channel congestion The counter records the number of DB resource application failure when attempting UL EGPRS TBF establishment due to UPPB-DSP channel congestion. 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. The counter accumulates at the following two time points: 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 1417.
FIGURE 1417 - DB RESOURCE REQUESTS FAILURE DUE TO UPPB-DSP CHANNEL CONGESTION (EGPRS)
Usage
Measurement Point
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 1418.
1406
FIGURE 1418 - DB RESOURCE REQUESTS FAILURE DUE TO UPPB-DSP CONGESTION (DL GPRS TBF ALREADY ESTABLISHED)
Times ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
Number of EGPRS UL TBF establishment channel allocate success. This counter counts the number of DB resource request successes when attempting UL EGPRS TBF establishment. This counter is used to find out the number of DB resource request successes when attempting UL GPRS TBF establishment. If PS control plane receives EGPRS channel requests from MS on CCCH or EGPRS Packet channel request on PCCCH and succeeds in applying for DB resource, the counter increments. The measurement point is A, as shown in Figure 1419.
1407
Times ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
C901200019 Number of cell success for EGPRS UL assignment due to ONE PHASE access
Definition Description
Number of EGPRS UL TBF establishment failure due to UPPB-DSP channel congestion. The counter records the number of DB resource application failure when attempting UL EGPRS TBF establishment due to UPPB-DSP channel congestion. 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. The counter accumulates at the following two time points: 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 1420
Usage
Measurement Point
1408
FIGURE 1420 - 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 1421
FIGURE 1421 - DB RESOURCE REQUESTS FAILURE DUE TO DPPB-DSP CONGESTION (DL GPRS TBF ALREADY ESTABLISHED)
Times ZGB-03-05-007 One Phase Access ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
1409
C901200020 Number of cell success for EGPRS UL assignment due to single block packet access
Definition Description Related Features
Number of cell success for EGPRS UL assignment due to single block packet access This counter is not used. ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
C901200021 Number of cell success for EGPRS UL assignment due to response paging
Definition Description Related Features
Number of cell success for EGPRS UL assignment due to response paging This counter is not used. ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
C901200022 Number of cell success for EGPRS UL assignment due to cell updating
Definition Description Related Features
Number of cell success for EGPRS UL assignment due to cell updating. This counter is not used. ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
1410
C901200023 Number of cell success for EGPRS UL assignment due to mobility management
Definition Description Related Features
Number of cell success for EGPRS UL assignment due to mobility management. This counter is not used. ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
C901200024 Number of cell success for EGPRS UL assignment due to TWO PHASE access
Definition Description Usage Measurement Point
Number of cell success for EGPRS UL assignment due to TWO PHASE access. This counter counts the number of successful UL EGPRS TBF establishment due to two phase access. This counter is used to find out the number of successful UL EGPRS TBF establishment due to two phase access. The counter accumulates at the following two time points: 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 1422.
1411
FIGURE 1422 - EGPRS DB RESOURCE REQUEST SUCCESSES DUE TO TWO PHASE ACCESS (CCCH)
If BSC receives EGPRS packet channel requests from MS on PCCCH due to two phase access and DB resource request succeeds, the counter increments. The measurement point is A, as shown inFigure 1423.
FIGURE 1423 - DB RESOURCE REQUEST SUCCESSES ON PCCCH DUE TO TWO PHASE ACCESS
Times ZGB-03-05-008 Two Phase Access ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
C901200025 Number of cell success for EGPRS UL assignment due to short access
Definition
1412
This counter counts the number of successful UL EGPRS TBF establishment due to short access. This counter is used to find out the number of successful UL GPRS TBF establishment due to short access. The counter accumulates at the following two time points: 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 1424.
FIGURE 1424 - 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 1425.
FIGURE 1425 - EGPRS DB RESOURCE REQUEST SUCCESSES DUE TO SHORT ACCESS (PCCCH)
1413
Number of allocated PDTCH for EGPRS UL TBF establishment. This counter counts the number of successfully assigned PDTCH when UL EGPRS TBF successfully established. This counter is used to find out the number of successfully assigned PDTCH when UL EGPRS TBF successfully established. When PS control plane receives EGPRS channel requests on CCCH from MS or EGPRS Packet channel request on PCCCH and DB resource requests succeed, the counter increments. The measurement point is A, as shown in Figure 1426.
FIGURE 1426 - DB RESOURCE REQUEST SUCCESSES (EGPRS)
Times ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-05-003 EGPRS Packet Channel Request on CCCH
C901200027 Number of EGPRS UL TBF establishment failure due to channel activate failed
Definition Description
Number of EGPRS UL TBF establishment failure due to channel activate failed. This counter counts the number of PDTCH activate failure when establishing UL EGPRS TBF.
1414
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). The counter accumulates at the following two time points: When BSC receives PDTCH channel activate failure message reported by BTS, the counter increments. The measurement point is A, as shown in Figure 1427.
FIGURE 1427 - PDCH ACTIVATION FAILURE
Measurement Point
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.
C901200028 Number of EGPRS UL TBF establishment failure due to BTS connection failed
Definition Description Usage
Number of EGPRS UL TBF establishment failure due to BTS connection failed. This counter counts the number of failure to establish UL EGPRS TBF due to BTS connection failure. 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. The counter accumulates at the following two time points: 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 1428.
Measurement Point
1415
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.
C901200029 Number of EGPRS UL TBF establishment failure due to BIU connection failed
Definition Description Usage
Number of EGPRS UL TBF establishment failure due to BIU connection failed. This counter counts the number of failure to establish UL EGPRS TBF due to BIU connection failure. 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. 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 1429.
Measurement Point
1416
Number of EGPRS UL TBF channel activate establishment success. This counter counts the number of channel activate and connection successes when establishing UL EGPRS TBF. This counter is used to find out the number of channel activate and connection successes when establishing UL EGPRS TBF. 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 1430.
FIGURE 1430 - UL EGPRS TBF ESTABLISHES CHANNEL ACTIVATION AND ACCESS SUCCESS
1417
C901200031 Number of EGPRS UL TBF establishment failure due to not receive PIA
Definition Description Usage
Number of EGPRS UL TBF establishment failure due to not receive PIA. This counter counts the number of failure to send immediate assignment message to MS when establishing UL EGPRS TBF. This counter is used to find out the number of failure to send immediate assignment message to MS when establishing UL EGPRS TBF. The counter accumulates at the following two time points: When PS control plane receives immediate assignment failure message reported by BTS, the counter increments. The measurement point is A, as shown in Figure 1431.
FIGURE 1431 - SUCCESSFUL IMMEDIATE ASSIGNMENT SENDING
Measurement Point
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.
1418
C901200032 Number of EGPRS UL TBF establishment failure on PCCCH/CCCH due to UPPB-DSP congestion
Definition Description Usage Measurement Point
Number of EGPRS UL TBF establishment failure on PCCCH/CCCH due to UPPB-DSP. This counter counts the number of failure to establish UL EGPRS TBF. This counter is used to find out the number of failure to establish UL EGPRS TBF. 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 1432.
FIGURE 1432 - UL GPRS TBF ESTABLISHMENT ON PCCCH/CCCH
1419
C901200033 Number of EGPRS UL TBF establishment failure on PACCH due to UPPB-DSP congestion
Definition Description
Number of EGPRS UL TBF establishment failure on PACCH due to UPPB-DSP congestion. This counter is not used currently.
Number of EGPRS UL TBF establishment success on PCCCH/CCCH. This counter counts the number of successful UL EGPRS TBF establishment and receiving MS TLL1. This counter is used to find out the number of successful UL EGPRS TBF establishment and receiving MS TLL1. The counter accumulates at the following two time points: When PS control plane receives MS TLL1 MAC establishment inmessage reported by PS user plane in the premise of one phase access, the counter increments. The measurement point is A, as shown in Figure 1433.
dication
1420
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 1434.
FIGURE 1434 - UL TWO-PHASE-ACCESS SINGLE BLOCK ASSIGNMENT SUCCESSES
Number of EGPRS UL TBF establishment success on PACCH. This counter is not used currently.
1421
C901200038 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for DL TBF establishment
Definition Description
Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for DL TBF 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 UL EGPRS TBF reallocation failure due to Abis resource congestion. This counter is used to find out the number of UL GPRS TBF reallocation failure due to Abis congestion. 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 1435.
FIGURE 1435 - DATABASE APPLICATION FAILURE DUE TO ABIS CONGESTION
1422
C901200039 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for DL TBF establishment
Definition Description
Number of EGPRS UL TBF resource reallocation failure due to RR congestion for DL TBF establishment. 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 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.
This counter is used to find out the number of UL EGPRS TBF reallocation failure due to RR congestion. 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 1436.
FIGURE 1436 - DATABASE APPLICATION FAILURE
DUE TO
RR CONGESTION
1423
C901200040 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for DL TBF establishment
Definition Description
Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion. 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. This counter is used to find out the number of UL EGPRS TBF reallocation failure due to UPPB-DSP channel congestion. 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 1437.
FIGURE 1437 - DATABASE APPLICATION FAILURE CHANNEL CONGESTION
DUE TO
UPPB-DSP
1424
C901200041 Number of EGPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment
Definition Description Usage Measurement Point
Number of EGPRS UL TBF resource reallocation success of channel allocation due to DL TBF establishment. The counter records the number of successful DL TBF establishment on PACCH when UL EGPRS TBF is already established. This counter is used to find out the number of DL EGPRS TBF reallocation successes. 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 1438.
FIGURE 1438 SUCCESSFUL RESOURCE APPLICATION
1425
C901200042 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to DL TBF establishment
Definition Description Usage Measurement Point
Number of allocated PDTCH for EGPRS UL TBF resource reallocation due to DL TBF establishment. The counter records the number of successful allocated PDTCH when UL EGPRS TBF is successfully reallocated. This counter is used to find out the number of successful allocated PDTCH when UL EGPRS TBF is successfully reallocated. The counter accumulates at the following two time points: 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 1439.
1426
C901200043 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment
Definition Description Usage Measurement Point
Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for DL TBF establishment. The counter records the number of PDTCH activate failure during UL GPRS TBF resource reallocation. This counter is used to find out the number of PDTCH activate failure during UL EGPRS TBF resource reallocation. The counter accumulates at the following two time points: When BSC receives PDTCH channel activate failure message from BTS, the counter increments. The measurement point is A, as shown inFigure 1440.
FIGURE 1440 - 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
1427
C901200044 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for DL TBF establishment
Definition Description Usage Measurement Point
Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for DL TBF establishment. The counter records the number of BTS connection failure during UL EGPRS TBF resource reallocation. This counter is used to find out the number of BTS connection failure during UL EGPRS TBF resource reallocation. The counter accumulates at the following two time points: 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 1441.
FIGURE 1441 - 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
1428
C901200045 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for DL TBF establishment
Definition Description Usage Measurement Point
Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for DL TBF establishment. The counter records the number of BIU connection failure during UL EGPRS TBF resource reallocation. This counter is used to find out the number of BIU connection failure during UL EGPRS TBF resource reallocation. 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 1442.
FIGURE 1442 - CONNECTION FAILED DUE TO BIU CONNECTION FAILURE
Unit
Times
1429
C901200046 Number of EGPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment
Definition Description Usage Measurement Point
Number of EGPRS UL TBF resource reallocation success of channel activate and connection for DL TBF establishment The counter records the number of channel activate and connection successes during UL EGPRS TBF resource reallocation. This counter is used to find out the number of channel activate and connection successes during UL EGPRS TBF resource reallocation. 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 1443.
FIGURE 1443 - RESOURCE APPLICATION FAILURE DUE TO ABIS CONGESTION (RESOURCE ADJUSTMENT)
Unit
Times
1430
C901200047 Number of EGPRS UL TBF resource reallocation failure due to DL TBF establishment
Definition Description Related Features
Number of EGPRS UL TBF resource reallocation failure due to DL TBF establishment. The counter is not used currently. ZGO-03-02-002 Enhancement on Channel Allocation
C901200048 Number of EGPRS UL TBF resource reallocation success due to DL TBF establishment
Definition Description Related Features
Number of EGPRS UL TBF resource reallocation success due to DL TBF establishment. The counter is not used currently. ZGO-03-02-002 Enhancement on Channel Allocation
C901200051 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission
Definition Description
Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for LLC transmission. 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
1431
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. 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 1444.
FIGURE 1444 - RESOURCE APPLICATION FAILURE DUE TO ABIS CONGESTION (RESOURCE ADJUSTMENT)
Measurement Point
C901200052 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission
Definition Description
Number of EGPRS UL TBF resource reallocation failure due to RR congestion for LLC transmission. 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.
1432
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. 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 1445.
FIGURE 1445 - RESOURCE APPLICATION FAILURE DUE TO RR CONGESTION (RESOURCE ADJUSTMENT)
Measurement Point
C901200053 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission
Definition Description
Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for LLC transmission. 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. This counter is used to find out DB resource request failure due to UPPB-DSP channel congestion after PS control plane receiving
Usage
1433
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 1446.
FIGURE 1446 - RESOURCE APPLICATION FAILURE DUE TO UPPB-DSP CHANNEL CONGESTION (RESOURCE ADJUSTMENT)
C901200054 Number of EGPRS UL TBF resource reallocation success of channel allocation due to LLC transmission
Definition Description
Number of EGPRS UL TBF resource reallocation success of channel allocation due to LLC transmission. 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. 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. 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 1447.
Usage
Measurement Point
1434
C901200055 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to LLC transmission
Definition Description
Number of allocated PDTCH for EGPRS UL TBF resource reallocation due to LLC transmission. 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. This counter is used to find out the number of successful allocated PDTCH when UL EGPRS TBF is successfully reallocated. 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 1448.
1435
C901200056 Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for LLC transmission
Definition Description
Number of EGPRS UL TBF resource reallocation failure due to channel activate failure for LLC transmission. This counter counts the number of PDTCH activate failure after BSC receiving resource reallocation request during UL EGPRS TBF resource reallocation. This counter is used to find out the number of PDTCH activate failure during UL EGPRS TBF resource reallocation. The measurement is taken at two time points listed below: When BSC receives PDTCH channel activate failure message from BTS, the counter increments. The measurement point is A, as shown inFigure 1449.
1436
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
C901200057 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for LLC transmission
Definition Description
Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for LLC transmission. The counter records the number of connection failure due to BTS connection failure after BSC receiving resource reallocation request during UL EGPRS TBF transmission. This counter is used to find out the number of BTS connection failure during UL EGPRS TBF resource transmission. The counter accumulates at the following two time points: 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
1437
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
C901200058 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for LLC transmission
Definition Description Usage Measurement Point
Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for LLC transmission. The counter records the number of BIU connection failure during UL EGPRS TBF transmission. This counter is used to find out the number of BIU connection failure during UL EGPRS TBF transmission. 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 1451.
1438
Unit
Times
C901200059 Number of EGPRS UL TBF resource reallocation success of channel activate for LLC transmission
Definition Description Usage Measurement Point
Number of EGPRS UL TBF resource reallocation success of channel activate for LLC transmission The counter records the number of channel activate and connection successes during UL EGPRS TBF transmission. This counter is used to find out the number of channel activate and connection successes during UL EGPRS TBF tranmission. 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 .
1439
FIGURE 1452
Unit
Times
C901200060 Number of EGPRS UL TBF resource reallocation failure due to LLC transmission
Definition Description Related Features
Number of EGPRS UL TBF resource reallocation failure due to LLC transmission. The counter is not used currently. ZGO-03-02-002 Enhancement on Channel Allocation
C901200061 Number of EGPRS UL TBF resource reallocation success due to LLC transmission
Definition Description Related Features
Number of EGPRS UL TBF resource reallocation success due to LLC transmission. The counter is not used currently. ZGO-03-02-002 Enhancement on Channel Allocation
1440
C901200062 Number of EGPRS UL TBF resource reallocation requests for resource request
Definition Description
Number of EGPRS UL TBF resource reallocation requests for resource request. The counter is not used currently.
C901200064 Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for resource request
Definition Description
Number of EGPRS UL TBF resource reallocation failure due to Abis congestion for resource request. 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. 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). 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 1453.
Usage
Measurement Point
1441
FIGURE 1453 - DB RESOURCE REQUESTS FAILURE DUE TO ABIS CONGESTION (RESOURCE REQUEST)
C901200065 Number of EGPRS UL TBF resource reallocation failure due to RR congestion for resource request
Definition Description
Number of EGPRS UL TBF resource reallocation failure due to RR congestion for resource request. 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). PS control plane receives resource request message from MS, and DB resource request fails due to RR congestion, the counter increments. The measurement point is A, as shown in Figure 1454.
Measurement Point
1442
C901200066 Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for resource request
Definition Description
Number of EGPRS UL TBF resource reallocation failure due to UPPB-DSP channel congestion for resource request. 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. 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). 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 1455.
Usage
Measurement Point
1443
FIGURE 1455 - DB RESOURCE REQUESTS FAILURE DUE TO UPPB-DSP CHANNEL CONGESTION (RESOURCE REQUEST)
C901200067 Number of EGPRS UL TBF resource reallocation success due to database allocation for resource request
Definition Description
Number of EGPRS UL TBF resource reallocation success due to database allocation for resource request 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. 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). 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 1456.
Usage
Measurement Point
1444
C901200068 Number of allocated PDCH for EGPRS UL TBF resource reallocation due to resource request
Definition Description
Number of allocated PDTCH for EGPRS UL TBF resource reallocation due to resource request. The counter records the number of successful allocated PDTCH after PS control plane receives resource request message from MS during UL EGPRS TBF process. 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). 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 1457.
Usage
Measurement Point
1445
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: When BSC receives PDTCH channel activate failure message from BTS, the counter increments. The measurement point is A, as shown in .
1446
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
C901200070 Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for resource request
Definition Description
Number of EGPRS UL TBF resource reallocation failure due to BTS connection failure for resource request. 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. 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). The counter accumulates at the following two time points: 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 1459.
Usage
Measurement Point
1447
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
C901200071 Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for resource request
Definition Description
Number of EGPRS UL TBF resource reallocation failure due to BIU connection failure for resource request. 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. 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). 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 1460.
Usage
Measurement Point
1448
Unit
Times
C901200072 Number of EGPRS UL TBF resource reallocation success of channel activate and connection for resource request
Definition Description
Number of EGPRS UL TBF resource reallocation success of channel activate and connection for resource request 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. 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). 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 1461.
Usage
Measurement Point
1449
FIGURE 1461 - RESOURCE APPLICATION FAILURE DUE TO ABIS CONGESTION (RESOURCE ADJUSTMENT)
Unit
Times
C901200073 Number of EGPRS UL TBF resource reallocation failure due to resource request
Description Related Features
C901200074 Number of EGPRS UL TBF resource reallocation success due to resource request
Description Related Features
1450
This counter counts the number of UL EGPRS TBF release after PS control plane receiving request due to flush LL. This counter is used to find out the number of UL EGPRS TBF release after PS control plane receiving request due to flush LL. 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 1462.
FIGURE 1462 RELEASE REQUEST
DUE TO
SUSPEND REQUEST
Unit
Times
This counter counts the number of UL EGPRS TBF release after PS control plane receiving request due to GPRS suspend requests. This counter is used to find out the number of UL EGPRS TBF release due to GPRS suspend requests. 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 1463.
1451
DUE TO
SUSPEND REQUEST
Unit
Times
This counter counts the number of UL EGPRS TBF forcing release by CS. This counter is used to find out the number of UL EGPRS TBF forcing release by CS. 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 1464.
FIGURE 1464 RELEASE REQUEST
DUE TO
PDCH REL
Unit
Times
1452
C901200078 Number of EGPRS UL TBF normal release due to user plane requests
Description Usage Measurement Point
This counter counts the number of UL EGPRS TBF normal release due to user plane requests. This counter is used to find out the number of UL EGPRS TBF normal release due to user plane requests. 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 1465.
FIGURE 1465 RELEASE REQUEST MAC
DUE TO
BY
Unit
Times
C901200079 Number of EGPRS UL TBF abnormal release due to user plane requests
Description Usage Measurement Point
This counter counts the number of UL EGPRS TBF abnormal release due to user plane requests. This counter is used to find out the number of UL EGPRS TBF abnormal release due to user plane requests. 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 1466.
1453
DUE TO
Unit
Times
Number of EGPRS UL TBF release due to NSVC unavailability. This counter counts the number of UL EGPRS TBF release due to NSVC unavailability. This counter is used to find out the number of UL EGPRS TBF release after receiving forcing release request due to NSVC unavailability. 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 1467.
FIGURE 1467 - RELEASE REQUEST DUE TO NSVC UNAVAILABILITY
Measurement Point
Unit
Times
1454
Number of EGPRS UL TBF release due to BVC unavailability. This counter counts the number of UL EGPRS TBF release due to BVC unavailability. This counter is used to find out the number of UL EGPRS TBF release after receiving forcing release request due to BVC unavailability. 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 1468.
FIGURE 1468 - RELEASE REQUEST DUE TO BVC UNAVAILABILITY
Measurement Point
Unit
Times
Number of EGPRS UL TBF release due to other reasons. This counter counts the number of UL EGPRS TBF forcing release due to other reasons. This counter is used to find out the number of UL EGPRS TBF release after receiving forcing release request due to other reasons. 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 1469.
1455
Unit
Times
Number of UL EGPRS TBF grab resources. This counter counts the number of UL EGPRS TBF grab resources. This counter is used to find out the frequency for UL EGPRS TBF grabbing other TBF resource. 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 1470.
FIGURE 1470 - UL EGPRS RESOURCE REQUEST SUCCESS
1456
Number of grab instance by UL EGPRS TBF. This counter counts the number of grab instance by UL EGPRS TBF. This counter is used to find out the frequency for UL EGPRS TBF grabbing other TBF resource. 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 1471.
FIGURE 1471 - UL EGPRS RESOURCE REQUEST SUCCESS
Number of UL EGPRS TBF queuing. This counter counts the number of UL EGPRS TBF queuing. This counter is used to find out the frequency for UL EGPRS TBF queuing. 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 1472.
1457
Number of UL EGPRS TBF queuing success. This counter counts the number of UL EGPRS TBF queuing success. This counter is used to find out the frequency for UL EGPRS TBF queuing success. This counter increments while UL EGPRS TBF is established during resource adjustment, the instance to be queued successfully assigns resource for user, and database is successfully registered. Measurement point is A as shown inFigure 1473.
FIGURE 1473 - UL EGPRS RESOURCE REQUEST SUCCESS
1458
Number of UL EGPRS TBF release TBF during queuing. This counter counts the number of UL EGPRS TBF release during queuing. This counter is used to find out the frequency for UL EGPRS TBF release during queuing. This counter increments while UL EGPRS TBF is released and instance still in queuing state. The measurement point is A as shown in Figure 1474.
FIGURE 1474 - RELEASE UL EGPRS TBF
1459
1460
Chapter
27
1461
C901210031 LLC transfer not via cell reselection ............... 1483 C901210032 LLC transfer fail Num via cell reselection......... 1483 C901210033 LLC transfer fail Num not via cell reselection ............................................................................. 1484
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.
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. When BSC receives a PAGING PS message, this counter increments. The measurement point is A, as shown in Figure 1475.
FIGURE 1475 PAGING PS PROCESS
Measurement Point
Number of paging CS message SGSN sending circuit paging message indicates that BSC originates packet paging for MS in designated cell. This counter counts the number of received messages.
1462
Measurement Point
When BSC receives a PAGING CS message, this counter increments. The measurement point is A, as shown inFigure 1476.
FIGURE 1476 - PAGING CS PROCESS
Number of Flush-LL Message received 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. By viewing the number of receiving this message by BSC, to check the MS handover condition. When BSC receives a FLUSH-LL message, this counter increments. The measurement point is A1, as shown in Figure 1477.
FIGURE 1477 - FLUSH-LL MESSAGE
Unit
Times
1463
Number of Flush-LL Message sent 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. When BSC receives a FLUSH-LL-ACK message, this counter increments. The measurement point is A2, as shown in Figure 1478.
FIGURE 1478 - FLUSH-LL MESSAGE
Measurement Point
Unit
Times
Number of BVC-BLOCK message sent BSC sending BVC block message indicates BVC designated by SGSN blocking. This counter counts the number of blocking designated BVC by BSC. When BSC sends a BVC-BLOCK message, this counter increments. The measurement point is A1, as shown inFigure 1479.
Measurement Point
1464
Unit
Times
Number of BVC-BLOCK-ACK message received 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. When BSC receives a BVC-BLOCK-ACK message, this counter increments. The measurement point is A2, as shown inFigure 1480 .
FIGURE 1480 - BVC BLOCKING PROCESS
Measurement Point
Unit
Times
1465
Number of BVC-UNBLOCK message sent BSC sends BVC unblocking message indicates BVC designated by SGSN unblocking, and this counter counts the number of unblocking designated BVC by BSC. When BSC sends a BVC-UNBLOCK message, this counter increments. The measurement point is A1, as shown inFigure 1481 .
FIGURE 1481 - BVC UNBLOCKING PROCESS
Measurement Point
Unit
Times
Number of BVC-UNBLOCK-ACK message received. 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. When BSC receives a BVC-UNBLOCK-ACK message, this counter increments. The measurement point is A2, as shown inFigure 1482.
Measurement Point
1466
Unit
Times
Number of BVC-RESET message sent BSC sends BVC reset message indicates SGSN resets designated BVC, and this counter counts the number of resetting designated BVC by BSC actively. When BSC sends a BVC-RESET message, this counter increments. The measurement point is A1, as shown inFigure 1483 .
FIGURE 1483 - BVC RESET PROCESS
Measurement Point
1467
Unit
Times
Number of BVC-RESET-ACK message received. 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. When BSC receives a BVC-RESET-ACK essage, this counter increments. The measurement point is A2, as shown in Figure 1484.
FIGURE 1484 - BVC RESET PROCESS
Measurement Point
Unit
Times
1468
Description
SGSN sends BVC reset message indicates BSC resets designated BVC, and this counter will count the number of resetting BVC by SGSN actively. When BSC receives a BVC-RESET message, this counter increments. The measurement point is A3, as shown inFigure 1485.
FIGURE 1485 - BVC RESET PROCESS
Description
Unit
Times
Number of BVC-RESET-ACK message sent. 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. When BSC sends a BVC-RESET-ACK message, this counter increments. The measurement point is A1, as shown inFigure 1486.
Measurement Point
1469
Unit
Times
Number of PERFORM-LOCATION-REQUEST message received. 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. By viewing the number of receiving locating request message by BSC, you can view the frequency of locating service. When BSC receives a PERFORM-LOCATION-REQUEST message, this counter increments. The measurement point is A1, as shown inFigure 1487 .
1470
Unit
Times
Number of PERFORM-LOCATION-RESPONSE message sent 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. By viewing the number of sending this message by BSC, you can view the frequency of locating service. When BSC sends a PERFORM-LOCATION- RESPONSE message, this counter increments. The measurement point is A1, as shown inFigure 1488.
1471
Unit
Times
Number of PERFORM-LOCATION-ABORT message received. SGSN sends abort locating message to request BSC abort current locating process. This counter counts the number of receiving this message by BSC. When BSC receives a PERFORM-LOCATION-ABORT message, this counter increments. The measurement point is A1, as shown inFigure 1489.
Measurement Point
1472
Unit
Times
Number of POSITION-COMMAND message sent. BSC sends locating command message to request SGSN perform locating command process. This counter counts the number of sending this message by BSC. BSC sends a POSITION-COMMAND message, this counter increments. The measurement point is A2, as shown inFigure 1490.
Measurement Point
1473
Unit
Times
Number of POSITION-RESPONSE message received. 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. When BSC receives a POSITION-RESPONSE message, this counter increments. The measurement point is A3, as shown inFigure 1491.
Measurement Point
1474
Unit
Times
Number of Flush-LL received if UL/DL TBF exist 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. 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 1492.
Measurement Point
1475
Unit
Times
Number of Flush-LL received if DL TBF exist 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. 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 1493.
FIGURE 1493 - RECEIVE FLUSH-LL FOR DL TBF
Measurement Point
1476
Unit
Times
Number of Flush-LL received if UL TBF exist 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. 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 1494.
FIGURE 1494 - RECEIVE FLUSH-LL FOR UL TBF
Measurement Point
Unit
Times
Number of reroute intra NSE. 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. When BSC receives a FLUSH-LL message and new and previous cells are same NSE, this counter increments. The measurement point is A1, as shown inFigure 1495.
Measurement Point
1477
Unit
Times
Number of reroute inter NSE intra BSS cell. SGSN sends FLUSH-LL message to notify of BSS MS passed intercell handover. This counter counts the number of receiving this message by BSC, and the number of same BSS and different NSEs for new and previous cells. 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 1496.
FIGURE 1496 - FLUSH-LL MESSAGE
Measurement Point
Unit
Times
1478
Number of reroute inter NSE inter BSS cell. SGSN sends FLUSH-LL message to notify of BSS MS passed intercell handover. This counter counts the number of receiving this message by BSC, and the number of different BSSs and NSEs for new and previous cells. 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 1497.
FIGURE 1497 - FLUSH-LL MESSAGE
Measurement Point
Unit
Times
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. 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. When PS control plane receives the indication of LLC frame transferring success or failure from PS user plane, the number of bytes of LLC frames successfully transferred is accumulated. Byte
Usage
1479
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. 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. When PS control plane receives the indication of LLC frame transferring success or failure from PS user plane, the number of LLC frames successfully transferred is accumulated. Times
Usage
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. 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. When PS control plane receives the indication of LLC frame transferring failure from PS user plane, the number of bytes of LLC frames failed to be transferred is accumulated. Byte
Usage
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. 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.
Usage
1480
When PS control plane receives the indication of LLC frame transferring failure from PS user plane, the number of LLC frames failed to be transferred is accumulated. Times
1481
ii. Usage This counter is used to find out the number of LLC frames successfully transferred after LLC frame transferring is initiated. iii. Measurement Point When PS control plane receives the indication of LLC frame transferring completion from PS user plane, if the transferring succeeds, then the counter increments. iv. Unit Times
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 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
1482
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 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
1483
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. iii. 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. iv. Unit Times 2. V6.20.200f This counter is not used.
1484
Chapter
28
GB Message Statistic
Table of Contents Overview...................................................................... 1486 C901220001 Sum of UL UNITDATA messages handled at BSSGP level.................................................................. 1487 C901220002 Sum of DL UNITDATA messages handled at BSSGP level.................................................................. 1487 C901220003 Number of receiving RA-CAPABILITY message ............................................................................ 1488 C901220004 Number of PTP packet paging received by BSC ............................................................................. 1489 C901220005 Number of PTP circuit paging received by BSC ............................................................................. 1489 C901220006 Number of RA-CAPABILITY-UPDATE message sent............................................................................. 1490 C901220007 Number of RA-CAPABILITY-UPDATE-ACK message received................................................................ 1491 C901220008 Number of wireless status PDU messages sent by BSC......................................................................... 1491 C901220009 Number of wireless status messages sent by BSC due to losing wireless association with MS .................. 1492 C901220010 Number of wireless status messages sent by BSC due to bad link quality ............................................. 1493 C901220011 Number of wireless status messages sent by BSC due to cell reselection command ............................... 1493 C901220012 Number of FLOW-CONTROL-BVC messages sent by BSC......................................................................... 1494 C901220013 Number of FLOW-CONTROL-BVC-ACK messages received by BSC ............................................................ 1494 C901220014 Number of FLOW-CONTROL-MS messages sent by BSC......................................................................... 1495 C901220015 Number of FLOW-CONTROL-MS-ACK messages received by BSC ............................................................ 1496 C901220016 Number of FLOW-CONTROL-PFC messages sent by BSC......................................................................... 1497 C901220017 Number of FLOW-CONTROL-PFC-ACK messages received by BSC ............................................................ 1498 C901220018 Number of status messages sent by BSC......... 1499 C901220019 Number of status messages received by BSC ............................................................................. 1500 C901220020 Number of status messages sent with BVCI Unknown ......................................................................... 1501 C901220021 Number of Status messages sent with cell service congestion ............................................................. 1501 C901220022 Number of status messages sent with protocol error............................................................................ 1502 C901220023 Number of status messages sent with Processor overload....................................................................... 1502
1485
C901220024 Number of status messages received with BVCI Unknown...................................................................... 1502 C901220025 Number of status messages received with cell service congestion ......................................................... 1503 C901220026 Number of status messages received with protocol error .................................................................... 1503 C901220027 Number of status messages received with processor overload ............................................................. 1503 C901220028 Number of DOWNLOAD-BSS-PFC messages sent by BSC......................................................................... 1504 C901220029 Number of BVCCREATE-BSS-PFC messages received by BSC............................................................... 1505 C901220030 Number of CREATE-BSS-PFC-ACK messages sent by BSC.................................................................. 1505 C901220031 Number of CREATE-BSS-PFC-NACK messages sent by BSC.................................................................. 1506 C901220032 Number of MODIFY-BSS-PFC messages sent by BSC ............................................................................. 1507 C901220033 Number of MODIFY-BSS-PFC-ACK messages received by BSC............................................................... 1508 C901220034 Number of DELETE-BSS-PFC messages received by BSC......................................................................... 1509 C901220035 Number of DELETE-BSS-PFC-ACK messages sent by BSC.................................................................. 1510 C901220036 Number of DELETE-BSS-PFC-REQ messages received by BSC............................................................... 1511 C901220037 Number of PS-HANDOVER-REQUIRED messages sent by BSC.................................................................. 1511 C901220038 Number of PS-HANDOVER-REQUIRED-ACK messages received by BSC ............................................. 1512 C901220039 Number of PS-HANDOVER-REQUIRED-NACK messages received by BSC ............................................. 1513 C901220040 Number of PS-HANDOVER-REQUEST messages received by BSC ............................................................ 1514 C901220041 Number of PS-HANDOVER-REQUEST-ACK messages sent by BSC ......................................................... 1515 C901220042 Number of PS-HANDOVER-REQUEST-NACK messages sent by BSC ................................................... 1516 C901220043 Number of PS-HANDOVER-COMPLETE messages sent by BSC.................................................................. 1517 C901220044 Number of PS-HANDOVER-CANCEL messages sent by BSC.................................................................. 1518 C901220045 Number of PS-HANDOVER-REQUEST messages with Service UTRAN CCO received by BSC......................... 1519 C901220046 Number of CREATE-BSS-PFC messages with Service UTRAN CCO received by BSC ............................... 1520
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).
1486
This counter counts the number of sending UL-UNITDATA PDU to SGSN by BSC. This counter increments each time BSC sends a UL-UNITDATA message. The measurement point is A, as shown in Figure 1498.
FIGURE 1498 MEASUREMENT POINT HANDLED AT BSSGP LEVEL
OF SUM OF
UL UNITDATA
MESSAGE
Unit
Times
SGSN sends DL-UNITDATA PDU to BSC, and this counter counts the number of receiving this message by BSC. This counter increments each time BSC receives a DL-UNITDATA message. The measurement point is A, as shown in Figure 1499.
1487
POINT OF SUM OF
DL UNITDATA
MESSAGE
Unit
Times
SGSN sends RA-CAPABILITY message to BSC, to indicate wireless capability of MS. This counter counts the number of receiving this message. When BSC receives a RA-CAPABILITY message, this counter increments. The measurement point is A, as shown in Figure 1500.
FIGURE 1500 MEASUREMENT MESSAGE RECEVIED POINT
OF
Measurement Point
NUMBER
OF
RA-CAPABILITY
Unit
Times
1488
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. When BSC receives a PAGING PS message, this counter increments. The measurement point is A, as shown in Figure 1501.
FIGURE 1501 PTP PACKET PAGING PROCESS
Measurement Point
Unit
Times
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. When BSC receives a PAGING CS message, this counter increments. The measurement point is A, as shown in Figure 1502.
Measurement Point
1489
Unit
Times
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. When BSC sends a RA-CAPABILITY-UPDATE message to SGSN, this counter increments. The measurement point is A1, as shown in Figure 1503.
FIGURE 1503 RA-CAPABILITY-UPDATE PROCESS
Measurement Point
Unit
Times
1490
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. When BSC receives a RA-CAPABILITY-UPDATE-ACK message from SGSN, this counter increments. The measurement point is A2, as shown in Figure 1504.
FIGURE 1504 RA-CAPABILITY-UPDATE PROCESS
Measurement Point
Unit
Times
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. The radio interface status can be checked by counting this message. When BSC sends a RADIO-STATUS message to SGSN, this counter increments. The measurement point is A, as shown in Figure 1505.
1491
Unit
Times
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. The radio interface status can be checked by counting this message. When BSC sends a RADIO-STATUS message to SGSN due to Losing wireless association with MS, this counter increments. Times
1492
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. The radio interface status can be checked by counting this message. When BSC sends a RADIO-STATUS message to SGSN due to bad link quality, this counter increments. Times
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. The radio interface status can be checked by counting this message. When BSC sends a RADIO-STATUS message to SGSN due to cell reselection command, this counter increments. Times
1493
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. When BSC sends a FLOW-CONTROL-BVC message, this counter increments. The measurement point is A1, as shown in Figure 1506.
FIGURE 1506 FLOW-CONTROL-BVC PROCESS
Measurement Point
Unit
Times
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.
1494
Measurement Point
When BSC receives a FLOW-CONTROL-BVC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 1507.
FIGURE 1507 FLOW-CONTROL-BVC PROCESS
Unit
Times
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. When BSC sends the FLOW-CONTROL-MS message, this counter increments. The measurement point is A1, as shown in Figure 1508.
Measurement Point
1495
Unit
Times
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. When BSC receives a FLOW-CONTROL-MS-ACK message, this counter increments. The measurement point is A2, as shown in Figure 1509.
Measurement Point
1496
Unit
Times
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. When BSC sends the FLOW-CONTROL-PFC message, this counter increments. The measurement point is A1, as shown in Figure 1510.
Measurement Point
1497
Unit
Times
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. When BSC receives a FLOW-CONTROL-PFC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 1511.
Measurement Point
1498
Unit
Times
BSC sends the status message to SGSN to indicate that abnormality occurs. This counter counts the number of BSC's sending this message. When BSC sends the STATUS message, this counter increments. The measurement point is A1, as shown in Figure 1512.
Measurement Point
1499
Unit
Times
SGSN sends the status message to BSC to indicate that abnormality occurs. This counter counts the number of BSC's receiving this message. When BSC receives the STATUS message, this counter increments. The measurement point is A2, as shown in Figure 1513.
Measurement Point
1500
Unit
Times
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. When BSC sends a "STATUS" message due to BVCI Unknown, this counter increments. Times
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. When BSC sends a STATUS message due to cell service congestion, this counter increments.
Measurement Point
1501
Unit
Times
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. When BSC sends a STATUS message due to protocol error, this counter increments. Times
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. When BSC sends a STATUS message due to processor overload, this counter increments. Times
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. When BSC receives a STATUS message due to BVCI Unknown, this counter increments. Times
1502
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. When BSC receives a STATUS message due to cell service congestion, this counter increments. Times
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. When BSC receives a STATUS message due to protocol error, this counter increments. Times
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. When BSC receives a STATUS message due to processor overload, this counter increments. Times
1503
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. When BSC sends the DOWNLOAD-BSS-PFC message, this counter increments. The measurement point is A1, as shown in Figure 1514.
FIGURE 1514 CREATE-BSS-PFC PROCESS
Measurement Point
Unit
Times
1504
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. When BSC receives a CREATE-BSS-PFC message, this counter increments. The measurement point is A2, as shown in Figure 1515.
FIGURE 1515 CREATE-BSS-PFC PROCESS
Measurement Point
Unit
Times
BSC sends the CREATE-BSS-PFC-ACK message to acknowledge the request of SGSN creating or modifying a packet flow control con-
1505
text. This counter counts the number of BSC's sending this message.
Measurement Point
When BSC sends a CREATE-BSS-PFC-ACK message, this counter increments. The measurement point is A3, as shown in Figure 1516.
FIGURE 1516 CREATE-BSS-PFC PROCESS
Unit
Times
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. When BSC sends a CREATE-BSS-PFC-NACK message, this counter increments. The measurement point is A4, as shown in Figure 1517.
Measurement Point
1506
Unit
Times
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. When BSC sends the MODIFY-BSS-PFC message, this counter increments. The measurement point is A1, as shown in Figure 1518.
Measurement Point
1507
Unit
Times
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. When BSC receives a MODIFY-BSS-PFC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 1519.
Measurement Point
1508
Unit
Times
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. When BSC receives a DELETE-BSS-PFC message, this counter increments. The measurement point is A1, as shown in Figure 1520.
Measurement Point
1509
Unit
Times
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. When BSC sends a DELETE-BSS-PFC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 1521.
Measurement Point
1510
Unit
Times
BSC This counter counts the number of PS-HANDOVER-REQUIRED messages sent to SGSN from BSC. The counter increments when BSC sends a PS-HANDOVER-REQUIRED message. The measurement point is A, as shown in Figure 1522.
1511
OF
PS-HANDOVER-
Unit
Times
BSC After a PS handover request is acknowledged, SGSN sends the PS-HANDOVER-REQUIRED-ACK message to BSC. This counter counts the number of PS-HANDOVER-REQUIRED-ACK messages received by BSC from SGSN. The counter increments when BSC receives the PS-HANDOVER-REQUIRED-ACK message. The measurement point is A, as shown in Figure 1523.
1512
OF
PS-HANDOVER-
Unit
Times
BSC If SGSN receives the non-acknowledgement message for PS handover request from BSC, then SGSN sends the PS-HANDOVER-REQUIRED-NACK message back to BSC. This counter counts the number of PS-HANDOVER-REQUIRED-NACK messages received by BSC from SGSN. The counter increments when BSC receives the PS-HANDOVER-REQUIRED-NACK message. The measurement point is A, as shown in Figure 1524.
1513
Unit
Times
BSC This counter counts the number of PS-HANDOVER-REQUEST messages received by BSC from SGSN. The counter increments when BSC receives the PS-HANDOVER-REQUEST message. The measurement point is A2, as shown in Figure 1525.
1514
OF
PS-HANDOVER-
Unit
Times
BSC This counter counts the number of PS-HANDOVER-REQUEST-ACK messages sent by BSC. The counter increments when BSC sends the PS-HANDOVER-REQUEST-ACK message. The measurement point is A3, as shown in Figure 1526.
1515
OF
PS-HANDOVER-
Unit
Times
BSC During the handover, if the channel request fails or the cell does not support PS handover, then creating MS or PS instance will fail. This counter counts the number of messages, which indicate failure of creating MS or PS instance, sent by BSC. The counter incre-
1516
ments when BSC sends the PS-HANDOVER-REQUEST-NACK message. The measurement point is A3, as shown in Figure 1527.
FIGURE 1527 MEASUREMENT POINT OF NUMBER REQUEST-NACK MESSAGES SENT BY BSC
OF
PS-HANDOVER-
Unit
Times
BSC When the destination cell receives the first RLC/MAC block sent from MS, it indicates that the handover is completed. This counter counts the number of PS-HANDOVER-COMPLETE messages sent
1517
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 1528.
FIGURE 1528 MEASUREMENT POINT OF NUMBER COMPLETE MESSAGES SENT BY BSC
OF
PS-HANDOVER-
Unit
Times
BSC If PS handover fails or waiting for handover is timeout, BSC sends the PS-HANDOVER-CANCEL message to SGSN. This counter counts the number of PS-HANDOVER-CANCEL messages sent by BSC. The counter increments when BSC sends the PS-HANDOVER-CANCEL message. The measurement point is A, as shown in Figure 1529.
1518
OF
NUMBER
OF
PS-HANDOVER-
Unit
Times
C901220045 Number of PS-HANDOVER-REQUEST messages with Service UTRAN CCO received by BSC
Statistics object Description
BSC After BSC receives the PS-HANDOVER-REQUEST message from SGSN, the message might contains the field Service UTRAN CCO, which indicates that 2G/3G handover is preferred. This counter counts the number of PS-HANDOVER-REQUEST messages, which contains the field Service UTRAN CCO, received by BSC. After BSC receives the PS-HANDOVER-REQUEST message from SGSN, it decodes the message to decide whether the message contains the field Service UTRAN CCO. If the message contains the field, the counter increments. The measurement point is A, as shown in Figure 1530.
1519
FIGURE 1530 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUEST MESSAGES WITH SERVICE UTRAN CCO RECEIVED BY BSC
Unit
Times
C901220046 Number of CREATE-BSS-PFC messages with Service UTRAN CCO received by BSC
Statistics object Description
BSC When BSC receives the CREATE-BSS-PFC message from SGSN, the message might contain the field Service UTRAN CCO. This counter counts the number of CREATE-BSS-PFC messages, which contains the field Service UTRAN CCO, received by BSC. After BSC receives the CREATE-BSS-PFC message from SGSN, it decodes the message to decide whether the message contains the field Service UTRAN CCO. If the message contains the field, the counter increments. The measurement point is A, as shown in Figure 1531.
1520
FIGURE 1531 MEASUREMENT POINT OF NUMBER OF CREATE-BSS-PFC MESSAGES WITH SERVICE UTRAN CCO RECEIVED BY BSC
Unit
Times
1521
1522
Chapter
29
TRX Measurement
Table of Contents Overview...................................................................... 1525 C901230001 Number of intra-cell handover in attempts ......................................................................... 1525 C901230002 Number of intra-cell handover ins success............................................................................. 1526 C901230003 Number of Intra-BSC inter-cell handover in attempts ......................................................................... 1526 C901230004 Number of Intra-BSC intra-cell handover ins success ........................................................................ 1527 C901230005 Number of Intra-MSC inter-cell handover in attempts ......................................................................... 1528 C901230006 Number of Intra-MSC inter-cell handover ins success ........................................................................ 1529 C901230007 TCH busy time............................................ 1529 C901230008 Number of TCH seizures (including handover) ......................................................................... 1530 C901230009 Number of call drops due to TCH LAPD breakage.............................................................................. 1530 C901230010 Number of call drops due to TCH radio link failure .............................................................................. 1531 C901230011 Number of TCH handover call drops............... 1531 C901230012 Number of TCH/F activation attempts (including handover) .................................................................... 1532 C901230013 Number of TCH/F activation success (including handover) .................................................................... 1533 C901230014 Number of TCH/F assignment attempts.......... 1534 C901230015 Number of TCH/F assignment success............ 1534 C901230016 Number of TCH/H activation attempts (including handover) .................................................................... 1535 C901230017 Number of TCH/H activation success (including handover) .................................................................... 1536 C901230018 Number of TCH/H assignment attempts ......... 1536 C901230019 Number of TCH/H assignment success ........... 1537 C901230020 SDCCH busy time ....................................... 1538 C901230021 Number of attempts for SDCCH .................... 1539 C901230022 Number of SDCCH call drops ........................ 1539 C901230023 Number of SDCCH activation attempts (including handover) ............................................................... 1541 C901230024 Number of SDCCH activation success (including handover) .................................................................... 1541 C901230025 Number of SDCCH assignment attempts......... 1542 C901230026 Number of SDCCH assignment success .......... 1543 C901230027 Number of samples with UL RQ = 0 ............... 1543 C901230028 Number of samples with UL RQ = 1 ............... 1544 C901230029 Number of samples with UL RQ = 2 ............... 1545 C901230030 Number of samples with UL RQ = 3 ............... 1545
1523
C901230031 Number of samples with UL RQ = 4 ............... 1546 C901230032 Number of samples with UL RQ = 5 ............... 1546 C901230033 Number of samples with UL RQ = 6 ............... 1547 C901230034 Number of samples with UL RQ = 7 ............... 1547 C901230035 Number of samples with DL RQ = 0............... 1548 C901230036 Number of samples with DL RQ = 1............... 1548 C901230037 Number of samples with DL RQ = 2............... 1549 C901230038 Number of samples with DL RQ = 3............... 1550 C901230039 Number of samples with DL RQ = 4............... 1550 C901230040 Number of samples with DL RQ = 5............... 1551 C901230041 Number of samples with DL RQ = 6............... 1551 C901230042 Number of samples with DL RQ = 7............... 1552 C901230043 Mean number of idle TCH/Fs with interference band 0 ......................................................................... 1552 C901230044 Mean number of idle TCH/Fs with interference band 1 ......................................................................... 1553 C901230045 Mean number of idle TCH/Fs with interference band 2 ......................................................................... 1553 C901230046 Mean number of idle TCH/Fs with interference band 3 ......................................................................... 1554 C901230047 Mean number of idle TCH/Fs with interference band 4 ......................................................................... 1554 C901230048 Mean number of idle TCH/Fs with interference band 5 ......................................................................... 1554 C901230049 Mean number of idle TCH/Hs with interference band 0 ......................................................................... 1555 C901230050 Mean number of idle TCH/Hs with interference band 1 ......................................................................... 1555 C901230051 Mean number of idle TCH/Hs with interference band 2 ......................................................................... 1555 C901230052 Mean number of idle TCH/Hs with interference band 3 ......................................................................... 1556 C901230053 Mean number of idle TCH/Hs with interference band 4 ......................................................................... 1556 C901230054 Mean number of idle TCH/Hs with interference band 5 ......................................................................... 1557 C901230055 Mean number of idle SDCCHs with interference band 0 ......................................................................... 1557 C901230056 Mean number of idle SDCCHs with interference band 1 ......................................................................... 1557 C901230057 Mean number of idle SDCCHs with interference band 2 ......................................................................... 1558 C901230058 Mean number of idle SDCCHs with interference band 3 ......................................................................... 1558 C901230059 Mean number of idle SDCCHs with interference band 4 ......................................................................... 1558 C901230060 Mean number of idle SDCCHs with interference band 5 ......................................................................... 1559 C901230061 Number of TRX poweroff .............................. 1559 C901230062 Duration of TRX poweroff ............................. 1559 C901230063 Number of uplink error frame on FR_V1 ......... 1560 C901230064 Total Number of uplink frame on FR_V1 ......... 1560 C901230065 Number of uplink error frame on FR_V2 ......... 1560 C901230066 Total Number of uplink frame on FR_V2 ......... 1561 C901230067 Number of uplink error frame on FR_V3 ......... 1561 C901230068 Total Number of uplink frame on FR_V3 ......... 1561 C901230069 Number of uplink error frame on HR_V1......... 1562 C901230070 Total Number of uplink frame on HR_V1 ......... 1562 C901230071 Number of uplink error frame on HR_V3......... 1562 C901230072 Total Number of uplink frame on HR_V3 ......... 1563
1524
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.
Number of intra-cell handover in attempts. 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. During intra-cell handover, measurement point will be counted after BSC receives CHANNEL ACTIVATE ACK. The measurement point is A, as shown in Figure 1532.
FIGURE 1532 - INTRA-CELL HANDOVER
Measurement Point
1525
Number of intra-cell handover ins success. 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. During intra-cell handover, the measurement point will be counted after receive ASSIGNMENT COMPLETE. The measurement point is A2, as shown in Figure 1533.
FIGURE 1533 - INTRA-CELL HANDOVER
Measurement Point
Number of Intra-BSC inter-cell handover in attempts During inter-cell handover controlled by BSC, source and target cells are different cells under same BSC. During inter-cell handover, first send CHANNEL ACTIVATE message to target channel.
1526
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 1534.
FIGURE 1534 - INTER-CELL HANDOVER CONTROLLED BY BSC
Number of Intra-BSC intra-cell handover ins success. 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. 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 1535.
Measurement Point
1527
Number of Intra-MSC inter-cell handover in attempts 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. During inter-cell handover (incoming) controlled by MSC, measurement point will be counted after BSC receives CHANNEL ACTIVATE ACK. The measurement point is A1, as shown in Figure 1536.
FIGURE 1536 - INTER-CELL HANDOVER CONTROLLED BY BSC
Measurement Point
Unit
Times
1528
Related Features
Number of Intra-MSC inter-cell handover ins success. 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. During inter-cell handover controlled by MSC, measurement point will be counted after BSC receives HANDOVER COMPLETE message from MS. The measurement point is A2, as shown in Figure 1537.
FIGURE 1537 - INTER-CELL HANDOVER CONTROLLED BY BSC
Measurement Point
TCH busy time To count used time in voice channel on carrier, including TCH/F and TCH/H. This can reflect carrier traffic. Measurement formula is: (current time last measured time) * the number of MS seizing channel. Reported measurement value shall be gotten by accumulation of each measurement value. After each accumulation, previous measured time will be changed to current time; at measurement point A, the number of MS seizing channel will increment after accumulation; at measurement point
1529
There are 3 measurement points: Accumulate while successfully acquire voice channel resource Accumulate while release voice channel resource Accumulate by regular measurement and acquisition
Unit
Second
Number of TCH seizures (including handover) The number of seizure voice channel on carrier, including TCH/F and TCH/H. This can reflect the traffic busy degree of carrier. Count while successfully acquire voice channel service. Times
Number of call drops due to TCH LAPD breakage. When LAPD link is disconnected, the call on carrier will be interrupted, and this counter will record call interruption condition caused by disconnected LAPD. Count while receive LAPD Disconnected message. Times
1530
Number of call drops due to TCH radio link failure. 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. Count while receiving radio link failure message. The measurement point is A, as shown in Figure 1538.
FIGURE 1538 - BSC RECEIVES RADIO LINK FAILURE MESSAGE REPORTED BY BTS
Measurement Point
Unit
Times
Number of TCH handover call drops. During handover, if HANDOVER COMMAND or ASSIGNMENT COMMAND (intra-cell handover) has been sent, but BSC doesnt receive HANDOVER COMPLETE message or ASSIGNMENT COMPLETE message during guard time, the handover is failed and intra-cell handover and BSC controlled intercell handover will be interrupted. This counter records the call interruption condition caused by handover failure. This counter will count at following cases: When receiving T3013 timer timeout message. The measurement point is A2, as shown in Figure 1539.
Measurement Point
1531
When receiving T3107 timer timeout message. The measurement point is A2, as shown in .Figure 1540.
FIGURE 1540 - INTRA-CELL HANDOVER FAILURE
Unit
Times
Number of TCH/F activation attempts (including handover) Count the number of originating CHANNEL ACTIVATE messages from carrier TCH/F channel. Count after BSC sends CHANNEL ACTIVATE message to BTS. The measurement point is A1, as shown inFigure 1541.
1532
Number of TCH/F activation success (including handover) Count the number of successful activation from carrier TCH/F channel. Count after BSC receives CHANNEL ACTIVATE ACK message. The measurement point is A2, as shown inFigure 1542 .
FIGURE 1542 - CHANNEL ACTIVATION MEASUREMENT POINT
1533
Number of TCH/F assignment attempts. Count the number of sending ASSIGNMENT COMMAND by BSC while assigning TCH/F channel. Count after BSC sends ASSIGNMENT COMMAND message to BTS. The measurement point is A1, as shownFigure 1543.
FIGURE 1543 - TCH/F CHANNEL ASSIGNMENT MEASUREMENT POINT
Number of TCH/F assignment success 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. Count after BSC receives EST IND or ASSIGNMENT COMPLETE message. The measurement point is A2, as shown inFigure 1544.
Measurement Point
1534
Number of TCH/H activation attempts (including handover). Count the number of originating channel activation from carrier TCH/H channel. Count after BSC sends CHANNEL ACTIVATE message to BTS. The measurement point is A1, as shown inFigure 1545.
FIGURE 1545 - CHANNEL ACTIVATION MEASUREMENT POINT
1535
Number of TCH/H activation success (including handover). Count the number of successful activation from carrier TCH/H channel. Count after BSC receives CHANNEL ACTIVATE ACK message. The measurement point is A2, as shown inFigure 1546 .
FIGURE 1546 - CHANNEL ACTIVATION MEASUREMENT POINT
Number of TCH/H assignment attempts Count the number of sending ASSIGNMENT COMMAND by BSC while assigning TCH/H channel.
1536
Measurement Point
Count after BSC sends ASSIGNMENT COMMAND message to BTS. The measurement point is A1, as shown inFigure 1547 .
FIGURE 1547 - TCH/F CHANNEL ASSIGNMENT MEASUREMENT POINT
Number of TCH/H assignment success 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. Count after BSC receives EST IND or ASSIGNMENT COMPLETE message. The measurement point is A2, as shown inFigure 1548 .
Measurement Point
1537
SDCCH busy time Time used by SDCCH channel on carrier, including assignment and handover. This can reflect traffic of carrier SDCCH channel. Measurement formula is: (current time last measured time) * the number of MS seizing channel. Reported measurement value shall be gotten by accumulation of each measurement value. After each accumulation, previous measured time will be changed to current time; when SDCCH channel is seized, the number of MS seizing channel will be incremented after accumulation; when SDCCH channel is released, the number of MS seizing channel will be decremented after accumulation.
Measurement Point
There are 3 measurement points as follows. Accumulate while successfully acquire SDCCH channel resource Accumulate while release SDCCH channel resource Accumulate by regular measurement and acquisition
Unit
Times
1538
Number of attempts for SDCCH Count the number of successful and failed SDCCH application during assignment and handover. Count after BSC applying for SDCCH is successful or failed. Times
Number of SDCCH call drops During assignment and handover, ASSIGNMENT COMPLETE or HANDOVER send ASSIGNMENT COMMAND or HANDOVER or T3107 timer times out, it is considered as SDCCH failure, see Figure 1549 andFigure 1550.
COMPLETE is not received after COMMAND message. After T3103
1539
If handover to external cell, when HANDOVER COMMAND is delivered, start THoOutGo, CLEAR COMMAND of MSC is not received before THoOutGo times out, it is considered as SDCCH failure, as shown inFigure 1551 .
FIGURE 1551 - THOOUTGO TIMEOUT
In addition, when LAPD is broken or disconnected, if channel is SDCCH, it will be recorded as SDCCH call drops.
Measurement Point
This counter will count at following cases: When BSC receives LAPD breakage message and channel is SDCCH. When BSC connection faults and channel is SDCCH. After THoOutGo timer times out. After T3103 timer times out. After T3107 timer times out.
Unit
Times
1540
Number of SDCCH activation attempts (including handover) Count the number of originating CHANNEL ACTIVATE messages from carrier SDCCH channel. Count after BSC sends CHANNEL ACTIVATE message to BTS. The measurement point is A1, as shown inFigure 1552 .
FIGURE 1552 - CHANNEL ACTIVATION MEASUREMENT POINT
Unit
Times
Number of SDCCH activation success (including handover) Count the number of successful activation from carrier SDCCH channel. Count after BSC receives CHANNEL ACTIVATE ACK message. The measurement point is A2, as shown inFigure 1553 .
1541
Unit
Times
Number of SDCCH assignment attempts 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. Count after BSC sends IMMEDIATE ASSIGNMENT message or ASSIGNMENT COMMAND to BTS. The measurement point is A1, as shown in Figure 1554.
FIGURE 1554 - CHANNEL ASSIGNMENT MEASUREMENT POINT
Measurement Point
1542
Unit
Times
Number of SDCCH assignment success 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. Count after BSC receives EST IND (CM SERV REQ) message. The measurement point is A2, as shown in Figure 1555.
FIGURE 1555 - CHANNEL ASSIGNMENT MEASUREMENT POINT
Measurement Point
Unit
Times
Number of samples with UL RQ = 0 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.
1543
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 1556.
FIGURE 1556 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with UL RQ = 1 This measurement value is the sample number with UL RQ=1 in measurement report. 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 1557.
FIGURE 1557 - BSC RECEIVES BY BTS
THE
Unit
Times
1544
Number of samples with UL RQ = 2 This measurement value is the sample number with UL RQ=2 in measurement report. 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 1558.
FIGURE 1558 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with UL RQ = 3 This measurement value is the sample number with UL RQ=3 in measurement report. 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 1559.
FIGURE 1559 - BSC RECEIVES BY BTS
THE
1545
Unit
Times
Number of samples with UL RQ = 4 This measurement value is the sample number with UL RQ=4 in measurement report. 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 1560.
FIGURE 1560 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with UL RQ = 5 This measurement value is the sample number with UL RQ=5 in measurement report. 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 1561.
1546
THE
Unit
Times
Number of samples with UL RQ = 6 This measurement value is the sample number with UL RQ=6 in measurement report. 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 1562.
FIGURE 1562 - BSC RECEIVES BY BTS
THE
Unit
Times
This measurement value is the sample number with UL RQ=7 in measurement report.
1547
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 1563.
FIGURE 1563 BSC RECEIVES BTS
THE
BY
Unit
Times
Number of samples with DL RQ = 0 This measurement value is the sample number with DL RQ=1 in measurement report. 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 1564.
FIGURE 1564 - BSC RECEIVES BY BTS
THE
Unit
Times
1548
This measurement value is the sample number with DL RQ=1 in measurement report. 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 1565.
FIGURE 1565 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with DL RQ = 2 This measurement value is the sample number with DL RQ=2 in measurement report. 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 1566.
FIGURE 1566 - BSC RECEIVES BY BTS
THE
Unit
Times
1549
Number of samples with DL RQ = 3 This measurement value is the sample number with DL RQ=3 in measurement report. 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 1567.
FIGURE 1567 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with DL RQ = 4 This measurement value is the sample number with DL RQ=4 in measurement report. 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 1568.
FIGURE 1568 - BSC RECEIVES BY BTS
THE
1550
Unit
Times
Number of samples with DL RQ = 5 This measurement value is the sample number with DL RQ=5 in measurement report. 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 1569.
FIGURE 1569 - BSC RECEIVES BY BTS
THE
Unit
Times
Number of samples with DL RQ = 6 This measurement value is the sample number with DL RQ=6 in measurement report. 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 1570.
1551
THE
Unit
Times
Number of samples with DL RQ = 7 This measurement value is the sample number with DL RQ=7 in measurement report. 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 1571.
FIGURE 1571 - BSC RECEIVES BY BTS
THE
Unit
Times
1552
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. Count when regularly query database. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
Mean number of idle TCH/Fs with interference band 1 This measurement value is idle TCH/F number when interference band is 1 in carrier. Count when regularly query database. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
Mean number of idle TCH/Fs with interference band 2 This measurement value is idle TCH/F number when interference band is 2 in carrier. Count when regularly query database. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
1553
Mean number of idle TCH/Fs with interference band 3 This measurement value is idle TCH/F number when interference band is 3 in carrier. Count when regularly query database. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
Mean number of idle TCH/Fs with interference band 4 This measurement value is idle TCH/F number when interference band is 4 in carrier. Count when regularly query database. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
Mean number of idle TCH/Fs with interference band 5 This measurement value is idle TCH/F number when interference band is 5 in carrier. Count when regularly query database. Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec
1554
Mean number of idle TCH/Hs with interference band 0 This measurement value is idle TCH/H number when interference band is 0 in carrier. Count when regularly query database. Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
Mean number of idle TCH/Hs with interference band 1 This measurement value is idle TCH/H number when interference band is 1 in carrier. Count when regularly query database. Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
Mean number of idle TCH/Hs with interference band 2 This measurement value is idle TCH/H number when interference band is 2 in carrier. Count when regularly query database.
1555
Mean number of idle TCH/Hs with interference band 3 This measurement value is idle TCH/H number when interference band is 3 in carrier. Count when regularly query database. Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
Mean number of idle TCH/Hs with interference band 4. This measurement value is idle TCH/H number when interference band is 4 in carrier. Count when regularly query database. Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
1556
Mean number of idle TCH/Hs with interference band 5. This measurement value is idle TCH/H number when interference band is 5 in carrier. Count when regularly query database. Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation
Mean number of idle SDCCHs with interference band 0 This measurement value is idle SDCCH number when interference band is 0 in carrier. Count when regularly query database. Times
Mean number of idle SDCCHs with interference band 1 This measurement value is idle SDCCH number when interference band is 1 in carrier. Count when regularly query database. Times
1557
Mean number of idle SDCCHs with interference band 2 This measurement value is idle SDCCH number when interference band is 2 in carrier. Count when regularly query database. Times
Mean number of idle SDCCHs with interference band 3 This measurement value is idle SDCCH number when interference band is 3 in carrier. Count when regularly query database. Times
Mean number of idle SDCCHs with interference band 4 This measurement value is idle SDCCH number when interference band is 4 in carrier. Count when regularly query database. Times
1558
Mean number of idle SDCCHs with interference band 5 This measurement value is idle SDCCH number when interference band is 5 in carrier. Count when regularly query database. Times
Number of TRX power off. This counter counts the number of TRX smart power off, excluding normal POWER OFF. This counter increments during smart power on. Times ZGO-04-04-002 Intelligent TRX Shutdown
Duration of TRX power off. This counter counts the duration of TRX power off. This counter increments during smart power on. Times ZGO-04-04-002 Intelligent TRX Shutdown
1559
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. The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received. Times
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. The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received. Times
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. The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received. Times
1560
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. The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received. Times
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. The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received. Times
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. The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received. Times
1561
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. The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received. Times
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. The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received. Times
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. The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received. Times
1562
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. The counter counts when the measurement report (preprocessing measurement report or enhanced measurement report) is received. Times
1563
1564
Chapter
30
Timeslot Measurement
Table of Contents Overview...................................................................... 1566 C901240001 Maximum value of UL RQ ............................. 1566 C901240002 Minimum value of UL RQ .............................. 1567 C901240003 Value of UL RQ ........................................... 1567 C901240004 Number of scans of UL RQ............................ 1568 C901240005 Maximum value of DL RQ ............................. 1569 C901240006 Minimum value of DL RQ.............................. 1569 C901240007 Value of DL RQ ........................................... 1570 C901240008 Number of scans of DL RQ ........................... 1570 C901240009 Maximum value of received UL signal strength ....................................................................... 1571 C901240010 Minimum value of received UL signal strength ....................................................................... 1572 C901240011 Total value of received UL signal strength......... 1572 C901240012 Number of received UL signal strength samples ............................................................................. 1573 C901240013 Maximum value of received DL signal strength ....................................................................... 1574 C901240014 Minimum value of received DL signal strength ....................................................................... 1574 C901240015 Total value of received DL signal strength......... 1575 C901240016 Number of received DL signal strength samples ............................................................................. 1575 C901240017 Value of power scans of MS transmitting power .......................................................................... 1576 C901240018 Number of power scans of MS transmitting power .......................................................................... 1577 C901240019 Value of power scans of BTS power ............... 1577 C901240020 Number of power scans of BTS power ............ 1578 C901240021 Number of immediate assignment failure......... 1578 C901240022 Number of assignment failure ....................... 1579 C901240023 Number of handovers failure ........................ 1580 C901240024 Maximum interference value......................... 1581 C901240025 Minimum interference value ......................... 1581 C901240026 Interference value....................................... 1582 C901240027 Number of regular scanning and sampling of interference value ............................................................ 1583 C901240028 Number of call drop..................................... 1583 C901240029 Maximum value of path balance .................... 1584 C901240030 Minimum value of path balance..................... 1584 C901240031 Value of path balance .................................. 1585 C901240032 Number of regular scanning and sampling of path balance................................................................. 1586 C901240033 Value of UL loss .......................................... 1586 C901240034 Number of regular scanning and sampling of UL loss ............................................................................. 1587
1565
C901240035 Total value of DL loss................................... 1587 C901240036 Number of regular scanning and sampling of DL loss ............................................................................. 1588 C901240037 Number of drops due to the bad quality of UL receive......................................................................... 1589 C901240038 Number of drops due to the bad quality of DL receive......................................................................... 1590 C901240039 Number of drops due to the low electric level of UL ............................................................................... 1592 C901240040 Number of drops due to the low electric level of DL ............................................................................... 1594 C901240041 Number of drops due to the TA too far ........... 1596 C901240042 Number of drops due to the other radio reasons ............................................................................ 1598 C901240043 The valid time of the used voice channel......... 1600 C901240044 Number of activated voice channel ................ 1601
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.
Maximum UL RQ This counter counts Maximum UL RQ in the measurement report of a timeslot in a cell. 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. After BSC receives the measurement report from BTS, if UL RQ in the report is bigger than the value in the counter, the UL RQ in the counter is replaced. The measurement point is A, as shown in Figure 1572.
Measurement Point
1566
Unit
NA
Minimum UL RQ This counter counts Minimum UL RQ in the measurement report of a timeslot in a cell. 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. 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 1573.
FIGURE 1573 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
NA
C901240003 Value of UL RQ
Definition Description
Total value of UL RQ This counter counts the total value of UL RQ of a timeslot of a cell in the measurement report.
1567
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. 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 1574.
FIGURE 1574 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
NA
Number of scans of UL RQ This counter counts the number of times of sampling UL RQ of a timeslot in a cell. 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. The counter increments after BSC receives the measurement report from BTS. The measurement point is A, as shown in Figure 1575.
FIGURE 1575 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
Times
1568
Maximum value of DL RQ This counter counts Maximum DL RQ in the measurement report of a timeslot in a cell. 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. After BSC receives the measurement report from BTS, if DL RQ in the report is bigger than the value in the counter, the DL RQ is in the counter replaced. The measurement point is A, as shown in Figure 1576
FIGURE 1576 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
NA
Minimum DL RQ This counter counts Minimum DL RQ in the measurement report of a timeslot in a cell. 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. 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 1577.
Measurement Point
1569
Unit
NA
C901240007 Value of DL RQ
Definition Description Usage
Total value of DL RQ This counter counts the total value of DL RQ of a timeslot of a cell in the measurement report. 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. 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 1578.
FIGURE 1578 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
NA
Number of scans of DL RQ This counter counts the number of times of sampling DL RQ of a timeslot in a cell.
1570
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. The counter increments after BSC receives the measurement report from BTS. The measurement point is A, as shown in Figure 1579.
FIGURE 1579 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
Times
Maximum value of received UL signal strength This counter counts Maximum value of received UL signal strength in the measurement report of a timeslot in a cell. 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. 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 1580.
FIGURE 1580 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
dBm
1571
Minimum value of received UL signal strength This counter counts Minimum value of received UL signal strength in the measurement report of a timeslot in a cell. 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. After BSC receives the measurement report from BTS, if the value of received UL signal strength in the report is less than the value in the counter, the received UL signal strength in the counter is replaced. The measurement point is A, as shown in Figure 1581.
FIGURE 1581 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
dBm
Total value of received UL signal strength This counter counts the total value of received UL signal strength of a timeslot of a cell in the measurement report. 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. 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 1582.
Measurement Point
1572
Unit
dBm
Number of received UL signal strength samples This counter counts the number of times of sampling UL signal strength in a timeslot in a cell. 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. The counter increments after BSC receives the measurement report from BTS. The measurement point is A, as shown in Figure 1583.
FIGURE 1583 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
Times
1573
Maximum value of received DL signal strength This counter counts Maximum value of received DL signal strength in the measurement report of a timeslot in a cell. 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. After BSC receives the measurement report from BTS, if DL reception strength in the report is bigger than the value in the counter, the DL reception strength in the counter is replaced. The measurement point is A, as shown in Figure 1584.
FIGURE 1584 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
dBm
Minimum value of received DL signal strength This counter counts Minimum value of received DL signal strength in the measurement report of a timeslot in a cell. 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. After BSC receives the measurement report from BTS, if DL reception strength in the report is less than the value in the counter, the DL reception strength in the counter is replaced. The measurement point is A, as shown in Figure 1585.
Measurement Point
1574
Unit
dBm
Total value of received DL signal strength This counter counts the total value of received DL signal strength in a timeslot in a cell in the measurement report. 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. 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 1586.
FIGURE 1586 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
dBm
1575
Description Usage
This counter counts the number of times of sampling received DL signal strength in a timeslot in a cell. 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. The counter increments after BSC receives the measurement report from BTS. The measurement point is A, as shown in Figure 1587.
FIGURE 1587 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
Times
Total value of power scans of MS transmitting power This counter counts the total value of MS transmitting power in a timeslot in a cell in the measurement report. 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. 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 1588.
FIGURE 1588 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
dBm
1576
Number of power scans of MS transmitting power This counter counts the number of times of sampling MS transmitting power in a timeslot in a cell. 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. The counter increments after BSC receives the measurement report from BTS. The measurement point is A, as shown in Figure 1589.
FIGURE 1589 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
Times
Total value of power scans of BTS power This counter counts the total value of BTS power in a timeslot in a cell in the measurement report. 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. 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 1590.
Measurement Point
1577
Unit
dBm
Number of power scans of BTS power This counter counts the number of times of sampling BTS power in a timeslot in a cell. 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. The counter increments after BSC receives the measurement report from BTS. The measurement point is A, as shown in Figure 1591.
FIGURE 1591 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
dBm
1578
Description Usage
This counter counts the number of times of immediate assignment failure in a timeslot in a cell. 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. After BSC sent immediate assignment to MS, if access Timer overtimes, the counter increments in relevant timeslot. The measurement point is A2, as shown in Figure 1592. In the waiting state, case release caused by any reason, leads immediate assignment failure, then the counter increments in relevant timeslot. The measurement point is A1, as shown in Figure 1592.
FIGURE 1592 IMMEDIATE ASSIGNMENT FAILURE MEASUREMENT POINT
Measurement Point
Unit
Times
Number of assignment failure This counter counts the number of times of assignment failure in a timeslot in a cell. 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. 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 1593. 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 1593.
Measurement Point
1579
Unit
Times
Number of handovers failure This counter counts the number of times of handover failure in a timeslot in a cell. 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. 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 1594. 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 1594.
FIGURE 1594 HANDOVERS FAILURE MEASUREMENT POINT
Measurement Point
Unit
Times
1580
Maximum interference value This counter counts the Maximum interference band value in a timeslot in a cell. 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. When BSC received resource indication from BTS updating interference band, if interference band reported is bigger than the value in the counter, the value in the counter is replaced. The measurement point is A, as shown in Figure 1595.
FIGURE 1595 RESOURCE INDICATION MEASUREMENT POINT
Measurement Point
Unit
NA
Minimum interference value This counter counts the Minimum interference band value in a timeslot in a cell. 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. When BSC received resource indication from BTS updating interference band, if interference band reported is less than the value in the counter, the value in the counter is replaced. The measurement point is A, as shown in Figure 1596.
Measurement Point
1581
Unit
NA
Total value of interference This counter counts the total value of interference band in a timeslot in a cell. 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. When BSC received resource indication from BTS updating interference band, the counter accumulates interference value for relevant timeslot. The measurement point is A, as shown in Figure 1597.
FIGURE 1597 RESOURCE INDICATION MEASUREMENT POINT
Measurement Point
Unit
NA
1582
Number of regular scanning and sampling of interference value This counter counts the number of times of interference band value report in a timeslot in a cell. 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. The counter increments in relevant timeslot after BSC receives resource indication from BTS updating interference band. The measurement point is A, as shown in Figure 1598.
FIGURE 1598 RESOURCE INDICATION MEASUREMENT POINT
Measurement Point
Unit
Times
Number of call drop This counter counts the number of call drop caused by radio link failure in a timeslot in a cell. 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. The counter increments in relevant timeslot after BSC receives radio link failure from BTS. The measurement point is A, as shown in Figure 1599.
Measurement Point
1583
Unit
Times
Maximum value of path balance 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. 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. 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 1600.
FIGURE 1600 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
dBm
1584
Description Usage
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. 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. 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 1601.
FIGURE 1601 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
dBm
Total value of path balance This counter counts the total value of path balance in a timeslot in a cell. 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. 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 1602.
FIGURE 1602 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
dBm
1585
Number of path balance sampling This counter counts the number of path balance sampling in a timeslot in a cell. 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. 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 1603.
FIGURE 1603 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
Times
Total value of UL loss This counter counts the total value of UL loss in a timeslot in a cell. 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. 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 1604.
Measurement Point
1586
Unit
dBm
Number of regular scanning and sampling of UL loss This counter counts the number of UL loss in a timeslot in a cell. 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. 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 1605.
FIGURE 1605 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
Times
Total value of DL loss This counter counts the maximum of DL loss in a timeslot in a cell.
1587
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. 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 1606.
FIGURE 1606 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
dB
Number of regular scanning and sampling of DL loss This counter counts the number of DL loss in a timeslot in a cell. 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. 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 1607.
FIGURE 1607 BSC RECEIVES THE MEASUREMENT REPORT SUBMITTED BY BTS
Measurement Point
Unit
Times
1588
Number of drops due to the bad quality of UL receive 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. 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. The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on SDCCH. The measurement point is A, as shown in Figure 1608.
FIGURE 1608 CALL DROP DUE TO RADIO LINK FAILURE IMMEDIATE ASSIGNMENT PROCESS
DURING
Usage
Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH. The measurement point is A, as shown in Figure 1609.
1589
DUE TO
DURING
Unit
Times
Number of drops due to the bad quality of DL receive 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. 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
Usage
1590
receiving quality. It is one of the radio parameters that evaluate the timeslot.
Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on SDCCH. The measurement point is A, as shown in Figure 1610.
FIGURE 1610 CALL DROP DUE TO RADIO LINK FAILURE IMMEDIATE ASSIGNMENT PROCESS
DURING
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH. The measurement point is A, as shown in Figure 1611.
1591
DUE TO
DURING
Unit
Times
Number of drops due to the low electric level of UL 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. 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
Usage
1592
receiving level. It is one of the radio parameters that evaluate the timeslot.
Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on SDCCH. The measurement point is A, as shown in Figure 1612.
FIGURE 1612 CALL DROP DUE TO RADIO LINK FAILURE IMMEDIATE ASSIGNMENT PROCESS
DURING
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH. The measurement point is A, as shown in Figure 1613.
1593
DUE TO
DURING
Unit
Times
Number of drops due to the low electric level of DL 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. 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
Usage
1594
receiving level. It is one of the radio parameters that evaluate the timeslot.
Measurement Point
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on SDCCH. The measurement point is A, as shown in Figure 1614.
FIGURE 1614 CALL DROP DUE TO RADIO LINK FAILURE IMMEDIATE ASSIGNMENT PROCESS
DURING
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH. The measurement point is A, as shown in Figure 1615.
1595
DUE TO
DURING
Unit
Times
Number of drops due to the TA too far 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. 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.
Usage
1596
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 1616.
FIGURE 1616 CALL DROP DUE TO RADIO LINK FAILURE IMMEDIATE ASSIGNMENT PROCESS
DURING
The counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH. The measurement point is A, as shown in Figure 1617.
1597
DUE TO
DURING
Unit
Times
Number of drops due to the other radio reasons 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.
1598
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. 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 1618.
FIGURE 1618 CALL DROP DUE TO RADIO LINK FAILURE IMMEDIATE ASSIGNMENT PROCESS
DURING
Measurement Point
counter counts when BSC receives the CONNectiOn FAILure INDicatiOn message at Abis interface on TCH. The measurement point is A, as shown in Figure 1619.
1599
DUE TO
DURING
Unit
Times
The valid time of the used voice channel This counter counts the valid occupation time of a timeslot's voice channel in the cell. 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. When BSC receives the measurement report from BTS, the counter is accumulated with a time value. Different measurement report type corresponds to different value, for common measurement re-
Measurement Point
1600
port, the time value is 480 ms. The measurement point is A, as shown in Figure 1620.
FIGURE 1620 BSC RECEIVES MEASUREMENT REPORT
FROM
BTS
Unit
ms
Number of activated voice channel This counter counts the number of a timeslot's voice channel being activated in the cell. 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. When BSC receives the CHANNEL ACTIVATE ACK message, the counter increments. The measurement point is A, as shown in Figure 1621.
FIGURE 1621 MEASUREMENT POINT
WHEN
Measurement Point
CHANNEL IS ACTIVATED
Unit
Times
1601
1602
Chapter
31
SDCCH Measurement
Table of Contents Overview...................................................................... 1604 C901250005 Number of SDCCH seizure success for Handover........................................................................... 1605 C901250007 Number of SDCCH allocation attempts for Assignment...................................................................... 1607 C901250010 Number of SDCCH allocation attempts for handover........................................................................... 1608 C901250011 Number of SDCCH allocation success for handover........................................................................... 1610 C901250012 Number of SDCCH allocation failure for handover........................................................................... 1611 C901250016 Number of SDCCH handover failure ............... 1612 C901250017 Number of SDCCH handover success ............. 1614 C901250018 Number of SDCCH handover failure with Reconnection ........................................................................ 1616 C901250019 Number of SDCCH handover failure without Reconnection.................................................................... 1616 C901250020 Number of SDCCH assignment attempts (MOC).......................................................................... 1617 C901250021 Number of successful SDCCH assignments (MOC).......................................................................... 1618 C901250022 Number of unsuccessful SDCCH assignments (MOC).......................................................................... 1619 C901250023 Number of SDCCH assignment attempts (MTC) .......................................................................... 1620 C901250024 Number of successful SDCCH assignments (MTC) .......................................................................... 1621 C901250025 Number of unsuccessful SDCCH assignments (MTC) .......................................................................... 1622 C901250026 Number of SDCCH assignment attempts (call re-establishment) .......................................................... 1623 C901250027 Number of successful SDCCH assignments (call re-establishment) .......................................................... 1624 C901250028 Number of unsuccessful SDCCH assignments (call re-establishment) ................................................... 1625 C901250029 Number of SDCCH assignment attempts (emergency call).................................................................... 1626 C901250030 Number of successful SDCCH assignments (emergency call) ........................................................... 1627 C901250031 Number of unsuccessful SDCCH assignments (emergency call) ........................................................... 1628 C901250032 Number of SDCCH assignment attempts (LOC) .......................................................................... 1629 C901250033 Number of successful SDCCH assignments (LOC) .......................................................................... 1630
1603
C901250034 Number of unsuccessful SDCCH assignments (LOC) .......................................................................... 1631 C901250035 Number of SDCCH assignment attempts (other cause) ......................................................................... 1632 C901250036 Number of successful SDCCH assignments (other cause) ................................................................ 1633 C901250037 Number of unsuccessful SDCCH assignments (other cause) ................................................................ 1634 C901250038 Count of USSD attempts to connect............... 1635 C901250039 Average dialoge time of USSD services .......... 1636 C901250040 Dialog counts of USSD services..................... 1636
Overview
SDCCH counters describe allocation, occupation, assignment, use of resources related to SDCCH, which as SDCCH configuration and parameters adjustment basis. Allocation of SDCCH is mainly in the process of immediate assignment and handover. Handover includes internal and external handover. The statistic unit in this measurement is cell. The Measurement point Of SDCCH counters in the process of immediate assignment is shown in Figure 1622.
FIGURE 1622 THE PROCESS OF IMMEDIATE ASSIGNMENT
The Measurement point Of SDCCH counters in the process of internal handover (like intra-cell handover) is shown in Figure 1623.
1604
INTRA-CELL
The Measurement point Of SDCCH counters in the process of external handover is shown in Figure 1624.
FIGURE 1624 THE PROCESS OF EXTERNAL HANDOVER
1605
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. This counter records the number of SDCCH seizure success for handover. When BSC requesting for SDCCH (due to handover) is completed and SDCCH seizure succeeds, or BSC gets valid response of waiting resource. The measurement point is B1 as shown in Figure 1625, and C1 as shown in Figure 1626.
FIGURE 1625 HANDOVER) THE PROCESS OF INTERNAL HANDOVER (LIKE
INTRA-CELL
1606
Number of SDCCH allocations attempts for assignment This counter records the number of SDCCH allocations attempts for assignment, including successful allocations (C900060008) and unsuccessful allocations (C900060009). 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. BSC activates SDCCH due to assignment (C900060008+C900060 009). The measurement point is A2 as shown in Figure 1627.
Usage
Measurement Point
1607
Number of SDCCH allocation attempts for handover 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. This counter records the number of SDCCH allocations attempts for handover, including successful allocations (C901250011) and unsuccessful allocations (C901250012). BSC activates SDCCH due to handover (C901250011+C90125001 2). The measurement point is B2 as shown in Figure 1628and C2 as shown in Figure 1629.
Usage
Measurement Point
1608
INTRA-CELL
1609
Number of SDCCH allocation success for handover 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. This counter records the number of SDCCH allocations success for handover. When BSC receives the CHL_ACT_ACK message from BTS due to handover. The measurement point is B2 as shown in Figure 1630, and C2 as shown in Figure 1631.
FIGURE 1630 HANDOVER) THE PROCESS OF INTERNAL HANDOVER (LIKE
INTRA-CELL
1610
Number of SDCCH allocation failure for handover 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. This counter records the number of SDCCH allocations failure for handover. BSC activates SDCCH for handover, but encounters the following situation: receives channel activation failed message, channel activation response message is incorrect, T9103 is time-out, channel instance is released, or channel is released forcibly. The measurement point is B2 as shown in Figure 1632 and C2 as shown in Figure 1633.
1611
INTRA-CELL
1612
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. When BSC receives ASS_COM message (intra-cell handover), HO_COM message (inter-cell handover), HO_FAILURE message or HO_FAILURE abnormally, time-out message, channel instance is released, or channel is released forcibly. The measurement point is B3 as shown in Figure 1634and C3 as shown in Figure 1635.
FIGURE 1634 HANDOVER) THE PROCESS OF INTERNAL HANDOVER (LIKE
INTRA-CELL
Measurement Point
1613
Number of SDCCH handover success 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. This counter records the number of MS accesses successfully SDCCH newly allocated in the process of handover. BSC receives ASS_COM message (intra-cell handover) or HO_COM message (inter-cell handover). The measurement point is B3 as shown in Figure 1636and C3 as shown in Figure 1637.
1614
INTRA-CELL
1615
Number of SDCCH handover failure with Reconnection In the process of handover, when BSC receives ASSIGN_FAIL message or HO_FAIL message, this counter increments. This counter records the number of MS accesses unsuccessfully SDCCH newly allocated in the process of handover and BSC receives handover failure message. BSC receives HO_FAILURE message. Times ZGB-03-02-003 Dynamic Configuration of SDCCH ZGO-02-02-004 SDCCH/SDCCH Handover
Number of SDCCH handover failure without Reconnection If handover fails and at same time BSC has not received any HO_FAILURE message, this counter increments. 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. When BSC has not received any HO_FAILURE message, time-out message, channel instance is released, or channel is released forcibly. Times ZGB-03-02-003 Dynamic Configuration of SDCCH ZGO-02-02-004 SDCCH/SDCCH Handover
1616
After BSC responds to the channel request due to MOC and successfully allocates and activates SDCCH, BSC sends the immediate assignment message IMM_ASS to MS to notify it to use the channel. After MS receives the message, it sends the SABM frame to BTS via SDCCH. After BTS receives the frame, it sends the EST_IND message to BSC. If BSC receives the EST_IND message correctly within specified time, it indicates that SDCCH assignment succeeds, this counter and C901250021 accumulate simultaneously. Otherwise, if BSC receives the EST_IND message incorrectly or T3101 is timeout, it indicates that SDCCH assignment fails, this counter and 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. 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 1638.
FIGURE 1638 IMMEDIATE ASSIGNMENT FLOW
Measurement Point
Unit
Times
1617
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 1639. This counter is supported in version V6.20.61 or later.
FIGURE 1639 NUMBER
OF SUCCESSFUL
SDCCH
ASSIGNMENTS
(MOC)
The counter counts when BSC correctly receives the EST_IND message or the assignment completion message. Times
1618
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. The counter counts when BSC receives the EST_IND message incorrectly or T3101 is timeout. The measurement point is A3, as shown in Figure 1640.
FIGURE 1640 NUMBER
OF UNSUCCESSFUL
Measurement Point
SDCCH
ASSIGNMENTS
(MOC)
Unit
Times
1619
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. 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 1641.
FIGURE 1641 NUMBER
OF
Measurement Point
SDCCH
ASSIGNMENT ATTEMPTS
(MTC)
Unit
Times
1620
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 1642.
FIGURE 1642 NUMBER
OF SUCCESSFUL
SDCCH
ASSIGNMENTS
(MTC)
The counter counts when BSC correctly receives the EST_IND message or the assignment completion message. Times
1621
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. This counter is supported in version V6.20.61 or later. The counter counts when BSC receives the EST_IND message incorrectly or T3101 is timeout. The measurement point is A3, as shown in Figure 1643.
FIGURE 1643 NUMBER
OF UNSUCCESSFUL
Measurement Point
SDCCH
ASSIGNMENTS
(MTC)
Unit
Times
1622
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.
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. 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 1644.
FIGURE 1644 NUMBER OF RE-ESTABLISHMENT) SDCCH
ASSIGNMENT ATTEMPTS
Measurement Point
(CALL
1623
Unit
Times
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, 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 1645.
FIGURE 1645 NUMBER OF SUCCESSFUL RE-ESTABLISHMENT) SDCCH
ASSIGNMENTS
(CALL
1624
The counter counts when BSC correctly receives the EST_IND message or the assignment completion message. Times
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. The counter counts when BSC receives the EST_IND message incorrectly or T3101 is timeout. The measurement point is A3, as shown in Figure 1646.
Measurement Point
1625
SDCCH
ASSIGNMENTS
(CALL
Unit
Times
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.
1626
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 1647.
FIGURE CALL) 1647 NUMBER
OF
SDCCH
ASSIGNMENT ATTEMPTS
(EMERGENCY
Unit
Times
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 cor-
1627
responding SDCCH after BSC sends the IMM_ASS message. The measurement point is A3, as shown in Figure 1648.
FIGURE 1648 NUMBER CALL)
OF SUCCESSFUL
SDCCH
ASSIGNMENTS
(EMERGENCY
The counter counts when BSC correctly receives the EST_IND message or the assignment completion message. Times
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.
1628
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. The counter counts when BSC receives the EST_IND message incorrectly or T3101 is timeout. The measurement point is A3, as shown in Figure 1649.
FIGURE 1649 NUMBER (EMERGENCY CALL)
OF UNSUCCESSFUL
Measurement Point
SDCCH
ASSIGNMENTS
Unit
Times
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. Otherwise, if BSC receives the EST_IND message incorrectly or T3101 is time-
1629
out, 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. 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 1650.
FIGURE 1650 NUMBER
OF
Measurement Point
SDCCH
ASSIGNMENT ATTEMPTS
(LOC)
Unit
Times
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.
1630
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 1651.
FIGURE 1651 NUMBER
OF SUCCESSFUL
SDCCH
ASSIGNMENTS
(LOC)
The counter counts when BSC correctly receives the EST_IND message or the assignment completion message. Times
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.
1631
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. The counter counts when BSC receives the EST_IND message incorrectly or T3101 is timeout. The measurement point is A3, as shown in Figure 1652.
FIGURE 1652 NUMBER
OF UNSUCCESSFUL
Measurement Point
SDCCH
ASSIGNMENTS
(LOC)
Unit
Times
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.
1632
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. 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 1653.
FIGURE 1653 NUMBER
OF
Measurement Point
SDCCH
ASSIGNMENT ATTEMPTS
(OTHER
CAUSE)
Unit
Times
After BSC responds to the channel request due to causes beyond what have been mentioned previously and successfully allocates
1633
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 1654.
FIGURE CAUSE) 1654 NUMBER
OF SUCCESSFUL
SDCCH
ASSIGNMENTS
(OTHER
The counter counts when BSC correctly receives the EST_IND message or the assignment completion message. Times
After BSC responds to the channel request due to causes beyond what have been mentioned previously and successfully allocates
1634
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 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. The counter counts when BSC receives the EST_IND message incorrectly or T3101 is timeout. The measurement point is A3, as shown in Figure 1655.
FIGURE 1655 NUMBER CAUSE)
OF UNSUCCESSFUL
Measurement Point
SDCCH
ASSIGNMENTS
(OTHER
Unit
Times
This counter counts the number of attempts of connecting USSD service. This counter is supported in version V6.20.614c.
1635
Times Cell
This counter counts the average conversation time of USSD service. This counter is supported in version V6.20.614c. Second Cell
This counter counts the number of conversations of USSD service. This counter is supported in version V6.20.614c.
Times Cell
1636
Chapter
32
TCH/F Measurement
Table of Contents Overview...................................................................... 1641 C901260002 Number of signaling TCH/F seizure success for assignment................................................................... 1644 C901260005 Number of signaling TCH/F seizure success for handover...................................................................... 1645 C901260007 Number of signaling TCH/F allocation attempts for assignment .............................................................. 1647 C901260010 Number of signaling TCH/F allocation attempts for handover ................................................................. 1648 C901260011 Number of signaling TCH/F allocation success for handover...................................................................... 1651 C901260013 Number of signaling TCH/F assignment attempts for assignment .............................................................. 1653 C901260016 Number of signaling TCH/F handover attempt .......................................................................... 1654 C901260017 Number of signaling TCH/F handover success............................................................................. 1657 C901260018 Number of signaling TCH/F handover failure with reconnection ................................................................. 1659 C901260019 Number of signaling TCH/F handover failure without reconnection...................................................... 1661 C901260021 Number of voice TCH/F seizure success for assignment...................................................................... 1662 C901260024 Number of voice TCH/F seizure success for handover........................................................................... 1663 C901260026 Number of TCH/F allocation attempts for assignment (speech version 1)................................................. 1666 C901260032 Number of TCH/F allocation attempts by BSC for handover (speech version 1) ........................................... 1667 C901260033 Number of TCH/F allocation success by BSC for handover (speech version 1) ........................................... 1670 C901260038 Number of TCH/F allocation attempts for assignment (speech version 2)................................................. 1672 C901260044 Number of TCH/F allocation attempts by BSC for handover (speech version 2) ........................................... 1674 C901260045 Number of TCH/F allocation success by BSC for handover (speech version 2) ........................................... 1676 C901260050 Number of TCH/F allocation attempts by BSC for assignment (speech version 3) ........................................ 1679 C901260056 Number of TCH/F allocation attempts by BSC for handover (speech version 3) ........................................... 1680 C901260057 Number of TCH/F allocation success by BSC for handover (speech version 3) ........................................... 1683 C901260062 Number of voice TCH/F assignment attempts by BSC ............................................................................. 1685
1637
C901260065 Number of voice TCH/F handover attempts ......................................................................... 1686 C901260067 Number of Voice TCH/F handover failure......... 1689 C901260068 Number of Voice TCH/F handover failure messages do not received by BSC ......................................... 1691 C901260070 Number of data TCH/F seizure success for assignment...................................................................... 1692 C901260073 Number of data TCH/F seizure success for handover........................................................................... 1693 C901260075 Number of data TCH/F allocation attempts for assignment................................................................... 1696 C901260081 Number of data TCH/F allocation attempts by BSC for handover .......................................................... 1697 C901260082 Number of data TCH/F allocation success for handover...................................................................... 1700 C901260087 Number of data TCH/F assignment attempts ......................................................................... 1702 C901260090 Number of data TCH/F handover attempts ......................................................................... 1703 C901260092 Number of data TCH/F handover failure ......... 1706 C901260093 Number of data TCH/F handover failure messages do not received by BSC ......................................... 1708 C901260094 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 1)................................................................................ 1709 C901260095 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 1) ......................................................................... 1710 C901260096 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 1)................................................................................ 1711 C901260097 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 1)................................................................................ 1712 C901260098 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 2)................................................................................ 1713 C901260099 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 2) ......................................................................... 1714 C901260100 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 2)................................................................................ 1715 C901260101 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 2)................................................................................ 1717 C901260102 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 3)................................................................................ 1718 C901260103 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 3) ......................................................................... 1719 C901260104 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 3)................................................................................ 1720 C901260105 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 3)................................................................................ 1722
1638
C901260106 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 1)................................................................................ 1723 C901260107 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 1)................................................................................ 1724 C901260108 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 1).......... 1725 C901260109 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 1)................................................................................ 1726 C901260110 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 1)......... 1727 C901260111 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 1)............. 1728 C901260112 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 2)................................................................................ 1729 C901260113 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 2)................................................................................ 1730 C901260114 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 2).......... 1731 C901260115 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 2)................................................................................ 1732 C901260116 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 2)......... 1733 C901260117 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 2)............. 1734 C901260118 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 3)................................................................................ 1735 C901260119 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 3)................................................................................ 1736 C901260120 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 3).......... 1737 C901260121 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 3)................................................................................ 1738 C901260122 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 3)......... 1739 C901260123 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 3)............. 1740 C901260124 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (data).............. 1741 C901260125 Number of TCH/F allocation failure due to request UDP port failure for assignment (data)..................... 1742 C901260126 Number of TCH/F allocation failure due to AIPB connection failure for assignment (data) ........................... 1742 C901260127 Number of TCH/F allocation failure due to request AIPB resource failure for handover (data)................. 1743 C901260128 Number of TCH/F allocation failure due to request UDP port failure for handover (data)........................ 1744 C901260129 Number of TCH/F allocation failure due to AIPB connection failure for handover (data).............................. 1745 C901260130 Number of assign TCH/F release by forced handover to forced handover source...................................... 1746
1639
C901260131 Number of assign TCH/F release by forced handover to queuing user .................................................... 1746 C901260132 Number of restore TCH/F release by forced handover to DBS ................................................................ 1747 C901260133 Number of assign TCHF release by forced release to forced release source ................................................. 1747 C901260134 Number of assign TCH/F release by forced release to queuing user..................................................... 1748 C901260135 Number of restore TCH/F release by forced release to DBS ................................................................. 1748 C901260136 Number of signaling TCH/F seizure failure for assignment (cause:Abis) ................................................ 1749 C901260137 Number of signaling TCH/F seizure failure for handover (cause:Abis) ................................................... 1750 C901260138 Number of voice TCH/F seizure failure for assignment (cause:Abis) ................................................... 1750 C901260139 Number of voice TCH/F seizure failure for handover (cause:Abis ) ....................................................... 1751 C901260140 Number of data TCH/F seizure failure for assignment (cause:Abis) ......................................................... 1751 C901260141 Number of data TCH/F seizure failure for handover (cause:Abis) ........................................................ 1752 C901260142 Number of signaling TCH/F seizure failure for assignment (cause:radio resource) .................................. 1752 C901260143 Number of signaling TCH/F seizure failure for handover (cause:radio resource) ..................................... 1753 C901260144 Number of voice TCH/F seizure failure for assignment (cause:radio resource) ..................................... 1753 C901260145 Number of voice TCH/F seizure failure for handover (cause:radio resource) .......................................... 1754 C901260146 Number of data TCH/F seizure failure for assignment (cause:radio resource) ........................................... 1754 C901260147 Number of data TCH/F seizure failure for handover (cause:radio resource) .......................................... 1755 C901260148 Number of FR_V1 assignment attempts ......... 1755 C901260149 Number of FR_V1 assignment success ........... 1756 C901260150 Number of FR_V2 assignment attempts ......... 1756 C901260151 Number of FR_V2 assignment success ........... 1756 C901260152 Number of FR_V3 assignment attempts ......... 1757 C901260153 Number of FR_V3 assignment success ........... 1757 C901260154 Number of FR_V1 handover.......................... 1758 C901260155 Number of FR_V1 handover success .............. 1758 C901260156 Number of FR_V2 handover.......................... 1759 C901260157 Number of FR_V2 handover success .............. 1759 C901260158 Number of FR_V3 handover.......................... 1760 C901260159 Number of FR_V3 handover success .............. 1760 C901260185 Resourse releasing of ordinary users due to being grabbed (TCH/F) ...................................................... 1761 C901260186 Handover of ordinary users due to be grabbed (TCH/F)........................................................................ 1762 C901260187 Number of Channel Request of priority users (TCH/F)........................................................................ 1763 C901260188 Number of Successful Channel seize of priority users (TCH/F) ............................................................... 1765 C901260189 Number of Successful grabbing channel of priority users (TCH/F) ........................................................ 1766
1640
Overview
In GSM BSC signaling system, allocation and usage of TCH/F channel mainly exist in assignment and handover flow, where assignment flow includes immediate assignment and common assignment; handover flow includes internal and external handover. For the measurement positions of TCH/F counter in immediate assignment flow, see Figure 1656.
FIGURE 1656 IMMEDIATE
ASSIGNMENT FLOW
During internal and external TC, for the measurement positions of TCH/F counter in common assignment flow, see Figure 1657and Figure 1658.
FIGURE 1657 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1641
ASSIGNMENT FLOW
(EXTERNAL TC)
During internal and external TC, for the measurement positions of TCH/F counter in internal handover flow (like intra-cell handover), see Figure 1659and Figure 1660.
FIGURE 1659 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1642
FIGURE 1660 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
During internal and external TC, for the measurement positions of TCH/F counter in external handover flow, see Figure 1661and Figure 1662
FIGURE 1661 EXTERNAL
HANDOVER FLOW
(INTERNAL TC)
1643
HANDOVER FLOW
(EXTERNAL TC)
Number of signaling TCH/F seizure success for assignment This counter counts the number of signaling TCH/F seizure success during assignment of signaling channel. After BSC receives channel request message, it will try to allocate channel for this request. If allocation and seizure succeed, this 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 1663
FIGURE 1663 IMMEDIATE
ASSIGNMENT FLOW
1644
Number of signaling TCH/F seizure success for handover This counter counts the number of signaling TCH/F seizure success during handover of signaling channel. 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 signaling channel) and does successful seizure, or BSC receives internal waiting resource effective message. The measurement points are C1 and D1, as shown in Figure 1664, Figure 1665, Figure 1666, and Figure 1667.
FIGURE 1664 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1645
FIGURE 1665 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1646
HANDOVER FLOW
(EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking
Number of signaling TCH/F allocation attempts for assignment This counter counts the number of signaling TCH/F allocation attempts when assigning signaling channel, including the number of allocation success (C900060014) and failure (C900060014). After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC sends channel activation message CHL_ACT to activate this TCH/F. if activation success, CHL_ACT_ACK message sent by BTS will be received, indicating TCH/F allocation success, this counter and C900060014 accumulate simultaneously; reversely, if channel activation failure due to receive channel activation failure message, incorrect channel activation response message, timer T9103 timeout, channel instance released, channel force-released, this counter and C900060015 accumulate simultaneously.
Measurement Point
After BSC activates TCH/F (due to assignment, used for signaling channel), this counter accumulates when CHL_ACT_ACK message sent by BTS is received correctly, channel activation failure message is received, channel activation response message is not correct, timer T9103 times out, channel instance is released, or channel is forcibly released. (C900060014+C900060015) The measurement point is A2, as shown in Figure 1668.
1647
ASSIGNMENT FLOW
Number of signaling TCH/F allocation attempts for handover This counter counts the number of signaling TCH/F allocation attempts during handover of signaling channel, including the number of allocation success (C901260011) and failure (C900060016). After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation success, 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 1669, Figure 1670,Figure 1671 and Figure 1672.
1648
HANDOVER
(LIKE
FIGURE 1670 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1649
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking
1650
Number of signaling TCH/F allocation success for handover This counter counts the number of signaling TCH/F allocation success during handover of signaling channel. After BSC responds channel request message allocation and successfully seizes channel, BSC sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation success, 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 1673, Figure 1674, Figure 1675, and Figure 1676.
FIGURE 1673 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1651
FIGURE 1674 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1652
HANDOVER FLOW
(EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking
Number of signaling TCH/F assignment attempts for assignment This counter counts the number of signaling TCH/F assignment success during assignment of TCH/F channel. 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.
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 1677.
1653
ASSIGNMENT FLOW
Number of signaling TCH/F handover attempt This counter counts the number of signaling TCH/F handover attempts, including the number of TCH/F handover success (C901260017), the number of TCH/F handover failure with return (C901260018), and the number of TCH/F handover failure without return (C901260019). This counter and C901260017 accumulate when BSC detects the handover success message sent by MS on reallocated TCH/F channel; this counter and C901260018 accumulate when handover failure message is received; this counter and C901260019 accumulate when it receives the message of exception, released instance, force-released instance, or timer timeout. For intra-cell handover, handover success symbolic message is ASS_COM; for inter-cell handover and external handover, handover success symbolic message is HO_COM. For intra-cell and inter-cell handover, this counter accumulates on the basis of source instance; for external handover, this counter accumulates on target instance because source instance doesnt at this BSC side.
Measurement Point
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 1678, Figure 1679, Figure 1680, and Figure 1681.
1654
HANDOVER
(LIKE
FIGURE 1679 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1655
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking
1656
Number of signaling TCH/F handover success his counter counts the number of signaling TCH/F handover success during handover of signaling channel. This counter accumulates when handover success message sent from MS is detected on reallocated TCH/F channel. For intra-cell handover, handover success symbolic message is ASS_COM; for inter-cell handover and external handover, handover success symbolic message is HO_COM. For intra-cell and inter-cell handover, this counter accumulates on the basis of source instance; for external handover, this counter accumulates on target instance because source instance doesnt at this BSC side.
Measurement Point
BSC receives ASS_COM or HO_COM message. The measurement points are C4 and D4, as shown in Figure 1682, Figure 1683, Figure 1684, and Figure 1685.
FIGURE 1682 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1657
FIGURE 1683 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1658
HANDOVER FLOW
(EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking
Number of signaling TCH/F handover failure with reconnection This counter counts the number of signaling TCH/F handover failure during handover of signaling channel. This counter accumulates when MS conducts handover on TCH/F channel, returns to previous channel after failed to access to new channel, receives assignment failure or handover failure from previous channel.
Measurement Point
BSC receives ASS_FAIL or HO_FAIL message. The measurement points are C4 and D4, as shown in Figure 1686, Figure 1687.
1659
HANDOVER
(INTERNAL TC
INTRA-CELL HANDOVER)
(INTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking
1660
Number of signaling TCH/F handover failure without reconnection 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 1688, Figure 1689.
FIGURE 1688 INTERNAL HANDOVER FAILURE FLOW 2 (INTERNAL TC
INTRA-CELL HANDOVER)
(INTERNAL TC
INTRA-CELL HANDOVER)
1661
Number of voice TCH/F seizure success for assignment This counter counts the number of voice TCH/F seizure success during assignment of signaling channel. 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 1690, Figure 1691.
FIGURE 1690 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1662
ASSIGNMENT FLOW
(EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface
Number of voice TCH/F seizure success for handover 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 1692, Figure 1693, Figure 1694, and Figure 1695.
1663
HANDOVER
(LIKE
FIGURE 1693 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1664
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1665
Number of TCH/F allocation attempts for assignment (speech version 1) This counter counts the number of TCH/F allocation attempts when assigning voice channel (for speech version 1), including the number of allocation success (C900060023) and failure (C900060024+C900060138+ C900060139+ C900060140). After BSC responds channel request message allocation and successfully seizes TCH/F channel, BSC firstly finishes connection, then sends channel activation message CHL_ACT to BTS to activate this TCH/F. if activation succeeds, BSC will receive CHL_ACT_ACK message sent by BTS, indicating TCH/F allocation success, this counter and C900060023 accumulate simultaneously; reversely, if failed, this counter and the counter that corresponds to failure will accumulate simultaneously.
Measurement Point
This counter accumulates when allocation succeeds or fails (due to assignment, used for voice channel, using speech version 1). The measurement points are B2 and B3, as shown in Figure 1696, Figure 1697.
FIGURE 1696 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1666
ASSIGNMENT FLOW
(EXTERNAL TC)
Times 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
C901260032 Number of TCH/F allocation attempts by BSC for handover (speech version 1)
Definition Description
Number of TCH/F allocation attempts by BSC for handover (speech version 1) 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.
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 1698, Figure 1699, Figure 1700, and Figure 1701.
1667
HANDOVER
(LIKE
FIGURE 1699 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1668
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1669
C901260033 Number of TCH/F allocation success by BSC for handover (speech version 1)
Definition Description
Number of TCH/F allocation success by BSC for handover(speech version 1) 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 1702, Figure 1703, Figure 1704, and Figure 1705.
FIGURE 1702 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1670
FIGURE 1703 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1671
HANDOVER FLOW
(EXTERNAL TC)
Times 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
Number of TCH/F allocation attempts for assignment (speech version 2) 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.
Measurement Point
This counter accumulates when allocation succeeds or fails (due to assignment, used for voice channel, using speech version 2).
1672
The measurement points are B2 and B3, as shown in Figure 1706, Figure 1707.
FIGURE 1706 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
ASSIGNMENT FLOW
(EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface
1673
C901260044 Number of TCH/F allocation attempts by BSC for handover (speech version 2)
Definition Description
Number of TCH/F allocation attempts by BSC for handover (speech version 2) 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 1708, Figure 1709, Figure 1710, and Figure 1711.
FIGURE 1708 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1674
FIGURE 1709 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1675
HANDOVER FLOW
(EXTERNAL TC)
Times 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
C901260045 Number of TCH/F allocation success by BSC for handover (speech version 2)
Definition Description
Number of TCH/F allocation success by BSC for handover (speech version 2) 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 points are C3 and D3, as shown in Figure 1712, Figure 1713, Figure 1714, and Figure 1715.
1676
HANDOVER
(LIKE
FIGURE 1713 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1677
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1678
C901260050 Number of TCH/F allocation attempts by BSC for assignment (speech version 3)
Definition Description
Number of TCH/F allocation attempts for assignment (speech version 3) 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 1716, Figure 1717.
FIGURE 1716 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1679
ASSIGNMENT FLOW
(EXTERNAL TC)
Times 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
C901260056 Number of TCH/F allocation attempts by BSC for handover (speech version 3)
Definition Description
Number of TCH/F allocation attempts by BSC for handover (speech version 3) 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.
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 1718, Figure 1719, Figure 1720, and Figure 1721.
1680
HANDOVER
(LIKE
FIGURE 1719 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1681
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1682
C901260057 Number of TCH/F allocation success by BSC for handover (speech version 3)
Definition Description
Number of TCH/F allocation success by BSC for handover (speech version 3) 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 1722, Figure 1723, Figure 1724, and Figure 1725.
FIGURE 1722 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1683
FIGURE 1723 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1684
HANDOVER FLOW
(EXTERNAL TC)
Times 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
Number of voice TCH/F assignment attempts by BSC This counter counts the number of voice TCH/F assignment attempts when assigning TCH/F channel as voice channel, including the number of assignment success (C900060028) and failure (C900060029). 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.
Measurement Point
For the assignment from port A, BSC receives the messages of assignment success, assignment failure, timer timeout, exception, released instance, or force-released instance. The measurement point is B5, as shown in Figure 1726, Figure 1727.
1685
ASSIGNMENT FLOW
(INTERNAL TC)
ASSIGNMENT FLOW
(EXTERNAL TC)
Number of voice TCH/F handover attempts This counter counts the number of voice TCH/F handover attempts, including the number of TCH/F handover success (C900060168), the number of TCH/F handover failure with return
1686
(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 1728, Figure 1729, Figure 1730, and Figure 1731.
FIGURE 1728 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1687
FIGURE 1729 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1688
HANDOVER FLOW
(EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking
Number of Voice TCH/F handover failure 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 1732, Figure 1733.
1689
HANDOVER
(INTERNAL TC
INTRA-CELL HANDOVER)
(INTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking
1690
C901260068 Number of Voice TCH/F handover failure messages do not received by BSC
Definition Description
Number of Voice TCH/F handover failure messages do not received by BSC This counter counts the number of voice TCH/F handover failure without response during handover of voice channel. This counter accumulates when handover fails or it cant return to source channel after BSC sends assignment / handover command to MS.
Measurement Point
This counter accumulates when BSC receives messages of exception, timer timeout, released instance, or force-released instance. The measurement points are C4 and D4, as shown in Figure 1734, Figure 1735.
FIGURE 1734 INTERNAL HANDOVER FAILURE FLOW 2 (INTERNAL TC
INTRA-CELL HANDOVER)
(INTERNAL TC
INTRA-CELL HANDOVER)
1691
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking
Number of data TCH/F seizure success for assignment This counter counts the number of data TCH/F seizure success during assignment of signaling channel. 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 1736, Figure 1737.
FIGURE 1736 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1692
ASSIGNMENT FLOW
(EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface
Number of data TCH/F seizure success for handover This counter counts the number of data TCH/F seizure success during handover of signaling channel. 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 1738, Figure 1739, Figure 1740, and Figure 1741.
1693
HANDOVER
(LIKE
FIGURE 1739 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1694
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1695
Number of data TCH/F allocation attempts for assignment 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). 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. 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 1742, Figure 1743.
FIGURE 1742 COMMON
ASSIGNMENT FLOW
Usage
Measurement Point
(INTERNAL TC)
1696
ASSIGNMENT FLOW
(EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface
Number of data TCH/F allocation attempts by BSC for handover This counter counts the number of data TCH/F allocation attempts during handover of data channel, including the number of allocation success (C901260082) and failure (C900060169+C900060170+C900060171+C900060172). 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 1744, Figure 1745, Figure 1746, and Figure 1747.
1697
HANDOVER
(LIKE
FIGURE 1745 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1698
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1699
Number of data TCH/F allocation success for handover 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 points are C3 and D3, as shown in Figure 1748, Figure 1749, Figure 1750, and Figure 1751.
FIGURE 1748 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1700
FIGURE 1749 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1701
HANDOVER FLOW
(EXTERNAL TC)
Times 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
Number of data TCH/F assignment attempts This counter counts the number of voice TCH/F assignment attempts when assigning TCH/F channel as data channel, including the number of assignment success (C900060036) and failure (C900060037). 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 1752, Figure 1753.
1702
ASSIGNMENT FLOW
(INTERNAL TC)
ASSIGNMENT FLOW
(EXTERNAL TC)
Number of data TCH/F handover attempts This counter counts the number of data TCH/F handover attempts, including the number of TCH/F handover success (C901260091), TCH/F response handover failure (C901260092), and TCH/F response-less handover failure (C901260093).
1703
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.
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 1754, Figure 1755, Figure 1756, and Figure 1757.
FIGURE 1754 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1704
FIGURE 1755 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1705
HANDOVER FLOW
(EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking
Number of data TCH/F handover failure 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 1758, Figure 1759.
1706
(INTERNAL TC
INTRA-CELL HANDOVER)
(INTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking
1707
C901260093 Number of data TCH/F handover failure messages do not received by BSC
Definition Description
Number of data TCH/F handover failure messages do not received by BSC 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 1760and Figure 1761.
FIGURE 1760 INTERNAL FAILURE FLOW 2
HANDOVER
(INTERNAL TC
INTRA-CELL HANDOVER)
HANDOVER
(INTERNAL TC
INTRA-CELL HANDOVER)
1708
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-011 Channel Repacking
C901260094 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 1)
Definition Description
Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 1) 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 1762.
FIGURE 1762 GENERAL ASSIGNMENT FAILURE FLOW 1 (EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface
1709
C901260095 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 1)
Definition Description
Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 1) 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 1763.
FIGURE 1763 GENERAL ASSIGNMENT FAILURE FLOW 2 (EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface
1710
C901260096 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 1)
Definition Description
Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 1) 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 1764and Figure 1765.
FIGURE 1764 INTERNAL
HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 1
1711
HANDOVER FLOW
(EXTERNAL TC)
Times 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
C901260097 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 1)
Definition Description
Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 1) 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 1766and Figure 1767.
1712
HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 2
2 (EXTERNAL TC)
Times 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
C901260098 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 2)
Definition Description
Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 2) 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.
1713
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 1768.
FIGURE 1768 GENERAL ASSIGNMENT FAILURE FLOW 1 (EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface
C901260099 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 2)
Definition Description
Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 2) 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.
1714
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 1769.
FIGURE 1769 GENERAL ASSIGNMENT FAILURE FLOW 2 (EXTERNAL TC)
Times ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface
C901260100 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 2)
Definition Description
Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 2) 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 1770and Figure 1771.
1715
HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 1
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1716
C901260101 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 2)
Definition Description
Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 2) 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 1772and Figure 1773.
FIGURE 1772 INTERNAL
HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 2
1717
2 (EXTERNAL TC)
Times 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
C901260102 Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 3)
Definition Description
Number of data TCH/F allocation failure for assignment due to TIPB connection failure (Speech version 3) 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 1774.
1718
Times 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
C901260103 Number of data TCH/F allocation failure for assignment due to Resource request to iTC failure (Speech version 3)
Definition Description
Number of data TCH/F allocation failure for assignment due to resource request to iTC failure (Speech version 3) 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 1775.
1719
Times 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
C901260104 Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 3)
Definition Description
Number of data TCH/F allocation failure for handover due to TIPB connection failure (Speech version 3) 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 1776and Figure 1777.
1720
HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 1
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1721
C901260105 Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 3)
Definition Description
Number of data TCH/F allocation failure for handover due to Resource request to iTC failure (Speech version 3) 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 1778and Figure 1779.
FIGURE 1778 INTERNAL
HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 2
1722
2 (EXTERNAL TC)
Times 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
C901260106 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 1)
Definition Description
Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 1) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request AIPB resource failure for assignment. This counter increments while BSC correctly receives database return failure or no AIPB board resource, and the reason to apply for channel is assignment and purpose is voice channel. The measurement point is A as shown in Figure 1780.
1723
C901260107 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 1)
Definition Description
Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 1) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure. This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module, and the reason is request UDP port failure for assignment. The measurement point is A as shown in Figure 1781.
1724
ALLOCATION FAILURE
C901260108 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 1)
Definition Description
Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 1) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure. This counter increments while BSC correctly receives EV_RANCONN_IPA_CONN_NACK message returned by access module (the reason is AIPB access failure) or TwaitConn timer timeout for assignment. The measurement point is A as shown in Figure 1782.
FIGURE 1782 CHANNEL
ALLOCATION FAILURE
Unit
Times
1725
Related Features
ZGO-05-04-003 A over IP
C901260109 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 1)
Definition Description
Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 1) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request AIPB resource failure for assignment. This counter increments while BSC correctly receives database return failure or no AIPB board resource, and the reason to apply for channel is handover and purpose is voice channel. The measurement point is A as shown in Figure 1783.
FIGURE 1783 REQUEST RESOURCE FAILURE
1726
C901260110 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 1)
Definition Description
Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 1) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure. 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 1784.
FIGURE 1784 CHANNEL
ALLOCATION FAILURE
1727
C901260111 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 1)
Definition Description
Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 1) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure. 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 1785.
FIGURE 1785 CHANNEL
ALLOCATION FAILURE
1728
C901260112 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 2)
Definition Description
Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 2) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request AIPB resource failure for assignment. 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 1786.
FIGURE 1786 REQUEST RESOURCE FAILURE
1729
C901260113 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 2)
Definition Description
Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 2) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure. 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 1787.
FIGURE 1787 CHANNEL
ALLOCATION FAILURE
1730
C901260114 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 2)
Definition Description
Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 2) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure. 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 1788.
FIGURE 1788 CHANNEL
ALLOCATION FAILURE
1731
C901260115 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 2)
Definition Description
Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 2) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request AIPB resource failure for assignment. 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 1789.
FIGURE 1789 REQUEST RESOURCE FAILURE
1732
C901260116 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 2)
Definition Description
Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 2) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure. 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 1790.
FIGURE 1790 CHANNEL
ALLOCATION FAILURE
1733
C901260117 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 2)
Definition Description
Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 2) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure. 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 1791.
FIGURE 1791 CHANNEL
ALLOCATION FAILURE
1734
C901260118 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 3)
Definition Description
Number of TCH/F allocation failure due to request AIPB resource failure for assignment (speech version 3) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request AIPB resource failure for assignment. 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 1792.
FIGURE 1792 REQUEST RESOURCE FAILURE
1735
C901260119 Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 3)
Definition Description
Number of TCH/F allocation failure due to request UDP port failure for assignment (speech version 3) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure. 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 1793.
FIGURE 1793 CHANNEL
ALLOCATION FAILURE
1736
C901260120 Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 3)
Definition Description
Number of TCH/F allocation failure due to AIPB connection failure for assignment (speech version 3) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure. 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 1794.
FIGURE 1794 CHANNEL
ALLOCATION FAILURE
1737
C901260121 Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 3)
Definition Description
Number of TCH/F allocation failure due to request AIPB resource failure for handover (speech version 3) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request AIPB resource failure for assignment. 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 1795.
FIGURE 1795 REQUEST RESOURCE FAILURE
Times ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP
1738
C901260122 Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 3)
Definition Description
Number of TCH/F allocation failure due to request UDP port failure for handover (speech version 3) 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. This counter increments while access module returns failure and the reason is failed to request UDP port.
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure. 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 1796.
FIGURE 1796 CHANNEL
ALLOCATION FAILURE
Times ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP
1739
C901260123 Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 3)
Definition Description
Number of TCH/F allocation failure due to AIPB connection failure for handover (speech version 3) 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 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.
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure. 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 1797.
FIGURE 1797 CHANNEL
ALLOCATION FAILURE
Times ZGO-01-01-003 Adaptive Multi-rate Codec (AMR) ZGO-03-02-011 Channel Repacking ZGO-05-04-003 A over IP
1740
C901260124 Number of TCH/F allocation failure due to request AIPB resource failure for assignment (data)
Definition Description
Number of TCH/F allocation failure due to request AIPB resource failure for assignment (data) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request AIPB resource failure for assignment. 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 1798.
FIGURE 1798 REQUEST RESOURCE FAILURE
1741
C901260125 Number of TCH/F allocation failure due to request UDP port failure for assignment (data)
Definition Description
Number of TCH/F allocation failure due to request UDP port failure for assignment (data) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure. 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 1799.
FIGURE 1799 CHANNEL
ALLOCATION FAILURE
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)
1742
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.
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure. 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 1800.
FIGURE 1800 CHANNEL
ALLOCATION FAILURE
C901260127 Number of TCH/F allocation failure due to request AIPB resource failure for handover (data)
Definition Description
Number of TCH/F allocation failure due to request AIPB resource failure for handover (data) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request AIPB resource failure for assignment. 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 1801.
1743
C901260128 Number of TCH/F allocation failure due to request UDP port failure for handover (data)
Definition Description
Number of TCH/F allocation failure due to request UDP port failure for handover (data) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to request UDP port failure. 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 1802.
1744
ALLOCATION FAILURE
C901260129 Number of TCH/F allocation failure due to AIPB connection failure for handover (data)
Definition Description
Number of TCH/F allocation failure due to AIPB connection failure for handover (data) 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.
This counter is used to find out the frequency of TCH/F allocation failure due to AIPB access failure. 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 1803.
FIGURE 1803 CHANNEL
ALLOCATION FAILURE
Unit
Times
1745
Related Features
C901260130 Number of assign TCH/F release by forced handover to forced handover source
Definition Description
Number of assign TCH/F release by forced handover to forced handover source When the BSC CS service instance is forcibly handover, this counter counts the number of times that the released TCH/F resource is assigned to the forced handover source. The BSC CS service instance is forcibly handover to release resource, if the released TCH/F resource is assigned to the forced handover source, the counter accumulates.
This counter is used to find out the frequency of the TCH/F released by forced handover being assigned to the forced handover source. The BSC CS service instance is forcibly handover to release resource, if the released TCH/F resource is assigned to the forced handover source, the counter accumulates. Times
Number of assign TCH/F release by forced handover to queuing user 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.
1746
This counter is used to find out the frequency of the TCH/F released by forced handover being 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. Times
Number of restore TCH/F release by forced handover to DBS 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.
This counter is used to find out the frequency of the TCH/F released by forced handover being restored to DBS. 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. Times
C901260133 Number of assign TCHF release by forced release to forced release source
Definition Description
Number of assign TCH/F release by forced release to forced release source 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.
1747
This counter is used to find out the frequency of the TCH/F released by forced release being 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. Times
Number of assign TCH/F release by forced release to queuing user 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.
This counter is used to find out the frequency of the TCH/F released by forced release being 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. Times
Number of restore TCH/F release by forced release to DBS 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.
1748
This counter is used to find out the frequency of the TCH/F released by forced release being restored to DBS. 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 1804 CHANNEL
ALLOCATION FAILURE
Unit
Times
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. 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. Times
1749
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. 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. Times
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. 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. Times
1750
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. 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. Times
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. 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. Times
1751
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. 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. Times
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. 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. Times
1752
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. 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. Times
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. 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. Times
1753
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. 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. Times
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. 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. Times
1754
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. 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. Times
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. 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. Times
Measurement Point
Unit
1755
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. For the assignment from A-interface, this counter accumulates after BSC receives the assignment success message. Times
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. 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. Times
Measurement Point
Unit
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.
1756
For the assignment from A-interface, this counter accumulates after BSC receives the assignment success message. Times
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. 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. Times
Measurement Point
Unit
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. For the assignment from A-interface, this counter accumulates after BSC receives the assignment success message. Times
1757
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. 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. Times
Measurement Point
Unit
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. The counter counts when BSC receives the ASS_COM message or the HO_COM message. Times
1758
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 handover, because the source instance is not at the BSC, the counter accumulates on the basis of destination instances. 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. Times
Measurement Point
Unit
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. The counter counts when BSC receives the ASS_COM message or the HO_COM message. Times
1759
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 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. 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. Times
Measurement Point
Unit
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. The counter counts when BSC receives the ASS_COM message or the HO_COM message. Times
1760
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. 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. After the ordinary user obtains TCH/F, if the forced release message from other call is received, the counter counts. The measurement point is A, as shown in Figure 1805.
Usage
Measurement Point
1761
FIGURE 1805 FLOW OF ORDINARY USER'S CALL BEING RELEASED RESOURCE BEING PREEMPTED
DUE TO
Unit
Times
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. 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.
Usage
1762
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 1806.
FIGURE 1806 FLOW OF HANDOVER RESOURCE BEING PREEMPTED
FOR
DUE TO
Unit
Times
This counter counts the number of requesting for TCH/F by highpriority users.
1763
After BSC receives the channel request, it attempts to allocate channel for the request. If the channel request is initiated by highpriority user, the counter increments.
Usage
This counter is used to find out the number of requesting for TCH/F by high-priority users. This counter is supported in version V6.20.61 or later. When the high-priority user requests for TCH/F, the counter counts. The measurement point is A, as shown in Figure 1807, Figure 1808, and Figure 1809.
FIGURE 1807 FLOW
OF
Measurement Point
OCCUPYING TCH/F
DURING
ASSIGNMENT
OF
OCCUPYING TCH/F
DURING
INTER-BSC HANDOVER
OF
OCCUPYING TCH/F
DURING
INTRA-BSC HANDOVER
Unit
Times
1764
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 highpriority user and the channel is obtained successfully, the counter increments.
Usage
This counter is used to find out the number of high-priority users' requesting for TCH/F successfully. This counter is supported in version V6.20.61 or later. When the high-priority user requests for TCH/F, if the channel is obtained successfully, the counter counts. The measurement point is A, as shown in Figure 1810, Figure 1811, and Figure 1812.
FIGURE 1810 FLOW
OF
Measurement Point
OCCUPYING TCH/F
DURING
ASSIGNMENT
OF
OCCUPYING TCH/F
DURING
INTER-BSC HANDOVER
OF
OCCUPYING TCH/F
DURING
INTRA-BSC HANDOVER
Unit
Times
1765
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. 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 1813, Figure 1814, and Figure 1815.
FIGURE 1813 FLOW
OF
Measurement Point
OCCUPYING TCH/F
DURING
ASSIGNMENT
OF
OCCUPYING TCH/F
DURING
INTER-BSC HANDOVER
1766
OF
OCCUPYING TCH/F
DURING
INTRA-BSC HANDOVER
Unit
Times
1767
1768
Chapter
33
TCH/H Measurement
Table of Contents Overview...................................................................... 1773 C901270002 Number of signaling TCH/H seizure success for assignment................................................................... 1776 C901270005 Number of signaling TCH/H seizure success for handover...................................................................... 1777 C901270007 Number of signaling TCH/H allocation attempts by BSC for assignment ................................................... 1779 C901270008 Number of signaling TCH/H allocation success for assignment .............................................................. 1780 C901270010 Number of signaling TCH/H allocation attempts by BSC due to handover ................................................. 1781 C901270011 Number of signaling TCH/H allocation success due to handover ............................................................ 1784 C901270012 Number of signaling TCH/H allocation failure due to handover .................................................................. 1786 C901270013 Number of signaling TCH/H assignment attempts by BSC .............................................................. 1787 C901270016 Number of signaling TCH/H handover attempts ......................................................................... 1788 C901270017 Number of signaling TCH/H handover success............................................................................. 1791 C901270018 Number of signaling TCH/H handover failure .............................................................................. 1793 C901270019 Number of signaling TCH/H handover failure messages do not received by BSC.................................... 1795 C901270021 Number of voice TCH/H seizure success for assignment...................................................................... 1796 C901270024 Number of voice TCH/H seizure success for handover........................................................................... 1797 C901270026 Number of TCH/H allocation attempts for assignment by BSC (speech version 1)...................................... 1800 C901270027 Number of TCH/H allocation success for assignment (speech version1).................................................. 1801 C901270032 Number of TCH/H allocation attempts by BSC during handover (speech version 1) ................................. 1803 C901270033 Number of TCH/H allocation success during handover (speech version 1) ................................................ 1805 C901270038 Number of TCH/H allocation attempts by BSC for assignment (speech version 2) ................................... 1807 C901270039 Number of TCH/H allocation success by BSC for assignment (speech version 2) ........................................ 1809 C901270044 Number of TCH/H allocation attempts for handover by BSC (speech version 2) ..................................... 1810 C901270045 Number of TCH/H allocation success for handover (speech version 2) ................................................ 1813
1769
C901270050 Number of TCH/H allocation attempts for assignment (speech version 3)................................................. 1815 C901270051 Number of TCH/H allocation success for assignment (speech version 3)................................................. 1817 C901270056 Number of TCH/H allocation attempts by BSC for handover (speech version 3) ...................................... 1818 C901270057 Number of TCH/H allocation success for handover (speech version 3) ................................................ 1821 C901270062 Number of Voice TCH/H assignment attempts by BSC ............................................................................. 1823 C901270065 Number of Voice TCH/H handover attempts ......................................................................... 1825 C901270067 Number of Voice TCH/H handover failure......... 1827 C901270068 Number of Voice TCH/H handover failure messages do not received by BSC ......................................... 1829 C901270070 Number of data TCH/H seizure success for assignment...................................................................... 1830 C901270073 Number of data TCH/H seizure success for handover........................................................................... 1831 C901270075 Number of data TCH/H allocation attempts for assignment by BSC........................................................ 1834 C901270076 Number of data TCH/H allocation success for assignment...................................................................... 1835 C901270081 Number of data TCH/H allocation attempts by BSC ............................................................................. 1837 C901270082 Number of data TCH/H allocation success for handover...................................................................... 1839 C901270087 Number of data TCH/H assignment attempts by BSC ............................................................................. 1842 C901270090 Number of data TCH/H handover attempts ......................................................................... 1843 C901270092 Number of data TCH/H handover failure ......... 1846 C901270093 Number of data TCH/H handover failure do not received by BSC ............................................................ 1847 C901270094 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 1)................................................................................ 1849 C901270095 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 1)................................................................................ 1850 C901270096 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 1).............. 1851 C901270097 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 1)................................................................................ 1852 C901270098 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 2)................................................................................ 1854 C901270099 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 2)................................................................................ 1855 C901270100 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 2).............. 1856 C901270101 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 2)................................................................................ 1857 C901270102 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 3)................................................................................ 1859
1770
C901270103 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 3)................................................................................ 1860 C901270104 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 3).............. 1861 C901270105 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 3)................................................................................ 1862 C901270106 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 1)................................................................................ 1863 C901270107 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 1)................................................................................ 1864 C901270108 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 1).......... 1865 C901270109 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 1)................................................................................ 1866 C901270110 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 1)......... 1867 C901270111 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 1)............. 1868 C901270112 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 2)................................................................................ 1869 C901270113 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 2)................................................................................ 1870 C901270114 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 2).......... 1871 C901270115 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 2)................................................................................ 1872 C901270116 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 2)......... 1873 C901270117 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 2)............. 1874 C901270118 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 3)................................................................................ 1875 C901270119 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 3)................................................................................ 1876 C901270120 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 3).......... 1877 C901270121 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 3)................................................................................ 1878 C901270122 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 3)......... 1879 C901270123 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 3)............. 1880 C901270124 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (data).............. 1881 C901270125 Number of TCH/H allocation failure due to request UDP port failure for assignment (data)..................... 1882 C901270126 Number of TCH/H allocation failure due to AIPB connection failure for assignment (data) ........................... 1882
1771
C901270127 Number of TCH/H allocation failure due to request AIPB resource failure for handover (data)................. 1883 C901270128 Number of TCH/H allocation failure due to request UDP port failure for handover (data)........................ 1884 C901270129 Number of TCH/H allocation failure due to AIPB connection failure for handover (data).............................. 1885 C901270130 Number of assign TCH/H release by forced handover to forced handover source...................................... 1886 C901270131 Number of assign TCH/H release by forced handover to queuing user .................................................... 1886 C901270132 Number of restore TCH/H release by forced handover to DBS ................................................................ 1887 C901270133 Number of assign TCH/H release by forced release to forced release source ......................................... 1887 C901270134 Number of assign TCH/H release by forced release to queuing user..................................................... 1888 C901270135 Number of restore TCH/H release by forced release to DBS ................................................................. 1888 C901270136 Number of signaling TCH/H seize failure for assign due to Abis lack ...................................................... 1889 C901270137 Number of signaling TCH/H seize failure for handover due to Abis lack .................................................... 1889 C901270138 Number of voice TCH/H seizure failure for assignment (cause:Abis) ................................................... 1890 C901270139 Number of voice TCH/H seizure failure for handover (cause:Abis ) ....................................................... 1890 C901270140 Number of data TCH/H seizure failure for assignment (cause:Abis) ......................................................... 1891 C901270141 Number of data TCH/H seizure failure for handover (cause:Abis) ........................................................ 1891 C901270142 Number of signaling TCH/H seize failure for assign due to radio resource lack ........................................ 1892 C901270143 Number of signaling TCH/H seize failure for handover due to radio resource lack ...................................... 1892 C901270144 Number of voice TCH/H seizure failure for assignment (cause:radio resource) ..................................... 1893 C901270145 Number of voice TCH/H seizure failure for handover (cause:radio resource) .......................................... 1893 C901270146 Number of data TCH/H seizure failure for assignment (cause:radio resource) ........................................... 1894 C901270147 Number of data TCH/H seizure failure for handover (cause:radio resource) .......................................... 1894 C901270148 Number of HR_V1 assignment attempts ......... 1895 C901270149 Number of HR_V1 assignment success........... 1895 C901270150 Number of HR_V3 assignment attempts ......... 1895 C901270151 Number of HR_V3 assignment success........... 1896 C901270152 Number of HR_V1 handover ......................... 1896 C901270153 Number of HR_V1 handover success.............. 1897 C901270154 Number of HR_V3 handover ......................... 1897 C901270155 Number of HR_V3 handover success.............. 1898 C901270177 Resource releasing of ordinary users due to being grabbed (TCH/H)...................................................... 1898 C901270178 Handover of ordinary users due to being grabbed (TCH/H) ........................................................... 1899 C901270179 Number of Channel Request of priority users (TCH/H) ....................................................................... 1901 C901270180 Number of Successful Channel seize of priority users (TCH/H)............................................................... 1902 C901270181 Number of Successful grabbing channel of priority users (TCH/H) ....................................................... 1903
1772
Overview
During GSM BSC signaling system, the allocation uses of TCH/H channel mainly exist in assignment and handover processes. The assignment processes include immediate assignment, general assignment; handover processes include inner handover and outer handover. The measurement point of TCH/H counters in immediate assignment process is shown in Figure 1816.
FIGURE 1816 IMMEDIATE
ASSIGNMENT FLOW
When TC is internal and external, the measurement point of TCH/H counter in general assignment processes is shown in Figure 1817and Figure 1818.
FIGURE 1817 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1773
ASSIGNMENT FLOW
(EXTERNAL TC)
When TC is internal and external, the measurement point of TCH/H counter in inner handover process is shown in Figure 1819 and Figure 1820.
FIGURE 1819 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1774
FIGURE 1820 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 1821 and Figure 1822.
FIGURE 1821 EXTERNAL
HANDOVER FLOW
(INTERNAL TC)
1775
HANDOVER FLOW
(EXTERNAL TC)
Number of signaling TCH/H seizure success for assignment This counter counts the number of TCH/H channel being seized when assigning signaling channel. After BSC receives request message, it tries to assign channel for the request. This counter increments when allocation and seizure succeed.
Measurement Point
BSC applies for channel (due to assignment, it is used for signaling channels) and seizure succeeds. The measurement point is A1, as shown in Figure 1823.
FIGURE 1823 IMMEDIATE
ASSIGNMENT FLOW
1776
Times 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
Number of signaling TCH/H seizure success for handover. This counter counts the number of TCH/H seizure success in signaling channel handover. After BSC receives channel request message, it tries to assign channel for the request. This counter will accumulate if assignment and seizure succeed; if application returns no signaling but it is possible to queue or being forced to disconnect, it will enter the state of waiting for resource. This counter will accumulate if waiting succeeds.
Measurement Point
BSC applies for channel (because handover, usage are signaling channels) and seizure succeeds, or it receives inner waiting resource valid message. The measurement points are C1, D1, as shown in Figure 1824, Figure 1825, Figure 1826, and Figure 1827.
FIGURE 1824 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1777
FIGURE 1825 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1778
HANDOVER FLOW
(EXTERNAL TC)
Times 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
Number of signaling TCH/H assignment attempts by BSC for assignment 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.
1779
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 1828.
FIGURE 1828 IMMEDIATE
ASSIGNMENT FLOW
Times 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
Number of signaling TCH/H allocation success for assignment This counter counts the number of TCH/H channel success assignment on allocating signaling channel. After BSC responds channel request messages assignment and successfully seizures channel, BSC sends channel activation message CHL_ACT to activate the TCH/H. If activated successfully, it will receive CHL_ACT_ACK message sent by BTS, it indicates that TCH/H assigns successfully and the counter accumulates.
Measurement Point
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 1829.
1780
ASSIGNMENT FLOW
Times 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
Number of signaling TCH/H allocation attempts by BSC due to handover 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.
1781
Measurement Point
After BSC activates TCH/H (because allocation, usage are signaling channel), receives correctly the CHL_ACK_ACK message sent by BTS, or receives channel activation failure message, wrong channel activation response message, timer T9013 timeout, channel instance being released, channel being forced to disconnection etc. (C901270011+C901270012). The measurement points are C3, C4, as shown in Figure 1830, Figure 1831, Figure 1832, and Figure 1833.
FIGURE 1830 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
FIGURE 1831 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1782
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1783
Number of signaling TCH/H allocation success due to handover This counter counts the number of successful TCH/H channel assignment in signaling channel handover. After BSC responds channel request messages assignment and successfully occupies channel, BSC sends channel activation message CHL_ACT to BTS to activate the TCH/H. If activated successfully, it will receive CHL_ACT_ACK message sent by BTS, it indicates that TCH/H assigns successfully and the counter accumulates.
Measurement Point
BSC receives correctly CHL_ACT_ACK message sent by BTS and the reason is that allocation and usage are signaling channel. The measurement points are C3, D3, as shown in Figure 1834, Figure 1835, Figure 1836, and Figure 1837.
FIGURE 1834 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1784
FIGURE 1835 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1785
HANDOVER FLOW
(EXTERNAL TC)
Times 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
Number of signaling TCH/H allocation failure due to handover This counter counts the number of TCH/H channel assignment failure. After BSC responds channel request message assignment and successfully occupies TCH/H channel, BSC send channel activation message CHL_ACT to BTS to activate the TCH/H. If channel activation fails due to receiving channel activation failure message, wrong channel activation response message, timer T9103 timeout, channel instance being released, channel being forced to disconnection etc, this counter will increment.
Measurement Point
BSC activates TCH/H to be used as signaling channel because of handover, but receiving channel activation failure message, wrong channel activation response message, timer T9103 timeout, channel instance being released, channel being forced to disconnection etc. The measurement points are C3, D3, as shown in Figure 1838, Figure 1839.
1786
(INTERNAL TC
INTRA-CELL HANDOVER)
2 (INTERNAL TC)
Times 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
Number of signaling TCH/H assignment attempts by BSC This counter counts the number of attempt allocating TCH/H channel to be signaling channel. After BSC responds channel request message assignment and successfully occupies channel, BSC sends channel activation message CHL_ACT to BTS to activate the TCH/H. To immediate allocation, after activated successfully BTS receives MS and send EST_IND message to BSC, BSC receives the messages and this counter ac-
1787
cumulates; if it is impossible to receive the MS access notification in the certain time, this allocation fails.
Measurement Point
For immediate allocation, this counter counts the number when BSC receives EST_IND message correctly or T31.3 timeout (not receive the MS access notification in the certain time). The measurement point is A3, as shown in Figure 1840.
FIGURE 1840 IMMEDIATE
ASSIGNMENT FLOW
Number of signaling TCH/H handover attempts This counter counts the number of TCH/H channel attempt in signaling channel handover, including the number of successful TCH/H handover (C901270017), the number of TCH/H handover failure with return (C901270018), and the number of TCH/H handover failure without return (C901270019). When BSC check the handover success message from MS in the newly assigned TCH/H channel, this counter and C901270017 will accumulate; if receiving the failure message, this counter and C901270018 will accumulate; if receiving abnormal message, or instance being released, instance being forced to disconnection, timer timeout, this counter and C901270019 will accumulate. For handover in cell, the symbol message of handover success is ASS_COM. For handover between cells and outer handover, the symbol message of handover success is HO_COM. For handover
1788
in cell and between cells, the counter accumulates based on the resource instance; for the outer handover, because the resource instance is not in present BSC, the counter accumulates based on the object instance.
Measurement Point
On newly assigned TCH/H channel, BSC check the handover success ASS_COM/HO_FAIL message sent by MS, or receives handover failure ASS_FAIL/HO_FAIL message, receives abnormal message, instance being released, instance being forced to disconnection, timer timeout, this counter will accumulate. The measurement points are C4, D4, as shown in Figure 1841, Figure 1842, Figure 1843, and Figure 1844.
FIGURE 1841 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
FIGURE 1842 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1789
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking
1790
Number of signaling TCH/H handover success This counter counts the number of TCH/H channel success in signaling channel handover. When BSC check the handover success message sent by MS in newly assigned TCH/H channel, this counter will accumulate. For handover in cell, the symbol message of handover success is ASS_COM. For handover between cells and outer handover, the symbol message of handover success is HO_COM. For handover in cell and between cells, the counter accumulates based on the resource instance; for the outer handover, because the resource instance is not in present BSC, the counter accumulates based on the object instance.
Measurement Point
BSC receives ASS_COM or HO_COM message. The measurement points are C4, D4, as shown in Figure 1845, Figure 1846, Figure 1847 and Figure 1848.
FIGURE 1845 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1791
FIGURE 1846 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1792
HANDOVER FLOW
(EXTERNAL TC)
Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking
Number of signaling TCH/H handover failure This counter counts the number of TCH/H channel return handover failure. This counter accumulates when MS on the TCH/H channel are in handover, accesses new channel failure and returns original channel, receives allocation failure on original channel or handover failure.
Measurement Point
BSC receives ASS_FAIL or HO_FAIL message. The measurement points are C4, D4, as shown in Figure 1849, Figure 1850.
1793
HANDOVER
(INTERNAL TC
INTRA-CELL HANDOVER)
(INTERNAL TC)
Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking
1794
C901270019 Number of signaling TCH/H handover failure messages do not received by BSC
Definition Description
Number of signaling TCH/H handover failure messages do not received by BSC This counter counts the number of TCH/H channel return no handover failure. This counter accumulates when BSC sends allocation request to MS or handover request, MS does not handover successfully and does not return original channel.
Measurement Point
BSC receives abnormal message, or instance being released, instance being forced to disconnection, timer timeout message. The measurement point is C4, as shown in Figure 1851, Figure 1852.
FIGURE 1851 INTERNAL HANDOVER FAILURE FLOW 2 (INTERNAL TC
INTRA-CELL HANDOVER)
(INTERNAL TC
INTRA-CELL HANDOVER)
1795
Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking
Number of voice TCH/H seizure success for assignment This counter counts the number of TCH/H channel being occupied successfully on allocation voice channel. After BSC receives channel request message, it attempts to assign channel for the request. This counter will accumulate if assignment and occupation succeed. If application returns no channel but possible to queue or force to disconnect, it enters the state of waiting for resource. This counter accumulates if waiting succeeds.
Measurement Point
BSC applies for channel (because allocation, usage are voice channel) and occupation succeeds or BSC receives inner waiting resource valid message. The measurement point is B1, as shown in Figure 1853, Figure 1854.
FIGURE 1853 INTERNAL FAILURE FLOW 1
HANDOVER
(INTERNAL TC
INTRA-CELL HANDOVER)
1796
(INTERNAL TC)
Times 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
Number of voice TCH/H seizure success for handover 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 1855, Figure 1856, Figure 1857, and Figure 1858.
1797
HANDOVER
(LIKE
FIGURE 1856 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1798
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1799
C901270026 Number of TCH/H allocation attempts for assignment by BSC (speech version 1)
Definition Description
Number of TCH/H allocation attempts for assignment by BSC (speech version 1) This counter counts the number of TCH/H channel being attempt to assign on allocation voice channel (used for voice version 1), including assignment success (C901270027) and assignment failure (C900060175+C900060176+900060177+C900060178) After BSC respond channel request message assignment and successfully occupied TCH/H channel, BSC first finishes connection, then sends channel activation message CHL_ACT to BTS to activate the the TCH/H. If activation succeeds, BSC will receive the CHL_ACT_ACK message sent by BTS. It indicated that assignment succeeds, this counter and C901270027 accumulate simultaneously; on the contrary, if failed, this counter and another counter related the failure reason accumulate siulataneously.
Measurement Point
Assignment succeeds or fails (because allocation and usage are voice channel, use voice version 1). The measurement points are B2, B3, as shown in Figure 1859, Figure 1860.
FIGURE 1859 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1800
ASSIGNMENT FLOW
(EXTERNAL TC)
Times 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
Number of TCH/H allocation success for assignment (speech version1) 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 1861, Figure 1862.
1801
ASSIGNMENT FLOW
(INTERNAL TC)
ASSIGNMENT FLOW
(EXTERNAL TC)
Times 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
1802
C901270032 Number of TCH/H allocation attempts by BSC during handover (speech version 1)
Definition Description
Number of TCH/H allocation attempts by BSC during handover (speech version 1) 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 1863, Figure 1864, and Figure 1865.
FIGURE 1863 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1803
FIGURE 1864 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
Times 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
1804
Number of TCH/H allocation success during handover (speech version 1) 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 1866, Figure 1867, Figure 1868, and Figure 1869.
FIGURE 1866 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1805
FIGURE 1867 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1806
HANDOVER FLOW
(EXTERNAL TC)
Times 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
C901270038 Number of TCH/H allocation attempts by BSC for assignment (speech version 2)
Definition Description
Number of TCH/H allocation attempts by BSC for assignment (speech version 2) This counter counts the number of TCH/H channel being attempt to assign on allocation voice channel (use voice version 2), including assignment success (C901270039) and assignment failure (C900060183+C900060184+900060185+C900060186) 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 TCH/H. If activation succeeds, it will receive the CHL_ACT_ACK message sent by BTS. It indicated that TCH/H assignment succeeds, this counter and C901270039 accumulate simultaneously; on the contrary, if failed, this counter and another counter related the failure reason accumulate simultaneously.
1807
Measurement Point
Assignment succeeds or fails (because allocation, usage are voice channel, use voice version 2). The measurement points are B2, B3, as shown in Figure 1870, Figure 1871.
FIGURE 1870 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
ASSIGNMENT FLOW
(EXTERNAL TC)
Times 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
1808
C901270039 Number of TCH/H allocation success by BSC for assignment (speech version 2)
Definition Description
Number of TCH/H allocation success by BSC for assignment (speech version 2) This counter counts the number of TCH/H channel success assignment on allocation voice channel (use voice version 2). After BSC responds channel request message assignment and successfully occupied channel, BSC sends channel activation message 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 2). The measurement point is B3, as shown in Figure 1872, Figure 1873.
FIGURE 1872 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1809
ASSIGNMENT FLOW
(EXTERNAL TC)
Times ZGO-03-03-003 1:8 Dynamic Multiplexing on Ater Interface ZGO-01-01-001 Half Rate ZGO-01-01-002 Enhanced Full Rate (EFR) Speech Codec ZGO-03-02-003 Full dynamic channel allocation on Um interface ZGO-03-02-005 Dynamic Half Rate Allocation
C901270044 Number of TCH/H allocation attempts for handover by BSC (speech version 2)
Definition Description
Number of TCH/H allocation attempts for handover by BSC (speech version 2) This counter counts the number of TCH/H channel being attempt to assign on voice channel (use voice version 2) handover, including assignment success (C901270045) and assignment failure (C900060187+C900060188+900060189+C900060190) After BSC responds channel request message assignment and successfully occupied TCH/H channel, BSC first finishes connection, 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.
1810
Measurement Point
Assignment succeeds or fails (because handover, usage are voice channel, use voice version 2). The measurement points are C2, D3, as shown in Figure 1874, Figure 1875, Figure 1876, and Figure 1877.
FIGURE 1874 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
FIGURE 1875 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1811
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1812
Number of TCH/H allocation success for handover (speech version 2) This counter counts the number of TCH/H channel success assignment on voice channel (use voice version 2). 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 handover and usage are voice channel (use voice version 2). The measurement points are C3, D3, as shown in Figure 1878, Figure 1879, Figure 1880, and Figure 1881.
FIGURE 1878 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1813
FIGURE 1879 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1814
HANDOVER FLOW
(EXTERNAL TC)
Times 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
Number of TCH/H allocation attempts for assignment (speech version 3) 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.
1815
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 1882and Figure 1883.
FIGURE 1882 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
ASSIGNMENT FLOW
(EXTERNAL TC)
Times 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
1816
Number of TCH/H allocation success for assignment (speech version 3) 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 1884 and Figure 1885.
FIGURE 1884 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1817
ASSIGNMENT FLOW
(EXTERNAL TC)
Times 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
C901270056 Number of TCH/H allocation attempts by BSC for handover (speech version 3)
Definition Description
Number of TCH/H allocation attempts by BSC for handover (speech version 3) 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.
1818
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 1886, Figure 1887, Figure 1888, and Figure 1889.
FIGURE 1886 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
FIGURE 1887 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1819
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1820
Number of TCH/H allocation success for handover (speech version 3) 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 1890, Figure 1891, Figure 1892, and Figure 1893.
FIGURE 1890 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1821
FIGURE 1891 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1822
HANDOVER FLOW
(EXTERNAL TC)
Times 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
Number of Voice TCH/H assignment attempts by BSC This counter counts the number of attempting TCH/H channel to be voice channel, including assignment success (C900060199) and allocation failure (C900060200). 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.
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.
1823
(INTERNAL TC)
ASSIGNMENT FLOW
(EXTERNAL TC)
1824
Number of Voice TCH/H handover attempts This counter counts the number of TCH/H channel attempt in voice channel handover, including the number of TCH/H handover success (C900060201), TCH/H handover failure with return (C901270067) and TCH/H handover failure without return (C901270068). During handover, when MS is accessed successfully on the new channel, BSC will receive allocation finishing message ASS_COM (handover in cell) or HO_COM message (handover between cells and outer handover). If BSC correctly receives the message above in the certain time, it indicated that handover succeed, the related counter and C900060201 will accumulate simultaneously; if BSC receives HO_FAILURE, it returns handover failure, this counter and C901270067 will accumulate simultaneously; if handover fails, BSC does not receive HO_FAILURE, then no return handover fails. This counter and C901270068 will accumulate simultaneously. For handover in cell and between cells, this counter accumulates based on the resource instance; for outer handover, because the resource instance is not in local BSC, the object instance accumulates.
Measurement Point
BSC receives ASS_COM/HO_COM message, ASS_FAIL/HO_FAIL message or receive abnormal message, the instance being released, the instance being forced to disconnection, timer timeout. The measurement points are C4, D4, as shown in Figure 1896, Figure 1897, Figure 1898, and Figure 1899.
FIGURE 1896 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1825
FIGURE 1897 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1826
HANDOVER FLOW
(EXTERNAL TC)
Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking
Number of Voice TCH/H handover failure This counter counts the number of TCH/H channel returning handover failure on voice channel handover. MS is in handover on TCH/H channel, accesses new channel failure and returns original channel. This counter accumulates when receiving allocation failure/handover failure on original channel.
Measurement Point
BSC receives the ASS_FAIL/HO_FAIL message. The measurement points are C4, D4, as shown in Figure 1900and Figure 1901.
1827
HANDOVER
(INTERNAL TC
INTRA-CELL HANDOVER)
(INTERNAL TC)
Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking
1828
C901270068 Number of Voice TCH/H handover failure messages do not received by BSC
Definition Description
Number of Voice TCH/H handover failure messages do not received by BSC This counter counts the number of TCH/H channel returning no handover failure on voice channel handover. BSC sends allocation request/handover request to MS, MS does not handover successfully, not return resource channel, and then accumulates.
Measurement Point
BSC receives abnormal message, timer timeout message or the instance being released, the instance being forced to disconnection. The measurement points are C4, D4, as shown in Figure 1902and Figure 1903.
FIGURE 1902 INTERNAL HANDOVER FAILURE FLOW 2 (INTERNAL TC
INTRA-CELL HANDOVER)
(INTERNAL TC
INTRA-CELL HANDOVER)
1829
Times ZGO-01-01-001 Half Rate ZGO-03-02-005 Dynamic Half Rate Allocation ZGO-03-02-011 Channel Repacking
Number of data TCH/H seizure success for assignment This counter counts the number of TCH/H channel being occupied successfully on allocation data channel. 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 1904and Figure 1905.
FIGURE 1904 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1830
ASSIGNMENT FLOW
(EXTERNAL TC)
Times 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
Number of data TCH/H seizure success for handover 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 1906, Figure 1907, Figure 1908, and Figure 1909.
1831
HANDOVER
(LIKE
FIGURE 1907 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1832
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1833
Number of data TCH/H allocation attempts for assignment by BSC 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). 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 C901270076 accumulate simultaneously; on the contrary, if fails, this counter and another counter related the failure reason accumulate simultaneously. Assignment succeeds or fails (because allocation, usage are data channel). The measurement points are B2, B5, as shown in Figure 1910and Figure 1911.
FIGURE 1910 COMMON
ASSIGNMENT FLOW
Usage
Measurement Point
(INTERNAL TC)
1834
ASSIGNMENT FLOW
(EXTERNAL TC)
Times 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
Number of data TCH/H allocation success for assignment 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 1912and Figure 1913.
1835
ASSIGNMENT FLOW
(INTERNAL TC)
ASSIGNMENT FLOW
(EXTERNAL TC)
Times 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
1836
Number of data TCH/H allocation attempts by BSC This counter counts the number of TCH/H channel being attempted to assign on data channel handover, including assignment success (C901270082) and assignment failure (C900060206 + C900060207 + C900060208 + C900060209). 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.
Measurement Point
Assignment succeeds or fails (because handover, usage are data channels). The measurement points are C3, D3, as shown in Figure 1914, Figure 1915, Figure 1916, and Figure 1917.
FIGURE 1914 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
1837
FIGURE 1915 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
HANDOVER FLOW
(INTERNAL TC)
1838
HANDOVER FLOW
(EXTERNAL TC)
Times 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
Number of data TCH/H allocation success for handover 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 1918, Figure 1919, Figure 1920, and Figure 1921.
1839
HANDOVER
(LIKE
FIGURE 1919 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1840
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1841
Number of data TCH/H assignment attempts by BSC This counter counts the number of attempting TCH/H channel to be data channel, including assignment success (C900060210) and allocation failure (C900060211). 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.
Measurement Point
For allocation from A-interface, BSC correctly receives the allocation success message, allocation failure message, timer timeout message, or abnormal message, the instance being released, the instance being forced to disconnect, this counter accumulates. The measurement point is B5, as shown in Figure 1922and Figure 1923.
FIGURE 1922 COMMON
ASSIGNMENT FLOW
(INTERNAL TC)
1842
ASSIGNMENT FLOW
(EXTERNAL TC)
Times 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
Number of data TCH/H handover attempts This counter counts the number of TCH/H channel attempt on data channel handover, including TCH/H handover success (C900060212), TCH/H returning handover failure (C901270092) and TCH/H returning no handover failure (C901270093). During handover, when MS is accessed successfully on the new channel, BSC will receive allocation finishing message ASS_COM (handover in cell) or HO_COM message (handover between cells and outer handover). If BSC correctly receives the message above in the certain time, it indicated that handover succeed, this related counter and C900060212 will accumulate simultaneously; if BSC receives HO_FAILURE, it returns handover failure, this counter and C901270092 will accumulate simultaneously; if handover fails, BSC does not receive HO_FAILURE, then no returning handover fails. This counter and C901270093 will accumulate simultaneously. For handover in cell and between cells, this counter accumulates based on the resource instance; for outer handover, because the resource instance is not in local BSC, the object instance accumulates.
1843
Measurement Point
BSC receives ASS_COM/HO_COM message, ASS_FAIL/HO_FAIL message or receive abnormal message, the instance being released, the instance being forced to disconnection, timer timeout. The measurement points are C4, D4, as shown in Figure 1924, Figure 1925, Figure 1926, and Figure 1927.
FIGURE 1924 INTERNAL (INTERNAL TC)
HANDOVER
(LIKE
FIGURE 1925 INTERNAL HANDOVER (DURING INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FLOW (EXTERNAL TC)
1844
HANDOVER FLOW
(INTERNAL TC)
HANDOVER FLOW
(EXTERNAL TC)
Times 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
1845
Number of data TCH/H handover failure This counter counts the number of TCH/H channel returning handover failure on data channel handover. MS is under handover on TCH/H channel, access new channel fails then returns original channel. This counter accumulates when receiving allocation failure/handover failure on original channel.
Measurement Point
BSC receives the ASS_FAIL/HO_FAIL message. The measurement points are C4, D4, as shown in Figure 1928and Figure 1929.
FIGURE 1928 INTERNAL FAILURE FLOW 1
HANDOVER
(INTERNAL TC
INTRA-CELL HANDOVER)
1846
(INTERNAL TC)
Times 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
Number of data TCH/H handover failure do not received by BSC This counter counts the number of TCH/H channel returning no handover failure on data channel handover. After BSC sends allocation request/handover request to MS, MS does not handover successfully, not go back to the original channel, then accumulate.
Measurement Point
BSC receives abnormal message, the instance being released, the instance being forced to disconnect or timer timeout message. The measurement point is C4, as shown in Figure 1930and Figure 1931.
1847
HANDOVER
(INTERNAL TC
INTRA-CELL HANDOVER)
HANDOVER
(INTERNAL TC
INTRA-CELL HANDOVER)
Times 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
1848
C901270094 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 1)
Definition Description
Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 1) This counter counts the number of TCH/H channel assignment failure due to TIPB connection failure when allocating voice channel (use voice version 1). After BSC responds channel request message assignment and successfully occupied TCH/H channel, BSC sends TIU connection request to TIPB. If TIU connection fails due to receiving TIU connection failure, or wrong TIU connection respond message, timer timeout, then this counter will accumulate.
Measurement Point
Due to allocation BSC uses TCH/H. Receive connection failure message, wrong connection respond message, or timer timeout when in TIU connection. The measurement point is B2, as shown in Figure 1932.
FIGURE 1932 GENERAL ASSIGNMENT FAILURE FLOW 1 (EXTERNAL TC)
Times 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
1849
C901270095 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 1)
Definition Description
Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 1) This counter counts the number of TCH/H channel assignment failure due to iTC application resource failure when allocating voice channel (use voice version 1). After BSC responds channel request message assignment and successfully occupied TCH/H channel, BSC apply for resource to iTC. If iTC application resource fails due to receiving iTC resource unavailability, or wrong response message, or timer timeout, then it contributes to TCH/H assignment failure and this counter will accumulate.
Measurement Point
Due to allocation BSC uses TCH/H. Receive iTC resource unabailability, wrong respond message, or timer timeout when in iTC application resource. The measurement point is B1, as shown in Figure 1933.
FIGURE 1933 GENERAL ASSIGNMENT FAILURE FLOW 2 (EXTERNAL TC)
Times 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
1850
C901270096 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 1)
Definition Description
Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 1) 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 1934and Figure 1935.
FIGURE 1934 INTERNAL
HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 1
1851
HANDOVER FLOW
(EXTERNAL TC)
Times 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
C901270097 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 1)
Definition Description
Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 1) 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.
1852
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 1936and Figure 1937.
FIGURE 1936 INTERNAL
HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 2
2 (EXTERNAL TC)
Times 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
1853
C901270098 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 2)
Definition Description
Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 2) This counter counts the number of TCH/H channel assignment failure due to TIPB connection failure when allocating voice channel (use voice version 2). 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 1938.
FIGURE 1938 GENERAL ASSIGNMENT FAILURE FLOW 1 (EXTERNAL TC)
Times 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
1854
C901270099 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 2)
Definition Description
Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 2) This counter counts the number of TCH/H channel assignment failure due to iTC application resource failure when allocating voice channel (use voice version 2). 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 response message, or timer timeout when in iTC application resource. The measurement point is B1, as shown in Figure 1939.
FIGURE 1939 GENERAL ASSIGNMENT FAILURE FLOW 2 (EXTERNAL TC)
Times 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
1855
C901270100 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 2)
Definition Description
Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 2) This counter counts the number of TCH/H channel assignment failure due to TIU connection failure when voice channel handover (use voice version 2). 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 1940and Figure 1941.
FIGURE 1940 INTERNAL
HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 1
1856
HANDOVER FLOW
(EXTERNAL TC)
Times 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
C901270101 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 2)
Definition Description
Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 2) This counter counts the number of TCH/H channel assignment failure due to iTC application resource failure when voice channel (use voice version 2). 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.
1857
Measurement Point
Due to handover BSC uses TCH/H. Receive iTC resource un availability, wrong response message, or timer timeout when in iTC application resource. The measurement points are C1, D1, as shown in Figure 1942and Figure 1943.
FIGURE 1942 INTERNAL
HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 2
2 (EXTERNAL TC)
Times 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
1858
C901270102 Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 3)
Definition Description
Number of TCH/H allocation failure for assignment due to TIPB connection failure (Speech version 3) 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 1944.
FIGURE 1944 GENERAL ASSIGNMENT FAILURE FLOW 1 (EXTERNAL TC)
Times 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
1859
C901270103 Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 3)
Definition Description
Number of TCH/H allocation failure for assignment due to Resource request to iTC failure (Speech version 3) 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 1945.
FIGURE 1945 GENERAL ASSIGNMENT FAILURE FLOW 2 (EXTERNAL TC)
Times 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
1860
C901270104 Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 3)
Definition Description
Number of TCH/H allocation failure for handover due to TIPB connection failure (Speech version 3) 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 1946and Figure 1947.
FIGURE 1946 INTERNAL
HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 1
1861
HANDOVER FLOW
(EXTERNAL TC)
Times 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
C901270105 Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 3)
Definition Description
Number of TCH/H allocation failure for handover due to Resource request to iTC failure (Speech version 3) 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.
Measurement Point
Due to allocation BSC uses TCH/H. Receive iTC resource unavailability, wrong response message, or timer timeout when in iTC ap-
1862
plication resource. The measurement points are C1, D1, as shown in Figure 1948 and Figure 1949.
FIGURE 1948 INTERNAL
HANDOVER (EXTERNAL TC INTRA-CELL HANDOVER, AND CHANNEL TYPES ARE CHANGED) FAILURE FLOW 2
2 (EXTERNAL TC)
Times 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
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)
1863
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.
This counter is used to find out the frequency of TCH/H allocation failure due to request AIPB resource failure for assignment. 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 1950.
FIGURE 1950 REQUEST RESOURCE FAILURE
Unit
Times
C901270107 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 1)
Definition Description
Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 1) 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.
1864
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 1951.
FIGURE 1951 CHANNEL
ALLOCATION FAILURE
Unit
Times
C901270108 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 1)
Definition Description
Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 1) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure. 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 1952.
1865
ALLOCATION FAILURE
Unit
Times
C901270109 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 1)
Definition Description
Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 1) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to request AIPB resource failure for assignment. 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 1953.
1866
C901270110 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 1)
Definition Description
Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 1) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to request UDP port failure. 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 1954.
1867
ALLOCATION FAILURE
C901270111 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 1)
Definition Description
Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 1) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure. 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 1955.
FIGURE 1955 CHANNEL
ALLOCATION FAILURE
Unit
Times
1868
Related Features
C901270112 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 2)
Definition Description
Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 2) 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 2) to apply for AIPB board resource from database, failed request (including database return failure or no AIPB board resource) indicates TCH/H allocation failure.
This counter is used to find out the frequency of TCH/H allocation failure due to request AIPB resource failure for assignment. 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 1956.
FIGURE 1956 REQUEST RESOURCE FAILURE
Unit
Times
1869
C901270113 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 2)
Definition Description
Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 2) 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 2), access request is sent to access module, if access module returns access failure due to UDP port request failure.
This counter is used to find out the frequency of TCH/H allocation failure due to request UDP port failure. 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 1957.
FIGURE 1957 CHANNEL
ALLOCATION FAILURE
Unit
Times
1870
C901270114 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 2)
Definition Description
Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 2) 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 2), access request is sent to access module, if access module returns access failure due to UDP port request failure.
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure. 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 1958.
FIGURE 1958 CHANNEL
ALLOCATION FAILURE
Unit
Times
1871
C901270115 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 2)
Definition Description
Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 2) 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 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/H allocation failure.
This counter is used to find out the frequency of TCH/H allocation failure due to request AIPB resource failure for assignment. 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 1959.
FIGURE 1959 REQUEST RESOURCE FAILURE
1872
C901270116 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 2)
Definition Description
Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 2) This counter counts the number of TCH/H 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.
This counter is used to find out the frequency of TCH/H allocation failure due to request UDP port failure. 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 1960.
FIGURE 1960 CHANNEL
ALLOCATION FAILURE
1873
C901270117 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 2)
Definition Description
Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 2) 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 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.
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure. 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 1961.
FIGURE 1961 CHANNEL
ALLOCATION FAILURE
1874
C901270118 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 3)
Definition Description
Number of TCH/H allocation failure due to request AIPB resource failure for assignment (speech version 3) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to request AIPB resource failure for assignment. 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 1962.
FIGURE 1962 REQUEST RESOURCE FAILURE
1875
C901270119 Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 3)
Definition Description
Number of TCH/H allocation failure due to request UDP port failure for assignment (speech version 3) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to request UDP port failure. 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 1963.
FIGURE 1963 CHANNEL
ALLOCATION FAILURE
1876
C901270120 Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 3)
Definition Description
Number of TCH/H allocation failure due to AIPB connection failure for assignment (speech version 3) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure. 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 1964.
FIGURE 1964 CHANNEL
ALLOCATION FAILURE
1877
C901270121 Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 3)
Definition Description
Number of TCH/H allocation failure due to request AIPB resource failure for handover (speech version 3) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to request AIPB resource failure for assignment. 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 1965.
FIGURE 1965 REQUEST RESOURCE FAILURE
1878
C901270122 Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 3)
Definition Description
Number of TCH/H allocation failure due to request UDP port failure for handover (speech version 3) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to request UDP port failure. 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 1966.
FIGURE 1966 CHANNEL
ALLOCATION FAILURE
1879
C901270123 Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 3)
Definition Description
Number of TCH/H allocation failure due to AIPB connection failure for handover (speech version 3) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure. 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 1967.
FIGURE 1967 CHANNEL
ALLOCATION FAILURE
1880
C901270124 Number of TCH/H allocation failure due to request AIPB resource failure for assignment (data)
Definition Description
Number of TCH/H allocation failure due to request AIPB resource failure for assignment (data) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to request AIPB resource failure for assignment. 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 1968.
FIGURE 1968 REQUEST RESOURCE FAILURE
Unit
Times
1881
C901270125 Number of TCH/H allocation failure due to request UDP port failure for assignment (data)
Definition Description
Number of TCH/H allocation failure due to request UDP port failure for assignment (data) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to request UDP port failure. 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 1969.
FIGURE 1969 CHANNEL
ALLOCATION FAILURE
Unit
Times
C901270126 Number of TCH/H allocation failure due to AIPB connection failure for assignment (data)
Definition Description
Number of TCH/H allocation failure due to AIPB connection failure for assignment (data) This counter counts the number of TCH/H channel allocation failure due to UDP port failure during assigning voice channel.
1882
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 Measurement Point
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure. 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 1970.
FIGURE 1970 CHANNEL
ALLOCATION FAILURE
Unit
Times
C901270127 Number of TCH/H allocation failure due to request AIPB resource failure for handover (data)
Definition Description
Number of TCH/H allocation failure due to request AIPB resource failure for handover (data) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to request AIPB resource failure for assignment. 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 1971.
1883
C901270128 Number of TCH/H allocation failure due to request UDP port failure for handover (data)
Definition Description
Number of TCH/H allocation failure due to request UDP port failure for handover (data) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to request UDP port failure. 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 1972.
FIGURE 1972 CHANNEL
ALLOCATION FAILURE
1884
C901270129 Number of TCH/H allocation failure due to AIPB connection failure for handover (data)
Definition Description
Number of TCH/H allocation failure due to AIPB connection failure for handover (data) 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.
This counter is used to find out the frequency of TCH/H allocation failure due to AIPB access failure. 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 1973.
FIGURE 1973 CHANNEL
ALLOCATION FAILURE
1885
C901270130 Number of assign TCH/H release by forced handover to forced handover source
Definition Description
Number of assign TCH/H release by forced handover to forced handover source 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. 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. Times
Number of assign TCH/H release by forced handover to queuing user 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.
This counter is used to find out the frequency of the TCH/H released by forced handover being 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. Times
1886
Number of restore TCH/H release by forced handover to DBS 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.
This counter is used to find out the frequency of the TCH/H released by forced handover being restored to DBS. 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. Times
C901270133 Number of assign TCH/H release by forced release to forced release source
Definition Description
Number of assign TCH/H release by forced release to forced release source 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.
This counter is used to find out the frequency of the TCH/H released by forced release being 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. Times
1887
Number of assign TCH/H release by forced release to queuing user 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.
This counter is used to find out the frequency of the TCH/H released by forced release being 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. Times
Number of restore TCH/H release by forced release to DBS 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.
This counter is used to find out the frequency of the TCH/H released by forced release being restored to DBS. 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. Times
1888
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. 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. Times
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. 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. Times
1889
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. 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. Times
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. 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. Times
1890
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. 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. Times
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. 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. Times
1891
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. 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. Times
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. 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. Times
1892
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. 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. Times
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. 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. Times
1893
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. 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. Times
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. 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. Times
1894
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. 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. Times
Measurement Point
Unit
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. For the assignment from A-interface, this counter accumulates after BSC receives the assignment success message. Times
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
1895
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. Times
Unit
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. For the assignment from A-interface, this counter accumulates after BSC receives the assignment success message. Times
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. 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.
Measurement Point
1896
Unit
Times
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. The counter counts when BSC receives the ASS_COM message or the HO_COM message. Times
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. 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. Times
Measurement Point
Unit
1897
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. The counter counts when BSC receives the ASS_COM message or the HO_COM message. Times
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. 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. After the ordinary user obtains TCH/H, if the forced release message from other call is received, the counter counts. The measurement point is A, as shown in Figure 1974.
Usage
Measurement Point
1898
Unit
Times
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.
1899
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. 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 1975.
FIGURE 1975 HANDOVER (TCH/H)
OF ORDINARY USERS DUE TO BEING GRABBED
Measurement Point
Unit
Times
1900
This counter counts the number of requesting for TCH/H by highpriority users. After BSC receives the channel request, it attempts to allocate channel for the request. If the channel request is initiated by highpriority user, the counter increments.
Usage
This counter is used to find out the number of requesting for TCH/H by high-priority users. This counter is supported in version V6.20.61 or later. When the high-priority user requests for TCH/H, the counter counts. The measurement point is A, as shown in Figure 1976, Figure 1977, and Figure 1978.
FIGURE 1976 FLOW
OF
Measurement Point
OCCUPYING TCH/F
DURING
ASSIGNMENT
OF
OCCUPYING TCH/F
DURING
INTER-BSC HANDOVER
OF
OCCUPYING TCH/F
DURING
INTRA-BSC HANDOVER
Unit
Times
1901
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 highpriority user and the channel is obtained successfully, the counter increments.
Usage
This counter is used to find out the number of high-priority users' requesting for TCH/H successfully. This counter is supported in version V6.20.61 or later. When the high-priority user requests for TCH/H, if the channel is obtained successfully, the counter counts. The measurement point is A, as shown in Figure 1979, Figure 1980, and Figure 1981.
FIGURE 1979 FLOW
OF
Measurement Point
OCCUPYING TCH/F
DURING
ASSIGNMENT
OF
OCCUPYING TCH/F
DURING
INTER-BSC HANDOVER
OF
OCCUPYING TCH/F
DURING
INTRA-BSC HANDOVER
Unit
Times
1902
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. 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 1982, Figure 1983, and Figure 1984.
FIGURE 1982 FLOW
OF
Measurement Point
OCCUPYING TCH/F
DURING
ASSIGNMENT
OF
OCCUPYING TCH/F
DURING
INTER-BSC HANDOVER
1903
OF
OCCUPYING TCH/F
DURING
INTRA-BSC HANDOVER
Unit
Times
1904
Chapter
34
1905
C901280024 Number of PHYSICAL CONTEXT CONFIRM messages........................................................................... 1925 C901280025 Number of RF CHANNEL RELEASE messages........................................................................... 1925 C901280026 Number of MS POWER CONTROL messages........................................................................... 1926 C901280027 Number of BS POWER CONTROL messages........................................................................... 1927 C901280028 Number of PREPROCESSED CONFIGURE messages........................................................................... 1927 C901280029 Number of PREPROCESSED MEASUREMENT RESULT messages ............................................................. 1928 C901280030 Number of RF CHANNEL RELEASE ACK messages........................................................................... 1929 C901280031 Number of SACCH INFO MODIFY messages........................................................................... 1930 C901280032 Number of ABIS_PREPROC_ENHANCEMEAS_RESULT messages ................................................ 1930 C901280033 Number of ABIS_ROUND_TRIP_DELAY_REPORT messages ..................................................................... 1931 C901280034 Number of ABIS_PRE_HO_NOTIFY messages........................................................................... 1932 C901280035 Number of ABIS_BCCH_INFO messages......... 1932 C901280036 Number of ABIS_CCCH_LOAD_IND messages........................................................................... 1933 C901280037 Number of ABIS_CHL_RQD messages............ 1934 C901280038 Number of ABIS_DELETE_IND messages......... 1934 C901280039 Number of ABIS_PAGING_CMD messages........................................................................... 1935 C901280040 Number of ABIS_IMM_ASSIGN_CMD messages........................................................................... 1936 C901280041 Number of ABIS_SMS_BROADCAST_REQ messages........................................................................... 1936 C901280042 Number of ABIS_SMS_BROADCAST_CMD messages........................................................................... 1937 C901280043 Number of ABIS_CBCH_LOAD_IND messages........................................................................... 1938 C901280044 Number of ABIS_EGPRS_CHL_REQ messages........................................................................... 1938 C901280045 Number of ABIS_LOAD_CONTROL messages........................................................................... 1939 C901280046 Number of ABIS_END_LOAD_CONTROL messages........................................................................... 1940 C901280047 Number of ABIS_END_LOAD_CONTROL_ACK messages ..................................................................... 1940 C901280048 Number of ABIS_PCCCH_LOAD_IND messages........................................................................... 1941 C901280049 Number of ABIS_RF_RESRC_IND messages........................................................................... 1942 C901280050 Number of ABIS_SACCH_FILLING messages........................................................................... 1942 C901280051 Number of ABIS_OVERLOAD messages .......... 1943 C901280052 Number of ABIS_ERROR_REPORT messages........................................................................... 1944 C901280053 Number of ABIS_SYSINFO_REQ messages........................................................................... 1944 C901280054 Number of ABIS_SI_BC_END messages ......... 1945 C901280055 Number of ABIS_SI_NACK messages............. 1946 C901280056 Number of ABIS_PWRCTRL_IND messages........................................................................... 1946
1906
C901280057 Number of ABIS_SYSINFO_ACK messages........................................................................... 1947 C901280061 Number of ABIS_PACKET_PBCCH_INF messages........................................................................... 1948 C901280062 Number of ABIS_PACKET_CCCH_PARA messages........................................................................... 1948 C901280063 Number of ABIS_PACKET_PBCCH_PARA messages........................................................................... 1949 C901280064 Number of ABIS_PACKET_CHN_REQ messages........................................................................... 1950 C901280065 Number of ABIS_PACKET_PAGING_CMD messages........................................................................... 1950 C901280066 Number of ABIS_PACKET_IMM_ASSIGN_CMD messages ..................................................................... 1951 C901280067 Number of ABIS_PACKET_CONNECT_FAIL_IND messages ..................................................................... 1952 C901280068 Number of ABIS_PACKET_PRACH_OVERLOAD messages ..................................................................... 1952 C901280069 Number of ABIS_PACKET_PCH_OVERLOAD messages ..................................................................... 1953 C901280070 Number of ABIS_PACKET_TA_REQUEST messages........................................................................... 1954 C901280071 Number of ABIS_PACKET_TA_REQUEST_ACK messages ..................................................................... 1954 C901280072 Number of ABIS_PACKET_CHN_CONFIG_CHG messages ..................................................................... 1955 C901280073 Number of ABIS_PACKET_CHN_CONFIG_CHG_RESP messages .............................................. 1956 C901280074 Number of ABIS_PACKET_PIA_DEL_IND messages........................................................................... 1956 C901280075 Number of ABIS_PACKET_SEND_PIA_IND messages........................................................................... 1957 C901280076 Number of ABIS_PACKET_CHN_CONFIG_REQ messages ..................................................................... 1958 C901280077 Number of ABIS_EGPRS_PACKET_CHN_REQ messages ..................................................................... 1958 C901280078 Number of ABIS_PS_CHANNEL_ACTIVE messages........................................................................... 1959 C901280079 Number of ABIS_PS_CHANNEL_ACTIVE_ACK messages ..................................................................... 1960 C901280080 Number of ABIS_PS_CHANNEL_ACTIVE_NACK messages ..................................................................... 1960 C901280081 Number of ABIS_PS_CHANNEL_RELEASE messages........................................................................... 1961 C901280082 Number of ABIS_PS_CHANNEL_RELEASE_ACK messages ..................................................................... 1962 C901280083 Number of ABIS_PS_CHANNEL_RELEASE_NACK messages ..................................................................... 1962 C901280084 Number of ABIS_PSCONN_CMM_REQ messages........................................................................... 1963 C901280085 Number of ABIS_PSCONN_CMM_ACK messages........................................................................... 1964 C901280086 Number of ABIS_PSCONN_CMM_NACK messages........................................................................... 1964 C901280087 Number of ABIS_GLOBAL_RESET messages........................................................................... 1965 C901280088 Number of ABIS_GLOBAL_RESET_ACK messages........................................................................... 1966 C901280089 Number of ABIS_GLOBAL_RESET_NACK messages........................................................................... 1966
1907
C901280090 Number of ABIS_PACKET_UP_ASSIGN messages........................................................................... 1967 C901280091 Number of ABIS_PACKET_DOWN_ASSIGN messages........................................................................... 1968 C901280092 Number of ABIS_CSCONN_CMM_REQ messages........................................................................... 1968 C901280093 Number of ABIS_CSCONN_CMM_ACK messages........................................................................... 1969 C901280094 Number of ABIS_CSCONN_CMM_NACK messages........................................................................... 1970 C901280095 Number of ABIS_CCMCONN_CMM_REQ messages........................................................................... 1970 C901280096 Number of ABIS_CCMCONN_CMM_ACK messages........................................................................... 1971 C901280097 Number of ABIS_CCMCONN_CMM_NACK messages........................................................................... 1972 C901280098 Number ABIS_PACKET_ACCESS_REJ messages........................................................................... 1972 C901280099 Number of ABIS_PACKET_IMM_ASSIGN_CMD_NEW messages ............................................ 1973 C901280100 Number of PACKET_DOWNLINK_ASSIGN messages........................................................................... 1974 C901280101 Number of PACKET_UPLINK_ASSIGN messages........................................................................... 1974 C901280102 Number of ABIS_PACKET_ACCESS_REJ_NEW messages ..................................................................... 1975
Overview
Abis interface message measurement is mainly for all kinds of messages of Abis interface to count. It is convenient to find out the frequency of all kinds of messages transmitting on Abis interface. When BSC receives the messages sent by BTS, the counter begin to count. The measurement point is A, as shown in Figure 1985.
FIGURE 1985 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
This counter accumulates before sending the message sent to BTS by BSC. The measurement point is A, as shown in Figure 1986.
1908
WHEN
Number of DATA REQUEST messages This counter counts the number of data request messages to be confirmed sent by BSC to LAPD. This counter is used to find out the frequency of data request message to be confirmed transmitting on Abis interface. This counter increments when BSC sends DATA REQuest message to BTS. The measurement point is A, as shown in Figure 1987.
FIGURE 1987 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1909
Number of DATA INDICATION messages This counter counts the number of data indication messages received by BSC on Abis interface. This counter is used to find out the frequency of data indication messages transmitting on Abis interface. This counter increments when BSC receives DATA INDication message. The measurement point is A, as shown in Figure 1988.
FIGURE 1988 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ERROR INDICATION messages 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. This counter is used to find out the frequency of error indication messages transmitting on Abis interface. This counter increments when BSC receives ERROR INDication message. The measurement point is A, as shown in Figure 1989.
1910
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ESTABLISH REQUEST messages 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. This counter is used to find out the frequency of Establish Request messages transmitting on Abis interface. This counter increments when BSC sends Establish Request message to BTS. The measurement point is A, as shown in Figure 1990.
FIGURE 1990 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1911
Number of ESTABLISH CONFIRM messages 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. This counter is used to find out the frequency of Establish Confirm messages transmitting on Abis interface. This counter increments when BSC receives Establish Confirm message. The measurement point is A, as shown in Figure 1991.
FIGURE 1991 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ESTABLISH INDICATION messages 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. This counter is used to find out the frequency of Establish Indication messages transmitting on Abis interface. This counter increments when BSC receives Establish Indication message. The measurement point is A, as shown in Figure 1992.
1912
ABIS
MESSAGE TO
BSC
Unit
Times
Number of RELEASE REQUEST messages 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. This counter is used to find out the frequency of Release Request messages transmitting on Abis interface. This counter increments when BSC sends Release Request message to BTS. The measurement point is A, as shown in Figure 1993.
FIGURE 1993 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1913
Number of RELEASE CONFIRM messages 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. This counter is used to find out the frequency of Release Confirm messages transmitting on Abis interface. This counter increments when BSC receives Release Confirm messages. The measurement point is A, as shown in Figure 1994.
FIGURE 1994 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of RELEASE INDICATION messages 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. This counter is used to find out the frequency of Release Indication messages transmitting on Abis interface. This counter increments when BSC receives Release Indication messages. The measurement point is A, as shown in Figure 1995.
1914
ABIS
MESSAGE TO
BSC
Unit
Times
Number of UNIT DATA REQUEST messages 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. This counter is used to find out the frequency of UNIT DATA REQUEST messages transmitting on Abis interface. This counter increments when BSC sends UNIT DATA REQUEST messages to BTS. The measurement point is A, as shown in Figure 1996.
FIGURE 1996 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1915
Number of UNIT DATA INDICATION messages 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. This counter is used to find out the frequency of UNIT DATA INDICATION messages transmitting on Abis interface. This counter increments when BSC receives UNIT DATA INDICATION messages. The measurement point is A, as shown in Figure 1997.
FIGURE 1997 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of CHANNEL ACTIVATION messages 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. This counter is used to find out the frequency of CHANNEL ACTIVATION messages transmitting on Abis interface. This counter increments when BSC sends CHANNEL ACTIVATION messages. The measurement point is A, as shown in Figure 1998.
1916
WHEN
Unit
Times
Number of CHANNEL ACTIVATION ACK messages 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. This counter is used to find out the frequency of CHANNEL ACTIVATION ACK messages transmitting on Abis interface. This counter increments when BSC receives CHANNEL ACTIVATION ACK messages. The measurement point is A, as shown in Figure 1999.
FIGURE 1999 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
1917
Number of CHANNEL ACTIVATION Negative ACK messages 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. This counter is used to find out the frequency of CHANNEL ACTIVATION Negative ACK messages transmitting on Abis interface. This counter increments when BSC receives CHANNEL ACTIVATION Negative ACK messages. The measurement point is A, as shown in Figure 2000.
FIGURE 2000 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of CONNECTION FAILURE INDICATION messages 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. This counter is used to find out the frequency of CONNECTION FAILURE INDICATION messages transmitting on Abis interface.
Usage
1918
Measurement Point
This counter increments when BSC receives CONNECTION FAILURE INDICATION messages. The measurement point is A, as shown in Figure 2001.
FIGURE 2001 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of DEACTIVATE SACCH messages 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. This counter is used to find out the frequency of DEACTIVATE SACCH messages transmitting on Abis interface. This counter increments when BSC receives DEACTIVATE SACCH messages. The measurement point is A, as shown in Figure 2002.
FIGURE 2002 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1919
Number of ENCRYPTION COMMAND messages BSC initiate ENCRYPTION COMMAND message to require encryption. This counter counts the number of ENCRYPTION COMMAND messages sent by BSC to LAPD. This counter is used to find out the frequency of ENCRYPTION COMMAND messages transmitting on Abis interface. This counter increments when BSC sends ENCRYPTION COMMAND messages to BTS. The measurement point is A, as shown in Figure 2003.
FIGURE 2003 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
Number of HANDOVER DETECTION messages 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. This counter is used to find out the frequency of HANDOVER DETCTION messages transmitting on Abis interface.
Usage
1920
Measurement Point
This counter increments when BSC receives HANDOVER DETCTION messages. The measurement point is A, as shown in Figure 2004.
FIGURE 2004 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of MEASUREMENT RESULT messages In general, MS reports a measurement report ( Um interface message MEASUREMENT messages) to BTS per 102/104 multi-frame through SACCH channel, including DL measurement information from 102/104 multi-frame. During the period BTS are also under DL measurement. Therefore every 102/104 multi-frame, BTS will combine these two information together, send to BSC through Abis message MEASUREMENT RESULT. For some reasons, BTS does not receive the MS measurement report on time, only put its UL measurement results into this MEASUREMENT RESULTS messages to send to BSC. This counter counts the number of MEASUREMENT RESULTS messages of Abis interface messages received by BSC.
This counter is used to find out the frequency of MEASUREMENT RESULTS messages transmitting on Abis interface. This counter increments when BSC receives MEASUREMENT RESULTS messages. The measurement point is A, as shown in Figure 2005.
1921
ABIS
MESSAGE TO
BSC
Unit
Times
Number of MODE MODIFY REQUEST messages 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. This counter is used to find out the frequency of MODE MODIFY REQUEST messages transmitting on Abis interface. This counter increments when BSC sends MODE MODIFY REQUEST messages to BTS. The measurement point is A, as shown in Figure 2006.
FIGURE 2006 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1922
Number of MODE MODIFY ACK messages 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. This counter is used to find out the frequency of MODE MODIFY ACK messages transmitting on Abis interface. This counter increments when BSC receives MODE MODIFY ACK messages. The measurement point is A, as shown in Figure 2007.
FIGURE 2007 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of MODE MODIFY NACK messages 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. This counter is used to find out the frequency of MODE MODIFY NACK messages transmitting on Abis interface. This counter increments when BSC receives MODE MODIFY NACK messages. The measurement point is A, as shown in Figure 2008.
1923
ABIS
MESSAGE TO
BSC
Unit
Times
Number of PHYSICAL CONTEXT REQUEST messages 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. This counter is used to find out the frequency of PHYSICAL CONTEXT REQUEST messages transmitting on Abis interface. This counter increments when BSC sends PHYSICAL CONTEXT REQUEST messages to BTS. The measurement point is A, as shown in Figure 2009.
FIGURE 2009 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1924
Number of PHYSICAL CONTEXT CONFIRM messages 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. This counter is used to find out the frequency of PHYSICAL CONTEXT COMFIRM messages transmitting on Abis interface. This counter increments when BSC receives PHYSICAL CONTEXT COMFIRM messages to BTS. The measurement point is A, as shown in Figure 2010.
FIGURE 2010 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of RF CHANNEL RELEASE messages 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. This counter is used to find out the frequency of RF CHANNEL RELEASE messages transmitting on Abis interface.
Usage
1925
Measurement Point
This counter increments when BSC sends RF CHANNEL RELEASE messages to BTS. The measurement point is A, as shown in Figure 2011.
FIGURE 2011 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
Number of MS POWER CONTROL messages 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. This counter is used to find out the frequency of MS POWER CONTROL messages transmitting on Abis interface. This counter increments when BSC sends MS POWER CONTROL messages to BTS. The measurement point is A, as shown in Figure 2012.
FIGURE 2012 MEASUREMENT POINT TO BTS
WHEN
1926
Unit
Times
Number of BS POWER CONTROL messages 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. This counter is used to find out the frequency of BS POWER CONTROL messages transmitting on Abis interface. This counter increments when BSC sends BS POWER CONTROL messages to BTS. The measurement point is A, as shown in Figure 2013.
FIGURE 2013 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
Number of PREPROCESSED CONFIGURE messages In order to reduce the load of processed measurement report of BSC and the messages flux of Abis interface, the process of preprocessed measurement report can be used. First BTS processes the
1927
102/104 multi-frame measurement data (average), then sends the processed result to BSC at lower frequency. To make BTS conduct preprocessed measurement report, first BSC sends PREPROCESSED CONFIGURE messages to BTS. The message includes some basic control parameters being processed. This counter counts the number of PREPROCESSED CONFIGURE messages of Abis interface messages sent by BSC.
Usage Measurement Point
This counter is used to find out the frequency of PREPROCESSED CONFIGURE messages transmitting on Abis interface. This counter increments when BSC sends PREPROCESSED CONFIGURE messages to BTS. The measurement point is A, as shown in Figure 2014.
FIGURE 2014 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
Number of PREPROCESSED MEASUREMENT RESULT messages 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. This counter is used to find out the frequency of PREPROCESSED MEASUREMENT RESULT messages transmitting on Abis interface. This counter increments when BSC receives PREPROCESSED MEASUREMENT RESULT messages to BTS. The measurement point is A, as shown in Figure 2015.
1928
ABIS
MESSAGE TO
BSC
Unit
Times
Number of RF CHANNEL RELEASE ACK messages 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. This counter is used to find out the frequency of RF CHANNEL RELEASE ACK messages transmitting on Abis interface. This counter increments when BSC receives RF CHANNEL RELEASE ACK messages to BTS. The measurement point is A, as shown in Figure 2016.
FIGURE 2016 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
1929
Number of SACCH INFO MODIFY messages 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. This counter is used to find out the frequency of SACCH INFO MODIFY messages transmitting on Abis interface. This counter increments when BSC sends SACCH INFO MODIFY messages to BTS. The measurement point is A, as shown in Figure 2017.
FIGURE 2017 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
Number of ABIS_PREPROC_ENHANCEMEAS_RESULT messages This counter counts the number of ABIS_PREPROC_ENHANCEMEAS_RESULT messages received by BSC.
1930
Usage
This counter is used to find out the frequency of enhanced preprocessed measurement report message transmitting on Abis interface. This counter increments when BSC receives ABIS_PREPROC_ENHANCEMEAS_RESULT messages. The measurement point is A, as shown in Figure 2018.
FIGURE 2018 BTS
SENDS MEASUREMENT POINT OF
Measurement Point
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_ROUND_TRIP_DELAY_REPORT messages This counter counts the number of ABIS_ROUND_TRIP_DELAY_REPORT messages received by BSC. This counter is used to find out the frequency of ROUND TRIP DELAY REPORT messages transmitting on Abis interface. This counter increments when BSC receives ROUND TRIP DELAY REPORT messages. The measurement point is A, as shown in Figure 2019.
FIGURE 2019 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
1931
Number of ABIS_PRE_HO_NOTIFY messages This counter counts the number of ABIS_PRE_HO_NOTIFY messages received by BSC. This counter is used to find out the frequency of PRE_HO_NOTIFY messages transmitting on Abis interface. This counter increments when BSC sends PRE-HANDOVER NOFICATION messages. The measurement point is A, as shown in Figure 2020.
FIGURE 2020 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
Number of ABIS_BCCH_INFO messages 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. This counter is used to find out the frequency of BCCH changing messages transmitting on Abis interface. This counter increments when BSC sends BCCH INFOMATION messages. The measurement point is A, as shown in Figure 2021.
1932
WHEN
Unit
Times
Number of ABIS_CCCH_LOAD_IND messages 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. This counter is used to find out the frequency of CCCH load indication messages transmitting on Abis interface. This counter increments when BSC receives CCCH LOAD INDICATION messages. The measurement point is A, as shown in Figure 2022.
FIGURE 2022 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
1933
Number of ABIS_CHL_RQD messages 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. This counter is used to find out the frequency of data indication messages transmitting on Abis interface. This counter increments when BSC receives CHANNEL REQUIRED messages. The measurement point is A, as shown in Figure 2023.
FIGURE 2023 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_DELETE_IND messages 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. This counter is used to find out the frequency of DELETE INDICATION messages transmitting on Abis interface. This counter increments when BSC receives DELETE INDICATION messages. The measurement point is A, as shown in Figure 2024.
1934
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PAGING_CMD messages 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. This counter is used to find out the frequency of PAGING COMMAND messages transmitting on Abis interface. This counter increments when BSC sends PAGING COMMAND messages to BTS. The measurement point is A, as shown in Figure 2025.
FIGURE 2025 MEASUREMENT POINT TO BTS
WHEN
1935
Number of ABIS_IMM_ASSIGN_CMD messages After BSC receives MS channel request, it tries for assigning one channel accordingly and activates the channel, then sends one IMMEDIATE ASSIGN COMMAND message to BTS. This message includes one complete Um interface RR layer IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED or IMMEDIATE ASSIGNMENT REJECT (if there is no channel) to notify MS. After BTS receives this message, it is in charge of assigning Um interface RR layer message of the message on CCCH to MS. This counter counts the number of ABIS_IMM_ASSIGN_CMD messages sent by BSC.
This counter is used to find out the frequency of IMMEDIATE ASSIGN COMMAND messages transmitting on Abis interface. This counter increments when BSC sends IMMEDIATE ASSIGN COMMAND messages to BTS. The measurement point is A, as shown in Figure 2026.
FIGURE 2026 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
Number of ABIS_SMS_BROADCAST_REQ messages This counter counts the number of ABIS_SMS_BROADCAST_REQ messages sent by BSC.
1936
This counter is used to find out the frequency of SMS BROADCAST REQUEST messages transmitting on Abis interface. This counter increments when BSC sends SMS BROADCAST REQUEST messages to BTS. The measurement point is A, as shown in Figure 2027.
FIGURE 2027 MEASUREMENT POINT TO BTS
WHEN
Number of ABIS_SMS_BROADCAST_CMD messages This counter counts the number of ABIS_SMS_BROADCAST_CMD messages sent by BSC. This counter is used to find out the frequency of SMS BROADCAST COMMAND messages transmitting on Abis interface. This counter increments when BSC sends MS BROADCAST COMMAND messages to BTS. The measurement point is A, as shown in Figure 2028.
FIGURE 2028 MEASUREMENT POINT TO BTS
WHEN
1937
Number of ABIS_CBCH_LOAD_IND messages 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. This counter is used to find out the frequency of CBCH LOAD INDICATION messages transmitting on Abis interface. This counter increments when BSC receives CBCH LOAD INDICATION messages to BTS. The measurement point is A, as shown in Figure 2029.
FIGURE 2029 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_EGPRS_CHL_REQ messages This counter counts the number of ABIS_EGPRS_CHL_REQ messages sent by BSC. This counter is used to find out the frequency of EGPRS_CHL_REQ messages transmitting on Abis interface.
1938
Measurement Point
This counter increments when BSC receives ABIS_EGPRS_CHL_REQ messages. The measurement point is A, as shown in Figure 2030.
FIGURE 2030 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_LOAD_CONTROL messages 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. This counter is used to find out the frequency of CCCHLOAD INDICATION messages transmitting on Abis interface. This counter increments when BSC receives CCCHLOAD INDICATION messages. The measurement point is A, as shown in Figure 2031.
FIGURE 2031 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
1939
Number of ABIS_END_LOAD_CONTROL messages This counter counts the number of ABIS_END_LOAD_CONTROL messages sent by BSC. This counter is used to find out the frequency of END LOAD CONTROL messages transmitting on Abis interface. This counter increments when BSC sends ABIS_END_LOAD_CONTROL messages to BTS. The measurement point is A, as shown in Figure 2032.
FIGURE 2032 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
Number of ABIS_END_LOAD_CONTROL_ACK messages This counter counts the number of ABIS_END_LOAD_CONTROL_ACK messages received by BSC. This counter is used to find out the frequency of END LOAD CONTROL RETURN messages transmitting on Abis interface. This counter increments when BSC receives ABIS_END_LOAD_CONTROL_ACK messages to BTS. The measurement point is A, as shown in Figure 2033.
1940
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PCCCH_LOAD_IND messages This counter counts the number of PCCH flow control control command messages of Abis interface messages received by BSC. This counter is used to find out the frequency of PCCH flow control control command messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PCCCH_LOAD_CONTROL_IND messages to BTS. The measurement point is A, as shown in Figure 2034.
FIGURE 2034 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
1941
Number of ABIS_RF_RESRC_IND messages 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. This counter is used to find out the frequency of RF RESOURCE INDICATION messages transmitting on Abis interface. This counter increments when BSC receives RF RESOURCE INDICATION messages. The measurement point is A, as shown in Figure 2035.
FIGURE 2035 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_SACCH_FILLING messages 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. This counter is used to find out the frequency of SACCH FILLING INFORMATION CHANGE messages transmitting on Abis interface. This counter increments when BSC sends SACCH FILLING messages. The measurement point is A, as shown in Figure 2036.
1942
WHEN
Unit
Times
Number of ABIS_OVERLOAD messages This counter counts the number of flow control messages of Abis interface messages received by BSC. This counter is used to find out the frequency of flow control messages transmitting on Abis interface. This counter increments when BSC receives overload messages. The measurement point is A, as shown in Figure 2037.
FIGURE 2037 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
1943
Number of ABIS_ERROR_REPORT messages 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. This counter is used to find out the frequency of error report messages transmitting on Abis interface. This counter increments when BSC receives error report messages. The measurement point is A, as shown in Figure 2038.
FIGURE 2038 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_SYSINFO_REQ messages This counter counts the number of ABIS_SYSINFO_REQ messages received by BSC. This counter is used to find out the frequency of systems information requirement messages transmitting on Abis interface. This counter increments when BSC receives ABIS_SYSINFO_REQ messages. The measurement point is A, as shown in Figure 2039.
1944
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_SI_BC_END messages This counter counts the number of ABIS_SI_BC_END indication messages sent by BSC. This counter is used to find out the frequency of systems information broadcast end indication messages transmitting on Abis interface. This counter increments when BSC sends ABIS_SI_BC_END messages to BTS. The measurement point is A, as shown in Figure 2040.
FIGURE 2040 MEASUREMENT POINT TO BTS
WHEN
Measurement Point
Unit
Times
1945
Number of ABIS_SI_NACK messages This counter counts the number of ABIS_SI_NACK messages received by BSC. This counter is used to find out the frequency of SI_NACK messages transmitting on Abis interface. This counter increments when BSC receives ABIS_SI_NACK messages to BTS. The measurement point is A, as shown in Figure 2041.
FIGURE 2041 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PWRCTRL_IND messages This counter counts the number of ABIS_PWRCTRL_IND messages received by BSC. This counter is used to find out the frequency of POWER CONTROL INDICATION messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PWRCTRL_IND messages. The measurement point is A, as shown in Figure 2042.
1946
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_SYSINFO_ACK messages This counter counts the number of ABIS_SYSINFO_ACK messages received by BSC. This counter is used to find out the frequency of SYSTEM INFORMATION ACKNOWLEDGE messages transmitting on Abis interface. This counter increments when BSC receives ABIS_SYSINFO_ACK messages. The measurement point is A, as shown in Figure 2043.
FIGURE 2043 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
1947
Number of ABIS_PACKET_PBCCH_INF messages This counter counts the number of ABIS_PACKET_PBCCH_INF messages received by BSC. This counter is used to find out the frequency of PACKET PBCCH INFORMATION messages transmitting on Abis interface. This counter increments when BSC sends ABIS_PACKET_PBCCH_INF messages. The measurement point is A, as shown in Figure 2044.
FIGURE 2044 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
Number of ABIS_PACKET_CCCH_PARA messages This counter counts the number of ABIS_PACKET_CCCH_PARA messages sent by BSC. This counter is used to find out the frequency of CCCH INFORMATION messages transmitting on Abis interface. This counter increments when BSC sends ABIS_PACKET_CCCH_PARA messages. The measurement point is A, as shown in Figure 2045.
1948
WHEN
Unit
Times
Number of ABIS_PACKET_PBCCH_PARA messages This counter counts the number of ABIS_PACKET_PBCCH_PARA messages sent by BSC. This counter is used to find out the frequency of PBCCH PATAMETER messages transmitting on Abis interface. This counter increments when BSC sends ABIS_PACKET_PBCCH_ PARA messages to BTS. The measurement point is A, as shown in Figure 2046.
FIGURE 2046 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1949
Number of ABIS_PACKET_CHN_REQ messages This counter counts the number of ABIS_PACKET_CHN_REQ messages received by BSC. This counter is used to find out the frequency of UL PACKET CHANNEL REQUIREMENT messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PACKET_CHN_ REQ messages to BTS. The measurement point is A, as shown in Figure 2047.
FIGURE 2047 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PACKET_PAGING_CMD messages This counter counts the number of ABIS_PACKET_PAGING_CMD messages received by BSC. This counter is used to find out the frequency of PACKET PAGING COMMAND messages transmitting on Abis interface. This counter increments when BSC sends ABIS_PACKET_PAGING_CMD messages to BTS. The measurement point is A, as shown in Figure 2048.
1950
WHEN
Number of ABIS_PACKET_IMM_ASSIGN_CMD messages This counter counts the number of PACKET IMMEDIATE ASSIGNMENT messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of PACKET IMMEDIATE ASSIGNMENT messages transmitting on Abis interface. This counter increments when BSC sends ABIS_PACKET_IMM_ASSIGN_CMD messages to BTS. The measurement point is A, as shown in Figure 2049.
FIGURE 2049 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1951
Number of ABIS_PACKET_CONNECT_FAIL_IND messages This counter counts the number of PACKET CONNECT FAILURE INDICATION messages of Abis interface messages received by BSC. This counter is used to find out the frequency of PACKET CONNECT FAILURE INDICATION messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PACKET_CONNECT_FAIL_IND messages to BTS. The measurement point is A, as shown in Figure 2050.
FIGURE 2050 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PACKET_PRACH_OVERLOAD messages This counter counts the number of PRACH OVERLOAD messages of Abis interface messages received by BSC. This counter is used to find out the frequency of PRACH OVERLOAD messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PACKET_PRACH_OVERLOAD messages. The measurement point is A, as shown in Figure 2051.
1952
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PACKET_PCH_OVERLOAD messages This counter counts the number of PCH OVERLOAD messages of Abis interface messages received by BSC. This counter is used to find out the frequency of PCH OVERLOAD messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PACKET_PCH_ OVERLOAD messages. The measurement point is A, as shown in Figure 2052.
FIGURE 2052 BTS
SENDS MEASUREMENT POINT OF
ABIS
MESSAGE TO
BSC
Unit
Times
1953
Number of ABIS_PACKET_TA_REQUEST messages This counter counts the number of TIME ADVANCE REQUEST messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of TIME ADVANCE REQUEST messages transmitting on Abis interface. This counter increments when BSC sends ABIS_PACKET_TA_REQUEST messages. The measurement point is A, as shown in Figure 2053.
FIGURE 2053 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
Number of ABIS_PACKET_TA_REQUEST_ACK messages This counter counts the number of TIME ADVANCE REQUEST ACKNOWLEDGE messages of Abis interface messages received by BSC. This counter is used to find out the frequency of TIME ADVANCE REQUEST ACKNOWLEDGE messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PACKET_TA_REQUEST_ACK messages. The measurement point is A, as shown in Figure 2054.
Usage
Measurement Point
1954
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PACKET_CHN_CONFIG_CHG messages This counter counts the number of CHANNEL CONFIGURATION CHANGE messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of CHANNEL CONFIGURATION CHANGE messages transmitting on Abis interface. This counter increments when BSC sends ABIS_PACKET_CHG_CONFIG_CHG messages. The measurement point is A, as shown in Figure 2055.
FIGURE 2055 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1955
Number of ABIS_PACKET_CHN_CONFIG_CHG_RESP messages This counter counts the number of CHANNEL CONFIGURATION CHANGE RESPONSE messages of Abis interface messages received by BSC. This counter is used to find out the frequency of CHANNEL CONFIGURATION CHANGE RESPONSE messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PACKET_CHG_CONFIG_CHG_RESP messages. The measurement point is A, as shown in Figure 2056.
FIGURE 2056 BTS
SENDS MEASUREMENT POINT OF
Usage
Measurement Point
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PACKET_PIA_DEL_IND messages This counter counts the number of IMMEDIATE ASSIGNMENT TRANSMISSION FAILURE INDICATION messages of Abis interface messages received by BSC. This counter is used to find out the frequency of IMMEDIATE ASSIGNMENT TRANSMISSION FAILURE INDICATION messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PACKET_PIA_DEL_IND messages. The measurement point is A, as shown in Figure 2057.
Usage
Measurement Point
1956
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PACKET_SEND_PIA_IND messages This counter counts the number of IMMEDIATE ASSIGNMENT TRANSMISSION SUCCESS INDICATION messages of Abis interface messages received by BSC. This counter is used to find out the frequency of IMMEDIATE ASSIGNMENT TRANSMISSION SUCCESS INDICATION messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PACKET_SEND_PIA_IND messages. The measurement point is A, as shown in Figure 2058.
FIGURE 2058 BTS
SENDS MEASUREMENT POINT OF
Usage
Measurement Point
ABIS
MESSAGE TO
BSC
Unit
Times
1957
Number of ABIS_PACKET_CHN_CONFIG_REQ messages This counter counts the number of PS PARAMETER CONFIGURATION REQUEST messages of Abis interface messages received by BSC. This counter is used to find out the frequency of PS PARAMETER CONFIGURATION REQUEST messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PACKET_CHN_ CONFIG_REQ messages. The measurement point is A, as shown in Figure 2059.
FIGURE 2059 BTS
SENDS MEASUREMENT POINT OF
Usage
Measurement Point
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_EGPRS_PACKET_CHN_REQ messages This counter counts the number of UL EGPRS PACKET REQUEST messages of Abis interface messages received by BSC. This counter is used to find out the frequency of UL EGPRS PACKET REQUEST messages transmitting on Abis interface. This counter increments when BSC receives ABIS_EGPRS_PACKET _CHN_REQ messages. The measurement point is A, as shown in Figure 2060.
1958
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PS_CHANNEL_ACTIVE messages This counter counts the number of PS CHANNEL ACTIVE COMMAND messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of PS CHANNEL ACTIVE COMMAND messages transmitting on Abis interface. This counter increments when BSC sends ABIS_PS_CHANNEL _ACTIVE messages. The measurement point is A, as shown in Figure 2061.
FIGURE 2061 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1959
Number of ABIS_PS_CHANNEL_ACTIVE_ACK messages This counter counts the number of PS CHANNEL ACTIVE ACKNOWLEDGEMENT COMMAND messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of PS CHANNEL ACTIVE ACKNOWLEDGEMENT COMMAND messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PS_CHANNEL _ACTIVE_ACK messages. The measurement point is A, as shown in Figure 2062.
FIGURE 2062 BTS
SENDS MEASUREMENT POINT OF
Usage
Measurement Point
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PS_CHANNEL_ACTIVE_NACK messages This counter counts the number of PS CHANNEL ACTIVE UNACKNOWLEDGEMENT COMMAND messages of Abis interface messages received by BSC. This counter is used to find out the frequency of PS CHANNEL ACTIVE UNACKNOWLEDGEMENT COMMAND messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PS_CHANNEL _ACTIVE_NACK messages. The measurement point is A, as shown in Figure 2063.
Usage
Measurement Point
1960
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PS_CHANNEL_RELEASE messages This counter counts the number of PS CHANNEL RELEASE COMMAND messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of PS CHANNEL RELEASE COMMAND messages transmitting on Abis interface. This counter increments when BSC sends ABIS_PS_CHANNEL_RELEASE messages to BTS. The measurement point is A, as shown in Figure 2064.
FIGURE 2064 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1961
Number of ABIS_PS_CHANNEL_RELEASE_ACK messages This counter counts the number of PS CHANNEL RELEASE ACKNOWLEDGEMENT COMMAND messages of Abis interface messages received by BSC. This counter is used to find out the frequency of PS CHANNEL RELEASE ACKNOWLEDGEMENT COMMAND messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PS_CHANNEL_RELEASE_ACK messages. The measurement point is A, as shown in Figure 2065.
FIGURE 2065 BTS
SENDS MEASUREMENT POINT OF
Usage
Measurement Point
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PS_CHANNEL_RELEASE_NACK messages This counter counts the number of PS CHANNEL RELEASE UNACKNOWLEDGEMENT COMMAND messages of Abis interface messages received by BSC. This counter is used to find out the frequency of PS CHANNEL RELEASE UNACKNOWLEDGEMENT COMMAND messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PS_CHANNEL_RELEASE_NACK messages. The measurement point is A, as shown in Figure 2066.
Usage
Measurement Point
1962
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PSCONN_CMM_REQ messages This counter counts the number of PS CONNECTION COMMAND messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of PS CONNECTION COMMAND messages transmitting on Abis interface. This counter increments when BSC sends ABIS_PSCONN_CMM_ REQ messages to BTS. The measurement point is A, as shown in Figure 2067.
FIGURE 2067 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1963
Number of ABIS_PSCONN_CMM_ACK messages This counter counts the number of PS CONNECTION SUCCESS COMMAND ACKNOWLEDGEMENT messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of PS CONNECTION SUCCESS COMMAND ACKNOWLEDGEMENT messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PSCONN_CMM_ACK messages. The measurement point is A, as shown in Figure 2068.
FIGURE 2068 BTS
SENDS MEASUREMENT POINT OF
Usage
Measurement Point
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PSCONN_CMM_NACK messages This counter counts the number of PS CONNECTION FAILURE COMMAND ACKNOWLEDGEMENT messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of PS CONNECTION FAILURE COMMAND ACKNOWLEDGEMENT messages transmitting on Abis interface. This counter increments when BSC receives ABIS_PSCONN_CMM_ NACK messages. The measurement point is A, as shown in Figure 2069.
Usage
Measurement Point
1964
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_GLOBAL_RESET messages This counter counts the number of GLOBAL RESET COMMAND messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of GLOBAL RESET COMMAND messages transmitting on Abis interface. This counter increments when BSC sends ABIS_GLOBAL_RESET messages to BTS. The measurement point is A, as shown in Figure 2070.
FIGURE 2070 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1965
Number of ABIS_GLOBAL_RESET_ACK messages This counter counts the number of GLOBAL RESET ACKNOWLEDGEMENT COMMAND messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of GLOBAL RESET ACKNOWLEDGEMENT COMMAND messages transmitting on Abis interface. This counter increments when BSC receives ABIS_GLOBAL_RESET_ACK messages. The measurement point is A, as shown in Figure 2071.
FIGURE 2071 BTS
SENDS MEASUREMENT POINT OF
Usage
Measurement Point
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_GLOBAL_RESET_NACK messages This counter counts the number of GLOBAL RESET UNACKNOWLEDGEMENT COMMAND messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of GLOBAL RESET UNACKNOWLEDGEMENT COMMAND messages transmitting on Abis interface. This counter increments when BSC receives ABIS_GLOBAL_RESET_NACK messages. The measurement point is A, as shown in Figure 2072.
Usage
Measurement Point
1966
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_PACKET_UP_ASSIGN messages This counter counts the number of PS UL ASSIGNMENT COMMAND messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of PS UL ASSIGNMENT COMMAND messages transmitting on Abis interface. This counter increments when BSC sends ABIS_PACKET_UP_ASSIGN messages to BTS. The measurement point is A, as shown in Figure 2073.
FIGURE 2073 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1967
Number of ABIS_PACKET_DOWN_ASSIGN messages This counter counts the number of PS DL ASSIGNMENT COMMAND messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of PS DL ASSIGNMENT COMMAND messages transmitting on Abis interface. This counter increments when BSC sends ABIS_PACKET_DOWN_ ASSIGN messages to BTS. The measurement point is A, as shown in Figure 2074.
FIGURE 2074 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
Number of ABIS_CSCONN_CMM_REQ messages This counter counts the number of CS CONNECTION COMMAND messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of CS CONNECTION COMMAND messages transmitting on Abis interface. This counter increments when BSC sends ABIS_CSCONN_CMM_ REQ messages to BTS. The measurement point is A, as shown in Figure 2075.
1968
WHEN
Unit
Times
Number of ABIS_CSCONN_CMM_ACK messages This counter counts the number of CS CONNECTION SUCCESS COMMAND ACKNOWLEDGEMENT messages of Abis interface messages received by BSC. This counter is used to find out the frequency of CS CONNECTION SUCCESS COMMAND ACKNOWLEDGEMENT messages transmitting on Abis interface. This counter increments when BSC receives ABIS_CSCONN_CMM_ACK messages. The measurement point is A, as shown in Figure 2076.
FIGURE 2076 BTS
SENDS MEASUREMENT POINT OF
Usage
Measurement Point
ABIS
MESSAGE TO
BSC
Unit
Times
1969
Number of ABIS_CSCONN_CMM_NACK messages This counter counts the number of CS CONNECTION FAILURE COMMAND ACKNOWLEDGEMENT messages of Abis interface messages received by BSC. This counter is used to find out the frequency of CS CONNECTION FAILURE COMMAND ACKNOWLEDGEMENT messages transmitting on Abis interface. This counter increments when BSC receives ABIS_CSCONN_CMM_ NACK messages. The measurement point is A, as shown in Figure 2077.
FIGURE 2077 BTS
SENDS MEASUREMENT POINT OF
Usage
Measurement Point
ABIS
MESSAGE TO
BSC
Unit
Times
Number of ABIS_CCMCONN_CMM_REQ messages This counter counts the number of CCM CONNECTION COMMAND messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of CCM CONNECTION COMMAND messages transmitting on Abis interface. This counter increments when BSC sends ABIS_CCMCONN_CMM_REQ messages to BTS. The measurement point is A, as shown in Figure 2078.
1970
WHEN
Unit
Times
Number of ABIS_CCMCONN_CMM_ACK messages This counter counts the number of CCM CONNECTION SUCCESS COMMAND ACKNOWLEDGEMENT messages of Abis interface messages received by BSC. This counter is used to find out the frequency of CCM CONNECTION SUCCESS COMMAND ACKNOWLEDGEMENT messages transmitting on Abis interface. This counter increments when BSC receives ABIS_CCMCONN_CMM_ACK messages. The measurement point is A, as shown in Figure 2079.
FIGURE 2079 BTS
SENDS MEASUREMENT POINT OF
Usage
Measurement Point
ABIS
MESSAGE TO
BSC
Unit
Times
1971
Number of ABIS_CCMCONN_CMM_NACK messages This counter counts the number of CCM CONNECTION FAILURE COMMAND ACKNOWLEDGEMENT messages of Abis interface messages received by BSC. This counter is used to find out the frequency of CCM CONNECTION FAILURE COMMAND ACKNOWLEDGEMENT messages transmitting on Abis interface. This counter increments when BSC receives ABIS_CCMCONN_CMM_NACK messages. The measurement point is A, as shown in Figure 2080.
FIGURE 2080 BTS
SENDS MEASUREMENT POINT OF
Usage
Measurement Point
ABIS
MESSAGE TO
BSC
Unit
Times
Number ABIS_PACKET_ACCESS_REJ messages This counter counts the number of PS ACCESS REJECT messages of Abis interface messages sent by BSC. This counter is used to find out the frequency of PS ACCESS REJECT messages transmitting on Abis interface. This counter increments when BSC sends ABIS_PACKET_ACCESS_REJ messages to BSC. The measurement point is A, as shown in Figure 2081.
1972
WHEN
Unit
Times
Number of ABIS_PACKET_IMM_ASSIGN_CMD_NEW messages This counter counts the number of new packet immediate assignment messages in the Abis interface messages sent by BSC. The counter is used to find out the frequency of new packet immediate assignment messages transmitted at Abis interface. 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 2082.
FIGURE 2082 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1973
Number of PACKET_DOWNLINK_ASSIGN messages This counter counts the number of packet downlink assignment messages in the Abis interface messages sent by BSC. The counter is used to find out the frequency of packet downlink assignment messages transmitted at Abis interface. When BSC sends the PACKET_DOWNLINK_ASSIGN message to BTS, the counter increments. The measurement point is A, as shown in Figure 2083.
FIGURE 2083 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
Number of PACKET_UPLINK_ASSIGN messages This counter counts the number of packet uplink assignment messages in the Abis interface messages sent by BSC. The counter is used to find out the frequency of packet uplink assignment messages transmitted at Abis interface. When BSC sends the PACKET_UPLINK_ASSIGN message to BTS, the counter increments. The measurement point is A, as shown in Figure 2084.
1974
WHEN
Unit
Times
Number of ABIS_PACKET_ACCESS_REJ_NEW messages This counter counts the number of new PS access reject messages in the Abis interface messages sent by BSC. The counter is used to find out the frequency of new PS access reject messages transmitted at Abis interface. When BSC sends the ABIS_PACKET_ACCESS_REJ_NEW message to BTS, the counter increments. The measurement point is A, as shown in Figure 2085.
FIGURE 2085 MEASUREMENT POINT TO BTS
WHEN
Unit
Times
1975
1976
Chapter
35
1977
C901290022 Number of Status messages sent with protocol error............................................................................ 1991 C901290023 Number of Status messages sent with Processor overload....................................................................... 1991 C901290024 Number of Status messages received with BVCI Unknown...................................................................... 1991 C901290025 Number of Status messages received with Cell service congestion ......................................................... 1992 C901290026 Number of Status messages received with protocol error .................................................................... 1992 C901290027 Number of Status messages received with Processor overload ............................................................. 1992 C901290028 Number of DOWNLOAD-BSS-PFC messages sent by BSC......................................................................... 1993 C901290029 Number of BVCCREATE-BSS-PFC messages received by BSC............................................................... 1993 C901290030 Number of CREATE-BSS-PFC-ACK messages sent by BSC.................................................................. 1994 C901290031 Number of CREATE-BSS-PFC-NACK messages sent by BSC.................................................................. 1995 C901290032 Number of MODIFY-BSS-PFC messages sent by BSC ............................................................................. 1995 C901290033 Number of MODIFY-BSS-PFC-ACK messages received by BSC............................................................... 1996 C901290034 Number of DELETE-BSS-PFC messages received by BSC......................................................................... 1997 C901290035 Number of DELETE -BSS-PFC-ACK messages sent by BSC.................................................................. 1997 C901290036 Number of DELETE -BSS-PFC-REQ messages received by BSC............................................................... 1998
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.
Sum of UL UNITDATA messages handled at BSSGP level This counter counts the number of sending UL-UNITDATA PDU to SGSN by BSC. When BSC sends a UL-UNITDATA message, this counter increments. The measurement point is A, as shown in Figure 2086.
1978
UL UNITDATA
MESSAGE
Unit
Times
Sum of DL UNITDATA messages handled at BSSGP level SGSN sends DL-UNITDATA PDU to BSC, and this counter counts the number of receiving this message by BSC. When BSC receives a DL-UNITDATA message, this counter increments. The measurement point is A, as shown in Figure 2087.
FIGURE 2087 MEASUREMENT HANDLED AT BSSGP LEVEL
POINT OF SUM OF
DL UNITDATA
MESSAGE
Unit
Times
1979
Number of RA-CAPABILITY message received SGSN sends RA-CAPABILITY message to BSC, to indicate wireless capability of MS. This counter counts the number of receiving this message. When BSC receives a RA-CAPABILITY message, this counter increments. The measurement point is A, as shown in Figure 2088.
FIGURE 2088 MEASUREMENT
MESSAGE RECEIVED POINT OF THE NUMBER OF
Measurement Point
RA-CAPABILITY
Unit
Times
Number of PTP packet paging received by BSC 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. When BSC receives a PAGING PS message, this counter increments. The measurement point is A, as shown in Figure 2089.
Measurement Point
1980
Unit
Times
Number of PTP circuit paging received by BSC 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. When BSC receives a PAGING CS message, this counter increments. The measurement point is A, as shown in Figure 2090.
FIGURE 2090 PTP CIRCUIT PAGING PROCESS
Measurement Point
Unit
Times
1981
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. When BSC sends a RA-CAPABILITY-UPDATE message to SGSN, this counter increments. The measurement point is A1, as shown in Figure 2091.
FIGURE 2091 RA-CAPABILITY-UPDATE PROCESS
Measurement Point
Unit
Times
Number of RA-CAPABILITY-UPDATE-ACK message received 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. When BSC sends a RA-CAPABILITY-UPDATE-ACK message from SGSN, this counter increments. The measurement point is A2, as shown in Figure 2092.
FIGURE 2092 RA-CAPABILITY-UPDATE PROCESS
Measurement Point
Unit
Times
1982
Number of Wireless Status PDU messages sent by BSC BSC sends wireless status PDU message, to indicate exception at SGSN radio interface. This counter counts the number of sending this message by BSC. View the status at radio interface by counting this message. When BSC sends a RADIO-STATUS message to SGSN, this counter increments. The measurement point is A, as shown in Figure 2093.
FIGURE 2093 RADIO-STATUS PROCESS
Unit
Times
C901290009 Number of Wireless Status messages sent by BSC due to Losing Wireless Association with MS
Definition Description
Number of Wireless Status messages sent by BSC due to Losing Wireless Association with MS 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. View the status at radio interface by counting this message. When BSC sends a RADIO-STATUS message due to Losing wireless association with MS, this counter increments.
1983
Unit
Times
C901290010 Number of wireless status messages sent by BSC due to Bad Link Quality
Definition Description
Number of wireless status messages sent by BSC due to Bad Link Quality 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. View the status at radio interface by counting this message. When BSC sends a RADIO-STATUS message to SGSN due to bad link quality, this counter increments. Times
C901290011 Number of Wireless status messages sent by BSC due to Cell reselection command
Definition Description
Number of Wireless status messages sent by BSC due to Cell reselection command 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. View the status at radio interface by counting this message. When BSC sends a RADIO-STATUS message to SGSN due to cell reselection command, this counter increments. Times
1984
Number of FLOW-CONTROL-BVC messages sent by BSC 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. When BSC sends a FLOW-CONTROL-BVC message, this counter increments, as A1 measurement position shown in Figure 2094.
FIGURE 2094 RADIO-STATUS PROCESS
Measurement Point
Unit
Times
Number of FLOW-CONTROL-BVC-ACK messages received by BSC 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. When BSC receives a FLOW-CONTROL-BVC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 2095.
Measurement Point
1985
Unit
Times
Number of FLOW-CONTROL-MS messages sent by BSC 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. When BSC sends a FLOW-CONTROL-MS message, this counter increments. The measurement point is A1, as shown in Figure 2096.
FIGURE 2096 FLOW-CONTROL-MS PROCESS
Measurement Point
Unit
Times
1986
Number of FLOW-CONTROL-MS-ACK messages received by BSC 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. When BSC receives a FLOW-CONTROL-MS-ACK message, this counter increments. The measurement point is A2, as shown in Figure 2097.
FIGURE 2097 FLOW-CONTROL-MS PROCESS
Measurement Point
Unit
Times
Number of FLOW-CONTROL- PFC messages sent by BSC 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. When BSC sends a FLOW-CONTROL-PFC message, this counter increments. The measurement point is A1, as shown in Figure 2098.
Measurement Point
1987
Unit
Times
Number of FLOW-CONTROL-PFC-ACK messages received by BSC 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. When BSC receives a FLOW-CONTROL-PFC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 2099.
FIGURE 2099 FLOW-CONTROL-PFC PROCESS
Measurement Point
Unit
Times
1988
Number of Status messages sent by BSC BSC sends status message to SGSN, to indicate exception occurred. This counter counts the number of sending this message by BSC. When BSC sends a STATUS message, this counter increments. The measurement point is A1, as shown in Figure 2100.
FIGURE 2100 STATUS PROCESS
Measurement Point
Unit
Times
Number of Status messages received by BSC SGSN sends status message to BSC, to indicate exception occurred. This counter counts the number of receiving this message by BSC. When BSC receives a STATUS message, this counter increments. The measurement point is A2, as shown in Figure 2101.
Measurement Point
1989
Unit
Times
Number of Status messages sent with BVCI Unknown 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. When BSC sends a STATUS message due to BVCI Unknown, this counter increments. Times
Number of Status messages sent with Cell service congestion 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. When BSC sends a STATUS message due to cell service congestion, this counter increments. Times
1990
Number of Status messages sent with protocol error 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. When BSC sends a STATUS message due to protocol error, this counter increments. Times
Number of Status messages sent with Processor overload 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. When BSC sends a STATUS message due to processor overload, this counter increments. Times
Number of Status messages received with BVCI Unknown 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. When BSC receives a STATUS message due to BVCI Unknown, this counter increments. Times
1991
Number of Status messages received with Cell service congestion 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. When BSC receives a STATUS message due to cell service congestion, this counter increments. Times
Number of Status messages received with protocol error 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. When BSC receives a STATUS message due to protocol error, this counter increments. Times
Number of Status messages received with cause Processor overload 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. When BSC receives a STATUS message due to processor overload, this counter increments. Times
1992
Number of DOWNLOAD-BSS-PFC messages sent by BSC 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. When BSC sends a DOWNLOAD-BSS-PFC message, this counter increments. The measurement point is A1, as shown in Figure 2102.
FIGURE 2102 CREATE-BSS-PFC PROCESS
Measurement Point
Unit
Times
Number of BVCCREATE-BSS-PFC messages received by BSC 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. When BSC receives a CREATE-BSS-PFC message, this counter increments. The measurement point is A2, as shown in Figure 2103.
Measurement Point
1993
Unit
Times
Number of CREATE-BSS-PFC-ACK messages sent by BSC 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. When BSC sends a CREATE-BSS-PFC-ACK message, this counter increments. The measurement point is A3, as shown in Figure 2104.
FIGURE 2104 CREATE-BSS-PFC PROCESS
Measurement Point
1994
Unit
Times
Number of CREATE-BSS-PFC-NACK messages sent by BSC 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. When BSC sends a CREATE-BSS-PFC-NACK message, this counter increments. The measurement point is A4, as shown in Figure 2105.
FIGURE 2105 CREATE-BSS-PFC PROCESS
Measurement Point
Unit
Times
Number of MODIFY-BSS-PFC messages sent by BSC BSC sends MODIFY-BSS-PFC message to SGSN to request modify packet flow control context. This counter counts the number of sending this message by BSC.
1995
Measurement Point
When BSC sends a MODIFY-BSS-PFC message, this counter increments. The measurement point is A1, as shown in Figure 2106.
FIGURE 2106 MODIFY-BSS-PFC PROCESS
Unit
Times
Number of MODIFY-BSS-PFC-ACK messages received by BSC 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. When BSC receives a MODIFY-BSS-PFC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 2107.
FIGURE 2107 MODIFY-BSS-PFC PROCESS
Measurement Point
Unit
Times
1996
Number of DELETE-BSS-PFC messages received by BSC 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. When BSC receives a DELETE-BSS-PFC message, this counter increments. The measurement point is A1, as shown in Figure 2108.
FIGURE 2108 DELETE-BSS-PFC PROCESS
Measurement Point
Unit
Times
Number of DELETE -BSS-PFC-ACK messages sent by BSC 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. When BSC sends a DELETE-BSS-PFC-ACK message, this counter increments. The measurement point is A2, as shown in Figure 2109.
Measurement Point
1997
Unit
Times
1998
Chapter
36
1999
C901300025 Number of abnormal cases in NS transmission due to unknown NSVC.................................................... 2016 C901300026 Number of abnormal cases in NS transmission due to protocol error ...................................................... 2017 C901300027 Number of test failure (while over max) ......... 2017 C901300028 Number of blocking procedure failure (after exceeding the maximum times) .......................................... 2018 C901300029 Number of unblocking procedure failure (after exceeding the maximum times)....................................... 2019 C901300030 Number of congestion occurrence of level 1................................................................................. 2020 C901300031 Number of congestion recovery of level 1......... 2020 C901300032 Number of congestion occurrence of level 2................................................................................. 2021 C901300033 Number of congestion recovery of level 2......... 2021 C901300034 Number of congestion occurrence of level 3................................................................................. 2021 C901300035 Number of congestion recovery of level 3......... 2021 C901300036 Number of BECN......................................... 2022 C901300037 Number of FECN ......................................... 2022
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.
Time of PVC unavailable This counter counts the time during which NSVC can not be used for data transmission. 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.
2000
Unit
Second
Time of PVC congestion frame relay 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. The counter starts counting when SGSN receives data in which BECN is set and stops counting when BECN is not set. The duration between the two time points is the total time of PVC congestion bit being set.
FIGURE 2111 TIME OF PVC CONGESTION FRAME RELAY
Measurement Point
Unit
Second
2001
Number of bytes received from SGSN This counter counts the number of bytes received by NS sublayer from SGSN. This counter performs statistics for FR layer, and the statistic data contains FR header.
The NSVC load can be checked through this counter. FR accumulates the number of bytes received from Gb interface. The measurement point is A1.
FIGURE 2112 UPLINK/DOWNLINK NS DATA
Unit
Byte
Number of bytes sent to SGSN This counter counts the number of bytes sent to SGSN from NS sublayer.
2002
This counter performs statistics for FR layer, and the statistic data contains FR header.
Usage Measurement Point
The NSVC load can be checked through this counter. FR accumulates the number of bytes sent each time. The measurement point is A2.
FIGURE 2113 UPLINK/DOWNLINK NS DATA
Unit
Byte
Number of PDU data sent by NS sub layer This counter counts the number of PDU data sent to SGSN from NS sub layer. The NSVC service load can be checked through this counter. ' The counter increments each time BSC's FR sends a PDU data to SGSN. The measurement point is A1.
FIGURE 2114 SENDING AND RECEIVING PDU DATA
Measurement Point
Unit
Times
2003
Number of PDU data received by NS sub layer This counter counts the number of PDU data received by NS sub layer from SGSN. The NSVC service load can be checked through this counter. ' The counter increments each time BSC's FR receives a PDU data from SGSN. The measurement point is A2.
FIGURE 2115 SENDING AND RECEIVING PDU DATA
Measurement Point
Unit
Times
Number of PDU data discarded by NS sub layer The amount of PDU data discarded by NS sub layer is the sum of incorrect PDU data received by NS sub layer from SGSN and PDU data that FR fails to send. The NSVC service load can be checked through this counter. ' The counter increments when NS sub layer receives an illegal PDU data. The counter increments when FR fails to send a PDU data.
Usage
Measurement Point
2004
Unit
Times
Number of reset messages send to opposite end by NS sub layer NS sub layer sends the NSVC resetting message to indicate SGSN to reset specified NSVC. This counter counts the number of resetting messages sent to opposite end by NS sub layer. The counter counts the number of BSC resetting specified NSVC. ' Each time BSC sends the NS-RESET message, this counter increments. The measurement point is A1.
FIGURE 2117 NSVC RESETTING PROCESS
Usage
Measurement Point
Unit
Times
2005
Number of received reset messages sent by opposite end 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. The counter counts the number of SGSN resetting specified NSVC. ' Each time BSC receives the NS-RESET message, this counter increments. The measurement point is A3.
FIGURE 2118 NSVC RESETTING PROCESS
Usage
Measurement Point
Unit
Times
C901300011 Number of reset confirm messages send to opposite end by NS sub layer
Definition Description
Number of reset confirm messages send to opposite end by NS sub layer 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. Each time BSC sends the NS-RESET-ACK message, this counter increments. The measurement point is A4.
Measurement Point
2006
Unit
Times
Number of received reset confirm messages sent by opposite end 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. Each time BSC receives the NS-RESET-ACK message, this counter increments. The measurement point is A2.
FIGURE 2120 NSVC RESETTING PROCESS
Measurement Point
Unit
Times
2007
Number of blocking messages send to opposite end by NS sub layer 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. Each time BSC sends the NS-BLOCK message, this counter increments. The measurement point is A1.
FIGURE 2121 NSVC BLOCKING PROCESS
Measurement Point
Unit
Times
Number of received blocking messages sent by opposite end SGSN sends the NSVC blocking message to indicate BSC to block specified NSVC. This counter counts the number of SGSN's blocking specified NSVC. Each time BSC receives the NS-BLOCK message, this counter increments. The measurement point is A3.
Measurement Point
2008
Unit
Times
C901300015 Number of blocking confirm messages send to opposite end by NS sub layer
Definition Description
Number of blocking confirm messages send to opposite end by NS sub layer 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. Each time BSC sends the NS-BLOCK-ACK message, this counter increments. The measurement point is A4.
FIGURE 2123 NSVC BLOCKING PROCESS
Measurement Point
Unit
Times
2009
Number of received blocking confirm messages sent by opposite end 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. Each time BSC receives the NS-BLOCK-ACK message, this counter increments. The measurement point is A2.
FIGURE 2124 NSVC BLOCKING PROCESS
Measurement Point
Unit
Times
Number of unblocking messages send to opposite end by NS sub layer 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.
2010
Measurement Point
Each time BSC sends the NS-UNBLOCK message, this counter increments. The measurement point is A1.
FIGURE 2125 NSVC UNBLOCKING PROCESS
Unit
Times
Number of received unblocking messages sent by opposite end SGSN sends the NSVC unblocking message to indicate BSC to unblock specified NSVC. This counter counts the number of SGSN's unblocking specified NSVC. Each time BSC receives the NS-UNBLOCK message, this counter increments. The measurement point is A3.
FIGURE 2126 NSVC UNBLOCKING PROCESS
Measurement Point
2011
Unit
Times
C901300019 Number of unblocking confirm messages send to opposite end by NS sub layer
Definition Description
Number of unblocking confirm messages send to opposite end by NS sub layer 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. Each time BSC sends the NS-UNBLOCK-ACK message, this counter increments. The measurement point is A4.
FIGURE 2127 NSVC UNBLOCKING PROCESS
Measurement Point
Unit
Times
2012
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. Each time BSC receives the NS-UNBLOCK-ACK message, this counter increments. The measurement point is A2.
FIGURE 2128 NSVC UNBLOCKING PROCESS
Measurement Point
Unit
Times
Number of abnormal cases in NS transmission due to network fault This counter counts the number of abnormal cases in NS sub layer transmission due to transmission network fault. 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.
2013
Unit
Times
Number of abnormal cases in NS transmission due to O&M interference This counter counts the number of abnormal cases in NS sub layer transmission due to O interference. When NS sub layer receives the blocking request from background, the counter increments. The measurement point is A1.
FIGURE 2130 BLOCKING NSVC BY BACKGROUND
Unit
Times
2014
Number of abnormal cases in NS transmission due to equipment fault This counter counts the number of abnormal cases in NS sub layer transmission due to equipment fault. When NS sub layer receives reported fault from frame relay and the fault is due to equipment fault, the counter increments. The measurement point is A1.
FIGURE 2131 FR REPORTING EQUIPMENT FAULT
Unit
Times
Number of abnormal cases in NS transmission due to NSVC block This counter counts the number of abnormal cases in NS sub layer transmission due to NSVC block. When NS sub layer sends the status message which is due to NSVC BLOCKED, the counter increments. The measurement point is A1.
2015
Unit
Times
Number of abnormal cases in NS transmission due to unknown NSVC This counter counts the number of abnormal cases in NS sub layer transmission due to unknown NSVC. When NS sub layer sends the status message which is due to unknown NSVC, the counter increments. The measurement point is A1.
FIGURE 2133 NSVC UNKNOWN
Unit
Times
2016
Number of abnormal cases in NS transmission due to protocol error This counter counts the number of abnormal cases in NS sub layer transmission due to protocol error. When NS sub layer sends the status message which is due to protocol error, including PDU semantic error, PDU being incompatible with protocol, protocol error, invalid necessary IE, and missing necessary IE, the counter increments. The measurement point is A1.
FIGURE 2134 NS PROTOCOL ERROR
Unit
Times
Number of test failure (while over max) This counters counts the number of test failure due to the maximum retransmission times being exceeded during the NS sub layer test procedure. 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.
Measurement Point
2017
Unit
Times
C901300028 Number of blocking procedure failure (after exceeding the maximum times)
Definition Description
Number of blocking procedure failure (after exceeding the maximum times) This counters counts the number of test failure due to the maximum retransmission times being exceeded during the NS sub layer blocking procedure. 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.
Measurement Point
2018
Unit
Times
C901300029 Number of unblocking procedure failure (after exceeding the maximum times)
Definition Description
Number of unblocking procedure failure (after exceeding the maximum times) This counters counts the number of test failure due to the maximum retransmission times being exceeded during the NS sub layer unblocking procedure. 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.
Measurement Point
2019
Unit
Times
2020
Description
2021
Description
Number of BECN This counter counts the number of setting BECN in the data sent by SGSN. The counter counts the number of NSVC backward congestions. When BECN in the data received by FR from SGSN is set, the counter accumulates. The measurement point is A1.
FIGURE 2138 UPLINK/DOWNLINK DATA BECN BEING SET
Unit
Times
Number of FECN This counter counts the number of setting FECN in the data sent by SGSN. The counter counts the number of NSVC forward congestions. When FECN in the data received by FR from SGSN is set, the counter accumulates. The measurement point is A2.
2022
Unit
Times
2023
2024
Chapter
37
2025
C901310027 Number of status messages sent with BVCI Unknown ......................................................................... 2043 C901310028 Number of status messages sent with cell service congestion ............................................................. 2043 C901310029 Number of status messages sent with protocol error............................................................................ 2044 C901310030 Number of status messages sent with processor overload....................................................................... 2044 C901310031 Number of status messages sent with semantically incorrect PDU ........................................................ 2045 C901310032 Number of status messages sent with invalid mandatory information element....................................... 2045 C901310033 Number of status messages sent with missing mandatory IE................................................................ 2046 C901310034 Number of status messages sent with missing conditional IE................................................................ 2046 C901310035 Number of status messages sent with unexpected conditional IE...................................................... 2047 C901310036 Number of status messages sent with conditional IE error ............................................................... 2047 C901310037 Number of status messages sent with protocol status incompatible error................................................ 2048 C901310038 Number of status messages received with BVCI unknown ...................................................................... 2048 C901310039 Number of status messages received with cell service congestion ......................................................... 2049 C901310040 Number of status messages received with protocol error .................................................................... 2049 C901310041 Number of status messages received with processor overload ............................................................. 2049 C901310042 Number of status messages received with BVC blocking ....................................................................... 2050 C901310043 Number of status messages received with semantically incorrect PDU................................................. 2050 C901310044 Number of status messages received with invalid mandatory IE................................................................ 2051 C901310045 Number of status messages received with missing mandatory IE .......................................................... 2051 C901310046 Number of status messages received with missing conditional IE........................................................... 2051 C901310047 Number of status messages received with unexpected conditional IE...................................................... 2052 C901310048 Number of status messages received with conditional IE error............................................................. 2052 C901310049 Number of status messages received with protocol status incompatible error ........................................ 2053 C901310050 Number of status messages received with SGSN congestion.................................................................... 2053
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.
2026
Number of CS Paging received by BSS This counter counts the number of PAGING CS messages received by NSE at BSC from SGSN. The counter is used to find out the frequency of SGSN's CS paging to MS. When BSS receives a message of which the type is GB_PAGING_CS, the counter increments. The measurement point is A.
FIGURE 2140 MEASUREMENT POINT OF BSS RECEIVING CS PAGING MESSAGE
Unit
Times
Number of PS Paging received by BSS This counter counts the number of PAGING PS messages received by NSE at BSC from SGSN. The counter is used to find out the frequency of SGSN's PS paging to MS. When BSS receives a message of which the type is GB_PAGING_PS, the counter increments. The measurement point is A.
FIGURE 2141 MEASUREMENT POINT OF BSS RECEIVING PS PAGING MESSAGE
2027
Unit
Times
Number of SUSPEND message sent When BSS receives the suspending GPRS service message from MS, BSS will send the SUSPEND message to SGSN. This counter counts the number of sending SUSPEND message from NSE. The counter is used to find out the frequency of MS's terminating GPRS service. When BSS sends the SUSPEND message, the counter increments. The measurement point is A1.
FIGURE 2142 SUSPEND PROCESS
Unit
Times
Number of SUSPEND-ACK message received 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. The counter is used to find out cases in which SGSN has response when MS requests for terminating GPRS service. When BSS receives the SUSPEND_ACK message, the counter increments. The measurement point is A2.
2028
Unit
Times
Number of SUSPEND-NACK message received 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. The counter is used to find out cases in which SGSN has no response when MS requests for terminating GPRS service. When BSS receives the SUSPEND_NACK message, the counter increments. The measurement point is A2.
FIGURE 2144 MEASUREMENT POINT OF BSS RECEIVING SUSPEND_NACK MESSAGE
Unit
Times
2029
Number of RESUME message sent 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. The counter is used to find out the frequency of MS's resuming GPRS service. When BSS sends the RESUME message, the counter increments. The measurement point is A1.
FIGURE 2145 RESUME PROCESS
Unit
Times
Number of RESUME-ACK message received 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. The counter is used to find out causes due to which SGSN has no response when MS requests for resuming GPRS service. When BSS receives the RESUME_ACK message, the counter increments. The measurement point is A2.
2030
Unit
Times
Number of RESUME-NACK message received If the MS in the RESUME PDU message sent from BSS is not found at SGSN, SGSN willl send the RESUME_NACK message to BSS. 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. The counter is used to find out cases in which SGSN has no response when MS requests for resuming GPRS service. When BSS receives the RESUME_NACK message, the counter increments. The measurement point is A2.
FIGURE 2147 MEASUREMENT POINT OF BSS RECEIVING RESUME_NACK MESSAGE
Unit
Times
2031
Number of FLUSH-LL message received 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. The counter is used to find out the frequency of MS's changing cell. When BSS receives the FLUSH_LL message, the counter increments. The measurement point is A1.
FIGURE 2148 FLUSH_LL PROCESS
Unit
Times
Number of FLUSH-LL-ACK message sent 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. 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. When BSS sends the FLUSH_LL_ACK message, the counter increments. The measurement point is A2.
Usage
Measurement Point
2032
Unit
Times
Number of LLC-DISCARDED message sent When the LLC PDU stored in BSS is deleted, the LLC_DISCARDED message is sent to SGSN. This counter counts the number of sending LLC_DISCARDED message from NSE. The counter is used to find out the storage of LLC PDU in BSS. When BSS sends the LLC_DISCARDED message, the counter increments. The measurement point is A.
FIGURE 2150 MEASUREMENT POINT OF BSS SENDING LLC_DISCARDED MESSAGE
Unit
Times
Number of BVC-BLOCK message sent 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
2033
with the BVC do not receive downlink data any more. This counter counts the number of sending BVC_BLOCK message from NSE.
Usage Measurement Point
The counter is used to find out the frequency of BSS's requesting to block BVC. When BSS sends the BVC_BLOCK message, the counter increments. The measurement point is A1.
FIGURE 2151 BVC_BLOCK PROCESS
Unit
Times
Number of BVC_BLOCK_ACK message received When SGSN receives the BVC_BLOCK message from BSS, it identifies the BVC to be blocked and stops sending data to the BVC, and replies the BVC_BLOCK_ACK message to BSS. This counter counts the number of BVC_BLOCK_ACK messages received by NSE. The counter is used to find out cases when BVC is blocked. When BSS receives the BVC_BLOCK_ACK message, the counter increments. The measurement point is A2.
FIGURE 2152 BVC_BLOCK PROCESS
Unit
Times
2034
Number of BVC-UNBLOCK message sent 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. The counter is used to find out the frequency of BSS's requesting to unblock BVC. When BSS sends the BVC_UNBLOCK message, the counter increments. The measurement point is A1.
FIGURE 2153 BVC_UNBLOCK PROCESS
Unit
Times
Number of BVC-UNBLOCK-ACK message received When SGSN receives the BVC_UNBLOCK message from BSS, it identifies the BVC to be unblocked and replies the BVC_UNBLOCK_ACK message to BSS. This counter counts the number of BVC_UNBLOCK_ACK messages received by NSE. The counter is used to find out cases when BVC is unblocked. When BSS receives the BVC_UNBLOCK_ACK message, the counter increments. The measurement point is A2.
2035
Unit
Times
Number of BVC-RESET message sent This counter counts the number of PCU sending signaling BVC resetting message through Gb interface. The counter is used to find out the frequency of requesting to restart BVC due to BVC failure. When NSE at BSC sends message of which the type is BVC_RESET and BVCI is zero, the counter increments. The measurement point is A1.
FIGURE 2155 PROCESS OF SENDING BVC_RESET
Unit
Times
2036
This counter counts the number of PCU's receiving the signaling BVC resetting message. The counter is used to find out cases when BVC is restarted. When NSE at BSC receives message of which the type is BVC_RESET and BVCI is zero, the counter increments. The measurement point is A1.
FIGURE 2156 PROCESS OF RECEIVING BVC_RESET
Unit
Times
Number of BVC-RESET-ACK message sent When PCU receives the signaling BVC resetting message from Gb interface, it replies the signaling BVC resetting acknowledge message. This counter counts the number of NSE's sending signaling BVC resetting acknowledge message. The counter is used to find out cases of SGSN initializing BVC. When NSE at BSC sends message of which the type is BVC_RESET_ACK and BVCI is zero, the counter increments. The measurement point is A2.
FIGURE 2157 PROCESS OF RECEIVING BVC_RESET
Unit
Times
2037
Number of BVC_RESET_ACK message received Number of PCU's receiving the signaling BVC resetting acknowledge message. This counter counts the number of NSE's receiving signaling BVC resetting acknowledge message. The counter is used to find out cases of BVC initialization. When NSE at BSC receives message of which the type is BVC_RESET_ACK and BVCI is zero, the counter increments. The measurement point is A2.
FIGURE 2158 PROCESS OF SENDING BVC_RESET
Unit
Times
Number of PERFORM_LOCATION_REQUEST message received 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. The counter is used to find out the frequency of SGSN's sending location request to BSS. When BSS receives the PERFORM_LOCATION_REQUEST message, the counter increments. The measurement point is A1.
2038
Unit
Times
Number of PERFORM_LOCATION_RESPONSE message sent 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. The counter is used to find out BSS's response to the location request from SGSN. When BSS sends the PERFORM_LOCATION_RESPONSE message, the counter increments. The measurement point is A2.
FIGURE 2160 PERFORM_LOCATION_REQUEST PROCESS
Unit
Times
2039
Number of PERFORM_LOCATION_ABORT message received 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. The counter is used to find out the frequency of SGSN's terminating location towards BSS. When BSS receives the PERFORM_LOCATION_ABORT message, the counter increments. The measurement point is A.
FIGURE 2161 MEASUREMENT POINT OF BSS RECEIVING PERFORM_LOCATION_ABORT MESSAGE
Unit
Times
Number of POSITION_COMMAND message sent 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. The counter is used to find out the frequency of BSS's requesting to implement positioning command to SGSN. When BSS sends the POSITION_COMMAND message, the counter increments. The measurement point is A1.
2040
Unit
Times
Number of POSITION_RESPONSE message received 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. The counter is used to find out the frequency of SGSN's requesting to implement positioning command to BSS. When BSS receives the POSITION_RESPONSE message, the counter increments. The measurement point is A2.
FIGURE 2163 POSITION_COMMAND PROCESS
Unit
Times
2041
Number of status messages sent 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. The counter is used to find out abnormality occurring when NSE receives downlink BSSGP PDU. 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 2164 STATUS PROCESS
Unit
Times
Number of status messages received 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. The counter is used to find out abnormality occurring when SGSN receives downlink BSSGP PDU. When NSE receives the STATUS message, the counter increments. The measurement point is A2.
2042
Unit
Times
Number of status messages sent with BVCI Unknown This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "BVCI unknown". The counter is used to find out the frequency of abnormality due to "BVCI unknown" occurring when NSE receives downlink BSSGP PDU. 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. Times
Number of status messages sent with cell service congestion This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "cell traffic congestion". The counter is used to find out the frequency of abnormality due to "cell traffic congestion" occurring when NSE receives downlink BSSGP PDU.
Usage
2043
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. Times
Number of status messages sent with protocol error This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Protocol error". The counter is used to find out the frequency of abnormality due to "Protocol error" occurring when NSE receives downlink BSSGP PDU. 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. Times
Number of status messages sent with processor overload This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Processor overload". The counter is used to find out the frequency of abnormality due to "Processor overload" occurring when NSE receives downlink BSSGP PDU. 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. Times
Usage
2044
Number of status messages sent with semantically incorrect PDU This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Semantically incorrect PDU". The counter is used to find out the frequency of abnormality due to "Semantically incorrect PDU" occurring when NSE receives downlink BSSGP PDU. 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. Times
Usage
C901310032 Number of status messages sent with invalid mandatory information element
Definition Description
Number of status messages sent with invalid mandatory information element This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Invalid mandatory information". The counter is used to find out the frequency of abnormality due to "Invalid mandatory information" occurring when NSE receives downlink BSSGP PDU. 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. Times
Usage
2045
Number of status messages sent with missing mandatory IE This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Missing mandatory IE". The counter is used to find out the frequency of abnormality due to "Missing mandatory IE" occurring when NSE receives downlink BSSGP PDU. 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. Times
Usage
Number of status messages sent with missing conditional IE This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Missing conditional IE". The counter is used to find out the frequency of abnormality due to "Missing conditional IE" occurring when NSE receives downlink BSSGP PDU. 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. Times
Usage
2046
Number of status messages sent with unexpected conditional IE This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Unexpected conditional IE". The counter is used to find out the frequency of abnormality due to "Unexpected conditional IE" occurring when NSE receives downlink BSSGP PDU. 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. Times
Usage
Number of status messages sent with conditional IE error This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Conditional IE error". The counter is used to find out the frequency of abnormality due to "Conditional IE error" occurring when NSE receives downlink BSSGP PDU. 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. Times
Usage
2047
C901310037 Number of status messages sent with protocol status incompatible error
Definition Description
Number of status messages sent with protocol status incompatible error 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". 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. 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. Times
Usage
Number of status messages received with BVCI unknown This counter counts the number of received STATUS messages which indicate "BVCI unknown". The counter is used to find out the frequency of abnormality due to "BVCI unknown" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "BVCI unknown", the counter increments. Times
2048
Number of status messages received with cell service congestion This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "cell traffic congestion". The counter is used to find out the frequency of abnormality due to "cell traffic congestion" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "cell traffic congestion", the counter increments. Times
Number of status messages received with protocol error This counter counts the number of received STATUS messages which indicate "Protocol error". The counter is used to find out the frequency of abnormality due to "Protocol error" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Protocol error", the counter increments. Times
Number of status messages received with processor overload This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "Processor overload".
2049
Usage
The counter is used to find out the frequency of abnormality due to "Processor overload" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Processor overload", the counter increments. Times
Number of status messages received with BVC blocking This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "BVCI-blocked". The counter is used to find out the frequency of abnormality due to "BVCI-blocked" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "BVCIblocked", the counter increments. Times
Number of status messages received with semantically incorrect PDU This counter counts the number of received STATUS messages which indicate "Semantically incorrect PDU". The counter is used to find out the frequency of abnormality due to "Semantically incorrect PDU" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Semantically incorrect PDU", the counter increments. Times
2050
Number of status messages received with invalid mandatory IE This counter counts the number of received STATUS messages which indicate "Invalid mandatory information". The counter is used to find out the frequency of abnormality due to "Invalid mandatory information" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Invalid mandatory information", the counter increments. Times
Number of status messages received with missing mandatory IE This counter counts the number of received STATUS messages which indicate "Missing mandatory IE". The counter is used to find out the frequency of abnormality due to "Missing mandatory IE" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Missing mandatory IE", the counter increments. Times
Number of status messages received with missing conditional IE This counter counts the number of received STATUS messages which indicate "Missing conditional IE".
2051
Usage
The counter is used to find out the frequency of abnormality due to "Missing conditional IE" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Missing conditional IE", the counter increments. Times
Number of status messages received with unexpected conditional IE This counter counts the number of received STATUS messages which indicate "Unexpected conditional IE". The counter is used to find out the frequency of abnormality due to "Unexpected conditional IE" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Unexpected conditional IE", the counter increments. Times
Number of status messages received with conditional IE error This counter counts the number of received STATUS messages which indicate "Conditional IE error". The counter is used to find out the frequency of abnormality due to "Conditional IE error" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Conditional IE error", the counter increments. Times
2052
C901310049 Number of status messages received with protocol status incompatible error
Definition Description Usage
Number of status messages received with protocol status incompatible error This counter counts the number of received STATUS messages which indicate "PDU not compatible with the protocol state". 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. When PCU receives STATUS message which indicates "PDU not compatible with the protocol state", the counter increments. Times
Number of status messages received with SGSN congestion This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "SGSN congestion". The counter is used to find out the frequency of abnormality due to "SGSN congestion" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "SGSN congestion", the counter increments. Times
2053
2054
Chapter
38
2055
C901320024 Number of power scans of UL signal level......... 2080 C901320025 Total value of power scans of DL signal quality ............................................................................... 2081 C901320026 Number of power scans of DL signal quality ............................................................................... 2082 C901320027 Total value of power scans of UL signal quality ............................................................................... 2083 C901320028 Number of power scans of UL signal quality ............................................................................... 2084 C901320029 Maximum value of UL signal level in regular scan ............................................................................ 2085 C901320030 Minimum value of UL signal level in regular scan ............................................................................ 2086 C901320031 Maximum value obtained in regular scan of DL signal level ................................................................... 2087 C901320032 Minimum value obtained in regular scan of DL signal level ................................................................... 2088 C901320033 Sum of Periodic BS Power (TCH/F) Search Result ............................................................................. 2089 C901320034 Periodic BS Power (TCH/F) Search Times......... 2089 C901320035 Sum of Periodic BS Power (TCH/H) Search Result ............................................................................. 2090 C901320036 Number of Periodic BS Power (TCH/H) Search ......................................................................... 2090 C901320037 Sum of Periodic BS Power (SDCCH) Search Result ............................................................................. 2091 C901320038 Number of Periodic BS Power (SDCCH) Search ......................................................................... 2091 C901320039 Sum of Periodic DL Signal Level (TCH/F) Search Result .......................................................................... 2091 C901320040 Number of Periodic DL Signal Level (TCH/F) Search ......................................................................... 2092 C901320041 Sum of Periodic DL Signal Level (TCH/H) Search Result .......................................................................... 2092 C901320042 Number of Periodic DL Signal Level (TCH/H) Search ......................................................................... 2093 C901320043 Sum of Periodic DL Signal Level (SDCCH) Search Result .......................................................................... 2093 C901320044 Number of Periodic DL Signal Level (SDCCH) Search ......................................................................... 2093
Overview
According to the receiving level and receiving quality in MS measurement report and the receiving level and receiving quality in BTS measurement, BTS decides whether to perform power control for MS or BTS. BTS also performs statistics according to different reasons for power control. There are two ways for power control: common control and rapid control. The power control amplitude in rapid control is larger than that in common control. Besides, BTS periodically samples the power of MS and BTS to get the average power. After the power control measurement task is customized, BTS periodically reports the power control statistic result to BSC through the PC TEST RPT message. The power control measurement result
2056
can be used to analyze coverage quality and power control effect and frequency. The power control measurement mechanism is shown as below. The measurement point for MS power control is A1, which is after BTS sending the power control message to MS. The measurement point for BTS power control is A2, which is after BTS sending the power control message to itself. The measurement point for periodical power sampling is A3. BSC collects the power control measurement counter information after it receives the PC TEST RPT message, which is at B1 as shown in below.
FIGURE 2166 POWER CONTROL MEASUREMENT
Number of normal increases of MS power due to UL signal level 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. The counter counts when BTS sends the message of increasing transmission power to MS. The measurement point is A1
Measurement Point
2057
Number of rapid increase in MS power due to UL signal level 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. The counter counts when BTS sends the message of increasing transmission power to MS. The measurement point is A1.
Measurement Point
2058
Number of normal decrease of MS power due to UL signal level 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. The counter counts when BTS sends the message of decreasing transmission power to MS. The measurement point is A1.
Measurement Point
2059
Number of rapid decrease in MS power due to UL signal level 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. The counter counts when BTS sends the message of decreasing transmission power to MS. The measurement point is A1.
Measurement Point
2060
Number of normal increases of BS power due to DL signal level 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. The counter counts when BTS sends the message of increasing transmission power to itself. The measurement point is A2.
Measurement Point
2061
Number of rapid increase in BS power due to DL signal level 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. The counter counts when BTS sends the message of increasing transmission power to itself. The measurement point is A2.
Measurement Point
2062
Number of normal decrease of BS power due to DL signal level 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. The counter counts when BTS sends the message of decreasing transmission power to itself. The measurement point is A2.
Measurement Point
2063
Number of rapid decrease in BS power due to DL signal level 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. The counter counts when BTS sends the message of decreasing transmission power to itself. The measurement point is A2.
Measurement Point
2064
Number of normal increases of MS power due to UL signal quality 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. The counter counts when BTS sends the message of increasing transmission power to MS. The measurement point is A1.
Measurement Point
2065
Number of rapid increase in MS power due to UL signal quality 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. The counter counts when BTS sends the message of increasing transmission power to MS. The measurement point is A1.
Measurement Point
2066
Number of normal decrease of MS power due to UL signal quality 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. The counter counts when BTS sends the message of decreasing transmission power to MS. The measurement point is A1.
Measurement Point
2067
Number of rapid decrease in MS power due to UL signal quality 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. The counter counts when BTS sends the message of decreasing transmission power to MS. The measurement point is A1.
Measurement Point
2068
Number of normal increases of BS power due to DL signal quality 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. The counter counts when BTS sends the message of increasing transmission power to itself. The measurement point is A2.
Measurement Point
2069
Number of rapid increase in BTS power due to DL signal quality 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. The counter counts when BTS sends the message of increasing transmission power to itself. The measurement point is A2.
Measurement Point
2070
Number of normal decrease of BS power due to DL signal quality 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. The counter counts when BTS sends the message of decreasing transmission power to itself. The measurement point is A2.
Measurement Point
2071
Number of rapid decrease in BTS power due to DL signal quality 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. The counter counts when BTS sends the message of decreasing transmission power to itself. The measurement point is A2.
Measurement Point
2072
Total value of each result of regular scanning of MS utilization power 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. The counter accumulates when BTS performs periodical scanning. The measurement point is A3.
Measurement Point
2073
Number of regular scanning and sampling of MS utilization power 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. The counter counts when BTS performs periodical scanning. The measurement point is A3.
Measurement Point
2074
Total value of each result of regular scanning of BS utilization power 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. The counter accumulates when BTS performs periodical scanning. The measurement point is A3.
Measurement Point
2075
Number of regular scanning and sampling of BS utilization power 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. The counter counts when BTS performs periodical scanning. The measurement point is A3.
Measurement Point
2076
Total value of power scans of DL signal level 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. The counter counts when BTS performs periodical scanning. The measurement point is A3.
Measurement Point
2077
Number of power scans of DL signal level 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. The counter counts when BTS performs periodical scanning. The measurement point is A3.
Measurement Point
2078
Total value of power scans of UL signal level 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. The counter counts when BTS performs periodical scanning. The measurement point is A3.
Measurement Point
2079
Number of power scans of UL signal level 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. The counter counts when BTS performs periodical scanning. The measurement point is A3.
Measurement Point
2080
Total value of power scans of DL signal quality 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. The counter counts when BTS performs periodical scanning. The measurement point is A3.
Measurement Point
2081
Number of power scans of DL signal quality 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. The counter counts when BTS performs periodical scanning. The measurement point is A3.
Measurement Point
2082
Total value of power scans of UL signal quality 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. The counter counts when BTS performs periodical scanning. The measurement point is A3.
Measurement Point
2083
Number of power scans of UL signal quality 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. The counter counts when BTS performs periodical scanning. The measurement point is A3.
Measurement Point
2084
Maximum value of UL signal level in regular scan When BSC collects information of power control measurement counters, this counter records the maximum uplink signal level value. The counter counts when BSC receives the reported power control measurement message PC TEST RPT. The measurement point is B1.
Measurement Point
2085
Minimum value of UL signal level in regular scan When BSC collects information of power control measurement counters, this counter records the minimum uplink signal level value. The counter counts when BSC receives the reported power control measurement message PC TEST RPT. The measurement point is B1.
Measurement Point
2086
Maximum value obtained in regular scan of DL signal level When BSC collects information of power control measurement counters, this counter records the maximum downlink signal level value. The counter counts when BSC receives the reported power control measurement message PC TEST RPT. The measurement point is B1.
Measurement Point
2087
Minimum value obtained in regular scan of DL signal level When BSC collects information of power control measurement counters, this counter records the minimum downlink signal level value. The counter counts when BSC receives the reported power control measurement message PC TEST RPT. The measurement point is B1.
Measurement Point
2088
Sum of Periodic BS Power (TCH/F) Search Result This counter records the total value of BS power (TCH/F) of periodical scannings. When the power control message is received and if the channel is TCH/F, then obtain the BS power in the message and accumulate. Grade ZGO-04-02-001 Dynamic BTS Power Control
2089
This counter counts the number of periodical scanning of BS power (TCH/F). When the power control message is received, if the channel is TCH/F and the message contains BS power information, then the counter increments. Times ZGO-04-02-001 Dynamic BTS Power Control
Sum of Periodic BS Power (TCH/H) Search Result This counter records the total value of BS power (TCH/H) of periodical scannings. When the power control message is received and if the channel is TCH/H, then obtain the BS power in the message and accumulate. Grade ZGO-04-02-001 Dynamic BTS Power Control
Number of Periodic BS Power (TCH/H) Search This counter counts the number of periodical scanning of BS power (TCH/H). When the power control message is received, if the channel is TCH/H and the message contains BS power information, then the counter increments. Times ZGO-04-02-001 Dynamic BTS Power Control
2090
Sum of Periodic BS Power (SDCCH) Search Result This counter records the total value of BS power (SDCCH) of periodical scannings. When the power control message is received and if the channel is SDCCH, then obtain the BS power in the message and accumulate. Grade ZGO-04-02-001 Dynamic BTS Power Control
Number of Periodic BS Power (SDCCH) Search This counter counts the number of periodical scanning of BS power (SDCCH). When the power control message is received, if the channel is SDCCH and the message contains BS power information, then the counter increments. Times ZGO-04-02-001 Dynamic BTS Power Control
Sum of Periodic DL Signal Level (TCH/F) Search Result This counter records the total value of downlink signal level (TCH/F) of periodical scannings. 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.
2091
This counter counts the number of periodical scanning of downlink signal level (TCH/F). This counter records the total value of downlink signal level (TCH/F) of periodical scannings. 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. Times ZGO-04-02-001 Dynamic BTS Power Control
Sum of Periodic DL Signal Level (TCH/H) Search Result This counter records the total value of downlink signal level (TCH/H) of periodical scannings. 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. Grade ZGO-04-02-001 Dynamic BTS Power Control
2092
Number of Periodic DL Signal Level (TCH/H) Search This counter counts the number of periodical scanning of downlink signal level (TCH/H). 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. Times ZGO-04-02-001 Dynamic BTS Power Control
Sum of Periodic DL Signal Level (SDCCH) Search Result This counter records the total value of downlink signal level (SDCCH) of periodical scannings. When the power control message is received and if the channel is SDCCH, then obtain the downlink signal level in the message and accumulate. Grade ZGO-04-02-001 Dynamic BTS Power Control
Number of Periodic DL Signal Level (SDCCH) Search This counter counts the number of periodical scanning of downlink signal level (SDCCH).
2093
When the power control message is received, if the channel is SDCCH and the message contains downlink signal level information, then the counter increments. Times ZGO-04-02-001 Dynamic BTS Power Control
2094
Chapter
39
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.
Time of PVC unavailable This counter counts the time during which NSVC can not be used for data transmission. The counter starts counting when NSVC link becomes abnormal and stops counting when NSVC link becomes normal. The duration
2095
between the two time points is the time during which NSVC is unavailable.
Unit Related Features
Number of abnormal cases in NS transmission due to network fault This counter is not used for the time being. ZGO-05-04-002 Gb over IP
Number of abnormal cases in NS transmission due to O&M interference This counter is not used for the time being. ZGO-05-04-002 Gb over IP
2096
Number of abnormal cases in NS transmission due to equipment fault This counter is not used for the time being. ZGO-05-04-002 Gb over IP
Number of abnormal cases in NS transmission due to unknown NSVC This counter counts the number of abnormal cases in NS sub layer transmission due to unknown NSVC. During the NS sub layer signaling interaction, the counter accumulates the number of signaling transmitted by unknown NSVC. Times ZGO-05-04-002 Gb over IP
Number of abnormal cases in NS transmission due to protocol error This counter counts the number of abnormal cases in NS sub layer transmission due to protocol error.
2097
When the field in NS signaling is inconsistent with that defined in protocol, the counter accumulates. Times ZGO-05-04-002 Gb over IP
Number of unsuccess test due to over max This counters counts the number of test failure due to the maximum retransmission times being exceeded during the NS sub layer test procedure. When the number of NS sub layer's sending NS-ALIVE PDU exceeds the maximum retransmission times NS-ALIVE-RETRIES and there is no response, the counter increments. The measurement point is A1.
FIGURE 2199 TEST PROCEDURE BEING ABNORMAL
Measurement Point
2098
Chapter
40
2099
C901340022 Number of status messages received with BVCI Unknown...................................................................... 2112 C901340023 Number of status messages received with cell service congestion ......................................................... 2113 C901340024 Number of status messages received with protocol error .................................................................... 2113 C901340025 Number of status messages received with processor overload ............................................................. 2114 C901340026 Number of DOWNLOAD-BSS-PFC messages sent by BSC......................................................................... 2114 C901340027 Number of BVCCREATE-BSS-PFC messages received by BSC............................................................... 2115 C901340028 Number of CREATE-BSS-PFC-ACK messages sent by BSC.................................................................. 2115 C901340029 Number of CREATE-BSS-PFC-NACK messages sent by BSC.................................................................. 2116 C901340030 Number of MODIFY-BSS-PFC messages sent by BSC ............................................................................. 2117 C901340031 Number of MODIFY-BSS-PFC-ACK messages received by BSC............................................................... 2117 C901340032 Number of DELETE-BSS-PFC messages received by BSC......................................................................... 2118 C901340033 Number of DELETE-BSS-PFC-ACK messages sent by BSC.................................................................. 2119 C901340034 Number of DELETE-BSS-PFC-REQ messages received by BSC............................................................... 2119 C901340035 Number of PS-HANDOVER-REQUIRED messages sent by BSC.................................................................. 2120 C901340036 Number of PS-HANDOVER-REQUIRED-ACK messages received by BSC ............................................. 2120 C901340037 Number of PS-HANDOVER-REQUIRED-NACK messages received by BSC ............................................. 2121 C901340038 Number of PS-HANDOVER-REQUEST messages received by BSC ............................................................ 2122 C901340039 Number of PS-HANDOVER-REQUEST-ACK messages sent by BSC ......................................................... 2123 C901340040 Number of PS-HANDOVER-REQUEST-NACK messages sent by BSC ................................................... 2124 C901340041 Number of PS-HANDOVER-COMPLETE messages sent by BSC.................................................................. 2125 C901340042 Number of PS-HANDOVER-CANCEL messages sent by BSC.................................................................. 2126 C901340043 Number of PS-HANDOVER-REQUEST messages with Service UTRAN CCO received by BSC......................... 2127 C901340044 Number of CREATE-BSS-PFC messages with Service UTRAN CCO received by BSC ............................... 2128
Overview
The Gb interface message measurement on IPGB HOST measures the number of transceiving various PTP messages at BSSGP layer of Gb interface in GPRS service, such as RA-CAPABILITY, RADIOSTATUS, and DOWNLOAD-BSS-PFC. Statistic unit in this measurement is cell.
2100
Number of RA-CAPABILITY message received 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. When BSC receives a RA-CAPABILITY message, this counter increments. The measurement point is A.
FIGURE 2200 MEASUREMENT POINT OF THE NUMBER OF RECEIVING RA-CAPABILITY MESSAGE
Measurement Point
Number of PTP packet paging received by BSC 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. When BSC receives a PAGING PS message, this counter increments. The measurement point is A.
FIGURE 2201 PTP PACKET PAGING PROCESS
Measurement Point
Unit
Times
2101
Related Features
ZGO-05-04-002 Gb over IP
Number of PTP circuit paging recevied by BSC 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. When BSC receives a PAGING CS message, this counter increments. The measurement point is A.
FIGURE 2202 PTP CIRCUIT PAGING PROCESS
Measurement Point
Number of RA-CAPABILITY-UPDATE message sent 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. When BSC sends a RA-CAPABILITY-UPDATE message to SGSN, this counter increments. The measurement point is A1.
Measurement Point
2102
Number of RA-CAPABILITY-UPDATE-ACK message received 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. When BSC receives a RA-CAPABILITY-UPDATE-ACK message from SGSN, this counter increments. The measurement point is A2.
FIGURE 2204 RA-CAPABILITY-UPDATE PROCESS
Measurement Point
2103
Number of wireless status PDU messages sent by BSC 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. The radio interface status can be checked by counting this message. When BSC sends a RADIO-STATUS message to SGSN, this counter increments. The measurement point is A.
FIGURE 2205 RADIO-STATUS PROCESS
C901340007 Number of wireless status messages sent by BSC due to losing wireless association with MS
Definition Description
Number of wireless status messages sent by BSC due to losing wireless association with MS 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. The radio interface status can be checked by counting this message. When BSC sends a RADIO-STATUS message to SGSN due to Losing wireless association with MS, this counter increments. Times
2104
Related Features
ZGO-05-04-002 Gb over IP
C901340008 Number of wireless status messages sent by BSC due to bad link quality
Definition Description
Number of wireless status messages sent by BSC due to bad link quality 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. The radio interface status can be checked by counting this message. When BSC sends a RADIO-STATUS message to SGSN due to bad link quality, this counter increments. Times ZGO-05-04-002 Gb over IP
C901340009 Number of wireless status messages sent by BSC due to cell reselection command
Definition Description
Number of wireless status messages sent by BSC due to cell reselection command 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. The radio interface status can be checked by counting this message. When BSC sends a RADIO-STATUS message to SGSN due to cell reselection command, this counter increments. Times ZGO-05-04-002 Gb over IP
2105
Number of FLOW-CONTROL-BVC messages sent by BSC 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. When BSC sends a FLOW-CONTROL-BVC message, this counter increments. The measuremnt point is A1.
FIGURE 2206 FLOW-CONTROL-BVC PROCESS
Measurement Point
Number of FLOW-CONTROL-BVC-ACK messages received by BSC 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. When BSC receives a FLOW-CONTROL-BVC-ACK message, this counter increments. The measurement point is A2.
Measurement Point
2106
Number of FLOW-CONTROL-MS messages sent by BSC 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. When BSC sends the FLOW-CONTROL-MS message, this counter increments. The measurement point is A1.
FIGURE 2208 FLOW-CONTROL-MS PROCESS
Measurement Point
2107
Number of FLOW-CONTROL-MS-ACK messages received by BSC 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. When BSC receives a FLOW-CONTROL-MS-ACK message, this counter increments. The measurement point is A2.
FIGURE 2209 FLOW-CONTROL-MS PROCESS
Measurement Point
Number of FLOW-CONTROL-PFC messages sent by BSC 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. When BSC sends the FLOW-CONTROL-PFC message, this counter increments. The measurement point is A1.
Measurement Point
2108
Number of FLOW-CONTROL-PFC-ACK messages received by BSC 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. When BSC receives a FLOW-CONTROL-PFC-ACK message, this counter increments. The measurement point is A2.
FIGURE 2211 FLOW-CONTROL-PFC PROCESS
Measurement Point
2109
Number of status messages sent by BSC BSC sends the status message to SGSN to indicate that abnormality occurs. This counter counts the number of BSC's sending this message. When BSC sends the STATUS message, this counter increments. The measurement point is A1.
FIGURE 2212 STATUS PROCESS
Measurement Point
Number of status messages received by BSC SGSN sends the status message to BSC to indicate that abnormality occurs. This counter counts the number of BSC's receiving this message. When BSC receives the STATUS message, this counter increments. The measurement point is A2.
Measurement Point
2110
Number of status messages sent with BVCI Unknown 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. When BSC sends a "STATUS" message due to BVCI Unknown, this counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages sent with cell service congestion 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. When BSC sends a "STATUS" message due to cell service congestion, this counter increments. Times ZGO-05-04-002 Gb over IP
2111
Number of status messages sent with protocol error 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. When BSC sends a "STATUS" message due to protocol error, this counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages sent with Processor overload 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. When BSC sends a "STATUS" message due to processor overload, this counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages received with BVCI Unknown BSC sends the status message to SGSN to indicate that abnormality occurs. This counter counts the number of BSC's receiving this message due to BVCI Unknown.
2112
When BSC receives a "STATUS" message due to BVCI Unknown, this counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages received with cell service congestion 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. When BSC receives a "STATUS" message due to cell service congestion, this counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages received with protocol error 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. When BSC receives a "STATUS" message due to protocol error, this counter increments. Times ZGO-05-04-002 Gb over IP
2113
Number of status messages received with processor overload 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. When BSC receives a "STATUS" message due to processor overload, this counter increments. Times ZGO-05-04-002 Gb over IP
Number of DOWNLOAD-BSS-PFC messages sent by BSC 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. When BSC sends the DOWNLOAD-BSS-PFC message, this counter increments. The measurement point is A1.
FIGURE 2214 CREATE-BSS-PFC PROCESS
Measurement Point
2114
Number of BVCCREATE-BSS-PFC messages received by BSC 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. When BSC receives a CREATE-BSS-PFC message, this counter increments. The measurement point is A2.
FIGURE 2215 CREATE-BSS-PFC PROCESS
Measurement Point
Number of CREATE-BSS-PFC-ACK messages sent by BSC 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. When BSC sends a CREATE-BSS-PFC-ACK message, this counter increments. The measurement point is A3.
Measurement Point
2115
Number of CREATE-BSS-PFC-NACK messages sent by BSC 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. When BSC sends a CREATE-BSS-PFC-NACK message, this counter increments. The measurement point is A4.
FIGURE 2217 CREATE-BSS-PFC PROCESS
Measurement Point
2116
Number of MODIFY-BSS-PFC messages sent by BSC 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. When BSC sends the MODIFY-BSS-PFC message, this counter increments. The measurement point is A1.
FIGURE 2218 MODIFY-BSS-PFC PROCESS
Measurement Point
Number of MODIFY-BSS-PFC-ACK messages received by BSC SGSN sends the MODIFY-BSS-PFC-ACK message to BSC to confirm the modification of packet flow control context. This counter counts the number of BSC's receiving this message. When BSC receives a MODIFY-BSS-PFC-ACK message, counter increments. The measurement point is A2. this
Measurement Point
2117
Number of DELETE-BSS-PFC messages received by BSC 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. When BSC receives a DELETE-BSS-PFC message, this counter increments. The measurement point is A1.
FIGURE 2220 DELETE-BSS-PFC PROCESS
Measurement Point
2118
Number of DELETE-BSS-PFC-ACK messages sent by BSC 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. When BSC sends a DELETE-BSS-PFC-ACK message, this counter increments. The measurement point is A2.
FIGURE 2221 DELETE-BSS-PFC PROCESS
Measurement Point
Number of DELETE-BSS-PFC-REQ messages received by BSC This counter is not used for the time being. ZGO-05-04-002 Gb over IP
2119
BSC This counter counts the number of PS-HANDOVER-REQUIRED messages sent to SGSN from BSC in IP transmission mode. The counter increments when BSC sends a PS-HANDOVER-REQUIRED message. The measurement point is A, as shown in Figure 2222.
FIGURE 2222 MEASUREMENT POINT OF NUMBER REQUIRED MESSAGES SENT BY BSC
OF
PS-HANDOVER-
Times
BSC After a PS handover request is acknowledged, SGSN sends the PS-HANDOVER-REQUIRED-ACK message to BSC. This counter counts the number of PS-HANDOVER-REQUIRED-ACK messages received by BSC in IP transmission mode. The counter increments
2120
when BSC receives the PS-HANDOVER-REQUIRED-ACK message. The measurement point is A, as shown in Figure 2223.
FIGURE 2223 MEASUREMENT POINT OF NUMBER REQUIRED-ACK MESSAGES RECEIVED BY BSC
OF
PS-HANDOVER-
Times
BSC If SGSN receives the non-acknowledgement message for PS handover request from BSC, then SGSN sends the PS-HANDOVERREQUIRED-NACK message back to BSC. This counter counts the number of PS-HANDOVER-REQUIRED-NACK messages received by BSC in IP transmission mode. The counter increments when BSC receives the PS-HANDOVER-REQUIRED-NACK message. The measurement point is A, as shown in Figure 2224.
2121
Times
BSC When SGSN receives the PS-HANDOVER-REQUIRED message from BSC, it sends the PS-HANDOVER-REQUEST message back to BSC. This counter counts the number of PS-HANDOVER-REQUEST messages received by BSC from SGSN. The counter increments when BSC receives the PS-HANDOVER-REQUEST message. The measurement point is A2, as shown in Figure 2225.
2122
OF
PS-HANDOVER-
Times
BSC 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 2226.
2123
OF
PS-HANDOVER-
Times
BSC 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
2124
number of messages, which indicate failure of creating MS or PS instance, sent by BSC in IP transmission mode. The counter increments when BSC sends the PS-HANDOVER-REQUEST-NACK message. The measurement point is A3, as shown in Figure 2227.
FIGURE 2227 MEASUREMENT POINT OF NUMBER REQUEST-NACK MESSAGES SENT BY BSC
OF
PS-HANDOVER-
Times
BSC
2125
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 2228.
FIGURE 2228 MEASUREMENT POINT OF NUMBER COMPLETE MESSAGES SENT BY BSC
OF
PS-HANDOVER-
Times
BSC If PS handover fails or waiting for handover is timeout, BSC sends the PS-HANDOVER-CANCEL message to SGSN. This counter counts the number of PS-HANDOVER-CANCEL messages sent by BSC in IP transmission mode. The counter increments when BSC sends the PS-HANDOVER-CANCEL message. The measurement point is A, as shown in Figure 2229.
2126
OF
NUMBER
OF
PS-HANDOVER-
Times
C901340043 Number of PS-HANDOVER-REQUEST messages with Service UTRAN CCO received by BSC
Statistics object Description
BSC After BSC receives the PS-HANDOVER-REQUEST message from SGSN, the message might contains the field Service UTRAN CCO, which indicates that 2G/3G handover is preferred. This counter counts the number of PS-HANDOVER-REQUEST messages, which contains the field Service UTRAN CCO, received by BSC 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 2230.
2127
FIGURE 2230 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUEST MESSAGES WITH SERVICE UTRAN CCO RECEIVED BY BSC
Times
C901340044 Number of CREATE-BSS-PFC messages with Service UTRAN CCO received by BSC
Statistics object Description
BSC When BSC receives the CREATE-BSS-PFC message from SGSN, the message might contain the field Service UTRAN CCO. This counter counts the number of CREATE-BSS-PFC messages, which contains the field Service UTRAN CCO, received by BSC in IP transmission mode. After BSC receives the CREATE-BSS-PFC message from SGSN, it decodes the message to decide whether the message contains the field Service UTRAN CCO. If the message contains the field, the counter increments. The measurement point is A, as shown in Figure 2231.
2128
FIGURE 2231 MEASUREMENT POINT OF NUMBER OF CREATE-BSS-PFC MESSAGES WITH SERVICE UTRAN CCO RECEIVED BY BSC
Times
2129
2130
Chapter
41
2131
C901350027 Number of status messages sent with BVCI Unknown ......................................................................... 2144 C901350028 Number of status messages sent with cell service congestion ............................................................. 2145 C901350029 Number of status messages sent with protocol error............................................................................ 2145 C901350030 Number of status messages sent with processor overload....................................................................... 2146 C901350031 Number of status messages sent with semantically incorrect PDU ........................................................ 2146 C901350032 Number of status messages sent with invalid mandatory information element....................................... 2147 C901350033 Number of status messages sent with missing mandatory IE................................................................ 2147 C901350034 Number of status messages sent with missing conditional IE................................................................ 2148 C901350035 Number of status messages sent with unexpected conditional IE...................................................... 2148 C901350036 Number of status messages sent with conditional IE error ............................................................... 2149 C901350037 Number of status messages sent with protocol status incompatible error................................................ 2149 C901350038 Number of status messages received with BVCI unknown ...................................................................... 2150 C901350039 Number of status messages received with cell service congestion ......................................................... 2150 C901350040 Number of status messages received with protocol error .................................................................... 2150 C901350041 Number of status messages received with processor overload ............................................................. 2151 C901350042 Number of status messages received with BVC blocking ....................................................................... 2151 C901350043 Number of status messages received with semantically incorrect PDU................................................. 2152 C901350044 Number of status messages received with invalid mandatory IE................................................................ 2152 C901350045 Number of status messages received with missing mandatory IE .......................................................... 2153 C901350046 Number of status messages received with missing conditional IE........................................................... 2153 C901350047 Number of status messages received with unexpected conditional IE...................................................... 2154 C901350048 Number of status messages received with conditional IE error............................................................. 2154 C901350049 Number of status messages received with protocol status incompatible error ........................................ 2155 C901350050 Number of status messages received with SGSN congestion.................................................................... 2155
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.
2132
Number of CS Paging received by BSS This counter counts the number of PAGING CS messages received by NSE at BSC from SGSN. The counter is used to find out the frequency of SGSN's CS paging to MS. When BSS receives a message of which the type is GB_PAGING_CS, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of PS Paging received by BSS This counter counts the number of PAGING PS messages received by NSE at BSC from SGSN. The counter is used to find out the frequency of SGSN's PS paging to MS. When BSS receives a message of which the type is GB_PAGING_PS, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of SUSPEND message sent When BSS receives the suspending GPRS service message from MS, BSS will send the SUSPEND message to SGSN. This counter counts the number of sending SUSPEND message from NSE.
2133
The counter is used to find out the frequency of MS's terminating GPRS service. When BSS sends the SUSPEND message, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of SUSPEND-ACK message received 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. The counter is used to find out cases in which SGSN has response when MS requests for terminating GPRS service. When BSS sends the SUSPEND_ACK message, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of SUSPEND-NACK message received 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. The counter is used to find out cases in which SGSN has no response when MS requests for terminating GPRS service. When BSS sends the SUSPEND_NACK message, the counter increments. Times ZGO-05-04-002 Gb over IP
2134
Number of RESUME message sent 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. The counter is used to find out the frequency of MS's resuming GPRS service. When BSS sends the RESUME message, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of RESUME-ACK message received 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. The counter is used to find out causes due to which SGSN has no response when MS requests for resuming GPRS service. When BSS sends the RESUME_ACK message, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of RESUME-NACK message received If the MS in the RESUME PDU message sent from BSS is not found at SGSN, SGSN willl send the RESUME_NACK message to BSS.
2135
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 Measurement Point Unit Related Features
The counter is used to find out cases in which SGSN has no response when MS requests for resuming GPRS service. When BSS receives the RESUME_NACK message, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of FLUSH-LL message received 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. The counter is used to find out the frequency of MS's changing cell. When BSS receives the FLUSH_LL message, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of FLUSH-LL-ACK message sent 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. 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. When BSS sends the FLUSH_LL_ACK message, the counter increments.
Usage
Measurement Point
2136
Number of LLC-DISCARDED message sent When the LLC PDU stored in BSS is deleted, the LLC_DISCARDED message is sent to SGSN. This counter counts the number of sending LLC_DISCARDED message from NSE. The counter is used to find out the storage of LLC PDU in BSS. When BSS sends the LLC_DISCARDED message, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of BVC-BLOCK message sent 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. The counter is used to find out the frequency of BSS's requesting to block BVC. When BSS sends the BVC_BLOCK message, the counter increments. Times ZGO-05-04-002 Gb over IP
2137
Number of BVC-BLOCK-ACK message received When SGSN receives the BVC_BLOCK message from BSS, it identifies the BVC to be blocked and stops sending data to the BVC, and replies the BVC_BLOCK_ACK message to BSS. This counter counts the number of BVC_BLOCK_ACK messages received by NSE. The counter is used to find out cases when BVC is blocked. When BSS receives the BVC_BLOCK_ACK message, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of BVC-UNBLOCK message sent 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. The counter is used to find out the frequency of BSS's requesting to unblock BVC. When BSS sends the BVC_UNBLOCK message, the counter increments. Times ZGO-05-04-002 Gb over IP
2138
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. The counter is used to find out cases when BVC is unblocked. When BSS receives the BVC_BLOCK_ACK message, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of BVC-RESET message sent This counter counts the number of PCU sending signaling BVC resetting message through Gb interface. The counter is used to find out the frequency of requesting to restart BVC due to BVC failure. When NSE at BSC sends message of which the type is BVC_RESET and BVCI is zero, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of BVC-RESET message received This counter counts the number of PCU's receiving the signaling BVC resetting message. The counter is used to find out cases when BVC is restarted. When NSE at BSC receives message of which the type is BVC_RESET and BVCI is zero, the counter increments. Times ZGO-05-04-002 Gb over IP
2139
Number of BVC-RESET-ACK message sent When PCU receives the signaling BVC resetting message from Gb interface, it replies the signaling BVC resetting acknowledgement message. This counter counts the number of NSE's sending signaling BVC resetting acknowledgement message. The counter is used to find out cases of SGSN initializing BVC. When NSE at BSC sends message of which the type is BVC_RESET_ACK and BVCI is zero, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of BVC-RESET-ACK message received Number of PCU's receiving the signaling BVC resetting acknowledgement message. This counter counts the number of NSE's receiving signaling BVC resetting acknowledgement message. The counter is used to find out cases of BVC initialization. When NSE at BSC receives message of which the type is BVC_RESET_ACK and BVCI is zero, the counter increments. Times ZGO-05-04-002 Gb over IP
2140
Number of PERFORMLOCATION-REQUEST message received 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. The counter is used to find out the frequency of SGSN's sending location request to BSS. When BSS receives the PERFORM_LOCATION_REQUEST message, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of PERFORM_LOCATION_RESPONSE message sent 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. The counter is used to find out BSS's response to the location request from SGSN. When BSS receives the PERFORM_LOCATION_REQUEST message, the counter increments. Times ZGO-05-04-002 Gb over IP
2141
Number of PERFORM_LOCATION_ABORT message received 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. The counter is used to find out the frequency of SGSN's terminating location towards BSS. When BSS receives the PERFORM_LOCATION_REQUEST message, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of POSITION_COMMAND message sent 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. The counter is used to find out the frequency of BSS's requesting to implement positioning command to SGSN. When BSS sends the POSITION_COMMAND message, the counter increments. Times ZGO-05-04-002 Gb over IP
2142
Number of POSITION_RESPONSE message received 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. The counter is used to find out the frequency of SGSN's requesting to implement positioning command to BSS. When BSS receives the POSITION_RESPONSE message, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages sent 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. The counter is used to find out abnormality occurring when NSE receives downlink BSSGP PDU. When NSE at BSC sends message of which the type is STATUS to the opposite end entity, the counter increments. Times ZGO-05-04-002 Gb over IP
2143
Number of status messages received 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. The counter is used to find out abnormality occurring when SGSN receives downlink BSSGP PDU. When NSE receives the STATUS message, the counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages sent with BVCI Unknown This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "BVCI unknown". The counter is used to find out the frequency of abnormality due to "BVCI unknown" occurring when NSE receives downlink BSSGP PDU. 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. Times ZGO-05-04-002 Gb over IP
2144
Number of status messages sent with cell service congestion This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "cell traffic congestion". The counter is used to find out the frequency of abnormality due to "cell traffic congestion" occurring when NSE receives downlink BSSGP PDU. 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. Times ZGO-05-04-002 Gb over IP
Usage
Number of status messages sent with protocol error This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Protocol error". The counter is used to find out the frequency of abnormality due to "Protocol error" occurring when NSE receives downlink BSSGP PDU. 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. Times ZGO-05-04-002 Gb over IP
2145
Number of status messages sent with processor overload This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Processor overload". The counter is used to find out the frequency of abnormality due to "Processor overload" occurring when NSE receives downlink BSSGP PDU. 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. Times ZGO-05-04-002 Gb over IP
Usage
Number of status messages sent with semantically incorrect PDU This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Semantically incorrect PDU". The counter is used to find out the frequency of abnormality due to "Semantically incorrect PDU" occurring when NSE receives downlink BSSGP PDU. 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. Times ZGO-05-04-002 Gb over IP
Usage
2146
C901350032 Number of status messages sent with invalid mandatory information element
Definition Description
Number of status messages sent with invalid mandatory information element This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Invalid mandatory information". The counter is used to find out the frequency of abnormality due to "Invalid mandatory information" occurring when NSE receives downlink BSSGP PDU. 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. Times ZGO-05-04-002 Gb over IP
Usage
Number of status messages sent with missing mandatory IE This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Missing mandatory IE". The counter is used to find out the frequency of abnormality due to "Missing mandatory IE" occurring when NSE receives downlink BSSGP PDU. 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. Times ZGO-05-04-002 Gb over IP
Usage
2147
Number of status messages sent with missing conditional IE This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Missing conditional IE". The counter is used to find out the frequency of abnormality due to "Missing conditional IE" occurring when NSE receives downlink BSSGP PDU. 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. Times ZGO-05-04-002 Gb over IP
Usage
Number of status messages sent with unexpected conditional IE This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Unexpected conditional IE". The counter is used to find out the frequency of abnormality due to "Unexpected conditional IE" occurring when NSE receives downlink BSSGP PDU. 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. Times ZGO-05-04-002 Gb over IP
Usage
2148
Number of status messages sent with conditional IE error This counter counts the number of NSE's sending STATUS message to opposite end entity, the message indicating "Conditional IE error". The counter is used to find out the frequency of abnormality due to "Conditional IE error" occurring when NSE receives downlink BSSGP PDU. 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. Times ZGO-05-04-002 Gb over IP
Usage
C901350037 Number of status messages sent with protocol status incompatible error
Definition Description
Number of status messages sent with protocol status incompatible error 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". 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. 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. Times ZGO-05-04-002 Gb over IP
Usage
2149
Number of status messages received with BVCI unknown This counter counts the number of received STATUS messages which indicate "BVCI unknown". The counter is used to find out the frequency of abnormality due to "BVCI unknown" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "BVCI unknown", the counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages received with cell service congestion This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "cell traffic congestion". The counter is used to find out the frequency of abnormality due to "cell traffic congestion" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "cell traffic congestion", the counter increments. Times ZGO-05-04-002 Gb over IP
2150
Description Usage
This counter counts the number of received STATUS messages which indicate "Protocol error". The counter is used to find out the frequency of abnormality due to "Protocol error" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Protocol error", the counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages received with processor overload This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "Processor overload". The counter is used to find out the frequency of abnormality due to "Processor overload" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Processor overload", the counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages received with BVC blocking This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "BVCI-blocked". The counter is used to find out the frequency of abnormality due to "BVCI-blocked" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "BVCIblocked", the counter increments. Times
2151
Related Features
ZGO-05-04-002 Gb over IP
Number of status messages received with semantically incorrect PDU This counter counts the number of received STATUS messages which indicate "Semantically incorrect PDU". The counter is used to find out the frequency of abnormality due to "Semantically incorrect PDU" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Semantically incorrect PDU", the counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages received with invalid mandatory IE This counter counts the number of received STATUS messages which indicate "Invalid mandatory information". The counter is used to find out the frequency of abnormality due to "Invalid mandatory information" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Invalid mandatory information", the counter increments. Times ZGO-05-04-002 Gb over IP
2152
Number of status messages received with missing mandatory IE This counter counts the number of received STATUS messages which indicate "Missing mandatory IE". The counter is used to find out the frequency of abnormality due to "Missing mandatory IE" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Missing mandatory IE", the counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages received with missing conditional IE This counter counts the number of received STATUS messages which indicate "Missing conditional IE". The counter is used to find out the frequency of abnormality due to "Missing conditional IE" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Missing conditional IE", the counter increments. Times ZGO-05-04-002 Gb over IP
2153
Number of status messages received with unexpected conditional IE This counter counts the number of received STATUS messages which indicate "Unexpected conditional IE". The counter is used to find out the frequency of abnormality due to "Unexpected conditional IE" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Unexpected conditional IE", the counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages received with conditional IE error This counter counts the number of received STATUS messages which indicate "Conditional IE error". The counter is used to find out the frequency of abnormality due to "Conditional IE error" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "Conditional IE error", the counter increments. Times ZGO-05-04-002 Gb over IP
2154
C901350049 Number of status messages received with protocol status incompatible error
Definition Description Usage
Number of status messages received with protocol status incompatible error This counter counts the number of received STATUS messages which indicate "PDU not compatible with the protocol state". 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. When PCU receives STATUS message which indicates "PDU not compatible with the protocol state", the counter increments. Times ZGO-05-04-002 Gb over IP
Number of status messages received with SGSN congestion This counter counts the number of PCU's receiving STATUS message from SGSN, the message indicating "SGSN congestion". The counter is used to find out the frequency of abnormality due to "SGSN congestion" occurring when SGSN receives downlink BSSGP PDU. When PCU receives STATUS message which indicates "SGSN congestion", the counter increments. Times ZGO-05-04-002 Gb over IP
2155
2156
Chapter
42
2157
C901360022 Number of HANDOVER SUCCEEDED messages........................................................................... 2175 C901360023 Number of HANDOVER CANDIDATE ENQUIRE messages ..................................................................... 2176 C901360024 Number of HANDOVER CANDIDATE RESPONSE messages ..................................................................... 2177 C901360025 Number of HANDOVER FAILURE messages........................................................................... 2177 C901360026 Number of HANDOVER PERFORMED messages........................................................................... 2178 C901360027 Number of HANDOVER REQUIRED REJECT messages........................................................................... 2179 C901360028 Number of HANDOVER DETECT messages........................................................................... 2179 C901360029 Number of CLEAR COMMAND messages ......... 2180 C901360030 Number of CLEAR COMPLETE messages ......... 2181 C901360031 Number of CLEAR REQUEST messages........... 2181 C901360032 Number of SAPI "N" REJECT messages .......... 2182 C901360033 Number of UL CONFUSION messages ............ 2182 C901360034 Number of DL CONFUSION messages ............ 2183 C901360035 Number of UL RESET messages .................... 2184 C901360036 Number of DL RESET messages .................... 2184 C901360037 Number of UL RESET ACKNOWLEDGE messages........................................................................... 2185 C901360038 Number of DL RESET ACKNOWLEDGE messages........................................................................... 2186 C901360039 Number of UL OVERLOAD messages .............. 2186 C901360040 Number of DL OVERLOAD messages .............. 2187 C901360041 Number of MSC INVOKE TRACE messages........................................................................... 2187 C901360042 Number of sent BSS INVOKE TRACE messages........................................................................... 2188 C901360043 Number of received BSS INVOKE TRACE messages........................................................................... 2189 C901360044 Number of sent CONNECTIONLESS INFORMATION messages ............................................................. 2189 C901360045 Number of received CONNECTIONLESS INFORMATION messages ......................................................... 2190 C901360046 Number of SUSPEND messages .................... 2190 C901360047 Number of RESUME messages ...................... 2191 C901360048 Number of Common ID messages ................. 2192 C901360049 Number of LSA INFORMATION messages......... 2192 C901360050 Number of PERFORM LOCATION REQUEST messages........................................................................... 2193 C901360051 Number of PERFORM LOCATION RESPONSE messages ..................................................................... 2193 C901360052 Number of PERFORM LOCATION ABORT messages........................................................................... 2194 C901360053 Number of sent BLOCK messages.................. 2194 C901360054 Number of received BLOCK ACK messages........................................................................... 2195 C901360055 Number of sent UNBLOCK messages ............. 2196 C901360056 Number of received UNBLOCK ACK messages........................................................................... 2197 C901360057 Number of received BLOCK messages ............ 2197 C901360058 Number of sent BLOCK ACK messages ........... 2198 C901360059 Number of received UNBLOCK messages......... 2199 C901360060 Number of sent UNBLOCK ACK messages......... 2199 C901360061 Number of UL RESET CIRCUIT messages......... 2200 C901360062 Number of DL RESET CIRCUIT messages......... 2201
2158
C901360063 Number of UL RESET CIRCUIT ACK messages........................................................................... 2201 C901360064 Number of DL RESET CIRCUIT ACK messages........................................................................... 2202 C901360065 Number of UL CIRCUIT GROUP BLOCK messages........................................................................... 2203 C901360066 Number of DL CIRCUIT GROUP BLOCK messages........................................................................... 2203 C901360067 Number of UL CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages .................................................. 2204 C901360068 Number of DL CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages .................................................. 2205 C901360069 Number of UL CIRCUIT GROUP UNBLOCK messages........................................................................... 2205 C901360070 Number of DL CIRCUIT GROUP UNBLOCK messages........................................................................... 2206 C901360071 Number of UL CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE messages .............................................. 2207 C901360072 Number of DL CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE messages .............................................. 2208 C901360073 Number of UL UNEQUIPPED CIRCUIT messages........................................................................... 2208 C901360074 Number of DL UNEQUIPPED CIRCUIT messages........................................................................... 2209 C901360075 Number of CHANGE CIRCUIT messages ......... 2210 C901360076 Number of CHANGE CIRCUIT ACK messages........................................................................... 2210 C901360077 Number of HANDOVER PERFORMED ACK messages........................................................................... 2211 C901360078 The count of Sending INTERNAL HANDOVER REQUIRED ....................................................................... 2211 C901360079 The count of Receiving INTERNAL HANDOVER COMMAND.................................................................... 2213 C901360080 The count of Receiving INTERNAL HANDOVER REJECT ........................................................................ 2214 C901360081 Number of INTERNAL HANDOVER ENQUIRY messages ..................................................................... 2214 C901360082 Number of UL RESET IP RESOURCE messages........................................................................... 2215 C901360083 Number of UL RESET IP RESOURCE ACKOWNLEDGE messages........................................................... 2216 C901360084 Number of DL RESET IP RESOURCE messages........................................................................... 2216 C901360085 Number of DL RESET IP RESOURCE ACKNOWLEDGE messages ............................................................ 2217 C901360086 Number of Release Clear Request on SDCCH............................................................................. 2218 C901360087 Number of Release Clear Request on TCH/F .......................................................................... 2218 C901360088 Number of Release Clear Request on TCH/H.......................................................................... 2218
Overview
The BSSMAP message measurement performs statistics for various BSSMAP messages at A-interface. It is used to find out the fre-
2159
quency of various BSSMAP messages transmitted at A-interface. When BSC receives the correct BSSMAP message from MSC, the counter counts. The measurement point is A
FIGURE 2232 MEASUREMENT POINT OF MSC SENDING BSSMAP MESSAGE TO BSC
Before BSC sends the BSSMAP message to MSC, the counter counts. The measurement point is A
FIGURE 2233 MEASUREMENT POINT OF BSC SENDING BSSMAP MESSAGE TO MSC
Number of ASSIGNMENT REQUEST messages 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. The counter is used to find out the frequency of assignment request messages transmitted at A-interface. When BSC receives the ASSIGNMENT REQUEST message, the counter increments. The measurement point is A.
2160
FIGURE 2234 MEASUREMENT POINT OF BSC RECEIVING ASSIGNMENT REQUEST MESSAGE FROM MSC
Unit
Times
Number of ASSIGNMENT COMPLETE messages 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. The counter is used to find out the frequency of assignment completion messages transmitted at A-interface. When BSC sends the ASSIGNMENT COMPLETE message to MSC, the counter increments. The measurement point is A.
FIGURE 2235 MEASUREMENT POINT OF BSC SENDING ASSIGNMENT COMPLETE MESSAGE TO MSC
Unit
Times
2161
Number of ASSIGNMENT FAILURE messages This counter counts the number of assignment failure messages in A-interface BSSMAP messages sent to MSC from BSC. The counter is used to find out the frequency of assignment failure messages transmitted at A-interface. When BSC sends the ASSIGNMENT FAILURE message to MSC, the counter increments. The measurement point is A
FIGURE 2236 MEASUREMENT POINT OF BSC SENDING ASSIGNMENT FAILURE MESSAGE TO MSC
Unit
Times
Number of RESOURCE REQUEST messages 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. The counter is used to find out the frequency of resource request messages transmitted at A-interface. When BSC receives the RESOURCE REQUEST message, the counter increments. The measurement point is A.
2162
FIGURE 2237 MEASUREMENT POINT OF MSC SENDING RESOURCE REQUEST MESSAGE TO BSC
Unit
Times
Number of RESOURCE INDICATION messages 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. The counter is used to find out the frequency of resource indication messages transmitted at A-interface. When BSC sends the RESOURCE INDICATION message to MSC, the counter increments. The measurement point is A.
FIGURE 2238 MEASUREMENT POINT OF BSC SENDING RESOURCE INDICATION MESSAGE TO MSC
Unit
Times
2163
Number of PAGING messages 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. The counter is used to find out the frequency of paging messages transmitted at A-interface. When BSC receives the PAGING message, the counter increments. The measurement point is A.
FIGURE 2239 MEASUREMENT POINT OF MSC SENDING PAGING MESSAGE TO BSC
Unit
Times
Number of CIPHER MODE COMMAND messages 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. The counter is used to find out the frequency of CIPHER MODE COMMAND messages transmitted at A-interface. When BSC receives the CIPHER MODE COMMAND message, the counter increments. The measurement point is A.
2164
FIGURE 2240 MEASUREMENT POINT OF MSC SENDING CIPHER MODE COMMAND MESSAGE TO BSC
Unit
Times
Number of CIPHER MODE COMPLETE messages 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. The counter is used to find out the frequency of CIPHER MODE COMPLETE messages transmitted at A-interface. When BSC sends the CIPHER MODE COMPLETE message to MSC, the counter increments. The measurement point is A.
FIGURE 2241 MEASUREMENT POINT OF BSC SENDING CIPHER MODE COMPLETE MESSAGE TO MSC
Unit
Times
2165
Number of CIPHER MODE REJECT messages 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. The counter is used to find out the frequency of CIPHER MODE REJECT messages transmitted at A-interface. When BSC sends the CIPHER MODE REJECT message to MSC, the counter increments. The measurement point is A.
FIGURE 2242 MEASUREMENT POINT OF BSC SENDING CIPHER MODE REJECT MESSAGE TO MSC
Unit
Times
Number of sent CLASSMARK UPDATE messages 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. The counter is used to find out the sending frequency of CLASSMARK UPDATE messages transmitted at A-interface. When BSC sends the CLASSMARK UPDATE message to MSC, the counter increments. The measurement point is A.
2166
FIGURE 2243 MEASUREMENT POINT OF BSC SENDING CLASSMARK UPDATE MESSAGE TO MSC
Unit
Times
Number of received CLASSMARK UPDATE messages This counter counts the number of CLASSMARK UPDATE messages in A-interface BSSMAP messages received by BSC. The counter is used to find out the frequency of receiving CLASSMARK UPDATE messages transmitted at A-interface. When BSC receives the CLASSMARK UPDATE message, the counter increments. The measurement point is A.
FIGURE 2244 MEASUREMENT POINT OF MSC SENDING CLASSMARK UPDATE MESSAGE TO BSC
Unit
Times
2167
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. The counter is used to find out the frequency of QUEUING INDICATION messages transmitted at A-interface. When BSC sends the QUEUING INDICATION message to MSC, the counter increments. The measurement point is A.
FIGURE 2245 MEASUREMENT POINT OF BSC SENDING QUEUING INDICATION MESSAGE TO MSC
Unit
Times
Number of COMPLETE LAYER 3 INFORMATION messages This counter counts the number of COMPLETE LAYER 3 INFORMATION messages in A-interface BSSMAP messages sent to MSC from BSC. The counter is used to find out the frequency of COMPLETE LAYER 3 INFORMATION messages transmitted at A-interface. When BSC sends the COMPLETE LAYER 3 INFORMATION message to MSC, the counter increments. The measurement point is A.
FIGURE 2246 MEASUREMENT POINT OF BSC SENDING COMPLETE LAYER 3 INFORMATION MESSAGE TO MSC
2168
Unit
Times
Number of CLASSMARK REQUEST messages 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. The counter is used to find out the frequency of CLASSMARK REQUEST messages transmitted at A-interface. When BSC receives the CLASSMARK REQUEST message, the counter increments. The measurement point is A.
FIGURE 2247 MEASUREMENT POINT OF MSC SENDING CLASSMARK REQUEST MESSAGE TO BSC
Unit
Times
Number of uplink LOAD INDICATION messages 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. The counter is used to find out the frequency of uplink load indication messages transmitted at A-interface.
Usage
2169
Measurement Point
When BSC sends the LOAD INDICATION message to MSC, the counter increments. The measurement point is A.
FIGURE 2248 MEASUREMENT POINT OF BSC SENDING LOAD INDICATION MESSAGE TO MSC
Unit
Times
Number of downlink LOAD INDICATION messages This counter counts the number of load indication messages in A-interface BSSMAP messages received by BSC. The counter is used to find out the frequency of downlink load indication messages transmitted at A-interface. When BSC receives the LOAD INDICATION message, the counter increments. The measurement point is A.
FIGURE 2249 MEASUREMENT POINT OF MSC SENDING LOAD INDICATION MESSAGE TO BSC
Unit
Times
2170
Number of HANDOVER REQUEST messages 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. The counter is used to find out the frequency of handover request messages transmitted at A-interface. When BSC receives the HANDOVER REQUEST message, the counter increments. The measurement point is A.
FIGURE 2250 MEASUREMENT POINT OF MSC SENDING HANDOVER REQUEST MESSAGE TO BSC
Unit
Times
Number of HANDOVER REQUIRED messages 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. The counter is used to find out the frequency of HANDOVER REQUIRED messages transmitted at A-interface. When BSC sends the HANDOVER REQUIRED message to MSC, the counter increments. The measurement point is A1.
2171
Unit
Times
Number of HANDOVER COMMAND messages 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. The counter is used to find out the frequency of HANDOVER COMMAND messages transmitted at A-interface. When BSC receives the HANDOVER COMMAND message, the counter increments. The measurement point is A4.
2172
Unit
Times
Number of HANDOVER REQUEST ACK messages 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. The counter is used to find out the frequency of HANDOVER REQUEST ACK messages transmitted at A-interface. When BSC sends the HANDOVER REQUEST ACK message to MSC, the counter increments. The measurement point is A3.
2173
Unit
Times
Number of HANDOVER COMPLETE messages 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. The counter is used to find out the frequency of HANDOVER COMPLETE messages transmitted at A-interface. When BSC sends the HANDOVER COMPLETE message to MSC, the counter increments. The measurement point is A5.
2174
Unit
Times
Number of HANDOVER SUCCEEDED messages 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. The counter is used to find out the frequency of HANDOVER SUCCEEDED messages transmitted at A-interface. When BSC receives the HANDOVER SUCCEEDED message, the counter increments. The measurement point is A6.
2175
Unit
Times
Number of HANDOVER CANDIDATE ENQUIRE messages 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. The counter is used to find out the frequency of HANDOVER CANDIDATE ENQUIRE messages transmitted at A-interface. When BSC receives the HANDOVER CANDIDATE ENQUIRE message, the counter increments. The measurement point is A1.
FIGURE 2256 PROCESS OF MSC SENDING HANDOVER CANDIDATE ENQUIRE MESSAGE TO BSC
2176
Unit
Times
Number of HANDOVER CANDIDATE RESPONSE messages After BSC receives the HANDOVER CANDIDATE ENQUIRE message, it initiates handover process for specified calls of the cell, that is, BSC sends corresponding HANDOVER REQUIRED messages to MSC. After all HANDOVER REQUIRED messages are sent, BSC notifies MSC of the number of triggered handover through the HANDOVER CANDIDATE RESPONSE message. This counter counts the number of HANDOVER CANDIDATE RESPONSE messages in A-interface BSSMAP messages sent to MSC from BSC.
The counter is used to find out the frequency of HANDOVER CANDIDATE RESPONSE messages transmitted at A-interface. When BSC sends the HANDOVER CANDIDATE RESPONSE message to MSC, the counter increments. The measurement point is A2.
FIGURE 2257 PROCESS OF MSC SENDING HANDOVER CANDIDATE ENQUIRE MESSAGE TO BSC
Unit
Times
2177
This counter counts the number of HANDOVER FAILURE messages in A-interface BSSMAP messages sent to MSC from BSC. The counter is used to find out the frequency of HANDOVER FAILURE messages transmitted at A-interface. When BSC sends the HANDOVER FAILURE message to MSC, the counter increments. The measurement point is A.
FIGURE 2258 MEASUREMENT POINT OF BSC SENDING HANDOVER FAILURE MESSAGE TO MSC
Unit
Times
Number of HANDOVER PERFORMED messages 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. The counter is used to find out the frequency of HANDOVER PERFORMED messages transmitted at A-interface. When BSC sends the HANDOVER PERFORMED message to MSC, the counter increments. The measurement point is A.
FIGURE 2259 MEASUREMENT POINT OF BSC SENDING HANDOVER PERFORMED MESSAGE TO MSC
Unit
Times
2178
Number of HANDOVER REQUIRED REJECT messages This counter counts the number of HANDOVER REQUIRED REJECT messages in A-interface BSSMAP messages received by BSC. The counter is used to find out the frequency of HANDOVER REQUIRED REJECT messages transmitted at A-interface. When BSC receives the HANDOVER REQUIRED REJECT message, the counter increments. The measurement point is A.
FIGURE 2260 MEASUREMENT POINT OF MSC SENDING HANDOVER REQUIRED REJECT MESSAGE TO BSC
Unit
Times
Number of HANDOVER DETECT messages This counter counts the number of HANDOVER DETECT messages in A-interface BSSMAP messages sent to MSC from BSC. The counter is used to find out the frequency of HANDOVER DETECT messages transmitted at A-interface. When BSC sends the HANDOVER DETECT message to MSC, the counter increments. The measurement point is A.
2179
FIGURE 2261 MEASUREMENT POINT OF BSC SENDING HANDOVER DETECT MESSAGE TO MSC
Unit
Times
Number of CLEAR COMMAND messages 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. The counter is used to find out the frequency of CLEAR COMMAND messages transmitted at A-interface. When BSC receives the CLEAR COMMAND message, the counter increments. The measurement point is A1.
FIGURE 2262 CLEAR PROCESS
Unit
Times
2180
Number of CLEAR COMPLETE messages 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. The counter is used to find out the frequency of CLEAR COMPLETE messages transmitted at A-interface. When BSC sends the CLEAR COMPLETE message to MSC, the counter increments. The measurement point is A2.
FIGURE 2263 CLEAR PROCESS
Unit
Times
Number of CLEAR REQUEST messages 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. The counter is used to find out the frequency of CLEAR REQUEST messages transmitted at A-interface. When BSC sends the CLEAR REQUEST message to MSC, the counter increments. The measurement point is A.
2181
FIGURE 2264 MEASUREMENT POINT OF BSC SENDING CLEAR REQUEST MESSAGE TO MSC
Unit
Times
Number of SAPI "N" REJECT messages This counter counts the number of SAPI "N" REJECT messages in A-interface BSSMAP messages sent to MSC from BSC. The counter is used to find out the frequency of SAPI "N" REJECT messages transmitted at A-interface. When BSC sends the SAPI "N" REJECT message to MSC, the counter increments. The measurement point is A.
FIGURE 2265 MEASUREMENT POINT OF BSC SENDING SAPI "N" REJECT MESSAGE TO MSC
Unit
Times
Number of UL CONFUSION messages When BSC receives the incorrect BSSMAP message from MSC, it sends the CONFUSION message to MSC. This counter counts the
2182
number of CONFUSION messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage Measurement Point
The counter is used to find out the frequency of uplink CONFUSION messages transmitted at A-interface. When BSC sends the CONFUSION message to MSC, the counter increments. The measurement point is A.
FIGURE 2266 MEASUREMENT POINT OF BSC SENDING CONFUSION MESSAGE TO MSC
Unit
Times
Number of DL CONFUSION messages 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. The counter is used to find out the frequency of downlink CONFUSION messages transmitted at A-interface. When BSC receives the CONFUSION message, the counter increments. The measurement point is A.
FIGURE 2267 MEASUREMENT POINT OF MSC SENDING CONFUSION MESSAGE TO BSC
Unit
Times
2183
Number of UL RESET messages 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. The counter is used to find out the frequency of uplink RESET messages transmitted at A-interface. When BSC sends the RESET message to MSC, the counter increments. The measurement point is A1.
FIGURE 2268 UPLINK RESET PROCESS
Unit
Times
Number of DL RESET messages 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. The counter is used to find out the frequency of downlink RESET messages transmitted at A-interface. When BSC receives the RESET message, the counter increments. The measurement point is A1.
2184
Unit
Times
Number of UL RESET ACKNOWLEDGE messages 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. The counter is used to find out the frequency of uplink RESET ACKNOWLEDGE messages transmitted at A-interface. When BSC sends the RESET ACKNOWLEDGE message to MSC, the counter increments. The measurement point is A2.
FIGURE 2270 DOWNLINK RESET PROCESS
Unit
Times
2185
Number of DL RESET ACKNOWLEDGE messages 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. The counter is used to find out the frequency of downlink RESET ACKNOWLEDGE messages transmitted at A-interface. When BSC receives the RESET ACKNOWLEDGE message, the counter increments. The measurement point is A2.
FIGURE 2271 UPLINK RESET PROCESS
Unit
Times
Number of UL OVERLOAD messages 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. The counter is used to find out the frequency of uplink OVERLOAD messages transmitted at A-interface. When BSC sends the OVERLOAD message to MSC, the counter increments. The measurement point is A.
2186
Unit
Times
Number of DL OVERLOAD messages 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. The counter is used to find out the frequency of downlink OVERLOAD messages transmitted at A-interface. When BSC receives the OVERLOAD message, the counter increments. The measurement point is A.
FIGURE 2273 MEASUREMENT POINT OF MSC SENDING OVERLOAD MESSAGE TO BSC
Unit
Times
2187
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. The counter is used to find out the frequency of MSC INVOKE TRACE messages transmitted at A-interface. When BSC receives the MSC INVOKE TRACE message, the counter increments. The measurement point is A.
FIGURE 2274 MEASUREMENT POINT OF MSC SENDING MSC INVOKE TRACE MESSAGE TO BSC
Unit
Times
Number of sent BSS INVOKE TRACE messages 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. The counter is used to find out the frequency of sending BSS INVOKE TRACE messages transmitted at A-interface. When BSC sends the BSS INVOKE TRACE message to MSC, the counter increments. The measurement point is A.
FIGURE 2275 MEASUREMENT POINT OF BSC SENDING BSS INVOKE TRACE MESSAGE TO MSC
2188
Unit
Times
Number of received BSS INVOKE TRACE messages This counter counts the number of BSS INVOKE TRACE messages in A-interface BSSMAP messages received by BSC. The counter is used to find out the frequency of receiving BSS INVOKE TRACE messages transmitted at A-interface. When BSC receives the BSS INVOKE TRACE message, the counter increments. The measurement point is A.
FIGURE 2276 MEASUREMENT POINT OF MSC SENDING BSS INVOKE TRACE MESSAGE TO BSC
Unit
Times
Number of sent CONNECTIONLESS INFORMATION messages This counter counts the number of CONNECTIONLESS INFORMATION messages in A-interface BSSMAP messages sent by BSC. The counter is used to find out the frequency of sending CONNECTIONLESS INFORMATION messages transmitted at A-interface. When BSC sends the CONNECTIONLESS INFORMATION message to MSC, the counter increments. The measurement point is A.
2189
FIGURE 2277 MEASUREMENT POINT OF BSC SENDING CONNECTIONLESS INFORMATION MESSAGE TO MSC
Unit
Times
Number of received CONNECTIONLESS INFORMATION messages This counter counts the number of CONNECTIONLESS INFORMATION messages in A-interface BSSMAP messages received by BSC. The counter is used to find out the frequency of receiving CONNECTIONLESS INFORMATION messages transmitted at A-interface. When BSC receives the CONNECTIONLESS INFORMATION message, the counter increments. The measurement point is A.
FIGURE 2278 MEASUREMENT POINT OF MSC SENDING CONNECTIONLESS INFORMATION MESSAGE TO BSC
Unit
Times
Number of SUSPEND messages When BSC detects that congestion occurs at radio interface, it sends a SUSPEND message to MSC, asking MSC to stop sending
2190
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 Measurement Point
The counter is used to find out the frequency of SUSPEND messages transmitted at A-interface. When BSC sends the SUSPEND message to MSC, the counter increments. The measurement point is A.
FIGURE 2279 MEASUREMENT POINT OF BSC SENDING SUSPEND MESSAGE TO MSC
Unit
Times
Number of RESUME messages 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. The counter is used to find out the frequency of RESUME messages transmitted at A-interface. When BSC sends the RESUME message to MSC, the counter increments. The measurement point is A.
FIGURE 2280 MEASUREMENT POINT OF BSC SENDING RESUME MESSAGE TO MSC
Unit
Times
2191
Number of Common ID messages This counter counts the number of Common ID messages in A-interface BSSMAP messages received by BSC. The counter is used to find out the frequency of Common ID messages transmitted at A-interface. When BSC receives the Common ID message, the counter increments. The measurement point is A.
FIGURE 2281 MEASUREMENT POINT OF MSC SENDING COMMON ID MESSAGE TO BSC
Unit
Times
Number of LSA INFORMATION messages 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. The counter is used to find out the frequency of LSA INFORMATION messages transmitted at A-interface. When BSC receives the LSA INFORMATION message, the counter increments. The measurement point is A.
FIGURE 2282 MEASUREMENT POINT OF MSC SENDING LSA INFORMATION MESSAGE TO BSC
2192
Unit
Times
Number of PERFORM LOCATION REQUEST messages This counter counts the number of PERFORM LOCATION REQUEST messages in A-interface BSSMAP messages received by BSC. The counter is used to find out the frequency of PERFORM LOCATION REQUEST messages transmitted at A-interface. When BSC receives the PERFORM LOCATION REQUEST message, the counter increments. The measurement point is A1.
FIGURE 2283 PROCESS OF MSC SENDING PERFORM LOCATION REQUEST MESSAGE TO BSC
Unit
Times
Number of PERFORM LOCATION RESPONSE messages This counter counts the number of PERFORM LOCATION RESPONSE messages in A-interface BSSMAP messages sent to MSC from BSC. The counter is used to find out the frequency of PERFORM LOCATION RESPONSE messages transmitted at A-interface. When BSC sends the PERFORM LOCATION RESPONSE message to MSC, the counter increments. The measurement point is A2.
2193
FIGURE 2284 PROCESS OF MSC SENDING PERFORM LOCATION REQUEST MESSAGE TO BSC
Unit
Times
Number of PERFORM LOCATION ABORT messages This counter counts the number of PERFORM LOCATION ABORT messages in A-interface BSSMAP messages received by BSC. The counter is used to find out the frequency of PERFORM LOCATION ABORT messages transmitted at A-interface. When BSC receives the PERFORM LOCATION ABORT message, the counter increments. The measurement point is A.
FIGURE 2285 MEASUREMENT POINT OF MSC SENDING PERFORM LOCATION ABORT MESSAGE TO BSC
Unit
Times
2194
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. The counter is used to find out the frequency of sending BLOCK messages transmitted at A-interface. When BSC sends the BLOCK message to MSC, the counter increments. The measurement point is A1.
FIGURE 2286 PROCESS OF BSC SENDING BLOCK MESSAGE TO MSC
Unit
Times
Number of received BLOCK ACK messages 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. The counter is used to find out the frequency of receiving BLOCK ACK messages transmitted at A-interface. When BSC receives the BLOCK ACK message, the counter increments. The measurement point is A2.
2195
Unit
Times
Number of sent UNBLOCK messages 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. The counter is used to find out the frequency of sending UNBLOCK messages transmitted at A-interface. When BSC sends the UNBLOCK message to MSC, the counter increments. The measurement point is A1.
FIGURE 2288 PROCESS OF BSC SENDING UNBLOCK MESSAGE TO MSC
Unit
Times
2196
Number of received UNBLOCK ACK messages 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. The counter is used to find out the frequency of receiving UNBLOCK ACK messages transmitted at A-interface. When BSC receives the UNBLOCK ACK message, the counter increments. The measurement point is A2.
FIGURE 2289 PROCESS OF BSC SENDING UNBLOCK MESSAGE TO MSC
Unit
Times
Number of received BLOCK messages 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. The counter is used to find out the frequency of receiving BLOCK messages transmitted at A-interface. When BSC receives the BLOCK message, the counter increments. The measurement point is A1.
2197
Unit
Times
Number of sent BLOCK ACK messages 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. The counter is used to find out the frequency of sending BLOCK ACK messages transmitted at A-interface. When BSC sends the BLOCK ACK message to MSC, the counter increments. The measurement point is A2.
FIGURE 2291 PROCESS OF MSC SENDING BLOCK MESSAGE TO BSC
Unit
Times
2198
Number of received UNBLOCK messages 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. The counter is used to find out the frequency of receiving UNBLOCK messages transmitted at A-interface. When BSC receives the UNBLOCK message, the counter increments. The measurement point is A1.
FIGURE 2292 PROCESS OF MSC SENDING UNBLOCK MESSAGE TO BSC
Unit
Times
Number of sent UNBLOCK ACK messages 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. The counter is used to find out the frequency of sending UNBLOCK ACK messages transmitted at A-interface. When BSC sends the UNBLOCK ACK message to MSC, the counter increments. The measurement point is A2.
2199
Unit
Times
Number of UL RESET CIRCUIT messages 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. The counter is used to find out the frequency of uplink RESET CIRCUIT messages transmitted at A-interface. When BSC sends the RESET CIRCUIT message to MSC, the counter increments. The measurement point is A1.
FIGURE 2294 PROCESS OF BSC SENDING RESET CIRCUIT MESSAGE TO MSC
Unit
Times
2200
Number of DL RESET CIRCUIT messages 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. The counter is used to find out the frequency of downlink RESET CIRCUIT messages transmitted at A-interface. When BSC receives the RESET CIRCUIT message, the counter increments. The measurement point is A1.
FIGURE 2295 PROCESS OF MSC SENDING RESET CIRCUIT MESSAGE TO BSC
Unit
Times
Number of UL RESET CIRCUIT ACK messages 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. The counter is used to find out the frequency of uplink RESET CIRCUIT ACK messages transmitted at A-interface. When BSC sends the RESET CIRCUIT ACK message to MSC, the counter increments. The measurement point is A2.
2201
Unit
Times
Number of DL RESET CIRCUIT ACK messages 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. The counter is used to find out the frequency of downlink RESET CIRCUIT ACK messages transmitted at A-interface. When BSC receives the RESET CIRCUIT ACK message, the counter increments. The measurement point is A2.
FIGURE 2297 PROCESS OF BSC SENDING RESET CIRCUIT MESSAGE TO MSC
Unit
Times
2202
Number of UL CIRCUIT GROUP BLOCK messages 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. The counter is used to find out the frequency of uplink CIRCUIT GROUP BLOCK messages transmitted at A-interface. When BSC sends the CIRCUIT GROUP BLOCK message to MSC, the counter increments. The measurement point is A1.
FIGURE 2298 PROCESS OF BSC SENDING CIRCUIT GROUP BLOCK MESSAGE TO MSC
Unit
Times
Number of DL CIRCUIT GROUP BLOCK messages 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. The counter is used to find out the frequency of downlink CIRCUIT GROUP BLOCK messages transmitted at A-interface. When BSC receives the CIRCUIT GROUP BLOCK message, the counter increments. The measurement point is A1.
2203
FIGURE 2299 PROCESS OF MSC SENDING CIRCUIT GROUP BLOCK MESSAGE TO BSC
Unit
Times
Number of UL CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages 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. The counter is used to find out the frequency of uplink CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages transmitted at A-interface. When BSC sends the CIRCUIT GROUP BLOCKING ACKNOWLEDGE message to MSC, the counter increments. The measurement point is A2.
FIGURE 2300 PROCESS OF MSC SENDING CIRCUIT GROUP BLOCK MESSAGE TO BSC
Usage
Measurement Point
Unit
Times
2204
Number of DL CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages 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. The counter is used to find out the frequency of downlink CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages transmitted at A-interface. When BSC receives the CIRCUIT GROUP BLOCKING ACKNOWLEDGE message, the counter increments. The measurement point is A2.
FIGURE 2301 PROCESS OF BSC SENDING CIRCUIT GROUP BLOCK MESSAGE TO MSC
Usage
Measurement Point
Unit
Times
Number of UL CIRCUIT GROUP UNBLOCK messages When BSC decides to unblock some terrestrial circuit of A-interface, it sends a CIRCUIT GROUP UNBLOCK message to MSC. This
2205
counter counts the number of CIRCUIT GROUP UNBLOCK messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage Measurement Point
The counter is used to find out the frequency of uplink CIRCUIT GROUP UNBLOCK messages transmitted at A-interface. When BSC sends the CIRCUIT GROUP UNBLOCK message to MSC, the counter increments. The measurement point is A1.
FIGURE 2302 PROCESS OF BSC SENDING CIRCUIT GROUP UNBLOCK MESSAGE TO MSC
Unit
Times
Number of DL CIRCUIT GROUP UNBLOCK messages 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. The counter is used to find out the frequency of downlink CIRCUIT GROUP UNBLOCK messages transmitted at A-interface. When BSC receives the CIRCUIT GROUP UNBLOCK message, the counter increments. The measurement point is A1.
FIGURE 2303 PROCESS OF MSC SENDING CIRCUIT GROUP UNBLOCK MESSAGE TO BSC
2206
Unit
Times
Number of UL CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE messages 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. The counter is used to find out the frequency of uplink CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE messages transmitted at A-interface. When BSC sends the CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message to MSC, the counter increments. The measurement point is A2.
FIGURE 2304 PROCESS OF MSC SENDING CIRCUIT GROUP UNBLOCK MESSAGE TO BSC
Usage
Measurement Point
Unit
Times
2207
Number of DL CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE messages 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. The counter is used to find out the frequency of downlink CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE messages transmitted at A-interface. When BSC receives the CIRCUIT GROUP UNBLOCKING ACKNOWLEDGE message, the counter increments. The measurement point is A2.
FIGURE 2305 PROCESS OF BSC SENDING CIRCUIT GROUP UNBLOCK MESSAGE TO MSC
Usage
Measurement Point
Unit
Times
Number of UL UNEQUIPPED CIRCUIT messages During circuit maintenance process, if BSC can not find the circuit in the message, it returns the UNEQUIPPED CIRCUIT message to
2208
MSC. This counter counts the number of UNEQUIPPED CIRCUIT messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage Measurement Point
The counter is used to find out the frequency of uplink UNEQUIPPED CIRCUIT messages transmitted at A-interface. When BSC sends the UNEQUIPPED CIRCUIT message to MSC, the counter increments. The measurement point is A.
FIGURE 2306 MEASUREMENT POINT OF BSC SENDING UNEQUIPPED CIRCUIT MESSAGE TO MSC
Unit
Times
Number of DL UNEQUIPPED CIRCUIT messages 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. The counter is used to find out the frequency of downlink UNEQUIPPED CIRCUIT messages transmitted at A-interface. When BSC receives the UNEQUIPPED CIRCUIT message, the counter increments. The measurement point is A.
FIGURE 2307 MEASUREMENT POINT OF MSC SENDING UNEQUIPPED CIRCUIT MESSAGE TO BSC
Unit
Times
2209
Number of CHANGE CIRCUIT messages When A-interface terrestrial circuits are allocated only by BSC, if MSC wants to perform circuit handover for a call connection, MSC will send a CHANGE CIRCUIT message to BSC and release the circuit at the same time. This counter counts the number of CHANGE CIRCUIT messages in A-interface BSSMAP messages received by BSC. The counter is used to find out the frequency of CHANGE CIRCUIT messages transmitted at A-interface. When BSC receives the CHANGE CIRCUIT message, the counter increments. The measurement point is A1.
FIGURE 2308 PROCESS OF MSC SENDING CHANGE CIRCUIT MESSAGE TO BSC
Unit
Times
Number of CHANGE CIRCUIT ACK messages When A-interface terrestrial circuits are allocated only by BSC, if MSC wants to perform circuit handover for a call connection, MSC will send a CHANGE CIRCUIT message to BSC and release the circuit at the same time. After BSC receives the message, it selects a new circuit being occupied that satisfies requirement, sends the circuit information in the CHANGE CIRCUIT ACK message to MSC, and releases the circuit. This counter counts the number of CHANGE CIRCUIT ACK messages in A-interface BSSMAP messages received by BSC.
2210
The counter is used to find out the frequency of CHANGE CIRCUIT ACK messages transmitted at A-interface. When BSC sends the CHANGE CIRCUIT ACK message to MSC, the counter increments. The measurement point is A2.
FIGURE 2309 PROCESS OF MSC SENDING CHANGE CIRCUIT MESSAGE TO BSC
Unit
Times
Number of HANDOVER PERFORMED ACK messages This counter counts the number of HANDOVER PERFORMED ACK messages received by BSC from MSC. This counter counts the number of CHANGE CIRCUIT ACK messages in A-interface BSSMAP messages received by BSC.
The counter is used to find out cases of BSC receiving the HANDOVER PERFORMED ACK message from MSC. When BSC receives the HANDOVER PERFORMED ACK message from MSC, the counter increments. Times
CELL
2211
Description
This counter counts the number of internal handover requests sent to MSC from BSC. The measurement point is A1, as shown in Figure 2310. Times
FIGURE 2310 MEASUREMENT POINT OF THE COUNT OF SENDING INTERNAL HANDOVER REQUIRED
Reference
3GPP TS 48008
2212
CELL This counter counts the number of internal handover commands sent to BSC from MSC. The measurement point is A2, as shown in Figure 2311. Times
FIGURE 2311 MEASUREMENT POINT OF INTERNAL HANDOVER COMMAND
THE
COUNT
OF
RECEIVING
Reference
3GPP TS 48008
2213
CELL This counter counts the number of internal handover rejections sent to BSC from MSC. The measurement point is A1, as shown in Figure 2312. Times
FIGURE 2312 MEASUREMENT POINT INTERNAL HANDOVER REJECT
OF THE
COUNT
OF
RECEIVING
Reference
3GPP TS 48008
CELL This counter counts the number of INTERNAL HANDOVER ENQUIRY messages sent by MSC. On TCH/F or TCH/H, when BSC receives the INTERNAL HANDOVER ENQUIRY message from MSC, the counter increments. The measurement point is A1, as shown in Figure 2313.
2214
Unit
Times
CELL This counter counts the number of IP resource resettings initiated by BSC towards MSC. OMCR initiates the IP resource resetting request, and the IPRSCRST module initiates the IP resource resetting request towards MSC through the ADispatch module. When the ADispatch module receives the IP resource resetting request from the IPRSCRST module, the counter increments. The measurement point is A, as shown in Figure 2314.
FIGURE 2314 OMCR INITIATING IP RESOURCE RESETTING FLOW
Unit
Times
2215
CELL This counter counts the number of IP resource resetting response messages sent to MSC from BSC. MSC initiates IP resource resetting towards BSC, and the IPRSCRST module at OMP sends IP resource resetting response to MSC through the ADispatch module. When the ADispatch module receives the IP resource resetting response, the counter increments. The measurement point is A, as shown in Figure 2315.
FIGURE 2315 MSC INITIATING IP RESOURCE RESETTING FLOW
Unit
Times
CELL This counter counts the number of IP resource resetting requests initiated by MSC towards BSC. MSC initiates the IP resource resetting requests towards the IPRSCRST module through the ADispatch module. When the ADispatch module receives the IP resource resetting request from MSC, the counter increments. The measurement point is A, as shown in Figure 2316.
2216
Unit Reference
CELL This counter counts the number of IP resource resetting response messages sent to BSC from MSC. OMCR initiates the IP resource resetting request, the IPRSCRST module initiates the IP resource resetting request towards MSC and waits for MSC to send back the IP resource resetting response. When the ADispatch module receives the IP resource resetting response from MSC, the counter increments. The measurement point is A, as shown in .
FIGURE 2317 OMCR INITIATING IP RESOURCE RESETTING FLOW
Unit
Times
2217
This counter counts the times that the BSC initiates the release when the MS occupies the SDCCH. This counter supports V6.20.200a and later.
Time
This counter counts the times that the BSC initiates the release when the MS occupies the TCH/F. None None Time
This counter counts the times that the BSC initiates the release when the MS occupies the TCH/H. None None Time
2218
Chapter
43
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.
Number of UL DTAP messages This counter counts the number of A-interface DTAP messages sent to MSC from BSC. This counter counts the number of HANDOVER CANDIDATE RESPONSE messages in A-interface BSSMAP messages sent to MSC from BSC.
Usage
The counter analyzes the frequency of uplink DTAP messages transmitted at A-interface.
2219
Measurement Point
The counter counts when BSC sends the DTAP message to MSC. The measurement point is A.
FIGURE 2318 MEASUREMENT POINT OF BSC SENDING A-INTERFACE DTAP MESSAGE TO MSC
Unit
Times
Number of DL DTAP messages 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. The counter analyzes the frequency of downlink DTAP messages transmitted at A-interface. The counter counts when BSC receives the Connection Indication message, Connection Confirm message, Disconnection Indication message, or Data Indication message, these messages containing DTAP message. The measurement point is A.
FIGURE 2319 MEASUREMENT POINT OF MSC SENDING A-INTERFACE DTAP MESSAGE TO BSC
Unit
Times
2220
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. The counter analyzes the frequency of uplink BSSMAP messages transmitted at A-interface. 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 2320 MEASUREMENT POINT OF BSC SENDING A-INTERFACE BSSMAP MESSAGE TO MSC
Unit
Times
Number of DL BSSMAP messages 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. The counter analyzes the frequency of downlink BSSMAP messages transmitted at A-interface. The counter counts when BSC receives the Connection Indication message, Connection Confirm message, Data Indication message, or UnitData Indication message, these messages containing BSSMAP message. The measurement point is A.
FIGURE 2321 MEASUREMENT POINT OF BSC RECEIVING A-INTERFACE BSSMAP MESSAGE FROM MSC
Unit
Times
2221
Number of DL BSSMAP messages received with error 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. The counter analyzes the frequency of received incorrect BSSMAP messages transmitted at A-interface. The counter counts when BSC receives incorrect BSSMAP message. Times
Number of chosen for MSC Load share by NULL_NRI This counter counts the number of a MSC being chosen for load sharing by NULL_NRI within the measurement period. 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. The counter counts when iBSC chooses an appropriate MSC route for MS access. Times
2222
C901370007 Number of chosen for MSC Load share by the NRI not in the MSC pool
Definition Description Usage
Number of chosen for MSC Load share by the NRI not in the MSC pool This counter counts the number of a MSC being chosen for load sharing by non-NULL_NRI within the measurement period. 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. The counter counts when iBSC chooses an appropriate MSC route for MS access. Times
2223
2224
Chapter
44
Overview
The terrestrial resource availability measurement performs statistics for the availability of terrestrial resource at A-interface, including the average number of available BSC trunk circuits, the average number of unavailable BSC trunk circuits, the maximum number of busy trunk circuits, the total busy time of BSC trunk cir-
2225
cuits, and the total congestion time of BSC trunk circuits. All these information reflects the A-interface trunk circuit resource usage. Statistic unit in this measurement is BSC.
Mean number of available trunk circuits This counter counts the average number of trunk circuits that can be used normally. The counter reflects the current trunk circuit usage. The counter counts when system periodically queries database for circuit information. Times
Mean number of unavailable trunk circuits This counter counts the average number of trunk circuits that can not be used normally, including the number of circuits being occupied and the number of circuits being blocked. The counter reflects the current trunk circuit usage. The counter counts when system periodically queries database for circuit information. Times
Maximum number of busy trunk circuits This counter counts the maximum number of trunk circuits being occupied during the measurement period. The counter reflects the transient occupation condition of trunk circuits. There are three measurement points for the maximum number of busy trunk circuits.
2226
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
Busy time of trunk circuit This counter counts the total time of all trunk circuits being occupied during the measurement period. The counter reflects the busy condition of trunk circuits. There are three measurement points for the busy time of trunk circuits. Before the trunk circuit is occupied successfully, the counter calculates the occupation time and accumulates. Before the trunk circuit is released, the counter calculates the occupation time and accumulates. During periodical measurement, the counter calculates the occupation time and accumulates.
Unit
Second
Congestion time of trunk circuit This counter counts the total time of failing to request trunk circuit The counter reflects the congestion condition of trunk circuits. There are three measurement points for the congestion time of trunk circuits. Before the trunk circuit is attempted to be occupied, if the congestion identifier is set, then the counter calculates the congestion time and accumulates.
2227
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
Mean number of available UDP port This counter counts the average number of available UDP ports. The counter is used to find out the average number of available UDP ports. The counter counts when system periodically queries database for circuit information. Times ZGO-05-04-003 A over IP
Mean number of unavailable UDP port This counter counts the average number of unavailable UDP ports. The counter is used to find out the average number of unavailable UDP ports. The counter counts when system periodically queries database for circuit information. Times ZGO-05-04-003 A over IP
2228
Number of allocation AIPB board success 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. The counter is used to find out the frequency of allocating AIPB board successfully. When the request of AIPB board from database is returned successfully, the counter accumulates. The measurement point is A.
FIGURE 2322 REQUESTING RESOURCE FROM DATABASE SUCCESSFULLY
Number of allocation AIPB board failure 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. The counter is used to find out the frequency of AIPB board allocation failure. When the request of AIPB board from database fails, the counter accumulates. The measurement point is A.
2229
Maximum number of seizure UDP port This counter counts the maximum number of UDP ports being occupied. The counter is used to find out the maximum number of UDP ports being occupied. The counter counts at the following time points. 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.
2230
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.
The counter is used to find out the frequency of successfully requesting AIPB board for UDP port through only one request. 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 2324 REQUESTING RESOURCE FROM DATABASE SUCCESSFULLY
Number of successful two time request UDP port to AIPB 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.
2231
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 2325 REQUESTING RESOURCE FROM DATABASE SUCCESSFULLY
Number of successful three time request UDP port to AIPB 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.
The counter is used to find out the frequency of successfully requesting AIPB board for UDP port through three requests. When the connection succeeds and the requesting AIPB board for UDP port succeeds after three requests, the counter accumulates. The measurement point is A.
2232
Number of failure request UDP port to AIPB 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.
The counter is used to find out the frequency of failing to request AIPB board for UDP port. When the connection failure message is returned, the counter accumulates. The measurement point is A.
FIGURE 2327 REQUESTING RESOURCE FROM DATABASE FAILURE
Unit
Times
2233
Related Features
ZGO-05-04-003 A over IP
Seizure duration of UDP port This counter counts the total time of UDPPort being occupied. The counter is used to find out the total time of UDPPort being occupied. The counter counts at the following time points. 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.
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. 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. After the call is established, BSC and MGW negotiate the RTP transmission mode. When control plane receives the RTP_MUX_RPT message from user plane, if the RTP multiplexing mode is not applied, the counter counts. The measurement point is A, as shown in Figure 2328.
Usage
Measurement Point
2234
THE
TIMES OF
USER PLANE
TRANSPORT WITHOUT
RTP
Unit
Times
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. 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. 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 applied, the counter counts. The measurement point is A, as shown in Figure 2329.
FIGURE 2329 THE TIMES OF HEADER COMPRESSION RTP
MULTIPLEXING APPLIED WITHOUT
Usage
Measurement Point
RTP
Unit
Times
2235
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. 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. 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 2330.
FIGURE 2330 THE TIMES OF HEADER COMPRESSION RTP
MULTIPLEXING APPLIED WITH
Usage
Measurement Point
RTP
Unit
Times
This counter counts the average number of busy trunk circuits. If the flow becomes abnormal or is to be released normally, the common processing function of release flow is called. Also, in active-standby changeover, the ranumc process calls the function to release the standby umc database. In the above two cases, if obtaining the instance occupying circuit fails, then the counter decrements. This counter is used to find out the occupation of trunk circuits. This counter is supported in version V6.20.200a or above.
Usage
2236
Measurement Point
1. When BSC receives the release command and releases the terrestrial circuit, it attempts to obtain the instance currently occupying circuit. If the instance obtaining fails, the counter counts. The measurement point is shown in Figure 2331.
FIGURE 2331 COMMON RELEASE FLOW
2. When the standby umc releases database and A-interface terrestrial circuit, the counter counts. The measurement point is shown in Figure 2332.
FIGURE 2332 STANDBY
UMC
Unit
Times
2237
This counter counts the average number of occupied UDP ports. 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. 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 2333.
FIGURE 2333 OMS REPORTING DATA
TO
Measurement Point
DATABASE
Unit
Times
2238
Chapter
45
2239
C901390022 Number of DL UNEQUIPPED Ater CIRCUIT messages........................................................................... 2249 C901390023 Number of UL BLOCK A CIRCUIT messages........................................................................... 2250 C901390024 Number of DL BLOCKING A CIRCUIT ACKNOWLEDGE messages ............................................................ 2250 C901390025 Number of UL UNBLOCK A CIRCUIT messages........................................................................... 2250 C901390026 Number of DL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages .................................................. 2251 C901390027 Number of DL BLOCK A CIRCUIT messages........................................................................... 2251 C901390028 Number of UL BLOCKING A CIRCUIT ACKNOWLEDGE messages ............................................................ 2251 C901390029 Number of DL UNBLOCK A CIRCUIT messages........................................................................... 2252 C901390030 Number of UL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages .................................................. 2252 C901390031 Number of UL BLOCK A CIRCUIT GROUP messages........................................................................... 2252 C901390032 Number of DL BLOCK A CIRCUIT GROUP messages........................................................................... 2253 C901390033 Number of UL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages .................................................. 2253 C901390034 Number of DL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages .................................................. 2253 C901390035 Number of UL UNBLOCK A CIRCUIT GROUP messages........................................................................... 2254 C901390036 Number of DL UNBLOCK A CIRCUIT GROUP messages........................................................................... 2254 C901390037 Number of UL UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages .............................................. 2255 C901390038 Number of DL UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages .............................................. 2255 C901390039 Number of UL UNEQUIPPED A CIRCUIT messages........................................................................... 2255 C901390040 Number of DL UNEQUIPPED A CIRCUIT messages........................................................................... 2256 C901390041 Number of UL Ater RESET messages.............. 2256 C901390042 Number of DL Ater RESET messages ............. 2256 C901390043 Number of UL Ater RESET ACKNOWLEDGE messages........................................................................... 2257 C901390044 Number of DL Ater RESET ACKNOWLEDGE messages........................................................................... 2257 C901390045 Number of UL Ater CONFUSION messages........................................................................... 2257 C901390046 Number of DL Ater CONFUSION messages........................................................................... 2258 C901390047 Number of RESOURCE REQUEST messages........................................................................... 2258 C901390048 Number of RESOURCE INDICATION messages........................................................................... 2258 C901390049 Number of RESOURCE NON-INDICATION messages........................................................................... 2259 C901390050 Number of resource release request messages........................................................................... 2259 C901390051 Number of resource release acknowledge messages........................................................................... 2260 C901390052 Number of resource failure messages ............ 2260 C901390053 Number of TFO status messages ................... 2260
2240
C901390054 Number of TFO common voice type messages........................................................................... 2261 C901390055 Number of TFO control messages .................. 2261
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.
Number of UL BLOCK Ater single CIRCUIT messages This counter counts the number of BLOCK messages sent by BSC to iTC. When BSC sends a BLOCK message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of DL BLOCKING Ater single CIRCUIT ACKNOWLEDGE messages This counter counts the number of BLOCKING ACKNOWLEDGE messages received by BSC from iTC. When BSC receives a BLOCKING ACKNOWLEDGE message, this counter increments. Times ZGO-05-02-005 Flex Ater
2241
Number of UL UNBLOCK Ater single CIRCUIT messages This counter counts the number of UNBLOCK messages sent by BSC to iTC. When BSC sends an UNBLOCK message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of DL UNBLOCKING Ater single CIRCUIT ACKNOWLEDGE messages This counter counts the number of UNBLOCKING ACKNOWLEDGE messages received by BSC from iTC. When BSC receives an UNBLOCKING ACKNOWLEDGE message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of DL BLOCK Ater single CIRCUIT messages This counter counts the number of BLOCK messages received by BSC from iTC.
2242
When BSC receives a BLOCK message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of UL BLOCKING Ater single CIRCUIT ACKNOWLEDGE messages This counter counts the number of BLOCKING ACKNOWLEDGE messages sent by BSC to iTC. When BSC sends a BLOCKING ACKNOWLEDGE message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of DL UNBLOCK Ater single CIRCUIT messages This counter counts the number of UNBLOCK messages received by BSC from iTC. When BSC receives an UNBLOCK message, this counter increments. Times ZGO-05-02-005 Flex Ater
2243
Number of UL UNBLOCKING Ater single CIRCUIT ACKNOWLEDGE messages This counter counts the number of UNBLOCKING ACKNOWLEDGE messages sent by BSC to iTC. When BSC sends an UNBLOCKING ACKNOWLEDGE message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of UL RESET Ater CIRCUIT messages This counter counts the number of RESET CIRCUIT messages sent by BSC to iTC. When BSC sends a RESET CIRCUIT message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of DL RESET Ater CIRCUIT messages This counter counts the number of RESET CIRCUIT messages received by BSC from iTC.
2244
When BSC receives a RESET CIRCUIT message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of UL RESET Ater CIRCUIT ACKNOWLEDGE messages This counter counts the number of RESET CIRCUIT ACKNOWLEDGE messages sent by BSC to iTC. When BSC sends a RESET CIRCUIT ACKNOWLEDGE message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of DL RESET Ater CIRCUIT ACKNOWLEDGE messages This counter counts the number of RESET CIRCUIT ACKNOWLEDGE messages received by BSC from iTC. When BSC receives a RESET CIRCUIT ACKNOWLEDGE message, this counter increments. Times ZGO-05-02-005 Flex Ater
2245
Number of UL BLOCK Ater GROUP CIRCUIT messages This counter counts the number of BLOCK CIRCUIT GROUP messages sent by BSC to iTC. When BSC sends a BLOCK CIRCUIT GROUP message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of DL BLOCK Ater GROUP CIRCUIT messages This counter counts the number of BLOCK CIRCUIT GROUP messages received by BSC from iTC. When BSC receives a BLOCK CIRCUIT GROUP message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of UL BLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages This counter counts the number of BLOCKING CIRCUIT GROUP ACKNOWLEDGE messages sent by BSC to iTC.
2246
When BSC sends a BLOCKING CIRCUIT GROUP ACKNOWLEDGE message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of DL BLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages This counter counts the number of BLOCKING CIRCUIT GROUP ACKNOWLEDGE messages received by BSC from iTC. When BSC receives a BLOCKING CIRCUIT GROUP ACKNOWLEDGE message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of UL UNBLOCK GROUP CIRCUIT messages on Ater This counter counts the number of UL UNBLOCK GROUP CIRCUIT messages on Ater sent by BSC to iTC. When BSC sends an UL UNBLOCK GROUP CIRCUIT messages on Ater, this counter increments. Times ZGO-05-02-005 Flex Ater
2247
Number of DL UNBLOCK Ater GROUP CIRCUIT messages This counter counts the number of UNBLOCK CIRCUIT GROUP messages received by BSC from iTC. When BSC receives an UNBLOCK CIRCUIT GROUP message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of UL UNBLOCKING Ater GROUP CIRCUIT ACKNOWLEDGE messages This counter counts the number of UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE messages sent by BSC to iTC. When BSC sends an UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE message, this counter increments. Times ZGO-05-02-005 Flex Ater
2248
This counter counts the number of UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE messages received by BSC from iTC. When BSC receives an UNBLOCKING CIRCUIT GROUP ACKNOWLEDGE message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of UL UNEQUIPPED Ater CIRCUIT messages This counter counts the number of UNEQUIPPED CIRCUIT messages sent by BSC to iTC. When BSC sends an UNEQUIPPED CIRCUIT message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of DL UNEQUIPPED Ater CIRCUIT messages This counter counts the number of UNEQUIPPED CIRCUIT messages received by BSC from iTC. When BSC receives an UNEQUIPPED CIRCUIT message, this counter increments. Times ZGO-05-02-005 Flex Ater
2249
Number of UL BLOCK A CIRCUIT messages This counter counts the number of BLOCK A CIRCUIT messages sent by BSC to iTC. When BSC sends a BLOCK A CIRCUIT message, this counter increments. Times
Number of DL BLOCKING A CIRCUIT ACKNOWLEDGE messages This counter counts the number of BLOCKING A CIRCUIT ACKNOWLEDGE messages received by BSC from iTC. When BSC receives a BLOCKING A CIRCUIT ACKNOWLEDGE message, this counter increments. Times
Number of UL UNBLOCK A CIRCUIT messages This counter counts the number of UNBLOCK A CIRCUIT messages sent by BSC to iTC. When BSC sends an UNBLOCK A CIRCUIT message, this counter increments. Times
2250
Number of DL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages This counter counts the number of UNBLOCKING A CIRCUIT ACKNOWLEDGE messages received by BSC from iTC. When BSC receives an UNBLOCKING A CIRCUIT ACKNOWLEDGE message, this counter increments. Times
Number of DL BLOCK A CIRCUIT messages This counter counts the number of BLOCK A CIRCUIT messages received by BSC from iTC. When BSC receives a BLOCK A CIRCUIT message, this counter increments. Times
Number of UL BLOCKING A CIRCUIT ACKNOWLEDGE messages This counter counts the number of BLOCKING A CIRCUIT ACKNOWLEDGE messages sent by BSC to iTC. When BSC sends a BLOCKING A CIRCUIT ACKNOWLEDGE message, this counter increments. Times
2251
Number of DL UNBLOCK A CIRCUIT messages This counter counts the number of UNBLOCK A CIRCUIT messages received by BSC from iTC. When BSC receives an UNBLOCK A CIRCUIT message, this counter increments. Times
Number of UL UNBLOCKING A CIRCUIT ACKNOWLEDGE messages This counter counts the number of UNBLOCKING A CIRCUIT ACKNOWLEDGE messages sent by BSC to iTC. When BSC sends an UNBLOCKING A CIRCUIT ACKNOWLEDGE message, this counter increments. Times
Number of UL BLOCK A CIRCUIT GROUP messages This counter counts the number of BLOCK A CIRCUIT GROUP messages sent by BSC to iTC. When BSC sends a BLOCK A CIRCUIT GROUP message, this counter increments. Times
2252
Number of DL BLOCK A CIRCUIT GROUP messages This counter counts the number of BLOCK A CIRCUIT GROUP messages received by BSC from iTC. When BSC receives a BLOCK A CIRCUIT GROUP message, this counter increments. Times
Number of UL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages This counter counts the number of BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages sent by BSC to iTC. When BSC sends a BLOCKING A CIRCUIT GROUP ACKNOWLEDGE message, this counter increments. Times
Number of DL BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages This counter counts the number of BLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages received by BSC from iTC.
2253
When BSC receives a BLOCKING A CIRCUIT GROUP ACKNOWLEDGE message, this counter increments. Times
Number of UL UNBLOCK A CIRCUIT GROUP messages This counter counts the number of UNBLOCK A CIRCUIT GROUP messages sent by BSC to iTC. When BSC sends an UNBLOCK A CIRCUIT GROUP message, this counter increments. Times
Number of DL UNBLOCK A CIRCUIT GROUP messages This counter counts the number of UNBLOCK A CIRCUIT GROUP messages received by BSC from iTC. When BSC receives an UNBLOCK A CIRCUIT GROUP message, this counter increments. Times
2254
Number of UL UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages This counter counts the number of UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages sent by BSC to iTC. When BSC sends an UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE message, this counter increments. Times
Number of DL UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages This counter counts the number of UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE messages received by BSC from iTC. When BSC receives an UNBLOCKING A CIRCUIT GROUP ACKNOWLEDGE message, this counter increments. Times
Number of UL UNEQUIPPED A CIRCUIT messages This counter counts the number of UNEQUIPPED A CIRCUIT messages sent by BSC to iTC.
2255
When BSC sends an UNEQUIPPED A CIRCUIT message, this counter increments. Times
Number of DL UNEQUIPPED A CIRCUIT messages This counter counts the number of UNEQUIPPED A CIRCUIT messages received by BSC from iTC. When BSC receives an UNEQUIPPED A CIRCUIT message, this counter increments. Times
Number of UL Ater RESET messages This counter counts the number of RESET messages sent by BSC to iTC. When BSC sends a RESET message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of DL Ater RESET messages This counter counts the number of RESET messages received by BSC from iTC. When BSC receives a RESET message, this counter increments. Times
2256
Related Features
Number of UL Ater RESET ACKNOWLEDGE messages This counter counts the number of RESET ACKNOWLEDGE messages sent by BSC to iTC. When BSC sends a RESET ACKNOWLEDGE message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of DL Ater RESET ACKNOWLEDGE messages This counter counts the number of RESET ACKNOWLEDGE messages received by BSC from iTC. When BSC receives a RESET ACKNOWLEDGE message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of UL Ater CONFUSION messages This counter counts the number of CONFUSION messages sent by BSC to iTC.
2257
When BSC sends a CONFUSION message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of DL Ater CONFUSION messages This counter counts the number of CONFUSION messages received by BSC from iTC. When BSC receives a CONFUSION message, this counter increments. Times ZGO-05-02-005 Flex Ater
Number of RESOURCE REQUEST messages This counter counts the number of RESOURCE REQUEST messages sent by BSC to iTC. When BSC sends a RESOURCE REQUEST message, this counter increments. Times
2258
This counter counts the number of RESOURCE REQUEST ACKNOWLEDGE messages received by BSC from iTC. When BSC receives a RESOURCE REQUEST ACKNOWLEDGE message, this counter increments. Times
Number of RESOURCE NON-INDICATION messages This counter counts the number of RESOURCE REQUEST NEGTIVE ACKNOWLEDGE messages received by BSC from iTC. When BSC receives a RESOURCE REQUEST NEGTIVE ACKNOWLEDGE message, this counter increments. Times
Number of resource release request messages This counter counts the number of RESOURCE RELEASE REQUEST messages sent by BSC to iTC. When BSC sends a RESOURCE RELEASE REQUEST message, this counter increments. Times
2259
Number of resource release acknowledge messages This counter counts the number of RESOURCE RELEASE ACKNOWLEDGE messages received by BSC from iTC. When BSC receives a RESOURCE RELEASE ACKNOWLEDGE message, this counter increments. Times
Number of resource failure messages This counter counts the number of RESOURCE FAILURE messages received by BSC from iTC. When BSC receives a RESOURCE FAILURE message, this counter increments. Times
Number of TFO status messages This counter counts the number of TFO STATE messages received by BSC from iTC. When BSC receives a TFO STATE message, this counter increments Times
2260
Number of TFO common voice type messages This counter counts the number of TFO CONMMONTYPE messages received by BSC from iTC. When BSC receives a TFO CONMMONTYPE message, this counter increments. Times
Number of TFO control messages This counter counts the number of TFO CONTROL INFORMATION messages sent by BSC to iTC. When BSC sends a TFO CONTROL INFORMATION message, this counter increments. Times
2261
2262
Chapter
46
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.
2263
Number of error SU due to Abnormal Flag 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. This counter is used to find out the occurrence of SUs carrying seven consecutive 1s in message code stream received by an MTP2 link. When an MTP2 link receives a message code stream carrying 1111111, this counter increments. Times
Usage
Number of error SU Length Error 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.) This counter is used to find out the occurrence of SUs carrying overlong or too short messages received by an MTP2 link. When a message octet is shorter than 6 or longer than 127, this counter increments. Times
Number of Out of Alignment This counter counts the number of message code streams out of alignment received by an MTP2 link. According to the protocol,
2264
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 Measurement Point Unit
This counter is used to find out the occurrence of message code streams out of alignment received by an MTP2 link. When the flag is invalid or the length of the signal unit exceeds the maximum value, this counter increments. Times
Number of error SU due not to Octet This counter counts the times of message code streams with nonoctet received by an MTP2 link. According to the protocol, the composition of the signal unit is a multiple of 8 bits. When an octet composed of non-8 bits occurs, this counter increments. This counter is used to find out the occurrence of message code streams with non-octet received by an MTP2 link. When an octet composed of non-8 bits occurs, this counter increments. Times
Number of error SU due to CRC Error 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. This counter is used to find out the occurrence of CRC errors received by an MTP2 link. When a CRC error occurs, this counter increments. Times
2265
Number of Other error 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. This counter is used to find out the occurrence of message errors other than the above four types received by an MTP2 link. When errors other than the above four types occur, this counter increments. Times
Number of Negative Acknowledgement Received This counter counts the number of negative acknowledgements received by an MTP2 link. This counter is used to find out the occurrence of negative acknowledgements received by an MTP2 link. When an MTP2 link receives a negative acknowledgement, this counter increments. Times
Octets of MSU Retransmitted This counter counts the number of octets retransmitted by an MTP2 link. This counter is used to find out the frequency of retransmission of an MTP2 link. When an MTP2 link is retransmitted, this counter increments by the corresponding octet. octet
2266
Number of MSU Resend This counter counts the number of MSU packets resent by MTP2. This counter is used to find out the frequency of MTP2 resending. When an MTP2 link is resent, this counter increments by the corresponding number of resent packets. Packet
Number of Align Error This counter counts the number of alignment or check error of an MTP2 link. This counter is used to find out the frequency of alignment failures of an MTP2 link. When an MTP2 link receives AlignNtpsbl during alignment, this counter increments. Times
Number of Error SU This counter counts the number of error SUs received by an MTP2 link. This counter is used to find out the frequency of receiving error SUs received by an MTP2 link. When an MTP2 link receives an error SU, this counter increments. Times
2267
Number of MSU discarded due to congestion This counter counts the number of MSUs discarded due to congestion resulted from full buffer on an MTP2 link. This counter is used to find out the frequency discarding MSUs due to congestion resulted from full buffer on an MTP2 link. When an MTP2 link discards MSU due to congestion, this counter increments. Times
Number of SL failure due to Abnormal FIBR/BSNR This counter counts the number of SL failures due to abnormal FIBR/BSNR. This counter is used to find out the occurrence of SL failures due to abnormal FIBR/BSNR. When an MTP2 link is broken due to abnormal FIBBSN, this counter increments. Times
Number of SL failure due to Excessive delay of ack This counter counts the number of SL failures due to excessive delay of acknowledgement. This counter is used to find out the occurrence of SL failures due to excessive delay of acknowledgement.
2268
When an MTP2 link is broken due to excessive delay of acknowledgement, this counter increments. Times
Number of SL failure due to Excessive error rate This counter counts the number of SL failures due to excessive error rate. This counter is used to find out the occurrence of SL failures due to excessive error rate. When an MTP2 link is broken due to excessive error rate, this counter increments. Times
Number of SL failure due to Excessive duration of congestion This counter counts the number of SL failures due to excessive duration of congestion. This counter is used to find out the occurrence of SL failures due to excessive duration of congestion. When an MTP2 link is broken due to congestion, this counter increments. Times
2269
2270
Chapter
47
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.
Peak memory usage of the main processor 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. This counter is used to view the peak memory usage of the main processor in measurement period. In the sampling period, sample a memory usage every 2 seconds.
2271
Unit
Percent
Mean value of the memory usage 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. This counter is used to find out the mean memory usage of the system. In the sampling period, sample a memory usage every 2 seconds. Percent
Peak load of CPU usage of the main processor 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. This counter is used to view the peak load of CPU usage in the specified measurement period. In the sampling period, sample a CPU usage every 2 seconds and use the peak value as the maximum value of the measurement point. Percent
2272
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. This counter is used to find out the mean CPU usage in the specified period. 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. Percent
Duration of the main processor keeping in peak state This counter counts the duration of the main processor in peak state. This counter is used to find out the duration of CPU peak status, which can serve as a reference for knowing system operating conditions. 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. Second
The time when peak load CPU usage occurred 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. This counter is used to find out the time when CPU peak occurred, which provides a basis for system performance analysis. 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. Second
2273
peak kilo-bytes of the rest UB 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. This counter is used to find out the peak kilo-bytes of the rest UB. In the sampling period, do sampling at an interval of 2 seconds and get the maximum kilo-bytes of the rest UB. Byte
Mean kilo-bytes of the rest UB In the sampling period, do sampling at an interval of 2 seconds. Divide the sum of the values of all measurement points by the number of measurement points. This counter is used to find out the condition of the rest UB. At the end of a collection period, average the bytes of the rest UB sampled every 2 seconds. Byte
2274
Chapter
48
SCTP AS Measurement
Table of Contents Overview...................................................................... 2276 C901420001 Number of IP packets dropped by SCTP due to some reasons ............................................................... 2276 C901420002 Number of received SCTP packets ................. 2276 C901420003 Bytes of packets received from ip.................. 2277 C901420004 Number of packets sent to ip ........................ 2277 C901420005 Bytes of packets sent to ip ........................... 2277 C901420006 Number of messages sent to ulp ................... 2278 C901420007 Bytes of messages sent to ulp ...................... 2278 C901420008 Number of messages received from ulp.......... 2278 C901420009 Bytes of messages received from .................. 2279 C901420010 Number of Congestion ................................. 2279 C901420011 Duration of congestion................................. 2279 C901420012 Chunk number of fast retransmission............. 2280 C901420013 Chunk number of time-out retransmission ............................................................................. 2280 C901420014 RTT is lower than T1.................................... 2280 C901420015 RTT is between T1 and T2 ............................ 2281 C901420016 RTT is higher than T2 .................................. 2281 C901420017 Number of network transmission dropped packets .............................................................................. 2281 C901420018 Maximum delay of network transmission......... 2282 C901420019 Minimum delay of network transmission......... 2282 C901420020 Total delay of network transmission(high 4 bytes).......................................................................... 2283 C901420021 Total delay of network transmission(low 4 bytes).......................................................................... 2283 C901420022 Number of delay samples of network transmission ............................................................................. 2283 C901420023 Maximum dithering of network transmission ............................................................................. 2284 C901420024 Minimum dithering of network transmission ............................................................................. 2284 C901420025 Total dithering of network transmission(high 4 bytes).......................................................................... 2285 C901420026 Total dithering of network transmission(low 4 bytes).......................................................................... 2285 C901420027 Number of dithering samples of network transmission ........................................................................ 2286 C901420028 Chunks Lost On Send Dirction....................... 2286 C901420029 Chunks Trans On Send Dirction ..................... 2286 C901420030 Number of abort from peer .......................... 2287 C901420031 Number of association break by retransmission ............................................................................. 2287
2275
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).
Number of IP packets dropped by SCTP due to some reasons This counter counts the number of IP packets dropped by the SCTP, including heartbeat and SHUTDOWN. When SCTP drops packets, this counter increments. This counter is used to find out the number of packets dropped by SCTP. When SCTP drops packets, this counter will count. Times
Number of received SCTP packets This counter counts the number of IP packets received by the SCTP, including heartbeat and SHUTDOWN. When SCTP receives packets, this counter increments. This counter is used to find out the number of packets received by SCTP. When SCTP receives packets, this counter will count. Times
2276
Bytes of packets received from ip 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. This counter is used to find out the number of DATA packet bytes received by SCTP. When SCTP receives DATA packets, this counter will count. Times
Number of packets sent to ip This counter counts the number of IP packets sent by the SCTP, including heartbeat and SHUTDOWN. When SCTP sends packets, this counter increments. This counter is used to find out the number of packets sent by SCTP. When SCTP sends packets, this counter will count. Times
Bytes of packets sent to ip 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. This counter is used to find out the number of DATA packet bytes sent by SCTP. When SCTP sends DATA packets, this counter will count. Times
2277
Number of messages sent to ulp This counter counts the number of messages sent by the SCTP to ULP. When SCTP sends messages to ULP, this counter increments. This counter is used to find out the number of messages sent by SCTP to ULP. When SCTP sends messages to ULP, this counter will count. Times
Bytes of messages sent to ulp This counter counts the number of message bytes sent by the SCTP to ULP. When SCTP sends messages to ULP, this counter accumulates. This counter is used to find out the number of message bytes sent by SCTP to ULP. When SCTP sends messages to ULP, this counter will count. Times
Number of messages received from ulp This counter counts the number of message bytes received by the SCTP from ULP. When SCTP receives messages from ULP, this counter accumulates. This counter is used to find out the number of messages received by SCTP from ULP. When SCTP receives ULP messages, this counter will count. Times
2278
Bytes of messages received from ulp This counter counts the number of message bytes received by the SCTP from ULP. When SCTP receives messages from ULP, this counter accumulates. This counter is used to find out the number of message bytes received by SCTP from ULP. When SCTP receives ULP messages, this counter will count. Times
Number of Congestion This counter counts the number of congestion control module zooming out congestion windows. When congestion control module zooms out congestion windows, this counter accumulates. This counter is used to find out the number of SCTP congestions. When congestion control module zooms out congestion windows, this counter will count. Times
Duration of congestion This counter counts the congestion duration. This counter is used to find out the duration of SCTP congestion. SCTP congestion control.
2279
Unit
ms
Chunk number of fast retransmission 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. This counter is used to find out the number of chunks fast transmitted by SCTP. When SCTP fast transmits chunks, this counter will count. Times
Chunk number of time-out retransmission 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. This counter is used to find out the number of chunks fast transmitted by SCTP. When SCTP retransmits chunks due to timeout, this counter will count. Times
RTT is lower than T1 This counter counts the statistics of RTT lower than T1. When RTT is lower than T1, this counter accumulates. This counter is used to find out the statistics of RTT lower than T1. When the sampled RTT is lower than T1, this counter will counts.
2280
Unit
None
RTT is between T1 and T2 This counter counts the statistics of RTT between T1 and T2. When RTT is between T1 and T2, this counter accumulates. This counter is used to find out the statistics of RTT between T1 and T2. When the sampled RTT is between T1 and T2, this counter will count. None
RTT is higher than T2 This counter counts the statistics of RTT higher than T2. When RTT is higher than T2, this counter accumulates. This counter is used to find out the statistics of RTT higher than T2. When the sampled RTT is higher than T2, this counter will count. None
Number of network transmission dropped packets This counter counts the number of dropped packets during network transmission and chunks re-transmitted. When SCTP receives no response after sending packets, this counter counts during retransmission.
2281
This counter is used to find out the statistics of packets dropped during network transmission. If SCTP receives no response after sending packets, this counter will count during retransmission. Times ZGO-05-04-005 IP SLA Monitoring
Maximum delay of network transmission 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. This counter is used to find out the maximum delay of network transmission. When RTT is calculated based on RTO sampling, determine the maximum delay of network transmission. ms ZGO-05-04-005 IP SLA Monitoring
Minimum delay of network transmission 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. This counter is used to find out the minimum delay of network transmission. When RTT is calculated based on RTO sampling, determine the minimum delay of network transmission. ms ZGO-05-04-005 IP SLA Monitoring
2282
Total delay of network transmission (high 4 bytes) This counter counts the high 4 bytes of total delay of network transmission for processing SCTP packets. This counter is used to find out the total delay of network transmission for processing SCTP packets. When RTT is calculated based on RTO sampling, delay of network transmission is accumulated. ms ZGO-05-04-005 IP SLA Monitoring
Total delay of network transmission(low 4 bytes) This counter counts the low 4 bytes of total delay of network transmission for processing SCTP packets. This counter is used to find out the total delay of network transmission for processing SCTP packets. When RTT is calculated based on RTO sampling, delay of network transmission is accumulated. ms ZGO-05-04-005 IP SLA Monitoring
2283
Description
This counter counts the number of delay samples of network transmission. In measurement internal, each time delay is sampled, this counter accumulates. This counter is used to find out the number of delay samples in measurement interval. When a delay sampling is done in measurement interval, this counter will count. Times ZGO-05-04-005 IP SLA Monitoring
Maximum dithering of network transmission 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. This counter is used to find out the maximum dithering of network transmission. When RTT is calculated based on RTO sampling, determine the maximum dithering of network transmission. ms ZGO-05-04-005 IP SLA Monitoring
Minimum dithering of network transmission 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. This counter is used to find out the minimum dithering of network transmission.
Usage
2284
When RTT is calculated based on RTO sampling, determine the minimum dithering of network transmission. ms ZGO-05-04-005 IP SLA Monitoring
Total dithering of network transmission(high 4 bytes) This counter counts the high 4 bytes of total dithering of network transmission for processing SCTP packets. This counter is used to find out the total dithering of network transmission for processing SCTP packets. When RTT is calculated based on RTO sampling, dithering of network transmission is accumulated. ms ZGO-05-04-005 IP SLA Monitoring
Total dithering of network transmission(low 4 bytes) This counter counts the low 4 bytes of total dithering of network transmission for processing SCTP packets. This counter is used to find out the total dithering of network transmission for processing SCTP packets. When RTT is calculated based on RTO sampling, dithering of network transmission is accumulated. ms ZGO-05-04-005 IP SLA Monitoring
2285
Number of dithering samples of network transmission This counter counts the number of delay samples of network transmission. In measurement internal, each time dithering is sampled, this counter accumulates. This counter is used to find out the number of dithering samples in measurement interval. When a dithering sampling is done in measurement interval, this counter will count. Times ZGO-05-04-005 IP SLA Monitoring
This counter counts the number of data blocks retransmitted by SCTP. 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. The counter counts when the data block marked as lost by SCTP (due to retransmission timer being timeout or determined by rapid retransmission algorithm) is sent. Number of data blocks
This counter counts the number of data blocks transmitted by SCTP. 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.
2286
The counter counts when the data block is sent. Here, the data block is the one sent for the first time. Number of data blocks
This counter counts the number of link breaks due to abort initiated from the peer end. This counter is supported in version V6.20.61 or later. When the abort message is received from the peer end, the counter increments. Times
This counter counts the number of link breaks due to retransmission. This counter is supported in version V6.20.61 or later. When the link breaks due to retransmission, the counter increments. Times
2287
2288
Chapter
49
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.
Packets number received This counter counts the number of messages received at IP port. The counter increments when a message is received. This counter is used to observe the number of messages received at IP port.
2289
Packets number transmitted This counter counts the number of messages sent at IP port. The counter increments when a message is sent. This counter is used to observe the number of messages sent at IP port. The counter accumulates when there is message sent at IP port. Times
Packets number discarded at rx end 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. This counter is used to observe the number of messages discarded at the receiving end of IP port. The counter accumulates when there is incorrect message discarded at the receiving end of IP port. Times
Packets number discarded at tx end This counter counts the number of messages discarded at the transmitting end of IP port. The counter increments when an incorrect message is discarded at the transmitting end.
2290
This counter is used to observe the number of messages discarded at the transmitting end of IP port. The counter accumulates when there is incorrect message discarded at the transmitting end of IP port. Times
2291
2292
Chapter
50
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.
Maximum of used DSP TS This counter counts the maximum number of each UPU DSP timeslot resource being occupied within the measurement period. This counter is used to find out the occupation of UPU DSP timeslot resource by PS service, which helps optimize the UPU DSP resource. The counter counts when PS user requests for the UPU DSP timeslot resource successfully. Times
2293
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. 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. The counter counts when PS user requests for the UPU DSP timeslot resource successfully. Times
Usage
Amount of used DSP TS This counter accumulates at each measurement point to get the sum of UPU DSP timeslot resource used by PS service within the measurement period. This counter reflects the average occupation of UPU DSP resource in PS service. The counter counts when PS user requests for the UPU DSP timeslot resource successfully. Times
Number of regular scanning and sampling The counter increments at the measurement point of C901440003. This counter and C901440003 reflect the average occupation of UPU DSP resource in PS service.
2294
This counter reflects the average occupation of UPU DSP resource in PS service. The counter counts when PS user requests for the UPU DSP timeslot resource successfully. Times
2295
2296
Chapter
51
2297
C901450033 The length of packet latency period between 60 ms and 80 ms (80 included) in Abis ................................. 2321 C901450034 The length of packet latency period between 80 ms and 100 ms (100 included) in Abis.............................. 2321 C901450035 The length of packet latency period between 100 ms and 120 ms (120 included) in Abis.............................. 2322 C901450036 The length of packet latency period between 120 ms and 140 ms (140 included) in Abis.............................. 2322 C901450037 The length of packet latency period between 140 ms and 160 ms (160 included) in Abis.............................. 2323 C901450038 The length of packet latency period between 160 ms and 180 ms (180 included) in Abis.............................. 2323 C901450039 The length of packet latency period larger than 180 ms in Abis .............................................................. 2324 C901450040 The max length of downlink packet latency period in Gb ..................................................................... 2324 C901450041 The min length of downlink packet latency period in Gb ..................................................................... 2324 C901450042 The average length of downlink packet latency period in Gb.................................................................. 2325 C901450043 The length of downlink packet latency period between 0 and 100 ms (100 included) in Gb......................... 2325 C901450044 The length of downlink packet latency period between 100 ms and 200 ms (200 included) in Gb ................ 2326 C901450045 The length of downlink packet latency period between 200 ms and 300 ms (300 included) in Gb ................ 2326 C901450046 The length of downlink packet latency period between 300 ms and 400 ms (400 included) in Gb ................ 2327 C901450047 The length of downlink packet latency period between 400 ms and 600 ms (600 included) in Gb ................ 2327 C901450048 The length of downlink packet latency period between 600 ms and 1000 ms (1000 included) in Gb............. 2328 C901450049 The length of downlink packet latency period larger than 1000 ms in Gb .............................................. 2328 C901450050 The max length of uplink packet latency period in Gb ........................................................................... 2329 C901450051 The min length of uplink packet latency period in Gb ........................................................................... 2329 C901450052 The average length of uplink packet latency period in Gb ..................................................................... 2329 C901450053 LLC Stall Num ............................................ 2330 C901450054 MAC Resource Congestion ............................ 2330 C901450055 BSSGP Resource Congestion......................... 2330 C901450056 Number of Pushing Down Uplink BandWidth .................................................................................. 2331 C901450057 Number of Pushing Down Downlink BandWidth .................................................................................. 2331 C901450058 Number of Pushing Up Uplink BandWidth......... 2332 C901450059 Number of Pushing Up Downlink BandWidth .......................................................................... 2333
Overview
Other process measurements contain the measurement on adjustments of frame number and NACC processes.
2298
Do NACC after receiving the Packet Cell Change Notification message sent by MS at network side. SGSN sends Flush LL to BSS after receiving the uplink frame sent by the MS in reselection cell, to notify cell reselection has been successfully done by the BSS MS. It is used to measure the max duration of NACC. The NACC duration is a sampling period, starting with BSS receiving the Packet Cell Change Notification message sent by MS and ending with BSS receiving the Flush LL message sent by SGSN. The measurement point is A, as shown in Figure 2334.
FIGURE 2334 NACC DURATION
Do NACC after receiving the Packet Cell Change Notification message sent by MS at network side. SGSN sends Flush LL to BSS after receiving the uplink frame sent by the MS in reselection cell, to notify cell reselection has been successfully done by the BSS MS. It is used to measure the minimum duration of NACC.
Usage
2299
Measurement Point
Minimum time of this NACC is the minimum of all NACC periods in a sampling period.
Do NACC after receiving the Packet Cell Change Notification message sent by MS at network side. SGSN sends Flush LL to BSS after receiving the uplink frame sent by the MS in reselection cell, to notify cell reselection has been successfully done by the BSS MS. It is used to measure the total time of all successful NACCs in this cell. The measurement point is A, as shown in Figure 2336.
2300
Total time of this NACC is the sum of all NACC periods in a sampling period.
Do NACC after receiving the Packet Cell Change Notification message sent by MS at network side. SGSN sends Flush LL to BSS after receiving the uplink frame sent by the MS in reselection cell, to notify cell reselection has been successfully done by the BSS MS. It is used to measure the number of NACC success. The measurement point is A, as shown in Figure 2337.
2301
POINT OF NUMBER OF
NACC
SUCCESS
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. It is used to measure the number of NACC without receiving flush LL. The measurement point is A, as shown in Figure 2338.
2302
POINT OF NUMBER OF
NACCS
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. It is used to measure the number of UL packet channel frame adjustment. Do the measurement while the uplink frame number carried in uplink PCU frame is inconsistent with the uplink frame number recorded on the channel.
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
2303
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 Measurement Point
It is used to measure the number of DL packet channel frame adjustment. Do the measurement while the adjustment value of downlink frame number carried in uplink PCU frame is not 0 and not located in the protection period.
C901450008 Sum of C
Description
This counter counts the C value in channel quality report while DRLC receives GPRS PACKET DOWNLINK ACK or EGPRS PACKET DOWNLINK ACK. This counter measures the C value about the channel quality. For GPRS or EGPRS, this counter increments while receiving PACKET DOWNLINK ACK. The measurement point is A, as shown in Figure 2339.
FIGURE 2339 MEASUREMENT
POINT FOR THE SUM OF
Unit
None
This counter counts the RxQual value in channel quality report while DRLC receives GPRS PACKET DOWNLINK ACK. This counter measures the RxQual value about the channel quality. This counter increments while GPRS receives PACKET DOWNLINK ACK. The measurement point is A, as shown in Figure 2340.
2304
Unit
None
This counter counts the GMSK-MEAN-BEP value in channel quality report while DRLC receives EGPRS PACKET DOWNLINK ACK. This counter measures the GMSK-MEAN-BEP value about the channel quality. This counter increments when EGPRS receives PACKET DOWNLINK ACK and the GMSK_MEAN_BEP indication bit is 1 in the channel quality report. The measurement point is A, as shown in Figure 2341.
2305
Unit
None
This counter counts the GMSK-CV-BEP value in channel quality report while DRLC receives EGPRS PACKET DOWNLINK ACK. This counter measures the GMSK-CV-BEP value about the channel quality. 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 2342.
2306
Unit
None
This counter counts the 8PSK-MEAN-BEP value in channel quality report while DRLC receives EGPRS PACKET DOWNLINK ACK. This counter measures the 8PSK-MEAN-BEP value about the channel quality. 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 2343.
2307
Unit
None
This counter counts the 8PSK-CV-BEP value in channel quality report while DRLC receives EGPRS PACKET DOWNLINK ACK. This counter measures the 8PSK-CV-BEP value about the channel quality. 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 2344.
2308
Unit
None
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. This counter measures the number of C sampling points about the channel quality. For GPRS or EGPRS, this counter increments while receiving PACKET DOWNLINK ACK. The measurement point is A, as shown in Figure 2345.
2309
Unit
Times
This counter counts the number of RxQual sampling points in channel quality report while DRLC receives GPRS PACKET DOWNLINK ACK. This counter measures the number of RxQual sampling points about the channel quality. This counter increments while GPRS receives PACKET DOWNLINK ACK. The measurement point is A, as shown in Figure 2346.
2310
Unit
Times
This counter counts the number of GMSK-MEAN-BEP sampling points in channel quality report when DRLC receives EGPRS PACKET DOWNLINK ACK. This counter measures the number of GMSK-MEAN-BEP sampling points about the channel quality. 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 2347.
2311
Unit
None
This counter counts the number of GMSK-CV-BEP sampling points in channel quality report while DRLC receives EGPRS PACKET DOWNLINK ACK. This counter measures the number of GMSK-CV-BEP sampling points about the channel quality. 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 2348.
2312
Unit
Times
This counter counts the number of 8PSK-MEAN-BEP sampling points in channel quality report while DRLC receives EGPRS PACKET DOWNLINK ACK. This counter measures the number of 8PSK-MEAN-BEP sampling points about the channel quality. 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 2349.
2313
Unit
None
This counter counts the number of 8PSK-CV-BEP sampling points in channel quality report while DRLC receives EGPRS PACKET DOWNLINK ACK. This counter measures the number of 8PSK-CV-BEP sampling points about the channel quality. 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 2350.
2314
Unit
Times
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. This counter measures the number of uplink TBFs under the acknowledgement mode. This counter measures the number of TBFs when URLC receives the uplink assginment or DTM assignment and the resource assignment message shall be recorded under the acknowledgement mode. The measurement point is A, as shown in Figure 2351.
FIGURE 2351 MEASUREMENT
POINT OF
NUMBER
OF
RLC
UPLINK
ACK TBF
Unit
Times
2315
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. This counter measures the number of uplink TBFs under the unacknowledgement mode. This counter measures the number of TBFs when URLC receives the uplink assginment or DTM assignment and the resource assignment message shall be recorded under the unacknowledgement mode. The measurement point is A, as shown in Figure 2352.
FIGURE 2352 MEASUREMENT
POINT OF
NUMBER
OF
RLC
UPLINK
ACK TBF
Unit
Times
C901450022 Number of DL-UNITDATA messages with Service UTRAN CCO received by BSC
This counter is not used for the time being.
2316
Cell This counter counts the maximum delay of the cell's PS service at Abis interface within the measurement period. When the uplink frame number and downlink frame number of PS service at BSC are synchronized, the counter gets the difference between the uplink frame number and downlink frame number, thus to get the delay of PS service at Abis interface. After comparison, the counter records the maximum delay.
2317
Unit
ms
Cell This counter counts the minimum delay of the cell's PS service at Abis interface within the measurement period. When the uplink frame number and downlink frame number of PS service at BSC are synchronized, the counter gets the difference between the uplink frame number and downlink frame number, thus to get the delay of PS service at Abis interface. After comparison, the counter records the minimum delay. ms
Unit
Cell This counter counts the average delay of the cell's PS service at Abis interface within the measurement period. When the uplink frame number and downlink frame number of PS service at BSC are synchronized, the counter gets the difference between the uplink frame number and downlink frame number, thus to get the delay of PS service at Abis interface. After adding all delays and dividing the sum by the number of measurements, the counter records the average delay.
2318
Unit
ms
Cell 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. ms
Unit
C901450030 The length of packet latency period between 0 and 20 ms (20 included) in Abis
Statistics object Description
Cell This counter counts the number of samples of which the delay of the cell's PS service at Abis interface is in the range of (0, 20 ms] within the measurement period. When the uplink frame number and downlink frame number of PS service at BSC are synchronized, the counter gets the difference between the uplink frame number and downlink frame number, thus to get the delay of PS service at Abis interface. If the delay is in the range, then the counter increments. Times
Unit
2319
C901450031 The length of packet latency period between 20 ms and 40 ms (40 included) in Abis
Statistics object Description
Cell This counter counts the number of samples of which the delay of the cell's PS service at Abis interface is in the range of (20 ms, 40 ms] within the measurement period. When the uplink frame number and downlink frame number of PS service at BSC are synchronized, the counter gets the difference between the uplink frame number and downlink frame number, thus to get the delay of PS service at Abis interface. If the delay is in the range, then the counter increments. Times
Unit
C901450032 The length of packet latency period between 40 ms and 60 ms (60 included) in Abis
Statistics object Description
Cell This counter counts the number of samples of which the delay of the cell's PS service at Abis interface is in the range of (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. Times
Unit
2320
C901450033 The length of packet latency period between 60 ms and 80 ms (80 included) in Abis
Statistics object Description
Cell This counter counts the number of samples of which the delay of the cell's PS service at Abis interface is in the range of (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. Times
Unit
C901450034 The length of packet latency period between 80 ms and 100 ms (100 included) in Abis
Statistics object Description
Cell This counter counts the number of samples of which the delay of the cell's PS service at Abis interface is in the range of (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. Times
Unit
2321
C901450035 The length of packet latency period between 100 ms and 120 ms (120 included) in Abis
Statistics object Description
Cell This counter counts the number of samples of which the delay of the cell's PS service at Abis interface is in the range of (100 ms, 120 ms] within the measurement period. When the uplink frame number and downlink frame number of PS service at BSC are synchronized, the counter gets the difference between the uplink frame number and downlink frame number, thus to get the delay of PS service at Abis interface. If the delay is in the range, then the counter increments. Times
Unit
C901450036 The length of packet latency period between 120 ms and 140 ms (140 included) in Abis
Statistics object Description
Cell This counter counts the number of samples of which the delay of the cell's PS service at Abis interface is in the range of (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. Times
Unit
2322
C901450037 The length of packet latency period between 140 ms and 160 ms (160 included) in Abis
Statistics object Description
Cell This counter counts the number of samples of which the delay of the cell's PS service at Abis interface is in the range of (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. Times
Unit
C901450038 The length of packet latency period between 160 ms and 180 ms (180 included) in Abis
Statistics object Description
Cell This counter counts the number of samples of which the delay of the cell's PS service at Abis interface is in the range of (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. Times
Unit
2323
C901450039 The length of packet latency period larger than 180 ms in Abis
Statistics object Description
Cell This counter counts the number of samples of which the delay of the cell's PS service at Abis interface is in the range of (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. Times
Unit
Cell This counter counts the maximum delay of the cell's PS service in downlink transmission at Gb interface within the measurement period. At BSC, when IP packet is received at Gb interface, the downlink received time is recorded; when IP packet is sent at Gb interface, the downlink sent time is recorded. Subtract the downlink received time from the downlink sent time to get the downlink delay at Gb interface. After comparison, the counter records the maximum delay. ms
Unit
Cell 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
2324
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
Cell 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. ms
Unit
C901450043 The length of downlink packet latency period between 0 and 100 ms (100 included) in Gb
Statistics object Description
Cell 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. Times
Unit
2325
C901450044 The length of downlink packet latency period between 100 ms and 200 ms (200 included) in Gb
Statistics object Description
Cell 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. Times
Unit
C901450045 The length of downlink packet latency period between 200 ms and 300 ms (300 included) in Gb
Statistics object Description
Cell 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. Times
Unit
2326
C901450046 The length of downlink packet latency period between 300 ms and 400 ms (400 included) in Gb
Statistics object Description
Cell 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. Times
Unit
C901450047 The length of downlink packet latency period between 400 ms and 600 ms (600 included) in Gb
Statistics object Description
Cell 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. Times
Unit
2327
C901450048 The length of downlink packet latency period between 600 ms and 1000 ms (1000 included) in Gb
Statistics object Description
Cell 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. Times
Unit
C901450049 The length of downlink packet latency period larger than 1000 ms in Gb
Statistics object Description
Cell 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. Times
Unit
2328
Cell This counter counts the maximum delay of the cell's PS service in uplink transmission at Gb interface within the measurement period. At BSC, when IP packet is sent at Gb interface, the uplink sent time is recorded; when IP packet is received at Gb interface, the uplink received time is recorded. Subtract the uplink sent time from the uplink received time to get the uplink delay at Gb interface. After comparison, the counter records the maximum delay. ms
Unit
Cell This counter counts the minimum delay of the cell's PS service in uplink transmission at Gb interface within the measurement period. At BSC, when IP packet is sent at Gb interface, the uplink sent time is recorded; when IP packet is received at Gb interface, the uplink received time is recorded. Subtract the uplink sent time from the uplink received time to get the uplink delay at Gb interface. After comparison, the counter records the minimum delay. ms
Unit
Cell This counter counts the average delay of the cell's PS service in uplink transmission at Gb interface within the measurement period. At BSC, when IP packet is sent at Gb interface, the uplink sent time is recorded; when IP packet is received at Gb interface, the uplink
2329
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
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. 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. 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. Times
Usage
Measurement Point
Unit
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. 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. When BSC receives the downlink data from SGSN, if BSC fails to create the BSSGP instance, then the counter counts. Times
Usage
2330
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. 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. The counter counts when BSC user plane receives the message of pushing down uplink bandwidth. The measurement point is A, as shown in Figure 2353.
FIGURE 2353 FLOW
OF
Usage
Measurement Point
Unit
Times
This counter counts the number of pushing down downlink bandwidth in the cell. When BSC control plane judges that the actual downlink bandwidth exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool, if the current theoretically allocated downlink bandwidth of resource pool is larger than available downlink bandwidth, BSC control plane sends the message of pushing down downlink bandwidth to BSC user plane.
2331
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. The counter counts when BSC user plane receives the message of pushing down downlink bandwidth. The measurement point is A, as shown in Figure 2354.
FIGURE 2354 FLOW
OF
Measurement Point
Unit
Times
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. 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. The counter counts when BSC user plane receives the message of pushing up uplink bandwidth. The measurement point is A, as shown in Figure 2355.
Usage
Measurement Point
2332
OF
Unit
Times
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. 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. The counter counts when BSC user plane receives the message of pushing up downlink bandwidth. The measurement point is A, as shown in Figure 2356.
FIGURE 2356 FLOW
OF
Usage
Measurement Point
Unit
Times
2333
2334
Chapter
52
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.
BSC sends the "Status Enquiry" message to query BRCH's status. This counter counts the number of "Status Enquiry" messages sent by BSC. When BSC sends the "Status Enquiry" message, this counter increments. The measurement point is A1, as shown in Figure 2357.
Measurement Point
2335
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. When BSC receives the "Status" message, this counter increments. The measurement point is A2, as shown in Figure 2358.
Measurement Point
2336
During the process of querying BRCH's status between BSC and SGSN, this counter counts the number of errors occurred at N392 every N393. Check the counter's value to observe the running status of BRCH. 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 2359.
2337
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.
Check the number of bytes received on BRCH to observe the load of BRCH. FR accumulates the number of bytes received on BRCH from Gb interface.
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.
Check the number of bytes sent on BRCH to observe the load of BRCH. FR accumulates the number of bytes sent on BRCH from Gb interface.
2338
Chapter
53
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.
This counter counts the number of SUSPEND messages sent to an SGSN from site or cell within the measurement period. This counter counts the number of SUSPEND messages sent to an SGSN from site or cell in downlink within the measurement period. The counter counts when the GB_SUSPEND message is sent. Times
2339
This counter counts the number of SUSPEND-ACK messages received by site or cell from an SGSN within the measurement period. This counter counts the number of SUSPEND-ACK messages received by site or cell from an SGSN within the measurement period. The counter counts when the GB_SUSPEND_ACK message is received from SGSN. Times
Usage
This counter counts the number of SUSPEND-NACK messages received by site or cell from an SGSN within the measurement period. This counter counts the number of SUSPEND-NACK messages received by site or cell from an SGSN within the measurement period. The counter counts when the GB_SUSPEND_NACK message is received from SGSN. Times
Usage
This counter counts the number of RESUME messages sent to an SGSN from site or cell within the measurement period. This counter counts the number of RESUME messages sent to an SGSN from site or cell in downlink within the measurement period. The counter counts when the GB_RESUME message is sent. Times
2340
This counter counts the number of RESUME-ACK messages received by site or cell from an SGSN within the measurement period. This counter counts the number of RESUME-ACK messages received by site or cell from an SGSN within the measurement period. The counter counts when the GB_RESUME_ACK message is received from SGSN. Times
Usage
This counter counts the number of RESUME-NACK messages received by site or cell from an SGSN within the measurement period. This counter counts the number of RESUME-NACK messages received by site or cell from an SGSN within the measurement period. The counter counts when the GB_RESUME_NACK message is received from SGSN. Times
Usage
2341
2342
Chapter
54
2343
C901480026 Number of SNS-CHANGEWEIGHT initiated by BSC without response .................................................... 2356 C901480027 Number of SNS-CHANGEWEIGHT initiated by SGSN received successful acknowledgements.................... 2356 C901480028 Number of SNS-CHANGEWEIGHT initiated by SGSN received failed acknowledgements .......................... 2357
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.
This counter counts the number of SNS-SIZE messages sent by NSE within the measurement period. This counter counts the number of SNS-SIZE messages sent by NSE within the measurement period. 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. Times ZGO-05-04-002 Gb over IP
This counter counts the number of acknowledged responses from NSE after NSE receives the SNS-SIZE message within the measurement period. This counter counts the number of acknowledged responses from NSE after NSE receives SNS-SIZE within the measurement period.
Usage
2344
The counter counts when the EV_NSCTRL_SIZE_ACK message from SGSN is received. Times ZGO-05-04-002 Gb over IP
This counter counts the number of unacknowledged responses from NSE after NSE receives the SNS-SIZE message within the measurement period. This counter counts the number of unacknowledged responses from NSE after NSE receives SNS-SIZE within the measurement period. After the SNS-SIZE message is received, this counter counts when NSE sends response message with the cause of unavailable NSVC or unavailable IPV4. Times ZGO-05-04-002 Gb over IP
Usage
ZGO-05-04-002 Gb over IP
This counter counts the number of SNS-CONFIG messages sent by NSE within the measurement period. This counter counts the number of SNS-CONFIG messages sent by NSE within the measurement period.
2345
The counter counts after NSE sends the SNS-CONFIG message. Times ZGO-05-04-002 Gb over IP
This counter counts the number of acknowledged responses from NSE after NSE receives the SNS-CONFIG message within the measurement period. This counter counts the number of acknowledged responses from NSE after NSE receives the SNS-CONFIG message successfully within the measurement period. The counter counts when NSE returns the acknowledged response after receiving the SNS-CONFIG message. Times ZGO-05-04-002 Gb over IP
Usage
This counter counts the number of unacknowledged responses from NSE after NSE receives the SNS-CONFIG message within the measurement period. This counter counts the number of unacknowledged responses from NSE after NSE receives the SNS-CONFIG message within the measurement period. The counter counts when NSE returns the unacknowledged response after receiving the SNS-CONFIG message. Times ZGO-05-04-002 Gb over IP
Usage
2346
This counter counts the number of SNS-CONFIG messages initiated by BSC but without any response within the measurement period. This counter counts the number of SNS-CONFIG messages initiated by BSC but without any response within the measurement period. The counter counts when it is timeout during the process of waiting for NSE's response for the SNS-CONFIG message. Times ZGO-05-04-002 Gb over IP
Usage
This counter counts the number of acknowledged responses of SNS-CONFIG messages initiated by SGSN within the measurement period. This counter counts the number of acknowledged responses of SNS-CONFIG messages initiated by SGSN within the measurement period. The counter counts when the EV_NSCTRL_CONFIG_IND message is received which indicates that the IP endpoint at SGSN is recorded successfully. Times ZGO-05-04-002 Gb over IP
Usage
2347
This counter counts the number of failures of the SNS-CONFIG message initiated by SGSN within the measurement period. This counter counts the number of failures of the SNS-CONFIG message initiated by SGSN within the measurement period. The counter counts when the EV_NSCTRL_CONFIG_IND message is received which indicates that the IP endpoint at SGSN fails to be recorded. Times ZGO-05-04-002 Gb over IP
This counter counts the number of SNS-ADD messages initiated by BSC within the measurement period. This counter counts the number of SNS-ADD messages initiated by BSC within the measurement period. The counter counts when BSC sends the EV_NSOAM_ADD_REQ message. Times ZGO-05-04-002 Gb over IP
2348
This counter counts the number of acknowledged responses of the SNS-ADD message initiated by BSC within the measurement period. This counter counts the number of acknowledged responses of the SNS-ADD message initiated by BSC within the measurement period. When BSC receives the EV_NSCTRL_SNSACK_IND message with acknowledgement, the counter increments. Times ZGO-05-04-002 Gb over IP
Usage
This counter counts the number of unacknowledged responses of the SNS-ADD message initiated by BSC within the measurement period. This counter counts the number of unacknowledged responses of the SNS-ADD message initiated by BSC within the measurement period. When BSC receives the EV_NSCTRL_SNSACK_IND message with unacknowledgement, the counter increments. Times ZGO-05-04-002 Gb over IP
Usage
2349
This counter counts the number of SNS-ADD messages initiated by BSC but without any response within the measurement period. This counter counts the number of SNS-ADD messages initiated by BSC but without any response within the measurement period. The counter counts when it is timeout during the process of BSC's waiting for the response for the SNS-ADD message. Times ZGO-05-04-002 Gb over IP
This counter counts the number of acknowledged responses of SNS-ADD messages initiated by SGSN within the measurement period. This counter counts the number of acknowledged responses of SNS-ADD messages initiated by SGSN within the measurement period. The counter counts when the EV_NSCTRL_ADD_IND message is received which indicates that the IP endpoint at SGSN is recorded successfully. Times ZGO-05-04-002 Gb over IP
Usage
2350
This counter counts the number of unacknowledged responses of SNS-ADD messages initiated by SGSN within the measurement period. This counter counts the number of unacknowledged responses of SNS-ADD messages initiated by SGSN within the measurement period. The counter counts when the EV_NSCTRL_ADD_IND message is received which indicates that the IP endpoint at SGSN fails to be recorded. Times ZGO-05-04-002 Gb over IP
Usage
This counter counts the number of SNS-DELETE messages initiated by BSC within the measurement period. This counter counts the number of SNS-DELETE messages initiated by BSC within the measurement period. The counter counts when the EV_NSOAM_DELETE_REQ message is sent. Times ZGO-05-04-002 Gb over IP
2351
This counter counts the number of acknowledged responses of the SNS-DELETE message initiated by BSC within the measurement period. This counter counts the number of acknowledged responses of the SNS-DELETE message initiated by BSC within the measurement period. The counter counts when BSC receives the SNS-ACK message with acknowledgement. Times ZGO-05-04-002 Gb over IP
Usage
This counter counts the number of unacknowledged responses of the SNS-DELETE message initiated by BSC within the measurement period. This counter counts the number of unacknowledged responses of the SNS-DELETE message initiated by BSC within the measurement period. The counter counts when BSC receives the SNS-ACK message with unacknowledgement. Times ZGO-05-04-002 Gb over IP
Usage
2352
This counter counts the number of SNS-DELETE messages initiated by BSC but without any response within the measurement period. This counter counts the number of SNS-DELETE messages initiated by BSC but without any response within the measurement period. The counter counts when it is timeout during the process of BSC's waiting for the response of SNS-DELETE message. Times ZGO-05-04-002 Gb over IP
This counter counts the number of acknowledged responses of SNS-DELETE messages initiated by SGSN within the measurement period. This counter counts the number of acknowledged responses of SNS-DELETE messages initiated by SGSN within the measurement period. The counter counts when the EV_NSCTRL_DELETE_IND message is received which indicates that the IP endpoint at SGSN is recorded successfully. Times ZGO-05-04-002 Gb over IP
Usage
2353
This counter counts the number of unacknowledged responses of SNS-DELETE messages initiated by SGSN within the measurement period. This counter counts the number of unacknowledged responses of SNS-DELETE messages initiated by SGSN within the measurement period. The counter counts when the EV_NSCTRL_DELETE_IND message is received which indicates that the IP endpoint at SGSN fails to be recorded. Times ZGO-05-04-002 Gb over IP
Usage
This counter counts the number of SNS-CHANGEWEIGHT messages initiated by BSC within the measurement period. This counter counts the number of SNS-CHANGEWEIGHT messages initiated by BSC within the measurement period. The counter counts when BSC receives the EV_NSOAM_CHANGEWEIGHT_REQ message. Times ZGO-05-04-002 Gb over IP
2354
This counter counts the number of acknowledged responses of the SNS-CHANGEWEIGHT message initiated by BSC within the measurement period. This counter counts the number of acknowledged responses of the SNS-CHANGEWEIGHT message initiated by BSC within the measurement period. When BSC receives the EV_NSCTRL_SNSACK_IND message with acknowledgement, the counter increments. Times ZGO-05-04-002 Gb over IP
Usage
This counter counts the number of unacknowledged responses of the SNS-CHANGEWEIGHT message initiated by BSC within the measurement period. This counter counts the number of unacknowledged responses of the SNS-CHANGEWEIGHT message initiated by BSC within the measurement period. When BSC receives the EV_NSCTRL_SNSACK_IND message with unacknowledgement, the counter increments. Times ZGO-05-04-002 Gb over IP
Usage
2355
This counter counts the number of SNS-CHANGEWEIGHT messages initiated by BSC but without any response within the measurement period. This counter counts the number of SNS-CHANGEWEIGHT messages initiated by BSC but without any response within the measurement period. The counter counts when it is timeout during the process of BSC's waiting for the response for the SNS-CHANGEWEIGHT message. Times ZGO-05-04-002 Gb over IP
Usage
This counter counts the number of acknowledged responses of the SNS-CHANGEWEIGHT message initiated by SGSN within the measurement period. This counter counts the number of acknowledged responses of the SNS-CHANGEWEIGHT message initiated by SGSN within the measurement period. The counter counts when the EV_NSCTRL_CHANGEWEIGHT_IND message is received which indicates that the IP endpoint at SGSN is recorded successfully. Times ZGO-05-04-002 Gb over IP
Usage
2356
This counter counts the number of unacknowledged responses of the SNS-CHANGEWEIGHT message initiated by SGSN within the measurement period. This counter counts the number of unacknowledged responses of the SNS-CHANGEWEIGHT message initiated by SGSN within the measurement period. The counter counts when the EV_NSCTRL_CHANGEWEIGHT_IND message is received which indicates that the IP endpoint at SGSN fails to be recorded. Times ZGO-05-04-002 Gb over IP
Usage
2357
2358
Chapter
55
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.
ZGO-05-04-002 Gb over IP
This counter counts the number of bytes sent to SGSN from NS sub layer.
2359
Usage
The NSVC load can be checked through this counter. This counter is supported in version V6.10.100a or above. IP accumulates the number of bytes sent each time. The measurement point is A1, as shown in Figure 2360.
FIGURE 2360 UPLINK NS DATA
Measurement Point
ZGO-05-04-002 Gb over IP
ZGO-05-04-002 Gb over IP
2360
ZGO-05-04-002 Gb over IP
2361
2362
Chapter
56
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.
ZGO-05-04-002 Gb over IP
2363
ZGO-05-04-002 Gb over IP
2364
Chapter
57
Queue Measurement
Table of Contents Overview...................................................................... 2365 C901510001 Average length of queue .............................. 2365 C901510002 Duration of queuing .................................... 2366 C901510003 Number of queuing ..................................... 2368 C901510004 Duration of queuing success ......................... 2369 C901510005 Number of queuing success .......................... 2370
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.
This counter counts the average queue length that a user has to wait for after entering the queue during the assignment or handover process. The counter's value is calculated by dividing the total queue length by the number of queues. When the measurement period expires, divide the total queue length by the number of queues to calculate the counter's value. The measurement point is shown in Figure 2361.
2365
OF
AVERAGE
LENGTH OF QUEUE
Unit
Times
This counter counts the total queuing time after a user enters the queue during the assignment or handover process. When the user enters the queue, the start queuing time is recorded; when the user exits the queue, the total queuing time is calculated by subtracting the start queuing time from the current time. The counter is used to find out how busy the channels are in a cell. 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
2366
time is calculated by subtracting the start queuing time from the current time. The measurement point is B2, as shown in Figure 2362 and Figure 2363.
FIGURE 2362 MEASUREMENT POINT QUEUING FAILS
OF
QUEUING DURATION
WHEN
OF
QUEUING DURATION
WHEN
Unit
Times
2367
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. This counter is used to find out how many queuing users there are in a cell. This counter counts the number of queuing users in a cell. The counter increments every time a user exits the queue. The measurement point is B2, as shown in Figure 2364 and Figure 2365.
FIGURE 2364 MEASUREMENT POINT QUEUING FAILS
OF
QUEUING DURATION
WHEN
2368
OF
QUEUING DURATION
WHEN
Unit
Times
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. This counter is used to find out how long it takes a user to queue in the cell before acquiring the resource. 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 2366.
2369
OF
QUEUING DURATION
WHEN
Unit
Second
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. This counter is used to find out how many users successfully acquiring resource after queuing in a cell. 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 2367.
2370
OF
QUEUING DURATION
WHEN
Unit
Times
2371
2372
Chapter
58
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.
2373
FIGURE 2368 MEASUREMENT POINT OF BTS SENDING CHANNEL ACTIVATION COMPLETION MESSAGE TO BSC
This counter counts the number of synchronous handover executions after the uplink channel activation completion message is received. This counter is used to find out the number of synchronous handover executions in the cell. After BSC receives the channel activation completion message from BTS, if the handover is synchronous handover, the counter increments. Times
2374
This counter counts the number of successful synchronous handovers after the uplink handover(assignment) completion message is received. This counter is used to find out the number of successful synchronous handovers in the cell. After BSC receives the uplink handover (assignment) completion message from BTS, if the handover is synchronous handover, the counter increments. Times
This counter counts the number of pre-synchronous handover executions after the uplink channel activation completion message is received. This counter is used to find out the number of pre-synchronous handover executions in the cell. After BSC receives the channel activation completion message from BTS, if the handover is pre-synchronous handover, the counter increments. Times
This counter counts the number of successful pre-synchronous handovers after the uplink handover(assignment) completion message is received. This counter is used to find out the number of successful pre-synchronous handovers in the cell.
Usage
2375
After BSC receives the uplink handover (assignment) completion message from BTS, if the handover is pre-synchronous handover, the counter increments. Times
This counter counts the number of pseudo-synchronous handover executions after the uplink channel activation completion message is received. This counter is used to find out the number of pseudo-synchronous handover executions in the cell. After BSC receives the channel activation completion message from BTS, if the handover is pseudo-synchronous handover, the counter increments. Times
This counter counts the number of successful pseudo-synchronous handovers after the uplink handover(assignment) completion message is received. This counter is used to find out the number of successful pseudosynchronous handovers in the cell. After BSC receives the uplink handover (assignment) completion message from BTS, if the handover is pseudo-synchronous handover, the counter increments. Times
2376
This counter counts the number of asynchronous handover executions after the uplink channel activation completion message is received. This counter is used to find out the number of asynchronous handover executions in the cell. After BSC receives the channel activation completion message from BTS, if the handover is asynchronous handover, the counter increments. Times
This counter counts the number of successful asynchronous handovers after the uplink handover(assignment) completion message is received. This counter is used to find out the number of successful asynchronous handovers in the cell. After BSC receives the uplink handover (assignment) completion message from BTS, if the handover is asynchronous handover, the counter increments. Times
2377
2378
Chapter
59
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 2370 and Figure 2371.
FIGURE 2370 MEASUREMENT POINT FROM A-INTERFACE
OF
2379
OF
This counter counts the number of paging messages received by BSC from A-interface. This counter is used to find out the number of paging messages received by BSC from A-interface. When BSC receives the paging message from A-interface, the counter increments. The measurement point is A, as shown in Figure 2372.
FIGURE 2372 MEASUREMENT FROM A-INTERFACE POINT
OF
Unit
Times
2380
This counter counts the number of PS paging messages received by BSC from Gb interface. When BSC receives the PS paging message from Gb interface, the counter increments. The measurement point is A, as shown in Figure 2373.
FIGURE 2373 MEASUREMENT POINT MESSAGE FROM GB INTERFACE
OF
When BSC receives the PS paging message from Gb interface, the counter increments. The measurement point is A, as shown in Figure 2373. Times
This counter counts the number of CS paging messages received by BSC from Gb interface. When BSC receives the CS paging message from Gb interface, the counter increments. The measurement point is A, as shown in Figure 2374.
2381
OF
When BSC receives the CS paging message from Gb interface, the counter increments. The measurement point is A, as shown in Figure 2374. Times
2382
Chapter
60
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.
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.
2383
This counter is used to find out the occupation condition of reserved channels. 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. Times
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. This counter is used to find out the occupation condition of reserved channels. 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. Times
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. This counter is used to find out the occupation condition of reserved channels. 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. Times
2384
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. This counter is used to find out the occupation condition of reserved channels. 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. Times
This counter counts the total duration of reserved channels being occupied in the cell. This counter is used to find out the occupation condition of reserved channels in the cell. BSC performs statistics every 15 minutes. Second
2385
2386
Chapter
61
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.
2387
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. This counter is used to find out the number of BSC's sending the SCCP link establishment requests to MSC. When BSC sends the Connect Req message to MSC, the counter increments. The measurement point is A, as shown in Figure 2375.
FIGURE 2375 MEASUREMENT POINT SCCP CONNECTION ATTEMPTS
OF
NUMBER
OF
BSC
ORIGINATED
Unit
Times
2388
This counter counts the number of successful SCCP link establishments initiated by BSC towards MSC. This counter is used to find out the number of successful SCCP link establishments initiated by BSC towards MSC. When BSC receives the SCCP connection confirmation message from MSC, the counter increments. The measurement point is A, as shown in Figure 2376.
FIGURE 2376 MEASUREMENT POINT SCCP CONNECTION ATTEMPTS
OF
NUMBER
OF
BSC
ORIGINATED
Unit
Times
2389
This counter counts the number of SCCP link establishment failures due to timeout, and the SCCP link establishment is initiated by BSC towards MSC. 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. When the timer T9105 expires, the counter increments. Times
Usage
This counter counts the number of SCCP link establishment requests being rejected, and the SCCP link establishment is initiated by BSC towards MSC. 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. When the Rana process receives the DISCONNECT IND message from the ADispatch process, the counter increments. The measurement point is A, as shown in Figure 2377.
Usage
Measurement Point
2390
OF
NUMBER
Unit
Times
This counter counts the number of SCCP link establishment requests initiated by MSC. This counter is used to find out the number of SCCP link establishment requests initiated by MSC. When BSC receives the Connect Indication message from MSC, the counter increments. The measurement point is A, as shown in Figure 2378.
2391
OF
NUMBER
OF
MSC
ORIGINATED
Unit
Times
This counter counts the number of successful SCCP link establishments initiated by MSC. This counter is used to find out the number of successful SCCP link establishments initiated by MSC. When BSC sends the Connect Response message to MSC, the counter increments. The measurement point is A, as shown in Figure 2379.
2392
OF
NUMBER
OF
MSC
ORIGINATED
Unit
Times
2393
2394
Chapter
62
2395
C901560025 Number of DL DTM failure occurs due to handover........................................................................... 2407 C901560026 Number of successfully DL DTM establishment ........................................................................... 2408
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.
This counter counts the number of accessing voice service by mobile phone that has the DTM capability in the cell within the measurement period. This counter is used to find out the number of accessing voice service by mobile phone that has the DTM capability in the cell. The counter counts in the following three cases. 1. When BSC receives the Classmark Change message from MS, if Classmark3 carries the information that the MS has DTM multitimeslot capability, the counter increments. 2. When BSC receives the Classmark Update message from MSC, if Classmark3 carries the information that the MS has DTM multi-timeslot capability, the counter increments. 3. During inter-cell handover or external handover, when the destination cell receives the Radio Apply message, if Classmark3 carries the information that the MS has DTM multi-timeslot capability, the counter increments. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
2396
This counter counts the number of accessing packet service by mobile phone that has the DTM capability in the cell within the measurement period. This counter is used to find out the number of accessing packet service by mobile phone that has the DTM capability in the cell. 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. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
This counter counts the number of IMSIs received during link establishment in the cell within the measurement period. This counter is used to find out the number of IMSIs received during link establishment in the cell. 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. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
2397
This counter counts the number of IMSIs received by the RANCS module during intra-cell handover within the measurement period. This counter is used to find out the number of IMSIs received by the RANCS module during intra-cell handover. During inter-cell handover or external handover, when the destination cell receives the Radio Apply message which carries the IMSI information, the counter increments. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
This counter counts the number of GTTP messages sent by MS in dedicated mode in the cell within the measurement period. This counter is used to find out the number of GTTP messages sent by MS in dedicated mode in the cell. During BSC's voice service process, the counter increments when the GTTP message (GPRS information) is received from MS. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
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. This counter is used to find out the number of GTTP messages successfully sent by BSC in dedicated mode in the cell.
Usage
2398
During BSC's voice service process, when the GTTP message is received from MS and then is successfully sent to SGSN, the counter increments. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
This counter counts the number of attempts of uplink DTM service initiated by MS in dedicated mode in the cell within the measurement period. This counter is used to find out the number of attempts of uplink DTM service initiated by MS in dedicated mode in the cell. During BSC's voice service process, the counter increments when the DTM request message is received from MS. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
This counter counts the number of failed attempts of uplink DTM service in the cell within the measurement period. This counter is used to find out the number of failed attempts of uplink DTM service in the cell. 1. When BSC receives the DTM request from MS but does not process due to MS not on SDCCH, the counter increments. 2. When BSC receives the DTM request from MS but does not process because there is no Classmark3 information of the MS, the counter increments. 3. When BSC receives the DTM request from MS but finds out that the cell where MS is located does not support DTM service, the counter increments. 4. When BSC receives the DTM request from MS but does not process due to the DTM request being repeated, the counter increments. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
2399
This counter counts the number of uplink DTM service requesting for database resource successfully in dedicated mode in the cell within the measurement period. This counter is used to find out the number of uplink DTM service requesting for database resource successfully in dedicated mode in the cell. During BSC's voice service process, when the DTM request is received from MS and the resource is acquired successfully, the counter increments. Times ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-003 Full dynamic channel allocation on Um interface
Usage
This counter counts the number of failed uplink DTM service requesting for database resource in dedicated mode in the cell within the measurement period. This counter is used to find out the number of failed uplink DTM service requesting for database resource in dedicated mode in the cell. During BSC's voice service process, when the DTM request is received from MS and the resource request fails, the counter increments. Times ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-003 Full dynamic channel allocation on Um interface
Usage
2400
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. 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. 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. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
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. 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. After the intra-cell handover is completed, if BSC judges that the MS is implementing DTM service, the counter increments. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
2401
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. 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. 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. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
This counter counts the number of failed uplink DTM service due to handover in dedicated mode in the cell within the measurement period. 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. 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. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
Usage
This counter counts the number of successful uplink DTM service establishments in dedicated mode in the cell within the measurement period.
2402
This counter is used to find out the number of successful uplink DTM service establishments in dedicated mode in the cell. 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. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
This counter counts the number of attempts of sending LLC frame on FACCH in dedicated mode in the cell within the measurement period. This counter is used to find out the number of attempts of sending LLC frame on FACCH in dedicated mode in the cell. During BSC's voice service process, when the downlink LLC data frame is received in GTTP mode, the counter increments. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
This counter counts the number of successfully sending LLC frame on FACCH in dedicated mode in the cell within the measurement period. This counter is used to find out the number of successfully sending LLC frame on FACCH in dedicated mode in the cell. During BSC's voice service process, when the LLC frame is sent on FACCH in GTTP mode, the counter increments. Times
2403
Related Features
C901560018 Attempt Number of DTM established due to SGSN sent LLC packets
Description
This counter counts the number of attempts of SGSN's sending LLC frame to trigger DTM service establishment in dedicated mode in the cell within the measurement period. 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. During BSC's voice service process, when DTM service is intiated due to receiving LLC data frame sent by SGSN, the counter increments. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
Usage
This counter counts the number of failed attempts of downlink DTM service in the cell within the measurement period. This counter is used to find out the number of failed attempts of downlink DTM service in the cell. 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. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
2404
This counter counts the number of downlink DTM service requesting for database resource successfully in dedicated mode in the cell within the measurement period. This counter is used to find out the number of downlink DTM service requesting for database resource successfully in dedicated mode in the cell. 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. Times ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-003 Full dynamic channel allocation on Um interface
Usage
This counter counts the number of failed downlink DTM service requesting for database resource in dedicated mode in the cell within the measurement period. This counter is used to find out the number of failed downlink DTM service requesting for database resource in dedicated mode in the cell. 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. Times ZGO-03-02-002 Enhancement on Channel Allocation ZGO-03-02-003 Full dynamic channel allocation on Um interface
Usage
2405
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. 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. 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. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
Usage
Measurement Point
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. 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. 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. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
Usage
2406
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. 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. 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. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
This counter counts the number of failed downlink DTM service due to handover in dedicated mode in the cell within the measurement period. 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. 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. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
Usage
2407
This counter counts the number of successful downlink DTM service establishments in dedicated mode in the cell within the measurement period. This counter is used to find out the number of successful downlink DTM service establishments in dedicated mode in the cell. 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. Times ZGO-03-02-003 Full dynamic channel allocation on Um interface
2408
Chapter
63
LAPD Measurement
Table of Contents Overview...................................................................... 2410 C901570001 Number of Application Data Package from CMP............................................................................. 2410 C901570002 Number of BTS Application Data Package Sent to MP ........................................................................... 2410 C901570003 Number of Data Package Ack Sent to Application ............................................................................. 2411 C901570004 Number of Application Data Package Ack from BTS ............................................................................. 2411 C901570005 Number of Application Nack Data Package sent to BTS ......................................................................... 2411 C901570006 Number of BTS Application Nack Data Package Receive by BTS ............................................................. 2412 C901570007 Number of Sending Frame............................ 2412 C901570008 Number of Received Frame .......................... 2412 C901570009 Number of High Priority Queue overflow......... 2413 C901570010 Number of Low Priority Queue overflow ......... 2413 C901570011 Number of Success in High Priority Queue.......................................................................... 2413 C901570012 Number of Success in Low Priority Queue......... 2414 C901570013 Number of in Queue Request UB Fail ............. 2414 C901570014 Resend Number .......................................... 2414 C901570015 Resend Request Number .............................. 2415 C901570016 Establish Link Number ................................. 2416 C901570017 Broken Number .......................................... 2416 C901570018 Protocol Error Number ................................. 2417 C901570019 Number of T200 Overtime............................ 2417 C901570020 Number of T201 Overtime............................ 2418 C901570021 Number of T203 Overtime............................ 2418 C901570022 Number of T204 Overtime............................ 2418 C901570023 Number of abnormal hop frame .................... 2419 C901570024 Number of normal hop frame........................ 2419 C901570025 Multi Channel Link Lose Frame...................... 2419 C901570026 No useful channel ....................................... 2420 C901570027 Max Up Flow .............................................. 2420 C901570028 Max Down Flow .......................................... 2420 C901570029 Current Up Flow.......................................... 2421 C901570030 Current Down Flow ..................................... 2421
2409
Overview
LAPD measurement counters reflect the message transceiving condition at Abis interface between BSC and BTS. The measurement takes each LAPD link (channel cluster) as the statistics unit. It measures the transmitted data volume on LAPD link and message transceiving condition on the link, and records exceptions in LAPD protocol processing.
This counter counts the number of downlink data messages received from CMP on LAPD link. This counter is used to find out the number of service and O&M messages received from CMP on LAPD link. The counter counts when SPB receives the EV_DLDATA_REQ message from CMP.
This counter counts the number of uplink data messages sent to CMP on LAPD link. This counter is used to find out the number of service and O&M messages sent to CMP on LAPD link. The counter counts when CMP receives the EV_DLDATA_IND message from SPB.
2410
This counter counts the number of downlink I frames sent to BTS on LAPD link. This counter is used to find out the number of LAPD information frames sent to BTS on LAPD link. The counter counts when BTS receives the I frame from SPB.
This counter counts the number of uplink I frames received from BTS on LAPD link. This counter is used to find out the number of LAPD information frames received from BTS on LAPD link. The counter counts when SPB receives the I frame from BTS.
This counter counts the number of downlink UI frames sent to BTS on LAPD link. This counter is used to find out the number of LAPD unnumbered frames sent to BTS on LAPD link.
2411
Measurement Point
The counter counts when BTS receives the UI frame from SPB.
This counter counts the number of uplink UI frames received from BTS on LAPD link. This counter is used to find out the number of LAPD unnumbered frames received from BTS on LAPD link. The counter counts when SPB receives the UI frame from BTS.
This counter counts the total number of message frames sent to BTS on LAPD link, including all LAPD protocol frame types. This counter is used to find out the total number of LAPD message frames sent to BTS on LAPD link. The counter counts when BTS receives the LAPD message from SPB.
This counter counts the total number of message frames received from BTS on LAPD link, including all LAPD protocol frame types. This counter is used to find out the total number of LAPD message frames received from BTS on LAPD link. The counter counts when SPB receives the LAPD message from BTS.
2412
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.
This counter is used to find out exceptions in receiving high-priority LAPD messages from CMP on LAPD link. The counter counts when a message is discarded due to the highpriority LAPD message queue being full.
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.
This counter is used to find out exceptions in receiving low-priority LAPD messages from CMP on LAPD link. The counter counts when a message is discarded due to the lowpriority LAPD message queue being full.
This counter counts the number of high-priority LAPD message entering the queue successfully. This counter is used to find out the number of successfully receiving high-priority LAPD messages from CMP on LAPD link.
2413
Measurement Point
The counter counts when SPB receives the high-priority message from CMP.
This counter counts the number of low-priority LAPD message entering the queue successfully. This counter is used to find out the number of successfully receiving low-priority LAPD messages from CMP on LAPD link. The counter counts when SPB receives the low-priority message from CMP.
This counter counts the number of failed UB requests when receiving the high/low-priority message on LAPD link. This counter is used to find out memory request failure when receiving the high/low-priority LAPD message from CMP on LAPD link. The counter counts when UB request fails during the process of receiving the high/low-priority message on LAPD link.
Measurement Point
This counter counts the number of resending I frame on LAPD link due to T200 timeout. 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. The counter counts when I frame is resent on LAPD link due to T200 timeout. The measurement point is A, as shown in Figure 2380.
Measurement Point
2414
OF
RESENDING I FRAME
ON
LAPD
This counter counts the number of resending frame on LAPD link according to the opposite end's response. In acknowledgement transmission mode, if the opposite end returns the unacknowledgement frame after a data frame is sent, it indicates that the data frame is not correctly received. In this case, the I frame requested by the opposite end is resent on LAPD link to the opposite end.
Usage
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. The measurement point is A, as shown in Figure 2381.
Measurement Point
2415
POINT
OF
NUMBER
OF
RESENDING FRAME
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.
This counter is used to find out the number of LAPD link establishments. LAPD link establishment negotiation is completed, and the system enters multi-frame establishment status.
This counter counts the number of LAPD link breaks. This counter is used to find out the number of LAPD link breaks. The LAPD link is released, and the system enters the status of waiting for link establishment.
2416
When protocol error occurs on LAPD link, the multi-frame link protocol reports the protocol error to the layer management entity. This counter counts the number of protocol error messages received by the layer management entity. This counter is used to find out protocol errors on LAPD link. The measurement point is A, as shown in Figure 2382.
OF
NUMBER
OF
PROTOCOL ERRORS
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. 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. The counter counts when the LAPD process receives the T200 timeout message.
Usage
Measurement Point
2417
T201 defines the time limit of response for LAPD identification authentication. This counter counts the number of T201 timeout on LAPD link. 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. The counter counts when the LAPD process receives the T201 timeout message.
Usage
Measurement Point
T203 defines the maximum time allowed for no frame interaction. This counter counts the number of T203 timeout on LAPD link. 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. The counter counts when the LAPD process receives the T203 timeout message.
Measurement Point
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. 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. The counter counts when the LAPD process receives the T204 timeout message.
Usage
Measurement Point
2418
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. 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. 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.
Usage
Measurement Point
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. 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. 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.
Usage
Measurement Point
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. 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.
Measurement Point
2419
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. The counter counts when message transmission on LAPD link fails due to no available channel.
Measurement Point
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. 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. The uplink flow on LAPD link is counted every 5 minutes, and the maximum flow is recorded.
Usage
Measurement Point
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. 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. The downlink flow on LAPD link is counted every 5 minutes, and the maximum flow is recorded.
Usage
Measurement Point
2420
This counter counts the current flow of uplink messages on LAPD link. The uplink flow on LAPD link is counted every 5 minutes. 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. The current flow of uplink messages on LAPD link is recorded every 5 minutes.
Measurement Point
This counter counts the current flow of downlink messages on LAPD link. The downlink flow on LAPD link is counted every 5 minutes. 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. The current flow of downlink messages on LAPD link is recorded every 5 minutes.
Usage
Measurement Point
2421
2422
Chapter
64
LCS Measurement
Table of Contents Overview...................................................................... 2424 C901580001 Number of receiving location request in CS............................................................................... 2424 C901580002 Number of receiving location abort in CS......... 2425 C901580003 Number of TA Request in CS......................... 2425 C901580004 Number of TA Response in CS....................... 2426 C901580005 Number of MS Position Command in CS ......... 2427 C901580006 Number of MS Position Response in CS .......... 2427 C901580007 Number of location success in CS .................. 2428 C901580008 Number of location failure due to abnormal status of Lb interface in CS ................................................. 2429 C901580009 Number of location failure due to radio Timer expiration in CS............................................................. 2429 C901580010 Number of sending BSSLAP RESET message due to Intra-BSS handover in CS ........................................... 2430 C901580011 Number of location failure due to Intra-BSS handover expiration in CS .................................................... 2431 C901580012 Number of location failure due to location Timer expiration in CS............................................................. 2432 C901580013 Number of location failure due to Inter-BSS handover in CS................................................................... 2433 C901580014 Number of location failure due to call drop in CS............................................................................... 2433 C901580015 Number of location failure due to other BSC's cause in CS .................................................................. 2434 C901580016 Number of receiving location request in PS ............................................................................... 2434 C901580017 Number of receiving location abort in PS......... 2435 C901580018 Number of TA Request in PS ......................... 2436 C901580019 Number of TA Response in PS ....................... 2437 C901580020 Number of MS Position Command in PS.......... 2437 C901580021 Number of MS Position Response in PS .......... 2438 C901580022 Number of location success in PS .................. 2439 C901580023 Number of location failure due to abnormal status of Lb interface in PS ................................................. 2439 C901580024 Number of location failure due to radio Timer expiration in PS ............................................................. 2440 C901580025 Number of location failure due to Inter-CMP cell reselection in PS............................................................ 2441 C901580026 Number of sending LOCATION INFORMATION message to SMLC due to Intra-CMP cell reselection in PS ............................................................................... 2442 C901580027 Number of location failure due to location Timer expiration in PS ............................................................. 2442 C901580028 Number of location failure due to other BSC's cause in PS................................................................... 2443
2423
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.
This counter counts the number of location requests received by CS domain from the core network. The counter counts when CS domain receives the location request from the core network. The measurement point is A, as shown in Figure 2383.
FIGURE 2383 MEASUREMENT POINT REQUEST IN CS
OF
NUMBER
OF RECEIVING LOCATION
2424
This counter counts the number of location terminations received by CS domain from the core network. The counter counts when CS domain receives the location termination from the core network. The measurement point is A, as shown in Figure 2384.
FIGURE 2384 MEASUREMENT POINT OF NUMBER TERMINATIONS RECEIVED IN CS DOMAIN
OF
LOCATION
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. 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 2385.
Measurement Point
2425
OF
NUMBER
OF
TA REQUEST
IN
CS
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. 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 2386.
FIGURE 2386 MEASUREMENT POINT CS DOMAIN
OF
Measurement Point
NUMBER
OF
TA RESPONSES
IN
2426
iBSC receives the MS position command from SMLC, then the counter counts the number of MS location requests in CS domain. The counter counts when the MS position command in CS domain is received. The measurement point is A, as shown in Figure 2387.
FIGURE 2387 MEASUREMENT POINT COMMANDS IN CS DOMAIN
OF
NUMBER
OF
MS POSITION
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. The counter counts when iBSC receives the position response from MS. The measurement point is A, as shown in Figure 2388.
Measurement Point
2427
OF
NUMBER
OF
MS POSITION
This counter counts the number of location successes in CS domain. The counter counts when iBSC receives the position result from SMLC. The measurement point is A, as shown in Figure 2389.
FIGURE 2389 MEASUREMENT IN CS DOMAIN POINT
OF
NUMBER
OF
LOCATION SUCCESSES
2428
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. 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 2390.
FIGURE 2390 MEASUREMENT POINT OF NUMBER OF LOCATION FAILURE DUE TO ABNORMAL STATUS OF LB INTERFACE IN CS
Measurement Point
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. After iBSC sends the location command to MS, the radio timer starts. When the timer is timeout, the counter counts the number
Measurement Point
2429
of location failures in CS domain due to radio timer timeout. The measurement point is A, as shown in Figure 2391.
FIGURE 2391 MEASUREMENT POINT OF TO RADIO TIMER EXPIRATION IN CS NUMBER
OF LOCATION FAILURE DUE
During the MS position process, when intra-BSC handover occurs, the counter counts the number of location delays. 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 2392.
2430
OF
LOCATION DELAYS
IN
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. The counter counts when the intra-BSC handover timer is timeout in CS domain. The measurement point is A, as shown in Figure 2393.
FIGURE 2393 MEASUREMENT POINT OF NUMBER OF LOCATION FAILURES DUE TO INTRA-BSS HANDOVER TIMER TIMEOUT IN CS DOMAIN
Measurement Point
Unit
Times
2431
Related Features
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. The counter counts when the location monitoring timer is timeout. The measurement point is A, as shown in Figure 2394.
FIGURE 2394 MEASUREMENT POINT OF NUMBER OF LOCATION TO LOCATION MONITORING TIMER TIMEOUT IN CS DOMAIN FAILURE
DUE
Measurement Point
2432
When the MS position command is received from SMLC, if the external handover flow is initiated, the location will fail. 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 2395.
FIGURE 2395 MEASUREMENT POINT OF NUMBER TO INTER-BSS HANDOVER IN CS DOMAIN
OF
LOCATION FAILURE
DUE
During the location process, iBSC receives the clear command from the core network. During the location process, the counter counts when iBSC receives the clear command from the core network. The measurement point is A, as shown in Figure 2396.
2433
FIGURE DUE TO
OF
NUMBER
OF
LOCATION FAILURE
Location fails due to other causes inside iBSC, such as message sending failure between modules, requesting SCCP connection failure, and timer setting failure. The counter counts when the following problems occur: message sending failure between modules, requesting SCCP connection failure, and timer setting failure. Times ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS
This counter counts the number of location requests received by PS domain from the core network.
2434
Measurement Point
The counter counts when PS domain receives the location request from the core network. The measurement point is A, as shown in Figure 2397.
FIGURE 2397 MEASUREMENT POINT IN PS DOMAIN
OF
NUMBER
OF
LOCATION REQUESTS
This counter counts the number of location terminations received by PS domain from the core network. The counter counts when PS domain receives the location termination from the core network. The measurement point is A, as shown in Figure 2398.
2435
OF
LOCATION
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. 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 2399.
FIGURE 2399 MEASUREMENT POINT DOMAIN
OF
Measurement Point
NUMBER
OF
TA REQUESTS
IN
PS
2436
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. 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 2400.
FIGURE 2400 MEASUREMENT POINT PS DOMAIN
OF
Measurement Point
NUMBER
OF
TA RESPONSES
IN
iBSC receives the MS position command from SMLC, then the counter counts the number of MS location requests in PS domain. The counter counts when BSC receives the MS position command in PS domain. The measurement point is A, as shown in Figure 2401.
2437
OF
NUMBER
OF
MS POSITION
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. The counter counts when iBSC receives the position response from the core network. The measurement point is A, as shown in Figure 2402.
FIGURE 2402 MEASUREMENT POINT RESPONSE IN PS DOMAIN
OF
Measurement Point
NUMBER
OF
MS POSITION
2438
This counter counts the number of location successes in PS domain. The counter counts when iBSC receives the position result from SMLC. The measurement point is A, as shown in Figure 2403.
FIGURE 2403 MEASUREMENT IN PS DOMAIN POINT
OF
NUMBER
OF
LOCATION SUCCESSES
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. 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 2404.
Measurement Point
2439
FIGURE 2404 MEASUREMENT POINT OF NUMBER OF LOCATION FAILURE DUE TO ABNORMAL STATUS OF LB INTERFACE IN PS
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. After iBSC sends the location command to the core network, the radio timer starts. When the timer is timeout, the counter counts the number of location failures in PS domain due to radio timer timeout. The measurement point is A, as shown in Figure 2405.
FIGURE 2405 NUMBER OF LOCATION FAILURES RADIO TIMER TIMEOUT
IN
Measurement Point
PS
DOMAIN DUE TO
Unit
Times
2440
Related Features
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. 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 2406.
FIGURE 2406 MEASUREMENT POINT OF NUMBER OF LOCATION FAILURE TO INTER-MODULE CELL RESELECTION IN PS DOMAIN
DUE
Measurement Point
2441
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. 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 2407.
FIGURE 2407 MEASUREMENT POINT OF NUMBER OF SENDING LOCATION INFORMATION MESSAGES TO LCS DUE TO INTRA-MODULE CELL RESELECTION IN PS DOMAIN
Measurement Point
When the location request from the core network is received, the location monitoring timer starts. If the timer is timeout, this
2442
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 2408.
FIGURE 2408 MEASUREMENT POINT OF NUMBER OF LOCATION FAILURE TO LOCATION MONITORING TIMER TIMEOUT IN PS DOMAIN
DUE
Location fails due to other causes inside iBSC, such as message sending failure between modules, requesting SCCP connection failure, and timer setting failure. The counter counts when the following problems occur: message sending failure between modules, requesting SCCP connection failure, and timer setting failure. Times ZGO-01-03-002 LCS with CGI+TA ZGO-01-03-003 LCS with AGPS
2443
2444
Chapter
65
Overview
LB interface global message measurement involve counters used for evaluating the global performance and status of LB interface.
The RESET message is received at BSC from SMLC. The counter counts when the RESET message is received at BSC from SMLC. The measurement point is A, as shown in Figure 2409.
2445
OF
NUMBER
OF
RESET MESSAGES
Unit
Times
BSC receives the RESET message from SMLC. This counter counts the number of the RESET ACK messages sent to SMLC from BSC. The counter counts when the RESET ACK message is sent to SMLC from BSC. The measurement point is A, as shown in Figure 2410.
FIGURE 2410 MEASUREMENT POINT SENT TO SMLC
OF
NUMBER
OF
2446
Unit
Times
This counter counts the number of RESET messages sent to SMLC from BSC. The counter counts when the RESET message is sent to SMLC from BSC. The measurement point is A, as shown in Figure 2411.
FIGURE 2411 MEASUREMENT POINT SENT TO SMLC
OF
NUMBER
OF
RESET MESSAGES
Unit
Times
This counter counts the number of RESET ACK messages received at BSC from SMLC. The counter counts when the RESET ACK message is received at BSC from SMLC. The measurement point is A, as shown in Figure 2412.
2447
OF
NUMBER
OF
Unit
Times
2448
Chapter
66
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.
2449
This counter counts the number of 16 K relay circuits configured at Ater interface. This counter is used to find out the number of 16 K relay circuits configured at Ater interface. 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 2413.
FIGURE 2413 MEASUREMENT POINT OF RELAY CIRCUITS OF ATER INTERFACE NUMBER
OF CONFIGURED
16 K
Unit
16 K
This counter counts the average number of unavailable 16 K relay circuits at Ater interface. This counter is used to find out the average number of unavailable 16 K relay circuits at Ater interface.
2450
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 2414.
FIGURE 2414 MEASUREMENT POINT RELAY CIRCUITS OF ATER INTERFACE
OF
AVERAGE
OF UNAVAILABLE
16K
Unit
16 K
This counter counts the average number of available 16 K relay circuits at Ater interface. This counter is used to find out the average number of available 16 K relay circuits at Ater interface. 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 2415.
2451
OF
AVERAGE
OF AVAILABLE
16 K
RELAY
Unit
16 K
This counter counts the maximum number of busy 16 K relay circuits at Ater interface. This counter is used to find out the maximum number of busy 16 K relay circuits at Ater interface. iBSC queries the database periodically and saves the value obtained from the database in this counter, or the counter counts when Ater interface terrestrial circuit is released. The measurement point is A in Figure 2416 and B in Figure 2417. (Note: Figure 2417 only gives one case of Ater interface terrestrial circuit being released.)
2452
MAXIMUM
OF BUSY
16 K
RELAY
MAXIMUM
OF BUSY
16 K
RELAY
Unit
Times
This counter counts the maximum number of busy 8 K relay circuits at Ater interface. This counter is used to find out the maximum number of busy 8 K relay circuits at Ater interface.
2453
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 2418 and B in Figure 2419. (Note: Figure 2419 only gives one case of Ater interface terrestrial circuit being released.)
FIGURE 2418 MEASUREMENT CIRCUITS OF ATER INTERFACE POINT - (1)
OF
MAXIMUM
OF BUSY
8K
RELAY
POINT - (2)
OF
MAXIMUM
OF BUSY
8K
RELAY
Unit
Times
2454
This counter counts the total busy time of 16 K relay circuits at Ater interface. This counter is used to find out the total busy time of 16 K relay circuits at Ater interface. 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 2420 and B in Figure 2421. (Note: Figure 2421 only gives one case of Ater interface terrestrial circuit being released.)
FIGURE 2420 MEASUREMENT POINT CIRCUITS OF ATER INTERFACE - (1)
OF
TOTAL
BUSY TIME OF
16 K
RELAY
2455
OF
TOTAL
BUSY TIME OF
16 K
RELAY
Unit
Second
This counter counts the total busy time of 8 K relay circuits at Ater interface. This counter is used to find out the total busy time of 8 K relay circuits at Ater interface. 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 2422 and B in Figure 2423. (Note: Figure 2423 only gives one case of Ater interface terrestrial circuit being released.)
2456
TOTAL
BUSY TIME OF
8K
RELAY
TOTAL
BUSY TIME OF
8K
RELAY
Unit
Second
2457
2458
Chapter
67
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.
This counter counts the number of link establishment requests initiated by BSC towards TC. This counter is used to find out the number of link establishment requests initiated by BSC towards TC.
2459
Measurement Point
Rancs sends the TC resource request to Ater interface. The counter increments when Ater interface sends the SCCP link establishment request to iTC. The measurement point is A, as shown in Figure 2424.
FIGURE 2424 MEASUREMENT POINT REQUESTS (BSC TO TC)
OF
NUMBER
OF
SCCP
ESTABLISHMENT
Unit
Times
This counter counts the number of successful link establishments initiated by BSC towards TC. 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. When the Ater process receives the Connect Conf message from iTC, the counter increments. The measurement point is A, as shown in Figure 2425.
Measurement Point
2460
OF
NUMBER
OF
SCCP CONNECTION
Unit
Times
This counter counts the number of failed link establishments, which is due to timer timeout, initiated by BSC towards TC. When the Ater process expires at the timer TAterWaitConn, the counter increments. The measurement point is A, as shown in Figure 2426.
2461
OF
NUMBER
OF
SCCP CONNECTION
Unit
Times
This counter counts the number of rejected link establishment requests initiated by BSC towards TC. When the Ater process receives the Disconnect Ind message from the AterDispatch process, the counter increments. The measurement point is A, as shown in Figure 2427.
2462
OF
NUMBER
OF
SCCP CONNECTION
Unit
Times
2463
2464
Chapter
68
2465
C901620021 Number of samples of UL RQ=3 and receive level between 16 and 20 ........................................................ 2484 C901620022 Number of samples of UL RQ=3 and receive level between 21 and 30 ........................................................ 2485 C901620023 Number of samples of UL RQ=3 and receive level between 31 and 40 ........................................................ 2486 C901620024 Number of samples of UL RQ=3 and receive level between 41 and 63 ........................................................ 2486 C901620025 Number of samples of UL RQ=4 and receive level between 0 and 10.......................................................... 2487 C901620026 Number of samples of UL RQ=4 and receive level between 11 and 15 ........................................................ 2488 C901620027 Number of samples of UL RQ=4 and receive level between 16 and 20 ........................................................ 2489 C901620028 Number of samples of UL RQ=4 and receive level between 21 and 30 ........................................................ 2489 C901620029 Number of samples of UL RQ=4 and receive level between 31 and 40 ........................................................ 2490 C901620030 Number of samples of UL RQ=4 and receive level between 41 and 63 ........................................................ 2491 C901620031 Number of samples of UL RQ=5 and receive level between 0 and 10.......................................................... 2492 C901620032 Number of samples of UL RQ=5 and receive level between 11 and 15 ........................................................ 2492 C901620033 Number of samples of UL RQ=5 and receive level between 16 and 20 ........................................................ 2493 C901620034 Number of samples of UL RQ=5 and receive level between 21 and 30 ........................................................ 2494 C901620035 Number of samples of UL RQ=5 and receive level between 31 and 40 ........................................................ 2495 C901620036 Number of samples of UL RQ=5 and receive level between 41 and 63 ........................................................ 2495 C901620037 Number of samples of UL RQ=6 and receive level between 0 and 10.......................................................... 2496 C901620038 Number of samples of UL RQ=6 and receive level between 11 and 15 ........................................................ 2497 C901620039 Number of samples of UL RQ=6 and receive level between 16 and 20 ........................................................ 2498 C901620040 Number of samples of UL RQ=6 and receive level between 21 and 30 ........................................................ 2498 C901620041 Number of samples of UL RQ=6 and receive level between 31 and 40 ........................................................ 2499 C901620042 Number of samples of UL RQ=6 and receive level between 41 and 63 ........................................................ 2500 C901620043 Number of samples of UL RQ=7 and receive level between 0 and 10.......................................................... 2501 C901620044 Number of samples of UL RQ=7 and receive level between 11 and 15 ........................................................ 2501 C901620045 Number of samples of UL RQ=7 and receive level between 16 and 20 ........................................................ 2502 C901620046 Number of samples of UL RQ=7 and receive level between 21 and 30 ........................................................ 2503 C901620047 Number of samples of UL RQ=7 and receive level between 31 and 40 ........................................................ 2504 C901620048 Number of samples of UL RQ=7 and receive level between 41 and 63 ........................................................ 2504 C901620049 Number of samples of DL RQ=0 and receive level between 0 and 10.......................................................... 2505 C901620050 Number of samples of DL RQ=0 and receive level between 11 and 15 ........................................................ 2506
2466
C901620051 Number of samples of DL RQ=0 and receive level between 16 and 20 ........................................................ 2507 C901620052 Number of samples of DL RQ=0 and receive level between 21 and 30 ........................................................ 2507 C901620053 Number of samples of DL RQ=0 and receive level between 31 and 40 ........................................................ 2508 C901620054 Number of samples of DL RQ=0 and receive level between 41 and 63 ........................................................ 2509 C901620055 Number of samples of DL RQ=1 and receive level between 0 and 10.......................................................... 2510 C901620056 Number of samples of DL RQ=1 and receive level between 11 and 15 ........................................................ 2510 C901620057 Number of samples of DL RQ=1 and receive level between 16 and 20 ........................................................ 2511 C901620058 Number of samples of DL RQ=1 and receive level between 21 and 30 ........................................................ 2512 C901620059 Number of samples of DL RQ=1 and receive level between 31 and 40 ........................................................ 2513 C901620060 Number of samples of DL RQ=1 and receive level between 41 and 63 ........................................................ 2513 C901620061 Number of samples of DL RQ=2 and receive level between 0 and 10.......................................................... 2514 C901620062 Number of samples of DL RQ=2 and receive level between 11 and 15 ........................................................ 2515 C901620063 Number of samples of DL RQ=2 and receive level between 16 and 20 ........................................................ 2516 C901620064 Number of samples of DL RQ=2 and receive level between 21 and 30 ........................................................ 2516 C901620065 Number of samples of DL RQ=2 and receive level between 31 and 40 ........................................................ 2517 C901620066 Number of samples of DL RQ=2 and receive level between 41 and 63 ........................................................ 2518 C901620067 Number of samples of DL RQ=3 and receive level between 0 and 10.......................................................... 2519 C901620068 Number of samples of DL RQ=3 and receive level between 11 and 15 ........................................................ 2519 C901620069 Number of samples of DL RQ=3 and receive level between 16 and 20 ........................................................ 2520 C901620070 Number of samples of DL RQ=3 and receive level between 21 and 30 ........................................................ 2521 C901620071 Number of samples of DL RQ=3 and receive level between 31 and 40 ........................................................ 2522 C901620072 Number of samples of DL RQ=3 and receive level between 41 and 63 ........................................................ 2522 C901620073 Number of samples of DL RQ=4 and receive level between 0 and 10.......................................................... 2523 C901620074 Number of samples of DL RQ=4 and receive level between 11 and 15 ........................................................ 2524 C901620075 Number of samples of DL RQ=4 and receive level between 16 and 20 ........................................................ 2525 C901620076 Number of samples of DL RQ=4 and receive level between 21 and 30 ........................................................ 2525 C901620077 Number of samples of DL RQ=4 and receive level between 31 and 40 ........................................................ 2526 C901620078 Number of samples of DL RQ=4 and receive level between 41 and 63 ........................................................ 2527 C901620079 Number of samples of DL RQ=5 and receive level between 0 and 10.......................................................... 2528 C901620080 Number of samples of DL RQ=5 and receive level between 11 and 15 ........................................................ 2528
2467
C901620081 Number of samples of DL RQ=5 and receive level between 16 and 20 ........................................................ 2529 C901620082 Number of samples of DL RQ=5 and receive level between 21 and 30 ........................................................ 2530 C901620083 Number of samples of DL RQ=5 and receive level between 31 and 40 ........................................................ 2531 C901620084 Number of samples of DL RQ=5 and receive level between 41 and 63 ........................................................ 2531 C901620085 Number of samples of DL RQ=6 and receive level between 0 and 10.......................................................... 2532 C901620086 Number of samples of DL RQ=6 and receive level between 11 and 15 ........................................................ 2533 C901620087 Number of samples of DL RQ=6 and receive level between 16 and 20 ........................................................ 2534 C901620088 Number of samples of DL RQ=6 and receive level between 21 and 30 ........................................................ 2534 C901620089 Number of samples of DL RQ=6 and receive level between 31 and 40 ........................................................ 2535 C901620090 Number of samples of DL RQ=6 and receive level between 41 and 63 ........................................................ 2536 C901620091 Number of samples of DL RQ=7 and receive level between 0 and 10.......................................................... 2537 C901620092 Number of samples of DL RQ=7 and receive level between 11 and 15 ........................................................ 2537 C901620093 Number of samples of DL RQ=7 and receive level between 16 and 20 ........................................................ 2538 C901620094 Number of samples of DL RQ=7 and receive level between 21 and 30 ........................................................ 2539 C901620095 Number of samples of DL RQ=7 and receive level between 31 and 40 ........................................................ 2540 C901620096 Number of samples of DL RQ=7 and receive level between 41 and 63 ........................................................ 2540
2468
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. This counter is used to find out radio channel's UL quality and receive level. This counter counts when BSC receives the UL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which UL RQ=0 and receive level is between 0 and 10. The measurement point is A, as shown in Figure 2429.
FIGURE 2429 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2469
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. This counter is used to find out radio channel's UL quality and receive level. 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 2430.
FIGURE 2430 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2470
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 Measurement Point
This counter is used to find out radio channel's UL quality and receive level. 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 2431.
FIGURE 2431 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2432.
2471
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2433.
FIGURE 2433 MEASUREMENT POINT REPORT TO BSC
OF
2472
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2434.
FIGURE 2434 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2473
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. This counter is used to find out radio channel's UL quality and receive level. 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 2435.
FIGURE 2435 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2474
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 Measurement Point
This counter is used to find out radio channel's UL quality and receive level. 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 2436.
FIGURE 2436 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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 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. This counter is used to find out radio channel's UL quality and receive level. 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 2437.
2475
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2438.
FIGURE 2438 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2476
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. This counter is used to find out radio channel's UL quality and receive level. 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 2439.
FIGURE 2439 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2477
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 Measurement Point
This counter is used to find out radio channel's UL quality and receive level. 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 2440.
FIGURE 2440 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2441.
2478
OF
Unit
Times
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 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. This counter is used to find out radio channel's UL quality and receive level. 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 2442.
FIGURE 2442 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2479
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. This counter is used to find out radio channel's UL quality and receive level. 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 2443.
FIGURE 2443 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2480
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 Measurement Point
This counter is used to find out radio channel's UL quality and receive level. 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 2444.
FIGURE 2444 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2445.
2481
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2446.
FIGURE 2446 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2482
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 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. This counter is used to find out radio channel's UL quality and receive level. 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 2447.
FIGURE 2447 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2483
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 Measurement Point
This counter is used to find out radio channel's UL quality and receive level. 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 2448.
FIGURE 2448 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2449.
2484
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2450.
FIGURE 2450 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2485
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. This counter is used to find out radio channel's UL quality and receive level. 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 2451.
FIGURE 2451 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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 measurement report).
2486
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 Measurement Point
This counter is used to find out radio channel's UL quality and receive level. 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 2452.
FIGURE 2452 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2453.
2487
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2454.
FIGURE 2454 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2488
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. This counter is used to find out radio channel's UL quality and receive level. 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 2455.
FIGURE 2455 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2489
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 Measurement Point
This counter is used to find out radio channel's UL quality and receive level. 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 2456.
FIGURE 2456 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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 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. This counter is used to find out radio channel's UL quality and receive level. 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 2457.
2490
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2458.
FIGURE 2458 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2491
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. This counter is used to find out radio channel's UL quality and receive level. 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 2459.
FIGURE 2459 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2492
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 Measurement Point
This counter is used to find out radio channel's UL quality and receive level. 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 2460.
FIGURE 2460 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2461.
2493
OF
Unit
Times
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 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. This counter is used to find out radio channel's UL quality and receive level. 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 2462.
FIGURE 2462 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2494
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. This counter is used to find out radio channel's UL quality and receive level. 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 2463.
FIGURE 2463 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2495
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 Measurement Point
This counter is used to find out radio channel's UL quality and receive level. 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 2464.
FIGURE 2464 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2465.
2496
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2466.
FIGURE 2466 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2497
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 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. This counter is used to find out radio channel's UL quality and receive level. 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 2467.
FIGURE 2467 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2498
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 Measurement Point
This counter is used to find out radio channel's UL quality and receive level. 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 2468.
FIGURE 2468 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2469.
2499
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2470.
FIGURE 2470 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2500
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. This counter is used to find out radio channel's UL quality and receive level. 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 2471.
FIGURE 2471 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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 measurement report).
2501
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 Measurement Point
This counter is used to find out radio channel's UL quality and receive level. 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 2472.
FIGURE 2472 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2473.
2502
OF
Unit
Times
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. This counter is used to find out radio channel's UL quality and receive level. 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 2474.
FIGURE 2474 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2503
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. This counter is used to find out radio channel's UL quality and receive level. 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 2475.
FIGURE 2475 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2504
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 Measurement Point
This counter is used to find out radio channel's UL quality and receive level. 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 2476.
FIGURE 2476 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
This counter counts the number of samples of DL RQ=0 and receive level between 0 and 10 in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter increments when BSC receives the DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) in which DL RQ=0 and receive level is between 0 and 10. This counter is used to find out radio channel's DL quality and receive level. 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 2477.
2505
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2478.
FIGURE 2478 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2506
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. This counter is used to find out radio channel's DL quality and receive level. 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 2479.
FIGURE 2479 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2507
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 Measurement Point
This counter is used to find out radio channel's DL quality and receive level. 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 2480.
FIGURE 2480 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2481.
2508
OF
Unit
Times
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 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. This counter is used to find out radio channel's DL quality and receive level. 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 2482.
FIGURE 2482 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2509
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. This counter is used to find out radio channel's DL quality and receive level. 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 2483.
FIGURE 2483 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2510
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 Measurement Point
This counter is used to find out radio channel's DL quality and receive level. 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 2484.
FIGURE 2484 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2485.
2511
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2486.
FIGURE 2486 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2512
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 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. This counter is used to find out radio channel's DL quality and receive level. 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 2487.
FIGURE 2487 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2513
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 Measurement Point
This counter is used to find out radio channel's DL quality and receive level. 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 2488.
FIGURE 2488 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2489.
2514
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2490.
FIGURE 2490 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2515
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. This counter is used to find out radio channel's DL quality and receive level. 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 2491.
FIGURE 2491 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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 measurement report).
2516
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 Measurement Point
This counter is used to find out radio channel's DL quality and receive level. 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 2492.
FIGURE 2492 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2493.
2517
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2494.
FIGURE 2494 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2518
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. This counter is used to find out radio channel's DL quality and receive level. 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 2495.
FIGURE 2495 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2519
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 Measurement Point
This counter is used to find out radio channel's DL quality and receive level. 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 2496.
FIGURE 2496 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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 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. This counter is used to find out radio channel's DL quality and receive level. 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 2497.
2520
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2498.
FIGURE 2498 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2521
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. This counter is used to find out radio channel's DL quality and receive level. 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 2499.
FIGURE 2499 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2522
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 Measurement Point
This counter is used to find out radio channel's DL quality and receive level. 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 2500.
FIGURE 2500 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2501.
2523
OF
Unit
Times
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 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. This counter is used to find out radio channel's DL quality and receive level. 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 2502.
FIGURE 2502 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2524
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. This counter is used to find out radio channel's DL quality and receive level. 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 2503.
FIGURE 2503 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2525
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 Measurement Point
This counter is used to find out radio channel's DL quality and receive level. 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 2504.
FIGURE 2504 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2505.
2526
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2506.
FIGURE 2506 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2527
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 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. This counter is used to find out radio channel's DL quality and receive level. 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 2507.
FIGURE 2507 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2528
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 Measurement Point
This counter is used to find out radio channel's DL quality and receive level. 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 2508.
FIGURE 2508 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2509.
2529
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2510.
FIGURE 2510 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2530
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. This counter is used to find out radio channel's DL quality and receive level. 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 2511.
FIGURE 2511 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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 measurement report).
2531
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 Measurement Point
This counter is used to find out radio channel's DL quality and receive level. 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 2512.
FIGURE 2512 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2513.
2532
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2514.
FIGURE 2514 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2533
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. This counter is used to find out radio channel's DL quality and receive level. 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 2515.
FIGURE 2515 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2534
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 Measurement Point
This counter is used to find out radio channel's DL quality and receive level. 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 2516.
FIGURE 2516 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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 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. This counter is used to find out radio channel's DL quality and receive level. 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 2517.
2535
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2518.
FIGURE 2518 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2536
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. This counter is used to find out radio channel's DL quality and receive level. 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 2519.
FIGURE 2519 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2537
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 Measurement Point
This counter is used to find out radio channel's DL quality and receive level. 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 2520.
FIGURE 2520 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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. This counter is used to find out radio channel's DL quality and receive level. 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 2521.
2538
OF
Unit
Times
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 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. This counter is used to find out radio channel's DL quality and receive level. 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 2522.
FIGURE 2522 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2539
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. This counter is used to find out radio channel's DL quality and receive level. 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 2523.
FIGURE 2523 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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).
2540
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 Measurement Point
This counter is used to find out radio channel's DL quality and receive level. 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 2524.
FIGURE 2524 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2541
2542
Chapter
69
2543
OF
This counter counts the number of samples with DL level in local cell subtracting the level in adjacent cell < -10dB in received DL radio measurement report (preprocessing report or enhanced preprocessing measurement report). This counter is used to find out DL level of adjacent cell. This counter increments while DL level in this cell in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) received by BSC subtracting the level of adjacent cell is lower than 10dB, as shown in Figure 2526.
FIGURE 2526 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2544
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). This counter is used to find out DL level of adjacent cell. This counter increments while DL level in this cell in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) received by BSC subtracting the level of adjacent cell is within -9dB~-5dB, as shown in Figure 2527.
FIGURE 2527 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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). This counter is used to find out DL level of adjacent cell. This counter increments while DL level in this cell in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) received by BSC subtracting the level of adjacent cell is within -4dB~0dB, as shown in Figure 2528.
2545
OF
Unit
Times
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). This counter is used to find out DL level of adjacent cell. This counter increments while DL level in this cell in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) received by BSC subtracting the level of adjacent cell is within 1dB~5dB, as shown in Figure 2529.
FIGURE 2529 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2546
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). This counter is used to find out DL level of adjacent cell. This counter increments while DL level in this cell in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) received by BSC subtracting the level of adjacent cell is within 6dB~10dB, as shown in Figure 2530.
FIGURE 2530 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
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). This counter is used to find out DL level of adjacent cell. This counter increments while DL level in this cell in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) received by BSC subtracting the level of adjacent cell is within 11dB~15dB, as shown in Figure 2531.
2547
OF
Unit
Times
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). This counter is used to find out DL level of adjacent cell. This counter increments while DL level in this cell in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) received by BSC subtracting the level of adjacent cell is within 16dB~20dB, as shown in Figure 2532.
FIGURE 2532 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2548
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). This counter is used to find out DL level of adjacent cell. This counter increments while DL level in this cell in DL radio measurement report (preprocessing report or enhanced preprocessing measurement report) received by BSC subtracting the level of adjacent cell is higher than 20dB, as shown in Figure 2533.
FIGURE 2533 MEASUREMENT POINT REPORT TO BSC
OF
Unit
Times
2549
2550
Chapter
70
Overview
The paging measurement measures the usage of paging channel queue and the number of failures in receiving paging message due to the paging message queue being full. It measures the paging performance data of base station, including the average length of paging queue at base station and the number of discarded paging messages due to the queue being full. Figure 2534 shows the paging performance measurement flow.
2551
This counter counts the number of PS paging messages discarded due to the queue being full. 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. The counter's value is obtained by querying database when the paging performance measurement data is reported periodically. Times
This counter counts the number of CS paging messages discarded due to the queue being full. 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.
2552
The counter's value is obtained by querying database when the paging performance measurement data is reported periodically. Times
This counter counts the occupancy of PCH message buffer queue which saves paging messages according to 2~9 51-multiframe mode at BTS. 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. The counter's value is obtained by querying database when the paging performance measurement data is reported periodically. Times
Usage
This counter counts the occupancy of PCH message buffer queue which saves paging messages according to 64 51-multiframe mode at BTS. 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. This counter is supported in version V6.20.200a or above. The counter's value is obtained by querying database when the paging performance measurement data is reported periodically. Times
Usage
2553
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. Percent Cell
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. Times Cell
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. Times
Unit
2554
Statistics Object
Cell
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. Times Cell
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. Times Cell
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. Times
Unit
2555
Statistics Object
Cell
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. Times Cell
2556
Chapter
71
Overview
The temperature and power of TRX are measured on TRU and reported to BSC periodically.
This counter counts the maximum value of TRX's power within the measurement period. SDR base station does not support the measurement. TRU is measured and reported periodically. dbm
2557
This counter counts the minimum value of TRX's power within the measurement period. SDR base station does not support the measurement. TRU is measured and reported periodically. dbm
This counter counts the average value of TRX's power within the measurement period. SDR base station does not support the measurement. TRU is measured and reported periodically. dbm
This counter counts the maximum value of TRX's temperature within the measurement period. SDR base station does not support the measurement. TRU is measured and reported periodically. Celsius
This counter counts the minimum value of TRX's temperature within the measurement period.
2558
This counter counts the average value of TRX's temperature within the measurement period. SDR base station does not support the measurement. TRU is measured and reported periodically. Celsius
2559
2560
Chapter
72
2561
C901660023 Number of mobile of GPRS multi TS ability 6................................................................................. 2588 C901660024 Number of mobile of GPRS multi TS ability 7................................................................................. 2590 C901660025 Number of mobile of GPRS multi TS ability 8................................................................................. 2592 C901660026 Number of mobile of GPRS multi TS ability 9................................................................................. 2593 C901660027 Number of mobile of GPRS multi TS ability 10 ............................................................................... 2595 C901660028 Number of mobile of GPRS multi TS ability 11 ............................................................................... 2597 C901660029 Number of mobile of GPRS multi TS ability 12 ............................................................................... 2598 C901660030 Number of mobile of GPRS multi TS ability 30 ............................................................................... 2600 C901660031 Number of mobile of GPRS multi TS ability 31 ............................................................................... 2602 C901660032 Number of mobile of GPRS multi TS ability 32 ............................................................................... 2603 C901660033 Number of mobile of GPRS multi TS ability 33 ............................................................................... 2605 C901660034 Number of mobile of GPRS multi TS ability 34 ............................................................................... 2607 C901660035 Number of mobile of EGPRS multi TS ability 1................................................................................. 2608 C901660036 Number of mobile of EGPRS multi TS ability 2................................................................................. 2610 C901660037 Number of mobile of EGPRS multi TS ability 3................................................................................. 2612 C901660038 Number of mobile of EGPRS multi TS ability 4................................................................................. 2613 C901660039 Number of mobile of EGPRS multi TS ability 5................................................................................. 2615 C901660040 Number of mobile of EGPRS multi TS ability 6................................................................................. 2617 C901660041 Number of mobile of EGPRS multi TS ability 7................................................................................. 2618 C901660042 Number of mobile of EGPRS multi TS ability 8................................................................................. 2620 C901660043 Number of mobile of EGPRS multi TS ability 9................................................................................. 2622 C901660044 Number of mobile of EGPRS multi TS ability 10 ............................................................................... 2623 C901660045 Number of mobile of EGPRS multi TS ability 11 ............................................................................... 2625 C901660046 Number of mobile of EGPRS multi TS ability 12 ............................................................................... 2627 C901660047 Number of mobile of EGPRS multi TS ability 30 ............................................................................... 2628 C901660048 Number of mobile of EGPRS multi TS ability 31 ............................................................................... 2630 C901660049 Number of mobile of EGPRS multi TS ability 32 ............................................................................... 2632 C901660050 Number of mobile of EGPRS multi TS ability 33 ............................................................................... 2633 C901660051 Number of mobile of EGPRS multi TS ability 34 ............................................................................... 2635 C901660052 Number of mobile support FR ....................... 2637 C901660053 Number of mobile support HR....................... 2637
2562
C901660054 Number of mobile support EFR ..................... 2638 C901660055 Number of mobile support AMRFR ................. 2639 C901660056 Number of mobile support AMRHR................. 2639 C901660057 Number of mobile support wideband AMROFR ........................................................................... 2640 C901660058 Number of mobile support wideband AMRFR ............................................................................. 2641 C901660059 Number of mobile support wideband AMROHR .......................................................................... 2642 C901660060 Number of mobile support AMROHR .............. 2643 C901660061 Number of mobile support extend uplink TBF ............................................................................. 2644 C901660062 Number of mobile support NACC ................... 2645 C901660063 Number of mobile support GPRS extend dynamic allocation ..................................................................... 2646 C901660064 Number of mobile support EGPRS extend dynamic allocation ............................................................ 2647 C901660065 Number of sampling received Classmark3.......................................................................... 2648 C901660066 Number of sampling received radio access ability ............................................................................... 2649 C901660069 Num of MS supporting PS handover............... 2650 C901660070 The Number of MS which Support SAIC.......... 2651 C901660071 The Number of MS which not Support SAIC............................................................................ 2652
This counter counts the number of mobiles that support the capability of single TS DTM. This counter measures the number of mobiles that support the single TS DTM ability. This counter increments while Rancs receives the Classmark Update message delivered by MSC or the Classmark Change message sent by MS and the message indicates the MS supports the single TS DTM ability. The measurement point is A1 or A2, as shown in Figure 2535.
2563
POINT
OF
NUMBER
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support DTM GPRS multi TS ability 5. It is used to measure the number of mobiles that support DTM GPRS multi TS ability 5. 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.
2564
OF
NUMBER
OF MOBILE SUPPORT
DTM
Unit
Times
This counter counts the number of mobiles that support DTM GPRS multi TS ability 9. It is used to measure the number of mobiles that support DTM GPRS multi TS ability 9. 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 2537.
2565
OF
NUMBER
OF MOBILE SUPPORT
DTM
Unit
Times
This counter counts the number of mobiles that support DTM GPRS multi TS ability 11. It is used to measure the number of mobiles that support DTM GPRS multi TS ability 11. 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 2538.
2566
OF
NUMBER
OF MOBILE SUPPORT
DTM
Unit
Times
This counter counts the number of mobiles that support DTM EGPRS multi TS ability 5. It is used to measure the number of mobiles that support DTM EGPRS multi TS ability 5. 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 2539.
2567
OF
NUMBER
OF MOBILE SUPPORT
DTM
Unit
Times
This counter counts the number of mobiles that support DTM EGPRS multi TS ability 9. It is used to measure the number of mobiles that support DTM EGPRS multi TS ability 9. 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 2540.
2568
OF
NUMBER
OF MOBILE SUPPORT
DTM
Unit
Times
This counter counts the number of mobiles that support DTM EGPRS multi TS ability 11. It is used to measure the number of mobiles that support DTM EGPRS multi TS ability 11. 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 2541.
2569
OF
NUMBER
OF MOBILE SUPPORT
DTM
Unit
Times
This counter counts the number of mobiles that support extend DTM GPRS multi TS ability 5. It is used to measure the number of mobiles that support extend DTM GPRS multi TS ability 5. 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 2542.
2570
FIGURE EXTEND
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support extend DTM GPRS multi TS ability 6. It is used to measure the number of mobiles that support extend DTM GPRS multi TS ability 6. 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 2543.
2571
FIGURE EXTEND
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support extend DTM GPRS multi TS ability 9. It is used to measure the number of mobiles that support extend DTM GPRS multi TS ability 9. 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 2544.
2572
FIGURE EXTEND
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support extend DTM GPRS multi TS ability 10. It is used to measure the number of mobiles that support extend DTM GPRS multi TS ability 10. 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 2545.
2573
FIGURE EXTEND
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support extend DTM GPRS multi TS ability 11. It is used to measure the number of mobiles that support extend DTM GPRS multi TS ability 11. 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 2546.
2574
FIGURE EXTEND
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support extend DTM EGPRS multi TS ability 5. It is used to measure the number of mobiles that support extend DTM EGPRS multi TS ability 5. 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 2547.
2575
FIGURE EXTEND
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support extend DTM EGPRS multi TS ability 6. It is used to measure the number of mobiles that support extend DTM EGPRS multi TS ability 6. 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 2548.
2576
FIGURE EXTEND
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support extend DTM EGPRS multi TS ability 9. It is used to measure the number of mobiles that support extend DTM EGPRS multi TS ability 9. 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 2549.
2577
FIGURE EXTEND
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support extend DTM EGPRS multi TS ability 10. It is used to measure the number of mobiles that support extend DTM EGPRS multi TS ability 10. 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 2550.
2578
FIGURE EXTEND
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support extend DTM EGPRS multi TS ability 11. It is used to measure the number of mobiles that support extend DTM EGPRS multi TS ability 11. 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 2551.
2579
FIGURE EXTEND
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support GPRS multi TS ability 1. It is used to measure the number of mobiles that support GPRS multi TS ability 1. This counter increments while PS control plane receives the downlink assignment requests sent by the user plane, the resource requests sent by the user plane on two-phase access, or the instance setup indication sent by the user plane and the message indicates the MS supports GPRS multi TS ability 1. The measurement point is A1, A2, and A3, as shown in Figure 2552, Figure 2553, Figure 2554.
2580
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
2581
Unit
Times
This counter counts the number of mobiles that support GPRS multi TS ability 2. It is used to measure the number of mobiles that support GPRS multi TS ability 2. 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 2555, Figure 2556, Figure 2557.
FIGURE 2555 MEASUREMENT MULTI TS ABILITY 2 - (1) POINT
OF
NUMBER
OF MOBILE OF
GPRS
2582
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
This counter counts the number of mobiles that support GPRS multi TS ability 3. It is used to measure the number of mobiles that support GPRS multi TS ability 3. This counter increments while PS control plane receives the downlink assignment requests sent by the user plane, the resource re-
2583
quests sent by the user plane on two-phase access, or the instance setup indication sent by the user plane and the message indicates the MS supports GPRS multi TS ability 3. The measurement point is A1, A2, and A3, as shown in Figure 2558, Figure 2559, Figure 2560.
FIGURE 2558 MEASUREMENT MULTI TS ABILITY 3 - (1) POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
2584
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
This counter counts the number of mobiles that support GPRS multi TS ability 4. It is used to measure the number of mobiles that support GPRS multi TS ability 4. 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 2561, Figure 2562, Figure 2563.
2585
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
2586
This counter counts the number of mobiles that support GPRS multi TS ability 5. This counter is used to measure the number of link setup requests originated from BSC to TC. 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 2564, Figure 2565, Figure 2566.
FIGURE 2564 MEASUREMENT MULTI TS ABILITY 5 - (1) POINT
OF
NUMBER
OF MOBILE OF
GPRS
2587
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
This counter counts the number of mobiles that support GPRS multi TS ability 6. It is used to measure the number of mobiles that support GPRS multi TS ability 6. 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
2588
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 2567, Figure 2568, Figure 2569.
FIGURE 2567 MEASUREMENT MULTI TS ABILITY 6 - (1) POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
2589
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
This counter counts the number of mobiles that support GPRS multi TS ability 7. It is used to measure the number of mobiles that support GPRS multi TS ability 7. 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 2570, Figure 2571, Figure 2572.
2590
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
2591
This counter counts the number of mobiles that support GPRS multi TS ability 8. It is used to measure the number of mobiles that support GPRS multi TS ability 8. 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 2573, Figure 2574, Figure 2575.
FIGURE 2573 MEASUREMENT MULTI TS ABILITY 8 - (1) POINT
OF
NUMBER
OF MOBILE OF
GPRS
2592
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
This counter counts the number of mobiles that support GPRS multi TS ability 9. It is used to measure the number of mobiles that support GPRS multi TS ability 9. 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
2593
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 2576, Figure 2577, Figure 2578.
FIGURE 2576 MEASUREMENT MULTI TS ABILITY 9 - (1) POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
2594
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
This counter counts the number of mobiles that support GPRS multi TS ability 10. It is used to measure the number of mobiles that support GPRS multi TS ability 10. 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 2579, Figure 2580, Figure 2581.
2595
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
2596
This counter counts the number of mobiles that support GPRS multi TS ability 11. It is used to measure the number of mobiles that support GPRS multi TS ability 11. 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 2582, Figure 2583, Figure 2584.
FIGURE 2582 MEASUREMENT MULTI TS ABILITY 11 - (1) POINT
OF
NUMBER
OF MOBILE OF
GPRS
2597
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
This counter counts the number of mobiles that support GPRS multi TS ability 12. It is used to measure the number of mobiles that support GPRS multi TS ability 12. 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
2598
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 2585, Figure 2586, Figure 2587.
FIGURE 2585 MEASUREMENT MULTI TS ABILITY 12 - (1) POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
2599
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
This counter counts the number of mobiles that support GPRS multi TS ability 30. It is used to measure the number of mobiles that support GPRS multi TS ability 30. 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 2588, Figure 2589, Figure 2590.
2600
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
2601
This counter counts the number of mobiles that support GPRS multi TS ability 31. It is used to measure the number of mobiles that support GPRS multi TS ability 31. 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 2591, Figure 2592, Figure 2593.
FIGURE 2591 MEASUREMENT MULTI TS ABILITY 31 - (1) POINT
OF
NUMBER
OF MOBILE OF
GPRS
2602
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
This counter counts the number of mobiles that support GPRS multi TS ability 32. It is used to measure the number of mobiles that support GPRS multi TS ability 32. 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
2603
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 2594, Figure 2595, Figure 2596.
FIGURE 2594 MEASUREMENT MULTI TS ABILITY 32 - (1) POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
2604
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
This counter counts the number of mobiles that support GPRS multi TS ability 33. It is used to measure the number of mobiles that support GPRS multi TS ability 33. 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 2597, Figure 2598, Figure 2599.
2605
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
2606
This counter counts the number of mobiles that support GPRS multi TS ability 34. It is used to measure the number of mobiles that support GPRS multi TS ability 34. 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 2600, Figure 2601, Figure 2602.
FIGURE 2600 MEASUREMENT MULTI TS ABILITY 34 - (1) POINT
OF
NUMBER
OF MOBILE OF
GPRS
2607
POINT
OF
NUMBER
OF MOBILE OF
GPRS
POINT
OF
NUMBER
OF MOBILE OF
GPRS
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 1. It is used to measure the number of mobiles that support EGPRS multi TS ability 1. 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
2608
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 2603, Figure 2604, Figure 2605.
FIGURE 2603 MEASUREMENT MULTI TS ABILITY 1 - (1) POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2609
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 2. It is used to measure the number of mobiles that support EGPRS multi TS ability 2. 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 2606, Figure 2607, Figure 2608.
2610
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2611
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 3. It is used to measure the number of mobiles that support EGPRS multi TS ability 3. 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 2609, Figure 2610, Figure 2611.
FIGURE 2609 MEASUREMENT MULTI TS ABILITY 3 - (1) POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2612
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 4. It is used to measure the number of mobiles that support EGPRS multi TS ability 4. 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
2613
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 2612, Figure 2613, Figure 2614.
FIGURE 2612 MEASUREMENT MULTI TS ABILITY 4 - (1) POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2614
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 5. This counter is used to measure the number of link setup requests originated from BSC to TC. 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 2615, Figure 2616, Figure 2617.
2615
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2616
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 6. It is used to measure the number of mobiles that support EGPRS multi TS ability 6. 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 6. The measurement point is A1, A2, and A3, as shown in Figure 2618, Figure 2619, Figure 2620.
FIGURE 2618 MEASUREMENT MULTI TS ABILITY 6 - (1) POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2617
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 7. It is used to measure the number of mobiles that support EGPRS multi TS ability 7. This counter increments while PS control plane receives the downlink assignment requests sent by the user plane, the resource re-
2618
quests sent by the user plane on two-phase access, or the instance setup indication sent by the user plane and the message indicates the MS supports EGPRS multi TS ability 7. The measurement point is A1, A2, and A3, as shown in Figure 2621, Figure 2622, Figure 2623.
FIGURE 2621 MEASUREMENT MULTI TS ABILITY 7 - (1) POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2619
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 8. It is used to measure the number of mobiles that support EGPRS multi TS ability 8. 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 8. The measurement point is A1, A2, and A3, as shown in Figure 2624, Figure 2625, Figure 2626.
2620
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
2621
This counter counts the number of mobiles that support EGPRS multi TS ability 9. It is used to measure the number of mobiles that support EGPRS multi TS ability 9. 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 2627, Figure 2628, Figure 2629.
FIGURE 2627 MEASUREMENT MULTI TS ABILITY 9 - (1) POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2622
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 10. It is used to measure the number of mobiles that support EGPRS multi TS ability 10. 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
2623
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 2630, Figure 2631, Figure 2632.
FIGURE 2630 MEASUREMENT MULTI TS ABILITY 10 - (1) POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2624
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 11. It is used to measure the number of mobiles that support EGPRS multi TS ability 11. 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 2633, Figure 2634, Figure 2635.
2625
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
2626
This counter counts the number of mobiles that support EGPRS multi TS ability 12. It is used to measure the number of mobiles that support EGPRS multi TS ability 12. 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 12. The measurement point is A1, A2, and A3, as shown in Figure 2636, Figure 2637, Figure 2638.
FIGURE 2636 MEASUREMENT MULTI TS ABILITY 12 - (1) POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2627
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 30. It is used to measure the number of mobiles that support EGPRS multi TS ability 30. This counter increments while PS control plane receives the downlink assignment requests sent by the user plane, the resource re-
2628
quests sent by the user plane on two-phase access, or the instance setup indication sent by the user plane and the message indicates the MS supports EGPRS multi TS ability 30. The measurement point is A1, A2, and A3, as shown in Figure 2639, Figure 2640, Figure 2641.
FIGURE 2639 MEASUREMENT MULTI TS ABILITY 30 - (1) POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2629
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 31. It is used to measure the number of mobiles that support EGPRS multi TS ability 31. 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 31. The measurement point is A1, A2, and A3, as shown in Figure 2642, Figure 2643, Figure 2644.
2630
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2631
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 32. It is used to measure the number of mobiles that support EGPRS multi TS ability 32. 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 2645, Figure 2646, Figure 2647.
FIGURE 2645 MEASUREMENT MULTI TS ABILITY 32 - (1) POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2632
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 33. It is used to measure the number of mobiles that support EGPRS multi TS ability 33. This counter increments while PS control plane receives the downlink assignment requests sent by the user plane, the resource re-
2633
quests sent by the user plane on two-phase access, or the instance setup indication sent by the user plane and the message indicates the MS supports EGPRS multi TS ability 33. The measurement point is A1, A2, and A3, as shown in Figure 2648, Figure 2649, Figure 2650.
FIGURE 2648 MEASUREMENT MULTI TS ABILITY 33 - (1) POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2634
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
Unit
Times
This counter counts the number of mobiles that support EGPRS multi TS ability 34. It is used to measure the number of mobiles that support EGPRS multi TS ability 34. 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 2651, Figure 2652, Figure 2653.
2635
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
POINT
OF
NUMBER
OF MOBILE OF
EGPRS
2636
Unit
Times
This counter counts the number of mobiles that support FR. It is used to measure the number of mobiles that support FR. This counter increments while Rancs process receives the setup (caller) or call confirmed message (callee) and the voice version contained in this message is FR. The measurement point is A1 (caller) and A2 (callee), as shown in Figure 2654.
FIGURE 2654 MEASUREMENT POINT
OF
NUMBER
OF MOBILE SUPPORT
FR
Unit
Times
This counter counts the number of mobiles that support HR. It is used to measure the number of mobiles that support HR. 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 2655.
2637
OF
NUMBER
OF MOBILE SUPPORT
HR
Unit
Times
This counter counts the number of mobiles that support EFR. It is used to measure the number of mobiles that support EFR. 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 2656.
FIGURE 2656 MEASUREMENT POINT
OF
NUMBER
OF MOBILE SUPPORT
EFR
Unit
Times
2638
This counter counts the number of mobiles that support AMRFR. It is used to measure the number of mobiles that support AMRFR. 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 2657.
FIGURE 2657 MEASUREMENT POINT AMRFR
OF
NUMBER
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support AMRHR. It is used to measure the number of mobiles that support AMRHR. 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 2658.
2639
OF
NUMBER
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support wideband AMROFR. It is used to measure the number of mobiles that support wideband AMROFR. 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 2659.
2640
POINT
OF
NUMBER
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support wideband AMRFR. It is used to measure the number of mobiles that support wideband AMRFR. 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 2660.
2641
POINT
OF
NUMBER
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support wideband AMROHR. It is used to measure the number of mobiles that support wideband AMROHR. 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 2661.
2642
POINT
OF
NUMBER
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of mobiles that support AMROHR. It is used to measure the number of mobiles that support AMROHR. 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 2662.
FIGURE 2662 MEASUREMENT POINT AMROHR
OF
NUMBER
OF MOBILE SUPPORT
Unit
Times
2643
This counter counts the number of mobiles that support extended uplink TBF. It is used to measure the number of mobiles that support extended uplink TBF. 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 2663 and Figure 2664.
FIGURE 2663 MEASUREMENT EXTEND UPLINK TBF - (1) POINT
OF
NUMBER
OF MOBILE SUPPORT
POINT
OF
NUMBER
OF MOBILE SUPPORT
2644
Unit
Times
This counter counts the number of mobiles that support NACC. It is used to measure the number of mobiles that support NACC. 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 2665 and Figure 2666.
FIGURE 2665 MEASUREMENT POINT NACC - (1)
OF
NUMBER
OF MOBILE SUPPORT
OF
NUMBER
OF MOBILE SUPPORT
2645
Unit
Times
This counter counts the number of mobiles that support GPRS extended dynamic allocation. It is used to measure the number of mobiles that support GPRS extended dynamic allocation. 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 2667 and Figure 2668.
FIGURE 2667 MEASUREMENT POINT OF EXTEND DYNAMIC ALLOCATION - (1) NUMBER
OF MOBILE SUPPORT
GPRS
2646
NUMBER
OF MOBILE SUPPORT
GPRS
Unit
Times
This counter counts the number of mobiles that support EGPRS extended dynamic allocation. It is used to measure the number of mobiles that support EGPRS extended dynamic allocation. 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 2669 and Figure 2670.
2647
FIGURE 2669 MEASUREMENT POINT OF NUMBER EGPRS EXTEND DYNAMIC ALLOCATION - (1)
OF MOBILE SUPPORT
FIGURE 2670 MEASUREMENT POINT OF NUMBER EGPRS EXTEND DYNAMIC ALLOCATION - (2)
OF MOBILE SUPPORT
Unit
Times
This counter counts the number of samples that receive Classmark3. It is used to measure the number of samples that receive Classmark3. This counter increments while Rancs receives the Classmark Update message delivered by MSC or the Classmark Change message
2648
sent by MS and the message indicates Classmark3 is received. The measurement point is A1 or A2, as shown in Figure 2671.
FIGURE 2671 MEASUREMENT POINT CLASSMARK3
OF
NUMBER
OF SAMPLING RECEIVED
Unit
Times
This counter counts the number of samples that receive radio access ability. It is used to measure the number of samples that receive radio access ability. This counter increments while PS control plane receives the downlink assignment requests sent by the user plane or the resource requests sent by the user plane on two-phase access and it counts the number of samples that receive that radio access ability. The measurement point is A1 and A2, as shown in Figure 2672 and Figure 2673.
2649
POINT
OF
NUMBER
OF SAMPLING RECEIVED
POINT
OF
NUMBER
OF SAMPLING RECEIVED
Unit
Times
MS This counter counts the number of MSs that support PS handover. This counter is used to find out the number of MSs that support PS handover. After BSC receives the resource request from MS, if the MS supports PS handover, the counter increments. The measurement point is A, as shown in Figure 2674.
2650
MEASUREMENT POINT
OF
NUMBER
OF
MS
SUPPORTING
PS
Unit
Times
This counter counts the number of mobile phones that support SAIC. 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. 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 2675.
FIGURE 2675 ASSIGNMENT/HANDOVER FLOW
Measurement Point
2. When BSC receives the Hoperformed Ack message, the counter counts. The measurement point is A1, as shown in Figure 2676.
2651
Unit
Times
This counter counts the number of mobile phones that do not support SAIC. 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. This counter is supported in version V6.20.210a or above. 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. Times
Measurement Point
Unit
2652
Chapter
73
2653
C901670035 Duration of manual prohibition...................... 2665 C901670036 Number of local automatic change back ......... 2665 C901670037 Number of SL restoration ............................. 2665 C901670038 Number of Local management inhibit............. 2666 C901670039 Duration of SL inhibition due to Local management actions................................................................. 2666 C901670040 Number of remote management inhibit .......... 2666 C901670041 Duration of SL inhibition due to remote management actions................................................................. 2667 C901670042 Number of remote processor outage.............. 2667 C901670043 Duration of SL inhibition due to remote processor outage.................................................................... 2667 C901670044 Number of sending unaccess messages.......... 2668 C901670045 Number of sending flow-control discarded messages........................................................................... 2668 C901670046 Ten thousand multiple bandwidth occupancy rate on outgoing signaling link......................................... 2668 C901670047 Ten thousand multiple bandwidth occupancy rate on incoming signaling link ....................................... 2669 C901670048 Link type ................................................... 2670 C901670049 Number of TFA sent .................................... 2670 C901670050 Number of TFA received............................... 2670 C901670051 Number of TFC sent .................................... 2670 C901670052 Number of TFC received............................... 2671 C901670053 Number of RST sent .................................... 2671 C901670054 Number of RST received .............................. 2671 C901670055 Number of TRA sent .................................... 2671 C901670056 Number of TRA received .............................. 2672 C901670057 Number of UPU sent .................................... 2672 C901670058 Number of UPU received .............................. 2672 C901670059 Number of message discard controlled by license ......................................................................... 2672
Overview
Message Transfer Part Level 3, MTP3 for short, implements bearer of narrow-band messages and broad-band messages of upperlayer users. The MTP3 link measurement task takes the link as the unit. It performs measurement of messages related to MTP3 link management, the number of data messages received and sent, and the number of bytes of data messages received and sent. Statistic unit in this measurement is link. This chapter introduces the meaning, usage, and measurement point of MTP3 link measurement counters.
This counter counts the duration of the signaling link being faulty, blocked, or not activated.
2654
During a measurement period, the counter counts the duration of MTP3 link not in the service status. Second
This counter counts the number of the signaling link exiting the service status. The counter accumulates when the link status is changed from available to unavailable. Times
This counter counts the number of MSUs sent on the signaling link. 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.
This counter counts the number of octets of SIF and SIO sent on the signaling link. The counter accumulates when the MSU message is sent on the link (only counting the number of octets of SIF and SIO).
2655
This counter counts the number of MSUs received on the signaling link. The counter accumulates when the MSU message is received on the link.
This counter counts the number of octets of SIF and SIO received on the signaling link. The counter accumulates when the MSU message is received on the link (only counting the number of octets of SIF and SIO).
During the measurement period, this counter counts the peak traffic load of the signaling link. Because the M2PA link shares the bandwidth, precise calculation of traffic load is not possible. The peak traffic load is calculated on the basis of a 2 Mbps link: Measurement unit time: 15 seconds 1. Number of bytes of messages sent within the measurement unit time = Number of octets of SIF and SIO sent within the measurement unit time + Number of MSUs sent within the measurement unit time * Length of the message header 2. Number of bytes of messages received within the measurement unit time = Number of octets of SIF and SIO received within the measurement unit time + Number of MSUs received within the measurement unit time * Length of the message header
2656
Note: For 64 kbps link and broadband link, the message header's length is 6. For 2 Mbps link and N * 64 kbps link, the message header's length is 9. 3. Traffic load within the measurement unit time = 10000 * (Number of bytes of messages sent + Number of bytes of messages received) * 8 / (Link bandwidth * 2 * 15)
Note: Here, 10000 indicates , 8 indicates the number of bits of the message's bytes, 2 indicates the receiving and the sending are on two directions, and 15 indicates the measurement unit time. 4. During the measurement period, the counter compares the traffic load of each measurement unit time, and the maximum traffic load is recorded as the peak traffic load.
Measurement Point Unit
During a measurement period, the counter records the peak traffic load of the link.
This counter records the duration of the signaling link being in the status of peak traffic load within the measurement period. Like the peak traffic load, the peak traffic duration is not precise, only for reference. At present, if the counter is not cleared, its value will be accumulated. If the buffer size is not unlimited, the counter's value cannot be accumulated when its value reaches 900 seconds. If the counter is cleared, the number of route being unavailable will be cleared too. If the route is unavailable, then the following case might exist and is considered normal: the number of link being unavailable is 0 but the duration of link being unavailable is still recorded.
This counter records the duration of the signaling link being in the status of peak traffic load within the measurement period. Second
2657
This counter counts the number of changeovers occurred on the signaling link (on OMP). When the MTP3 link exits the service and changeover is initiated on the link, the counter accumulates.
This counter counts the number of transfer-prohibited messages received on the signaling link. The counter increments when the TFP message is received on the link.
This counter counts the ratio () of link bandwidth that the signaling message occupies. Because the M2PA link shares the bandwidth, precise calculation of ratio is not possible. The ratio is calculated on the basis of a 2 Mbps link, and the calculation result is only for reference. 1. Number of bytes of messages sent = Number of octets of SIF and SIO sent + Number of MSUs sent * Length of the message header 2. Number of bytes of messages received = Number of octets of SIF and SIO received + Number of MSUs received * Length of the message header
Note: For 64 kbps link and broadband link, the message header's length is 6. For 2 Mbps link and N * 64 kbps link, the message header's length is 9. 3. Link occupation ratio () = 10000 * (Number of bytes of messages sent + Number of bytes of messages received) * 8 / (Link bandwidth * 2 * counting time)
2658
The counter counts when the request of MTP3 link performance statistics is received.
This counter counts the number of SCCP messages received on the link. 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.
This counter counts the number of SCCP messages sent on the link. The counter accumulates when the SCCP message is sent on the link.
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. The counter accumulates when the ALCAP message is received on the link.
Measurement Point
2659
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. The counter accumulates when the ALCAP message is sent on the link.
Measurement Point
This counter counts the number of SNM messages received on the link. The counter accumulates when the SNM message is received on the link.
This counter counts the number of SNM messages sent on the link. The counter accumulates when the SNM message is sent on the link.
This counter counts the number of STM messages (i.e. link test message) received on the link.
2660
Measurement Point
The counter accumulates when the STM message is received on the link.
This counter counts the number of STM messages (i.e. link test message) sent on the link. The counter accumulates when the STM message is sent on the link.
This counter counts the number of octets of SCCP SIF and SIO received on the link. The counter accumulates when the SCCP message is received on the link.
This counter counts the number of octets of SCCP SIF and SIO sent on the link. The counter accumulates when the SCCP message is sent on the link.
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.
2661
Measurement Point
The counter accumulates when the ALCAP message is received on the link.
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. The counter accumulates when the ALCAP message is sent on the link.
Measurement Point
This counter counts the number of octets of SNM SIF and SIO received on the link. The counter accumulates when the SNM message is received on the link.
This counter counts the number of octets of SNM SIF and SIO sent on the link. The counter accumulates when the SNM message is sent on the link.
This counter counts the number of octets of SIF and SIO of the link test message (STM) received on the link. The counter accumulates when the STM message is received on the link.
2662
This counter counts the number of octets of SIF and SIO of the link test message (STM) sent on the link. The counter accumulates when the STM message is sent on the link.
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. 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.
Measurement Point
This counter counts the number of the link being at the congestion level 1. The counter's value is not zero only for ANSI standard, for other protocol types, its value is always zero. The counter accumulates when the link congestion is at level 1.
Measurement Point
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.
2663
Measurement Point
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. The counter accumulates when the link congestion is at level 3.
Measurement Point
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. The counter records the duration of the link being at the congestion level 1 during a measurement period. Second
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. The counter records the duration of the link being at the congestion level 2 during a measurement period. Second
2664
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. The counter records the duration of the link being at the congestion level 3 during a measurement period. Second
This counter counts the duration of the link being in the manual deactivation status. The counter records the duration of the link being in the manual deactivation status during a measurement period. Second
This counter counts the number of changebacks occurred on the signaling link (on OMP). When the MTP3 link is put into service and changeback is initiated on the link, the counter accumulates. Times
This counter counts the number of signaling link being restored to be available. The counter accumulates when the link status is changed from unavailable to available. Times
2665
This counter counts the number of local inhibitions successfully initiated by management entity (on OMP). When the management entity initiates local inhibition successfully, the counter accumulates. Times
This counter counts the duration from local inhibition being initiated successfully and local uninhibition being initiated successfully (on OMP). When the local inhibition is initiated successfully, the counter starts counting. When the local uninhibition succeeds, the counter stops counting and records the duration. Second
This counter counts the number of remote inhibitions successfully initiated by management entity (on OMP). When the management entity initiates remote inhibition successfully, the counter accumulates. Times
2666
This counter counts the duration from remote inhibition being initiated successfully and remote uninhibition being initiated successfully (on OMP). When the remote inhibition is initiated successfully, the counter starts counting. When the remote uninhibition succeeds, the counter stops counting and records the duration. Second
This counter counts the number of the remote processor being faulty. This counter accumulates when the remote processor is faulty. Times
This counter counts the duration of the remote processor being faulty. This counter counts when the remote processor is faulty. Second
2667
This counter counts the number of transfer-prohibited messages (TFP) on the link. The counter accumulates when the TFP message is sent on the link. Times
This counter counts the number of flow-control discarded messages sent on the link. The counter accumulates when the flow-control discarded messages is sent on the link.
C901670046 Ten thousand multiple bandwidth occupancy rate on outgoing signaling link
Description
This counter counts the ratio () of bandwidth occupied by the outgoing link. Outgoing link occupation ratio () = 10000 * Number of bytes of messages sent * 8 / (Link bandwidth * Measurement time)
Note: Here, 10000 indicates , multiplication of 8 indicates conversion from byte to bit, the link bandwidth unit is bit/s, and the measurement time unit is s. Number of bytes of messages sent = Number of octets of SIF and SIO sent + Number of MSUs sent * Length of the message header
2668
Note: For 64 kbps link and broadband link, the message header's length is 6. For 2 Mbps link and N * 64 kbps link, the message header's length is 9. The link bandwidth is described as follows: For 64 kbps link, N * 64 kbps link, and 2 Mbps link database configuration, the bandwidth means the number of timeslots. In other words, if the configured bandwidth is n, the bandwidth is n * 64000 bps. For broadband link, the bandwidth unit is kbps. In other words, if the bandwidth obtained from the database is n, the bandwidth is n * 1000 bps.
Measurement Point
The counter counts when the request of MTP3 link performance statistics is received.
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.
2669
This counter records the link type. If the link or link group is 64 kbps, the corresponding value is 1, represented as Narrow 64K Signaling. If the link or link group is n * 64 kbps, the corresponding value is 2, represented as Narrow N*64K Signaling. If the link or link group is 2 Mbps, the corresponding value is 3, represented as Narrow 2M Signaling. If the link or link group is broadband, the corresponding value is 4, represented as ATM Signaling - SSCS. If the link or link group is M2PA, the corresponding value is 5, represented as M2PA Signaling.
This counter counts the number of TFA messages sent on the link. The counter accumulates when the TFA message is sent on the link.
This counter counts the number of TFA messages received on the link. The counter accumulates when the TFA message is received on the link.
This counter counts the number of TFC messages sent on the link. The counter accumulates when the TFC message is sent on the link.
2670
This counter counts the number of TFC messages received on the link. The counter accumulates when the TFC message is received on the link.
This counter counts the number of RST messages (i.e. route-set test message) sent on the link. The counter accumulates when the RST message is sent on the link.
This counter counts the number of RST messages (i.e. route-set test message) received on the link. The counter accumulates when the RST message is received on the link.
This counter counts the number of service-restart-allowed messages (TRA) sent on the link. The counter accumulates when the TRA message is sent on the link.
2671
This counter counts the number of service-restart-allowed messages (TRA) received on the link. The counter accumulates when the TRA message is received on the link.
This counter counts the number of user-part-unavailable messages (UPU) sent on the link. The counter accumulates when the UPU message is sent on the link.
This counter counts the number of user-part-unavailable messages (UPU) received on the link. The counter accumulates when the UPU message is received on the link.
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.
2672
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.
2673
2674
Chapter
74
2675
of of of of
ERROR message sent................... 2686 ERROR message received ............. 2686 NOTIFY message sent .................. 2686 NOTIFY message received ............ 2687
Overview
M3UA is short for MTP3-User Adaptation Layer. M3UA measurement performs measurement of messages related to M3UA link management, the number of data messages received and sent, and the number of bytes of data messages received and sent. Statistic unit in this measurement is SCTP. It supports IP bearer of messages of some SS7 MTP3 users. It supports seamless operations of peer-layer MTP3 user protocols. It supports MTP3 nework management functions.
This chapter introduces the meaning, usage, and measurement point of M3UA performance measurement counters.
This counter counts the number of data messages sent. The counter accumulates when the data message is sent. Times
This counter counts the number of data messages received. The counter accumulates when the data message is received. Times
2676
This counter counts the number of ASP Up messages sent. The counter accumulates when the ASP Up message is sent. Times
This counter counts the number of ASP Up messages received. The counter accumulates when the ASP Up message is received. Times
This counter counts the number of ASP Up Ack messages received. The counter accumulates when the ASP Up Ack message is received. Times
This counter counts the number of ASP Up Ack messages sent. The counter accumulates when the ASP Up Ack message is sent. Times
2677
This counter counts the number of ASP Down messages sent. The counter accumulates when the ASP Down message is sent. Times
This counter counts the number of ASP Down messages received. The counter accumulates when the ASP Down message is received. Times
This counter counts the number of ASP Down Ack messages received. The counter accumulates when the ASP Down Ack message is received. Times
This counter counts the number of ASP Down Ack messages sent. The counter accumulates when the ASP Down Ack message is sent.
2678
Unit
Times
This counter counts the number of ASP Inactive messages sent. The counter accumulates when the ASP Inactive message is sent. Times
This counter counts the number of ASP Inactive messages received. The counter accumulates when the ASP Inactive message is received. Times
This counter counts the number of ASP Inactive Ack messages received. The counter accumulates when the ASP Inactive Ack message is received. Times
2679
This counter counts the number of ASP Inactive Ack messages sent. The counter accumulates when the ASP Inactive Ack message is sent. Times
This counter counts the number of ASP Active messages sent. The counter accumulates when the ASP Active message is sent. Times
This counter counts the number of ASP Active messages received. The counter accumulates when the ASP Active message is received. Times
This counter counts the number of ASP Active Ack messages received.
2680
The counter accumulates when the ASP Active Ack message is received. Times
This counter counts the number of ASP Active Ack messages sent. The counter accumulates when the ASP Active Ack message is sent. Times
This counter counts the number of DAUD messages sent. The counter accumulates when the DAUD message is sent. Times
This counter counts the number of SCON messages received. The counter accumulates when the SCON message is received. Times
2681
This counter counts the number of DAVA messages received. The counter accumulates when the DAVA message is received. Times
This counter counts the number of DUNA messages received. The counter accumulates when the DUNA message is received. Times
This counter counts the number of invalid data message received. The counter counts when the key information carried in the message is incorrect. Times
2682
Measurement Point
This counter counts the number of MGMT messages received. The counter accumulates when the MGMT message is received.
This counter counts the number of HeartBeat messages received. The counter accumulates when the HeartBeat message is received. Times
This counter counts the number of HeartBeatAck messages sent. The counter accumulates when the HeartBeatAck message is sent. Times
This counter counts the number of bytes of DATA messages received by M3UA. The counter counts when M3UA receives the DATA message.
2683
Unit
Byte
This counter counts the number of bytes of DATA messages sent by M3UA. The counter counts when M3UA sends the DATA message. Byte
This counter counts the number of bytes of MGMT messages sent. The counter counts when the NTFY message or the ERR message is sent. Byte
This counter counts the number of bytes of management messages received. The counter counts when the NTFY message or the ERR message is received. Byte
2684
When a message is discarded due to flow control, the counter's value increments. The measurement is performed according to SCTP. The counter counts when a message is discarded due to flow control.
Measurement Point
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. 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.
Measurement Point
This counter counts the bytes of all messages sent on SCTP, including data message, management message, ASPSM message, ASPTM message, and MGMT message. Byte
Unit
2685
This counter counts the bytes of all messages received on SCTP, including data message, management message, ASPSM message, ASPTM message, and MGMT message. Byte
Unit
This counter counts the number of ERROR messages sent. The counter accumulates when the ERROR message is sent. Times
This counter counts the number of ERROR messages received. The counter accumulates when the ERROR message is received. Times
This counter counts the number of NOTIFY messages sent. The counter accumulates when the NOTIFY message is sent. Times
2686
This counter counts the number of NOTIFY messages received. The counter accumulates when the NOTIFY message is received. Times
2687
2688
Chapter
75
2689
C901690043 Number of LUDTS gtt .................................. 2701 C901690044 Number of UDT gtt failure ............................ 2701 C901690045 Number of UDTS gtt failure .......................... 2701 C901690046 Number of XUDT gtt failure .......................... 2701 C901690047 Number of XUDTS gtt failure ........................ 2702 C901690048 Number of LUDT gtt failure........................... 2702 C901690049 Number of LUDTS gtt failure......................... 2702 C901690050 Number of CR gtt........................................ 2702 C901690051 Number of CR gtt failure .............................. 2703 C901690052 Number of gtt Count ................................... 2703 C901690053 Number of gtt failure ................................... 2703 C901690054 Number of N_UnitDataReq LongUserData gtt failure .......................................................................... 2703 C901690055 Number of UPU received .............................. 2704 C901690056 Number of SSA received .............................. 2704 C901690057 Number of SSA sent .................................... 2704 C901690058 Number of SST received .............................. 2704 C901690059 Number of SST sent .................................... 2705
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.
This counter counts the number of UDTs sent by SCCP of the local office. The counter accumulates when SCCP sends UDT. Times
2690
This counter counts the number of UDTs received by SCCP of the local office. The counter accumulates when SCCP receives UDT. Times
This counter counts the number of UDTSs sent by SCCP of the local office. The counter accumulates when SCCP sends UDTS. Times
This counter counts the number of UDTSs received by SCCP of the local office. The counter accumulates when SCCP receives UDTS. Times
This counter counts the number of ERRs sent by SCCP of the local office.
2691
Measurement Point
This counter counts the number of ERRs received by SCCP of the local office. The counter accumulates when SCCP receives ERR.
This counter counts the number of SSPs sent by SCCP of the local office. The counter accumulates when SCCP sends SSP.
This counter counts the number of SSPs received by SCCP of the local office. The counter accumulates when SCCP receives SSP.
This counter counts the number of RSRs sent by SCCP of the local office.
2692
Measurement Point
This counter counts the number of RSRs received by SCCP of the local office. The counter accumulates when SCCP receives RSR.
This counter counts the number of RSCs sent by SCCP of the local office. The counter accumulates when SCCP sends RSC.
This counter counts the number of RSCs received by SCCP of the local office. The counter accumulates when SCCP receives RSC.
This counter counts the number of SSTs that does not receive the response. The SST is sent by SCCP of the local office. The counter accumulates when the SST sent by SCCP does not receive the response.
2693
This counter counts the number of CREFs sent by SCCP of the local office. The counter accumulates when SCCP sends CREF.
This counter counts the number of CREFs received by SCCP of the local office. The counter accumulates when SCCP receives CREF.
This counter counts the number of XUDTs sent by SCCP of the local office. The counter accumulates when SCCP sends XUDT.
This counter counts the number of XUDTs received by SCCP of the local office.
2694
Measurement Point
This counter counts the number of XUDTSs sent by SCCP of the local office. The counter accumulates when SCCP sends XUDTS.
This counter counts the number of XUDTSs received by SCCP of the local office. The counter accumulates when SCCP receives XUDTS.
This counter counts the number of LUDTs sent by SCCP of the local office. The counter accumulates when SCCP sends LUDT.
This counter counts the number of LUDTs received by SCCP of the local office.
2695
Measurement Point
This counter counts the number of LUDTSs sent by SCCP of the local office. The counter accumulates when SCCP sends LUDTS.
This counter counts the number of LUDTSs received by SCCP of the local office. The counter accumulates when SCCP receives LUDTS.
This counter counts the number of DT1s received by SCCP of the local office. The counter accumulates when SCCP receives DT1.
This counter counts the number of DT1s sent by SCCP of the local office.
2696
Measurement Point
This counter counts the number of DT2s received by SCCP of the local office. The counter accumulates when SCCP receives DT2.
This counter counts the number of DT2s sent by SCCP of the local office. The counter accumulates when SCCP sends DT2.
This counter counts the number of sending CONNECTREQ to SCCP. The counter accumulates when SCCP receives CONNECTREQ.
2697
Measurement Point
This counter counts the number of sending CONNECTRES to SCCP. The counter accumulates when SCCP receives CONNECTRES.
This counter counts the number of sending CONNECTRES to SCCP. The counter accumulates when SCCP receives CONNECTRES.
This counter counts the number of sending DISCONNECTREQ to SCCP. The counter accumulates when SCCP receives DISCONNECTREQ.
This counter counts the number of DISCONNECTINDs received from SCCP. This counter accumulates when DISCONNECTIND is received from SCCP.
2698
This counter counts the number of CRs sent by SCCP of the local office. The counter accumulates when SCCP sends CR.
This counter counts the number of CRs received by SCCP of the local office. The counter accumulates when SCCP receives CR.
This counter counts the number of CCs sent by SCCP of the local office. The counter accumulates when SCCP sends CC.
This counter counts the number of CCs received by SCCP of the local office. The counter accumulates when SCCP receives CC.
2699
Measurement Point
This counter counts the number of UDTS GT translations. The counter when uplink/downlink UDTS GT translation is performed.
This counter counts the number of XUDT GT translations. The counter when uplink/downlink XUDT GT translation is performed.
This counter counts the number of XUDTS GT translations. The counter when uplink/downlink XUDTS GT translation is performed.
This counter counts the number of LUDT GT translations. The counter when uplink/downlink LUDT GT translation is performed.
2700
This counter counts the number of LUDTS GT translations. The counter when uplink/downlink LUDTS GT translation is performed.
This counter counts the number of UDT GT translation failures. The counter counts when uplink/downlink UDT GT translation fails. Times
This counter counts the number of UDTS GT translation failures. The counter counts when uplink/downlink UDTS GT translation fails. Times
This counter counts the number of XUDT GT translation failures. The counter counts when uplink/downlink XUDT GT translation fails.
2701
This counter counts the number of XUDTS GT translation failures. The counter counts when uplink/downlink XUDTS GT translation fails. Times
This counter counts the number of LUDT GT translation failures. The counter counts when uplink/downlink LUDT GT translation fails. Times
This counter counts the number of LUDTS GT translation failures. The counter counts when uplink/downlink LUDTS GT translation fails. Times
This counter counts the number of CR GT translations. The counter when uplink/downlink CR GT translation is performed. Times
2702
This counter counts the number of CR GT translation failures. The counter counts when uplink/downlink CR GT translation fails. Times
This counter counts the number of GT translations. The counter counts when GT translation is performed.
This counter counts the number of GT translation failures. The counter counts when GT translation fails. Times
This counter counts the number of failures of GT translation of downlink N_UnitDataReq long user message. The counter counts when the GT translation of downlink N_UnitDataReq long user message fails. Times
2703
This counter counts the number of UPUs received by SCCP of the local office. The counter accumulates when SCCP receives UPU.
This counter counts the number of SSAs received by SCCP of the local office. The counter accumulates when SCCP receives SSA.
This counter counts the number of SSAs sent by SCCP of the local office. The counter accumulates when SCCP sends SSA.
This counter counts the number of SSTs received by SCCP of the local office.
2704
Measurement Point
This counter counts the number of SSTs sent by SCCP of the local office. The counter accumulates when SCCP sends SST.
2705
2706
Chapter
76
Overview
Message Transfer Part Level 3, MTP3 for short, implements bearer of narrow-band messages and broad-band messages of upperlayer users. This meaurement takes link set as the unit. It performs measurement of the following information: duration of link set being unavailable, number of link sets being unavailable, and number of links available. A signaling link set is available so long as it has one link available. If all links in a signaling link set are unavailable, the signaling link set is unavailable. This chapter introduces the meaning, usage, and measurement point of MTP3 signaling link set statistic measurement.
This counter counts the number of all links being available in the signaling link set. When the signaling link set's status changes from at least one link being available to all links being unavailable, the counter increments. Times
2707
This counter counts the duration of all links being available in the signaling link set. 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. Second
This counter counts the number of available signaling links in the signaling link set, including the signaling link currently being used. This counter counts the number of available signaling links in the signaling link set, including the signaling link currently being used.
There are five link set types: 64 kbps signaling link set n * 64 kbps signaling link set 2 Mbps signaling link set Broadband signaling link set M2PA signaling link set
2708
Chapter
77
2709
C901710041 Receiving refuse error, reason is management blocking ....................................................................... 2721 C901710042 Receiving required ASP ID............................ 2721 C901710043 Receiving invalid ASP ID .............................. 2721 C901710044 Receiving invalid parameter value ................. 2722 C901710045 Receiving parameter field error ..................... 2722 C901710046 Receiving unexpected parameter error........... 2722 C901710047 Receiving destination status unknown............ 2722 C901710048 Receiving missing parameter error ................ 2723 C901710049 Receiving no configured AS for ASP ............... 2723
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.
This counter counts when an Error message is sent outwards from the local office, with the error code of "Invalid Version". The counter accumulates when an Error message with the error code of "Invalid Version" is sent outwards from the local office.
This counter counts when an Error message is sent outwards from the local office, with the error code of "Unsupported Message Class". The counter accumulates when an Error message with the error code of "Unsupported Message Class" is sent outwards from the local office.
Measurement Point
2710
This counter counts when an Error message is sent outwards from the local office, with the error code of "Unsupported Message Type". The counter accumulates when an Error message with the error code of "Unsupported Message Type" is sent outwards from the local office.
Measurement Point
This counter counts when an Error message is sent outwards from the local office, with the error code of "Unexpected Message". The counter accumulates when an Error message with the error code of "Unexpected Message" is sent outwards from the local office.
This counter counts when an Error message is sent outwards from the local office, with the error code of "Unsupported Traffic Mode". The counter accumulates when an Error message with the error code of "Unsupported Traffic Mode" is sent outwards from the local office.
This counter counts when an Error message is sent outwards from the local office, with the error code of "Invalid Routing Context". The counter accumulates when an Error message with the error code of "Invalid Routing Context" is sent outwards from the local office.
2711
This counter counts when an Error message is sent outwards from the local office, with the error code of "Protocol Error". The counter accumulates when an Error message with the error code of "Protocol Error" is sent outwards from the local office.
This counter counts the number of invalid message types sent. It is same as the counter "Unsupported Message Type(T)". The counter counts when the message type sent is invalid.
This counter counts the number of error messages sent outwards from the local office. The counter accumulates when the error message is sent outwards from the local office.
This counter counts when an Error message is received, with the error code of "Invalid Version". The counter accumulates when an Error message with the error code of "Invalid Version" is received.
2712
This counter counts when an Error message is received, with the error code of "Unsupported Message Class". The counter accumulates when an Error message with the error code of "Unsupported Message Class" is received.
This counter counts when an Error message is received, with the error code of "Unsupported Message Type". The counter accumulates when an Error message with the error code of "Unsupported Message Type" is received.
This counter counts when an Error message is received, with the error code of "Unexpected Message". The counter accumulates when an Error message with the error code of "Unexpected Message" is received.
This counter counts when an Error message is received, with the error code of "Unsupported Traffic Mode". The counter accumulates when an Error message with the error code of "Unsupported Traffic Mode" is received.
2713
This counter counts when an Error message is received, with the error code of "Invalid Routing Context". The counter accumulates when an invalid routing context message is received.
This counter counts when an Error message is received, with the error code of "Protocol Error". The counter accumulates when an Error message with the error code of "Protocol Error" is received.
This counter counts the number of invalid message types received. It is same as the counter "Unsupported Message Type(R)". The counter counts when the message type received is invalid.
This counter counts the number of error messages received. The counter accumulates when the error message is received. Times
2714
This counter counts when a DUPU message is received, with the indication of "Unknown". The counter accumulates when a DUPU message with the indication of "Unknown" is received.
This counter counts when a DUPU message is received, with the indication of "Unequipped Remote User". The counter accumulates when a DUPU message with the indication of "Unequipped Remote User" is received.
This counter counts when a DUPU message is received, with the indication of "Inaccessible Remote User". The counter accumulates when a DUPU message with the indication of "Inaccessible Remote User" is received.
This counter counts the number of DUPU messages received. The counter accumulates when the DUPU message is received. Times
2715
This counter counts when an Error message is sent outwards from the local office, with the error code of "Invalid Network Appearance". The counter accumulates when an Error message with the error code of "Invalid Network Appearance" is sent outwards from the local office.
Measurement Point
This counter counts when an Error message is received, with the error code of "Invalid Network Appearance". The counter accumulates when an Error message with the error code of "Invalid Network Appearance" is received.
This counter counts when a DUPU message is sent, with the indication of "Unknown". The counter accumulates when a DUPU message with the indication of "Unknown" is sent. Times
2716
C901710026 Number of DUPU message sent which cause is Unequipped Remote User
Description Measurement Point Unit
This counter counts when a DUPU message is sent, with the indication of "Unequipped Remote User". The counter accumulates when a DUPU message with the indication of "Unequipped Remote User" is sent. Times
C901710027 Number of DUPU message sent which cause is Inaccessible Remote User
Description Measurement Point Unit
This counter counts when a DUPU message is sent, with the indication of "Inaccessible Remote User". The counter accumulates when a DUPU message with the indication of "Inaccessible Remote User" is sent. Times
This counter counts the number of DUPU messages sent. The counter accumulates when the DUPU message is sent. Times
2717
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. 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.
Measurement Point
This counter counts when an Error message is sent outwards from the local office, with the error code of "Invalid Stream ID". The counter accumulates when an Error message with the error code of "Invalid Stream ID" is sent outwards from the local office.
This counter counts when an Error message is sent outwards from the local office, with the error code of "Management Blocking Rejection". The counter accumulates when an Error message with the error code of "Management Blocking Rejection" is sent outwards from the local office.
Measurement Point
2718
This counter counts when an Error message is sent outwards from the local office, with the error code of "ASP ID Required". The counter accumulates when an Error message with the error code of "ASP ID Required" is sent outwards from the local office.
This counter counts when an Error message is sent outwards from the local office, with the error code of "Invalid ASP ID". The counter accumulates when an Error message with the error code of "Invalid ASP ID" is sent outwards from the local office.
This counter counts when an Error message is sent outwards from the local office, with the error code of "Invalid Parameter Value". The counter accumulates when an Error message with the error code of "Invalid Parameter Value" is sent outwards from the local office.
This counter counts when an Error message is sent outwards from the local office, with the error code of "Parameter Field Error". The counter accumulates when an Error message with the error code of "Parameter Field Error" is sent outwards from the local office.
2719
This counter counts when an Error message is sent outwards from the local office, with the error code of "Unexpected Parameter". The counter accumulates when an Error message with the error code of "Unexpected Parameter" is sent outwards from the local office.
This counter counts when an Error message is sent outwards from the local office, with the error code of "Destination Status Unknown". The counter accumulates when an Error message with the error code of "Destination Status Unknown" is sent outwards from the local office.
Measurement Point
This counter counts when an Error message is sent outwards from the local office, with the error code of "Missing Parameter Error". The counter accumulates when an Error message with the error code of "Missing Parameter Error" is sent outwards from the local office.
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". 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.
Measurement Point
2720
This counter counts when an Error message is received, with the error code of "Invalid Stream ID". The counter accumulates when an Error message with the error code of "Invalid Stream ID" is received.
This counter counts when an Error message is received, with the error code of "Management Blocking Rejection". The counter accumulates when an Error message with the error code of "Management Blocking Rejection" is received.
This counter counts when an Error message is received, with the error code of "ASP ID Required". The counter accumulates when an Error message with the error code of "ASP ID Required" is received.
This counter counts when an Error message is received, with the error code of "Invalid ASP ID". The counter accumulates when an Error message with the error code of "Invalid ASP ID" is received.
2721
This counter counts when an Error message is received, with the error code of "Invalid Parameter Value". The counter accumulates when an Error message with the error code of "Invalid Parameter Value" is received.
This counter counts when an Error message is received, with the error code of "Parameter Field Error". The counter accumulates when an Error message with the error code of "Parameter Field Error" is received.
This counter counts when an Error message is received, with the error code of "Unexpected Parameter". The counter accumulates when an Error message with the error code of "Unexpected Parameter" is received.
This counter counts when an Error message is received, with the error code of "Destination Status Unknown". The counter accumulates when an Error message with the error code of "Destination Status Unknown" is received.
2722
This counter counts when an Error message is received, with the error code of "Missing Parameter Error". The counter accumulates when an Error message with the error code of "Missing Parameter Error" is received.
This counter counts when an Error message is received, with the error code of "AS not configured with the ASP". The counter accumulates when an Error message with the error code of "AS not configured with the ASP" is received.
2723
2724
Chapter
78
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.
This counter counts the number of upper-layer user messages sent by AS of M3UA. The counter counts when M3UA sends the upper-layer user message. Times
2725
This counter counts the number of bytes of upper-layer user messages sent by AS of M3UA. The counter counts when M3UA sends the upper-layer user message. Byte
This counter counts the number of upper-layer user messages received by AS of M3UA. The counter counts when M3UA receives the upper-layer user message from SCTP. Times
This counter counts the number of bytes of upper-layer user messages received by AS of M3UA. The counter counts when M3UA receives the upper-layer user message from SCTP. Byte
2726
Chapter
79
Timer Statistics
Table of Contents Overview...................................................................... 2727 C901730001 Number of all timers ................................... 2727 C901730002 Number of available timer ............................ 2728 C901730003 Peak value of timer ..................................... 2728 C901730004 Number of success to set timer..................... 2728 C901730005 Number of failure to set timer....................... 2728
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.
2727
Measurement Point
This counter counts the number of available timers. The counter counts when a timer control block is released successfully.
This counter records the peak value of timer usage. The counter counts when the timer usage exceeds the current peak value.
This counter counts the number of successes in setting timer. The counter counts when the timer is set successfully. Times
This counter counts the number of failures in setting timer. The counter counts when the timer setting fails. Times
2728
Chapter
80
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.
This counter counts the total number of active processes. The measurement point is determined during process creation and is not changed during the operation.
2729
This counter counts the total number of processes. The measurement point is configured in the configuration file.
This counter counts the total number of scheduled processes. This counter increments when a process is scheduled. It counts the times of process scheduling in the last 2 seconds.
2730
Chapter
81
Overview
UB memory performance statistics refer to the statistics on the usage of current system UB and user UB on a certain board, including the statistics based on UB size and number of used UBs. Two statistic methods are available: Calculate UB usage based on quantity Calculate UB usage based on size
The statistics based on quantity reflects the percentage of used UB from the perspective of quantity. The statistics based on size reflects the usage of UB from the perspective of used size. If the query mode is 1, the system starts statistics based on the quantity of used UBs and returns the percentage of currently used UBs. If the query mode is -1, the system starts statistics based on the size of used UBs and returns the percentage of currently used USs. The unit of this UB performance statistics is board.
C901750001 ID of UB Set
Description
This counter counts the ID of a UB set. INNER_MEM_POOL_GROUP represents the memory pool sets that are internally used. USER_MEM_POOL_GROUP represents the memory pool sets that are used by user.
2731
Measurement Point
C901750002 Size of UB
Description Measurement Point
This counter counts the size of the UBs in a UB set. The measurement point is configured and unchanged.
C901750003 Number of UB
Description Measurement Point
This counter counts the number of UBs in the UB pool set. The measurement point is related to current UB usage status and may dynamically change with the addition or reduction of switching blocks.
This counter counts the number of used UBs. The measurement point is related to the current UB usage status.
2732
Chapter
82
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.
This counter indicates the disk device ID, which is /FLASH0, /DOC0, /IDE0, /IDE1, /IDE2, or /IDE3. The measurement point is related to the disk configuration on the current board.
This counter counts the total space. The measurement point is unchanged. KB
2733
This counter counts the free space. The disk space occupation changes each time a file is added, modified, or deleted. KB
2734
Chapter
83
2735
C901770041 Number of ULP Sent Chunk Request to SCTP OK during a little time ......................................................... 2745 C901770042 Number of SCTP Sent Chunk Request to ULP ............................................................................. 2746 C901770043 Number of Abort Request from ULP ............... 2746 C901770044 Number of Received Abort From Peer ............ 2746 C901770045 Number of Link Break for Retransfer.............. 2746
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.
This counter counts the number of associations passively established. When an association is accepted, this counter counts.
This counter counts the number of initiated associations. When an association is actively initiated, this counter counts.
2736
Measurement Point
This counter counts the number of aborted associations. When an association is aborted, this counter counts.
This counter counts the times of chunk retransmission. When a chunks is retransmitted, this counter counts.
This counter counts the number of sent unordered chunks. When an unordered chunk is sent, this counter counts.
This counter counts the number of received unordered chunks. When an unordered chunk is received, this counter counts.
2737
Measurement Point
This counter counts the number of received chunks. When a chunk is received, this counter counts.
This counter counts the number of sent INIT chunks. When an INIT chunk is sent, this counter counts.
This counter counts the number of received INIT chunks. When an INIT chunk is received, this counter counts.
This counter counts the number of sent INITACK chunks. When an INITACK chunks is sent, this counter counts.
2738
Measurement Point
This counter counts the number of sent COOKIE chunks. When a COOKIE chunk is sent, this counter counts.
This counter counts the number of received COOKIE chunks. When a COOKIE chunk is received, this counter counts.
This counter counts the number of sent COOKIE ACK chunks. When a COOKIE ACK chunk is sent, this counter counts.
This counter counts the number of received COOKIE ACK chunks. When a COOKIE ACK chunk is received, this counter counts.
2739
Measurement Point
This counter counts the number of received heartbeats. When a HEARTBEAT chunk is received, this counter counts.
This counter counts the number of sent heartbeat acknowledgement chunks. When a HEARTBEAT ACK chunk is sent, this counter counts.
This counter counts the number of sent heartbeat acknowledgement chunks. When a HEARTBEAT ACK chunk is sent, this counter counts.
2740
Measurement Point
This counter counts the number of received ABORT chunks. When an ABORT chunk is received, this counter counts.
This counter counts the number of sent SHUTDOWN chunks. When a SHUTDOWN chunk is sent, this counter counts.
This counter counts the number of received SHUTDOWN chunks. When a SHUTDOWN chunk is received, this counter counts.
2741
Measurement Point
This counter counts the number of received SHUTDOWN ACK chunks. When a SHUTDOWN ACK chunk is received, this counter counts.
This counter counts the number of sent SHUTDOWN COMPLETE chunks. When a SHUTDOWN COMPLETE chunk is sent, this counter counts.
This counter counts the number of received SHUTDOWN COMPLETE chunks. When a SHUTDOWN COMPLETE chunk is received, this counter counts.
2742
Measurement Point
This counter counts the number of received ERROR chunks. When an ERROR chunk is received, this counter counts.
This counter counts the number of sent ECNE chunks. As the implementation at bottom layer is not supported, the statistics are invalid. When an ECNE chunk is sent, this counter counts.
Measurement Point
This counter counts the number of sent ECNE chunks. As the implementation at bottom layer is not supported, the statistics are invalid. When an ECNE chunk is sent, this counter counts.
Measurement Point
This counter counts the number of sent CWR chunks. As the implementation at bottom layer is not supported, the statistics are invalid.
2743
Measurement Point
This counter counts the number of received CWR chunks. As the implementation in bottom layer is not supported, the statistics are invalid. When a CWR chunk is received, this counter counts.
Measurement Point
This counter counts the number of received Error packets. When an Error packet is received, this counter counts.
This counter counts the number of received OOTB chunks. When an OOTB chunk is received, this counter counts.
This counter counts the number of chunk requests sent by ULP when association is alive. When ULP initiates chunk requests when association is alive, this counter counts.
2744
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. Each time there is a successful chunk request sent by ULP when association is alive, this counter counts.
Measurement Point
This counter counts the number of chunk requests sent by ULP. As the implementation at bottom layer is not supported, the statistics are invalid. When ULP sends a chunk request, this counter counts.
Measurement Point
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. When a chunk request sent by ULP to SCTP is successful, this counter counts.
Measurement Point
2745
This counter counts the number of chunk requests sent by SCTP to ULP. As the implementation at bottom layer is not supported, the statistics are invalid. When SCTP sends chunk requests to ULP, this counter counts.
Measurement Point
This counter counts the number of ABORT requests from ULP. As the implementation at lower layer is not supported, the statistics are invalid. When ULP sends an ABORT request to SCTP, this counter counts.
Measurement Point
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. When SCTP receives an ABORT message from the peer end, this counter counts.
Measurement Point
This counter counts the number of link disconnections due to retransfer. When a link is broken due to retransmission, this counter counts.
2746
Chapter
84
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.
Association states are as follows: Closed, Cookie wait, Cookie Echoed, Established, Shutdown Pending, Shutdown Received, Shutdown Sent, and Shutdown Ack Sent.
2747
Measurement Point
None
This counter counts the number of unsuccessful synchronization message sent to ULP. When synchronization messages are sent to ULP, this counter counts.
This counter counts the number of invalid ULPIDs returned by ULP. When ULP returns ULPID, this counter counts.
This counter counts the number of associations initiated to ULP. When association is actively established and Cookie ACK is received, this counter increments.
This counter counts the number of passively established associations reported to ULP. When association is passively established and Cookie Echo is received, this counter increments.
2748
This counter counts the number of restarted associations reported to ULP. When an association is restarted, this counter counts.
This counter counts the number of lost associations reported to ULP. When an association is lost, this counter counts.
This counter counts the number of Destroy instance requests sent by ULP. When ULP sends a Destroy instance request, this counter counts.
This counter counts the number of association shutdown requests sent by ULP.
2749
Measurement Point
This counter counts the number of association abort requests sent by ULP. When ULP sends an ABORT message, this counter counts.
2750
Chapter
85
2751
C901790026 VC-4 Remote Errored Second (High-order path 3)................................................................................ 2761 C901790027 VC-4 Remote Severely Errored Second (Highorder path 1) ................................................................ 2761 C901790028 VC-4 Remote Severely Errored Second (Highorder path 2) ................................................................ 2762 C901790029 VC-4 Remote Severely Errored Second (Highorder path 3) ................................................................ 2762 C901790030 VC-4 Remote Unavailable Second (High-order path 1) ........................................................................ 2762 C901790031 VC-4 Remote Unavailable Second (High-order path 2) ........................................................................ 2763 C901790032 VC-4 Remote Unavailable Second (High-order path 3) ........................................................................ 2763 C901790033 B1(Regenerator Section) BIP-8 Background Block Error Ratio ........................................................... 2763 C901790034 B1(Regenerator Section) BIP-8 Errored Second Ratio ........................................................................... 2764 C901790035 B1(Regenerator Section) BIP-8 Errored Second ............................................................................. 2764 C901790036 B1(Regenerator Section) BIP-8 Severely Errored Second ........................................................................ 2765 C901790037 B1(Regenerator Section) BIP-8 Unavailable Second ............................................................................. 2765 C901790038 B2(Multiplex Section) BIP-24 Background Block Error Ratio.................................................................... 2765 C901790039 B2(Multiplex Section) BIP-24 Errored Second Ratio ........................................................................... 2766 C901790040 B2(Multiplex Section) BIP-24 Errored Second ............................................................................. 2766 C901790041 B2(Multiplex Section) BIP-24 Severely Errored Second ........................................................................ 2767 C901790042 B2(Multiplex Section) BIP-24 Unavailable Second ............................................................................. 2767 C901790043 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 1) ....................................................... 2767 C901790044 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 2) ....................................................... 2768 C901790045 B3(VC-4) BIP-8 Background Block Error Ratio (High-order path 3) ....................................................... 2768 C901790046 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 1) ................................................................... 2769 C901790047 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 2) ................................................................... 2769 C901790048 B3(VC-4) BIP-8 Errored Second Ratio (High-order path 3) ................................................................... 2769 C901790049 B3(VC-4) BIP-8 Errored Second (High-order path 1) ........................................................................ 2770 C901790050 B3(VC-4) BIP-8 Errored Second (High-order path 2) ........................................................................ 2770 C901790051 B3(VC-4) BIP-8 Errored Second (High-order path 3) ........................................................................ 2770 C901790052 B3(VC-4) BIP-8 Severely Errored Second (Highorder path 1) ................................................................ 2771 C901790053 B3(VC-4) BIP-8 Severely Errored Second (Highorder path 2) ................................................................ 2771 C901790054 B3(VC-4) BIP-8 Severely Errored Second (Highorder path 3) ................................................................ 2771 C901790055 B3(VC-4) BIP-8 Unavailable Second (High-order path 1) ........................................................................ 2772
2752
C901790056 B3(VC-4) BIP-8 Unavailable Second (High-order path 2) ........................................................................ 2772 C901790057 B3(VC-4) BIP-8 Unavailable Second (High-order path 3) ........................................................................ 2772 C901790058 LOF second ................................................ 2773
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.
Description
2753
Regeneration section overhead byte B1 is used as the BIP code to monitor bit errors of regeneration section. 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.
Three multiplex section overhead byte B2s are used as the BIP code to monitor bit errors of multiplex section. 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.
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. 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.
Measurement Point
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.
2754
Measurement Point
This counter is similar to dwB3E2. It corresponds to high-order path 3. This counter is similar to dwB3E2. It corresponds to high-order path 3.
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). 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.
Measurement Point
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. 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.
Measurement Point
2755
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. This counter is similar to dwVC4REI1. It corresponds to high-order path 2.
Measurement Point
This counter is similar to dwVC4REI2. It corresponds to high-order path 3. This counter is similar to dwVC4REI2. It corresponds to high-order path 3.
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). 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.
Measurement Point
2756
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). 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.
Measurement Point
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). 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.
Measurement Point
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 con-
2757
tains 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.
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). 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.
Measurement Point
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. 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,
Measurement Point
2758
This counter is similar to dwVC4FEBBER1. It corresponds to highorder path 2. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2. This counter is similar to dwVC4FEBBER1. It corresponds to highorder path 2.
Measurement Point
This counter is similar to dwVC4FEBBER2. It corresponds to highorder path 3. This counter is similar to dwVC4FEBBER2. It corresponds to highorder path 3.
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. 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
Measurement Point
2759
dwVC4REI increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwVC4FEER1.
This counter is similar to dwVC4FEER1. It corresponds to highorder path 2. When SDH type is AU-4, it is meaningless. When SDH type is AU-3 or STS-3, it corresponds to high-order path 2. This counter is similar to dwVC4FEER1. It corresponds to highorder path 2.
Measurement Point
This counter is similar to dwVC4FEER2. It corresponds to highorder path 3. This counter is similar to dwVC4FEER2. It corresponds to highorder path 3.
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. 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
Measurement Point
2760
dwVC4REI increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwVC4FEES1.
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. This counter is similar to dwVC4FEES1. It corresponds to highorder path 2.
Measurement Point
This counter is similar to dwVC4FEES2. It corresponds to highorder path 3. This counter is similar to dwVC4FEES2. It corresponds to highorder path 3.
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. 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
Measurement Point
2761
dwVC4REI increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwVC4FESES1.
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. This counter is similar to dwVC4FESES1. It corresponds to highorder path 2.
Measurement Point
This counter is similar to dwVC4FESES2. It corresponds to highorder path 3. This counter is similar to dwVC4FESES2. It corresponds to highorder path 3.
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. 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
Measurement Point
2762
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.
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. This counter is similar to dwVC4FEUAS1. It corresponds to highorder path 2.
Measurement Point
This counter is similar to dwVC4FEUAS2. It corresponds to highorder path 3. This counter is similar to dwVC4FEUAS2. It corresponds to highorder path 3.
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).
2763
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.
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). 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.
Measurement Point
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). 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.
Measurement Point
2764
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. 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 dwB1SES.
Measurement Point
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). 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
Measurement Point
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
2765
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.
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). 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.
Measurement Point
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). 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.
Measurement Point
2766
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. 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 dwB2SES.
Measurement Point
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). 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.
Measurement Point
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
2767
after deducting the unusable time and the error blocks appearing in the SES period. The ratio between the BBE numbers and total block numbers after deducting the unusable time and all the blocks during the SES period is called background block error rate (BBER). When SDH type is AU-4, AU-3, and STS-3, the corresponding highorder path is 1.
Measurement Point
When the B3 byte received by high-order path 1 is verified to be inconsistent with the result of BIP-8 check for VC-4 block of previous STM-1 frame at local end, the block is assumed to have error. VC-4 path BIP code counter dwB3E increments. SDTB periodically queries this counter, which can serve as reference for the calculation of dwB3BBER1.
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. This counter is similar to dwB3BBER1. It corresponds to high-order path 2.
Measurement Point
This counter is similar to dwB3BBER2. It corresponds to high-order path 3. This counter is similar to dwB3BBER2. It corresponds to high-order path 3.
2768
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. 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.
Measurement Point
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. This counter is similar to dwB3ER1. It corresponds to high-order path 2.
Measurement Point
This counter is similar to dwB3ER2. It corresponds to high-order path 3. This counter is similar to dwB3ER2. It corresponds to high-order path 3.
2769
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. 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.
Measurement Point
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. This counter is similar to dwB3ES1. It corresponds to high-order path 2.
Measurement Point
This counter is similar to dwB3ES2. It corresponds to high-order path 3. This counter is similar to dwB3ES2. It corresponds to high-order path 3.
2770
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. 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.
Measurement Point
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. This counter is similar to dwB3SES1. It corresponds to high-order path 2.
Measurement Point
This counter is similar to dwB3SES2. It corresponds to high-order path 3. This counter is similar to dwB3SES2. It corresponds to high-order path 3.
2771
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. 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.
Measurement Point
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. This counter is similar to dwB3UAS1. It corresponds to high-order path 2.
Measurement Point
This counter is similar to dwB3UAS2. It corresponds to high-order path 3. This counter is similar to dwB3UAS2. It corresponds to high-order path 3.
2772
This counter counts the seconds of LOF. The statistic result is 0 if it is not temporally used. This counter counts when LOF occurs and does not stop until LOF restores.
2773
2774
Chapter
86
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
2775
E1 signal in various sections and paths of transport network. This chapter describes the main performance statistic items, statistic method, and standard compliance of PEB22554 module. PEB22554 module is a digital trunk access chip. It can connect the transport network as standard E1 port at line side. The system side provides four E1s to bear services such as IMA for the system. The performance statistic items of PEB22554 module in E1 mode include FAS error, CRC error, and E-bit error. The statistic method is as follows: query the number of error blocks of receiving end signals at the interval of 1S, and handle the error events in accordance with ITU-T G.826 standard.
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.
This counter counts the duration of code slip during detection period. Code slip occurs when receiving clock and transmitting clock are insynchronous. This counter counts the duration of code slip. Second
This counter counts the time available at near end, that is, the result of excluding UAS from total detection period. This counter counts the available seconds at near end. Second
2776
If 10 consecutive near end SESs occur, the link is regarded to be unavailable (UAS). The ten seconds are counted as unavailable seconds. The link is regarded to be recovered if no near end SES occurs in 10 consecutive seconds. These ten seconds are counted as unavailable seconds. This counter counts the unavailable seconds at near end. Second
This counter increments each second near end detects LOF, LOS, AIS alarm, and FAS error when link is available. For multi-frame, this counter also counts the number of CRC-4 error blocks. If there is one or more CRC-4 errors within a second, this counter increments. This counter counts the errored seconds at near end. Second
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. When severely errored seconds at near end are detected, this counter counts. Second
2777
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. When near end background block error occurs, this counter counts. The basic frame is invalid and thus use 0. Second
This counter counts the number of FAS errors during the specified period. When FAS error is detected, this counter counts.
This counter counts the number of CRC4 errors during the specified period. When CRC4 error is detected, this counter counts.
For details, see the formula under the table. This counter counts the number of errored codes. PPM
2778
For details, see the formula under the table. When unavailable seconds are detected at near end, this counter counts. Ten-thousandth
For details, see the formula under the table. When errored seconds are detected at near end, this counter counts. Ten-thousandth
For details, see the formula under the table. When severely errored seconds at near end are detected, this counter counts. Ten-thousandth
2779
Measurement Point
When background block error is detected at near end, this counter counts.
This counter counts the time available at far end, that is, the result of excluding UAS from total detection period. This counter counts the available seconds at far end. Second
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. When unavailable seconds are detected at far end, this counter counts. Second
This counter increments each second near end detects RAI alarm and EBIT error when link is available. When errored seconds are detected at far end, this counter counts. Second
2780
This counter increments each second far end detects RAI alarm and EBIT (EBIT>=805) error when link is available. When severely errored seconds are detected at far end, this counter counts. Second
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. When far end background block errors are detected, this counter counts.
Measurement Point
This counter counts the times of sub-frame errors in multi-frame during the detection period. When EBIT error is detected, this counter counts. Times
For details, see the formula under the table. When unavailable seconds are detected at far end, this counter counts. Ten-thousandth
2781
For details, see the formula under the table. When errored seconds are detected at far end, this counter counts. Ten-thousandth
For details, see the formula under the table. When severely errored seconds are detected at far end, this counter counts. Ten-thousandth
For details, see the formula under the table. When background block error is detected at far end, this counter counts. Ten-thousandth
2782
Chapter
87
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.
2783
There are two frame types: basic frame and multi-frame. 1 F24 (ESF) without CRC6 2 F24 (ESF) with CRC6 3 F12 (SF) 4 F4 5 F72
This counter counts the duration of code slip during detection period. Code slip occurs when receiving clock and transmitting clock are insynchronous. This counter counts the duration of code slip. Second
This counter counts the time available at near end, that is, the result of excluding UAS from total detection period. This counter counts the available seconds at near end.
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. When unavailable seconds are detected at near end, this counter counts.
Measurement Point
2784
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. When errored seconds are detected at near end, this counter counts.
Measurement Point
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. When severely errored seconds at near end are detected, this counter counts.
Measurement Point
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. When near end background block errors are detected, this counter counts.
Measurement Point
2785
This counter counts the number of FAS errors during the specified period. When FAS error is detected, this counter counts.
This counter counts the number of CRC6 errors during the specified period. When CRC6 error is detected, this counter counts.
See the formula. This counter counts the number of errored codes. PPM
See the formula. When unavailable seconds are detected at near end, this counter counts. Ten-thousandth
2786
See the formula. When errored seconds are detected at near end, this counter counts. Ten-thousandth
See the formula. When severely errored seconds at near end are detected, this counter counts. Ten-thousandth
See the formula. When background block errors are detected at near end, this counter counts.
2787
2788
Chapter
88
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.
2789
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. This counter is used to find out the transceiving data flow at the port within the measurement period. The counter counts when the message is received at the port. BYTE
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. This counter is used to find out the transceiving data flow at the port within the measurement period. The counter counts when the message is received at the port. BYTE
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. This counter is used to find out the transceiving data flow at the port within the measurement period. The counter counts when the message is transmitted at the port. BYTE
2790
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. This counter is used to find out the transceiving data flow at the port within the measurement period. The counter counts when the message is transmitted at the port. BYTE
This counter counts the port's physical bandwidth when the statistic data is reported. 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). The counter counts when the data is reported. Mbit/s
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 This counter is used to find out the average receiving rate at the port. The counter's value is calculated when the data is reported. bit/s
2791
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. This counter is used to find out the maximum receiving rate at the port. The counter's value is calculated when the data is reported. bit/s
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 This counter is used to find out the average transmitting rate at the port. The counter's value is calculated when the data is reported. bit/s
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. This counter is used to find out the maximum transmitting rate at the port. The counter's value is calculated when the data is reported. bit/s
2792
This counter counts the number of packets discarded at the receiving end (higher 4 bytes). This counter is supported in version V6.20.61 or later. The counter counts when the discarded packet is received at the port.
This counter counts the number of packets discarded at the receiving end (lower 4 bytes). This counter is supported in version V6.20.61 or later. The counter counts when the discarded packet is received at the port.
This counter counts the number of packets discarded at the transmitting end (higher 4 bytes). This counter is supported in version V6.20.61 or later. The counter counts when the discarded packet is transmitted at the port.
2793
This counter counts the number of packets discarded at the transmitting end (lower 4 bytes). This counter is supported in version V6.20.61 or later. The counter counts when the discarded packet is transmitted at the port.
C901820014 Number of packets received when receiving bit rate is max during performance period
Description Usage Measurement Point
This counter counts the number of packets received at the peak rate of the port. This counter is supported in version V6.20.61 or later. 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.
C901820015 Number of packets sent when sending bit rate is max during performance period
Description Usage Measurement Point
This counter counts the number of packets sent at the peak rate of the port. This counter is supported in version V6.20.61 or later. 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.
2794
Chapter
89
Overview
AMR rate statistics counts the total number of uplink/downlink frames of absolute rate at the cell level. AMR rate statistics at baseband counts the total number of uplink/downlink frames of absolute rate (coding frame) according to cells. The full-rate channel has 8 rates while the half-rate channel has 6 rates. Each carriers requires 28 counters. Figure 2677 shows the AMR rate statistics flow.
2795
This counter counts the number of coding frames which adopt 12.2 k coding rate in downlink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
2796
This counter counts the number of coding frames which adopt 10.2 k coding rate in downlink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 7.95 k coding rate in downlink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 7.40 k coding rate in downlink in AMR full-rate channel service. 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.
2797
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 6.70 k coding rate in downlink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 5.90 k coding rate in downlink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
2798
This counter counts the number of coding frames which adopt 5.15 k coding rate in downlink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 4.75 k coding rate in downlink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 7.95 k coding rate in downlink in AMR half-rate channel service. 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.
2799
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 7.40 k coding rate in downlink in AMR half-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 6.70 k coding rate in downlink in AMR half-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
2800
This counter counts the number of coding frames which adopt 5.90 k coding rate in downlink in AMR half-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 5.15 k coding rate in downlink in AMR half-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 4.75 k coding rate in downlink in AMR half-rate channel service. 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.
2801
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 12.2 k coding rate in uplink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 10.2 k coding rate in uplink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
2802
This counter counts the number of coding frames which adopt 7.95 k coding rate in uplink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 7.40 k coding rate in uplink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 6.70 k coding rate in uplink in AMR full-rate channel service. 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.
2803
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 5.90 k coding rate in uplink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 5.15 k coding rate in uplink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
2804
This counter counts the number of coding frames which adopt 4.75 k coding rate in uplink in AMR full-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 7.95 k coding rate in uplink in AMR half-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 7.40 k coding rate in uplink in AMR half-rate channel service. 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.
2805
The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 6.70 k coding rate in uplink in AMR half-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 5.90 k coding rate in uplink in AMR half-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
2806
This counter counts the number of coding frames which adopt 5.15 k coding rate in uplink in AMR half-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
This counter counts the number of coding frames which adopt 4.75 k coding rate in uplink in AMR half-rate channel service. 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. The counter's value is obtained by querying database when the AMR rate statistic data is reported periodically. Number of frames
2807
2808
Chapter
90
UMAC Measurement
Table of Contents Overview...................................................................... 2811 C901850001 receive discard packets flag.......................... 2811 C901850002 receive discard packets low 32bits................. 2812 C901850003 receive discard packets high 32bits ............... 2812 C901850004 receive bytes flag........................................ 2812 C901850005 receive bytes low 32bits .............................. 2813 C901850006 receive bytes high 32bits ............................. 2813 C901850007 receive packets flag .................................... 2813 C901850008 receive packets low 32bits ........................... 2814 C901850009 receive packets high 32bits .......................... 2814 C901850010 receive broadcast packets flag ...................... 2814 C901850011 receive broadcast packets low 32bits ............. 2815 C901850012 receive broadcast packets high 32bits............ 2815 C901850013 receive multicast packets flag ....................... 2815 C901850014 receive multicast packets low 32bits .............. 2816 C901850015 receive multicast packets high 32bits............. 2816 C901850016 receive CRC or align error packets flag........... 2816 C901850017 receive CRC or align error packets low 32bits .......................................................................... 2817 C901850018 receive CRC or align error packets high 32bits .......................................................................... 2817 C901850019 receive small than 64 bytes packets flag......... 2817 C901850020 receive small than 64 bytes packets low 32bits .......................................................................... 2818 C901850021 receive small than 64 bytes packets high 32bits .......................................................................... 2818 C901850022 receive large than 1518 bytes packets flag ............................................................................. 2818 C901850023 receive large than 1518 bytes packets low 32bits .......................................................................... 2819 C901850024 receive large than 1518 bytes packets high 32bits .......................................................................... 2819 C901850025 The flag of received fragment packets............ 2819 C901850026 Number of fragment packets received (low 32 bit).............................................................................. 2820 C901850027 Number of received fragment packets (high 32 bit).............................................................................. 2820 C901850028 receive Jabber packets flag .......................... 2820 C901850029 receive Jabber packets low 32bits ................. 2821 C901850030 receive Jabber packets high 32bits ................ 2821 C901850031 receive Collision count flag ........................... 2821 C901850032 receive Collision count low 32bits .................. 2822 C901850033 receive Collision count high 32bits................. 2822 C901850034 receive 64 bytes packets flag........................ 2822 C901850035 receive 64 bytes packets low 32bits............... 2823 C901850036 receive 64 bytes packets high 32bits ............. 2823
2809
C901850037 receive 65 to 127 bytes packets flag.............. 2823 C901850038 receive 65 to 127 bytes packets low 32bits .......................................................................... 2824 C901850039 receive 65 to 127 bytes packets high 32bits .......................................................................... 2824 C901850040 receive 128 to 255 bytes packets flag ............ 2824 C901850041 receive 128 to 255 bytes packets low 32bits .......................................................................... 2825 C901850042 receive 128 to 255 bytes packets high 32bits .......................................................................... 2825 C901850043 receive 256 to 511 bytes packets flag ............ 2825 C901850044 receive 256 to 511 bytes packets low 32bits .......................................................................... 2826 C901850045 receive 256 to 511 bytes packets high 32bits .......................................................................... 2826 C901850046 receive 512 to 1023 bytes packets flag .......... 2826 C901850047 receive 512 to 1023 bytes packets low 32bits .......................................................................... 2827 C901850048 receive 512 to 1023 bytes packets high 32bits .......................................................................... 2827 C901850049 receive 1024 to 1518 bytes packets flag......... 2827 C901850050 receive 1024 to 1518 bytes packets low 32bits .......................................................................... 2828 C901850051 receive 1024 to 1518 bytes packets high 32bits .......................................................................... 2828 C901850052 send discard packets flag ............................. 2828 C901850053 send discard packets low 32bits .................... 2829 C901850054 send discard packets high 32bits................... 2829 C901850055 send packet bytes flag ................................. 2829 C901850056 send packet bytes low 32bits........................ 2830 C901850057 send packets bytes high 32bits ..................... 2830 C901850058 send packets flag ........................................ 2830 C901850059 send packets low 32bits ............................... 2831 C901850060 send packets high 32bits.............................. 2831 C901850061 send broadcast packets flag ......................... 2831 C901850062 send broadcast packets low 32bits ................ 2832 C901850063 send broadcast packets high 32bits ............... 2832 C901850064 send multicast packets flag .......................... 2832 C901850065 send multicast packets low 32bits ................. 2833 C901850066 send multicast packets high 32bits ................ 2833 C901850067 send CRC or Align error packets flag.............. 2833 C901850068 send CRC or Align error packets low 32bits .......................................................................... 2834 C901850069 send CRC or Align error packets high 32bits .......................................................................... 2834 C901850070 send small than 64 bytes packets flag ........... 2834 C901850071 send small than 64 bytes packets low 32bits .......................................................................... 2835 C901850072 send small than 64 bytes packets high 32bits .......................................................................... 2835 C901850073 send large than 1518 bytes packets flag......... 2835 C901850074 send large than 1518 bytes packets low 32bits .......................................................................... 2836 C901850075 send large than 1518 bytes packets high 32bits .......................................................................... 2836 C901850076 The flag of sent fragment packets ................. 2836 C901850077 Number of sent fragment packets (low 32 bit).............................................................................. 2837 C901850078 Number of sent fragment packets (high 32 bit).............................................................................. 2837
2810
C901850079 send Jabber packets flag.............................. 2837 C901850080 send Jabber packets low 32bits..................... 2838 C901850081 send Jabber packets high 32bits ................... 2838 C901850082 send Collision count flag .............................. 2838 C901850083 send Collision count low 32bits ..................... 2839 C901850084 send Collision count high 32bits .................... 2839 C901850085 send 64 bytes packets flag ........................... 2839 C901850086 send 64 bytes packets low 32bits .................. 2840 C901850087 send 64 bytes packets high 32bits................. 2840 C901850088 send 65 to 127 bytes packets flag ................. 2840 C901850089 send 65 to 127 bytes packets low 32bits......... 2841 C901850090 send 65 to 127 bytes packets high 32bits......... 2841 C901850091 send 128 to 255 bytes packets flag ............... 2841 C901850092 send 128 to 255 bytes packets low 32bits......... 2842 C901850093 send 128 to 255 bytes packets high 32bits .......................................................................... 2842 C901850094 send 256 to 511 bytes packets flag ............... 2842 C901850095 send 256 to 511 bytes packets low 32bits......... 2843 C901850096 send 256 to 511 bytes packets high 32bits .......................................................................... 2843 C901850097 send 512 to 1023 bytes packets flag ............. 2843 C901850098 send 512 to 1023 bytes packets low 32bits .......................................................................... 2844 C901850099 send 512 to 1023 bytes packets high 32bits .......................................................................... 2844 C901850100 send 1024 to 1518 bytes packets flag............ 2844 C901850101 send 1024 to 1518 bytes packets low 32bits .......................................................................... 2845 C901850102 send 1024 to 1518 bytes packets high 32bits .......................................................................... 2845 C901850103 Logic port type ........................................... 2845
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.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid.
2811
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
This counter records the lower 32 bits of the statistic item of discarded packet in the receiving direction. This counter is used to find out the amount of packets discarded in the receiving direction. The counter counts when the packet is received.
This counter records the higher 32 bits of the statistic item of discarded packet in the receiving direction. This counter is used to find out the amount of packets discarded in the receiving direction. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2812
Measurement Point
None
This counter records the lower 32 bits of the statistic item of total bytes of received packets. This counter is used to find out the total number of bytes received. The counter counts when the packet is received.
This counter records the higher 32 bits of the statistic item of total bytes of received packets. This counter is used to find out the total number of bytes received. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2813
Measurement Point
None
This counter records the lower 32 bits of the statistic item of the number of received packets. This counter is used to find out the number of packets received. The counter counts when the packet is received.
This counter records the higher 32 bits of the statistic item of the number of received packets. This counter is used to find out the number of packets received. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2814
Measurement Point
None
This counter records the lower 32 bits of the statistic item of the number of received broadcast packets. This counter is used to find out the number of broadcast packets received. The counter counts when the packet is received.
This counter records the higher 32 bits of the statistic item of the number of received broadcast packets. This counter is used to find out the number of broadcast packets received. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2815
Measurement Point
None
This counter records the lower 32 bits of the statistic item of the number of received multicast packets. This counter is used to find out the number of multicast packets received. The counter counts when the packet is received.
This counter records the higher 32 bits of the statistic item of the number of received multicast packets. This counter is used to find out the number of multicast packets received. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2816
Measurement Point
None
This counter records the lower 32 bits of the statistic item of the number of received CRC or alignment error packets. This counter is used to find out the number of received CRC or alignment error packets. The counter counts when the packet is received.
This counter records the higher 32 bits of the statistic item of the number of received CRC or alignment error packets. This counter is used to find out the number of received CRC or alignment error packets. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2817
Measurement Point
None
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. This counter is used to find out the number of received packets of which the size is smaller than 64 bytes. The counter counts when the packet is received.
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. This counter is used to find out the number of received packets of which the size is smaller than 64 bytes. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid.
2818
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
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. This counter is used to find out the number of received packets of which the size is larger than 1518 bytes. The counter counts when the packet is received.
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. This counter is used to find out the number of received packets of which the size is larger than 1518 bytes. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are
2819
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
This counter records the lower 32 bits of the statistic item of the number of received fragment packets. This counter is used to find out the number of received fragment packets. The counter counts when the packet is received.
This counter records the higher 32 bits of the statistic item of the number of received fragment packets. This counter is used to find out the number of received fragment packets. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless.
2820
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
This counter records the lower 32 bits of the statistic item of the number of received Jabber packets. This counter is used to find out the number of received Jabber packets. The counter counts when the packet is received.
This counter records the higher 32 bits of the statistic item of the number of received Jabber packets. This counter is used to find out the number of received Jabber packets. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid.
2821
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
This counter records the lower 32 bits of the statistic item of the number of received collisions. This counter is used to find out the number of received collisions. The counter counts when the packet is received.
This counter records the higher 32 bits of the statistic item of the number of received collisions. This counter is used to find out the number of received collisions. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2822
Measurement Point
None
This counter records the lower 32 bits of the statistic item of the number of received packets of which the size is 64 bytes. This counter is used to find out the number of received packets of which the size is 64 bytes. The counter counts when the packet is received.
This counter records the higher 32 bits of the statistic item of the number of received packets of which the size is 64 bytes. This counter is used to find out the number of received packets of which the size is 64 bytes. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2823
Measurement Point
None
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. This counter is used to find out the number of received packets of which the size is between 65 bytes and 127 bytes. The counter counts when the packet is received.
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. This counter is used to find out the number of received packets of which the size is between 65 bytes and 127 bytes. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2824
Measurement Point
None
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. This counter is used to find out the number of received packets of which the size is between 128 bytes and 255 bytes. The counter counts when the packet is received.
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. This counter is used to find out the number of received packets of which the size is between 128 bytes and 255 bytes. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2825
Measurement Point
None
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. This counter is used to find out the number of received packets of which the size is between 256 bytes and 511 bytes. The counter counts when the packet is received.
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. This counter is used to find out the number of received packets of which the size is between 256 bytes and 511 bytes. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2826
Measurement Point
None
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. This counter is used to find out the number of received packets of which the size is between 512 bytes and 1023 bytes. The counter counts when the packet is received.
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. This counter is used to find out the number of received packets of which the size is between 512 bytes and 1023 bytes. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid.
2827
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
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. This counter is used to find out the number of received packets of which the size is between 1024 bytes and 1518 bytes. The counter counts when the packet is received.
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. This counter is used to find out the number of received packets of which the size is between 1024 bytes and 1518 bytes. The counter counts when the packet is received.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are
2828
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
This counter records the lower 32 bits of the statistic item of the number of transmitted packets being discarded. This counter is used to find out the number of transmitted packets being discarded. The counter counts when the packet is transmitted.
This counter records the higher 32 bits of the statistic item of the number of transmitted packets being discarded. This counter is used to find out the number of transmitted packets being discarded. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid.
2829
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
This counter records the lower 32 bits of the statistic item of total bytes of transmitted packets. This counter is used to find out the total number of bytes of transmitted packets. The counter counts when the packet is transmitted.
This counter records the higher 32 bits of the statistic item of total bytes of transmitted packets. This counter is used to find out the total number of bytes of transmitted packets. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2830
Measurement Point
None
This counter records the lower 32 bits of the statistic item of the number of transmitted packets. This counter is used to find out the total number of transmitted packets. The counter counts when the packet is transmitted.
This counter records the higher 32 bits of the statistic item of the number of transmitted packets. This counter is used to find out the total number of transmitted packets. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2831
Measurement Point
None
This counter records the lower 32 bits of the statistic item of the number of transmitted broadcast packets. This counter is used to find out the number of transmitted broadcast packets. The counter counts when the packet is transmitted.
This counter records the higher 32 bits of the statistic item of the number of transmitted broadcast packets. This counter is used to find out the number of transmitted broadcast packets. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2832
Measurement Point
None
This counter records the lower 32 bits of the statistic item of the number of transmitted multicast packets. This counter is used to find out the number of transmitted multicast packets. The counter counts when the packet is transmitted.
This counter records the higher 32 bits of the statistic item of the number of transmitted multicast packets. This counter is used to find out the number of transmitted multicast packets. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2833
Measurement Point
None
This counter records the lower 32 bits of the statistic item of the number of transmitted CRC or alignment error packets. This counter is used to find out the number of transmitted CRC or alignment error packets. The counter counts when the packet is transmitted.
This counter records the higher 32 bits of the statistic item of the number of transmitted CRC or alignment error packets. This counter is used to find out the number of transmitted CRC or alignment error packets. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2834
Measurement Point
None
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. This counter is used to find out the number of transmitted packets of which the size is smaller than 64 bytes. The counter counts when the packet is transmitted.
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. This counter is used to find out the number of transmitted packets of which the size is smaller than 64 bytes. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid.
2835
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
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. This counter is used to find out the number of transmitted packets of which the size is larger than 1518 bytes. The counter counts when the packet is transmitted.
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. This counter is used to find out the number of transmitted packets of which the size is larger than 1518 bytes. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are
2836
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
This counter records the lower 32 bits of the statistic item of the number of transmitted fragment packets. This counter is used to find out the number of transmitted fragment packets. The counter counts when the packet is transmitted.
This counter records the higher 32 bits of the statistic item of the number of transmitted fragment packets. This counter is used to find out the number of transmitted fragment packets. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are
2837
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
This counter records the lower 32 bits of the statistic item of the number of transmitted Jabber packets. This counter is used to find out the number of transmitted Jabber packets. The counter counts when the packet is transmitted.
This counter records the higher 32 bits of the statistic item of the number of transmitted Jabber packets. This counter is used to find out the number of transmitted Jabber packets. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid.
2838
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
This counter records the lower 32 bits of the statistic item of the number of transmitted collisions. This counter is used to find out the number of transmitted collisions. The counter counts when the packet is transmitted.
This counter records the higher 32 bits of the statistic item of the number of transmitted collisions. This counter is used to find out the number of transmitted collisions. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2839
Measurement Point
None
This counter records the lower 32 bits of the statistic item of the number of transmitted packets of which the size is 64 bytes. This counter is used to find out the number of transmitted packets of which the size is 64 bytes. The counter counts when the packet is transmitted.
This counter records the higher 32 bits of the statistic item of the number of transmitted packets of which the size is 64 bytes. This counter is used to find out the number of transmitted packets of which the size is 64 bytes. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2840
Measurement Point
None
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. This counter is used to find out the number of transmitted packets of which the size is between 65 bytes and 127 bytes. The counter counts when the packet is transmitted.
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. This counter is used to find out the number of transmitted packets of which the size is between 65 bytes and 127 bytes. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2841
Measurement Point
None
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. This counter is used to find out the number of transmitted packets of which the size is between 128 bytes and 255 bytes. The counter counts when the packet is transmitted.
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. This counter is used to find out the number of transmitted packets of which the size is between 128 bytes and 255 bytes. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2842
Measurement Point
None
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. This counter is used to find out the number of transmitted packets of which the size is between 256 bytes and 511 bytes. The counter counts when the packet is transmitted.
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. This counter is used to find out the number of transmitted packets of which the size is between 256 bytes and 511 bytes. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid. If BIT4 is set as 1, it indicates that the statistics overflow is detected, however, it does not guarantee that all overflows are detected.
2843
Measurement Point
None
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. This counter is used to find out the number of transmitted packets of which the size is between 512 bytes and 1023 bytes. The counter counts when the packet is transmitted.
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. This counter is used to find out the number of transmitted packets of which the size is between 512 bytes and 1023 bytes. The counter counts when the packet is transmitted.
This counter flags the property of the statistic item. If BIT7 is set as 1, it indicates that the current statistics is invalid, that is, the statistics of the related higher 32 bits and lower 32 bits are meaningless. If BIT6 is set as 1, it indicates that the current statistics is of low precision, the statistics of the related higher 32 bits are invalid, and only the statistics of the related lower 32 bits are valid.
2844
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
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. This counter is used to find out the number of transmitted packets of which the size is between 1024 bytes and 1518 bytes. The counter counts when the packet is transmitted.
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. This counter is used to find out the number of transmitted packets of which the size is between 1024 bytes and 1518 bytes. The counter counts when the packet is transmitted.
This counter records the logic port type (0: internal; 1: external; 0xffffffff: invalid). None None None
2845
2846
Chapter
91
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.
2847
BSC This counter counts the number of handover attempts initiated by MS due to too low uplink receiving strength. This counter is used to find out the frequency of handover initiated by MS due to uplink receiving strength. If the counter's value is large, it indicates that the uplink level is poor. After BSC receives the measurement report, it performs handover decision. If the handover decision indicates that handover is required and the handover is due to uplink receiving strength, the counter increments. The measurement point is A, as shown in Figure 2678.
FIGURE 2678 MEASUREMENT POINT OF DUE TO UPLINK RECEIVED STRENGTH NUMBER
OF HANDOVER ATTEMPTS
Unit
Times
BSC 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 2679.
2848
NUMBER
OF HANDOVER ATTEMPTS
Unit
Times
BSC 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 2680.
FIGURE 2680 MEASUREMENT DUE TO UPLINK QUALITY POINT
OF
NUMBER
OF HANDOVER ATTEMPTS
Unit
Times
2849
BSC 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 2681.
FIGURE 2681 MEASUREMENT DUE TO DOWNLINK QUALITY POINT
OF
NUMBER
OF HANDOVER ATTEMPTS
Unit
Times
BSC 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 due to uplink interference, the counter increments. The measurement point is A, as shown in Figure 2682.
2850
NUMBER
OF HANDOVER ATTEMPTS
Unit
Times
BSC 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 2683.
FIGURE 2683 MEASUREMENT POINT OF DUE TO DOWNLINK INTERFERENCE NUMBER
OF HANDOVER ATTEMPTS
Unit
Times
2851
BSC 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 2684.
FIGURE DUE TO 2684 MEASUREMENT POINT PBGT
OF
NUMBER
OF HANDOVER ATTEMPTS
Unit
Times
BSC 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 mobil-
2852
ity 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 2685.
FIGURE 2685 DUE TO LARGE MEASUREMENT POINT TA
OF
NUMBER
OF HANDOVER ATTEMPTS
Unit
Times
BSC 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 2686.
FIGURE 2686 MEASUREMENT POINT OF DUE TO UPLINK BREAK UP QUICKLY NUMBER
OF HANDOVER ATTEMPTS
2853
Unit
Times
BSC This counter counts the number of handover attempts initiated by MS due to macro-micro switch. If the adjacent cell's level is larger than or equal to the threshold value and the adjacnet cell is a lower-level cell, the macro-micro handover will occur. This counter is used to find out the frequency of handover initiated by MS due to macro-micro switch. The counter's value reflects the traffic absorption of the micro cell. After BSC receives the measurement report, it performs handover decision. If the handover 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 2687.
FIGURE 2687 MEASUREMENT POINT OF DUE TO MACRO-MICRO SWITCH NUMBER
OF HANDOVER ATTEMPTS
Unit
Times
BSC This counter counts the number of MS's handover attempts due to traffic. The handover is initiated by BSC, some traffic of the local cell is moved to the destination cell, which reduces the traffic load of the local cell. This counter is used to find out the frequency of
2854
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 2688.
FIGURE 2688 MEASUREMENT DUE TO HIGH TRAFFIC POINT
OF
NUMBER
OF HANDOVER ATTEMPTS
Unit
Times
C901880012 Number of handover attempts due to a good standard level in FDD adjacent cell
Statistics object Description
BSC This counter counts the number of MS's handover attempts due to good base level in FDD adjacent cell. This counter is used to find out the frequency of handover due to good base level in FDD adjacent cell. The counter's value reflects the traffic absorption in the FDD network. After BSC receives the measurement report, 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 2689.
2855
FIGURE 2689 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS DUE TO A GOOD STANDARD LEVEL IN FDD ADJACENT CELL
Unit
Times
C901880013 Number of handover attempts due to a good standard level in TDD adjacent cell
Statistics object Description
BSC This counter counts the number of MS's handover attempts due to good base level in TDD adjacent cell. This counter is used to find out the frequency of handover due to good base level in TDD adjacent cell. The counter's value reflects the traffic absorption in the TDD network. After BSC receives the measurement report, 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 2690.
FIGURE 2690 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS DUE TO A GOOD STANDARD LEVEL IN TDD ADJACENT CELL
Unit
Times
2856
BSC This counter counts the number of MS's handover attempts due to Packet Cell Change Notification (PCCN). This counter is used to find out the frequency of handover due to Packet Cell Change Notification (PCCN). The counter's value reflects that the local cell's signal is weaker than that of the destination cell specified by PCCN. After BSC receives PCCN, if both the cell and MS support PS handover and the cell allows handover due to PCCN, then MS attempts PS handover, and the counter increments. The measurement point is A, as shown in Figure 2691.
FIGURE DUE TO 2691 MEASUREMENT POINT PCCN
OF
NUMBER
OF HANDOVER ATTEMPTS
Unit
Times
2857
2858
Chapter
92
2859
C901890026 Number of successful 2G to FDD handovers ......................................................................... 2879 C901890027 Number of 2G to TDD handover attempts......... 2880 C901890028 Number of 2G to TDD handover executions ............................................................................ 2880 C901890029 Number of successful 2G to TDD handovers ......................................................................... 2881 C901890030 Number of 3G to 2G handover attempts......... 2882 C901890031 Number of 3G to 2G handover executions ............................................................................ 2882 C901890032 Number of successful 3G to 2G handovers ......................................................................... 2883 C901890033 Number of T12 expiry.................................. 2884 C901890034 Number of PCCF received............................. 2884 C901890035 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause Create PFC Failure .............. 2885 C901890036 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause PS Handover Target not allowed ....................................................................... 2886 C901890037 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause PS Handover not Supported in Target BSS or Target System........................................... 2887 C901890038 Number of PS-HANDOVER-REQUIRED-NACK messages received with cause other reasons..................... 2887 C901890039 Number of failure in optimised handover due to failure alloc resource ..................................................... 2888 C901890040 Number of failure in optimised handover due to PS handover not supported in target cell .......................... 2889
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.
Cell This counter counts the number of synchronous handovers initiated by MS in the source cell. The source cell and destination cell of the synchronous handover are under the same site. This counter is used to find out the frequency of the synchronous handover initiated by MS in the source cell. It is one of the parameters that evaluate the radio environment. When BSC sends the PS HAN-
2860
DOVER COMMAND message to MS, if the handover is synchronous handover, then the counter increments. The measurement point is A, as shown in Figure 2692.
FIGURE 2692 MEASUREMENT POINT
HANDOVER EXECUTIONS OF
NUMBER
OF SYNCHRONOUS
Unit
Times
Cell This counter counts the number of successful synchronous handovers initiated by MS in the source cell. This counter is used to find out the number of successful synchronous handovers in the source cell. It helps study the synchronous handover condition. If the handover is synchronous handover and is of normal handover mode, then MS performs handover to the channel allocated in the new cell after receiving the PS HANDOVER COMMAND message. After the new cell receives the first correct RLC/MAC block, the PS HANDOVER COMPLETE message is sent to SGSN, then SGSN sends the DELETE BSS PFC message to notify the source cell to release radio resource. When the source cell receives the DELETE BSS PFC message, it indicates that the handover is completed, and the counter increments. The measurement point is A, as shown in Figure 2693. If the handover is synchronous handover and is of optimized handover mode, then MS performs handover to the channel allocated in the new cell after receiving the PS HANDOVER COMMAND message. After the new cell receives the first correct RLC/MAC block, the PS HANDOVER COMPLETE message is sent to SGSN, and the optimized handover complete command (PS_OPTHO_END) is sent to the source cell. Then, the source cell considers that the handover succeeds, and the counter increments. The measurement point is A, as shown in Figure 2694.
2861
NUMBER
OF SUCCESSFUL
NUMBER
OF SUCCESSFUL
Unit
Times
Cell This counter counts the number of pre-synchronous handovers initiated by MS in the source cell. The source cell and destination cell of the pre-synchronous handover are not under the same site. This counter is used to find out the frequency of the pre-synchronous
2862
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 2695.
FIGURE 2695 MEASUREMENT POINT
HANDOVER EXECUTIONS OF
NUMBER
OF PRE-SYNCHRONOUS
Unit
Times
Cell This counter counts the number of successful pre-synchronous handovers initiated by MS in the source cell. This counter is used to find out the number of successful pre-synchronous handovers in the source cell. It helps study the pre-synchronous handover condition. If the handover is pre-synchronous handover and is of normal handover mode, then, after the new cell receives the first correct RLC/MAC block, the PS HANDOVER COMPLETE message is sent to SGSN, and SGSN sends the DELETE BSS PFC message to notify the source cell to release radio resource. When the source cell receives the DELETE BSS PFC message, it indicates that the handover is completed, and the counter increments. The measurement point is A, as shown in Figure 2696. If the handover is pre-synchronous handover and is of optimized handover mode, then, after the new cell receives the first correct RLC/MAC block, the PS HANDOVER COMPLETE message is sent to SGSN, and the optimized handover complete command (PS_OPTHO_END) is sent to the source cell. Then, the source cell considers that the handover succeeds, and the counter increments. The measurement point is A, as shown in Figure 2697.
2863
POINT
OF
NUMBER
OF PRE-SYNCHRONOUS
POINT
OF
NUMBER
OF PRE-SYNCHRONOUS
Unit
Times
Cell This counter counts the number of asynchronous handovers initiated by MS in the source cell. The source cell and destination cell of the synchronous handover are not under the same site. This counter is used to find out the frequency of the asynchronous
2864
handover initiated by MS in the source cell. It is one of the parameters that evaluate the radio environment. When BSC sends the PS HANDOVER COMMAND message to MS, if the handover is asynchronous handover, then the counter increments. The measurement point is A, as shown in Figure 2698.
FIGURE 2698 MEASUREMENT HANDOVER EXECUTIONS POINT
OF
NUMBER
OF ASYNCHRONOUS
Unit
Times
Cell This counter counts the number of successful asynchronous handovers initiated by MS in the source cell. This counter is used to find out the number of successful asynchronous handovers in the source cell. It helps study the asynchronous handover condition. If the handover is asynchronous handover and is of normal handover mode, then, after the new cell receives the first correct RLC/MAC block, the PS HANDOVER COMPLETE message is sent to SGSN, and SGSN sends the DELETE BSS PFC message to notify the source cell to release radio resource. When the source 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 2699. 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 2700.
2865
POINT (1)
OF
NUMBER
OF SUCCESSFUL
POINT (2)
OF
NUMBER
OF SUCCESSFUL
Unit
Times
Cell This counter counts the number of normal handovers initiated by MS in the source cell. This counter is used to find out the frequency of the normal handover initiated by MS in the source cell. It is one of the parameters that evaluate the radio environment. When BSC sends the PS HANDOVER COMMAND message to MS, if the handover is normal handover, then the counter increments. The measurement point is A, as shown in Figure 2701.
2866
OF
NUMBER
OF NORMAL HANDOVER
Unit
Times
Cell This counter counts the number of successful normal handovers initiated by MS in the source cell. This counter is used to find out the number of successful normal handovers in the source cell. It helps study the normal handover condition. If the handover is of normal handover mode, then, after the new cell receives the first correct RLC/MAC block, the PS HANDOVER COMPLETE message is sent to SGSN, and SGSN sends the DELETE BSS PFC message to notify the source cell to release radio resource. When the source 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 2702.
FIGURE 2702 HANDOVERS MEASUREMENT POINT
OF
NUMBER
OF SUCCESSFUL NORMAL
2867
Unit
Times
Cell This counter counts the number of optimized handover executions initiated by MS in the source cell. During the optimized handover, the source cell and the destination cell have the same NSE and Routing Area Code (RAC). This counter is used to find out the frequency of the optimized handover execution in the source cell. It is one of the parameters that evaluate the radio environment. When BSC sends the PS HANDOVER COMMAND message to MS, if the handover is optimized handover, then the counter increments. The measurement point is A, as shown in Figure 2703.
FIGURE 2703 EXECUTIONS MEASUREMENT POINT
OF
NUMBER
OF OPTIMISED HANDOVER
Unit
Times
Cell This counter counts the number of optimized handovers initiated by MS in the source cell. This counter is used to find out the number of successful optimized handovers in the source cell. It helps study the optimized handover condition. If the handover is of optimized handover mode, then, after the new cell receives the first correct RLC/MAC block, the PS HANDOVER COMPLETE message is sent to SGSN, and the optimized handover complete command
2868
(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 2704.
FIGURE 2704 HANDOVERS MEASUREMENT POINT
OF
NUMBER
OF SUCCESSFUL OPTIMISED
Unit
Times
Cell This counter counts the number of intra-BSC inter-cell outgoing handover attempts initiated by MS in the source cell. This counter is used to find out the frequency of the intra-BSC inter-cell outgoing handover attempt initiated by MS in the source cell. It is one of the parameters that evaluate the radio environment. When user plane receives the handover decision PSHO_PSCmd from control plane, if it requires to initiate intra-BSC inter-cell handover, then the counter increments. The measurement point is A, as shown in Figure 2705.
2869
NUMBER
OF
INTRA-BSC
INTER-CELL
Unit
Times
Cell 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 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 2706.
FIGURE 2706 MEASUREMENT POINT OF OUTGOING HANDOVER EXECUTIONS NUMBER
OF
INTRA-BSC
INTER-CELL
Unit
Times
2870
Cell 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 2707. 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 2708.
FIGURE 2707 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL INTER-CELL OUTGOING HANDOVERS - (1) INTRA-BSC
2871
FIGURE 2708 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL INTER-CELL OUTGOING HANDOVERS - (2)
INTRA-BSC
Unit
Times
BSC This counter counts the number of inter-BSC outgoing handover attempts initiated by MS in the source cell. This counter is used to find out the frequency of the inter-BSC outgoing handover attempt initiated by MS in the source cell. It is one of the parameters that evaluate the radio environment. When user plane receives the handover decision PSHO_PSCmd from control plane, if it requires to initiate inter-BSC handover, then the counter increments. The measurement point is A, as shown in Figure 2709.
FIGURE 2709 MEASUREMENT HANDOVER ATTEMPTS POINT
OF
NUMBER
OF
INTER-BSC
OUTGOING
2872
Unit
Times
BSC 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 2710.
FIGURE 2710 MEASUREMENT HANDOVER EXECUTIONS POINT
OF
NUMBER
OF
INTER-BSC
OUTGOING
Unit
Times
BSC This counter counts the number of successful inter-BSC handovers. This counter is used to find out the frequency of the successful inter-BSC handover initiated by MS in the source cell. 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 2711.
2873
Unit
Times
BSC This counter counts the number of inter-cell incoming handover attempts initiated by MS towards the destination cell. This counter is used to find out the frequency of inter-cell incoming handover attempt initiated by MS. It is one of the parameters that evaluate the radio environment. When the destination BSC receives the SGSN handover request, it indicates that the resource request succeeds, and the counter increments. The measurement point is A, as shown in Figure 2712.
FIGURE 2712 MEASUREMENT POINT
ATTEMPTS OF
NUMBER
OF INCOMING HANDOVER
Unit
Times
2874
BSC This counter counts the number of BSC-controlled inter-cell incoming handover executions initiated by MS towards the destination cell. This counter is used to find out the frequency of BSC-controlled inter-cell incoming handover attempt initiated by MS. It is 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 2713.
FIGURE 2713 MEASUREMENT POINT
EXECUTIONS OF
NUMBER
OF INCOMING HANDOVER
Unit
Times
BSC This counter counts the number of successful BSC-controlled intercell incoming handovers initiated by MS towards the destination cell. This counter is used to find out the frequency of successful BSC-controlled inter-cell incoming handover initiated by MS. It is 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 2714.
2875
MEASUREMENT POINT
OF
NUMBER
OF SUCCESSFUL INCOMING
Unit
Times
Cell This counter counts the number of intra-cell handover attempts. This counter is used to find out the frequency of intra-cell handover attempt initiated by MS. It is one of the parameters that evaluate the radio environment. When BSC receives the measurement report from MS, it performs handover decision. If the handover decision indicates that intra-cell handover is required, the counter increments. The measurement point is A, as shown in Figure 2715.
FIGURE 2715 ATTEMPTS MEASUREMENT POINT
OF
NUMBER
OF
INTRA-CELL
HANDOVER
Unit
Times
2876
Cell This counter counts the number of intra-cell handover executions initiated by MS. This counter is used to find out the frequency of intra-cell handover execution initiated by MS. It is one of the parameters that evaluate the radio environment. After the MAC module in BSC requests for resource successfully or unsuccessfully, the counter increments. Times
Unit
Cell 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. Times
Unit
Cell This counter counts the number of failed intra-cell handovers initiated by MS. This counter is used to find out the frequency of intra-cell handover executions initiated by MS. It is one of the parameters that evaluate the radio environment. After the MAC module in BSC fails to request for resource, the counter increments. Times
Unit
2877
BSC This counter counts the number of 2G-to-FDD handover attempts initiated by MS. This counter is used to find out the frequency of handover attempt from 2G cell to FDD cell initiated by MS. It is 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 2716.
FIGURE 2716 MEASUREMENT POINT
ATTEMPTS OF
NUMBER
OF
2G
TO
FDD
HANDOVER
Unit
Times
BSC 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 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 2717.
2878
OF
NUMBER
OF
2G
TO
FDD
HANDOVER
Unit
Times
BSC This counter counts the number of successful 2G-to-FDD handovers initiated by MS. This counter is used to find out the frequency of successful handover from 2G cell to FDD cell initiated by MS. It is one of the parameters that evaluate the radio environment. When the source BSC receives the DELETE BSS PFC message from SGSN, it indicates that the handover is completed, if the handover is FDD handover, the counter increments. The measurement point is A, as shown in Figure 2718.
FIGURE 2718 MEASUREMENT POINT FDD HANDOVERS
OF
NUMBER
OF SUCCESSFUL
2G
TO
Unit
Times
2879
BSC 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 2719.
FIGURE 2719 MEASUREMENT POINT
ATTEMPTS OF
NUMBER
OF
2G
TO
TDD
HANDOVER
Unit
Times
BSC This counter counts the number of 2G-to-TDD handover executions initiated by MS. This counter is used to find out the frequency of handover execution from 2G cell to TDD cell initiated by MS. It is 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 2720.
2880
OF
NUMBER
OF
2G
TO
TDD
HANDOVER
Unit
Times
BSC This counter counts the number of successful 2G-to-TDD handovers initiated by MS. This counter is used to find out the frequency of successful handover from 2G cell to TDD cell initiated by MS. It is one of the parameters that evaluate the radio environment. When the source BSC receives the DELETE BSS PFC message from SGSN, it indicates that the handover is completed, if the handover is TDD handover, the counter increments. The measurement point is A, as shown in Figure 2721.
FIGURE 2721 MEASUREMENT POINT TDD HANDOVERS
OF
NUMBER
OF SUCCESSFUL
2G
TO
Unit
Times
2881
BSC This counter counts the number of 3G-to-2G outgoing handover attempts initiated by MS. This counter is used to find out the frequency of 3G-to-2G handover attempt initiated by MS. It is one of the parameters that evaluate the radio environment. When the destination BSC receives the resource assignment, if the access cell is 3G cell, the counter increments. The measurement point is A, as shown in Figure 2722.
FIGURE 2722 ATTEMPTS MEASUREMENT POINT
OF
NUMBER
OF
3G
TO
2G
HANDOVER
Unit
Times
BSC This counter counts the number of 3G-to-2G outgoing handover executions initiated by MS. This counter is used to find out the frequency of 3G-to-2G handover execution initiated by MS. It is one 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 2723.
2882
MEASUREMENT POINT
OF
NUMBER
OF
3G
TO
2G
HANDOVER
Unit
Times
BSC This counter counts the number of successful 3G-to-2G incoming handovers initiated by MS. This counter is used to find out the frequency of successful 3G-to-2G handover initiated by MS. It is one 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 2724.
FIGURE 2724 MEASUREMENT POINT 2G HANDOVERS
OF
NUMBER
OF SUCCESSFUL
3G
TO
Unit
Times
2883
BSC This counter counts the number of T12 being timeout. This counter is used to find out the frequency of handover failure due to T12 timeout. When T12 is timeout, the MAC instance in the source cell considers that the handover fails, it records the destination cell of the failed handover and clears the handover flag. If T12 is timeout before BSC disables it, the counter increments. The measurement point is A, as shown in Figure 2725.
FIGURE 2725 MEASUREMENT POINT
OF
NUMBER
OF
T12
EXPIRY
Unit
Times
BSC This counter counts the number of the Packet Cell Change Failure messages received. When handover fails, MS returns to the original cell and sends the Packet Cell Change Failure message to BSC, and BSC sends the PS Handover Cancel message to SGSN. When BSC receives the Packet Cell Change Failure message from MS, the counter increments. The measurement point is A, as shown in Figure 2726.
2884
OF
NUMBER
OF
PCCF
RECEIVED
Unit
Times
C901890035 Number of PS-HANDOVER-REQUIRE D-NACK messages received with cause Create PFC Failure
Statistics object Description
BSC This counter counts the number of received PS Handover Required Nack messages with the cause "Create PFC Failure". This counter is used to find out the frequency of handover failure due to "Create PFC Failure". When BSC receives the PS Handover Required Nack message from SGSN with the cause of "Create PFC Failure", the counter increments. The measurement point is A, as shown in Figure 2727.
FIGURE 2727 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUIRED-NACK MESSAGES RECEIVED WITH CAUSE CREATE PFC FAILURE
Unit
Times
2885
C901890036 Number of PS-HANDOVER-REQUIRE D-NACK messages received with cause PS Handover Target not allowed
Statistics object Description
BSC 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 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 2728.
FIGURE 2728 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUIRED-NACK MESSAGES RECEIVED WITH CAUSE PS HANDOVER TARGET NOT ALLOWED
Unit
Times
2886
C901890037 Number of PS-HANDOVER-REQUIRE D-NACK messages received with cause PS Handover not Supported in Target BSS or Target System
Statistics object Description
BSC 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 2729.
FIGURE 2729 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUIRED-NACK MESSAGES RECEIVED WITH CAUSE PS HANDOVER NOT SUPPORTED IN TARGET BSS OR TARGET SYSTEM
Unit
Times
C901890038 Number of PS-HANDOVER-REQUIRE D-NACK messages received with cause other reasons
Statistics object
BSC
2887
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 2730.
FIGURE 2730 MEASUREMENT POINT OF NUMBER OF PS-HANDOVERREQUIRED-NACK MESSAGES RECEIVED WITH CAUSE OTHER REASONS
Unit
Times
BSC This counter counts the number of handover failure due to resource allocation failure in the optimized handover mode. This counter is used to find out the frequency of handover failure due to resource allocation failure in the optimized handover mode. If RANUMC fails to create MS or RANPS instance, the counter increments. Then, RANUMC sends the EV_RANU_PS_OPTHO_ACK message to the RANUHPMU module in the source cell, and the resource allocation result is written as resource allocation failure in the message. The measurement point is A, as shown in Figure 2731.
2888
FIGURE 2731 MEASUREMENT POINT OF NUMBER OF FAILURE IN OPTIMISED HANDOVER DUE TO RESOURCE ALLCOATION FAILURE
Unit
Times
C901890040 Number of failure in optimised handover due to PS handover not supported in target cell
Statistics object Description
BSC This counter counts the number of handover failures due to that PS handover is not supported in the destination cell in the optimized handover mode. This counter is used to find out the frequency of handover failure due to PS handover not supported in destination cell in the optimized handover mode. When RANPS queries that the cell does not support PS handover, the counter increments. Then, RANPS sends the EV_RANU_PS_OPTHO_ACK message to the RANUHPMU module in the source cell, the resource allocation result is written as destination cell not supporting PS handover in the message, and RANPS instance is released. The measurement point is A, as shown in Figure 2732.
2889
FIGURE 2732 MEASUREMENT POINT OF NUMBER PS HANDOVER NOT SUPPORTED IN TARGET CELL
Unit
Times
2890
Chapter
93
IURG Measurement
Table of Contents Overview...................................................................... 2891 C901900001 Number of relocation requests (on Iur-g)......... 2891 C901900002 Number of relocation executions (on Iur-g) .......................................................................... 2892 C901900003 Number of relocation successes (on Iur-g) .......................................................................... 2894 C901900004 Number of relocation failures due to no valid radio resource (on Iur-g) ................................................ 2895 C901900005 Number of relocation failures due to no valid terrestrial circuit resource (on Iur-g) ................................ 2895 C901900006 Number of relocation failures due to loss of UE handover complete message (on Iur-g) ............................ 2896 C901900007 Number of relocation failures due to MS returning to original channel (on Iur-g) ..................................... 2897 C901900008 Number of relocation failures due to other causes (on Iur-g) .......................................................... 2898
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.
BSC This counter counts the number of ENHANCED RELOCATION RESOURCE REQUEST messages received by BSC at Iur-g interface from RNC. The measurement point is A1, as shown in Figure 2733. (DBS is the database subsystem of BSC software)
2891
OF
Unit
Times
BSC After the radio resource is obtained, the handover relocation acknowledgement message is sent to the opposite end through Iur-g
2892
interface. The measurement point is A2, as shown in Figure 2734. (DBS is the database subsystem of BSC software)
FIGURE 2734 MEASUREMENT POINT
OF
Unit
Times
2893
BSC Connect the link with the core nework and send the handover completion message successfully to the core network. The measurement point is A3, as shown in Figure 2735. (DBS is the database subsystem of BSC software)
OF
Unit
Times
2894
C901900004 Number of relocation failures due to no valid radio resource (on Iur-g)
Statistics object Description
BSC Radio resource request fails. The measurement point is A4, as shown in Figure 2736. (DBS is the database subsystem of BSC software)
FIGURE 2736 MEASUREMENT POINT OF NUMBER OF RELOCATION FAILURES DUE TO NO VALID RADIO RESOURCE (ON IUR-G)
Unit
Times
C901900005 Number of relocation failures due to no valid terrestrial circuit resource (on Iur-g)
Statistics object Description
BSC The terrestrial circuit allocated at A-interface is unavailable. The measurement point is A5, as shown in Figure 2737. (DBS is the database subsystem of BSC software)
2895
FIGURE 2737 MEASUREMENT POINT OF NUMBER TERRESTRIAL CIRCUIT RESOURCE (ON IUR-G)
Unit
Times
C901900006 Number of relocation failures due to loss of UE handover complete message (on Iur-g)
Statistics object Description
BSC Time expires but the handover completion message that indicates MS accesses the network is not received. The measurement point is A6, as shown in Figure 2738. (DBS is the database subsystem of BSC software)
2896
FIGURE 2738 MEASUREMENT POINT OF NUMBER OF RELOCATION FAILURES DUE TO LOSS OF HANDOVER COMPLETE MESSAGE (ON IUR-G)
UE
Unit
Times
C901900007 Number of relocation failures due to MS returning to original channel (on Iur-g)
Statistics object Description
BSC BSC receives the handover relocation response message at Iur-g interface, indicating that MS returns to the original channel. The measurement point is A7, as shown in Figure 2739. (The figure omits the intermediate process, and it only describes the follow-
2897
ing process: RNC initiates handover relocation, UE returns to the original channel, and RNC notifies BSC to release resource.)
FIGURE DUE TO 2739 MEASUREMENT POINT OF NUMBER OF RELOCATION MS RETURNING TO ORIGINAL CHANNEL (ON IUR-G)
FAILURES
Unit
Times
BSC Time expires but the handover request or access failure message is not received from the core network. This counter counts handover failure causes except for those counted by C901900004 ~ C901900007. Times
Unit
2898
Chapter
94
RTCP Measurement
Table of Contents Overview...................................................................... 2899 C901910001 local jitter (CS)........................................... 2899 C901910002 distant jitter (CS)........................................ 2900 C901910003 average one-way delay (CS)......................... 2901 C901910004 maximal one-way delay (CS) ........................ 2903 C901910005 local cumulative fraction lost (CS) ................. 2905 C901910006 distant cumulative fraction lost (CS) .............. 2906 C901910007 local jitter (PS) ........................................... 2907 C901910008 distant jitter (PS) ........................................ 2908 C901910009 average one-way delay (PS) ......................... 2909 C901910010 maximal one-way delay (PS) ........................ 2911 C901910011 local cumulative fraction lost (PS) ................. 2913 C901910012 distant cumulative fraction lost (PS) .............. 2914
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.
CELL This parameter is calculated by IPRB at BSC. Suppose Si is the time stamp of RTP packet i, and Ri is the local clock time when the packet arrives the local end, then, the relative transmission time of the two RTP packets i and j received at the local end is: Relative transmission time = The receiver's clock time when RTP packet arrives - RTP packet's RTP time stamp Relative transmission time difference D(j, i) = (Rj - Sj) - (Ri - Si) Jitter calculation formula: J(i) = J(i - 1) + (|D(i-1, i)| - J(i - 1))/16
2899
Oms_SlaProc accumulates the value within the statistics granularity. When the statistics granularity expires, divide the accumulated value by the number of times of the parameter being received, and fill the average value in the reported data area. The counter's working flow is shown in Figure 2740.
FIGURE 2740 MEASUREMENT POINT
OF LOCAL JITTER
(CS)
Unit
ms
CELL 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 2741.
2900
OF LOCAL JITTER
(CS)
Unit
ms
CELL This parameter is calculated by IPRB. Its physical meaning is the delay between the RTP packet being sent and being received at the opposite end, the calculation formula is: delay = (Current time Previous time - DLSR)/2
2901
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 2742.
2902
(CS)
Unit
ms
CELL This parameter is calculated by IPRB. Its physical meaning is the delay between the RTP packet being sent and being received at the opposite end, the calculation formula is: delay = (Current time Previous time - DLSR)/2
2903
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 2743.
FIGURE 2743 MEASUREMENT POINT
OF MAXIMAL ONE-WAY DELAY
(CS)
2904
Unit
ms
CELL udLocalTotalRcvCnt: Number of accumulatively received packets at the local end within the report interval (the report interval is 5 s in this system) This parameter is calculated by IPRB. IPRB accumulates the number of received RTP packets in uplink, when the report interval expires, subtract the number of received packets 5 s ago from the current number of received packets to calculate the parameter's value. udLocalIntervalLossCnt: Number of accumulatively lost packets at the local end within the report interval This parameter is calculated by IPRB. The number of accumulatively lost packets at the local end is calculated by subtracting the number of actually received packets from the number of expected received packets. The number of accumulatively lost packets at the local end within the report interval is calculated by subtracting the number of lost packets 5 s ago from the current number of accumulatively lost packets at the local end. Oms_SlaProc accumulates the two parameters respectively within the statistics granularity, and marks the two values as udRcv and udLoss. The counter's value is calculated according to the following formula: If (udRcv + udLoss == 0) C901910005 = 0; else C901910005 = 10000 udLoss/(udRcv + udLoss) The counter's working flow is shown in Figure 2744.
2905
(CS)
Unit
CELL udLocalTotalRcvCnt: Number of accumulatively received packets at the local end within the report interval (the report interval is 5 s in this system) This parameter is calculated by IPRB. IPRB accumulates the number of received RTP packets in uplink, when the report interval expires, subtract the number of received packets 5 s ago from the current number of received packets to calculate the parameter's value. udLocalIntervalLossCnt: Number of accumulatively lost packets at the local end within the report interval This parameter is calculated by IPRB. The number of accumulatively lost packets at the local end is calculated by subtracting the
2906
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 2745.
FIGURE 2745 MEASUREMENT POINT
OF DISTANT CUMULATIVE FRACTION LOST
(CS)
Unit
CELL This parameter is calculated by IPRB at BSC. Suppose Si is the time stamp of RTP packet i, and Ri is the local clock time when the packet arrives the local end, then, the relative transmission time of the two RTP packets i and j received at the local end is:
2907
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 2746.
FIGURE 2746 MEASUREMENT POINT
OF LOCAL JITTER
(PS)
Unit
ms
CELL This parameter's value is directly extracted from the RTCP SR packet sent from BTS, saved in IPRB, and reported to Host.
2908
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 2747.
FIGURE 2747 MEASUREMENT POINT
OF DISTANT JITTER
(PS)
Unit
ms
CELL This parameter is calculated by IPRB. Its physical meaning is the delay between the RTP packet being sent and being received at the opposite end, the calculation formula is: delay = (Current time Previous time - DLSR)/2
2909
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 2748.
2910
(PS)
Unit
ms
CELL This parameter is calculated by IPRB. Its physical meaning is the delay between the RTP packet being sent and being received at the opposite end, the calculation formula is: delay = (Current time Previous time - DLSR)/2
2911
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 2749.
FIGURE 2749 MEASUREMENT POINT
OF MAXIMAL ONE-WAY DELAY
(PS)
2912
Unit
ms
CELL udLocalTotalRcvCnt: Number of accumulatively received packets at the local end within the report interval (the report interval is 5 s in this system) This parameter is calculated by IPRB. IPRB accumulates the number of received RTP packets in uplink, when the report interval expires, subtract the number of received packets 5 s ago from the current number of received packets to calculate the parameter's value. udLocalIntervalLossCnt: Number of accumulatively lost packets at the local end within the report interval This parameter is calculated by IPRB. The number of accumulatively lost packets at the local end is calculated by subtracting the number of actually received packets from the number of expected received packets. The number of accumulatively lost packets at the local end within the report interval is calculated by subtracting the number of lost packets 5 s ago from the current number of accumulatively lost packets at the local end. Oms_SlaProc accumulates the two parameters respectively within the statistics granularity, and marks the two values as udRcv and udLoss. The counter's value is calculated according to the following formula: If (udRcv + udLoss == 0) C901910011 = 0; else C901910011 = 10000 udLoss/(udRcv + udLoss) The counter's working flow is shown in Figure 2750.
2913
(PS)
Unit
CELL udDistantIntervalLossCnt: Number of accumulatively lost packets at the opposite end within the report interval IPRB extracts the number of accumulatively lost packets in downlink from SR packet sent from BTS. When the report interval expires, subtract the number of lost packets 5 s ago from the current number of accumulatively lost packets to calculate the parameter's value. udDistantTotalRcvCnt: Number of accumulatively received packets at the opposite end within the report interval This parameter is calculated by IPRB through subtracting the number of lost packets at the opposite end within 5 s from the number of sent packets at the local end within 5 s.
2914
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 2751.
FIGURE 2751 MEASUREMENT POINT
OF DISTANT CUMULATIVE FRACTION LOST
(PS)
Unit
2915
2916
Chapter
95
DSP Measurement
Table of Contents Overview...................................................................... 2917 C901920001 the times of loss of TRAU frame synchronization in BIPB ........................................................................ 2917
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.
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. The counter is used to find out the frequency of search failure of TRAU frame synchronization header. BSC searches the synchronization header after receiving the TRAU frame sent by BTS. The measurement point is A1, as shown in Figure 2752.
2917
POINT
TRAU
FRAME
Unit
Second
2918
Chapter
96
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.
2919
IPAbisPool This counter counts the number of CS service access being rejected due to insufficient uplink Abis bandwidth. It reflects whether the uplink bandwidth of IP bandwidth resource pool, which is related to Abis interface transmission, is appropriate. After BSC receives the resource request from MS, it will allocate resource for MS. If CS service access is rejected due to insufficient uplink Abis bandwidth, the counter increments. The measurement point is A, as shown in Figure 2753.
FIGURE 2753 MEASUREMENT POINT OF NUMBER LACK OF IPABIS BANDWIDTH UPLINK
OF
CS CALL DENIED
FOR
Unit
Times
IPAbisPool This counter counts the number of CS service access being rejected due to insufficient downlink Abis bandwidth. It reflects whether the downlink bandwidth of IP bandwidth resource pool, which is related to Abis interface transmission, is appropriate. After BSC receives the resource request from MS, it will allocate resource for MS. If CS service access is rejected due to insufficient downlink Abis bandwidth, the counter increments. The measurement point is A, as shown in Figure 2754.
2920
OF
CS CALL DENIED
FOR
Unit
Times
IPAbisPool This counter counts the number of PS service access being rejected due to insufficient uplink Abis bandwidth. It reflects whether the uplink bandwidth of IP bandwidth resource pool, which is related to Abis interface transmission, is appropriate. After BSC receives the resource request from MS, it will allocate resource for MS. If PS service access is rejected due to insufficient uplink Abis bandwidth, the counter increments. The measurement point is A, as shown in Figure 2755.
FIGURE 2755 MEASUREMENT POINT OF NUMBER LACK OF IPABIS BANDWIDTH UPLINK
OF
PS CALL DENIED
FOR
Unit
Times
2921
IPAbisPool This counter counts the number of PS service access being rejected due to insufficient downlink Abis bandwidth. It reflects whether the downlink bandwidth of IP bandwidth resource pool, which is related to Abis interface transmission, is appropriate. After BSC receives the resource request from MS, it will allocate resource for MS. If PS service access is rejected due to insufficient downlink Abis bandwidth, the counter increments. The measurement point is A, as shown in Figure 2756.
FIGURE 2756 MEASUREMENT POINT OF NUMBER LACK OF IPABIS BANDWIDTH DOWNLINK
OF
PS CALL DENIED
FOR
Unit
Times
This counter counts the number of pushing down uplink bandwidth in the resource pool. When BSC control plane judges that the actual uplink bandwidth exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool, if the current theoretically allocated uplink bandwidth of resource pool is larger than available uplink bandwidth, BSC control plane sends the message of pushing down uplink bandwidth to BSC user plane, and the counter increments. 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.
Usage
2922
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 2757.
FIGURE 2757 FLOW POOL
OF
IN
RESOURCE
Unit
Times
This counter counts the number of pushing down downlink bandwidth in the resource pool. When BSC control plane judges that the actual downlink bandwidth exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool, if the current theoretically allocated downlink bandwidth of resource pool is larger than available downlink bandwidth, BSC control plane sends the message of pushing down downlink bandwidth to BSC user plane, and the counter increments. 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. The counter counts when BSC control plane sends the message of pushing down downlink bandwidth. The measurement point is A, as shown in Figure 2758.
Usage
Measurement Point
2923
OF
Unit
Times
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. 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. The counter counts when BSC control plane sends the message of pushing up uplink bandwidth. The measurement point is A, as shown in Figure 2759.
FIGURE 2759 FLOW POOL
OF
Usage
Measurement Point
IN
RESOURCE
Unit
Times
2924
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. 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. The counter counts when BSC control plane sends the message of pushing up downlink bandwidth. The measurement point is A, as shown in Figure 2760.
FIGURE 2760 FLOW POOL
OF
Usage
Measurement Point
IN
RESOURCE
Unit
Times
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.
2925
The counting criterion is not that the CS service is initiated successfully but that the Abis resource is preempted successfully.
Usage Measurement Point Unit
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.
2926
Chapter
97
Overview
The principle of dynamic power sharing is: To better use the rated output power of the Power Amplifier (PA) of RRU, the BCCH carrier occupies fixed transmitting power, and other service carriers can dynamically share the transmitting power of RRU. Moreover, to facilitate observing the result of power sharing, several counters are added for power-sharing measurement. Statistic unit in the power-sharing measurement is cell. To use dynamic power sharing, the function of downlink dynamic power control must be enabled first. After services are accessed, the base station increases or decreases the downlink power according to the measurement report result.
2927
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. 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. 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 2761.
FIGURE 2761 POWER SHARING COUNTER 1
Usage
Measurement Point
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
2928
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. 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: The message contains the downlink power adjustment information. The value of degraded dBs (0 dB ~ 30 dB) for the channel by downlink power control is smaller than the value of enhanced dBs (0 dB ~ 1.5 dB) for the carrier by the power level configured in OMCR.
Measurement Point
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. 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.
Usage
2929
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 2763, Figure 2764, and Figure 2765.
FIGURE 2763 ASSIGNMENT FAILURE PROCESS
FOR
DESTINATION CELL
IN
ALLOCATING CHANNEL
FOR
EXTERNAL INCOMING
2930
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. 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. When iBSC allocates CS service channel during the process of assignment or handover, if the function of dynamic power sharing is enabled, there might be several channels that fail to be allocated due to insufficient power of timeslots. The counter increments when a channel fails to be allocated due to insufficient power of timeslot. The measurement points are A1 and B1, as shown in Figure 2766, Figure 2767, and Figure 2768.
FIGURE 2766 C901940004A
Usage
Measurement Point
2931
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. 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.
Usage
2932
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.
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. 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. 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
Measurement Point
2933
2934
Chapter
98
2935
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.
Cell This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell. This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell. It helps check the direction of handover between cells. 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 2769.
FIGURE 2769 MEASUREMENT ON THE ADJACENT CELL - (1) POINT
OF
NUMBER
OF HANDOVER ATTEMPTS
For SGSN-controlled external handover, the counter increments when the source cell sends the handover request message to SGSN. The measurement point is A, as shown in Figure 2770.
2936
POINT
OF
NUMBER
OF HANDOVER ATTEMPTS
Unit
Times
C901950002 Number of successful handovers from selected cell to the adjacent cell
Statistics object Description
Cell This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell. This counter is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell. It helps check the direction of handover between cells. 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 2771.
FIGURE 2771 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL HANDOVERS FROM SELECTED CELL TO THE ADJACENT CELL - (1)
2937
For SGSN-controlled external handover, when the source cell receives the release command issued by SGSN and if the release is due to handover success, then the counter increments. The measurement point is A, as shown in Figure 2772.
FIGURE 2772 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL HANDOVERS FROM SELECTED CELL TO THE ADJACENT CELL - (2)
Unit
Times
C901950003 Number of handover attempts from adjacent cell to the selected cell
Statistics object Description
Cell This counter counts the number of MS's incoming handover attempts from a specific cell to the local cell. This counter is used to find out the number of MS's incoming handover attempts from a specific cell to the local cell. It helps check the direction of handover between cells. 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 2773.
2938
FIGURE 2773 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 2774.
FIGURE 2774 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS FROM ADJACENT CELL TO THE SELECTED CELL - (2)
Unit
Times
C901950004 Number of successful handovers from adjacent cell to the selected cell
Statistics object Description
Cell This counter counts the number of MS's successful incoming handovers from a specific cell to the local cell. This counter is used to find out the number of MS's successful incoming handovers from a specific cell to the local cell. It helps check the direction of handover between cells. For BSC-controlled inter-cell handover, the counter increments when the destination cell receives the handover completion mes-
2939
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 2776.
FIGURE 2776 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL HANDOVERS FROM ADJACENT CELL TO THE SELECTED CELL - (2)
Unit
Times
C901950005 Number of handover attempts from selected cell to the adjacent cell due to better uplink quality
Statistics object Description
Cell This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to uplink qulaity. This counter is used to find out the number of MS's outgoing han-
2940
dover attempts from the local cell to a specific cell due to uplink quality. It helps check the direction of handover between cells. For BSC-controlled inter-cell handover, when the destination cell receives the radio channel request message from the source cell, if the handover is due to uplink quality, the counter increments. The measurement point is A, as shown in Figure 2777.
FIGURE 2777 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 2778.
FIGURE 2778 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO BETTER UPLINK QUALITY - (2)
Unit
Times
2941
C901950006 Number of handover attempts from selected cell to the adjacent cell due to better downlink quality
Statistics object Description
Cell This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to downlink qulaity. This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell due to downlink 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 2779.
FIGURE 2779 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 2780.
2942
FIGURE 2780 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO BETTER DOWNLINK QUALITY - (2)
Unit
Times
C901950007 Number of successful handovers from selected cell to the adjacent cell due to better uplink quality
Statistics object Description
Cell This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to uplink qulaity. This counter is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell due to uplink 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 2781.
2943
FIGURE 2781 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 2782.
FIGURE 2782 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL HANDOVERS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO BETTER UPLINK QUALITY - (2)
Unit
Times
C901950008 Number of successful handovers from selected cell to the adjacent cell due to better downlink quality
Statistics object Description
Cell This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to downlink qulaity. This counter is used to find out the number of MS's successful out-
2944
going 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 2783.
FIGURE 2783 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 2784.
FIGURE 2784 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL HANDOVERS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO BETTER DOWNLINK QUALITY - (2)
Unit
Times
2945
C901950009 Number of handover attempts from selected cell to the adjacent cell due to better uplink strength
Statistics object Description
Cell This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to uplink strength. This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell due to uplink strength. It helps check the direction of handover between cells. 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 2785.
FIGURE 2785 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO BETTER UPLINK STRENGTH - (1)
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 2786.
2946
FIGURE 2786 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO BETTER UPLINK STRENGTH - (2)
Unit
Times
C901950010 Number of handover attempts from selected cell to the adjacent cell due to better downlink strength
Statistics object Description
Cell This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to downlink strength. This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell due to downlink strength. It helps check the direction of handover between cells. 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 2787.
2947
FIGURE 2787 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 2788.
FIGURE 2788 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO BETTER DOWNLINK STRENGTH - (2)
Unit
Times
C901950011 Number of successful handovers from selected cell to the adjacent cell due to better uplink strength
Statistics object Description
Cell This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to uplink strength.
2948
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. 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 2789.
FIGURE 2789 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 2790.
FIGURE 2790 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL HANDOVERS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO BETTER UPLINK STRENGTH - (2)
Unit
Times
2949
C901950012 Number of successful handovers from selected cell to the adjacent cell due to better downlink strength
Statistics object Description
Cell This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to downlink strength. This counter is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell due to downlink 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 2791.
FIGURE 2791 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 2792.
2950
FIGURE 2792 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL HANDOVERS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO BETTER DOWNLINK STRENGTH - (2)
Unit
Times
C901950013 Number of handover attempts from selected cell to the adjacent cell due to PBGT
Statistics object Description
Cell This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to PBGT. This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell due to PBGT. It helps 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 2793.
FIGURE 2793 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO PBGT - (1)
2951
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 2794.
FIGURE 2794 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO PBGT - (2)
Unit
Times
C901950014 Number of successful handovers from selected cell to the adjacent cell due to PBGT
Statistics object Description
Cell This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to PBGT. This counter is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell due to PBGT. It helps 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 2795.
2952
FIGURE 2795 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 2796.
FIGURE 2796 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL HANDOVERS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO PBGT - (2)
Unit
Times
C901950015 Number of handover attempts from selected cell to the adjacent cell due to large TA
Statistics object Description
Cell This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to too large TA. This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell due to too large TA. It helps check the direction of handover between cells. For BSC-controlled inter-cell handover, when the destination cell receives the radio channel request message from the source cell,
2953
if the handover is due to too large TA, the counter increments. The measurement point is A, as shown in Figure 2797.
FIGURE 2797 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO LARGE TA - (1)
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 2798.
FIGURE 2798 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO LARGE TA - (2)
Unit
Times
C901950016 Number of successful handover from selected cell to the adjacent cell due to large TA
Statistics object Description
Cell This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to too large TA. This counter is used to find out the number of MS's successful outgoing
2954
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 2799.
FIGURE 2799 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 2800.
FIGURE 2800 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL HANDOVER FROM SELECTED CELL TO THE ADJACENT CELL DUE TO LARGE TA - (2)
Unit
Times
2955
C901950017 Number of handover attempts from selected cell to the adjacent cell due to high traffic
Statistics object Description
Cell This counter counts the number of MS's outgoing handover attempts from the local cell to a specific cell due to too heavy traffic. This counter is used to find out the number of MS's outgoing handover attempts from the local cell to a specific cell due to too heavy traffic. It helps check the direction of handover between cells. 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 2801.
FIGURE 2801 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 2802.
2956
FIGURE 2802 MEASUREMENT POINT OF NUMBER OF HANDOVER ATTEMPTS FROM SELECTED CELL TO THE ADJACENT CELL DUE TO HIGH TRAFFIC - (2)
Unit
Times
C901950018 Number of successful handover from selected cell to the adjacent cell due to high traffic
Statistics object Description
Cell This counter counts the number of MS's successful outgoing handovers from the local cell to a specific cell due to too heavy traffic. This counter is used to find out the number of MS's successful outgoing handovers from the local cell to a specific cell due to too heavy traffic. It helps check the direction of handover between cells. 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 2803.
FIGURE 2803 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL HANDOVER FROM SELECTED CELL TO THE ADJACENT CELL DUE TO HIGH TRAFFIC - (1)
2957
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 2804.
FIGURE 2804 MEASUREMENT POINT OF NUMBER OF SUCCESSFUL HANDOVER FROM SELECTED CELL TO THE ADJACENT CELL DUE TO HIGH TRAFFIC - (2)
Unit
Times
2958
Chapter
99
LAPDm Measurement
Table of Contents Overview...................................................................... 2960 C902000001 Number of Error Indications due to T200 expired on SDCCH .................................................................... 2961 C902000002 Number of Error Indications due to unsolicited message on SDCCH ....................................................... 2961 C902000003 Number of Error Indications due to unsolicited DM response on SDCCH ................................................. 2962 C902000004 Number of Error Indications due to sequence error on SDCCH ............................................................ 2963 C902000005 Number of Error Indications due to frame content error on SDCCH ...................................................... 2963 C902000006 Number of Error Indications due to SABM command on SDCCH ........................................................... 2964 C902000007 Number of Error Indications due to T200 expired on TCH/F...................................................................... 2965 C902000008 Number of Error Indications due to unsolicited message on TCH/F......................................................... 2965 C902000009 Number of Error Indications due to unsolicited DM response on TCH/F ................................................... 2966 C902000010 Number of Error Indications due to sequence error on TCH/F .............................................................. 2967 C902000011 Number of Error Indications due to frame content error on TCH/F ....................................................... 2967 C902000012 Number of Error Indications due to SABM command on TCH/F ............................................................. 2968 C902000013 Number of Error Indications due to T200 expired on TCH/H ..................................................................... 2969 C902000014 Number of Error Indications due to unsolicited message on TCH/H ........................................................ 2969 C902000015 Number of Error Indications due to unsolicited DM response on TCH/H .................................................. 2970 C902000016 Number of Error Indications due to sequence error on TCH/H ............................................................. 2971 C902000017 Number of Error Indications due to frame content error on TCH/H ....................................................... 2971 C902000018 Number of Error Indications due to SABM command on TCH/H ............................................................ 2972 C902000019 Number of Release Indications due to T200 expired on SDCCH ............................................................ 2973 C902000020 Number of Release Indications due to unsolicited DM response on SDCCH ................................................. 2973 C902000021 Number of Release Indications due to sequence error on SDCCH ............................................................ 2974 C902000022 Number of Release Indications due to T200 expired on TCH/F (signaling) .............................................. 2975
2959
C902000023 Number of Release Indications due to unsolicited DM response on TCH/F (signaling) ................................... 2976 C902000024 Number of Release Indications due to sequence error on TCH/F (signaling) .............................................. 2976 C902000025 Number of Release Indications due to T200 expired on TCH/F (speech)................................................. 2977 C902000026 Number of Release Indications due to unsolicited DM response on TCH/F (speech) ...................................... 2978 C902000027 Number of Release Indications due to sequence error on TCH/F (speech) ................................................. 2979 C902000028 Number of Release Indications due to T200 expired on TCH/F (data) .................................................... 2979 C902000029 Number of Release Indications due to unsolicited DM response on TCH/F (data) ......................................... 2980 C902000030 Number of Release Indications due to sequence error on TCH/F (data) .................................................... 2981 C902000031 Number of Release Indications due to T200 expired on TCH/H (signaling).............................................. 2982 C902000032 Number of Release Indications due to unsolicited DM response on TCH/H (signaling)................................... 2982 C902000033 Number of Release Indications due to sequence error on TCH/H (signaling).............................................. 2983 C902000034 Number of Release Indications due to T200 expired on TCH/H (speech) ................................................ 2984 C902000035 Number of Release Indications due to unsolicited DM response on TCH/H (speech) ..................................... 2985 C902000036 Number of Error Indications due to sequence error on TCH/H (speech) ................................................ 2985 C902000037 Number of Release Indications due to T200 expired on TCH/H (data).................................................... 2986 C902000038 Number of Release Indications due to unsolicited DM response on TCH/H (data) ......................................... 2987 C902000039 Number of Release Indications due to sequence error on TCH/H (data) .................................................... 2988 C902000040 Number of Release Indications without Error Ind on SDCCH .................................................................... 2988 C902000041 Number of Release Indications without Error Ind on TCH/F (signaling) ...................................................... 2989 C902000042 Number of Release Indications without Error Ind on TCH/F (speech)......................................................... 2989 C902000043 Number of Release Indications without Error Ind on TCH/F (data) ............................................................ 2990 C902000044 Number of Release Indications without Error Ind on TCH/H (signaling) ..................................................... 2990 C902000045 Number of Release Indications without Error Ind on TCH/H (speech) ........................................................ 2990 C902000046 Number of Release Indications without Error Ind on TCH/H (data)............................................................ 2991
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.
2960
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2805.
FIGURE 2805 NUMBER ON SDCCH
OF
Usage
Measurement Point
ERROR INDICATIONS
DUE TO
T200
EXPIRED
Unit
Times
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". This counter counts the number of ERROR INDICATION messages, received by BSC from BTS, that contain the cause of "unsolicited message".
Usage
2961
The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2806.
FIGURE 2806 NUMBER OF MESSAGE ON SDCCH ERROR INDICATIONS
DUE TO UNSOLICITED
Unit
Times
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2807.
FIGURE 2807 NUMBER OF RESPONSE ON SDCCH ERROR INDICATIONS
DUE TO UNSOLICITED
Usage
Measurement Point
DM
Unit
Times
2962
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2808.
FIGURE 2808 NUMBER ON SDCCH
OF
Usage
Measurement Point
ERROR INDICATIONS
Unit
Times
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2809.
Usage
Measurement Point
2963
ERROR INDICATIONS
Unit
Times
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2810.
FIGURE 2810 ON SDCCH NUMBER
OF
Usage
Measurement Point
ERROR INDICATIONS
DUE TO
SABM
COMMAND
Unit
Times
2964
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2811.
FIGURE 2811 NUMBER ON TCH/F
OF
Usage
Measurement Point
ERROR INDICATIONS
DUE TO
T200
EXPIRED
Unit
Times
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2812.
Usage
Measurement Point
2965
ERROR INDICATIONS
DUE TO UNSOLICITED
Unit
Times
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2813.
FIGURE 2813 C902000009
Usage
Measurement Point
Unit
Times
2966
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2814.
FIGURE 2814 NUMBER ON TCH/F
OF
Usage
Measurement Point
ERROR INDICATIONS
Unit
Times
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2815.
Usage
Measurement Point
2967
ERROR INDICATIONS
Unit
Times
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2816.
FIGURE 2816 ON TCH/F NUMBER
OF
Usage
Measurement Point
ERROR INDICATIONS
DUE TO
SABM
COMMAND
Unit
Times
2968
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2817.
FIGURE 2817 NUMBER ON TCH/H
OF
Usage
Measurement Point
ERROR INDICATIONS
DUE TO
T200
EXPIRED
Unit
Times
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2818.
Usage
Measurement Point
2969
ERROR INDICATIONS
DUE TO UNSOLICITED
Unit
Times
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2819.
FIGURE 2819 NUMBER OF RESPONSE ON TCH/H ERROR INDICATIONS
DUE TO UNSOLICITED
Usage
Measurement Point
DM
Unit
Times
2970
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2820.
FIGURE 2820 NUMBER ON TCH/H
OF
Usage
Measurement Point
ERROR INDICATIONS
Unit
Times
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2821.
Usage
Measurement Point
2971
ERROR INDICATIONS
Unit
Times
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". 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. The counter counts when BSC receives the ERROR INDICATION message. The measurement point is A, as shown in Figure 2822.
FIGURE 2822 ON TCH/H NUMBER
OF
Usage
Measurement Point
ERROR INDICATIONS
DUE TO
SABM
COMMAND
Unit
Times
2972
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". 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. 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 2823.
FIGURE 2823 ON SDCCH NUMBER
OF
Usage
Measurement Point
RELEASE INDICATIONS
DUE TO
T200
EXPIRED
Unit
Times
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 "unsolicited DM response".
2973
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. 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 2824.
FIGURE 2824 NUMBER OF RELEASE INDICATIONS DM RESPONSE ON SDCCH
DUE TO UNSOLICITED
Measurement Point
Unit
Times
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". 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. 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 2825.
Usage
Measurement Point
2974
NUMBER
OF
RELEASE INDICATIONS
Unit
Times
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". 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. 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 2826.
FIGURE 2826 NUMBER TCH/F (SIGNALING)
OF
Usage
Measurement Point
RELEASE INDICATIONS
DUE TO
T200
EXPIRED ON
Unit
Times
2975
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". 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. 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 2827.
FIGURE 2827 NUMBER OF RELEASE RESPONSE ON TCH/F (SIGNALING) INDICATIONS
DUE TO UNSOLICITED
Usage
Measurement Point
DM
Unit
Times
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
2976
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. 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 2828.
FIGURE 2828 NUMBER OF ON TCH/F (SIGNALING) RELEASE INDICATIONS
DUE TO SEQUENCE ERROR
Measurement Point
Unit
Times
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". 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. 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 2829.
Usage
Measurement Point
2977
RELEASE INDICATIONS
DUE TO
T200
EXPIRED
Unit
Times
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". 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. 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 2830.
FIGURE 2830 NUMBER OF RELEASE INDICATIONS DM RESPONSE ON TCH/F (SPEECH)
DUE TO UNSOLICITED
Usage
Measurement Point
Unit
Times
2978
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". 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. 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 2831.
FIGURE 2831 NUMBER OF ON TCH/F (SPEECH) RELEASE INDICATIONS
DUE TO SEQUENCE ERROR
Usage
Measurement Point
Unit
Times
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
2979
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. 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 2832.
FIGURE 2832 NUMBER TCH/F (DATA)
OF
Measurement Point
RELEASE INDICATIONS
DUE TO
T200
EXPIRED ON
Unit
Times
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". 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. 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 2833.
Usage
Measurement Point
2980
DUE TO UNSOLICITED
Unit
Times
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". 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. 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 2834.
FIGURE 2834 NUMBER OF ON TCH/F (DATA) RELEASE INDICATIONS
DUE TO SEQUENCE ERROR
Usage
Measurement Point
Unit
Times
2981
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". 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. 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 2835.
FIGURE 2835 NUMBER TCH/H (SIGNALING)
OF
Usage
Measurement Point
RELEASE INDICATIONS
DUE TO
T200
EXPIRED ON
Unit
Times
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
2982
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. 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 2836.
FIGURE 2836 NUMBER OF RELEASE INDICATIONS DUE TO UNSOLICITED RESPONSE ON TCH/H (SIGNALING) DM
Measurement Point
Unit
Times
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". 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. 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 2837.
Usage
Measurement Point
2983
RELEASE INDICATIONS
Unit
Times
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". 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. 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 2838.
FIGURE 2838 NUMBER OF ON TCH/H (SPEECH) RELEASE INDICATIONS
DUE TO
Usage
Measurement Point
T200
EXPIRED
Unit
Times
2984
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". 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. 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 2839.
FIGURE 2839 NUMBER OF RELEASE INDICATIONS DM RESPONSE ON TCH/H (SPEECH)
DUE TO UNSOLICITED
Usage
Measurement Point
Unit
Times
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
2985
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. 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 2840.
FIGURE 2840 NUMBER OF ON TCH/H (SPEECH) ERROR INDICATIONS
DUE TO SEQUENCE ERROR
Measurement Point
Unit
Times
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". 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. 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 2841.
Usage
Measurement Point
2986
RELEASE INDICATIONS
DUE TO
T200
EXPIRED
Unit
Times
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". 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. 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 2842.
FIGURE 2842 NUMBER OF RELEASE INDICATIONS DM RESPONSE ON TCH/H (DATA)
DUE TO UNSOLICITED
Usage
Measurement Point
Unit
Times
2987
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". 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. 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 2843.
FIGURE 2843 NUMBER OF ON TCH/H (DATA) RELEASE INDICATIONS
DUE TO SEQUENCE ERROR
Usage
Measurement Point
Unit
Times
This counter counts the times of receiving the Abis Rel Ind message without receiving the Abis Error Ind message when the MS occupies the SDCCH. None
Usage
2988
None Time
This counter counts the times of receiving the Abis Rel Ind message without receiving the Abis Error Ind message when the MS occupies the TCH/F signaling channel. None None Time
This counter counts the times of receiving the Abis Rel Ind message without receiving the Abis Error Ind message when the MS occupies the TCH/F speech channel. None None Time
2989
This counter counts the times of receiving the Abis Rel Ind message without receiving the Abis Error Ind message when the MS occupies the TCH/F data channel. None None Time
This counter counts the times of receiving the Abis Rel Ind message without receiving the Abis Error Ind message when the MS occupies the TCH/H signaling channel. None None Time
This counter counts the times of receiving the Abis Rel Ind message without receiving the Abis Error Ind message when the MS occupies the TCH/H speech channel. None None
2990
Unit
Time
This counter counts the times of receiving the Abis Rel Ind message without receiving the Abis Error Ind message when the MS occupies the TCH/H data channel. None None Time
2991
2992
Chapter
100
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 2844.
2993
OF
PS-BANDWIDTH ALLOCATION
The measurement point of access control cause statistics for CS-bandwidth allocation is shown in Figure 2845.
FIGURE 2845 ACCESS CONTROL
OF
CS-BANDWIDTH ALLOCATION
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. 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. 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 2846.
Usage
Measurement Point
2994
Unit
Times
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. 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. 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 2847.
FIGURE 2847 NUMBER C2
OF
Usage
Measurement Point
THAN
2995
Unit
Times
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: BSC control plane judges that the actual uplink bandwidth of the resource pool is smaller than C2, which is the safe allocation lower limit about bandwidth at the resource pool. The actual uplink bandwidth of the resource pool plus theoretically-allocated uplink bandwidth for the service exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool.
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. 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 2848.
FIGURE 2848 AND CURRENT NUMBER OF THAT SUM OF PS UPLINK BANDWIDTH MEASURED BANDWIDTH ALLOCATED MORE THAN C1
Measurement Point
2996
Unit
Times
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. 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. 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 2849.
FIGURE 2849 NUMBER THAN OVERBOOKING
OF
Usage
Measurement Point
Unit
Times
2997
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. 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. 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 2850.
FIGURE 2850 NUMBER THAN C2
OF
Usage
Measurement Point
Unit
Times
2998
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: BSC control plane judges that the actual downlink bandwidth of the resource pool is smaller than C2, which is the safe allocation lower limit about bandwidth at the resource pool. The actual downlink bandwidth of the resource pool plus theoretically-allocated downlink bandwidth for the service exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool.
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. 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, 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 2851.
FIGURE 2851 NUMBER OF THAT SUM OF PS DOWNLINK BANDWIDTH MEASURED AND CURRENT BANDWIDTH ALLOCATED MORE THAN C1
Measurement Point
Unit
Times
2999
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. 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. 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 2852.
FIGURE 2852 NUMBER OF THAN OVERBOOKING CS UPLINK BANDWIDTH ALLOCATED MORE
Usage
Measurement Point
Unit
Times
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.
3000
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. 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 2853.
FIGURE 2853 NUMBER C2
OF
Measurement Point
THAN
Unit
Times
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: BSC control plane judges that the actual uplink bandwidth of the resource pool is smaller than C2, which is the safe allocation lower limit about bandwidth at the resource pool. The actual uplink bandwidth of the resource pool plus theoretically-allocated uplink bandwidth for the service exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool.
3001
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 2854.
FIGURE 2854 AND CURRENT NUMBER OF THAT SUM OF CS UPLINK BANDWIDTH MEASURED BANDWIDTH ALLOCATED MORE THAN C1
Times
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. 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. When BSC has new CS service to be activated, if BSC control plane judges that the allocated downlink bandwidth exceeds OverBook-
Usage
Measurement Point
3002
ing, the counter counts. The measurement point is A, as shown in Figure 2855.
FIGURE 2855 NUMBER THAN OVERBOOKING
OF
Unit
Times
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. 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. 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 2856.
Usage
Measurement Point
3003
NUMBER
OF
Unit
Times
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: BSC control plane judges that the actual downlink bandwidth of the resource pool is smaller than C2, which is the safe allocation lower limit about bandwidth at the resource pool. The actual downlink bandwidth of the resource pool plus theoretically-allocated downlink bandwidth for the service exceeds C1, which is the safe allocation upper limit about bandwidth at the resource pool.
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. 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, 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 2857.
Measurement Point
3004
FIGURE 2857 NUMBER OF THAT SUM OF CS DOWNLINK BANDWIDTH MEASURED AND CURRENT BANDWIDTH ALLOCATED MORE THAN C1
Unit
Times
3005
3006
Chapter
101
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
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 2858.
3007
Times BSC
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 2859.
Times
3008
Statistics Object
BSC
This counter counts the number of failures in setting up VGCS. When BSC sends the VGCS SETUP REFUSE message (corresponding to VGCS call) to MSC, the counter increments. The measurement point is A1, as shown in Figure 2860.
Times BSC
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 2861.
3009
Times BSC
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 2862.
Times
3010
Statistics Object
BSC
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 2863.
Times BSC
3011
3012
Chapter
102
VGCS Measurement
Table of Contents Overview...................................................................... 3014 C902030001 Number of VGCS assignment attempts .......... 3014 C902030002 Number of VGCS assignment success ............ 3015 C902030003 Number of VGCS assignment failure .............. 3015 C902030004 Number of VGCS Inter-BSC outgoing handover attempts of Talker ......................................................... 3016 C902030005 Number of VGCS Inter-BSC outgoing handover execution of Talker ........................................................ 3017 C902030006 Number of VGCS Inter-BSC outgoing handover success of Talker ........................................................... 3018 C902030007 Number of VGCS Inter-BSC outgoing handover failure of Talker ............................................................. 3019 C902030008 Number of VGCS Inter-BSC incoming handover attempts of Talker ......................................................... 3020 C902030009 Number of VGCS Inter-BSC incoming handover execution of Talker ........................................................ 3021 C902030010 Number of VGCS Inter-BSC incoming handover success of Talker ........................................................... 3021 C902030011 Number of VGCS channel request attempts for NOTIFICATION RESPONSE of Listener............................... 3022 C902030012 Number of VGCS channel request success for NOTIFICATION RESPONSE of Listener............................... 3023 C902030013 Number of VGCS channel request failure for NOTIFICATION RESPONSE of Listener................................... 3024 C902030014 Number of VGCS channel release for Listener detection...................................................................... 3025 C902030015 Number of Talker drops due to radio link failure .............................................................................. 3026 C902030016 Number of Talker quit .................................. 3027 C902030017 Number of attempts for Listener uplink request ........................................................................... 3027 C902030018 Number of VGCS Intra-BSC Inter-cell outgoing handover attempts of Talker............................................ 3028 C902030019 Number of VGCS Intra-BSC Inter-cell outgoing handover execution of Talker........................................... 3029 C902030020 Number of VGCS Intra-BSC Inter-cell outgoing handover success of Talker ............................................. 3030 C902030021 Number of VGCS Intra-BSC Inter-cell outgoing handover failure of Talker ............................................... 3031 C902030022 Number of VGCS Intra-BSC Inter-cell incoming handover attempts of Talker............................................ 3032 C902030023 Number of VGCS Intra-BSC Inter-cell incoming handover execution of Talker........................................... 3033 C902030024 Number of VGCS Intra-BSC Inter-cell incoming handover success of Talker ............................................. 3034 C902030025 Number of NCH overflow of VGCS ................. 3034
3013
C902030026 Number of successes for Listener uplink request ........................................................................... 3035 C902030027 Number of failures for Listener uplink request ........................................................................... 3036
Overview
This measurement performs statistics for performance indices of voice group call service flow, which involves VGCS assignment, Talker handover, Listener notification response, and NCH overflow. Statistics object: cell
This counter counts the number of assignment attempts due to VGCS. When BSC receives the VGCS ASSIGNMENT REQUEST message (indicating VGCS call) of corresponding legal cell from MSC, the counter increments. The measurement point is A1, as shown in Figure 2864.
Times
3014
Statistics Object
Cell
This counter counts the number of successful assignments due to VGCS. When BSC sends the VGCS ASSIGNMENT RESULT message (corresponding to VGCS call) to MSC as response to the VGCS ASSIGNMENT REQUEST message, the counter increments. The measurement point is A2, as shown in Figure 2865.
Times Cell
This counter counts the number of assignment failures due to VGCS. When BSC receives the VGCS/VBS ASSIGNMENT REQUEST message from MSC, if channel allocation for group call service fails due to one or other reasons, BSC sends the VGCS/VBS ASSIGNMENT FAILURE message to MSC (corresponding to VGCS call), and the counter increments. The measurement point is A1, as shown in Figure 2866.
3015
Times Cell
This counter counts the number of inter-BSC outgoing handover attempts initiated from the source cell by the talker who is having the VGCS service. When BSC receives the measurement report from the talker's mobile phone, if the handover decision indicates inter-cell handover is required but the currently attempted cell is not under the BSC, then the original BSC will send the A_HO_RQD message to MSC to trigger inter-BSC cell handover. In such cases, the counter increments. The measurement point is A1, as shown in Figure 2867.
3016
Times Cell
This counter counts the number of inter-BSC outgoing handover executions initiated from the source cell by the talker who is having the VGCS service. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently attempted cell is not under the BSC, then the original BSC will send the A_HO_RQD message to MSC to trigger inter-BSC cell handover. If the original BSC receives the handover command returned by MSC, the counter increments. The measurement point is A2, as shown in Figure 2868.
3017
Times Cell
This counter counts the number of successful inter-BSC outgoing handovers initiated from the source cell by the talker who is having the VGCS service. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently attempted cell is not under the BSC, then the original BSC will send the A_HO_RQD message to MSC to trigger inter-BSC cell handover. If the mobile phone is successfully accessed to the destination cell, the source cell receives the release command or the HANDOVER SUCCEEDED message issued from MSC. In such cases, the counter increments. The measurement point is A3, as shown in Figure 2869.
3018
Times Cell
This counter counts the number of failures in inter-BSC outgoing handover requests initiated by the talker from the source cell. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently attempted cell is not under the BSC, then the original BSC will send the A_HO_RQD message to MSC to trigger inter-BSC cell handover. If the original BSC receives the handover rejection message returned from MSC or does not receive any response from MSC before the protection timer expires, the counter increments. The measurement point is A1, as shown in Figure 2870.
3019
Times Cell
This counter counts the number of attempts of incoming handover towards the local cell when the talker, who is having the VGCS service, is performing inter-BSC handover. When the destination cell receives the HANDOVER REQUEST message from MSC, if the request is due to incoming handover, the counter increments. The measurement point is A1, as shown in Figure 2871.
3020
Times Cell
This counter counts the number of executions of incoming handover towards the local cell when the talker, who is having the VGCS service, is performing inter-BSC handover. When the destination cell receives the HANDOVER REQUEST message from MSC, if the channel is allocated and activated successfully, the counter increments. The measurement point is A2, as shown in Figure 2872.
Times Cell
This counter counts the number of successful incoming handovers towards the local cell when the talker, who is having the VGCS service, is performing inter-BSC handover. When the destination cell
3021
receives the handover completion message from Um interface, if the handover is inter-BSC incoming handover, the counter increments. The measurement point is A3, as shown in Figure 2873.
FIGURE 2873 INTER-BSC INTER-CELL INCOMING HANDOVER SUCCESS
Times Cell
C902030011 Number of VGCS channel request attempts for NOTIFICATION RESPONSE of Listener
Description
This counter counts the number of attempts of BSC's allocating VGCS channel during the listener's notification response flow. When BSC receives the EST IND (NOTIFICATION RESPONSE) message, the counter increments. The measurement point is A1, as shown in Figure 2874.
3022
Times Cell
C902030012 Number of VGCS channel request success for NOTIFICATION RESPONSE of Listener
Description
This counter counts the number of BSC's successfully allocating VGCS channel during the listener's notification response flow. When BSC successfully allocates VGCS channel and returns the VGCS/VBS ASSIGNMENT STATUS message to MSC, the counter increments. The measurement point is A2, as shown in Figure 2875.
3023
Times Cell
C902030013 Number of VGCS channel request failure for NOTIFICATION RESPONSE of Listener
Description
This counter counts the number of failures in BSC's allocating VGCS channel during the listener's notification response flow. When BSC fails in allocating VGCS channel, the counter increments. The measurement point is A1, as shown in Figure 2876.
3024
Times Cell
This counter counts the number of VGCS channel being released due to that BSC cannot detect the listener. When BSC cannot detect the listener on VGCS channel, it releases the VGCS channel and returns the VGCS ASSIGNMENT STATUS message to MSC, and the counter increments. The measurement point is A1, as shown in Figure 2877.
3025
IN
CELL
Times Cell
This counter counts the number of BSC's releasing uplink due to radio link fault at the talker end. When BSC detects on VGCS channel that the radio link is broken at the talker end or the new talker fails in occupying the channel, it sends the UPLINK RELEASE INDICATION message to MSC, and the counter increments. The measurement point is A1, as shown in Figure 2878.
DUE TO
Times
3026
Statistics Object
Cell
This counter counts the number of the talker's, who is on the group call channel, giving up the conversation due to one or other reasons. When BSC receives the UPLINK RELEASE message from the talker, it sends the UPLINK RELEASE INDICATION message to MSC, and the counter increments. The measurement point is A1, as shown in Figure 2879.
Times Cell
This counter counts the number of the listener's attempts of becoming a talker through uplink request. When BSC sends the UPLINK REQUEST message to MSC, the counter increments. The measurement point is A1, as shown in Figure 2880.
3027
Times Cell
This counter counts the number of intra-BSC inter-cell outgoing handover attempts initiated from the source cell by the talker who is having the VGCS service. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates that intra-cell handover is required and the currently attempted cell is under the BSC, the counter increments. The measurement point is A1, as shown in Figure 2881.
3028
Times Cell
This counter counts the number of executions of intra-BSC inter-cell outgoing handover initiated from the source cell by the talker who is having the VGCS service. Here, execution means the destination cell succeeds in requesting radio resource and the message of resource available is returned. During the handover, when the destination cell succeeds in requesting channel, it returns the message of radio resource available to the source cell. After the source cell receives the message, if the channel request is due to intra-BSC inter-cell handover, the counter increments. The measurement point is A2, as shown in Figure 2882.
3029
Times Cell
This counter counts the number of successful intra-BSC inter-cell outgoing handovers initiated from the source cell by the talker who is having the VGCS service. During the handover, if the source cell receives the handover completion message returned from the destination cell, then it indicates that MS is accessed to the destination channel and the handover succeeds. In such cases, the counter increments. The measurement point is A3, as shown in Figure 2883.
3030
Times Cell
This counter counts the number of failures of intra-BSC inter-cell outgoing handovers initiated from the source cell by the talker who is having the VGCS service. During the handover, whenever the handover fails due to any exception, the counter increments. The measurement point is A1, as shown in Figure 2884.
3031
Times Cell
This counter counts the number of attempts of incoming handover towards the destination cell when the talker, who is having the VGCS service, is performing intra-BSC inter-cell handover. When the destination cell under the BSC receives the channel request from the source cell, if the request is due to inter-cell handover, the counter increments. The measurement point is A1, as shown in Figure 2885.
Times
3032
Statistics Object
Cell
This counter counts the number of executions of incoming handover towards the destination cell when the talker, who is having the VGCS service, is performing intra-BSC inter-cell handover. If the channel is successfully activated in the destination cell under the BSC and the request is due to inter-cell handover, the counter increments. The measurement point is A2, as shown in Figure 2886.
Times
3033
Statistics Object
Cell
This counter counts the number of successful incoming handovers towards the destination cell when the talker, who is having the VGCS service, is performing intra-BSC inter-cell handover. When the destination cell under the BSC receives the handover completion message, if the handover is intra-BSC inter-cell handover, the counter increments. The measurement point is A3, as shown in Figure 2887.
Times Cell
This counter counts the number of overflows of VGCS notification message on NCH channel. When BSC receives the ERROR REPORT
3034
message from BTS, if the cause is "NOTIFICATION OVERFLOW", the counter increments. This counter is supported in version V8.00.00 or later.
Unit Statistics Object
Times Cell
This counter counts the number of the listener's successfully becoming a talker through uplink request. When MSC sends the UPLINK REQUEST ACK message to BSC, if BSC returns the UPLINK REQUEST CONFIRM message, the counter increments. The measurement point is A1, as shown in Figure 2888.
Times
3035
Statistics Object
Cell
This counter counts the number of failures in the listener's becoming a talker through uplink request. After BSC sends the UPLINK REQUEST message to MSC, if it receives UPLINK REQUEST REJECT message from MSC or the timer expires, the counter increments. The measurement point is A1, as shown in Figure 2889.
Times Cell
3036
Chapter
103
VBS Measurement
Table of Contents Overview...................................................................... 3038 C902040001 Number of VBS assignment attempts............. 3038 C902040002 Number of VBS assignment success .............. 3039 C902040003 Number of VBS assignment failure ................ 3039 C902040004 Number of VBS Inter-BSC outgoing handover attempts of Talker ......................................................... 3040 C902040005 Number of VBS Inter-BSC outgoing handover execution of Talker ........................................................ 3041 C902040006 Number of VBS Inter-BSC outgoing handover success of Talker ........................................................... 3042 C902040007 Number of VBS Inter-BSC outgoing handover failure of Talker ............................................................. 3043 C902040008 Number of VBS Inter-BSC incoming handover attempts of Talker ......................................................... 3044 C902040009 Number of VBS Inter-BSC incoming handover execution of Talker ........................................................ 3045 C902040010 Number of VBS Inter-BSC incoming handover success of Talker ........................................................... 3046 C902040011 Number of VBS channel request attempts for NOTIFICATION RESPONSE of Listener............................... 3046 C902040012 Number of VBS channel request success for NOTIFICATION RESPONSE of Listener................................... 3047 C902040013 Number of VBS channel request failure for NOTIFICATION RESPONSE of Listener................................... 3048 C902040014 Number of VBS channel release for Listener detection ......................................................................... 3049 C902040015 Number of VBS Intra-BSC Inter-cell outgoing handover attempts of Talker............................................ 3050 C902040016 Number of VBS Intra-BSC Inter-cell outgoing handover execution of Talker........................................... 3051 C902040017 Number of VBS Intra-BSC Inter-cell outgoing handover success of Talker ............................................. 3052 C902040018 Number of VBS Intra-BSC Inter-cell outgoing handover failure of Talker ............................................... 3053 C902040019 Number of VBS Intra-BSC Inter-cell incoming handover attempts of Talker............................................ 3054 C902040020 Number of VBS Intra-BSC Inter-cell incoming handover execution of Talker........................................... 3055 C902040021 Number of VBS Intra-BSC Inter-cell incoming handover success of Talker ............................................. 3056 C902040022 Number of NCH overflow of VBS ................... 3056 C902040023 Number of Talker drops due to radio link failure .............................................................................. 3057
3037
Overview
This measurement performs statistics for performance indices of voice broadcast service, which involves VBS assignment, Talker handover, Listener notification response, and NCH overflow. Statistics object: cell
This counter counts the number of assignment attempts due to VBS. When BSC receives the VBS ASSIGNMENT REQUEST message (indicating VBS call) of corresponding legal cell from MSC, the counter increments. The measurement point is A1, as shown in Figure 2890.
Times
3038
Statistics Object
Cell
This counter counts the number of successful assignments due to VBS. When BSC sends the VBS ASSIGNMENT RESULT message (corresponding to VBS call) to MSC as response to the VBS ASSIGNMENT REQUEST message, the counter increments. The measurement point is A2, as shown in Figure 2891.
Times Cell
This counter counts the number of assignment failures due to VBS. When BSC receives the VGCS/VBS ASSIGNMENT REQUEST message from MSC, if channel allocation for group call service fails due to one or other reasons, BSC sends the VGCS/VBS ASSIGNMENT FAILURE message to MSC (corresponding to VBS call), and the counter increments. The measurement point is A1, as shown in Figure 2892.
3039
Times Cell
This counter counts the number of inter-BSC outgoing handover attempts initiated from the source cell by the talker who is having the VBS service. When BSC receives the measurement report from the talker's mobile phone, if the handover decision indicates intercell handover is required but the currently attempted cell is not under the BSC, then the original BSC will send the A_HO_RQD message to MSC to trigger inter-BSC cell handover. In such cases, the counter increments. The measurement point is A1, as shown in Figure 2893.
3040
Times Cell
This counter counts the number of inter-BSC outgoing handover executions initiated from the source cell by the talker who is having the VBS service. When BSC receives the measurement report from the talker's mobile phone, if the handover decision indicates inter-cell handover is required but the currently attempted cell is not under the BSC, then the original BSC will send the A_HO_RQD message to MSC to trigger inter-BSC cell handover. If the original BSC receives the handover command returned by MSC, the counter increments. The measurement point is A2, as shown in Figure 2894.
3041
Times Cell
This counter counts the number of successful inter-BSC outgoing handovers initiated from the source cell by the talker who is having the VBS service. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently attempted cell is not under the BSC, then the original BSC will send the A_HO_RQD message to MSC to trigger inter-BSC cell handover. If the mobile phone is successfully accessed to the destination cell, the source cell receives the release command issued from MSC. In such cases, the counter increments. The measurement point is A3, as shown in Figure 2895.
3042
Times Cell
This counter counts the number of failures of inter-BSC outgoing handover request initiated from the source cell by the talker who is having the VBS service. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently attempted cell is not under the BSC, then the original BSC will send the A_HO_RQD message to MSC to trigger inter-BSC cell handover. If the original BSC receives the handover rejection message returned from MSC or does not receive any response from MSC before the protection timer expires, the counter increments. The measurement point is A1, as shown in Figure 2896.
3043
OF
TALKER
Times Cell
This counter counts the number of attempts of incoming handover towards the destination cell when the talker, who is having the VBS service, is performing inter-BSC handover. When the destination cell receives the HANDOVER REQUEST message from MSC, if the request is due to incoming handover, the counter increments. The measurement point is A1, as shown in Figure 2897.
3044
Times Cell
This counter counts the number of executions of incoming handover towards the local cell when the talker, who is having the VBS service, is performing inter-BSC handover. When the destination cell receives the HANDOVER REQUEST message from MSC, if the channel is allocated and activated successfully, the counter increments. The measurement point is A2, as shown in Figure 2898.
Times
3045
Statistics Object
Cell
This counter counts the number of successful incoming handovers towards the local cell when the talker, who is having the VBS service, is performing inter-BSC handover. When the destination cell receives the handover completion message from Um interface, if the handover is inter-BSC incoming handover, the counter increments. The measurement point is A3, as shown in Figure 2899.
Times Cell
C902040011 Number of VBS channel request attempts for NOTIFICATION RESPONSE of Listener
Description
This counter counts the number of attempts of BSC's allocating VBS channel during the listener's notification response flow. When BSC receives the EST IND (NOTIFICATION RESPONSE) message,
3046
the counter increments. The measurement point is A1, as shown in Figure 2900.
FIGURE 2900 LISTENER'S NOTIFICATION RESPONSE PROCESS (SUCCESS)
Times Cell
C902040012 Number of VBS channel request success for NOTIFICATION RESPONSE of Listener
Description
This counter counts the number of BSC's successfully allocating VBS channel during the listener's notification response flow. When BSC successfully allocates VGCS channel and returns the VGCS/VBS ASSIGNMENT STATUS message to MSC, the counter increments. The measurement point is A2, as shown in Figure 2901.
3047
Times Cell
C902040013 Number of VBS channel request failure for NOTIFICATION RESPONSE of Listener
Description
This counter counts the number of failures in BSC's allocating VBS channel during the listener's notification response flow. When BSC fails in allocating VGCS channel, the counter increments. The measurement point is A1, as shown in Figure 2902.
3048
Times Cell
This counter counts the number of VBS channel being released due to that BSC cannot detect the listener. When BSC cannot detect the listener on VBS channel, it releases the VBS channel and returns the VGCS ASSIGNMENT STATUS message to MSC, and the counter increments. The measurement point is A1, as shown in Figure 2903.
3049
IN
CELL
Times Cell
This counter counts the number of intra-BSC inter-cell outgoing handover attempts initiated from the source cell by the talker who is having the VBS service. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates that intra-cell handover is required and the currently attempted cell is under the BSC, the counter increments. The measurement point is A1, as shown in Figure 2904.
3050
Times Cell
This counter counts the number of executions of intra-BSC inter-cell outgoing handover initiated from the source cell by the talker who is having the VBS service. Here, execution means the destination cell succeeds in requesting radio resource and the message of resource available is returned. During the handover, when the destination cell succeeds in requesting channel, it returns the message of radio resource available to the source cell. After the source cell receives the message, if the channel request is due to intra-BSC inter-cell handover, the counter increments. The measurement point is A2, as shown in Figure 2905.
3051
Times Cell
This counter counts the number of successful intra-BSC inter-cell outgoing handovers initiated from the source cell by the talker who is having the VBS service. During the handover, if the source cell receives the handover completion message returned from the destination cell, then it indicates that MS is accessed to the destination channel and the handover succeeds. In such cases, the counter increments. The measurement point is A3, as shown in Figure 2906.
3052
Times Cell
This counter counts the number of failures of intra-BSC inter-cell outgoing handovers initiated from the source cell by the talker who is having the VBS service. During the handover, whenever the handover fails due to any exception, the counter increments. The measurement point is A1, as shown in Figure 2907.
3053
Times Cell
This counter counts the number of attempts of incoming handover towards the destination cell when the talker, who is having the VBS service, is performing intra-BSC inter-cell handover. When the destination cell under the BSC receives the channel request from the source cell, if the request is due to inter-cell handover, the counter increments. The measurement point is A1, as shown in Figure 2908.
Times
3054
Statistics Object
Cell
This counter counts the number of executions of incoming handover towards the destination cell when the talker, who is having the VBS service, is performing intra-BSC inter-cell handover. If the channel is successfully activated in the destination cell under the BSC and the request is due to inter-cell handover, the counter increments. The measurement point is A2, as shown in Figure 2909.
Times
3055
Statistics Object
Cell
This counter counts the number of successful incoming handovers towards the destination cell when the talker, who is having the VBS service, is performing intra-BSC inter-cell handover. When the destination cell under the BSC receives the handover completion message, if the handover is intra-BSC inter-cell handover, the counter increments. The measurment point is A3, as shown in Figure 2910.
Times Cell
This counter counts the number of overflows of VBS notification message on NCH channel. When BSC receives the ERROR REPORT
3056
message from BTS, if the cause is "NOTIFICATION OVERFLOW", the counter increments. This counter is supported in version V8.00.00 or later.
Unit Statistics Object
Times Cell
This counter counts the number of BSC's releasing the resource occupied by the talker due to radio link fault at the talker end. When BSC detects on VBS channel that the radio link is disconnected at the talker end, it releases the talker's resource, and the counter increments. The measurement point is A1, as shown in Figure 2911.
DUE TO
Times Cell
3057
3058
Chapter
104
eMLPP Measurement
Table of Contents Overview...................................................................... 3060 C902050001 Number of Talker is preempted ..................... 3060 C902050002 Number of Listener is preempted .................. 3060 C902050003 Number of preempt attempts due to VGCS setup ........................................................................... 3061 C902050004 Number of preempt attempts due to VBS setup ........................................................................... 3062 C902050005 Number of preempt execution due to VGCS setup ........................................................................... 3063 C902050006 Number of preempt execution due to VBS setup ........................................................................... 3064 C902050007 Number of preempt attempts due to NOTIFICATION RESPONSE of Listener ............................................ 3065 C902050008 Number of preempt execution due to NOTIFICATION RESPONSE of Listener ............................................ 3066 C902050009 Number of preempt attempts due to Inter-BSC handover of Talker ......................................................... 3067 C902050010 Number of preempt execution due to Inter-BSC handover of Talker ......................................................... 3068 C902050011 Number of preempt attempts due to Intra-BSC Inter-cell handover of Talker ........................................... 3069 C902050012 Number of preempt execution due to Intra-BSC Inter-cell handover of Talker ........................................... 3070 C902050013 Number of queuing attempts due to VGCS setup ........................................................................... 3071 C902050014 Number of queuing execution due to VGCS setup ........................................................................... 3072 C902050015 Number of queuing attempts due to VBS setup ........................................................................... 3073 C902050016 Number of queuing execution due to VBS setup ........................................................................... 3074 C902050017 Number of queuing attempts due to NOTIFICATION RESPONSE of Listener ............................................ 3075 C902050018 Number of queuing execution due to NOTIFICATION RESPONSE of Listener ............................................ 3076 C902050019 Number of queuing attempts due to inter-BSC incoming handover of Talker ........................................... 3077 C902050020 Number of queuing execution due to inter-BSC incoming handover of Talker ........................................... 3078 C902050021 Number of queuing attempts due to Intra-BSC Inter-cell handover of Talker ........................................... 3079 C902050022 Number of queuing execution due to Intra-BSC Inter-cell handover of Talker ........................................... 3080
3059
Overview
This measurement performs statistics for conditions of high-priority group call service preempting resource from low-priority service. It involves the following performance data: the number of forced release of listener/talker; the number of forced release due to group call setup, listener's notification response, or talker handover; the number of queuing due to group call setup, listener's notification response, or talker handover. Statistics object: cell
This counter counts the number of TCH, which is occupied by the talker, being forcedly released. The channel occupied by the talker will be forcedly released by other high-priority call (no available radio resource in the cell). When the channel instance where the talker is located receives the forced release message from other high-priority call, the counter increments. This counter is supported in version V8.00.00 or later. Times Cell
This counter counts the number of TCH, which is monitored by the listener, being forcedly released. The group call/broadcast channel monitored by the listener will be forcedly released by other high-priority call (no available radio resource in the cell). When the group call channel instance where the listener is located receives the forced release message from other high-priority call, the counter increments. This counter is supported in version V8.00.00 or later. Times
Unit
3060
Statistics Object
Cell
This counter counts the number of attempts of forced release due to no available radio resource when BSC establishes the VGCS channel for a cell. When BSC receives the assignment request for establishing VGCS channel for a cell, if there is no available radio resource for the cell, it judges whether the forced release can be attempted. If the forced release can be attempted, the counter increments before the forced release message is sent to the forced release instance. The measurement point is A1, as shown in Figure 2912.
FIGURE 2912 VGCS/VBS ESTABLISHMENT PROCESS
Times
3061
Statistics Object
Cell
This counter counts the number of attempts of forced release due to no available radio resource when BSC establishes the VBS channel for a cell. When BSC receives the assignment request for establishing VBS channel for a cell, if there is no available radio resource for the cell, it judges whether the forced release can be attempted. If the forced release can be attempted, the counter increments before the forced release message is sent to the forced release instance. The measurement point is A1, as shown in Figure 2913.
FIGURE 2913 VGCS/VBS ESTABLISHMENT PROCESS
Times
3062
Statistics Object
Cell
This counter counts the number of executions of forced release due to no available radio resource when BSC establishes the VGCS channel for a cell. When BSC establishes the VGCS channel for a cell, if there is no available radio channel for the cell, the forced release is attempted. When the message that resource is available returned from the forced release instance is received, the counter increments. The measurement point is A2, as shown in Figure 2914.
FIGURE 2914 VGCS/VBS ESTABLISHMENT PROCESS
Times
3063
Statistics Object
Cell
This counter counts the number of executions of forced release due to no available radio resource when BSC establishes the VBS channel for a cell. When BSC establishes the VBS channel for a cell, if there is no available radio channel for the cell, the forced release is attempted. When the message that resource is available returned from the forced release instance is received, the counter increments. The measurement point is A2, as shown in Figure 2915.
FIGURE 2915 VGCS/VBS ESTABLISHMENT PROCESS
Times
3064
Statistics Object
Cell
This counter counts the number of attempts of forced release due to no available radio resource during the listener's notification response process. When BSC receives the listener's notification response to establish the VGCS/VBS channel for a cell, if there is no available radio resource, it judges whether the forced release can be attempted. If the forced release can be attempted, the counter increments before the forced release message is sent to the forced release instance. The measurement point is A1, as shown in Figure 2916.
Times
3065
Statistics Object
Cell
This counter counts the number of executions of forced release due to no available radio resource during the listener's notification response process. When BSC receives the listener's notification response to establish the VGCS/VBS channel for a cell, it will attempt forced release if there is no available radio resource. When the message that resource is available returned from the forced release instance is received, the counter increments. The measurement point is A2, as shown in Figure 2917.
Times
3066
Statistics Object
Cell
This counter counts the number of attempts of forced release due to the destination cell having no available radio resource when the talker performs incoming handover towards a cell controlled by another BSC. When the destination instance fails in channel allcoation, the forced release can be attempted according to MS's priority and the configuration at MSC and BSC. When the destination cell under another BSC receives the radio channel request message, if the request is due to inter-BSC incoming handover of the talker and if the destination cell does not have available radio channel, it is judged whether the forced release can be attempted. If the forced release can be attempted, the counter increments before the destination cell sends the forced release message to the forced release instance. The measurement point is A1, as shown in Figure 2918.
OF
TALKER
3067
Times Cell
This counter counts the number of executions of forced release due to the destination cell having no available radio resource when the talker performs incoming handover towards a cell controlled by another BSC. When the destination cell under another BSC receives the radio channel request message, if the request is due to inter-BSC incoming handover of the talker and if the destination cell does not have available radio channel, the forced release is attempted. When the destination cell receives the message that resource is available returned from the forced release instance, the counter increments. The measurement point is A2, as shown in Figure 2919.
OF
TALKER
3068
Times Cell
This counter counts the number of attempts of forced release due to the destination cell having no available radio resource when the talker performs intra-BSC inter-cell handover. When the destination instance fails in channel allocation, the forced release can be attempted according to MS's priority and the configuration at MSC and BSC. When the destination cell under the BSC receives the radio channel request message, if the request is due to BSC-controlled inter-cell handover of the talker and if the destination cell does not have available radio channel, it is judged whether the forced release can be attempted. If the forced release can be attempted, the counter increments before the destination cell sends the forced release message to the forced release instance. The measurement point is A1, as shown in Figure 2920.
OF
TALKER
3069
Times Cell
This counter counts the number of executions of forced release due to the destination cell having no available radio resource when the talker performs intra-BSC inter-cell handover. When the destination cell under the BSC receives the radio channel request message, if the request is due to BSC-controlled inter-cell handover of the talker and if the destination cell does not have available radio channel, the forced release is attempted. When the destination cell receives the message that resource is available returned from the forced release instance, the counter increments. The measurement point is A2, as shown in Figure 2921.
OF
TALKER
Times
3070
Statistics Object
Cell
This counter counts the number of attempts of queuing due to a cell having no available radio resource when BSC establishes the VGCS channel for the cell. When BSC receives the VGCS assignment request to establish the VGCS channel for a cell, if there is no available resource, it judges whether queuing can be performed. If queuing can be performed, the cell instance is added to the queue waiting for resource, and the counter increments. The measurement point is A1, as shown in Figure 2922.
FIGURE 2922 VGCS CELL ESTABLISHMENT PROCESS
Times
3071
Statistics Object
Cell
This counter counts the number of executions of queuing due to a cell having no available radio resource when BSC establishes the VGCS channel for the cell. When BSC receives the VGCS assignment request to establish the VGCS channel for a cell, if there is no available resource, the cell instance is added to the queue waiting for resource. When the cell instance receives the message that resource is available, the counter increments. The measurement point is A2, as shown in Figure 2923.
FIGURE 2923 VGCS CELL ESTABLISHMENT PROCESS
Times
3072
Statistics Object
Cell
This counter counts the number of attempts of queuing due to a cell having no available radio resource when BSC establishes the VBS channel for the cell. When BSC receives the VBS assignment request to establish the VBS channel for a cell, if there is no available resource, it judges whether queuing can be performed. If queuing can be performed, the cell instance is added to the queue waiting for resource, and the counter increments. The measurement point is A1, as shown in Figure 2924.
FIGURE 2924 VBS CELL ESTABLISHMENT PROCESS
Times
3073
Statistics Object
Cell
This counter counts the number of executions of queuing due to a cell having no available radio resource when BSC establishes the VBS channel for the cell. When BSC receives the VBS assignment request to establish the VBS channel for a cell, if there is no available resource, the cell instance is added to the queue waiting for resource. When the cell instance receives the message that resource is available, the counter increments. The measurement point is A2, as shown in Figure 2925.
FIGURE 2925 VBS CELL ESTABLISHMENT PROCESS
Times
3074
Statistics Object
Cell
This counter counts the number of attempts of queuing due to no available radio resource when BSC establishes the VGCS/VBS channel for the listener during the listener's notification response flow. When BSC receives the listener's notification response message, if there is no available channel and if the listener is allowed to wait for radio channel resource in the queue, the counter increments. The measurement point is A1, as shown in Figure 2926.
FIGURE 2926 LISTENER'S NOTIFICATION RESPONSE PROCESS
Times
3075
Statistics Object
Cell
This counter counts the number of executions of queuing due to no available radio resource when BSC establishes the VGCS/VBS channel for the listener during the listener's notification response flow. When BSC receives the listener's notification response message, if there is no available channel and if the listener is allowed to wait for radio channel resource in the queue, then the counter increments if the listener gets the radio channel resource. The measurement point is A2, as shown in Figure 2927.
FIGURE 2927 LISTENER'S NOTIFICATION RESPONSE PROCESS
Times
3076
Statistics Object
Cell
This counter counts the number of attempts of queuing due to the destination cell having no available radio resource when the talker performs incoming handover towards a cell controlled by another BSC. When BSC receives the handover request from MSC, which is inter-BSC incoming handover of the talker, if there is no available channel and if VGCS/VBS is allowed to wait for radio channel resource in the queue, the counter increments. The measurement point is A1, as shown in Figure 2928.
FIGURE 2928 INTER-BSC INCOMING HANDOVER
OF
TALKER
Times
3077
Statistics Object
Cell
This counter counts the number of executions of queuing due to the destination cell having no available radio resource when the talker performs incoming handover towards a cell controlled by another BSC. When BSC receives the handover request from MSC, which is inter-BSC incoming handover of the talker, if there is no available channel and if VGCS/VBS is allowed to wait for radio channel resource in the queue, then the counter increments when the radio channel resource is obtained through waiting. The measurement point is A2, as shown in Figure 2929.
FIGURE 2929 INTER-BSC INCOMING HANDOVER
OF
TALKER
Times
3078
Statistics Object
Cell
This counter counts the number of attempts of queuing due to the destination cell having no available radio resource when the talker performs incoming handover towards a cell controlled by the same BSC. If the following three conditions are satisfied, the counter increments: The request is due to BSC-controlled inter-cell incoming handover of the talker; The destination cell does not have available radio channel; VGCS/VBS is allowed to wait for radio channel resource in the queue.
TALKER
Times
3079
Statistics Object
Cell
This counter counts the number of executions of queuing due to the destination cell having no available radio resource when the talker performs incoming handover towards a cell controlled by the same BSC. If the following three conditions are satisfied and the radio channel resource is obtained through waiting, the counter increments: The request is due to BSC-controlled inter-cell incoming handover of the talker; The destination cell does not have available radio channel; VGCS/VBS is allowed to wait for radio channel resource in the queue.
TALKER
Times Cell
3080
Chapter
105
Overview
Flow control measurement counters are used to measure BHCA or paging message overload at the processor. Statistic unit in this measurement is CMP.
After BSC receives the channel request message from BTS, it performs statistics of the number of channel requests within the unit time. If the number exceeds the set threshold value, flow control must be performed to discard subsequent channel request messages received in the meaurement period. After a unit time expires, check whether the number of channel requests received in the measurement period exceeds the threshold value. If the number is larger than the threshold value, the counter increments. The measurement point is shown in Figure 2932.
3081
OF
NUMBER
OF
CHANNEL REQUESTS
Times CMP
After BSC receives the paging message issued by MSC, it performs statistics of the number of paging messages that do not contain eMLPP priority information received within the unit time. If the number exceeds the set threshold value, flow control must be performed to discard subsequent paging messages not containing eMLPP priority information received in the measurement period. After a unit time expires, check whether the number of common paging messages received in the measurement period exceeds the threshold value. If the number is larger than the threshold value, the counter increments. The measurement point is shown in Figure 2933.
FIGURE 2933 MEASUREMENT POINT
OF
NUMBER
OF
PAGING MESSAGES
Times CMP
3082
Chapter
106
3083
C902120021 BSC-controlled incoming handover success time due to queue (On SDCCH) .............................................. 3106 C902120022 Number of BSC-controlled incoming handover success due to queue (On SDCCH)................................... 3107 C902120023 Number of MSC-controlled incoming handover attempts (On SDCCH) .................................................... 3108 C902120024 Number of incoming handover failure due to unavailable radio resource (On SDCCH) ............................... 3108 C902120025 Number of incoming handover failure due to other factors (On SDCCH)............................................... 3109 C902120026 Number of MSC-controlled incoming handover (On SDCCH) ................................................................. 3110 C902120027 Number of MSC-controlled incoming handover attempts due to forced release (On SDCCH)...................... 3111 C902120028 Number of MSC-controlled incoming handover due to forced release (On SDCCH) ................................... 3112 C902120029 Number of MSC-controlled incoming handover attempts due to queue (On SDCCH)................................. 3113 C902120030 Number of MSC-controlled incoming handover due to queue (On SDCCH) .............................................. 3114 C902120031 Number of MSC-controlled incoming handover attempts due to forced handover (On SDCCH)................... 3115 C902120032 Number of MSC-controlled incoming handover due to forced handover (On SDCCH) ................................ 3116 C902120033 Number of MSC-controlled incoming handover success (On SDCCH)...................................................... 3117 C902120034 MSC-controlled incoming handover time due to queue (On SDCCH) ........................................................ 3117 C902120035 Number of MSC-controlled incoming handover queue (On SDCCH) ........................................................ 3119 C902120036 MSC-controlled incoming handover success time due to queue (On SDCCH) .............................................. 3121 C902120037 Number of MSC-controlled incoming handover success due to queue (On SDCCH)................................... 3122
Overview
SDCCH general handover measurement counters are used to count the number of handover successes and handover failures on SDCCH and study the frequency of various abnormalities occurred during the handover process. Statistic unit in this measurement is cell.
3084
This counter counts the number of attempts of intra-BSC inter-cell outgoing handover initiated by MS on SDCCH in the source cell. This counter is used to find out the frequency of intra-BSC intercell outgoing handover attempt initiated by MS. It is one of the parameters that evaluate the radio environment. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates that inter-cell handover is required and the currently attempted cell is under the BSC, the counter increments. The measurement point is A, as shown in Figure 2934.
FIGURE 2934 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER ATTEMPT (ON SDCCH)
Times
3085
Statistics Object
Cell
This counter counts the number of executions of intra-BSC intercell outgoing handover initiated by MS on SDCCH in the source cell. Here, execution means the destination cell succeeds in requesting radio resource and the message of resource available is returned. This counter is used to find out the frequency of execution of intra-BSC inter-cell outgoing handover initiated by MS. It is one of the parameters that evaluate the radio environment, reflecting the handover flow. During the handover, when the destination cell succeeds in requesting channel, it returns the message of radio resource available to the source cell. After the source cell receives the message, if the channel request is due to intra-BSC inter-cell handover, the counter increments. The measurement point is A, as shown in Figure 2935.
FIGURE 2935 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER EXECUTION
Times
3086
Statistics Object
Cell
This counter counts the number of successful intra-BSC inter-cell outgoing handover initiated by MS on SDCCH in the source cell. This counter is used to find out the frequency of successful intraBSC inter-cell outgoing handover initiated by MS. It is one of the parameters that evaluate the handover condition. During the handover, if the source cell receives the handover completion message returned from the destination cell, then it indicates that MS is accessed to the destination channel and the handover succeeds. In such cases, the counter increments. The measurement point is A, as shown in Figure 2936.
FIGURE 2936 BSC-CONTROLLED INTER-CELL OUTGOING HANDOVER SUCCESS
Times
3087
Statistics Object
Cell
This counter counts the number of attempts of MSC-controlled inter-BSC outgoing handover initiated by MS on SDCCH in the source cell. This counter is used to find out the frequency of MSC-controlled inter-BSC outgoing handover attempt initiated by MS. It is one of the parameters that evaluate the radio environment. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently attempted cell is under a different BSC, then the source BSC will send the A_HO_RQD message to MSC to trigger inter-BSC inter-cell handover. In this case, the counter increments. The measurement point is A, as shown in Figure 2937.
FIGURE 2937 MSC-CONTROLLED OUTGOING HANDOVER ATTEMPT
Times
3088
Statistics Object
Cell
C902120005 Number of MSC-controlled outgoing handover request failures due to unclear factors (On SDCCH)
Description
This counter counts the number of failures of MSC-controlled interBSC outgoing handover request initiated by MS on SDCCH in the source cell, and the failure is due to unclear causes. This counter is used to find out the frequency of failure of MSC-controlled outgoing handover request initiated by MS due to unclear causes. It also helps study the condition of handover initiated by MSC. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently attempted cell is under a different BSC, then the source BSC will send the A_HO_RQD message to MSC to trigger inter-BSC inter-cell handover. If BSC does not receive any response message from MSC before the protection timer expires, the counter increments. The measurement point is A, as shown in Figure 2938.
FIGURE 2938 MSC-CONTROLLED OUTGOING HANDOVER FAILURE UNCLEAR CAUSE
DUE TO
Times
3089
Statistics Object
Cell
C902120006 Number of MSC-controlled outgoing handover request failures due to unavailable radio resource (On SDCCH)
Description
This counter counts the number of failures of MSC-controlled interBSC outgoing handover request initiated by MS on SDCCH in the source cell, and the failure is due to no available radio resource. This counter is used to find out the frequency of failure of MSC-controlled outgoing handover request initiated by MS due to no available radio resource. It also helps study the condition of handover initiated by MSC. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently attempted cell is under a different BSC, then the source BSC will send the A_HO_RQD message to MSC to trigger inter-BSC inter-cell handover. If the source BSC receives the handover reject message from MSC and the cause is no available radio resource, the counter increments. The measurement point is A, as shown in Figure 2939.
FIGURE 2939 MSC-CONTROLLED HANDOVER REQUEST BEING REJECTED
Times
3090
Statistics Object
Cell
C902120007 Number of MSC-controlled outgoing handover request failures due to other factors (On SDCCH)
Description
This counter counts the number of failures of MSC-controlled interBSC outgoing handover request initiated by MS on SDCCH in the source cell, and the failure is due to causes except for no available terrestrial resource and no available radio resource. This counter is used to find out the frequency of failure of MSCcontrolled outgoing handover request initiated by MS due to other causes. It also helps study the condition of handover initiated by MSC. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently attempted cell is under a different BSC, then the source BSC will send the A_HO_RQD message to MSC to trigger inter-BSC inter-cell handover. If the source BSC receives the handover reject message from MSC due to other causes, the counter increments. The measurement point is A, as shown in Figure 2940.
FIGURE 2940 MSC-CONTROLLED HANDOVER REQUEST BEING REJECTED
Times
3091
Statistics Object
Cell
This counter counts the number of MSC-controlled inter-BSC outgoing handovers initiated by MS on SDCCH in the source cell. This counter is used to find out the frequency of MSC-controlled inter-BSC outgoing handover initiated by MS. It also helps study the condition of handover initiated by MSC. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently attempted cell is under a different BSC, then the source BSC will send the A_HO_RQD message to MSC to trigger inter-BSC inter-cell handover. If the source BSC receives the handover command returned by MSC, the counter increments. The measurement point is A, as shown in Figure 2941.
FIGURE 2941 NUMBER EXECUTIONS
OF
Times
3092
Statistics Object
Cell
This counter counts the number of successful MSC-controlled inter-BSC outgoing handover initiated by MS on SDCCH in the source cell. This counter is used to find out the frequency of successful MSCcontrolled inter-BSC outgoing handover initiated by MS. It also helps study the condition of handover initiated by MSC. When BSC receives the measurement report from the talker's mobile phone, it performs handover decision. If the handover decision indicates inter-cell handover is required but the currently attempted cell is under a different BSC, then the source BSC will send the A_HO_RQD message to MSC to trigger inter-BSC inter-cell handover. If the mobile phone is successfully accessed to the destination cell, the source cell receives the release command issued from MSC. In such cases, the counter increments. The measurement point is A, as shown in Figure 2942.
FIGURE 2942 NUMBER SUCCESSES
OF
Times
3093
Statistics Object
Cell
This counter counts the number of attempts of BSC-controlled inter-cell incoming handover 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 cell under the BSC receives the channel request from the source cell, if the request is due to inter-cell handover, the counter increments. The measurement point is A, as shown in Figure 2943.
FIGURE 2943 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER ATTEMPT
Times
3094
Statistics Object
Cell
This counter counts the number of BSC-controlled inter-cell incoming handover executions initiated by MS towards SDCCH of the destination cell. This counter is used to find out the frequency of BSC-controlled inter-cell incoming handover initiated by MS. It is one of the parameters that evaluate the radio environment, reflecting the handover flow. If the channel is successfully activated in the destination cell under the BSC and the request is due to inter-cell handover, the counter increments. The measurement point is A, as shown in Figure 2944.
FIGURE 2944 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER EXECUTION
Times
3095
Statistics Object
Cell
C902120012 Number of BSC-controlled incoming handover attempts due to forced release (On SDCCH)
Description
During the process of BSC-controlled inter-cell incoming handover towards SDCCH initiated by MS, this counter counts the number of attempts of forced release due to no available radio resource in the destination cell. When the destination instance fails in channel allocation, the forced release can be attempted according to MS's priority and the configuration at MSC and BSC. This counter is used to find out the frequency of forced release attempt during the process of BSC-controlled inter-cell incoming handover initiated by MS. It reflects the handover flow. When the destination cell under the BSC receives the radio channel request message, if the request is due to BSC-controlled inter-cell handover and if the destination cell does not have available radio channel, it is judged whether the forced release can be attempted. If the forced release can be attempted, the counter increments before the destination cell sends the forced release message to the forced release instance. The measurement point is A, as shown in Figure 2945.
FIGURE 2945 FORCED RELEASE ATTEMPT
Times
3096
Statistics Object
Cell
C902120013 Number of BSC-controlled incoming handover due to forced release (On SDCCH)
Description
During the process of BSC-controlled inter-cell incoming handover towards SDCCH initiated by MS, this counter counts the number of forced releases due to no available radio resource in the destination cell. This counter is used to find out the frequency of forced release during the process of BSC-controlled inter-cell incoming handover initiated by MS. It reflects the handover flow. When the destination cell under the BSC receives the radio channel request message, if the request is due to BSC-controlled inter-cell handover and if the destination cell does not have available radio channel, the forced release is attempted. When the destination cell receives the message that resource is available returned from the forced release instance, the counter increments. The measurement point is A2, as shown in Figure 2946.
FIGURE 2946 FORCED RELEASE EXECUTION
Times
3097
Statistics Object
Cell
C902120014 Number of BSC-controlled incoming handover attempts due to queue (On SDCCH)
Description
During the process of BSC-controlled inter-cell incoming handover towards SDCCH initiated by MS, this counter counts the number of attempts of queuing due to no available radio resource in the destination cell. This counter is used to find out the frequency of queuing attempt during the process of BSC-controlled inter-cell incoming handover initiated by MS. It reflects the handover flow. When the destination cell under the BSC receives the radio channel request message, if the request is due to BSC-controlled inter-cell incoming handover and if the destination cell does not have available radio channel, it is judged whether queuing can be attempted. If queuing can be performed, the destination cell instance is added to the queue waiting for resource, and the counter increments. The measurement point is A, as shown in Figure 2947.
FIGURE 2947 QUEUING ATTEMPT
Times
3098
Statistics Object
Cell
During the process of BSC-controlled inter-cell incoming handover towards SDCCH initiated by MS, this counter counts the number of queuings due to no available radio resource in the destination cell. This counter is used to find out the frequency of queuing during the process of BSC-controlled inter-cell incoming handover initiated by MS. It reflects the handover flow. When the destination cell under the BSC receives the radio channel request message, if the request is due to BSC-controlled intercell incoming handover and if the destination cell does not have available radio channel, the destination instance is added into the queue. When the destination cell receives the message of resource available, the counter increments. The measurement point is A2, as shown in Figure 2948.
FIGURE 2948 QUEUING EXECUTION
3099
Times Cell
C902120016 Number of BSC-controlled incoming handover attempts due to forced handover (On SDCCH)
Description
During the process of BSC-controlled inter-cell incoming handover towards SDCCH initiated by MS, this counter counts the number of attempts of forced handover due to no available radio resource in the destination cell. This counter is used to find out the frequency of forced handover attempt during the process of BSC-controlled inter-cell incoming handover initiated by MS. It reflects the handover flow. When the destination cell under the BSC receives the radio channel request message, if the request is due to BSC-controlled inter-cell incoming handover and if the destination cell does not have available radio channel, it is judged whether forced handover can be attempted. If the forced handover can be attempted, the counter increments before the destination cell sends the forced handover message to the forced handover instance. The measurement point is A, as shown in Figure 2949.
FIGURE 2949 FORCED HANDOVER ATTEMPT
Times
3100
Statistics Object
Cell
C902120017 Number of BSC-controlled incoming handover due to forced handover (On SDCCH)
Description
During the process of BSC-controlled inter-cell incoming handover towards SDCCH initiated by MS, this counter counts the number of forced handovers due to no available radio resource in the destination cell. This counter is used to find out the frequency of forced handover during the process of BSC-controlled inter-cell incoming handover initiated by MS. It reflects the handover flow. When the destination cell under the BSC receives the radio channel request message, if the request is due to BSC-controlled inter-cell incoming handover and if the destination cell does not have available radio channel, the forced handover message is sent to the forced handover instance and the destination cell is added into the queue. When the destination cell receives the message of resource available, the counter increments. The measurement point is A2, as shown in Figure 2950.
FIGURE 2950 FORCED HANDOVER EXECUTION
3101
Times Cell
This counter counts the number of successful BSC-controlled intercell incoming handovers towards SDCCH initiated by MS. This counter is used to find out the frequency of successful BSCcontrolled inter-cell incoming handover initiated by MS. It reflects the handover flow. When the destination cell under the BSC receives the handover completion message, if the handover is BSC-controlled inter-cell handover, the counter increments. The measurement point is A, as shown in Figure 2951.
FIGURE 2951 BSC-CONTROLLED INTER-CELL INCOMING HANDOVER SUCCESS
Times
3102
Statistics Object
Cell
This counter counts the total queuing time of waiting for resource for BSC-controlled incoming handover towards SDCCH in the cell. The queuing time means the duration from an instance entering the queue to the instance exiting the queue. This counter is used to find out the total queuing time of waiting for resource for BSC-controlled incoming handover in the cell. It helps study the cell's traffic and the condition of queuing for resource. When the database obtains resource through dynamic channel conversion or when the MS releases resource, the queuing instance receives the message of resource available. If the resource request is due to BSC-controlled incoming handover, the counter accumulates the queuing time. The measurement point is A, as shown in Figure 2952.
FIGURE 2952 QUEUING EXECUTION
If the instance's queuing timer expires and if the resource request is due to BSC-controlled incoming handover, the counter accumulates the queuing time. The measurement point is A, as shown in Figure 2953.
3103
During the instance's queuing process, when the instance is released due to some causes, if the resource request is due to BSC-controlled incoming handover, the counter accumulates the queuing time. The measurement point is A, as shown in Figure 2954.
FIGURE 2954 RELEASING INSTANCE
DURING
QUEUING
Second Cell
This counter counts the number of queuings due to BSC-controlled incoming handover towards SDCCH in the cell. This counter is used to find out the total number of queuings due to BSC-controlled incoming handover in the cell. It helps study the cell's traffic.
3104
When the database obtains resource through dynamic channel conversion or when the MS releases resource, the queuing instance receives the message of resource available. If the resource request is due to BSC-controlled incoming handover, the counter increments. The measurement point is A, as shown in Figure 2955.
FIGURE 2955 QUEUING EXECUTION
If the instance's queuing timer expires and if the resource request is due to BSC-controlled incoming handover, the counter increments. The measurement point is A, as shown in Figure 2956.
FIGURE 2956 INCOMING HANDOVER QUEUING EXPIRES
During the instance's queuing process, when the instance is released due to some causes, if the resource request is due to BSC-controlled incoming handover, the counter increments. The measurement point is A, as shown in Figure 2957.
FIGURE 2957 RELEASING INSTANCE
DURING
QUEUING
3105
Times Cell
C902120021 BSC-controlled incoming handover success time due to queue (On SDCCH)
Description
This counter counts the total time of successfully obtaining SDCCH resource through queuing due to BSC-controlled incoming handover in the cell. This counter is used to find out the total time of successfully obtaining resource through queuing due to BSC-controlled incoming handover in the cell. It helps study the effective queuing time. When the database obtains resource through dynamic channel conversion or when the MS releases resource, the queuing instance receives the message of resource available. If the resource request is due to BSC-controlled incoming handover, the counter accumulates the queuing time. The measurement point is A, as shown in Figure 2958.
FIGURE 2958 QUEUING EXECUTION
Second
3106
Statistics Object
Cell
C902120022 Number of BSC-controlled incoming handover success due to queue (On SDCCH)
Description
This counter counts the total number of SDCCHs successfully obtained through queuing due to BSC-controlled incoming handover in the cell. This counter is used to find out the total number of calls that successfully obtain resource through queuing due to BSC-controlled incoming handover in the cell. It helps study the queuing success rate. When the database obtains resource through dynamic channel conversion or when the MS releases resource, the queuing instance receives the message of resource available. If the resource request is due to BSC-controlled incoming handover, the counter increments. The measurement point is A, as shown in Figure 2959.
FIGURE 2959 QUEUING EXECUTION
Times
3107
Statistics Object
Cell
This counter counts the number of attempts of inter-BSC incoming handover initiated by MSC towards SDCCH in the local cell. This counter is used to find out the frequency of inter-BSC incoming handover attempt initiated by MSC. It is one of the parameters that evaluate the radio environment. When the destination cell receives the channel request due to external incoming handover, the counter increments. The measurement point is A, as shown in Figure 2960.
FIGURE 2960 MSC-CONTROLLED INCOMING HANDOVER ATTEMPT
Times Cell
C902120024 Number of incoming handover failure due to unavailable radio resource (On SDCCH)
Description
During the process of inter-BSC incoming handover initiated by MSC towards SDCCH in the local cell, this counter counts the num-
3108
ber of incoming handover failures due to no available radio resource. This counter is used to find out the frequency of incoming handover failure due to no available radio resource during the process of inter-BSC incoming handover initiated by MSC. It helps study the external handover flow. After the destination cell receives the handover request message issued by MSC, it allocates radio channel and attempts to activate and connect the channel. If the process fails, the destination cell sends the handover failure message to MSC, and the counter increments. The measurement point is A, as shown in Figure 2961.
FIGURE 2961 MSC-CONTROLLED INCOMING HANDOVER FAILURE
Times Cell
C902120025 Number of incoming handover failure due to other factors (On SDCCH)
Description
During the process of inter-BSC incoming handover initiated by MSC towards SDCCH in the local cell, this counter counts the number of incoming handover failures due to causes except for blocked circuit, unmatched circuit groups, and no available radio resource. This counter is used to find out the frequency of incoming handover failure due to other causes during the process of inter-BSC incoming handover initiated by MSC. It helps study the external handover flow. After the destination cell receives the handover request message issued by MSC, if the incoming handover fails due to other causes, the destination cell sends the handover failure message to MSC,
3109
Times Cell
This counter counts the number of inter-BSC incoming handover initiated by MSC towards SDCCH in the local cell. This counter is used to find out the number of inter-BSC incoming handovers initiated by MSC. It is one of the parameters that evaluate the radio environment, helping study the incoming handover flow. When the destination cell receives the handover request message issued by MSC, if the channel is allocated and activated successfully, the counter increments. The measurement point is A, as shown in Figure 2963.
FIGURE 2963 MSC-CONTROLLED INCOMING HANDOVER EXECUTION
3110
Times Cell
C902120027 Number of MSC-controlled incoming handover attempts due to forced release (On SDCCH)
Description
During the process of MSC-controlled inter-BSC incoming handover towards SDCCH initiated by MS, this counter counts the number of attempts of forced release due to no available radio resource in the destination cell. When the destination instance fails in channel allocation, the forced release can be attempted according to MS's priority and the configuration at MSC and BSC. This counter is used to find out the frequency of forced release attempt during the process of MSC-controlled inter-BSC incoming handover initiated by MS. It reflects the handover flow. When the destination cell receives the radio channel request message, if the request is due to MSC-controlled inter-BSC handover and if the destination cell does not have available radio channel, it is judged whether the forced release can be attempted. If the forced release can be attempted, the counter increments before the destination cell sends the forced release message to the forced release instance. The measurement point is A, as shown in Figure 2964.
FIGURE 2964 FORCED RELEASE ATTEMPT
Times
3111
Statistics Object
Cell
C902120028 Number of MSC-controlled incoming handover due to forced release (On SDCCH)
Description
During the process of MSC-controlled inter-BSC incoming handover towards SDCCH initiated by MS, this counter counts the number of forced releases due to no available radio resource in the destination cell. This counter is used to find out the frequency of forced release during the process of MSC-controlled inter-BSC incoming handover initiated by MS. It reflects the handover flow. When the destination cell receives the radio channel request message, if the request is due to MSC-controlled inter-BSC incoming handover and if the destination cell does not have available radio channel, the forced release is attempted. When the destination cell receives the message that resource is available returned from the forced release instance, the counter increments. The measurement point is A, as shown in Figure 2965.
FIGURE 2965 FORCED RELEASE EXECUTION
Times
3112
Statistics Object
Cell
C902120029 Number of MSC-controlled incoming handover attempts due to queue (On SDCCH)
Description
During the process of MSC-controlled inter-BSC incoming handover towards SDCCH initiated by MS, this counter counts the number of attempts of queuing due to no available radio resource in the destination cell. This counter is used to find out the frequency of queuing attempt during the process of MSC-controlled inter-BSC incoming handover initiated by MS. It reflects the handover flow. When the destination cell receives the radio channel request message, if the request is due to MSC-controlled inter-BSC handover and if the destination cell does not have available radio channel, it is judged whether queuing can be attempted. If queuing can be performed, the detination cell instance is added to the queue waiting for resource, and the counter increments. The measurement point is A, as shown in Figure 2966.
FIGURE 2966 QUEUING ATTEMPT
Times
3113
Statistics Object
Cell
During the process of MSC-controlled inter-BSC incoming handover towards SDCCH initiated by MS, this counter counts the number of queuings due to no available radio resource in the destination cell. This counter is used to find out the frequency of queuing during the process of MSC-controlled inter-BSC incoming handover initiated by MS. It reflects the handover flow. When the destination cell receives the radio channel request message, if the request is due to MSC-controlled inter-BSC incoming handover and if the destination cell does not have available radio channel, the destination instance is added into the queue. When the destination cell receives the message of resource available, the counter increments. The measurement point is A, as shown in Figure 2967.
FIGURE 2967 QUEUING EXECUTION
Times
3114
Statistics Object
Cell
C902120031 Number of MSC-controlled incoming handover attempts due to forced handover (On SDCCH)
Description
During the process of MSC-controlled inter-BSC incoming handover towards SDCCH initiated by MS, this counter counts the number of attempts of forced handover due to no available radio resource in the destination cell. This counter is used to find out the frequency of forced handover attempt during the process of MSC-controlled inter-BSC incoming handover initiated by MS. It reflects the handover flow. When the destination cell receives the radio channel request message, if the request is due to MSC-controlled inter-BSC handover and if the destination cell does not have available radio channel, it is judged whether forced handover can be attempted. If the forced handover can be attempted, the counter increments before the destination cell sends the forced handover message to the forced handover instance. The measurement point is A, as shown in Figure 2968.
FIGURE 2968 FORCED HANDOVER ATTEMPT
Times
3115
Statistics Object
Cell
C902120032 Number of MSC-controlled incoming handover due to forced handover (On SDCCH)
Description
During the process of MSC-controlled inter-BSC incoming handover towards SDCCH initiated by MS, this counter counts the number of forced handovers due to no available radio resource in the destination cell. This counter is used to find out the frequency of forced handover during the process of MSC-controlled inter-BSC incoming handover initiated by MS. It reflects the handover flow. When the destination cell receives the radio channel request message, if the request is due to MSC-controlled inter-BSC incoming handover and if the destination cell does not have available radio channel, the forced handover message is sent to the forced handover instance and the destination cell is added into the queue. When the destination cell receives the message of resource available, the counter increments. The measurement point is A, as shown in Figure 2969.
FIGURE 2969 MSC-CONTROLLED FORCED HANDOVER EXECUTION
Times
3116
Statistics Object
Cell
This counter counts the number of successful MSC-controlled inter-BSC incoming handovers towards SDCCH initiated by MS. This counter is used to find out the frequency of successful MSCcontrolled inter-cell incoming handover initiated by MS. It reflects the handover flow. When the destination cell receives the handover completion message, if the handover is MSC-controlled inter-BSC incoming handover, the counter increments. The measurement point is A, as shown in Figure 2970.
FIGURE 2970 MSC-CONTROLLED INCOMING HANDOVER SUCCESS
Times Cell
C902120034 MSC-control led incoming handover time due to queue (On SDCCH)
Description
This counter counts the total queuing time of waiting for resource for MSC-controlled incoming handover towards SDCCH in the cell.
3117
This counter is used to find out the total queuing time of waiting for resource for MSC-controlled incoming handover in the cell. It helps study the cell's traffic and the condition of queuing for resource. When the database obtains resource through dynamic channel conversion or when the MS releases resource, the queuing instance receives the message of resource available. If the resource request is due to MSC-controlled incoming handover, the counter accumulates the queuing time. The measurement point is A, as shown in Figure 2971.
FIGURE 2971 QUEUING EXECUTION
If the instance's queuing timer expires and if the resource request is due to MSC-controlled incoming handover, the counter accumulates the queuing time. The measurement point is A, as shown in Figure 2972.
FIGURE 2972 INCOMING HANDOVER QUEUING EXPIRES
During the instance's queuing process, when the instance is released due to some causes, if the resource request is due to MSC-controlled incoming handover, the counter accumulates the queuing time. The measurement point is A, as shown in Figure 2973.
3118
DURING
QUEUING
Second Cell
This counter counts the number of queuings due to MSC-controlled incoming handover towards SDCCH in the cell. This counter is used to find out the total number of queuings due to MSC-controlled incoming handover in the cell. It helps study the cell's traffic. When the database obtains resource through dynamic channel conversion or when the MS releases resource, the queuing instance receives the message of resource available. If the resource request is due to MSC-controlled incoming handover, the counter increments. The measurement point is A, as shown in Figure 2974.
3119
If the instance's queuing timer expires and if the resource request is due to MSC-controlled incoming handover, the counter increments. The measurement point is A, as shown in Figure 2975.
FIGURE 2975 INCOMING HANDOVER QUEUING EXPIRES
During the instance's queuing process, when the instance is released due to some causes, if the resource request is due to MSC-controlled incoming handover, the counter increments. The measurement point is A, as shown in Figure 2976.
FIGURE 2976 RELEASING INSTANCE
DURING
QUEUING
Times
3120
Statistics Object
Cell
C902120036 MSC-contr olled incoming handover success time due to queue (On SDCCH)
Description
This counter counts the total time of successfully obtaining SDCCH resource through queuing due to MSC-controlled incoming handover in the cell. This counter is used to find out the total time of successfully obtaining resource through queuing due to MSC-controlled incoming handover in the cell. It helps study the effective queuing time. When the database obtains resource through dynamic channel conversion or when the MS releases resource, the queuing instance receives the message of resource available. If the resource request is due to MSC-controlled incoming handover, the counter accumulates the queuing time. The measurement point is A, as shown in Figure 2977.
FIGURE 2977 QUEUING EXECUTION
Second
3121
Statistics Object
Cell
C902120037 Number of MSC-controlled incoming handover success due to queue (On SDCCH)
Description
This counter counts the total number of SDCCHs successfully obtained through queuing due to MSC-controlled incoming handover in the cell. This counter is used to find out the total number of calls that successfully obtain resource through queuing due to MSC-controlled incoming handover in the cell. It helps study the queuing success rate. When the database obtains resource through dynamic channel conversion or when the MS releases resource, the queuing instance receives the message of resource available. If the resource request is due to MSC-controlled incoming handover, the counter increments. The measurement point is A, as shown in Figure 2978.
FIGURE 2978 QUEUING EXECUTION
Second Cell
3122
Chapter
107
Overview
Local switch measurement performs measurement for the success rate of local switch establishment, failure causes, and the distribution of local switch types that are attempted to establish. Statistic unit in this measurement is cell.
3123
This counter counts the number of requests of local switch establishment inside BSC received by the service module from the local switch management module. As shown in Figure 2979, when the EV_LSMNG_LS_START_REQ message is received, if the local switch type to be established is inside BSC, the counter counts.
FIGURE 2979 LOCAL SWITCH ESTABLISHMENT REQUEST
Times Cell
This counter counts the number of requests of local switch establishment inside BSC received by the service module from the local switch management module. As shown in Figure 2980, when the EV_LSMNG_LS_START_REQ message is received, if the local switch type to be established is inside site, the counter counts.
FIGURE 2980 LOCAL SWITCH ESTABLISHMENT REQUEST
3124
Times Cell
C902130003 The Request Number of Local Switch Establish (Inside Site Group)
Description
This counter counts the number of requests of local switch establishment inside BSC received by the service module from the local switch management module. As shown in Figure 2981, when the EV_LSMNG_LS_START_REQ message is received, if the local switch type to be established is inside site group, the counter counts.
FIGURE 2981 LOCAL SWITCH ESTABLISHMENT REQUEST
Times Cell
C902130004 The Request Number of Local Switch Release (Return Normal Call)
Description
This counter counts the number of normal calls returned from the local switch after the service module receives the request message. This measurement is performed at two measurement points. The first measurement point: After handover is performed, if the local switch cannot be held, the local switch management module sends the request of local switch establishment to reestablish the
3125
voice channel that passes TC. After the RANCS module receives the request message, the counter counts. The second measurement point: If the local switch cannot be held due to various abnormalities, the local switch management module sends the request of local switch termination. After the RANCS module receives the termination request, the counter counts. The measurement points are shown in Figure 2982 and Figure 2983.
FIGURE 2982 RETURNING NORMAL CALL REQUEST
DURING
HANDOVER
FROM
LOCAL SWITCH
Times Cell
C902130005 The Failure Number of Establishing Local Switch (Inside BSC/Connect Fail)
Description
This counter counts the number of failures of local switch establishment inside BSC, and the failure is due to connection failure. As shown in Figure 2984, to establish the local switch inside BSC, the DSP channel at the Abis interface processing board should be connected. When connecting the board fails or connecting the board expires, the counter increments.
3126
Times Cell
C902130006 The Failure Number of Establishing Local Switch (Inside BSC/Other Reason Fail)
Description
This counter counts the number of failures of local switch establishment inside BSC, and the failure is due to other causes except for connection failure. This counter is supported in version V6.20.614c. Times Cell
C902130007 The Failure Number of Establishing Local Switch (Inside Site/Fail Returned by Site)
Description
This counter counts the number of failures of local switch establishment inside the site, and the failure is due to response failure of the site. As shown in Figure 2985, to establish the local switch inside the site, the request of local switch establishment should be sent to the site. After the site receives the request, it judges
3127
whether the local switch can be established with the relevant resource inside the site. If the local switch can be established, the site returns the message that the local switch is established successfully; otherwise, the site returns the message that the local switch establishment fails. If RANCS service receives the message indicating the failure of local switch establishment inside the site (ABIS_LOCALSWITCH_NACK), the counter increments.
FIGURE 2985 FAILURE
OF
Times Cell
C902130008 The Failure Number of Establishing Local Switch (Inside Site Group/Fail Returned by Site)
Description
This counter counts the number of failures of local switch establishment inside the site group, and the failure is due to response failure of the site. As shown in Figure 2986, to establish the local switch inside the site group, the request of local switch establishment should be sent to the site. After the site receives the request, it judges whether to start sending voice package to the opposite-end site and simultaneously receiving the voice package from the opposite-end site. If the corresponding voice package can be received from the opposite-end site within a period of time, it indicates that the local switch is allowed, and the site returns the message of the local switch being established successfully; otherwise, the site returns the message that the local switch establishment fails. If RANCS service receives the message indicating the failure of local switch establishment inside the site group (ABIS_LOCALSWITCH_NACK), the counter increments.
3128
OF
Times Cell
C902130009 The Failure Number of Establishing Local Switch (Inside Site/No answer from Site)
Description
This counter counts the number of failures of local switch establishment inside the site, and the failure is due to that the site's responding time expires. As shown in Figure 2987, to establish the local switch inside the site, the request of local switch establishment should be sent to the site. If it expires that RANCS service waits for the message indicating local switch establishment success inside the site (ABIS_LOCALSWITCH_ACK), the counter increments.
FIGURE 2987 RESPONDING TIME EXPIRES SWITCH INSIDE SITE
WHEN
ESTABLISHING LOCAL
Times
3129
Statistics Object
Cell
C902130010 The Failure Number of Establishing Local Switch (Inside Site Group/No answer from Site)
Description
This counter counts the number of failures of local switch establishment inside the site group, and the failure is due to that the site's responding time expires. As shown in Figure 2988, to establish the local switch inside the site group, the request of local switch establishment should be sent to the site. If it expires that RANCS service waits for the message indicating local switch establishment success inside the site group (ABIS_LOCALSWITCH_ACK), the counter increments.
FIGURE 2988 RESPONDING TIME EXPIRES SWITCH INSIDE SITE
WHEN
ESTABLISHING LOCAL
Times Cell
C902130011 The Failure Number of Establishing Local Switch (Inside Site/Other Reason Fail)
Description
This counter counts the number of failures of local switch establishment inside the site, and the failure is due to other causes
3130
except for that the site fails to respond and the site's responding time expires. This counter is supported in version V6.20.614c.
Unit Statistics Object
Times Cell
C902130012 The Failure Number of Establishing Local Switch (Inside Site Group/Other Reason Fail)
Description
This counter counts the number of failures of local switch establishment inside the site group, and the failure is due to other causes except for that the site fails to respond and the site's responding time expires. This counter is supported in version V6.20.614c. Times Cell
This counter counts the number of failures of the local switch returning the normal call, and the failure is due to Abis resource unavailable. When the local switch is inside the site or the site group, the corresponding Abis resource is not required after the local switch is established, thus the resource is released. However, when the local switch returns the normal call, the Abis resource should be requested again. If the database module returns that the Abis resource request fails, the counter increments. The measurement point is A, as shown in Figure 2989.
3131
OF
FROM
LOCAL SWITCH
Times Cell
This counter counts the number of failures of the local switch returning the normal call, and the failure is due to connection failure. When the local switch returns the normal call, the Abis resource and the TC resource (for external TC, it is Ater resource) should be connected again. The measurement point is B, as shown in Figure 2990 and Figure 2991. If the board returns the message indicating connection failure or that the waiting for connection response expires, the counter increments.
FIGURE 2990 PROCESS (TC IS INTERNAL)
OF
FROM
LOCAL SWITCH
3132
OF
FROM
LOCAL SWITCH
Times Cell
This counter counts the number of failures of the local switch returning the normal call, and the failure is due to Ater resource unavailable. When BSC is configured as TC being external, the corresponding Ater resource is not required after the local switch is established, thus the resource is released. However, when the local switch returns the normal call, the Ater resource should be requested again. If iTC returns that the Ater resource request fails (Ater_ResrcReqNegAck), the counter increments. The measurement point is A, as shown in Figure 2992.
FIGURE 2992 FAILURE (TC IS EXTERNAL)
OF
FROM
LOCAL SWITCH
3133
Times Cell
3134
Chapter
108
TFO Measurement
Table of Contents C902420001 Number of first try to contact distant partner after TFO being enabled ................................................. 3135 C902420002 Number of retrying to contact distant partner after being interrupted ................................................... 3136 C902420003 Number of TFO contacting with distant partner after first try................................................................. 3137 C902420004 Number of TFO recontacting with distant partner after TFO being interrupted............................................. 3138 C902420005 Number of TFO establishment after first try............................................................................... 3139 C902420006 Number of TFO reestablishment after being interrupted...................................................................... 3140 C902420007 Number of synchronization lost at A-Interface resulting in TFO off ........................................................ 3141 C902420008 Number of codec type mismatch resulting in TFO off ............................................................................... 3142 C902420009 Number of rate control failure resulting in TFO off when using AMR codec type ....................................... 3143 C902420010 Number of mode changes for establishing TFO ............................................................................. 3143 C902420011 Number of mode changes for optimizing TFO ............................................................................. 3144 C902420012 Number of active collection changes for establishing TFO ................................................................... 3144 C902420013 Number of active collection changes for optimizing TFO ........................................................................ 3144
C902420001 Number of first try to contact distant partner after TFO being enabled
Description
This counter counts the times that the TRAU attempts the TFO negotiation for the first time. This counter indicates the capability that the TRAU attempts TFO negotiation for the first time during MS conversations by sending the TFO message when TFO is enabled. During MS conversations, the TRAU receives the TFO_Enable message and starts the TFO state machine. When detecting the
3135
PCM_NON_IDLE message sent by the A interface, the TRAU sends the TFO_FILL message to the A interface first, and then sends the TFO_REQ/ACK message that carries the current speech version info to the peer end to attempt TFO negotiation.
Usage Measurement Point
None When the TRAU sends the TFO_REQ/ACK message for the first time, this counter increases by 1, as shown in Figure 2993.
FIGURE 2993 NUMBER OF FIRST ATTEMPT AFTER TFO BEING ENABLED
TO
Unit
Time
This counter counts the times that the TRAU re-attempts TFO negotiation after first TFO negotiation. This counter indicates the TFO re-negotiation capability when the TFO interaction is out-of-sync and when the configuration changes after handover during MS conversations. During the TFO negotiation attempt, when the TFO interaction on the A interface is out-of-sync, or the synchronization is lost after TFO establishment, or speech version configuration changes due to handover, the TRAU will re-send the TFO message that carries the local configuration info to attempt renegotiation.
None When the TRAU re-sends the TFO_REQ(_L) message, this counter increases by 1, as shown in Figure 2994.
3136
OF
RETRYING
TO
Unit
Time
C902420003 Number of TFO contacting with distant partner after first try
Description
This counter counts the times that the TRAU succeeds in the first TFO negotiation attempt. This counter indicates the capability that the TRAU succeeds in the first TFO negotiation attempt. The TRAU receives the TFO_Enable message and starts the TFO state machine. When detecting the PCM_NON_IDLE message sent by the A interface, the TRAU sends the TFO_FILL message to the A interface first, and then sends the TFO_REQ/ACK message that carries the current speech version info to the peer end to attempt TFO negotiation. If the peer end supports TFO, the peer end will also attempt TFO negotiation by sending a response after receiving the TFO message sent by the local end. When the local end receives the TFO_ACK message replied by the peer end, it indicates that the negotiation succeeds.
None When the TRAU receives the TFO_ACK/TFO_Frame message sent by the peer end after sending the TFO_REQ/ACK message for the first time to attempt TFO negotiation, this counter increases by 1, as shown in Figure 2995.
3137
OF
TFO
Unit
Time
C902420004 Number of TFO recontacting with distant partner after TFO being interrupted
Description
This counter counts the times that the TRAU succeeds in TFO negotiation reattempt. This counter indicates the capability that the TRAU succeeds in TFO negotiation reattempt. During the TFO negotiation attempt, when the TFO interaction on the A interface is out-of-sync, or the synchronization is lost after TFO establishment, or speech version configuration changes due to handover, the TRAU will re-send the TFO_REQ(_L) message that carries the local configuration info to attempt renegotiation. If it still supports TFO, the peer end will respond to the TFO message sent by the local end or initiate the similar renegotiation. When the local end receives the TFO_ACK(_L) message replied by the peer end, it indicates that the renegotiation succeeds.
None When the TRAU receives the TFO_ACK(_L) message replied by the peer end after re-sending the TFO_REQ(_L) message, this counter increases by 1, as shown in Figure 2996.
3138
FIGURE 2996 NUMBER OF TFO RECONTACTING WITH DISTANT PARTNER AFTER TFO BEING INTERRUPTED
Unit
Time
This counter counts the times that the TRAU succeeds in TFO establishment after the first TFO negotiation. This counter indicates the capability that the TRAU succeeds in TFO establishment after the first TFO negotiation. During MS conversations, the TRAU receives the TFO_Enable message and starts the TFO state machine. When detecting the PCM_NON_IDLE message sent by the A interface, the TRAU sends the TFO message to attempt the first TFO negotiation. If it supports TFO, the peer end will take similar action to attempt TFO negotiation by responding to the TFO message sent by the local end. When the local end receives the TFO_ACK message replied by the peer end, it indicates that the negotiation succeeds. If the codec algorithms of the two parties match according to the negotiation result, the requirement for TFO establishment is met, and the TRAU will send the TFO frame.
None When the TRAU receives and uses the TFO frame, TFO is established and this counter increases by 1, as shown in Figure 2997.
3139
OF
Unit
Time
This counter counts the times that the TRAU succeeds in TFO establishment after TFO renegotiation. This counter indicates the capability that the TRAU succeeds in TFO establishment after TFO renegotiation. TFO may not be established successfully after the TRAU attempts the first negotiation. When the TFO synchronization is lost or speech version configuration changes due to handover, the TFO establishment may be interrupted. When the TFO establishment is interrupted, the TRAU will re-send the TFO_REQ(_L) message that carries the local configuration info to attempt renegotiation. If it still supports TFO, the peer end will respond to the TFO message sent by the local end or initiate the similar renegotiation. When the renegotiation is successful, the TRAU will send the TFO frame if the codec algorithms match according to the negotiation result indicating that the requirement for TFO establishment is met.
None When the TRAU receives and uses the TFO frame, TFO is established and this counter increases by 1, as shown in Figure 2998.
3140
OF
Unit
Time
This counter counts the times that TFO is interrupted due to synchronization loss on the A interface. This counter indicates the situation that TFO is interrupted or cannot be established due to TFO synchronization loss. When the TRAU attempts TFO establishment negotiation or TFO is established, the interaction of the TFO message or TFO frame is abnormal if synchronization on the A interface is lost. In this case, the TFO cannot be established or will be interrupted.
None When the TRAU attempts the TFO establishment negotiation, this counter increases by 1 if the TFO message replied by the peer end is interrupted or TFO cannot be established due to the failure in receiving the TFO frame sent by the peer end, as shown in Figure 2999. When TFO is established, this counter increases by 1 if TFO is interrupted due to TFO synchronization loss, as shown in Figure 3000.
3141
AT
A-INTERFACE
AT
A-INTERFACE
Unit
Time
This counter counts the times that TFO is interrupted due to codec algorithm mistach. This counter indicates the impact of the codec algorithm configuration on TFO establishment. When the TRAU succeeds in TFO negotiation, TFO cannot be established and this counter increases by 1 if the codec algorithms of the two parties do not match according to the negotiation result. When TFO is established, TFO is interrupted and this counter increases by 1 if the local or remote codec algorithm changes due to handover and the codec algorithms do not match after renegotiation.
3142
C902420009 Number of rate control failure resulting in TFO off when using AMR codec type
Description
This counter counts the times that TFO cannot be established due to rate control failure during TFO establishment when the MS uses the AMR algorithm. This counter indicates the times that TFO cannot be established due to rate control failure when the MS uses the AMR algorithm. After the TRAU succeeds in TFO negotiation, the TRAU sends the TFO_SOON configuration message to the BTS, indicating that the currently requested CMR is the highest speech coding rate that meets the requirement for TFO establishment, if the codec algorithms of two parties are AMR and ACS configuration collection meets the requirement for TFO establishment according to the negotiation result. Meanwhile, the TRAU starts a TFO timer, which requires the BTS to control the uplink speech coding rate within the permitted time range. After receiving the TFO_SOON message, the BTS controls the MS uplink rate. When detecting that the uplink coding rate of the MS does not exceed CMR, the BTS considers that the rate control is successful and replies a TFO_SOON message to the TRAU. If the TRAU does not receive the TFO_SOON message replied by the BTS before the timer times out, it indicates that the rate control fails and TFO cannot be established. In this case, this counter increases by 1.
This counter does not count for the time being. ZGO-04-02-006 TFO
3143
This counter does not count for the time being. ZGO-04-02-006 TFO
This counter does not count for the time being. ZGO-04-02-006 TFO
This counter does not count for the time being. ZGO-04-02-006 TFO
3144
Chapter
109
IP SLA PD Statistic
Table of Contents C902270001 PD Type..................................................... 3145 C902270002 PD SubType ............................................... 3146 C902270003 ULP Pno..................................................... 3146 C902270004 ULP TYPE ................................................... 3146 C902270005 ULP ID ...................................................... 3146 C902270006 Packet Type................................................ 3147 C902270007 Up Protocol ................................................ 3147 C902270008 Source IP 1 ................................................ 3147 C902270009 Source IP 2 ................................................ 3147 C902270010 Source IP 3 ................................................ 3147 C902270011 Source IP 4 ................................................ 3148 C902270012 Source Port ................................................ 3148 C902270013 Destination IP 1.......................................... 3148 C902270014 Destination IP 2.......................................... 3148 C902270015 Destination IP 3.......................................... 3149 C902270016 Destination IP 4.......................................... 3149 C902270017 Destination Port.......................................... 3149 C902270018 Send PD Request ........................................ 3150 C902270019 Receive PD Reply ........................................ 3150 C902270020 PD Packet Loss Rate .................................... 3150 C902270021 PD Packet statistics by watch time................. 3150 C902270022 PD Packet Loss Rate by watch time ............... 3151 C902270023 PD Packet Out of Sequence .......................... 3151 C902270024 Receive PD Request..................................... 3151 C902270025 Send PD Reply............................................ 3152 C902270025 Min Delay .................................................. 3152 C902270027 Max Delay.................................................. 3152 C902270028 Mean Delay ................................................ 3152 C902270029 Max Jitter .................................................. 3153 C902270030 Min Jitter ................................................... 3153 C902270031 Mean Jitter................................................. 3153 C902270032 Jitter Sampling Times .................................. 3153 C902270033 Number of delay sampling............................ 3154
C902270001 PD Type
Description Usage Measurement Point Unit
3145
C902270002 PD SubType
Description Usage Measurement Point Unit
For IP PD, each bit of ucPDSubType indicates a performance index. For other detection type, this field is reserved. None None None
This counter indicates the process No. of the upper layer user. None None None
The ULP type is used to differentiate multiple upper layer users of a same process. For example, when SCTP/TCP/DNS/RTP of the BRS process initiates detection, the respective protocol No. is set as the ULP type. None None None
C902270005 ULP ID
Description Usage Measurement Point Unit
The ULP IDs are used to identify multiple detection tasks initiated by a same upper layer user. None None None
3146
This counter indicates the detection packet type (ICMP or UDP). None None None
C902270007 Up Protocol
Description Usage Measurement Point Unit
This counter indicates No. of the upper layer protocol for internal encapsulation (1: ICMP, 6: TCP, 17: UDP, 132: SCTP). None None None
C902270008 Source IP 1
Description Usage Measurement Point Unit
C902270009 Source IP 2
Description Usage Measurement Point Unit
C902270010 Source IP 3
Description
3147
C902270011 Source IP 4
Description Usage Measurement Point Unit
This counter indicates No. of the source port. None None None
C902270013 Destination IP 1
Description Usage Measurement Point Unit
C902270014 Destination IP 2
Description Usage
3148
None None
C902270015 Destination IP 3
Description Usage Measurement Point Unit
C902270016 Destination IP 4
Description Usage Measurement Point Unit
This counter indicates No. of the destination port. None None None
3149
The counter counts the number of the sent PD Requests. None None None
The counter counts the number of the received PD replies. None None None
This counter indicates the PD packet loss ratio. The field is scraped. None This counter is updated when the delay reporting timer times out or PD response packet is received or PD status is queried. 0.1
The counter counts the number of packets received in the specified watch time. None
3150
This counter is updated when a packet is received in the watch time. None
The counter indicates the packet loss ratio in the specified watch time. None This counter is updated when the delay reporting timer times out or the PD reply packet is received or the PD status is queried. 0.1
The counter counts the number of PD packets that are out of sequence. None This counter is increased by 1 when an out-of-sequence PD reply packet is received. None
The counter counts the number of received PD requests. This counter is not supported and its value is invalid currently. None This counter increases by 1 when a PD request is received. None
3151
The counter counts the number of send PD replies. This counter is not supported and its value is invalid currently. None This counter increases by 1 when a PD reply is rent. None
The counter indicates the minimum delay. None This counter is updated when a PD reply packet is received. ms
The counter indicates the maximum delay. None This counter is updated when a PD reply packet is received. ms
The counter indicates the mean delay. None This counter is updated when the delay reporting timer times out or the PD reply packet is received or the PD status is queried.
3152
Unit
ms
The counter indicates the maximum jitter. None This counter is updated when a PD reply packet is received. ms
The counter indicates the minimum jitter. None This counter is updated when the PD reply packet is received. ms
The counter indicates the mean delay. None This counter is updated when the delay reporting timer times out or the PD reply packet is received or the PD status is queried. ms
The counter counts the number of jitter samplings. None This counter is updated when a PD reply packet is received. Time
3153
The counter counts the number of delay samplings. None This counter is updated when a PD reply packet is received. Time
3154
Chapter
110
3155
C902430001 Number of handover attempts from adjacent 3G cell to the selected cell
Description
During an inter-system handover from an adjacent 3G cell to the selected cell, this counter increases by 1 when the BSC receives the Handover Request message from the MSC. None The measurement point is A1 shown in Figure 3001.
FIGURE 3001 NUMBER OF HANDOVER ATTEMPTS CELL TO THE SELECTED CELL
FROM THE
ADJACENT 3G
Unit
Time
C902430002 Number of successful handovers from adjacent 3G cell to the selected cell
Description
During an inter-system handover from an adjacent 3G cell to the selected cell, this counter increases by 1 when the BSC receives from the MS the Handover Complete message that indicates the incoming handover is successful. None The measurement point is A2 shown in the figure titled Number of Handover Attempts from the Adjacent 3G Cell to the Selected Cell. Time
3156
C902430003 Number of handover attempts from selected cell to the adjacent 3G cell
Description
During an inter-system handover from the selected cell to an adjacent 3G cell, this counter increases by 1 when the BSC sends the Handover Required message to the MSC. None The measurement point is A3 shown in Figure 3002.
FIGURE 3002 NUMBER OF HANDOVER ATTEMPTS TO THE ADJACENT 3G CELL
FROM THE
SELECTED CELL
Unit
Time
During an inter-system handover from the selected cell to an adjacent 3G cell, this counter increases by 1 when the BSC receives the Handover Command message from the MSC. None The measurement point is A4 shown in the figure titled Number of Handover Attempts from the Selected Cell to the Adjacent 3G Cell. Time
3157
C902430005 Number of successful handovers from selected cell to the adjacent 3G cell
Description
During an inter-system handover from the selected cell to an adjacent 3G cell, this counter increases by 1 when the BSC receives the Clear Command message (with the reason successful handover included) from the MSC. None The measurement point is A5 shown in the figure titled Number of Handover Attempts from the Selected Cell to the Adjacent 3G Cell. Time
C902430006 Number of handover attempts from selected cell to the adjacent 3G cell due to measurement result
Description
During an inter-system handover from the selected cell to an adjacent 3G cell, this counter increases by 1 when the handover is triggered by the measurement report and when the BSC sends the Handover Required message to the MSC. None The measurement point is A3 shown in the figure titled Number of Handover Attempts from the Selected Cell to the Adjacent 3G Cell. Time
3158
C902430007 Number of handovers from selected cell to the adjacent 3G cell due to measurement result
Description
During an inter-system handover from the selected cell to an adjacent 3G cell, this counter increases by 1 when the handover is triggered by the measurement report and when the BSC receives the Handover Command message from the MSC. None The measurement point is A4 shown in the figure titled Number of Handover Attempts from the Selected Cell to the Adjacent 3G Cell. Time
C902430008 Number of successful handovers from selected cell to the adjacent 3G cell due to measurement result
Description
During an inter-system handover from the selected cell to an adjacent 3G cell, this counter increases by 1 when the handover is triggered by the measurement report and when the BSC receives the Clear Command message (with the reason successful handover included) from the MSC. None The measurement point is A5 shown in the figure titled Number of Handover Attempts from the Selected Cell to the Adjacent 3G Cell. Time
3159
C902430009 Number of handover attempts from selected cell to the adjacent 3G cell due to traffic
Description
During an inter-system handover from the selected cell to an adjacent 3G cell, this counter increases by 1 when the handover is triggered by the traffic and when the BSC sends the Handover Required message to the MSC. None The measurement point is A3 shown in the figure titled Number of Handover Attempts from the Selected Cell to the Adjacent 3G Cell. Time
C902430010 Number of handovers from selected cell to the adjacent 3G cell due to traffic
Description
During an inter-system handover from the selected cell to an adjacent 3G cell, this counter increases by 1 when the handover is triggered by the traffic and when the BSC receives the Handover Command message from the MSC. None The measurement point is A4 shown in the figure titled Number of Handover Attempts from the Selected Cell to the Adjacent 3G Cell. Time
3160
C902430011 Number of successful handovers from selected cell to the adjacent 3G cell due to traffic
Description
During an inter-system handover from the selected cell to an adjacent 3G cell, this counter increases by 1 when the handover is triggered by the traffic and when the BSC receives the Clear Command message (with the reason successful handover included) from the MSC. None The measurement point is A5 shown in the figure titled Number of Handover Attempts from the Selected Cell to the Adjacent 3G Cell. Time
C902430012 Number of handover attempts from selected cell to the adjacent 3G cell due to saving call
Description
During an inter-system handover from the selected cell to an adjacent 3G cell, this counter increases by 1 when the handover is triggered as a rescue handover and when the BSC sends the Handover Required message to the MSC. None The measurement point is A3 shown in the figure titled Number of Handover Attempts from the Selected Cell to the Adjacent 3G Cell. Time
3161
C902430013 Number of handovers from selected cell to the adjacent 3G cell due to saving call
Description
During an inter-system handover from the selected cell to an adjacent 3G cell, this counter increases by 1 when the handover is triggered as a rescue handover and when the BSC receives the Handover Command message from the MSC. None The measurement point is A4 shown in the figure titled Number of Handover Attempts from the Selected Cell to the Adjacent 3G Cell. Time
C902430014 Number of successful handovers from selected cell to the adjacent 3G cell due to saving call
Description
During an inter-system handover from the selected cell to an adjacent 3G cell, this counter increases by 1 when the handover is triggered as a rescue handover and when the BSC receives the Clear Command message (with the reason successful handover included) from the MSC. None The measurement point is A5 shown in the figure titled Number of Handover Attempts from the Selected Cell to the Adjacent 3G Cell. Time
3162
Appendix
Corresponding Relationship between Basic Measurement Counters and General Measurement Counters
In the network management system, ZXG10 iBSC performance measurement has two types, basic measurement and general management. The difference between the two is that general measurement is impossible unless a measurement task is created, while basic measurement is used for regular reports, which can be outputted without creating a measurement task. Except different IDs, basic measurement counters and general measurement counters share the same information, such as name, description, and measurement. Table 1 lists the corresponding relationship between the two types of counters.
TABLE 1 CORRESPONDING RELATIONSHIP BETWEEN BASIC MEASUREMENT COUNTERS AND GENERAL MEASUREMENT COUNTERS Basic Measurement Counter ID C900040001 C900040002 C900040003 C900040004 C900040005 C900040006 C900040007 C900040008 C900040009 C900040010 Corresponding General Measurement Counter ID C901000007 C901000016 C901000017 C901000018 C901000019 C901000020 C901000021 C901000022 C901000029 C901000038
3163
Basic Measurement Counter ID C900040011 C900040012 C900040013 C900040014 C900040015 C900040016 C900040017 C900040018 C900040019 C900040020 C900040021 C900040022 C900040023 C900040024 C900040025 C900040026 C900040027 C900040028 C900040029 C900040030 C900040031 C900040032 C900040033 C900040034 C900040035 C900040036 C900040037 C900040038 C900040039 C900040040
Corresponding General Measurement Counter ID C901000039 C901000040 C901000041 C901000042 C901000043 C901000044 C901000049 C901000051 C901010008 C901010015 C901010016 C901010017 C901010018 C901010019 C901010020 C901010021 C901010029 C901010036 C901010037 C901010038 C901010039 C901010040 C901010041 C901010042 C901010047 C901010049 C901010051 C901010052 C901010053 C901010054
3164
Appendix A Corresponding Relationship between Basic Measurement Counters and General Measurement Counters
Basic Measurement Counter ID C900040041 C900040042 C900040043 C900040044 C900040045 C900040046 C900040047 C900040048 C900040049 C900040050 C900040051 C900040052 C900040053 C900040054 C900040055 C900040056 C900040057 C900040058 C900040059 C900040060 C900040061 C900040062 C900040063 C900040064 C900040065 C900040066 C900040067 C900040068 C900040069 C900040070
Corresponding General Measurement Counter ID C901010055 C901010057 C901010058 C901010059 C901010060 C901010061 C901020010 C901020011 C901020012 C901020013 C901020015 C901020016 C901020017 C901020018 C901020027 C901020028 C901020029 C901020030 C901020032 C901020033 C901020035 C901020036 C901020037 C901020038 C901020039 C901020040 C901020042 C901020043 C901020045 C901020046
3165
Basic Measurement Counter ID C900040071 C900040072 C900040073 C900040074 C900040075 C900040076 C900040077 C900040078 C900040079 C900040080 C900040081 C900040082 C900040083 C900040084 C900040085 C900040086 C900040087 C900040088 C900040089 C900040090 C900040091 C900040092 C900040093 C900040094 C900040095 C900040096 C900040097 C900040098 C900040099 C900040100
Corresponding General Measurement Counter ID C901020047 C901020048 C901020049 C901020051 C901020052 C901020053 C901020054 C901160015 C901160016 C901030001 C901030002 C901030003 C901030004 C901030005 C901030015 C901030016 C901030017 C901030018 C901030028 C901030029 C901030030 C901030031 C901030043 C901030044 C901030045 C901030046 C901030047 C901030057 C901030058 C901030059
3166
Appendix A Corresponding Relationship between Basic Measurement Counters and General Measurement Counters
Basic Measurement Counter ID C900040101 C900040102 C900040103 C900040104 C900040105 C900040106 C900040107 C900040108 C900040109 C900040110 C900040111 C900040112 C900040113 C900040114 C900040115 C900040116 C900040117 C900040118 C900040119 C900040120 C900040121 C900040122 C900040123 C900040124 C900040125 C900040126 C900040127 C900040128 C900040129 C900040130
Corresponding General Measurement Counter ID C901030060 C901030070 C901030071 C901030072 C901030073 C901030096 C901030097 C901170001 C901170006 C901170021 C901170022 C901170034 C901170035 C901180001 C901180006 C901180021 C901180022 C901180034 C901180035 C901190001 C901190014 C901190036 C901190037 C901190049 C901190050 C901190062 C901190063 C901200001 C901200014 C901200036
3167
Basic Measurement Counter ID C900040131 C900040132 C900040133 C900040134 C900040135 C900040136 C900040137 C900040138 C900040139 C900040140 C900040141 C900040142 C900040143 C900040144 C900040145 C900040146 C900040147 C900040148 C900040149 C900040150 C900040151 C900040152 C900040153 C900040154 C900040155 C900040156 C900040157 C900040158 C900040159 C900040160
Corresponding General Measurement Counter ID C901200037 C901200049 C901200050 C901200062 C901200063 C901040003 C901040007 C901040008 C901040016 C901040017 C901000002 C901000003 C901000004 C901000008 C901000024 C901000025 C901000026 C901000030 C901000053 C901000054 C901000055 C901000056 C901000057 C901000059 C901000060 C901000061 C901000062 C901000063 C901010003 C901010004
3168
Appendix A Corresponding Relationship between Basic Measurement Counters and General Measurement Counters
Basic Measurement Counter ID C900040161 C900040162 C900040163 C900040164 C900040165 C900040166 C900040167 C900040168 C900040169 C900040170 C900040171 C900040172 C900040173 C900040174 C900040175 C900040176 C900040177 C900040178 C900040179 C900040180 C900040181 C900040182 C900040183 C900040184 C900040185 C900040186 C900040187 C900040188 C900040189 C900040190
Corresponding General Measurement Counter ID C901010005 C901010063 C901010024 C901010025 C901010026 C901010030 C901040015 C901010009 C901000064 C901000065 C901010062 C901030006 C901030007 C901030008 C901030009 C901030010 C901030011 C901030012 C901030013 C901030014 C901030019 C901030020 C901030021 C901030022 C901030023 C901030024 C901030025 C901030026 C901030027 C901030032
3169
Basic Measurement Counter ID C900040191 C900040192 C900040193 C900040194 C900040195 C900040196 C900040197 C900040198 C900040199 C900040200 C900040201 C900040202 C900040203 C900040204 C900040205 C900040206 C900040207 C900040208 C900040209 C900040210 C900040211 C900040212 C900040213 C900040214 C900040215 C900040216 C900040217 C900040218 C900040219 C900040220
Corresponding General Measurement Counter ID C901030033 C901030034 C901030035 C901030036 C901030037 C901030038 C901030039 C901030040 C901030048 C901030049 C901030050 C901030051 C901030052 C901030053 C901030054 C901030055 C901030056 C901030061 C901030062 C901030063 C901030064 C901030065 C901030066 C901030067 C901030068 C901030069 C901030074 C901030075 C901030076 C901030077
3170
Appendix A Corresponding Relationship between Basic Measurement Counters and General Measurement Counters
Basic Measurement Counter ID C900040221 C900040222 C900040223 C900040224 C900040225 C900040232 C900040233 C900040234 C900040235 C900030001 C900030002 C900060001 C900060002 C900060003 C900060004 C900060005 C900060006 C900060007 C900060008 C900060009 C900060010 C900060011 C900060012 C900060013 C900060014 C900060015 C900060016 C900060017 C900060018 C900060019
Corresponding General Measurement Counter ID C901030078 C901030079 C901030080 C901030081 C901030082 C901020055 C901020056 C901020057 C901020058 C901460004 C901460005 C901110005 C901110007 C901250001 C901250002 C901250003 C901250004 C901250006 C901250008 C901250009 C901260001 C901260003 C901260004 C901260006 C901260008 C901260009 C901260012 C901260014 C901260015 C901260020
3171
Basic Measurement Counter ID C900060020 C900060021 C900060022 C900060023 C900060024 C900060025 C900060026 C900060027 C900060028 C900060029 C900060030 C900060031 C900060032 C900060033 C900060034 C900060035 C900060036 C900060037 C900060038 C900060039 C900060040 C900060041 C900060042 C900060043 C900060044 C900060045 C900060046 C900060047 C900060048 C900060049
Corresponding General Measurement Counter ID C901260022 C901260023 C901260025 C901260027 C901260028 C901260039 C901260051 C901260052 C901260063 C901260064 C901260069 C901260071 C901260072 C901260074 C901260076 C901260077 C901260088 C901260089 C901270001 C901270003 C901270004 C901270006 C901270020 C901270022 C901270023 C901270025 C901270069 C901270071 C901270072 C901270074
3172
Appendix A Corresponding Relationship between Basic Measurement Counters and General Measurement Counters
Basic Measurement Counter ID C900060050 C900060051 C900060052 C900060053 C900060054 C900060055 C900060056 C900060057 C900060058 C900060059 C900060060 C900060061 C900060062 C900060063 C900060064 C900060065 C900060066 C900060067 C900060068 C900060069 C900060070 C900060071 C900060072 C900060073 C900060074 C900060075 C900060076 C900060077 C900060078 C900060079
Corresponding General Measurement Counter ID C901150003 C901150008 C901070006 C901070050 C901070051 C901070052 C901120019 C901120020 C901120021 C901120022 C901120023 C901120025 C901120026 C901120027 C901120028 C901120029 C901120036 C901120037 C901120038 C901120039 C901120040 C901120041 C901120042 C901120043 C901120044 C901120045 C901120046 C901120047 C901120048 C901120049
3173
Basic Measurement Counter ID C900060080 C900060081 C900060082 C900060083 C900060084 C900060085 C900060086 C900060087 C900060088 C900060089 C900060090 C900060091 C900060092 C900060093 C900060094 C900060095 C900060096 C900060097 C900060098 C900060099 C900060100 C900060101 C900060102 C900060103 C900060104 C900060105 C900060106 C900060107 C900060108 C900060109
Corresponding General Measurement Counter ID C901120050 C901120051 C901060025 C901060026 C901060027 C901060028 C901060029 C901060030 C901060031 C901060032 C901060033 C901060034 C901060047 C901090002 C901090003 C901090009 C901090010 C901090012 C901090019 C901090029 C901090031 C901090033 C901090036 C901090050 C901090051 C901090056 C901090057 C901090070 C901090071 C901090076
3174
Appendix A Corresponding Relationship between Basic Measurement Counters and General Measurement Counters
Basic Measurement Counter ID C900060110 C900060111 C900060112 C900060113 C900060114 C900060115 C900060116 C900060117 C900060118 C900060119 C900060120 C900060121 C900060122 C900060123 C900060124 C900060125 C900060126 C900060127 C900060128 C900060129 C900060130 C900060131 C900060132 C900060133 C900060134 C900060135 C900060136 C900060137 C900060138 C900060139
Corresponding General Measurement Counter ID C901090077 C901090082 C901090083 C901090088 C901090089 C901090094 C901090095 C901090100 C901090101 C901090106 C901090107 C901080013 C901080001 C901080002 C901080005 C901080009 C901080010 C901080015 C901080021 C901080023 C901080031 C901110025 C901150013 C901080007 C901080028 C901270015 C901110002 C901110030 C901260029 C901260030
3175
Basic Measurement Counter ID C900060140 C900060141 C900060142 C900060143 C900060144 C900060145 C900060146 C900060147 C900060148 C900060149 C900060150 C900060151 C900060152 C900060153 C900060154 C900060155 C900060156 C900060157 C900060158 C900060159 C900060160 C900060161 C900060162 C900060163 C900060164 C900060165 C900060166 C900060167 C900060168 C900060169
Corresponding General Measurement Counter ID C901260031 C901260040 C901260041 C901260042 C901260043 C901260053 C901260054 C901260055 C901260078 C901260079 C901260080 C901070041 C901280058 C901280059 C901280060 C901080019 C901260034 C901260035 C901260036 C901260037 C901260046 C901260047 C901260048 C901260049 C901260058 C901260059 C901260060 C901260061 C901260066 C901260083
3176
Appendix A Corresponding Relationship between Basic Measurement Counters and General Measurement Counters
Basic Measurement Counter ID C900060170 C900060171 C900060172 C900060173 C900060174 C900060175 C900060176 C900060177 C900060178 C900060179 C900060180 C900060181 C900060182 C900060183 C900060184 C900060185 C900060186 C900060187 C900060188 C900060189 C900060190 C900060191 C900060192 C900060193 C900060194 C900060195 C900060196 C900060197 C900060198 C900060199
Corresponding General Measurement Counter ID C901260084 C901260085 C901260086 C901260091 C901270009 C901270028 C901270029 C901270030 C901270031 C901270034 C901270035 C901270036 C901270037 C901270040 C901270041 C901270042 C901270043 C901270046 C901270047 C901270048 C901270049 C901270052 C901270053 C901270054 C901270055 C901270058 C901270059 C901270060 C901270061 C901270063
3177
Basic Measurement Counter ID C900060200 C900060201 C900060202 C900060203 C900060204 C900060205 C900060206 C900060207 C900060208 C900060209 C900060210 C900060211 C900060212 C900060213 C900060214 C900060215 C900060216 C900060217 C900060218 C900060219 C900060220 C900060221 C900060222 C900060223 C900060224 C900060225 C900060226 C900060227 C900060228 C900060229
Corresponding General Measurement Counter ID C901270064 C901270066 C901270077 C901270078 C901270079 C901270080 C901270083 C901270084 C901270085 C901270086 C901270088 C901270089 C901270091 C901090014 C901090016 C901090018 C901090035 C901080020 C901080029 C901070013 C901070020 C901070027 C901070034 C901070048 C901060048 C901060049 C901060050 C901060051 C901060052 C901060053
3178
Appendix A Corresponding Relationship between Basic Measurement Counters and General Measurement Counters
Basic Measurement Counter ID C900060230 C900060231 C900060232 C900060233 C900060234 C900060235 C900060236 C900060237 C900060238 C900060239 C900060240 C900060241 C900060242 C900060243 C900060244 C900060245 C900050001 C900050002
Corresponding General Measurement Counter ID C901060054 C901060055 C901060056 C901060057 C901060070 C901270014 C901110004 C901090143 C901090144 C901090146 C901090147 C901250013 C901250014 C901250015 C901070016 C901070037 C901410004 C901410003
3179
3180
Glossary
3G - The 3rd Generation Mobile Communications - AGCH - Absolute Grant Channel - ALCAP - Access Link Control Application Protocol - ATM - Asynchronous Transfer Mode - BHCA - Busy Hour Call Attempt - BSC - Base Station Controller - BSS - Base Station System - BTS - Base Transceiver Station - BVC - BSSGP Virtual Connection - BSSGP CCCH - Common Control Channel CMP - Calling Main Processor - CPU - Central Processing Unit - CS - Circuit Switched - DB - DataBase - DM - Delay Measurement -
3181
DSP - Digital Signal Processor - DTAP - Direct Transfer Application Part - FDD - Frequency Division Duplex - GPRS - General Packet Radio Service - GSM - Global System for Mobile Communication - HR - Half Rate - IMSI - International Mobile Subscriber Identity - IP - Internet Protocol - LAPD - Link Access Procedure for D-channel - LLC - Logic Link Control - MAC - Medium Access Control - MO - Mobile Originated - MOC - Mobile Original Call - MS - Mobile Station - MSC - Mobile Switching Center - MSU - Message Signal Unit - MT - Mobile Terminated -
3182
Glossary
MTC - Mobile Terminated Call - NACC - Network Assisted Cell Change - NSE - Network Service Entity - NSVC - Network Service Virtual Connection - OMC-R - Operations& Maintenance Center-Radio - PACCH - Packet Associated Control Channel - PCH - Paging Channel - PCU - Packet Control Unit - PDTCH - Packet Data Traffic Channel - PDU - Packet Data Unit - PRI - Primary Rate Interface - / 2M PS - Packet Switched - PSI - PCF Session Identity - PCF PSK - Phase Shift Keying - QoS - Quality of Service - RLC - Radio Link Control - RMM - RF Management Module
3183
RMM is the control centre of RFS. It works on a 1+1 standby mode.The clock reference is also provided by the RMM. - RR - Resource Record - SACCH - Slow Associated Control Channel - SAPI - Service Access Point Identifier - SCCP - SS7 Signaling Connection Control Part - SS7 SCCP - Signaling Connection Control Part - SDCCH - Stand alone Dedicated Control Channel - SGSN - Service GPRS Supporting Node - GPRS SIF - Signaling Information Field - SIO - Service Information Octet - SM - Short Message - SMM - Session Manage Module - SNM - Signaling Network Management - TCH - Traffic Channel - / TDD - Time Division Duplex - TDM - Time Division Multiplexing - TFA - Transfer Allowed signal - /
3184
Glossary
TFC - Transfer Controlled signal - / TFI - TDM Fiber Interface - TDM TFO - Tandem Free Operation - TFP - Transfer Prohibited signal - / TRX - Transmitter and Receiver - TS - Time Slot - UL - Uplink - USSD - Unstructured Supplementary Service Data - eMLPP - enhanced Multi-Level Precedence and Pre-emption -
3185