nokia nsn traffic measurments

1 Traffic Measurement

DN9813827Issue 11-1 en29/04/2008

# Nokia Siemens Networks 1 (319)

BSC3153Nokia GSM/EDGE BSS, Rel. BSS13, BSC andTCSM, Rel. S13, Product Documentation, v.4

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given as is and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright Nokia Siemens Networks 2008. All rights reserved.

2 (319) # Nokia Siemens Networks DN9813827Issue 11-1 en

29/04/2008


Contents

Contents 3

List of tables 9

List of figures 10

Summary of changes 15

1 1 Traffic Measurement 17

2 Counters of Traffic Measurement 312.1 001000 / SEIZURE ATTEMPTS 312.2 001001 / SEIZURE ATTEMPTS WITH BUSY SDCCH 322.3 001002 / TRANSACTIONS FAIL DUE TO BSS FAIL 322.4 001003 / TRANSACTIONS FAIL DUE TO RADIO FAIL 332.5 001004 / TRANSACTIONS FAIL DUE RADIO ON SOURCE CHANNEL

DURING HO 342.6 001005 / TRANSACTIONS FAIL DUE RADIO ON TARGET

CHANNEL 352.7 001006 / SUCCESS SEIZURE FOR HO 362.8 001007 / SUCCESS SEIZURE FOR IMMEDIATE ASSIGNMENT 362.9 001008 / SUCCESS TCH SEIZURE FOR HO 372.10 001009 / SUCCESS TCH SEIZURE FOR NORMAL ASSIGNMENT 372.11 001010 / TCH REQUEST SUCCESS AND UNSUCCESS 382.12 001011 / TCH REQUEST REJECTED DUE TO LACK 392.13 001012 / TRANSACTIONS ENDED DUE TO BSS PROBLEM 402.14 001013 / TRANSACTIONS ENDED DUE RADIO FAIL 412.15 001014 / TRANSACTIONS ENDED DUE SOURCE CHANNEL FAIL

DURING HO 422.16 001015 / TRANSACTIONS ENDED DUE TARGET CHANNEL FAIL 422.17 001016 / CALL ATTEMPTS IN THE QUEUE 432.18 001017 / HANDOVER ATTEMPTS IN THE QUEUE 442.19 001018 / AVE QUEUE LENGTH FOR CHANNEL SEIZURE

REQUEST 452.20 001019 / QUEUE DENOMINATOR 1 452.21 001020 / AVE QUEUE TIME OF CALL ATTEMPTS 462.22 001021 / QUEUE DENOMINATOR 2 472.23 001022 / AVE QUEUE TIME OF HO ATTEMPTS 472.24 001023 / QUEUE DENOMINATOR 3 482.25 001024 / NOT SERVED QUEUED CALL ATTEMPTS 492.26 001025 / NOT SERVED QUEUED HO ATTEMPTS 502.27 001026 / TCH CALL REQ 502.28 001027 / SDCCH ACT FAIL 512.29 001028 / TCH ACT FAIL 522.30 001029 / TCH TR FAIL 532.31 001030 / TCH TR FAIL SOURCE 532.32 001031 / TCH TR FAIL TARGET 542.33 001032 / NOT RELEVANT 55

DN9813827Issue 11-1 en29/04/2008


Contents

2.34 001033 / SDCCH ABIS PROBL 552.35 001034 / SDCCH A IF PROBL 562.36 001035 / SDCCH LAPD FAIL 572.37 001036 / SDCCH BTS FAIL 572.38 001037 / SDCCH USER ACT 582.39 001038 / SDCCH BCSU RESET 592.40 001039 / SDCCH NETW ACT 592.41 001040 / TRUNK RES INVOC 602.42 001041 / SUCC TRUNK RES INVOC 612.43 001042 / TRUNK RES INVOC RES REFUSED 612.44 001043 / TCH REQ FACCH CALLSET 622.45 001044 / TCH SEIZ FACCH CALL SET 632.46 001045 / TCH ABIS PROBL 642.47 001046 / TCH LAPD FAIL 642.48 001047 / TCH BTS FAIL 652.49 001048 / TCH USER ACT 662.50 001049 / TCH BCSU RESET 662.51 001050 / TCH NETW ACT 672.52 001051 / TCH A IF PROBL 682.53 001052 / TRHO REQ 682.54 001053 / TRHO ENQUIRIES 692.55 001054 / FOR REL ASSIGN REQ ATT 702.56 001055 / FOR HO ASSIGN REQ ATT 702.57 001056 / QUE ALL ASSIGN REQ ATT 712.58 001057 / QUE NALL ASSIGN REQ ATT 722.59 001058 / FOR REL ASSIGN REQ FAIL 732.60 001059 / FOR HO ASSIGN REQ FAIL 742.61 001060 / QUE ALL ASSIGN REQ FAIL 752.62 001061 / QUE NALL ASSIGN REQ FAIL 752.63 001062 / FOR REL HO REQ ATT 762.64 001063 / FOR HO HO REQ ATT 772.65 001064 / QUE ALL HO REQ ATT 782.66 001065 / QUE NALL HO REQ ATT 782.67 001066 / FOR REL HO REQ FAIL 792.68 001067 / FOR HO HO REQ FAIL 802.69 001068 / QUE ALL HO REQ FAIL 812.70 001069 / QUE NALL HO REQ FAIL 822.71 001070 / FORCED RELEASES 822.72 001071 / FORCED HANDOVERS 832.73 001072 / SDCCH ACT FAIL CALL 842.74 001073 / NOT RELEVANT 842.75 001074 / SDCCH ACT FAIL TARGET 852.76 001075 / SDCCH ABIS FAIL CALL 862.77 001076 / SDCCH ABIS FAIL SOURCE 862.78 001077 / SDCCH ABIS FAIL TARGET 872.79 001078 / SDCCH A IF FAIL CALL 882.80 001079 / SDCCH A IF FAIL SOURCE 892.81 001080 / SDCCH A IF FAIL TARGET 902.82 001081 / TCH ACT FAIL CALL 902.83 001082 / NOT RELEVANT 912.84 001083 / TCH ACT FAIL TARGET 922.85 001084 / TCH ABIS FAIL CALL 92


29/04/2008


2.86 001085 / TCH ABIS FAIL SOURCE 932.87 001086 / TCH ABIS FAIL NEW 942.88 001087 / TCH A IF FAIL CALL 942.89 001088 / TCH A IF FAIL SOURCE 952.90 001089 / TCH A IF FAIL NEW 962.91 001090 / TCH REQ UND OVER 972.92 001091 / TCH SEIZ UND OVER 982.93 001092 / TCH REJ REQ UND OVE 982.94 001093 / SUCC MOC TEST CALL 992.95 001094 / FAIL MOC TEST CALL 1002.96 001095 / PRI SUBSCR TCH REQ 1002.97 001096 / PRI SUBSCR SUCC TCH SEIZ 1012.98 001097 / NO PRI SUBSCR REFUSED TCH REQ 1022.99 001098 / TCH SEIZ ATT DUE SDCCH CON 1032.100 001099 / TCH SEIZ DUE SDCCH CON 1042.101 001100 / TRUNK TCH REJECTED FR REQ 1042.102 001101 / TRUNK TCH REJECTED HR REQ 1052.103 001102 / FULL TCH REQ SUCC UNSUCC 1062.104 001103 / HALF TCH REQ SUCC UNSUCC 1072.105 001104 / TCH REQ FULL PREFERRED 1082.106 001105 / TCH REQ HALF PREFERRED 1092.107 001106 / SUCC FULL TCH SEIZ 1112.108 001107 / SUCC HALF TCH SEIZ 1112.109 001108 / FULL TCH SEIZ SPEECH VER 1 1122.110 001109 / FULL TCH SEIZ SPEECH VER 2 1132.111 001110 / FULL TCH SEIZ SPEECH VER 3 1142.112 001111 / HALF TCH SEIZ SPEECH VER 1 1152.113 001112 / HALF TCH SEIZ SPEECH VER 2 1162.114 001113 / HALF TCH SEIZ SPEECH VER 3 1172.115 001114 / FULL TCH SEIZ NORM ASSIGNMENT 1182.116 001115 / HALF TCH SEIZ NORM ASSIGNMENT 1192.117 001116 / FULL TCH SEIZ INT HO CH RATE 1202.118 001117 / HALF TCH SEIZ INT HO CH RATE 1212.119 001118 / REJ TCH REQ DUE LACK FR 1222.120 001119 / REJ TCH REQ DUE LACK HR 1232.121 001120 / FULL TCH REJ DUE HR TRAF 1242.122 001121 / HALF TCH REJ DUE FR TRAF 1252.123 001122 / TCH REJ DUE REQ CH A IF CRC 1262.124 001123 / FULL TCH REQ FACCH CALL 1262.125 001124 / TCH FACCH CALL CH RATE NOT DEF 1272.126 001125 / SUCC FULL TCH SEIZ FACCH CALL 1282.127 001126 / SUCC HALF TCH SEIZ FACCH CALL 1292.128 001127 / ENDED DUE TRANSC FR RATE 1 1302.129 001128 / ENDED DUE TRANSC FR RATE 2 1302.130 001129 / ENDED DUE TRANSC FR RATE 3 1312.131 001130 / ENDED DUE TRANSC HR RATE 1 1322.132 001131 / ENDED DUE TRANSC HR RATE 2 1322.133 001132 / ENDED DUE TRANSC HR RATE 3 1332.134 001133 / FULL TCH TR FAIL 1342.135 001134 / HALF TCH TR FAIL 1352.136 001135 / SDCCH SEIZ ATT FOR MOC 1362.137 001136 / SDCCH SEIZ ATT FOR MTC 136

DN9813827Issue 11-1 en29/04/2008


Contents

2.138 001137 / TCH SEIZ ATT FOR MOC 1372.139 001138 / TCH SEIZ ATT FOR MTC 1382.140 001139 / TCH REL BECAUSE OF RADIO FAIL 1392.141 001140 / TCH REL DUE TO BSS FAIL 1402.142 001141 / TCH SEIZ FAILS DUE TO CONG 1412.143 001142 / QUEUED URGENT HANDOVER ATTEMPTS 1422.144 001143 / AVE QUE TIME OF URGENT HO ATTEMPTS 1432.145 001144 / QUE DENOMINATOR 4 1442.146 001145 / AVE QUE TIME OF NON URGENT HO ATTEMPTS 1452.147 001146 / QUE DENOMINATOR 5 1462.148 001147 / QUEUED URG HO ATTS NOT SERVED 1462.149 001148 / MS SUCC TCH SEIZURE FOR ASSIGNMENT

COMPLETE 1472.150 001149 / CALLS ENDED BY USER DURING DADL/B SETUP 1482.151 001150 / SUCC TCH SEIZ WHEN GOOD QUAL IN ADJACENTS 1492.152 001151 / TCH REQ REJ DUE TO BAD QUALITY IN ADJACENT 1492.153 001152 / SUCC TCH SEIZ WHEN QUAL BETW GOOD AND BAD IN

ADJACENT 1502.154 001153 / TCH REQ REJ WHEN QUAL BETW GOOD AND BAD IN

ADJACENT 1502.155 001154 / DYNAMIC SDCCH RECONFIGURATION ATTEMPT 1512.156 001155 / UNSUCC IMM ASS SDCCH ATTEMPT 1522.157 001156 / HSCSD TCH REQ WITH 14,4 1532.158 001157 / HSCSD SUCC TCH SEIZ WITH 14,4 1532.159 001158 / HSCSD TRANSP TCH REQ 1542.160 001159 / HSCSD SUCC TRANSP TCH SEIZ 1552.161 001160 / HSCSD REQ FOR CALL SETUP 1562.162 001161 / HSCSD TCH REQ FOR HO 1572.163 001162 / HSCSD SUCC TCH SEIZ FOR CALL SETUP 1572.164 001163 / HSCSD SUCC TCH SEIZ FOR HO 1582.165 001164 / HSCSD CON REL DUE TO FAIL 1592.166 001165 / SUCCESS TCH SEIZURE FOR DIRECT ACCESS 1602.167 001166 / TCH REQUEST FOR DIRECT ACCESS REJECTED DUE TO

LACK 1602.168 001167 / TCH REQUEST FOR A BSC CONTROLLED TRHO

PROCEDURE 1612.169 001168 / SUCC TCH SEIZ FOR A BSC CONTROLLED TRHO 1622.170 001169 / REJ TCH SEIZ FOR A BSC CONTROLLED TRHO DUE LACK

OF RESOURCES 1632.171 001170 / SUCCESSFUL TCH SEIZURES FOR DADLB HO 1632.172 001171 / TCH REQUEST IN DADLB HO REJECTED 1642.173 001172 / DADLB START DUE TO EXCEEDED LOAD 1652.174 001173 / REMOVAL FROM QUE DUE TO DR 1652.175 001174 / GPRS TER UPGRD REQ 1662.176 001175 / INCOMPL SERV GPRS TER UPGR REQ 1672.177 001176 / GPRS TER UG REJ DUE CSW TR 1672.178 001177 / GPRS TER UG REJ DUE LACK PSW RES 1682.179 001178 / GPRS TER UG REJ DUE LACK PCU CAP 1692.180 001179 / GPRS TER DG DUE INC IN CSW TR 1692.181 001180 / GPRS TER UG DUE DEC CSW TR 1702.182 001181 / GPRS TER DOWNGRADE REQ 1702.183 001182 / FULL TCH SEIZ INTRA AMR HO 171


29/04/2008


2.184 001183 / HALF TCH SEIZ INTRA AMR HO 1722.185 001184 / TCH CALL REQ FOR AMR 1732.186 001185 / SUCCESSFUL AMR CODEC SET DOWNGRADES 1732.187 001186 / UNSUCCESSFUL AMR CODEC SET DOWNGRADES 1742.188 001187 / SUCCESSFUL AMR CODEC SET UPGRADES 1752.189 001188 / UNSUCCESSFUL AMR CODEC SET UPGRADES 1762.190 001189 / TCH REQ FOR 96 DAT CALL 1762.191 001190 / SUCC TCH SEIZ FOR 96 DAT CALL 1772.192 001191 / SPARE001191 1772.193 001192 / TCH REQUESTS FOR CALL ATTEMPT 1782.194 001193 / SUCCESSFUL TCH SEIZURES FOR CALL ATTEMPT 1782.195 001194 / TCH ACCESS REJECTED DUE LOW RX 1792.196 001195 / MSC O HO CMD 1792.197 001196 / BSC O HO CMD 1802.198 001197 / BTS HO ASSGN 1812.199 001198 / TCH REL DUE TO RADIO FAIL PH 9-11 1812.200 001199 / TCH REL DUE TO BSS FAIL PH 2-3 1822.201 001200 / TCH REL DUE TO BSS FAIL PH 9-11 1832.202 001201 / SDCCH FAIL PH 3 1832.203 001202 / DROP AFTER TCH ASSIGN 1842.204 001203 / ERROR IND DURING LU 1842.205 001204 / DROP TCH ASSCOMPL TO RFCH REL 1852.206 001205 / TCH REL DUE RAD FAIL PH 2-3 1872.207 001206 / TCH REL DUE RAD FAIL PH 12-14 1882.208 001207 / TCH REL DUE BSS FAIL PH 12-14 1882.209 001208 / A IF CRC MISMATCH CALL SETUP 1892.210 001209 / GPRS TER DG REJ DUE STREAMING 1892.211 001210 / GPRS TER DG REQ WHEN EQOS ON 1902.212 001211 / TCH REL BSC BSC CONFLICT CALL 1912.213 001212 / TCH REL BSC BSC CONFLICT TARG 1912.214 001213 / GPRS TER UG REQ FROM CSW 1922.215 001214 / GPRS TER UG FROM CSW PARTIAL 1922.216 001215 / GPRS TER UG FROM CSW FAILED 1932.217 001216 / TCH REQ REJ DUE TO LACK OF RES PER BCSU 1942.218 001217 / INTERNAL TO EXTERNAL HO 1952.219 001218 / NOT CHANGED INTERNAL HO 1952.220 001219 / SPARE001219 1962.221 001220 / SPARE001220 1972.222 001221 / SPARE001221 1972.223 001222 / SPARE001222 1982.224 001223 / SPARE001223 1982.225 001224 / SPARE001224 1992.226 001225 / SPARE001225 1992.227 001226 / SPARE001226 2002.228 001227 / SPARE001227 2002.229 001228 / SPARE001228 2012.230 001229 / SPARE001229 2012.231 001230 / SPARE001230 2022.232 001231 / SDCCH LU ATTEMPTS 2022.233 001232 / SDCCH LU ATTEMPTS FAIL 2032.234 001233 / DROPS AFTER DTM CS TCH ASSIGNMENT 2032.235 001234 / DTM CS TCH DROPS BETWEEN ASSCOMPL AND RFCH REL

DN9813827Issue 11-1 en29/04/2008


Contents

ACK 2042.236 001235 / FORCED RELEASE AFTER FORCED HO 2052.237 001236 / CLASS 2 SUBSCRIBER FORCED RELEASE 2062.238 001237 / TCH REQUESTS FOR CALL ATTEMPT CLASS 1 2062.239 001238 / SUCCESSFUL TCH SEIZURES FOR CALL ATTEMPT CLASS

1 2072.240 001239 / TCH REQUESTS FOR CALL ATTEMPT CLASS 2 2082.241 001240 / SUCCESSFUL TCH SEIZURES FOR CALL ATTEMPT CLASS

2 2082.242 001241 / TCH REQUESTS FOR CALL ATTEMPT CLASS 3 2092.243 001242 / SUCCESSFUL TCH SEIZURES FOR CALL ATTEMPT CLASS

3 2102.244 001243 / DR TRAU DOWNGRADE ATTEMPTED IN AMR HO 2102.245 001244 / DR TRAU DOWNGRADE ATTEMPT FAILED 2112.246 001245 / DR TRAU UPGRADE ATTEMPTED IN AMR HO 2122.247 001246 / DR TRAU UPGRADE ATTEMPT FAILED 2122.248 001247 / SEIZURE IN AMR FR TO HR HO 2132.249 001248 / SEIZURE IN AMR HR TO FR HO 2132.250 001249 / INTERNAL AMR HO TO EXTERNAL 2142.251 001250 / SUCCESSFUL LRTCH SEIZURES 215

3 Signalling charts of Traffic Measurement 217

4 Signalling charts of Dual Transfer Mode 297


29/04/2008


List of tables

Table 1. Measurement description of Traffic Measurement 17

Table 2. SDCCH attempts counters 17

Table 3. SDCCH success counters 18

Table 4. SDCCH failure counters 18

Table 5. TCH requests and attempts counters 19

Table 6. TCH success counters 21

Table 7. TCH failure counters 22

Table 8. Other counters 25

Table 9. GPRS counters 26

Table 10. Spare counters 27

DN9813827Issue 11-1 en29/04/2008


List of tables

List of figures

Figure 1. Basic call without counters 218

Figure 2. Basic call with counters 219

Figure 3. Basic call with priority subscriber 220

Figure 4. FACCH call setup due to SDCCH congestion without counters 221

Figure 5. FACCH call setup due to SDCCH congestion with counters 222

Figure 6. FACCH call setup due to SDCCH congestion, no free TCH channel.Optional software directed retry is not activated 223

Figure 7. Normal release 224

Figure 8. Basic call, no free TCH and queuing or directed retry is not allowed 225

Figure 9. Successful TCH queuing 226

Figure 10. Basic call, no free TCHs, unsuccessful queuing and directed retry notactivated 227

Figure 11. TCH assignment failure due to MSC's inability to switch circuit pool 228

Figure 12. Unsuccessful TCH activation 229

Figure 13. Unsuccessful TCH activation, timer expires while waiting forCHANNEL_ACTIVATION_ACK message 230

Figure 14. TCH assignment failure 231

Figure 15. TCH assignment failure, MSC sends CLEAR_COMMAND message 232

Figure 16. CONNECTION_FAILURE message with cause transcoder_failure duringa call 233

Figure 17. TRX or TSL is blocked with different causes during a call 234

Figure 18. SDCCH congestion, FACCH call setup is not activated 235

Figure 19. Unsuccessful SDCCH activation 236

Figure 20. Unsuccessful SDCCH activation, timer expires while waiting forCHANNEL_ACTIVATION_ACK message 237

Figure 21. Connection failure during SDCCH assignment 238

Figure 22. SDCCH assignment failure 239

Figure 23. Unsuccessful SDCCH activation, timer expires while waiting forPHYSICAL_CONTEXT_CONFIRM message 240

Figure 24. TRX/TSL is blocked with different causes during an SDCCH channelactivation 241


29/04/2008


Figure 25. Successful trunk reservation. Counters updated: 001040, 001041 andbasic call counters, see Figure 2. 242

Figure 26. Unsuccessful trunk reservation 243

Figure 27. Successful internal intra-cell handover. Counters 001090 and 001091 areupdated only with underlay overlay handover. 244

Figure 28. Internal intra-cell handover, successful TCH queuing 245

Figure 29. Unsuccessful internal intra-cell handover, timer expires while waiting forCHANNEL_ACTIVATION_ACK message 247

Figure 30. Unsuccessful internal intra-cell handover, CONNECTION_FAILUREmessage with cause remote_transcoder_failure comes to the targetchannel 248

Figure 31. Unsuccessful internal intra-cell handover, timer expires on the sourcechannel, call cleared 249

Figure 32. Unsuccessful underlay overlay internal intra-cell handover, queuing notallowed 250

Figure 33. Internal intra-cell handover, unsuccessful TCH queuing 251

Figure 34. Internal directed retry 253

Figure 35. Successful internal inter-cell handover 254

Figure 36. Unsuccessful internal inter-cell handover 255

Figure 37. Successful external handover, target 256

Figure 38. Successful external handover, source 257

Figure 39. Unsuccessful external handover, source BSC, timer expires while waitingfor CLEAR_COMMAND message 258

Figure 40. Unsuccessful external handover, MS sends a handover failure 259

Figure 41. Successful traffic reason handover, source 260

Figure 42. Successful SDCCH internal intra-cell handover 261

Figure 43. Unsuccessful SDCCH internal intra-cell handover, timer expires whilewaiting for CHANNEL_ACTIVATION_ACK message 262

Figure 44. Unsuccessful SDCCH internal intra-cell handover, unsuccessful channelactivation 263

Figure 45. Unsuccessful SDCCH internal intra-cell handover,CONNECTION_FAILURE message comes to the target channel duringhandover 264

Figure 46. Successful SDCCH internal inter-cell handover 265

Figure 47. Unsuccessful SDCCH internal inter-cell handover, BTS sends

DN9813827Issue 11-1 en29/04/2008


List of figures

CONNECTION_FAILURE message 266

Figure 48. Successful SDCCH external handover target 267

Figure 49. Successful SDCCH external handover source. No countersupdating. 267

Figure 50. Unsuccessful SDCCH external handover, timer expires while waiting forCLEAR_COMMAND message 268

Figure 51. Successful forced release 269

Figure 52. Unsuccessful forced release 270

Figure 53. Unsuccessful forced release with external handover 271

Figure 54. Successful forced handover 272

Figure 55. Unsuccessful forced handover 273

Figure 56. Unsuccessful forced handover with external handover 274

Figure 57. Reconfiguration from TCH to SDCCH 275

Figure 58. Normal call 276

Figure 59. Mobile originated HSCSD call setup 277

Figure 60. Successful internal inter-cell handover for HSCSD, target cell allocationsand activations for three channels 278

Figure 61. A CONNECTION_FAILURE message which comes during anHSCSD 279

Figure 62. Internal intra-cell direct access from a regular DCCH to the super-reuseTRX. Optional software direct access to super-reuse TRX in IUOactivated. 280

Figure 63. Unsuccessful internal intra-cell direct access from regular DCCH to thesuper-reuse TRX due to lack of resources. Optional software directaccess to super-reuse TRX in IUO activated. 281

Figure 64. Timer T3107 expires while waiting for ASSIGNMENT_COMPLETEmessage 282

Figure 65. Average counter updating 283

Figure 66. Successful handover due to DADL/B 283

Figure 67. Unsuccessful DADL/B handover due to lack of resources 284

Figure 68. Successful BSC controlled TRHO 284

Figure 69. Unsuccessful BSC controlled TRHO 285

Figure 70. Dropped call between ASSIGNMENT COMPLETE andDISCONNECT 286


29/04/2008


Figure 71. Dropped call between ASSIGNMENT COMPLETE and RF CHANNELRELEASE ACK 287

Figure 72. Circuit pool switching during call setup, chart 1/2 288

Figure 73. Circuit pool switching during call setup, chart 2/2 289

Figure 74. AMR packing or unpacking handover 290

Figure 75. Successful handover type reselection from an internal inter-cell TCH toTCH handover to an external handover due to switching the circuitpool 291

Figure 76. Internal inter-cell handover change to external handover due to circuit poolswitching, target-cell 292

Figure 77. Internal intra-cell handover change to external due to circuit poolswitching, source side 293

Figure 78. Internal intra-cell handover change to external due to circuit poolswitching, target side 294

Figure 79. Circuit pool switch during inter-system handover, target-BSC 295

Figure 80. Circuit pool switch during external handover, target-BSC 296

Figure 81. MO DTM call establishment 298

Figure 82. MT DTM call establishment 299

Figure 83. DTM call reallocation; too high CS connection interference 300

Figure 84. DTM call reallocation; inadequate PS connection quality 301

Figure 85. DTM call; internal inter-cell handover; CS connection power budget 302

Figure 86. DTM call; internal inter-cell handover; lack of resources in the PSterritory 303

Figure 87. DTM call; external handover, source BSC 304

Figure 88. DTM call; external handover, target BSC 305

Figure 89. DTM call release initiated by the MS 306

Figure 90. DTM call release; packet data transfer end 307

Figure 91. DTM REQUEST rejected when IMSI data not available 308Figure 92. Unsuccessful MO DTM; activation of a CS TCH in the PS territory fails,

timer expires while waiting for CHANNEL ACTIVATION ACK 309

Figure 93. Unsuccessful MT DTM; activation of a CS TCH in the PS territory fails,timer expires while waiting for CHANNEL ACTIVATION ACK 310

Figure 94. Unsuccessful MT DTM; DTM ASSIGNMENT FAILURE received 311

DN9813827Issue 11-1 en29/04/2008


List of figures

Figure 95. Timer T3107 expires while waiting for ASSIGNMENT COMPLETE 312

Figure 96. DTM call reallocation failure; DTM ASSIGNMENT FAILURE received 313

Figure 97. DTM CS connection drops after ASSIGNMENT COMPLETE;CONNECTION FAILURE received 314

Figure 98. DTM CS connection drops after ASSIGNMENT COMPLETE; RELEASEINDICATION not received 315

Figure 99. Unsuccessful DTM call reallocation; timer T3107 expires while waiting forASSIGNMENT COMPLETE 316

Figure 100.DTM TBF assignment failure; UL RLC block not received 317

Figure 101.DTM-capable MS paging 318


29/04/2008


Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument issue contains all changes made to previous issues.

Changes made between issues 11-1 and 11-0

Counters 001182 and 001183: information on when the counter is updatedhas been moved from Description to the Updated field.

Counter 001236: minor editorial change in the Updated field.

Nine new signalling charts added in section Signalling charts of TrafficMeasurement: Figures 72-80. The name of Figure 11 changed to TCHassignment failure due to MSC's inability to switch circuit pool.


New counters 001235 - 001242 related to BSS20869: Market ExpansionToolkit added.

New counters 001243 - 001249 related to BSS20588: TRAU Bicasting inAMR FR/HR Handover added.

New counter 001250 related to BSS21274: Long Reach TSL (Flexi EDGEBTS) added.

Object level information updated in chapter 1.

Counter table format changed.

The signalling chart 'TCH assignment failure, MSC sendsCLEAR_COMMAND message' updated.

Signalling charts of Dual Transfer Mode updated. For detailed informationon the updates, see Summary of changes in 106 CS DTM Measurement.

DN9813827Issue 11-1 en29/04/2008


Summary of changes


New counters 001231 001234 added. Spare counters 001192, 001193,001217 and 001218 changed to real counters. Counters 001184, 001196,001198, 001199, and 001204 001207 modified.

Counters 001150 001153 changed to be no longer in use and signallingchart 66 removed because Dynamic Hot Spot is no longer supported.

Counters 001209 and 001210 changed to be not in use becauseEnhanced Quality of Service is not supported in S12. Enhanced Quality ofService will be available in S13.

New signalling charts 70 and 71 added, and signalling charts 13, 15, 16,17, 27, 29, 34, 35, 38, 42, 46, and 64 updated in Chapter 3.

Signalling charts of Dual Transfer Mode,which contains some signallingcharts related to counters 001233 and 001234, has been added.

Editorial changes made.


29/04/2008


1 1 Traffic MeasurementThe BSC traffic measurement registers information related to the standalone dedicated control channel (SDCCH) and traffic channels (TCH). TheBSC traffic measurement counters are divided into seven different classes.There are counters regarding the number of attempts to seize TCHs andSDCCHs, successful calls, lengths of the queue, and the reasons forfailures. This measurement collects one set of results for each BTS.Signalling charts are drawn with the accuracy of message interface.

Measurement description

Table 1. Measurement description of Traffic Measurement

Measurement

Measurement ID

Measurement abbreviation

Traffic Measurement

1

TRAFFIC

Product BSC

Product software release S1

Target name BTS

Measurement counters

. SDCCH attempts counters

Table 2. SDCCH attempts counters

Counter Counter number

Seizure attempts 001000

SDCCH seizure attempts for MOC 001135

SDCCH seizure attempts for MTC 001136

DN9813827Issue 11-1 en29/04/2008



Table 2. SDCCH attempts counters (cont.)


Dynamic SDCCH reconfiguration attempt 001154

SDCCH LU attempts 001231

. SDCCH success counters

Table 3. SDCCH success counters


Success seizure for HO 001006

Success seizure for immediate assignment 001007

. SDCCH failure counters

Table 4. SDCCH failure counters


Seizure attempts with busy SDCCH 001001

Transactions failed due to BSS failure 001002

Transactions failed due to radio failure 001003

Transact. failed due radio on source channel duringHO

001004

Transact. failed due radio on target channel duringHO

001005

SDCCH activation failure 001027

SDCCH Abis problems 001033

SDCCH A interface problems 001034

SDCCH LAPD failure 001035

SDCCH BTS failure 001036

SDCCH user actions 001037

SDCCH BCSU reset 001038

SDCCH network actions 001039

SDCCH activation failure call 001072

SDCCH activation failure target 001074


29/04/2008


Table 4. SDCCH failure counters (cont.)


SDCCH Abis failure call 001075

SDCCH Abis failure source 001076

SDCCH Abis failure target 001077

SDCCH A interface failure call 001078

SDCCH A interface failure source 001079

SDCCH A interface failure target 001080

Unsuccess immediate assignment SDCCH attempt 001155

SDCCH failures in phase 3 001201

Error indication messages during Location Update 001203

SDCCH LU attempts fail 001232

. TCH requests and attempts counters

Table 5. TCH requests and attempts counters


TCH request success and unsuccess 001010

Call attempts in the queue 001016

Handover attempts in the queue 001017

TCH call request 001026

Trunk reservation invocations 001040

TCH requests FACCH call setup 001043

Traffic reason HO requests 001052

Traffic reason HO enquiries 001053

Forced release assign request attempts 001054

Forced HO assign request attempts 001055

Queuing allowed assign request attempts 001056Queuing not allowed assign request attempts 001057Forced release HO request attempts 001062

Forced HO HO request attempts 001063

Queuing allowed HO request attempts 001064Queuing not allowed HO request attempts 001065

DN9813827Issue 11-1 en29/04/2008



Table 5. TCH requests and attempts counters (cont.)


TCH requests underlay overlay 001090

TCH seizure underlay overlay 001091

Priority subscriber TCH requests 001095

TCH seizure attempt due SDCCH congestion 001098

Full TCH requests success unsuccess 001102

Half TCH requests success unsuccess 001103

TCH requests full preferred 001104

TCH requests half preferred 001105

Full TCH requests FACCH call 001123

TCH FACCH call channel rate not defined 001124

TCH seizure attempts for MOC 001137

TCH seizure attempts for MTC 001138

Queued urgent handover attempts 001142TCH requests for 14.4k data calls 001156

HSCSD transparent TCH request 001158

HSCSD request for call setup 001160

HSCSD TCH request for HO 001161

TCH request for a BSC controlled TRHO procedure 001167

DADLB start due to exceeded load 001172

TCH requests for AMR call 001184

TCH requests for 9.6k data calls 001189

TCH requests for call attempt 001192

HO commands in outgoing MSC-controlled handover 001195

HO commands in outgoing BSCcontrolled handover 001196

Assignment commands in intra-BTS handover 001197

TCH requests for call attempt class 1 001237



. TCH success counters


29/04/2008


Table 6. TCH success counters


Success TCH seizure for HO 001008

Success TCH seizure for normal assignment 001009

Success trunk reservation invocations 001041

TCH seizure FACCH call setup 001044

Forced releases 001070

Forced handovers 001071

Priority subscriber success TCH seizure 001096

TCH seizure due SDCCH congestion 001099

Success full TCH seizure 001106

Success half TCH seizure 001107

Full TCH seizure speech ver 1 001108



Half TCH seizure speech ver 1 001111



Full TCH seizure normal assignment 001114

Half TCH seizure normal assignment 001115

Full TCH seizure internal HO channel rate 001116

Half TCH seizure internal HO channel rate 001117

Success full TCH seizure FACCH call 001125

Success half TCH seizure FACCH call 001126

MS success TCH seizure for assignment complete 001148

Calls ended by user during DADL/B setup 001149

Success TCH seizure when good quality in adjacents 001150Succ TCH seiz when qual betw good and bad in adj 001152HSCSD success TCH seizure with 14.4 001157

HSCSD success transparent TCH seizure 001159

HSCSD success TCH seizure for call setup 001162

HSCSD success TCH seizure for HO 001163

Success TCH seizure for direct access 001165

Succ TCH seiz for a controlled TRHO 001168

DN9813827Issue 11-1 en29/04/2008



Table 6. TCH success counters (cont.)


Successful TCH seizures for DADLB HO 001170

Removal from queue due to DR 001173

Successful FR TCH seizures with AMR codecs forHO

001182

Successful HR TCH seizures with AMR codecs forHO

001183

Successful TCH seizures for call attempt 001193

Successful TCH seizures for call attempt class1 001238



Seizure in AMR FR to HR HO 001247

Seizure in AMR HR to FR HO 001248

Successful LRTCH seizures 001250

. TCH failure counters

Table 7. TCH failure counters


TCH request rejected due to lack 001011Transactions ended due to BSS problem 001012

Transactions ended due to radio failure 001013

Transact. ended due source channel failure duringHO

001014

Transact. ended due target channel failure during HO 001015

Not served queued call attempts 001024

Not served queued HO attempts 001025

TCH activation failure 001028

TCH transcoder failure 001029

TCH transcoder failure source 001030

TCH transcoder failure target 001031

Trunk reservation invocations result refused 001042

TCH Abis problems 001045


29/04/2008


Table 7. TCH failure counters (cont.)


TCH LAPD failure 001046

TCH BTS failure 001047

TCH user actions 001048

TCH BCSU reset 001049

TCH network actions 001050

TCH A interface problems 001051

Forced release assign request failed 001058

Forced HO assign request failed 001059

Queuing allowed assign request failed 001060Queuing not allowed assign request failed 001061Forced release HO request failed 001066

Forced HO HO request failed 001067

Queuing allowed HO request failed 001068Queuing not allowed HO request failed 001069TCH activation failure call 001081

TCH activation failure target 001083

TCH Abis failure call 001084

TCH Abis failure source 001085

TCH Abis failure new 001086

TCH A interface failure call 001087

TCH A interface failure source 001088

TCH A interface failure new 001089

TCH rejected requests underlay overlay 001092Non-priority subscriber refused TCH requests 001097

Trunk TCH rejected FR requests 001100Trunk TCH rejected HR requests 001101Rejected TCH requests due lack FR 001118Rejected TCH requests due lack HR 001119Full TCH rejected requests due HR traffic 001120Half TCH rejected requests due FR traffic 001121TCH rejected due requested channel A interfacecircuit

001122

Ended due transcoder FR rate 1 001127

DN9813827Issue 11-1 en29/04/2008







Ended due transcoder HR rate 1 001130



Full TCH transaction failures 001133

Half TCH transaction failures 001134

TCH release due to radio failure 001139

TCH release due to BSS failure 001140

TCH seizure failure due to congestion 001141

Queued urgent HO attempts not served 001147TCH request rejected due to bad quality in adjacents 001151TCH req rej when qual betw good and bad in adj 001153HSCSD connection releases due to failure 001164

TCH request for direct access rejected due to lack 001166Rej TCH seiz for BSC contr TRHO due lack of res 001169TCH request in DADLB HO rejected 001171TCH drop due to too low RX level 001194

TCH releases due to radio failures, updated inphases 9-11

001198

TCH releases due to BSS failures, updated in phases2-3

001199

TCH releases due to BSS failures, updated in phases9-11

001200

Dropped calls after TCH assignment 001202

Number of TCH drops between Assignment Completeand RF Channel Release messages

001204

Number of TCH releases due to radio failures,updated only in phases 2-3

001205

Number of TCH releases due to radio failures,updated only in phases 12-14

001206

Number of TCH releases due to BSS failures,updated only in phases 12-14

001207

001208


29/04/2008




Number of TCH requests rejected due to themismatch between the types of the requestedchannel and the A interface circuit, updated only incall setup phase

Number of TCH releases due to BSC-BSC conflict incall setup

001211

Number of TCH releases due to BSC-BSC conflict fortarget channel

001212

Number of TCH requests rejected due to lack ofresources per BCSU

001216

Drops after DTM CS TCH assignment 001233

DTM CS TCH drops between ASSCOMPL and RFCHREL ACK

001234

. Other counters

Table 8. Other counters


Average queue length for channel seizure request 001018

Queue denominator 1 001019Average queue time of call attempts 001020

Queue denominator 2 001021Average queue time of HO attempts 001022

Queue denominator 3 001023Not relevant 001032

Not relevant 001073

Not relevant 001082

Successful MOC test call 001093

Unsuccessful MOC test call 001094

Average queuing time of urgent HO attempts 001143

Queue denominator 4 001144Average queuing time of non-urgent HO attempts 001145

Queue denominator 5 001146Successful AMR codec set downgrades 001185

DN9813827Issue 11-1 en29/04/2008



Table 8. Other counters (cont.)


Unsuccessful AMR codec set downgrades 001186

Successful AMR codec set upgrades 001187

Unsuccessful AMR codec set upgrades 001188

Internal to external HO 001217

Not changed internal HO 001218

Forced release after forced HO 001235

Class 2 subscriber forced release 001236

DR TRAU downgrade attempted in AMR HO 001243

DR TRAU downgrade attempt failed 001244

DR TRAU upgrade attempted in AMR HO 001245

DR TRAU upgrade attempt failed 001246

Internal AMR HO to external 001249

. GPRS counters

Table 9. GPRS counters


GPRS territory upgrade requests 001174

Incompletely served GPRS territory upgrade requests 001175

GPRS upgrade requests rejected due to CSW traffic 001176GPRS upgrade requests rejected due to lack of PSW 001177GPRS upgrade requests rejected due to to lack ofPCU

001178

GPRS downgrades due to increase in CSW traffic 001179

GPRS upgrades due to decrease in CSW traffic 001180

GPRS territory downgrade requests 001181

GPRS territory downgrade rejected due to streamingtraffic

001209

GPRS territory downgrade rejected due to need ofCS resources.

001210

Number of GPRS territory upgrade requestes fromCSW

001213

001214


29/04/2008


Table 9. GPRS counters (cont.)


Number of GPRS territory upgrade requests fromCSW, partially successful

Number of GPRS territory upgrade requests fromCSW, failed

011215

. Spare counters

Table 10. Spare counters


Spare001191 001191

Spare001219 001219

Spare001220 001220

Spare001221 001221

Spare001222 001222

Spare001223 001223

Spare001224 001224

Spare001225 001225

Spare001227 001227

Spare001228 001228

Spare001229 001229

Spare001230 001230

Related topics

. Counters of Traffic Measurement

. Signalling charts of Traffic Measurement

. Signalling charts of Dual Transfer Mode

Instructions

. BSC Statistics Administration

DN9813827Issue 11-1 en29/04/2008



For information on using this measurement to test the activation ofrelated software, see the testing instructions in:

. Activating and Testing BSS6071: EFR

. Activating and Testing BSS6115: Half Rate

. Activating and Testing BSS7003 and BSS7037: HSCSD and 14.4kbit/s Data Services

. Activating and Testing BSS7036: Dynamic SDCCH

. Activating and Testing BSS9006: GPRS

. Activating and Testing BSS10004: AMR

. Activating and Testing BSC3910: Pre-emption and BSS20869:Market Expansion Toolkit

. Activating and Testing BSS21274: Long Reach TSL (Flexi EDGEBTS)

Reference

. BSC Measurement Counters Displaying Program (FOXMEA)

. Performance Measurements

Descriptions

. Advanced Multilayer Handling

. Direct Access to Desired Layer/Band

. Directed Retry in BSC

. Dual Transfer Mode in BSC

. Dynamic Abis

. Dynamic Frequency and Channel Allocation in BSC

. Dynamic SDCCH in Radio Channel Allocation

. GPRS/EDGE System Feature Description

. Enhanced Coverage by Frequency Hopping

. Enhanced Speech Codecs: AMR and EFR

. Extended Cell Range

. FACCH Call Set-up


29/04/2008


. Half Rate in BSC

. Handover Support for Coverage Enhancements

. HSCSD and 14.4 kbit/s Data Services in BSC

. Intelligent Underlay-Overlay

. Multi BCF Control in BSC

. Radio Resource Pre-emption and Queuing in BSC

. Traffic Reason Handover in BSC

. Trunk Reservation

DN9813827Issue 11-1 en29/04/2008




29/04/2008


2 Counters of Traffic Measurement2.1 001000 / SEIZURE ATTEMPTS

Counter ID: 001000 Network element name: SEIZURE ATTEMPTS

Version: 2.1 NetAct name: SDCCH_SEIZ_ATT

Description: Number of times when an MS attempts to seize an SDCCH.

Updated: When the RRM receives requests for SDCCH from an MS as the MS needs a channel foreither a call or a HO.

See figures:- Basic call with counters- FACCH call setup due to SDCCH congestion with counters- FACCH call setup due to SDCCH congestion, no free TCH channel- SDCCH congestion, FACCH call setup is not activated- Successful SDCCH internal intra-cell handover- Successful SDCCH internal inter-cell handover- Successful SDCCH external handover target- Reconfiguration from TCH to SDCCH

Logical type: Sum Trigger type: Event Sampling interval:

Unit: Integer number Range: Example values:

Dependencies with other counters:

Operability class:

Related to feature: Related to standard:

3GPP Measurement name (Clause header):3GPP Measurement type:

Exceptions to related standard:

Used from release: S1 Definition updated in release:

DN9813827Issue 11-1 en29/04/2008


Counters of Traffic Measurement

2.2 001001 / SEIZURE ATTEMPTS WITH BUSY SDCCH

Counter ID: 001001 Network element name: SEIZURE ATTEMPTS WITH BUSYSDCCH

Version: 2.1 NetAct name: SDCCH_BUSY_ATT

Description: Number of times when an MS attempts to seize an SDCCH but the attempt isunsuccessful because all SDCCHs are busy. This counter does not necessarily mean that the callattempt is lost, because the call may be established as an FACCH call setup using TCH instead ofSDCCH. This counter is not triggered when the TCH reconfiguration is attempted because of dynamicSDCCH allocation. If the attempt fails, the SDCCH_busy_attempt is triggered together with 1155UNSUCC_IMM_ASS_SDCCH_ATTEMPT.

Updated: When the RRM has no SDCCHs to allocate for a call or HO attempts.

See figures:- FACCH call setup due to SDCCH congestion with counters- FACCH call setup because of SDCCH congestion- SDCCH congestion, FACCH call setup is not activated




Operability class:

Related to feature:

BSS20003: CS Statistics Enhancements

Related to standard:




2.3 001002 / TRANSACTIONS FAIL DUE TO BSS FAIL

Counter ID: 001002 Network element name: TRANSACTIONS FAIL DUE TOBSS FAIL

Version: 2.1 NetAct name: SDCCH_BSS_FAIL

Description: Number of SDCCH transactions ended because of a BSS failure.

Impact: See field descriptions of the counters 001033, 001034, 001035, and 001036.


29/04/2008


Updated: When one of the counters 001033, 001034, 001035, or 001036 is updated. This counterrepresents their sum.

See figures:- Unsuccessful SDCCH activation, timer expires while waiting for CHANNEL_ACTIVATION_ACKmessage- SDCCH assignment failure- Unsuccessful SDCCH activation, timer expires while waiting for PHYSICAL_CONTEXT_CONFIRMmessage- TRX/TSL is blocked with different causes during an SDCCH channel activation- Unsuccessful SDCCH internal intra-cell handover, timer expires while waiting forCHANNEL_ACTIVATION_ACK message- Unsuccessful SDCCH external handover, timer expires while waiting for CLEAR_COMMANDmessage




Operability class:





2.4 001003 / TRANSACTIONS FAIL DUE TO RADIOFAIL

Counter ID: 001003 Network element name: TRANSACTIONS FAIL DUE TORADIO FAIL

Version: 2.1 NetAct name: SDCCH_RADIO_FAIL

Description: Number of SDCCH transactions ended because of a radio failure.

Impact: Call cleared

Reason for the Impact: External / Abis Interface

Updated: When an SDCCH transaction ends because of a radio failure (radio link timeout) and theRRM releases the SDCCH.

This counter is updated in call phases 1-8 only.

See figures:- TCH assignment failure- Connection failure during SDCCH assignment

DN9813827Issue 11-1 en29/04/2008






Operability class:





2.5 001004 / TRANSACTIONS FAIL DUE RADIO ONSOURCE CHANNEL DURING HO

Counter ID: 001004 Network element name: TRANSACTIONS FAIL DUE RADIOON SOURCE CHANNEL DURING HO

Version: 2.1 NetAct name: SDCCH_RF_OLD_HO

Description: Number of SDCCH transactions ended because of a radio failure on the source channelduring a handover between SDCCH-SDCCH or SDCCH-TCH.

It is this counter in the source cell that is updated. If the target cell lies within the same BSC, alsocounter 001005 in the target cell is updated along with this counter.

Impact: HO failure and call cleared

Updated: When an SDCCH transaction ends because of a radio failure (HO failure) on the sourcechannel during a handover attempt and the RRM releases the SDCCH.


See figure Unsuccessful SDCCH internal inter-cell handover, BTS sends CONNECTION_FAILUREmessage.




001005: TRANSACTIONS FAIL DUE RADIO ON TARGET CHANNEL

Operability class:


3GPP Measurement name (Clause header):


29/04/2008


3GPP Measurement type:



2.6 001005 / TRANSACTIONS FAIL DUE RADIO ONTARGET CHANNEL

Counter ID: 001005 Network element name: TRANSACTIONS FAIL DUE RADIOON TARGET CHANNEL

Version: 2.1 NetAct name: SDCCH_RF_NEW_HO

Description: Number of SDCCH transactions ended because of a radio failure on the target channelduring an SDCCH HO.

Impact: HO failure, the call may possibly be cleared

Reason for the impact: Since the MS cannot access the target channel, a radio failure occurs. Theunsuccessful seizure may have been caused by a missing indication of call establishment, missingdetection of HO, missing indication of the HO completed, or corrupted messages related to the HO.

Updated: When an SDCCH transaction ends because of a radio failure on the target channel during ahandover attempt and the RRM releases the SDCCH.


See figure Unsuccessful SDCCH internal intra-cell handover, CONNECTION_FAILURE messagecomes to the target channel during handover.




Operability class:





DN9813827Issue 11-1 en29/04/2008



2.7 001006 / SUCCESS SEIZURE FOR HO

Counter ID: 001006 Network element name: SUCCESS SEIZURE FOR HO

Version: 2.1 NetAct name: SDCCH_HO_SEIZ

Description: Number of successful SDCCH seizures for a handover.

Updated: When the RRM allocates an SDCCH as a response to an SDCCH request in a handoverattempt.

See figures:- Successful SDCCH internal intra-cell handover- Successful SDCCH internal inter-cell handover- Successful SDCCH external handover target




Operability class:





2.8 001007 / SUCCESS SEIZURE FOR IMMEDIATEASSIGNMENT

Counter ID: 001007 Network element name: SUCCESS SEIZURE FORIMMEDIATE ASSIGNMENT

Version: 2.1 NetAct name: SDCCH_ASSIGN

Description: Number of successful seizures of SDCCH for an immediate assignment.

Updated: When the RRM allocates an SDCCH for an immediate assignment in a call attempt.

See figures:- Basic call with counters- Reconfiguration from TCH to SDCCH





29/04/2008


Operability class:





2.9 001008 / SUCCESS TCH SEIZURE FOR HO

Counter ID: 001008 Network element name: SUCCESS TCH SEIZURE FOR HO

Version: 2.1 NetAct name: TCH_HO_SEIZ

Description: Number of successful requests for a TCH in a handover.

Updated: When the RRM allocates a TCH as a response to a TCH request in a handover attempt.The channel is reserved by the RRM, but the success of the HO is not known in this phase.

See figures:- Successful internal intra-cell handover- Internal intra-cell HO, successful TCH queuing- Successful internal inter-cell handover- Successful external handover, target




Operability class:





2.10 001009 / SUCCESS TCH SEIZURE FOR NORMALASSIGNMENT

Counter ID: 001009 Network element name: SUCCESS TCH SEIZURE FORNORMAL ASSIGNMENT

DN9813827Issue 11-1 en29/04/2008



Version: 2.1 NetAct name: TCH_NORM_SEIZ

Description: Number of successful requests for a TCH in a normal assignment.

Updated: When the RRM allocates a TCH as a response to a TCH request in a call attempt.

See figures:- Basic call with counters- Basic call with priority subscriber- Successful TCH queuing- Successful forced release- Successful forced handover




Operability class:





2.11 001010 / TCH REQUEST SUCCESS ANDUNSUCCESS

Counter ID: 001010 Network element name: TCH REQUEST SUCCESS ANDUNSUCCESS

Version: 2.1 NetAct name: TCH_REQUESTDescription: Total number of requests for a TCH (successful and unsuccessful).Updated: When the RRM receives a request for a TCH either in a call or a handover attempt.

See figures:- Basic call with counters- Basic call with priority subscriber- FACCH call setup due to SDCCH congestion with counters- FACCH call setup because of SDCCH congestion- Basic call, no free TCH and queuing or directed retry is not allowed- Successful TCH queuing- Basic call, no free TCHs, unsuccessful queuing and directed retry not activated- TCH assignment failure with cause switch_circuit_pool, queuing and directed retry not allowed- Unsuccessful trunk reservation- Successful internal intra-cell handover- Internal intra-cell HO, successful TCH queuing- Unsuccessful underlay overlay internal intra-cell handover, queuing not allowed


29/04/2008


- Internal intra-cell handover, unsuccessful TCH queuing- Internal directed retry- Successful internal inter-cell handover- Successful external handover, target- Successful forced release- Unsuccessful forced release- Unsuccessful forced release with external handover- Successful forced handover- Unsuccessful forced handover- Unsuccessful forced handover with external handover




Operability class:





2.12 001011 / TCH REQUEST REJECTED DUE TO LACK

Counter ID: 001011 Network element name: TCH REQUEST REJECTED DUETO LACK

Version: 2.1 NetAct name: TCH_REQ_REJ_LACKDescription: Number of requests for TCHs that are rejected because there are no radio resourcesavailable. This counter is also updated when a request for TCH is rejected because of a mismatchbetween the types of the requested channel and the A interface circuit.

See also counter 004079.

Updated: When the RRM has no TCHs available for either call or HO attempt requests, or the RRMchanges the A interface circuit pool before the TCH allocation. This counter may be updatedimmediately after a TCH request or, in case of queuing, when the queuing timer expires.

NOTE! In case of DR this counter is updated as follows:

1) When a call is removed from the queue because of a DR attempt, this counter is NOT updated onthe SOURCE side, instead counter 001173 is updated.2) If queuing is not used or the queuing timer expires before a DR attempt, this counter is updated onthe SOURCE side.3) On the TARGET side, this counter is updated in case of congestion (blocking).

See figures:- Basic call without counters

DN9813827Issue 11-1 en29/04/2008



- Basic call, no free TCHs, unsuccessful queuing and directed retry not activated- TCH assignment failure with cause switch_circuit_pool, queuing and directed retry not allowed- Unsuccessful underlay overlay internal intra-cell handover, queuing not allowed- Internal intra-cell handover, unsuccessful TCH queuing- Unsuccessful forced release- Unsuccessful forced release with external handover- Unsuccessful forced handover




004079: CAUSE DIR RETRY

Operability class:




Used from release: S1 Definition updated in release: S11

2.13 001012 / TRANSACTIONS ENDED DUE TO BSSPROBLEM

Counter ID: 001012 Network element name: TRANSACTIONS ENDED DUE TOBSS PROBLEM

Version: 2.1 NetAct name: TCH_BSS_FAIL

Description: Number of TCH transactions ended because of BSS problems.

Impact: See descriptions of counters 001045, 001046, 001047 and 001051.

Updated: When one of the counters 001045, 001046, 001047, or 001051 is updated. This counterrepresents their sum.

See figures:- Unsuccessful TCH activation, timer expires while waiting for CHANNEL_ACTIVATION_ACK message- TCH assignment failure, MSC sends CLEAR_COMMAND message- TRX or TSL is blocked with different causes during a call- Unsuccessful internal intra-cell handover, timer expires while waiting forCHANNEL_ACTIVATION_ACK message- Unsuccessful external handover, source BSC, timer expires while waiting for CLEAR_COMMANDmessage- Unsuccessful external handover, MS sends a handover failure- Dropped call between ASSIGNMENT COMPLETE and DISCONNECT


29/04/2008





Operability class:





2.14 001013 / TRANSACTIONS ENDED DUE RADIO FAIL

Counter ID: 001013 Network element name: TRANSACTIONS ENDED DUERADIO FAIL

Version: 2.1 NetAct name: TCH_RADIO_FAIL

Description: Number of TCH transactions ended because of a radio failure.


Updated: When a TCH transaction ends because of a radio failure and the RRM releases the TCH.This counter is typical in connection with coverage problems. ERROR INDICATION is sent by the BTSto the BSC in the following cases:- Sequence error in a received message (the case where retransmission is not possible).- Timer T200 has expired N200 +1 times (MS does not respond any more).- Unsolicited DM response when link is established.

This counter is updated in call phases 1-8 or 15 only.

See figures:- Timer T3107 expires while waiting for ASSIGNMENT_COMPLETE message- Dropped call between ASSIGNMENT COMPLETE and DISCONNECT




Operability class:




Used from release: S1 Definition updated in release: S11

DN9813827Issue 11-1 en29/04/2008



2.15 001014 / TRANSACTIONS ENDED DUE SOURCECHANNEL FAIL DURING HO

Counter ID: 001014 Network element name: TRANSACTIONS ENDED DUESOURCE CHANNEL FAIL DURING HO

Version: 2.1 NetAct name: TCH_RF_OLD_HO

Description: Number of TCH transactions ended because of a radio failure on the source channelduring a handover attempt.


Updated: When a TCH transaction ends because of a radio failure (HO failure) on the source channelduring a handover attempt.


See figure Unsuccessful internal intra-cell handover, timer expires on the source channel, call cleared.




Operability class:





2.16 001015 / TRANSACTIONS ENDED DUE TARGETCHANNEL FAIL

Counter ID: 001015 Network element name: TRANSACTIONS ENDED DUETARGET CHANNEL FAIL

Version: 2.1 NetAct name: TCH_RF_NEW_HO


29/04/2008


Description: A TCH transaction ends because of a radio failure (HO failure) on the target channelduring a handover attempt.

Counter 001088 is also updated along with this counter if the MS fails to return to the old channelduring an inter-BSC handover.


Reason for the impact: Since the MS cannot access the target channel, a radio failure occurs. It maybe caused by missing indication of call establishment, missing detection of HO, missing indication ofthe HO completed or corrupted messages related to HO.

Updated: When a TCH transaction ends because of a radio failure on the target channel during ahandover attempt.





001088: TCH A IF FAIL SOURCE

Operability class:





2.17 001016 / CALL ATTEMPTS IN THE QUEUE

Counter ID: 001016 Network element name: CALL ATTEMPTS IN THE QUEUEVersion: 2.1 NetAct name: TCH_QD_CALL_ATTDescription: Number of call attempts set in the queue for a TCH.

Counter 001010 is updated along with this counter.

Updated: When the RRM puts a TCH request for call attempt in the queue since it has no TCHs ofthe requested kind available.

See figures:- Successful TCH queuing- Basic call, no free TCHs, unsuccessful queuing and directed retry not activated


DN9813827Issue 11-1 en29/04/2008





001010: TCH REQUEST SUCCESS AND UNSUCCESS

Operability class:





2.18 001017 / HANDOVER ATTEMPTS IN THE QUEUE

Counter ID: 001017 Network element name: HANDOVER ATTEMPTS IN THEQUEUE

Version: 2.1 NetAct name: TCH_QD_HO_ATTDescription: Number of HO attempts set in the queue for a TCH.


Updated: When the RRM sets a TCH request for a handover attempt in the queue since it has noTCHs of the requested kind available.

See figures:- Internal intra-cell HO, successful TCH queuing- Internal intra-cell handover, unsuccessful TCH queuing- Internal directed retry





Operability class:






29/04/2008


2.19 001018 / AVE QUEUE LENGTH FOR CHANNELSEIZURE REQUEST

Counter ID: 001018 Network element name: AVE QUEUE LENGTH FORCHANNEL SEIZURE REQUEST

Version: 2.1 NetAct name: AVE_Q_SEIZ_REQDescription: Average number of requests for channel seizure in the queue.

Updated: Every 20 seconds, as averaging takes place once in the measurement period. The samplecounter is updated when a request is set in the queue or removed from it. Updated only to normalTRX record, not to extended TRX record.

See figure Average counter updating.

Logical type: Sum Trigger type: Sample Sampling interval: 20 s



Operability class:





2.20 001019 / QUEUE DENOMINATOR 1

Counter ID: 001019 Network element name: QUEUE DENOMINATOR 1Version: 2.1 NetAct name: QUEUE_DENOM1Description: Denominator of the average number of requests for channel seizure (always > 0).Updated:

Logical type: Sum Trigger type: Sample Sampling interval: 20 s



Operability class:

DN9813827Issue 11-1 en29/04/2008







2.21 001020 / AVE QUEUE TIME OF CALL ATTEMPTS

Counter ID: 001020 Network element name: AVE QUEUE TIME OF CALLATTEMPTS

Version: 2.1 NetAct name: AVE_Q_TIM_CALL_ATTDescription: The average time for which call attempts are kept in the queue (the unit of the value is 10ms).

In a successful case counters 001009 and 001021 are updated along with this counter. In anunsuccessful case counters 001021, 001024 and 001060 are updated along with this counter.

Updated: When a TCH request for a call attempt is removed from the queue (both in a successful andunsuccessful case).

See figures:- Successful TCH queuing- Basic call, no free TCHs, unsuccessful queuing and directed retry not activated

Logical type: Sum Trigger type: Duration Sampling interval:

Unit: 10 ms Range: Example values:


001009: SUCCESS TCH SEIZURE FOR NORMAL ASSIGNMENT

001021: QUEUE DENOMINATOR 2

001024: NOT SERVED QUEUED CALL ATTEMPTS

001060: QUE ALL ASSIGN REQ FAIL

Operability class:




29/04/2008





Counter ID: 001021 Network element name: QUEUE DENOMINATOR 2Version: 2.1 NetAct name: QUEUE_DENOM2Description: Denominator of the average time for which call attempts are kept in the queue (always >0).Updated: See figures:- Successful TCH queuing- Basic call, no free TCHs, unsuccessful queuing and directed retry not activated




Operability class:





2.23 001022 / AVE QUEUE TIME OF HO ATTEMPTS

Counter ID: 001022 Network element name: AVE QUEUE TIME OF HOATTEMPTS

Version: 2.1 NetAct name: AVE_Q_TIM_HO_ATTDescription: The average time for which HO attempts are kept in the queue (the unit of the value is 10ms).

In a successful case counters 001008 and 001023 are updated along with this counter. In anunsuccessful case counters 001023, 001025 and 001068 are updated along with this counter.

DN9813827Issue 11-1 en29/04/2008



Updated: When a TCH request for a handover attempt is removed from the queue (both in asuccessful and unsuccessful case).

See figures:- Internal intra-cell HO, successful TCH queuing- Internal intra-cell handover, unsuccessful TCH queuing- Internal directed retry

Logical type: Sum Trigger type: Duration Sampling interval:

Unit: 10 ms Range: Example values:


001008: SUCCESS TCH SEIZURE FOR HO


001025: NOT SERVED QUEUED HO ATTEMPTS

001068: QUE ALL HO REQ FAIL

Operability class:






Counter ID: 001023 Network element name: QUEUE DENOMINATOR 3Version: 2.1 NetAct name: QUEUE_DENOM3Description: Denominator of the average time for which HO attempts are kept in the queue (always >0).Updated: See figures:- Internal intra-cell HO, successful TCH queuing- Internal intra-cell handover, unsuccessful TCH queuing- Internal directed retry




29/04/2008



Operability class:





2.25 001024 / NOT SERVED QUEUED CALL ATTEMPTS

Counter ID: 001024 Network element name: NOT SERVED QUEUED CALLATTEMPTS

Version: 2.1 NetAct name: UNSRV_QD_CALL_ATTDescription: Number of call attempts in the queue which were not served.

Counters 001020, 001021 and 001060 are updated along with this counter.

Updated: When a call attempt is removed from the queue because a timer expires, or the call attemptis substituted by another attempt of higher priority. NOTE! This counter is not updated in DR (neitherin a successful or unsuccessful DR).

See figure Basic call, no free TCHs, unsuccessful queuing and directed retry not activated.




001020: AVE QUEUE TIME OF CALL ATTEMPTS


001060: QUE ALL ASSIGN REQ FAIL

Operability class:





DN9813827Issue 11-1 en29/04/2008



2.26 001025 / NOT SERVED QUEUED HO ATTEMPTS

Counter ID: 001025 Network element name: NOT SERVED QUEUED HOATTEMPTS

Version: 2.1 NetAct name: UNSRV_QD_HO_ATTDescription: Number of HO attempts in the queue which were not served.

Counters 001022, 001023 and 001068 are updated along with this counter.

Updated: When a handover attempt is removed from the queue because a timer expires, or the HOattempt is substituted by another attempt of higher priority.

See figure Internal intra-cell handover, unsuccessful TCH queuing.




001022: AVE QUEUE TIME OF HO ATTEMPTS


001068: QUE ALL HO REQ FAIL

Operability class:





2.27 001026 / TCH CALL REQ

Counter ID: 001026 Network element name: TCH CALL REQVersion: 2.1 NetAct name: TCH_CALL_REQ


29/04/2008


Description: Number of TCH requests for a normal assignment (both successful and unsuccessful).


Updated: When the RRM receives a TCH request in a call attempt.

See figures:- Basic call with counters- Basic call with priority subscriber- Successful TCH queuing- Basic call, no free TCHs, unsuccessful queuing and directed retry not activated- TCH assignment failure with cause switch_circuit_pool, queuing and directed retry not allowed- Unsuccessful trunk reservation- Internal directed retry- Successful forced release- Unsuccessful forced release- Successful forced handover- Unsuccessful forced handover





Operability class:





2.28 001027 / SDCCH ACT FAIL

Counter ID: 001027 Network element name: SDCCH ACT FAIL

Version: 2.1 NetAct name: SDCCH_ACT_FAIL

Description: Number of SDCCH transactions that are ended because of a failure in the activation of achannel either during a call or HO attempt.

Impact:- Call cleared- HO failure

Reason for the impact: External / Abis interface

DN9813827Issue 11-1 en29/04/2008



Updated: When either of the counters 001072 and 001074 is updated. This counter represents theirsum.

See figures:- Unsuccessful SDCCH activation- Unsuccessful SDCCH internal intra-cell handover, unsuccessful channel activation




Operability class:





2.29 001028 / TCH ACT FAIL

Counter ID: 001028 Network element name: TCH ACT FAIL

Version: 2.1 NetAct name: TCH_ACT_FAIL

Description: Number of TCH transactions that are ended because of a failure in the activation of achannel either during a call or HO attempt.


Reason for the impact: Abis Interface

Updated: When either of the counters 001081 and 001083 is updated. This counter represents theirsum.

See figures:- Unsuccessful TCH activation- Unsuccessful internal inter-cell handover




Operability class:


3GPP Measurement name (Clause header):


29/04/2008


3GPP Measurement type:



2.30 001029 / TCH TR FAIL

Counter ID: 001029 Network element name: TCH TR FAIL

Version: 2.1 NetAct name: TCH_TR_FAIL

Description: Number of TCH transactions that are ended because of a transcoder failure.


Updated: When a TCH transaction ends because of a transcoder failure during a call attempt and theRRM releases the TCH. These failures can also contain situations when the timer T3109 expires in aBSC in call release phase while waiting for the Release Indication. The MS subscriber does not seethese failures caused by the T3109 expiry as real drop calls.

This counter is updated in call phases 1-8 or 15 only.

See figure CONNECTION_FAILURE message with cause transcoder_failure during a call.




Operability class:





2.31 001030 / TCH TR FAIL SOURCE

Counter ID: 001030 Network element name: TCH TR FAIL SOURCE

Version: 2.1 NetAct name: TCH_TR_FAIL_OLD

DN9813827Issue 11-1 en29/04/2008



Description: Number of TCH transactions that are ended because of a transcoder failure on the sourcechannel during a handover on a TCH.


Updated: When a TCH transaction ends because of a transcoder failure on the source channel duringa handover attempt and the RRM releases the TCH. This happens before the RRM receives amessage from the MS stating that the HO or assignment is completed.





Operability class:





2.32 001031 / TCH TR FAIL TARGET

Counter ID: 001031 Network element name: TCH TR FAIL TARGET

Version: 2.1 NetAct name: TCH_TR_FAIL_NEW

Description: Number of TCH transactions that are ended because of a transcoder failure on the targetchannel during a handover on a TCH.


Updated: When a TCH transaction ends because of a transcoder failure on the target channel duringa handover attempt and the RRM releases the TCH. This happens before the RRM receives amessage from the MS stating that the HO or assignment is completed.


See figure Unsuccessful internal intra-cell handover, CONNECTION_FAILURE message with causeremote_transcoder_failure comes to the target channel.




Operability class:



29/04/2008





2.33 001032 / NOT RELEVANT

Counter ID: 001032 Network element name: NOT RELEVANT

Version: 2.0 NetAct name: SDCCH_FAST_SEIZ

Description: Not in use

Updated:

Logical type: Trigger type: Sampling interval:

Unit: Range: Example values:


Operability class:





2.34 001033 / SDCCH ABIS PROBL

Counter ID: 001033 Network element name: SDCCH ABIS PROBL

Version: 2.1 NetAct name: SDCCH_ABIS_FAIL

Description: Number of SDCCH transactions that are ended because of a failure in the Abis interface.



DN9813827Issue 11-1 en29/04/2008



Updated: When any of the counters 001075, 001076 or 001077 is updated. This counter representstheir sum.

See figures:- Unsuccessful SDCCH activation, timer expires while waiting for CHANNEL_ACTIVATION_ACKmessage- Unsuccessful SDCCH activation, timer expires while waiting for PHYSICAL_CONTEXT_CONFIRMmessage- TRX/TSL is blocked with different causes during an SDCCH channel activation- Unsuccessful SDCCH internal intra-cell handover, timer expires while waiting forCHANNEL_ACTIVATION_ACK message




Operability class:





2.35 001034 / SDCCH A IF PROBL

Counter ID: 001034 Network element name: SDCCH A IF PROBL

Version: 2.1 NetAct name: SDCCH_A_IF_FAIL

Description: Number of SDCCH transactions that are ended because of a failure in the A interface.


Reason for the impact: External / A interface

Updated: When any of the counters 001078, 001079, and 001080 is updated. This counter representstheir sum.

See figures:- SDCCH assignment failure- Unsuccessful SDCCH external handover, timer expires while waiting for CLEAR_COMMANDmessage





29/04/2008


Operability class:





2.36 001035 / SDCCH LAPD FAIL

Counter ID: 001035 Network element name: SDCCH LAPD FAIL

Version: 2.1 NetAct name: SDCCH_LAPD_FAIL

Description: Number of SDCCH transactions that are ended because of an LAPD failure. (The blockedTRX is in one of these substates: signalling link fault or PCM fault.)



Updated: When an SDCCH transaction ends because of a TRX blocked by an LAPD failure and theRRM releases the SDCCH.

See figure TRX/TSL is blocked with different causes during an SDCCH channel activation.




Operability class:





2.37 001036 / SDCCH BTS FAIL

DN9813827Issue 11-1 en29/04/2008



Counter ID: 001036 Network element name: SDCCH BTS FAIL

Version: 2.1 NetAct name: SDCCH_BTS_FAIL

Description: Number of SDCCH transactions that are ended because of a BTS failure. (The blockedTRX is in one of these substates: FU fault, CU fault, BTS reset, BCF reset, both CU and FU fault,BCF fault.)


Updated: When an SDCCH transaction ends because of a TRX being blocked by a BTS failure andthe RRM releases the SDCCH.





Operability class:





2.38 001037 / SDCCH USER ACT

Counter ID: 001037 Network element name: SDCCH USER ACT

Version: 2.1 NetAct name: SDCCH_USER_ACT

Description: Number of SDCCH transactions that are ended because of user actions. (The TRX/TSL isin substate blocked by the user.)


Updated: When the user disconnects a busy SDCCH by blocking the TSL/TRX with an MMLcommand. The transaction ends and the SDCCH is released.





Operability class:


29/04/2008



3GPP Measurement name (Clause header):3GPP Measu

nokia nsn traffic measurments

Documents