bss network doctor formulas nokia

BSS Network Doctor FormulasDN98619493 Nokia Corporation 1 (302)Issue 2-3 en Nokia Proprietary and Confidential

BSS Network Doctor Formulas

The information in this documentation is subject to change without notice and describes onlythe product defined in the introduction of this documentation. This documentation is intended

for the use of Nokia's customers only for the purposes of the agreement under which thedocumentation is submitted, and no part of it may be reproduced or transmitted in any form ormeans without the prior written permission of Nokia. The documentation has been prepared tobe used by professional and properly trained personnel, and the customer assumes fullresponsibility when using it. Nokia welcomes customer comments as part of the process ofcontinuous development and improvement of the documentation.The information or statements given in this documentation concerning the suitability, capacity,or performance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However, Nokiahas made all reasonable efforts to ensure that the instructions contained in the documentationare adequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.Nokia's liability for any errors in the documentation is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation orthe information in it.This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.NOKIA logo is a registered trademark of Nokia Corporation.Other product names mentioned in this documentation may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright Nokia Corporation 2003. All rights reserved.2 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

ContentsContents 3

List of tables 5

List of figures 6

1 About this manual 311.1 Summary of changes 311.2 What you need to know first 331.3 Where to find more 341.4 Typographic conventions 341.4.1 Text styles 341.5 Terms and concepts 351.5.1 Abbreviations 351.5.2 Terms 37

2 BSS counter formulas 392.1 Additional GPRS channels (ach) 392.2 Multislot (msl) 412.3 TBF (tbf) 452.4 LLC (llc) 562.5 RLC (rlc) 562.6 Frame relay (frl) 742.7 HSCSD (hsd) 782.8 Dynamic Abis Pool (dap) 792.9 Random access (rach) 802.10 SDCCH drop failures (sd) 822.10.1 SDCCH drop counters 832.10.2 Problems with the SDCCH drop counters 852.11 SDCCH drop ratio (sdr) 862.12 Setup success ratio (cssr) 872.13 TCH drop failures 882.13.1 TCH drop call counters 882.13.2 Drop call ratio 912.13.3 Drop-out ratio 912.13.4 Problems with the drop call counters 922.14 Drop call failures (dcf) 922.15 TCH drop call % (dcr) 932.16 Adaptive Multirate (amr) 1072.17 Position based services (pbs) 1082.18 Handover (ho) 1102.19 Handover failure % (hfr) 1232.20 Handover success % (hsr) 1492.21 Handover failures (hof) 1532.22 Interference (itf) 1582.23 Congestion (cngt) 1592.24 Queuing (que) 1612.25 Blocking (blck) 164DN98619493 Nokia Corporation 3 (302)Issue 2-3 en Nokia Proprietary and Confidential


2.26 Traffic (trf) 1742.27 Traffic directions 235

2.27.1 Mobile originated calls (moc) 2352.27.2 Mobile terminated calls (mtc) 2362.28 Paging (pgn) 2382.29 Short message service (sms) 2422.30 Directed retry (dr) 2432.31 Availability (ava) 2452.32 Unavailability (uav) 2592.33 Location updates (lu) 2632.34 LU success % (lsr) 2642.35 Emergency call (ec) 2642.36 Emergency call success % (ecs) 2642.37 Call re-establishment (re) 2652.38 Call re-establishment success % (res) 2652.39 Quality 2662.39.1 Downlink quality (dlq) 2662.39.2 Uplink quality (ulq) 2702.40 Downlink and uplink level 2742.40.1 Downlink level (dll) 2742.40.2 Uplink level (ull) 2742.41 Power (pwr) 2752.42 Level (lev) 2752.43 Distance (dis) 2762.44 Link balance, power, level (lb) 2772.45 Call success (csf) 2812.46 Configuration (cnf) 2963 Missing Counters 2993.1 XX1 2993.2 XX2 2993.3 XX3 2993.4 XX4 300

Index 3014 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

List of tablesTable 1. Text styles in this document 35Table 2. Abbreviations 35Table 3. Terms used in this document 37Table 4. SDCCH Drop Counters 84Table 5. TCH drop call counters 89DN98619493 Nokia Corporation 5 (302)Issue 2-3 en Nokia Proprietary and Confidential


List of figuresFigure 1. Additional GPRS channel use, S9PS (ach_1) 40Figure 2. Average additional GPRS channel hold time, S9PS (ach_2) 40Figure 3. Additional GPRS channels seized, S9PS (ach_3) 40Figure 4. Total additional GPRS channel hold time, S9PS (ach_4) 41Figure 5. Distribution of UL multislot requests, S9PS (msl_1) 41Figure 6. Distribution of DL multislot requests, S9PS (msl_2) 41Figure 7. Distribution of UL multislot allocations, S9PS (msl_3) 42Figure 8. Distribution of DL multislot allocations, S9PS (msl_4) 42Figure 9. Ratio of unreserved GPRS UL TSL requests, S9PS (msl_5) 42Figure 10. Ratio of unreserved GPRS DL TSL requests, S9PS (msl_6) 42Figure 11. UL multislot allocations, S9PS (msl_9) 43Figure 12. DL multislot allocations, S9PS (msl_10) 43Figure 13. Average number of allocated timeslots, UL S9PS (msl_11) 43Figure 14. Average number of allocated timeslots, DL S9PS (msl_13) 43Figure 15. Average number of requested UL timeslots, S9PS (msl_13) 44Figure 16. Average number of requested DL timeslots, S9PS (msl_14) 44Figure 17. UL multislot allocation %, S9PS (msl_15a) 44Figure 18. DL multislot allocation %, S9PS (msl_16a) 45Figure 19. UL multislot requests, S9PS (msl_17) 45Figure 20. DL multislot requests, S9PS (msl_18) 45Figure 21. Average number of LLC blocks per UL TBF, S9PS (tbf_3) 46Figure 22. Average number of LLC blocks per DL TBF, S9PS (tbf_4) 46Figure 23. Average UL TBF duration, S9PS (tbf_5) 46Figure 24. Average UL TBF duration, S9PS (tbf_5a) 47Figure 25. Average DL TBF duration, S9PS (tbf_6a) 47Figure 26. Average UL TBF duration, unack mode, S9PS (tbf_7) 47Figure 27. Average DL TBF duration, unack mode, S9PS (tbf_8) 47Figure 28. UL mlslot allocation blocking, S9PS (tbf_15) 48Figure 29. DL mlslot allocation blocking, S9PS (tbf_16) 486 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

Figure 30. UL TBF releases due to CS traffic %, S9PS (tbf_19) 49

Figure 31. DL TBF releases due to CS traffic %, S9PS (tbf_20) 49Figure 32. UL drops per 10 Kbytes, MS lost, S9PS (tbf_27a) 49Figure 33. UL drops per 10 Kbytes, MS lost, S9PS (tbf_27b) 50Figure 34. UL drops per 10 Kbytes, MS lost, S10.5PS (tbf_27c) 51Figure 35. DL drops per 10 Kbytes, MS lost, S9PS (tbf_28a) 51Figure 36. DL drops per 10 Kbytes, MS lost, S9PS (tbf_28b) 52Figure 37. DL drops per 10 Kbytes, MS lost, S10.5PS (tbf_28c) 52Figure 38. UL TBF reallocation failure ratio, S9PS (tbf_29) 52Figure 39. DL TBF reallocation failure ratio, S9PS (tbf_30) 53Figure 40. UL TBF reallocation attempts, S9PS (tbf_31) 53Figure 41. DL TBF reallocation attempts, S9PS (tbf_32) 53Figure 42. TBF success % S9PS (tbf_34) 54Figure 43. UL TBF releases due to flush %, S9PS (tbf_35) 54Figure 44. DL TBF releases due to flush %, S9PS (tbf_36) 54Figure 45. Average UL TBF per timeslot, S9PS (tbf_37b) 55Figure 46. Average DL TBF per timeslot, S9PS (tbf_38b) 55Figure 47. UL GPRS TBF establishments, S10.5PS (tbf_41) 55Figure 48. DL GPRS TBF establishments, S10.5PS (tbf_42) 55Figure 49. Expired LLC frames % DL, S9PS (llc_1) 56Figure 50. Discarded UL LLC frames, NSE unavailability %, S9PS (llc_2) 56Figure 51. Ack. CS1 RLC blocks UL, S9PS (rlc_1) 56Figure 52. Ack. CS1 RLC blocks DL, S9PS (rlc_2) 57Figure 53. Ack. CS1 RLC DL block error rate, S9PS (rlc_3a) 57Figure 54. Unack. CS1 RLC UL block error rate, S9PS (rlc_4a) 57Figure 55. Ack. CS1 RLC UL block error rate), S9PS (rlc_5a) 57Figure 56. UL CS1 RLC data share, S9PS (rlc_6a) 58Figure 57. UL CS1 ack RLC data share, S9PS (rlc_6b) 58Figure 58. UL CS1 unack RLC data share, S9PS (rlc_6c) 58Figure 59. UL CS2 RLC data share, S9PS (rlc_7a) 59Figure 60. DL CS1 RLC data share, S9PS (rlc_8a) 59DN98619493 Nokia Corporation 7 (302)Issue 2-3 en Nokia Proprietary and Confidential


Figure 61. DL CS1 ack RLC data share, S9PS (rlc_8b) 59

Figure 62. DL CS1 unack RLC data share, S9PS (rlc_8c) 60Figure 63. DL CS2 RLC data share, S9PS (rlc_9a) 60Figure 64. UL CS1 RLC block error rate, S9PS (rlc_10a) 61Figure 65. UL CS1 RLC block error rate, S9PS (rlc_10b) 62Figure 66. UL CS2 ARLC block error rate, S9PS (rlc_11a) 63Figure 67. UL CS2 RLC block error rate, S9PS (rlc_11b) 63Figure 68. UL CS2 ACK RLC block error rate, S9PS (rlc_11c) 64Figure 69. DL CS1 RLC block error rate, S9PS (rlc_12) 64Figure 70. DL CS1 ACK RLC block error rate, S9PS (rlc_12a) 64Figure 71. DL CS2 RLC block error rate, S9PS (rlc_13) 64Figure 72. UL RLC blocks, S9PS (rlc_14) 65Figure 73. DL RLC blocks, S9PS (rlc_15) 65Figure 74. UL ACK EGPRS block error ratio S10.5PS (rlc_18) 65Figure 75. DL ACK EGPRS block error ratio S10.5PS (rlc_19) 66Figure 76. UL ACK EGPRS block error ratio MCS-n, S10.5PS (rlc_20) 66Figure 77. DL ACK EGPRS block error ratio MCS-n, S10.5PS (rlc_21) 66Figure 78. UL ACK RLC data share MCS-n, S10.5PS (rlc_22) 67Figure 79. UL UNACK RLC data share MCS-n, S10.5PS (rlc_23) 67Figure 80. DL ACK RLC data share MCS-n, S10.5PS (rlc_24) 67Figure 81. DL UNACK RLC data share MCS-n, S10.5PS (rlc_25) 68Figure 82. GMSK RLC data block share, S10.5PS (rlc_39) 68Figure 83. GMSK RLC data share, S10.5PS (rlc_41) 69Figure 84. GPRS UL ACK RLC data share, S10.5PS (rlc_42) 69Figure 85. GPRS UL UNACK RLC data share, S10.5PS (rlc_43) 70Figure 86. GPRS DL ACK RLC data share, S10.5PS (rlc_44) 70Figure 87. GPRS DL UNACK RLC data share, S10.5PS (rlc_45) 71Figure 88. EGPRS UL ACK RLC data share, S10.5PS (rlc_46) 71Figure 89. EGPRS UL UNACK RLC data share, S10.5PS (rlc_47) 72Figure 90. EGPRS DL ACK RLC data share, S10.5PS (rlc_48) 73Figure 91. EGPRS DL UNACK RLC data share, S10.5PS (rlc_49) 738 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

Figure 92. Kbytes in sent frames, S9PS (frl_1) 74

Figure 93. Kbytes in received frames, S9PS (frl_2) 74Figure 94. Wrong check seq. errors per Mbyte, S9PS (frl_3) 75Figure 95. Other errors per Mbyte, S9PS (frl_4) 75Figure 96. Bytes in discarded sent frames, S9PS (frl_5) 75Figure 97. Bytes in discarded received frames, S9PS (frl_6) 75Figure 98. Maximum sent load %, S9PS (frl_7) 76Figure 99. Maximum received load %, S9PS (frl_8) 76Figure 100. Sent frames, S9PS (frl_9) 77Figure 101. Received frames, S9PS (frl_10) 77Figure 102. Discarded sent frames, S9PS (frl_11) 77Figure 103. Discarded received frames, S9PS (frl_12) 77Figure 104. Discarded bytes, UL NS-VC congestion S9PS (frl_13a) 78Figure 105. Throughput ratio, S7HS (hsd_15) 78Figure 106. Bps traffic share, S7HS (hsd_49) 78Figure 107. Bps traffic share, S7HS (hsd_50) 79Figure 108. Average usage of DL Dynamic Abis Pool, S10.5PS (dap_1) 79Figure 109. Average usage of UL Dynamic Abis Pool, S10.5PS (dap_2) 80Figure 110. Average RACH slot, S1 (rach_1) 80Figure 111. Peak RACH load, average, S1 (rach_2) 80Figure 112. Peak RACH load %, S1 (rach_3) 81Figure 113. Average RACH load %, S1 (rach_4) 81Figure 114. Average RACH busy, S1 (rach_5) 81Figure 115. RACH rejected due to illegal establishment, S5 (rach_6) 82Figure 116. Total RACH rejection ratio, S7 (rach_7) 82Figure 117. Ghosts detected on SDCCH and other failures, S1 (sd_1) 82Figure 118. Ghosts detected on SDCCH and other failures, S1 (sd_1a) 83Figure 119. SDCCH drop %, S3 (sdr_1a) 87Figure 120. SDCCH drop %, abis fail excluded, S3 (sdr_2) 87Figure 121. Illegal establishment cause % (sdr_3b) 87Figure 122. SDCCH, TCH setup success %, S4 (cssr_2) 88DN98619493 Nokia Corporation 9 (302)Issue 2-3 en Nokia Proprietary and Confidential


Figure 123. TCH drop calls in HO, S2 (dcf_2) 92

Figure 124. TCH drop calls in BSC outgoing HO, S3 (dcf_3) 92Figure 125. TCH drop calls in intra-cell HO, S3 (dcf_4) 93Figure 126. TCH drop calls in intra BSC HO, S3 (dcf_6) 93Figure 127. Drop calls in BSC incoming HO, S3 (dcf_7) 93Figure 128. TCH drop calls in HO, S7 (dcf_11) 93Figure 129. TCH drop call %, area, real, after re-establishment S3 (dcr_3f) 94Figure 130. TCH drop call %, area, real, before re-establishment, S3 (dcr_3g) 95Figure 131. TCH drop call %, area, real, after re-establishment, S7 (dcr_3h) 96Figure 132. TCH drop call %, area, real, before re-establishment, S3 (dcr_3i) 97Figure 133. TCH drop call %, area, real, after re-establishment, S7 (dcr_3j) 98Figure 134. TCH drop-out %, BTS level, before call re-establishment, S3 (dcr_4c) 99Figure 135. TCH drop-out %, BTS level, before call re-establishment, S3 (dcr_4d) 99Figure 136. TCH drop-out %, BTS level, before call re-establishment, S7

(dcr_4e) 100Figure 137. TCH drop-out %, BTS level, before call re-establishment, S7

(dcr_4f) 100Figure 138. TCH drop call (dropped conversation) %, BSC level, S4 (dcr_5) 101Figure 139. . . TCH dropped conversation %, area, re-establishment considered, S7

(dcr_5b) 102Figure 140. TCH drop call %, after TCH assignment, without re-establishment, area

level, S7 (dcr_8) 102Figure 141. . . . TCH drop call %, after TCH assignment, with re-establishment, area

level, S7 (dcr_8b) 103Figure 142. Drops per erlang, before re-establishment, S4 (dcr_10) 103Figure 143. Drops per erlang, after re-establishment, S4 (dcr_10a) 104Figure 144. Drops per erlang, after re-establishment, S7 (dcr_10b) 104Figure 145. Transcoder failure ratio, FR (dcr_16) 104Figure 146. Transcoder failure ratio, EFR (dcr_17) 105Figure 147. Transcoder failure ratio, HR (dcr_18) 105Figure 148. Transcoder failure ratio, AMR FR (dcr_19) 105Figure 149. Transcoder failure ratio, AMR HR (dcr_20) 105Figure 150. Transcoder failure ratio (dcr_21) 10610 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

Figure 151. Call failures share of transcoder failures (dcr_22) 106

Figure 152. HO target share of transcoder failures (dcr_23) 106Figure 153. HO source share of transcoder failures (dcr_24) 106Figure 154. Transcoder failures (dcr_25) 107Figure 155. Codec set upgrade attempts, S10 (amr_1) 107Figure 156. Codec set downgrade attempts, S10 (amr_2) 107Figure 157. Codec set upgrade failure ratio, S10 (amr_3) 107Figure 158. Codec set downgrade failure ratio, S10 (amr_4) 108Figure 159. Failure ratio of location calculations for external LCS clients, S10

(pbs_1a) 108Figure 160. Failure ratio of location calculations for emergency calls, S10

(pbs_2a) 108Figure 161. Failure ratio of E-OTD location calculations, S10 (pbs_3) 108Figure 162. Failure ratio of E-OTD location calculations, S10 (pbs_3a) 109Figure 163. Failure ratio of location calculations for MS, S10 (pbs_4a) 109Figure 164. Failure ratio of location calculations for operator, S10 (pbs_5a) 109Figure 165. Failure ratio of location calculations using stand-alone GPS, S10

(pbs_6) 109Figure 166. Failure ratio of location calculations using stand-alone GPS, S10

(pbs_6a) 110Figure 167. Unspecified LCS requests, S10 (pbs_8) 110Figure 168. Return from super TRXs to regular TRX, S4 (ho_1) 110Figure 169. HO attempts from regular TRXs to super, S4 (ho_2) 110Figure 170. HO attempts from super to regular, S4 (ho_3) 111Figure 171. Share of HO attempts from super to regular due to DL quality, S4

(ho_4) 111Figure 172. Share of HO attempts from super to regular due to DL interference, S4

(ho_5) 111Figure 173. Share of HO attempts from super to regular due to UL interference, S4

(ho_6) 111Figure 174. Share of HO attempts from super to regular due to bad C/I, S4

(ho_7) 112Figure 175. MSC incoming HO attempts (ho_8) 112Figure 176. MSC outgoing HO attempts (ho_9) 112DN98619493 Nokia Corporation 11 (302)Issue 2-3 en Nokia Proprietary and Confidential


Figure 177. BSC incoming HO attempts (ho_10) 112

Figure 178. BSC outgoing HO attempts (ho_11) 112Figure 179. Intra-cell HO attempts, S6 (ho_12a) 113Figure 180. HO attempts, outgoing and intra-cell, S4 (ho_13) 113Figure 181. HO attempts, S3 (ho_13a) 113Figure 182. HO attempts, outgoing and intra-cell, S5 (ho_13b) 114Figure 183. HO attempts, outgoing and intra-cell, S3 (ho_13e) 114Figure 184. HO attempts, outgoing and intra-cell, S9, (ho_13g) 114Figure 185. TCH requests for HO (ho_14a) 115Figure 186. TCH requests for HO (ho_14b) 115Figure 187. TCH seizures for HO (ho_15) 115Figure 188. TCH-TCH HO attempts (ho_16) 115Figure 189. SDCCH-TCH HO attempts (ho_17) 116Figure 190. SDCCH-SDCCH HO attempts (ho_18) 116Figure 191. TCH-TCH HO successes (ho_19) 116Figure 192. SDCCH-TCH HO successes (ho_20) 117Figure 193. SDCCH-SDCCH HO successes (ho_21) 117Figure 194. MSC controlled HO attempts (ho_22) 117Figure 195. BSC controlled HO attempts (ho_23) 117Figure 196. Intra-cell HO attempts (ho_24) 118Figure 197. MSC controlled HO successes (ho_25) 118Figure 198. BSC controlled HO successes (ho_26) 118Figure 199. Intra-cell HO successes (ho_27) 118Figure 200. MSC incoming HO successes (ho_28) 119Figure 201. MSC outgoing HO successes (ho_29) 119Figure 202. BSC incoming HO successes (ho_30) 119Figure 203. BSC outgoing HO successes (ho_31) 119Figure 204. Incoming HO success (ho_32) 119Figure 205. Outgoing HO successes (ho_33) 120Figure 206. Outgoing HO attempts (ho_34) 120Figure 207. Incoming HO attempts (ho_35) 12012 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

Figure 208. Outgoing SDCCH-SDCCH HO attempts (ho_36) 120

Figure 209. Incoming SDCCH-SDCCH HO attempts (ho_37) 120Figure 210. Outgoing SDCCH-TCH HO attempts (ho_38) 121Figure 211. Incoming SDCCH-TCH HO attempts (ho_39) 121Figure 212. Outgoing TCH-TCH HO attempts (ho_40) 121Figure 213. Incoming TCH-TCH HO attempts (ho_41) 121Figure 214. Outgoing SDCCH-SDCCH HO success (ho_42) 121Figure 215. Incoming SDCCH-SDCCH HO success (ho_43) 122Figure 216. Outgoing SDCCH-TCH HO success (ho_44) 122Figure 217. Incoming SDCCH-TCH HO success (ho_45) 122Figure 218. Outgoing TCH-TCH HO success (ho_46) 122Figure 219. Incoming TCH-TCH HO success (ho_47) 122Figure 220. Intra-cell HO share, S1 (ho_48) 123Figure 221. MSC controlled incoming HO attempts (ho_49) 123Figure 222. Total HO failure %, S1 (hfr_1) 124Figure 223. Total HO failure %, S1 (hfr_2) 125Figure 224. Intra-cell HO failure share, S1 (hfr_3a) 125Figure 225. Intra-cell HO failure share, S1 (hfr_3b) 126Figure 226. Intra-cell HO failure share, S1 (hfr_3c) 126Figure 227. Intra-cell HO failure share, S1 (hfr_3d) 126Figure 228. Incoming MSC ctrl HO failure %, S1 (hfr_4) 127Figure 229. Incoming MSC ctrl HO failure share, S1 (hfr_4a) 127Figure 230. Incoming MSC ctrl HO failure share, S1 (hfr_4b) 127Figure 231. Incoming MSC ctrl HO failure share, S1 (hfr_4c) 128Figure 232. Incoming MSC ctrl HO failure share, S1 (hfr_4d) 128Figure 233. Outgoing MSC ctrl HO failure share %, S1 (hfr_5a) 129Figure 234. Outgoing MSC ctrl HO failure share %, S1 (hfr_5b) 129Figure 235. Outgoing MSC ctrl HO failure share %, S1 (hfr_5c) 129Figure 236. Outgoing MSC ctrl HO failure share %, S1 (hfr_5d) 130Figure 237. Incoming BSC ctrl HO failure %, S1 (hfr_6) 130Figure 238. Incoming BSC ctrl HO failure share %, S1 (hfr_6a) 130DN98619493 Nokia Corporation 13 (302)Issue 2-3 en Nokia Proprietary and Confidential


Figure 239. Incoming BSC ctrl HO failure %, S1 (hfr_6b) 131

Figure 240. Incoming BSC ctrl HO failure share %, S1 (hfr_6c) 131Figure 241. Incoming BSC ctrl HO failure %, S1 (hfr_6d) 132Figure 242. Outgoing BSC ctrl HO failure share, S1 (hfr_7) 132Figure 243. Outgoing BSC ctrl HO failure share, S1 (hfr_7a) 132Figure 244. Outgoing BSC ctrl HO failure share, S1 (hfr_7b) 133Figure 245. Outgoing BSC ctrl HO failure share, S1 (hfr_7c) 133Figure 246. Outgoing BSC ctrl HO failure share, S1 (hfr_7d) 133Figure 247. Internal inter HO failure %, S4 (hfr_8) 134Figure 248. Internal intra HO failure %, S4 (hfr_9) 134Figure 249. External source HO failure %, S4 (hfr_10) 134Figure 250. HO failure % from super to regular, S4 (hfr_12) 134Figure 251. HO failure % from regular to super, S4 (hfr_13) 135Figure 252. Share of HO failures from regular to super due to return, S4 (hfr_14) 135Figure 253. Share of HO failures from regular to super due to MS lost, S4

(hfr_15) 135Figure 254. Share of HO failures from regular to super due to another cause, S4

(hfr_16) 135Figure 255. Share of HO failures from super to regular due to return, S4 (hfr_17) 136Figure 256. Share of HO failures from super to regular due to MS lost, S4

(hfr_18) 136Figure 257. Share of HO failures from super to regular due to another cause, S4

(hfr_19) 136Figure 258. SDCCH-SDCCH HO failure %, S2 (hfr_20) 137Figure 259. SDCCH-TCH HO failure %, S2 (hfr_21) 137Figure 260. TCH-TCH HO failure %, S2 (hfr_22) 137Figure 261. SDCCH-SDCCH incoming HO failure %, S2 (hfr_23) 138Figure 262. SDCCH-SDCCH outgoing HO failure ratio, S2 (hfr_24) 138Figure 263. SDCCH-TCH incoming HO failure %, S2 (hfr_25) 138Figure 264. SDCCH-TCH outgoing HO failure %, S2 (hfr_26) 138Figure 265. TCH-TCH incoming HO failure %, S2 (hfr_27) 139Figure 266. TCH-TCH outgoing HO failure %, S2 (hfr_28) 139Figure 267. MSC ctrl HO failure %, blocking (hfr_29) 13914 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

Figure 268. MSC ctrl HO failure %, not allowed (hfr_30) 139

Figure 269. MSC ctrl HO failure %, return to old (hfr_31) 140Figure 270. MSC ctrl HO failure %, call clear (hfr_32) 140Figure 271. MSC ctrl HO failure %, end HO (hfr_33) 140Figure 272. MSC ctrl HO failure %, end HO BSS (hfr_34) 140Figure 273. MSC ctrl HO failure %, wrong A interface (hfr_35) 141Figure 274. MSC ctrl HO failure %, adjacent cell error (hfr_36) 141Figure 275. BSC ctrl HO failure %, blocking (hfr_37) 141Figure 276. BSC ctrl HO failure %, not allowed (hfr_38) 141Figure 277. BSC ctrl HO failure %, return to old (hfr_39) 142Figure 278. BSC ctrl HO failure %, call clear (hfr_40) 142Figure 279. BSC ctrl HO failure %, end HO (hfr_41) 142Figure 280. BSC ctrl HO failure %, end HO BSS (hfr_42) 142Figure 281. BSC ctrl HO failure %, wrong A interface (hfr_43) 143Figure 282. BSC ctrl HO drop call % (hfr_44) 143Figure 283. Intra-cell HO failure %, cell_fail_lack (hfr_45) 143Figure 284. Intra-cell HO failure %, not allowed (hfr_46) 143Figure 285. Intra-cell HO failure %, return to old (hfr_47) 144Figure 286. Intra-cell HO failure %, call clear (hfr_48) 144Figure 287. Intra-cell HO failure %, MS lost (hfr_49) 144Figure 288. Intra-cell HO failure %, BSS problem (hfr_50) 144Figure 289. Intra-cell HO failure %, drop call (hfr_51) 145Figure 290. HO failure % to adjacent cell (hfr_52) 145Figure 291. HO failure % from adjacent cell (hfr_53) 145Figure 292. HO failure %, blocking excluded (hfr_54a) 146Figure 293. HO failure % due to radio interface blocking (hfr_55) 146Figure 294. Intra-cell HO failure %, wrong A interface (hfr_56) 146Figure 295. Intra-cell HO failure % (hfr_57) 146Figure 296. HO failures to target cell, S6 (hfr_58) 147Figure 297. HO failures from target cell, S6 (hfr_59) 147Figure 298. HO drop ratio (hfr_68) 148DN98619493 Nokia Corporation 15 (302)Issue 2-3 en Nokia Proprietary and Confidential


Figure 299. HO failures to target WCDMA cell, S10.5 (hfr_69) 148

Figure 300. HO failures from target WCDMA cell, S10.5 (hfr_70) 148Figure 301. MSC controlled outgoing SDCCH-SDCCH HO success %, S1

(hsr_1) 149Figure 302. MSC controlled outgoing SDCCH-TCH HO success %, S1 (hsr_2) 149Figure 303. MSC controlled outgoing TCH-TCH HO success %, S1 (hsr_3) 149Figure 304. BSC controlled outgoing SDCCH-SDCCH HO success %, S1

(hsr_4) 149Figure 305. BSC controlled outgoing SDCCH-TCH HO success %, S1 (hsr_5) 150Figure 306. BSC controlled outgoing TCH-TCH HO success %, S1 (hsr_6) 150Figure 307. Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_7) 150Figure 308. Intra-cell SDCCH-TCH HO success %, S1 (hsr_8) 150Figure 309. Intra-cell TCH-TCH HO success %, S1 (hsr_9) 150Figure 310. MSC controlled incoming SDCCH-SDCCH HO success %, S1

(hsr_10) 151Figure 311. MSC controlled incoming SDCCH-TCH HO success %, S1 (hsr_11) 151Figure 312. MSC controlled incoming TCH-TCH HO success %, S1 (hsr_12) 151Figure 313. BSC controlled incoming SDCCH-SDCCH HO success %, S1

(hsr_13) 151Figure 314. BSC controlled incoming SDCCH-TCH HO success %, S1 (hsr_14) 151Figure 315. BSC controlled incoming TCH-TCH HO success %, S1 (hsr_15) 152Figure 316. BSC controlled incoming HO success %, S1 (hsr_16) 152Figure 317. MSC controlled incoming HO success %, S1 (hsr_17) 152Figure 318. Incoming HO success %, S1 (hsr_18) 152Figure 319. Outgoing HO success %, S1 (hsr_19) 152Figure 320. Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_20) 153Figure 321. Intra-cell SDCCH-TCH HO success %, S1 (hsr_21) 153Figure 322. Intra-cell TCH-TCH HO success %, S1 (hsr_22) 153Figure 323. Outgoing HO failures due to lack of resources (hof_1) 153Figure 324. Incoming HO failures due to lack of resources (hof_2) 154Figure 325. TCH HO failures when return to old channel was successful (hof_3) 154Figure 326. SDCCH HO failures when return to old channel was successful

(hof_4) 15416 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

Figure 327. MSC incoming HO failures (hof_5) 154

Figure 328. MSC outgoing HO failures (hof_6) 155Figure 329. MSC outgoing HO failures (hof_6a) 155Figure 330. BSC incoming HO failures (hof_7) 155Figure 331. BSC incoming HO failures (hof_7a) 155Figure 332. BSC outgoing HO failures (hof_8) 156Figure 333. BSC outgoing HO failures (hof_8a) 156Figure 334. Intra-cell HO failures (hof_9) 156Figure 335. Intra-cell HO failures (hof_9a) 156Figure 336. Failed outgoing HO, return to old (hof_10) 156Figure 337. Outgoing HO failures (hof_12) 157Figure 338. Intra-cell HO failure, return to old channel (hof_13) 157Figure 339. Intra-cell HO failure, drop call (hof_14) 157Figure 340. Incoming HO failures (hof_15) 157Figure 341. UL interference, BTS level, S1 (itf_1) 158Figure 342. Idle TSL percentage of time in band X, TRX level, IUO, S4 (itf_2) 158Figure 343. UL interference from IUO, TRX level, S4 (itf_3) 159Figure 344. UL interference from Power Control, TRX level, S6 (itf_4) 159Figure 345. TCH congestion time, S1 (cngt_1) 159Figure 346. SDCCH congestion time, S1 (cngt_2) 160Figure 347. FTCH time congestion % (cngt_3) 160Figure 348. FTCH time congestion % (cngt_3a) 160Figure 349. HTCH time congestion % (cngt_4) 160Figure 350. HTCH time congestion % (cngt_4a) 161Figure 351. Queued, served TCH call requests % (que_1a) 161Figure 352. Queued, served TCH HO requests % (que_2) 161Figure 353. Queued, served TCH HO requests % (que_2a) 162Figure 354. Successful queued TCH requests (que_3) 162Figure 355. Successful non-queued TCH requests (que_4) 162Figure 356. Successful queued TCH HO requests (que_5) 162Figure 357. Successful non-queued TCH HO requests (que_6) 163DN98619493 Nokia Corporation 17 (302)Issue 2-3 en Nokia Proprietary and Confidential


Figure 358. Non-queued, served TCH call requests % (que_7) 163

Figure 359. Non-queued, served TCH HO requests % (que_8) 163Figure 360. Non-queued, served TCH HO requests % (que_8a) 163Figure 361. TCH raw blocking, S1 (blck_1) 164Figure 362. SDCCH blocking %, S1 (blck_5) 164Figure 363. SDCCH real blocking %, S1 (blck_5a) 164Figure 364. TCH raw blocking % on super TRXs, S4 (blck_6) 165Figure 365. TCH raw blocking % on regular TRXs, S4 (blck_7) 165Figure 366. TCH call blocking, before DR, S2 (blck_8) 165Figure 367. TCH call blocking %, DR compensated, S2 (blck_8b) 166Figure 368. TCH call blocking %, DR and DAC compensated, EFR excluded, S5

(blck_8d) 167Figure 369. Blocked calls, S5 (blck_9b) 168Figure 370. Blocked calls, S5 (blck_9c) 168Figure 371. Blocked TCH HOs, S2 (blck_10a) 168Figure 372. Blocked TCH HOs, S5 (blck_10b) 169Figure 373. TCH HO blocking, S2 (blck_11a) 169Figure 374. TCH HO blocking without Q, S2 (blck_11b) 169Figure 375. TCH HO blocking, S5 (blck_11c) 170Figure 376. Blocked incoming and internal HO, S2 (blck_12) 170Figure 377. Blocked incoming and internal HO, S2 (blck_12a) 170Figure 378. AG blocking, S1 (blck_13) 171Figure 379. FCS blocking, S5 (blck_14) 171Figure 380. Blocked SDCCH seizure attempts, S5 (blck_15) 171Figure 381. HO blocking % (blck_16a) 172Figure 382. Handover blocking % (blck_16b) 172Figure 383. Blocked FACCH call setup TCH requests (blck_18) 172Figure 384. Handover blocking to target cell (blck_19) 172Figure 385. Handover blocking from target cell (blck_20) 173Figure 386. NACK ratio of p-immediate assignment, S9PS (blck_21) 173Figure 387. Territory upgrade rejection %, S9PS (blck_22) 17318 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

Figure 388. Handover blocking to target WCDMA cell, S10.5 (blck_27) 174

Figure 389. Handover blocking from target WCDMA cell, S10.5 (blck_28) 174Figure 390. TCH traffic sum, S1 (trf_1) 175Figure 391. TCH traffic sum, S1 (trf_1a) 175Figure 392. TCH traffic sum of normal TRXs, S1 (trf_1b) 175Figure 393. TCH traffic sum of extended TRXs, S1 (trf_1c) 175Figure 394. Average call length, S1 (trf_2b) 176Figure 395. Average call length, S1 (trf_2d) 176Figure 396. CS territory usage, S1 (trf_3) 177Figure 397. FTCH usage, S5 (trf_3b) 177Figure 398. Average SDCCH holding time, S1 (trf_4) 178Figure 399. Average FTCH holding time, S1 (trf_5) 178Figure 400. TCH seizures for new call (call bids), S1 (trf_6) 178Figure 401. SDCCH usage %, S1 (trf_7b) 179Figure 402. SDCCH usage %, S1 (trf_7c) 179Figure 403. TCH traffic absorption on super, S4 (trf_8) 179Figure 404. TCH traffic absorption on super, S4 (trf_8a) 180Figure 405. Average cell TCH traffic from IUO, S4 (trf_9) 180Figure 406. Cell TCH traffic from IUO, S4 (trf_9a) 180Figure 407. Super TRX TCH traffic, S4 (trf_10) 181Figure 408. Sum of super TRX TCH traffic, S4 (trf_10a) 181Figure 409. Average SDCCH traffic, erlang, S2 (trf_11) 181Figure 410. Average SDCCH traffic, erlang, S2 (trf_11b) 181Figure 411. Average TCH traffic, erlang, S2 (trf_12) 182Figure 412. Average TCH traffic, erlang, S2 (trf_12a) 182Figure 413. Average CS traffic, erlang, S2 (trf_12b) 182Figure 414. Handover/call % (trf_13b) 183Figure 415. Intra-cell handover/call % (trf_13c) 183Figure 416. HO / call % (trf_13d) 183Figure 417. Handover/call % (trf_13e) 184Figure 418. IUO, average TCH seizure length on super TRXs, S4 (trf_14b) 184DN98619493 Nokia Corporation 19 (302)Issue 2-3 en Nokia Proprietary and Confidential


Figure 419. IUO, average TCH seizure length on regular TRXs, S4 (trf_15b) 185

Figure 420. Average TRX traffic, IUO, S4 (trf_16) 185Figure 421. Average TRX TCH seizure length, IUO, S4 (trf_17) 185Figure 422. Average TRX TCH seizure length, IUO, S4 (trf_17a) 185Figure 423. Average TRX TCH seizure length, IUO, S4 (trf_17b) 185Figure 424. TCH requests for a new call, S3 (trf_18) 186Figure 425. TCH requests for a new call, S3 (trf_18a) 186Figure 426. Peak busy TCH (trf_19) 186Figure 427. Average unit load (trf_20) 186Figure 428. Call time difference between TRXs, S4 (trf_21) 187Figure 429. Call time difference between TRXs, S4 (trf_21a) 187Figure 430. Number of mobiles located in a cell, BSC (trf_23a) 188Figure 431. Total TCH seizure time (call time in seconds) (trf_24b) 189Figure 432. Total TCH seizure time (call time in hours) (trf_24c) 189Figure 433. SDCCH true seizures (trf_25) 189Figure 434. SDCCH true seizures, S7 (trf_25a) 190Figure 435. SDCCH true seizures for call and SS (trf_26) 190Figure 436. SDCCH true seizures for call, SMS, SS (trf_27) 190Figure 437. Peak busy SDCCH seizures (trf_28) 190Figure 438. IUO layer usage % (trf_29) 191Figure 439. SDCCH seizures (trf_30) 191Figure 440. Call time (minutes) from p_nbsc_res_avail (trf_32) 191Figure 441. Non-AMR call time from p_nbsc_rx_qual (trf_32a) 191Figure 442. Call time from p_nbsc_rx_statistics (trf_32b) 192Figure 443. SDCCH HO seizure % out of SDCCH seizure attempts (trf_33) 192Figure 444. SDCCH assignment % out of SDCCH seizure attempts (trf_34) 192Figure 445. TCH HO seizure % out of TCH HO seizure request (trf_35) 192Figure 446. TCH norm seizure % out of TCH call request (trf_36) 193Figure 447. TCH normal seizure % out of TCH call requests (trf_36a) 193Figure 448. TCH FCS seizure % out of TCH FCS attempts (trf_37) 193Figure 449. TTCH FCS (due to SDCCH congestion) seizure % out of SDCCH seizure20 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

attempts (trf_38) 193

Figure 450. TCH seizures for new calls (trf_39) 194Figure 451. TCH seizures for new calls (trf_39a) 194Figure 452. HTCH usage, S5 (trf_40) 194Figure 453. MOC rate, S6 (trf_41) 195Figure 454. MTC rate, S6 (trf_42) 195Figure 455. TCH single band subscriber holding time, S6 (trf_43) 195Figure 456. TCH dual band subscriber holding time, S6 (trf_44) 195Figure 457. TCH data call seizures (trf_46) 196Figure 458. Share of single band traffic (trf_47) 196Figure 459. Share of dual band traffic (trf_48) 196Figure 460. Call retries due to A interface pool mismatch (trf_49) 196Figure 461. HO retries due to A interface pool mismatch (trf_50) 197Figure 462. TCH single band subscribers share of holding time, S6 (trf_51) 197Figure 463. TCH dual band subscribers share of holding time, S6 (trf_52) 197Figure 464. Calls started as FACCH call setup (trf_53) 197Figure 465. SDCCH seizures (trf_54) 198Figure 466. TCH normal seizures (trf_55) 198Figure 467. Total FTCH seizure time (trf_56) 198Figure 468. Total HTCH seizure time (trf_57) 198Figure 469. Average TCH hold time for HSCSD, S7 (trf_58) 199Figure 470. Average number of HSCSD users, S7HS (trf_60) 199Figure 471. . . . . . . . . . . Average HSCSD main channel traffic, S7HS (trf_60a) 199Figure 472. . . . . . . . . . . . . Average upgrade pending time for HSCSD (trf_62) 199Figure 473. . . . . . . . Average upgrade pending time due to congestion (trf_63) 200Figure 474. . . . . . . . . . . . .Total reporting time of ph1 and ph2 mobiles (trf_64) 200Figure 475. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Total TCH seizures (trf_65) 200Figure 476. . . . . . . . . . . . . . . . Net UL data traffic per timeslot, S9PS (trf_69a) 200Figure 477. . . . . . . . . . . . . . . . Net DL data traffic per timeslot, S9PS (trf_70a) 201Figure 478. Average UL throughput per allocated timeslot, S9PS (trf_72b) 202Figure 479. Average effective UL throughput per used tsl, S9PS (trf_72d) 202DN98619493 Nokia Corporation 21 (302)Issue 2-3 en Nokia Proprietary and Confidential


Figure 480. Average effective UL throughput per used timeslot, S10PS (trf_72f) 203

Figure 481. . . . . Average DL throughput per allocated timeslot, S9PS (trf_73b) 204Figure 482. Average effective DL throughput per used timeslot, S9PS (trf_73d) 205Figure 483.

Average effective DL throughput per used timeslot, S10PS (trf_73f)206

Figure 484. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Total RLC data, S9PS (trf_74a) 206Figure 485. Total GPRS RLC data, S9PS (trf_74b) 207Figure 486. . . . . . . . . . . . . . . . . . .GPRS territory UL utilisation, S9PS (trf_76b) 207Figure 487. . . . . . . . . . . . . . . . . . .GPRS territory DL utilisation, S9PS (trf_77a) 208Figure 488. UL GPRS traffic, S9PS (trf_78a) 209Figure 489. DL GPRS traffic, S9PS (trf_79a) 210Figure 490. TCH free margin, S9PS (trf_81) 210Figure 491. TCH usage % for CS (trf_83) 210Figure 492. Normal TCH usage % for CS (trf_83a) 211Figure 493. TCH usage % for PS, S9PS (trf_84a) 211Figure 494. Normal TCH usage % for PS, S9PS (trf_84b) 211Figure 495. Total TCH usage % for CS, S9PS (trf_85) 211Figure 496. Total TCH usage % for CS and PS, S9PS (trf_85b) 212Figure 497. Free TCH %, S9PS (trf_86a) 212Figure 498. Free TCH %, S9PS (trf_86b) 212Figure 499. Free TCH %, S10.5PS (trf_86c) 213Figure 500. Total TCH % for PS (trf_87b) 213Figure 501. Total TCH % for dedicated PS, S9PS (trf_88b) 214Figure 502. Average total UL throughput per used timeslot, S9PS (trf_89) 215Figure 503. Average total UL throughput per used TSL, S10PS (trf_89a) 216Figure 504. Average total DL throughput per used timeslot, S9PS (trf_90) 216Figure 505. Average total DL throughput per used timeslot, S10PS (trf_90a) 217Figure 506. SDCCH true seizures for call (trf_91) 217Figure 507. Average HSCSD subchannel traffic, S7HS (trf_92) 218Figure 508. Average HSCSD subchannel traffic, S7HS (trf_92a) 218Figure 509. Voice calls on SDCCH, S1 (trf_93) 21822 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

Figure 510. TCH traffic, S1 (trf_94) 218

Figure 511. GPRS traffic sum, S9PS (trf_95a) 219Figure 512. GPRS territory utilisation, S9PS (trf_96a) 220Figure 513. . . . . . . . . . . . . . . . . . . . . PS territory utilisation, S10.5PS (trf_96b) 221Figure 514. Average CS traffic, normal TRXs, erlang, S2 (trf_97) 222Figure 515. Average CS traffic, extended TRXs S2 (trf_98) 222Figure 516. Average HSCSD traffic, normal TRXs, S7HS (trf_99) 222Figure 517. Average HSCSD traffic, extended TRXs, S7HS (trf_100) 223Figure 518. Average HTCH traffic, S7HS (trf_101) 223Figure 519. Average HTCH traffic, normal TRXs, S7HS (trf_102) 223Figure 520. Average HTCH traffic, extended TRXs, S7HS (trf_103) 223Figure 521. Average HSCSD main channel traffic, normal TRXs, S7HS (trf_104) 224Figure 522. Average HSCSD main channel traffic, extended TRXs, S7HS

(trf_105) 224Figure 523. Average FTCH single traffic, S7HS (trf_106) 224Figure 524. Average FTCH single traffic, normal TRXs, S7HS (trf_107) 224Figure 525. Average FTCH single traffic, extended TRXs, S7HS (trf_108) 225Figure 526. Peak busy TCH on normal TRXs (trf_109) 225Figure 527. Peak busy TCH on normal TRXs (trf_110) 225Figure 528. Normal TCH usage % for CS (trf_111) 225Figure 529. Normal TCH usage % for CS (trf_112) 226Figure 530. CS call samples, non-AMR call (trf_113) 226Figure 531. CS call samples, AMR call (trf_114) 226Figure 532. TCH traffic time, non-AMR calls (trf_115) 227Figure 533. TCH traffic time, AMR calls (trf_116) 227Figure 534. TCH traffic time, FR AMR calls (trf_117) 228Figure 535. TCH traffic time, HR AMR calls (trf_118) 228Figure 536. TCH traffic time, all calls (trf_119) 228Figure 537. TCH traffic share of non-AMR calls (trf_120) 228Figure 538. TCH traffic share of FR AMR calls (trf_121) 229Figure 539. TCH traffic share of HR AMR calls (trf_122) 229DN98619493 Nokia Corporation 23 (302)Issue 2-3 en Nokia Proprietary and Confidential


Figure 540. Average effective UL timeslot throughput per TBF, S10PS (trf_123) 229

Figure 541. Average effective DL timeslot throughput per TBF, S10PS (trf_124) 230Figure 542. MS specific flowrate (trf_125) 230Figure 543. Total RLC payload data (Kbytes), MCS-n, S10.5PS (trf_131) 231Figure 544. UL RLC data MCS-n, S10.5PS (trf_140) 232Figure 545. DL RLC data MCS-n, S10.5PS (trf_141) 232Figure 546. Normal TCH usage % for EGPRS, S10.5PS (trf_160) 233Figure 547. . . . . . . . . . . . . . . . . . . . . . . . .UL EGPRS traffic, S10.5PS (trf_161) 233Figure 548. DL EGPRS traffic, S10.5PS (trf_162) 234Figure 549. Total EGPRS RLC data, S9PS (trf_167) 234Figure 550. SDCCH seizures for MO calls, S2 (moc_1) 235Figure 551. Successful MO speech calls, S3 (moc_2) 235Figure 552. Successful MO data calls, S3 (moc_3) 235Figure 553. MO call success ratio, S6 (moc_4) 236Figure 554. MO speech call attempts, S3 (moc_5) 236Figure 555. MO call bids, S2 (moc_6) 236Figure 556. SDCCH seizures for MT calls, S2 (mtc_1) 237Figure 557. Successful MT speech calls (mtc_2) 237Figure 558. Successful MT data calls, S3 (mtc_3) 237Figure 559. MT call success ratio, S6 (mtc_4) 237Figure 560. MT speech call attempts (mtc_5) 238Figure 561. MT call attempts, S2 (mtc_6) 238Figure 562. Number of paging messages sent, S2 (pgn_1) 238Figure 563. Paging buffer size average, S1 (pgn_2) 239Figure 564. Average paging buffer space, S1 (pgn_3) 239Figure 565. Average free space of paging GSM buffer area, S1 (pgn_3a) 239Figure 566. Paging success ratio, S1 (pgn_4) 240Figure 567. . . . . . . Average paging buffer air interface occupancy, S7 (pgn_5) 240Figure 568. . . . . . . . . . . . Average paging buffer Gb occupancy, S7PS (pgn_6) 240Figure 569. . Average air interface DRX buffer load, due to paging, S7 (pgn_7) 240Figure 570. Average air interface DRX buffer load, due to DRX AG, S7 (pgn_8) 24124 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

Figure 571. .Average air interface non-DRX buffer load due to AG, S7 (pgn_9) 241

Figure 572. Average free space of paging GPRS buffer area, S9 (pgn_10) 241Figure 573. SMS establishment failure % (sms_1) 242Figure 574. SMS TCH establishment failure % (sms_2) 242Figure 575. SMS SDCCH establishment failure % (sms_3) 242Figure 576. SMS establishment attempts (sms_4) 243Figure 577. SMS SDCCH establishment attempts (sms_5) 243Figure 578. SMS TCH establishment attempts (sms_6) 243Figure 579. DR, outgoing attempts, S3 (dr_1) 243Figure 580. DR attempts, S3 (dr_1a) 244Figure 581. DR, incoming attempts, S3 (dr_2) 244Figure 582. DR, outgoing success to another cell, S3 (dr_3) 244Figure 583. DR, incoming success from another cell, S3 (dr_4) 244Figure 584. DR, intra-cell successful HO, S3 (dr_5) 244Figure 585. % of new calls successfully handed over to another cell by DR, S3

(dr_6) 245Figure 586. DR, outgoing to another cell, failed, S3 (dr_7) 245Figure 587. DR, intra-cell failed, S3 (dr_8) 245Figure 588. TCH availability %, S4 (ava_1a) 246Figure 589. TCH availability %, S9 (ava_1c) 246Figure 590. TCH availability %, S9 (ava_1d) 247Figure 591. Average available TCH, S1 (ava_2) 247Figure 592. Average available SDCCH, S1 (ava_3) 247Figure 593. SDCCH availability %, S4 (ava_4) 247Figure 594. Average available FTCH in area, S1 (ava_5) 248Figure 595. DMR availability %, S6 (ava_6) 248Figure 596. DN2 availability %, S6 (ava_7) 248Figure 597. TRU availability %, S6 (ava_8) 248Figure 598. Average defined HTCH, S1 (ava_9) 249Figure 599. SC ET availability %, S7 (ava_10) 249Figure 600. BSC ET availability %, S7 (ava_11) 249DN98619493 Nokia Corporation 25 (302)Issue 2-3 en Nokia Proprietary and Confidential


Figure 601. SC TCSM availability %, S7 (ava_12) 249

Figure 602. BSC TCSM availability %, S7 (ava_13) 250Figure 603. TRE availability %, S6 (ava_14) 250Figure 604. Average CS territory, S9 (ava_15) 250Figure 605. . . . . . . . . . . . . . Average available PDTCH in BTS, S9PS (ava_16) 251Figure 606. Average PS territory, S9PS (ava_16a) 252Figure 607. . . . . Average available dedicated GPRS channels, S9PS (ava_17) 252Figure 608. Average available dedicated GPRS channels, S9PS (ava_17a) 252Figure 609. TRE-SEL availability %, S6 (ava_20) 253Figure 610. Number of timeslots available for CS traffic, S9 (ava_21) 253Figure 611. Number of timeslots available for CS traffic on normal TRXs, S9

(ava_21a) 253Figure 612. Number of HR timeslots available, S9 (ava_22) 254Figure 613. Number of HR timeslots available, S9 (ava_22a) 254Figure 614. Number of FR timeslots available, S9 (ava_23) 254Figure 615. Number of FR timeslots available, S9 (ava_23a) 254Figure 616. Number of dual timeslots available, S9 (ava_24) 255Figure 617. Number of dual timeslots available, S9 (ava_24a) 255Figure 618. Average number of available TCH timeslots, S9 (ava_25a) 255Figure 619.

Number of available TCH timeslots, PS and CS common , S9 (ava_26) 256

Figure 620. Number of available TCH timeslots, PS and CS common, S9(ava_26a) 256

Figure 621. Average CS TCH in normal TRXs, S9 (ava_28) 256Figure 622. Average available CS TCH in extended TRXs, S9 (ava_29) 257Figure 623. Number of HR tsls available, normal TRXs, S9 (ava_30) 257Figure 624. Number of HR tsls available, extended TRXs S9 (ava_31) 257Figure 625. Number of FR timeslots available, normal TRXs, S9 (ava_32) 258Figure 626. Number of FR timeslots available, extended TRXs, S9 (ava_33) 258Figure 627. Number of dual timeslots available, normal TRXs, S9 (ava_34) 258Figure 628. Number of dual timeslots available, extended TRXs, S9 (ava_35) 259Figure 629. Average unavailable TSL per BTS, S1 (uav_1) 25926 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

Figure 630. Average unavailable TSL per BTS, S1 (uav_1a) 259

Figure 631. Average unavailable TSL per BTS, S1 (uav_1b) 259Figure 632. Total outage time (uav_2) 260Figure 633. Number of outages (uav_3) 260Figure 634. Share of unavailability due to user (uav_4) 260Figure 635. Share of unavailability due to internal reasons (uav_5) 261Figure 636. Share of unavailability due to external reasons (uav_6) 261Figure 637. TRX unavailability time due to user (uav_7) 261Figure 638. TRX unavailability time due to internal reasons (uav_8) 261Figure 639. TRX unavailability time due to external reasons (uav_9) 262Figure 640. Average unavailable SDCCH, S5 (uav_10) 262Figure 641. Average unavailable TCH, S5 (uav_11a) 262Figure 642. Average bearer unavailability, S9PS (uav_12) 262Figure 643. Average unavailable TCH on normal TRXs, S5 (uav_13) 262Figure 644. Average unavailable TCH on extended TRXs, S5 (uav_14) 263Figure 645. Number of LU attempts, S1 (lu_1) 263Figure 646. Average of LU attempts per hour, S1 (lu_2) 263Figure 647. Number of LU attempts, S1 (lu_3) 263Figure 648. LU success %, S6 (lsr_2) 264Figure 649. Emergency calls, S6 (ec_1) 264Figure 650. Emergency call success %, S6 (ecs_1) 265Figure 651. Call re-establishment attempts, S6 (re_1) 265Figure 652. Call re-establishments, S6 (re_2) 265Figure 653. Call re-establishment success %, S6 (res_1) 265Figure 654. DL BER, S1 (dlq_1) 266Figure 655. DL cumulative quality % in class X, S1 (dlq_2) 266Figure 656. DL cumulative quality % in class X, S1 (dlq_2a) 267Figure 657. DL quality %, FER based, S10 (dlq_3) 267Figure 658. DL cumulative quality % in class X, HR AMR, S10 (dlq_4) 267Figure 659. DL cumulative quality % in class X, FR AMR, S10 (dlq_5) 268Figure 660. DL cumulative quality % in class X,S10 (dlq_6) 268DN98619493 Nokia Corporation 27 (302)Issue 2-3 en Nokia Proprietary and Confidential


Figure 661. DL quality 0-5 %, HR, FER based, S10 (dlq_7) 268

Figure 662. DL quality 0-5 %, FR, FER based, S10 (dlq_8) 269Figure 663. DL quality 0-5 % EFR, FER based, S10 (dlq_9) 269Figure 664. DL quality 0-5 % AMR HR, FER based, S10 (dlq_10) 269Figure 665. DL quality 0-5 % AMR FR, FER based, S10 (dlq_11) 269Figure 666. UL BER, S1 (ulq_1) 270Figure 667. UL cumulative quality % in class X, S1 (ulq_2) 270Figure 668. UL cumulative quality % in class X, S1 (ulq_2a) 271Figure 669. UL quality %, FER based, S10 (ulq_3) 271Figure 670. UL cumulative quality % in class X, HR AMR, S10 (ulq_4) 271Figure 671. UL cumulative quality % in class X, FR AMR, S10 (ulq_5) 272Figure 672. UL cumulative quality % in class X, non-AMR S10 (ulq_6) 272Figure 673. UL quality 0-5 %, HR, FER based, S10 (ulq_7) 272Figure 674. UL quality 0-5 %, FR, FER based, S10 (ulq_8) 273Figure 675. UL quality 0-5 % EFR, FER based, S10 (ulq_9) 273Figure 676. UL quality 0-5 % AMR HR, FER based, S10 (ulq_10) 273Figure 677. UL quality 0-5 % AMR FR, FER based, S10 (ulq_11) 273Figure 678. Share % per range, S4 (dll_1) 274Figure 679. Sorting factor for undefined adjacent cell, S4 (dll_2) 274Figure 680. Share % per range, S4 (ull_1) 274Figure 681. Average MS power, S2 (pwr_1) 275Figure 682. Average MS power, S2 (pwr_1b) 275Figure 683. Average BS power, S2 (pwr_2) 275Figure 684. Average DL signal strength, S2 (lev_1) 275Figure 685. Average DL signal strength, S2 (lev_1a) 276Figure 686. Average UL signal strength, S2 (lev_2) 276Figure 687. Average UL signal strength, S2 (lev_2a) 276Figure 688. Average MS-BS distance (dis_1) 276Figure 689. Average MS-BS distance (dis_1a) 277Figure 690. MS-BS distance class upper range (dis_3a) 277Figure 691. Link balance, S1 (lb_1) 27828 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

Figure 692. Share in acceptance range, S4 (lb_2) 278

Figure 693. Share in normal, S4 (lb_3) 278Figure 694. Share in MS limited, S4 (lb_4) 278Figure 695. Share in BS limited, S4 (lb_5) 279Figure 696. Share in maximum power, S4 (lb_6) 279Figure 697. Average MS power attenuation, S2 (lb_7) 279Figure 698. Average MS power, S2 (lb_7b) 279Figure 699. Average UL signal strength, S2 (lb_9) 280Figure 700. Average DL signal strength, S2 (lb_10) 280Figure 701. Average MS power attenuation, S2 (lb_11) 280Figure 702. Average BS power attenuation, S2 (lb_12) 280Figure 703. Average link imbalance, S2 (lb_13) 281Figure 704. SDCCH access probability, before FCS (csf_1) 281Figure 705. SDCCH access probability (csf_1a) 282Figure 706. SDCCH success ratio (csf_2a) 282Figure 707. SDCCH success ratio (csf_2d) 283Figure 708. SDCCH success ratio, area (csf_2e) 283Figure 709. SDCCH success ratio, BTS, S6 (csf_2g) 284Figure 710. SDCCH success ratio, BTS (csf_2i) 285Figure 711. SDCCH success ratio, area (csf_2m) 286Figure 712. SDCCH success ratio, BTS (csf_2n) 287Figure 713. TCH access probability without DR (csf_3a) 288Figure 714. TCH access probability without DR and Q (csf_3b) 288Figure 715. TCH access probability without Q (csf_3c) 288Figure 716. TCH access probability, real (csf_3d) 289Figure 717. TCH access probability without DR (csf_3i) 289Figure 718. TCH access probability without DR and Q (csf_3j) 289Figure 719. TCH access probability, real (csf_3k) 290Figure 720. TCH access probability, real (csf_3l) 290Figure 721. TCH access probability without DR and Q (csf_3m) 291Figure 722. TCH success ratio, area, before call re-establisment (csf_4o) 291DN98619493 Nokia Corporation 29 (302)Issue 2-3 en Nokia Proprietary and Confidential


Figure 723. TCH success ratio, area, after call re-establishment, S6 (csf_4p) 292

Figure 724. TCH success ratio, BTS, before call re-establisment (csf_4q) 292Figure 725. TCH success ratio, BTS, after call re-establishment (csf_4r) 293Figure 726. TCH success ratio, BTS, after call re-establishment (csf_4t) 293Figure 727. TCH success ratio, area, before call re-establishment, S7(csf_4u) 294Figure 728. TCH success ratio, area, after call re-establishment, S7 (csf_4v) 294Figure 729. TCH success ratio, BTS, after call re-establishment (csf_4x) 295Figure 730. TCH success ratio, BTS, before call re-establishment (csf_4y) 295Figure 731. Activation related SDCCH access probability, S7, (csf_12) 296Figure 732. SDCCH call success probability, S10.5 (csf_13a) 296Figure 733. Reuse pattern (cnf_1) 296Figure 734. Reuse pattern, S1 (cnf_2) 29730 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

About this manualNote

1 About this manualThis document defines the formulas used to calculating the Key PerformanceIndicators based on the Nokia NetAct PM database.

This document contains also formulas which are not used in any actual reports ofthe Nokia NetAct post-processing tools. You can see the formulas used in post-processing from the actual reports of the tools.

This document serves as a reference to the available formulas and does notinclude information on whether the formula is in use or not.

The information contained in this document relates to BSS Network Doctorsoftware version 3.1.5, Nokia NetAct release OSS3.1 and to release S10.5 ED ofthe Nokia BSC software. This document should not be used with any otherversions of the Nokia NetAct or Nokia BSC software.

This document is intended for the network operators of the Nokia NetAct.

This chapter covers the following topics:

Summary of changes

What you need to know first

Where to find more

Typographic conventions

Concepts and terminology

1.1 Summary of changesIn this Change Delivery (OSS CD 0163)As a result of the changes made to BSS Network Doctor software from version to3.1.3. to 3.1.5, the following changes have been made into this document:DN98619493 Nokia Corporation 31 (302)Issue 2-3 en Nokia Proprietary and Confidential


New formulas

Blocking

- blck_27 and blck_28

Dynamic Abis Pool

- dap_1 and dap_2

Handover

- ho_13_f replaced with ho_13g- ho_35 replaced with ho_49

HFR

- hfr_69 and hfr_70

RLC

- rlc_18 to rlc_25- rlc_39- rlc_41 to rlc_49

TBF

- tbf_27c- tbf_28c- tbf_41 and tbf_42

Traffic

- trf_72f- trf_73f- trf_86c- trf_89a- trf_90a- trf_96b- trf_131- trf_140 and trf_141- trf_160 to trf_162- trf_167

In the previous Change Delivery (OSS CD 0091)As a result of the changes made to BSS Network Doctor software from version to3.1.2. to 3.1.3, the following changes have been made into this document:

Changed formulas32 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

About this manual

Traffic- trf_13d changed to trf_13e

Call success

- csf_2j changed to csf_2m- csf_2k changed to csf_2n- csf_13 changed to csf_13a

New formulas Downlink quality

- dlq_3 to dlq_5 and dlq_7 to dlq_11

Drop call failures

- dcf_11

Handover failures

- hof_9

HSCSD (new)- hsd_15, hsd_49 and hsd_50

Multislot

- msl_5 and msl_6

Position based services

- pbs_3 and pbs_6

Traffic

- trf_2b, trf_7c, trf_11b, trf_17, trf_60a. trf_92a and trf_125

Uplink quality

- ulq_3 to ulq_5 and ulq_7 to ulq_11

1.2 What you need to know first

This document assumes that you are familiar with the following areas:

The concepts of the Nokia NetAct and GSM networks in general

A text processing utility, such as vi or dtpad. These text processors areused for editing certain configuration files.DN98619493 Nokia Corporation 33 (302)Issue 2-3 en Nokia Proprietary and Confidential


1.3 Where to find moreWhen you perform the users tasks described in this document, you may need torefer to other documentation for further information. Below is a list of manualsthat you will find useful, as well as a brief description of the manuals contents.

Other BSS Network Doctor documents

Administering BSS Network Doctor, DN98619369, for systemadministrators tasks related to running BSS Network Doctor.

BSS Network Doctor Reports, DN98614186, for a detailed description onutilising the Network Doctor reports.

OSS NED library documents

Database Description for BSC Measurements, DN98619454, for adescription of the structure of performance management (PM) tables in theNokia NetAct PM database and the records, including counters, in eachtable.

Other Nokia documents

Call Related DX Causes in BSC, Functional Description, DN9814277, foran explanation of phases and for a list of causes in TCH and SDCCHobservations to find details for dropping calls.#1

DX Cause Coding Mapping, DN9813878, for an explanation to therelationship between DX cause codes and PM counters and for the analysisof TCH and SDCCH observations.#2

1.4 Typographic conventions

The following tables present the typographic conventions which have been usedin this manual to describe different actions and restrictions.

1.4.1 Text styles

The following table presents the typefaces and fonts and their indications.34 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

About this manual1.5 Terms and concepts

The lists below presents the terms and abbreviations used in this document.

1.5.1 Abbreviations

Table 1. Text styles in this document

Style Explanation

Initial Upper-caseLettering

Application names

Italiced text EmphasisState, status or mode

Courier File and directory namesNames of database tablesParametersUser namesSystem outputUser input

UPPER-CASELETTERING

Keys on the keyboard (ALT, TAB, CTRL etc.)

Bold text User interface components

Initial Upper-caseLettering in Italics

Referenced documentsReferenced sections and chapters within a document

Variable user input

Table 2. Abbreviations

Abbreviation Explanation

AG Access Grant

AMR Adaptive Multirate

BCCH Broadcast Control Channel

BCF Base Control Function

BER Bit Error RatioDN98619493 Nokia Corporation 35 (302)Issue 2-3 en Nokia Proprietary and Confidential


Table 2. Abbreviations (Continued)BSC Base Station Controller

BSS Base Station Subsystem

BTS Base Transceiver Station

CI Cell Identity

DL Downlink

DR Directed Retry

FCS Frame Check Sequence

GPRS General Packet Radio Service

HO Handover

HSCSD High Speed Circuit Switched Data

IUO Intelligent Underlay Overlay

KPI Key Performance Indicator

LU Location Update

MML Man-machine Language

MOC Mobile Originated Call

MR Maintenance Region

MS Mobile Station

MSC Mobile Services Switching Centre

OMC Operation and Maintenance Centre

PBS Position Based Services

PI Performance Indicator

PLMN Public Land Mobile Network

PM Performance Management

RACH Random Access Control Channel

SDCCH Stand Alone Dedicated Control Channel

SMS Short Message Service

SQL Standard Query Language

SS Supplementary Service

TCH Traffic Channel

TR Trunk Reservation

Abbreviation Explanation36 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

About this manual

Table 2. Abbreviations (Continued)1.5.2 Terms

The lists below presents the abbreviations and terms used in this document.

TRX Transceiver

TSL Timeslot

UL Uplink

Abbreviation Explanation

Table 3. Terms used in this document

Term Explanation

AGCH A downlink control channel that is used to carry aresponse to a mobile channel allocation request.The AGCH assigns the mobile to operate on aspecific TDMA timeslot.

Bit Error Ratio The ratio of the number of the bit errors to the totalnumber of bits transmitted within a given time period.

Broadcast Control Channel (BCCH) A channel from a base station to a mobile station(MS) used for transmission of messages to allmobile stations located in the cell coverage area.

Cell Identity (CI) A number which identifies a cell to the networkswithin a location area (LA).

Clear Code Code that describes why the call set-up or the callitself has been disconnected.

Day The counting of data per day is based on theperiod_start_time field in the measurementtables. This field always tells the starting hour of themeasurement period. Under one day there are hoursfrom 00 to 23.

Directed Retry A procedure used in a call set-up phase forassigning a mobile station to a traffic channel of acell other than the serving cell when the traffic iscongested.

Frame Check Sequence Extra characters added to a frame for the purposesof error control. The FCS is used in HDCL, FrameRelay, and other data link layer protocols.DN98619493 Nokia Corporation 37 (302)Issue 2-3 en Nokia Proprietary and Confidential


Table 3. Terms used in this document (Continued)For any other terms, refer to Glossary, DN9763965.

Key Performance Indicator The performance of the network is calculated fromthe Nokia NetAct based on the Network Elementcounter information. Sometimes the plain counter assuch describes an important performance aspect(number of calls, for example) of the network butsometimes a formula of counters is needed (e.g.drop call ratio).

Maintenance Region Each object in the NetAct database belongs to oneand only one Maintenance Region (MR).

Mobile Terminated Call A call in which the called subscriber used a mobiletelephone.

Nokia NetAct A product of Nokia Telecommunications for theoperation and maintenance of cellular networks.

SQL*Plus An interactive program for accessing the database.

Stand-alone Dedicated ControlChannel (SDCCH)

A control channel (CCH) used for roaming,authentication, encryption activation and call control.

Timeslot (TSL) A timeslot in the time division multiple access(TDMA) frame in the GSM radio interface.

Traffic Channel A logical radio channel assigned to a base stationand primarily intended for conversation.

Trunk Reservation A stochastic algorithm employed in a channelallocation from a cell.

Term Explanation38 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

BSS counter formulasNote

2 BSS counter formulasThis chapter lists all BSS Network Doctor formulas. The more commonly usedones are described in further detail concerning their use or known problems withthem, for example. In connection with the name of a formula there is also areference to the BSC release (S1 to S10.5) since when the counters of the formulahave been available.

The use of formulas backwards, S4 formulas with S3 for example, gives either noresults because the measurement is not available, or false results because somecounters, which are new in S4, will be filled with value -1 by the OMC for S3BSCs.

When running the reports with newer counters, be careful especially when youhave two BSC software releases running in the network simultaneously. Thesimplest way to avoid problems is to start to use new counters of a new BSCrelease only when the new software release is used in the entire network under theNokia NetAct framework release.

2.1 Additional GPRS channels (ach)Additional GPRS channel use, S9PS (ach_1)Use: BTS level, especially BH values can be used for adjusting the

CDEF parameter.Example: If the value equals to one, on average one additional timeslot

has been used for GPRS. If the situation continues, it indicatesa need to extend the default or the dedicated territory.

Known problems: The numerator is incremented when the TBF is released.Therefore, if there is, for example, one long TBF but no othertraffic, the value of this KPI can be totally incorrect becausethe whole TBF duration is counted on one measurementperiod.

Experiences on use: ach_1 is included in ava_16.

total hold time of all additional GPRS ch. seizures (sec)DN98619493 Nokia Corporation 39 (302)Issue 2-3 en Nokia Proprietary and Confidential


----------------------------------------------------------- =

period durationsum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100---------------------------------------

sum(period_duration*60)

Counters from table(s):p_nbsc_res_avail

Unit: timeslot

Figure 1. Additional GPRS channel use, S9PS (ach_1)

Average additional GPRS channel hold time, S9PS (ach_2)Use: If the value is high, more default area is needed.

total hold time of all additional GPRS ch. seizures (sec)--------------------------------------------------------------- =

total nbr of all additional GPRS channel seizures

sum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100--------------------------------------------------------------------------

sum(decode(AVE_ADD_GPRS_CH_HOLD_TIME_SUM ,0,0,AVE_ADD_GPRS_CH_HOLD_TIME_DEN)

Counters from table(s):p_nbsc_res_availUnit: sec

Figure 2. Average additional GPRS channel hold time, S9PS (ach_2)

Additional GPRS channels seized, S9PS (ach_3)Use: How many times an additional channel has been released (a

case of territory downgrade).Known problems: Shows slightly incorrect values in the case of an extended cell.

sum(decode(AVE_ADD_GPRS_CH_HOLD_TIME_SUM,0,0,AVE_ADD_GPRS_CH_HOLD_TIME_DEN)

Counters from table(s):p_nbsc_res_avail

Figure 3. Additional GPRS channels seized, S9PS (ach_3)

Total additional GPRS channel hold time, S9PS (ach_4)Use: How many times an additional channel has been released (a

case of territory downgrade).Known problems: Shows slightly incorrect values in the case of an extended cell.

sum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100

Counters from table(s):40 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en

BSS counter formulas

p_nbsc_res_availUnit: secFigure 4. Total additional GPRS channel hold time, S9PS (ach_4)

2.2 Multislot (msl)Distribution of UL multislot requests, S9PS (msl_1)Use: Indicates the share of a multislot request type to all multislot

requests.

req_X_TSL_UL100 * -------------------------------------------------------------------------- %

sum(req_1_TSL_UL+req_2_TSL_UL+req_1_TSL_UL +req_4_TSL_UL+ req_5_8_TSL_UL)

req_X_TSL_UL = one of the componentsof the denominator.

Counters from table(s):p_nbsc_packet_control_unit

Figure 5. Distribution of UL multislot requests, S9PS (msl_1)

Distribution of DL multislot requests, S9PS (msl_2)Use: Indicates the share of a multislot request type to all multislot

requests.

req_X_TSL_DL100 * -------------------------------------------------------------------------- %

sum(req_1_TSL_DL+req_2_TSL_DL+req_1_TSL_DL +req_4_TSL_DL+ req_5_8_TSL_DL)

req_X_TSL_UL = one of the components of the denominator.


Figure 6. Distribution of DL multislot requests, S9PS (msl_2)

Distribution of UL multislot allocations, S9PS (msl_3)Use: Indicates the share of a multislot request type to all multislot

requests.

alloc X TSL UL100 * ---------------------------------------------------- %

sum(alloc_1_TSL_UL + alloc_2_TSL_UL + alloc_1_TSL_UL+alloc_4_TSL_UL + alloc_5_8_TSL_UL)

req_X_TSL_UL = one of the components of the denominator.DN98619493 Nokia Corporation 41 (302)Issue 2-3 en Nokia Proprietary and Confidential


Counters from table(s):p_nbsc_packet_control_unitFigure 7. Distribution of UL multislot allocations, S9PS (msl_3)

Distribution of DL multislot allocations, S9PS (msl_4)Use: Indicates the share of a multislot request type to all multislot

requests.

alloc_X_TSL_DL100 * ------------------------------------------------------ %

sum(alloc_1_TSL_DL+alloc_2_TSL_DL+alloc_1_TSL_DL+alloc_4_TSL_DL+ alloc_5_8_TSL_DL)

req_X_TSL_DL = one of the components of the denominator.


Figure 8. Distribution of DL multislot allocations, S9PS (msl_4)

Ratio of unreserved GPRS UL TSL requests, S9PS (msl_5)Use: Indicates the share of a multislot request type to all multislot

requests.

sum(alloc_1_TSL_UL+2*alloc_2_TSL_UL+3*alloc_3_TSL_UL +4*alloc_4_TSL_UL)100 * ----------------------------------------------------------------------- %

sum(req_1_TSL_UL+2*req_2_TSL_UL+3*req_3_TSL_UL +4*req_4_TSL_UL)


Figure 9. Ratio of unreserved GPRS UL TSL requests, S9PS (msl_5)

Ratio of unreserved GPRS DL TSL requests, S9PS (msl_6)Use: Indicates the share of a multislot request type to all multislot

requests.

sum(alloc_1_TSL_DL+2*alloc_2_TSL_DL+3*alloc_3_TSL_DL +4*alloc_4_TSL_DL)100 * ----------------------------------------------------------------------- %

sum(req_1_TSL_DL+2*req_2_TSL_DL+3*req_3_TSL_DL +4*req_4_TSL_DL)


Figure 10. Ratio of unreserved GPRS DL TSL requests, S9PS (msl_6)42 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en


UL multislot allocations, S9PS (msl_9)Use: Total number of multislot allocations in UL.sum(alloc_1_TSL_UL+ alloc_2_TSL_UL+ alloc_3_TSL_UL

+ alloc_4_TSL_UL+ alloc_5_8_TSL_UL)


Figure 11. UL multislot allocations, S9PS (msl_9)

DL multislot allocations, S9PS (msl_10)Use: Total number of multislot allocations in DL.

sum(alloc_1_TSL_DL+ alloc_2_TSL_DL+ alloc_3_TSL_DL

+ alloc_4_TSL_DL+ alloc_5_8_TSL_DL)


Figure 12. DL multislot allocations, S9PS (msl_10)

Average number of allocated timeslots, UL S9PS (msl_11)

sum(alloc_1_TSL_UL + 2*alloc_2_TSL_UL + 3*alloc_3_TSL_UL + 4*alloc_4_TSL_UL)----------------------------------------------------------------------------

sum(alloc_1_TSL_UL + alloc_2_TSL_UL + alloc_3_TSL_UL+alloc_4_TSL_UL)


Figure 13. Average number of allocated timeslots, UL S9PS (msl_11)

Average number of allocated timeslots, DL S9PS (msl_12)

sum(alloc_1_TSL_DL + 2*alloc_2_TSL_DL + 3*alloc_3_TSL_DL + 4*alloc_4_TSL_DL)----------------------------------------------------------------------------

sum(alloc_1_TSL_DL + alloc_2_TSL_DL + alloc_3_TSL_DL + alloc_4_TSL_DL)


Figure 14. Average number of allocated timeslots, DL S9PS (msl_13)DN98619493 Nokia Corporation 43 (302)Issue 2-3 en Nokia Proprietary and Confidential


Average number of requested UL timeslots, S9PS (msl_13)Known problems: If one phase access is used (MS on CCCH), only the requestedone single timeslot can be requested. Otherwise the MS classdefines how many timeslots are requested. This makes themeaning of the KPI less accurate.

sum(req_1_TSL_UL + 2*req_2_TSL_UL + 3*req_3_TSL_UL + 4*req_4_TSL_UL)--------------------------------------------------------------------

sum(req_1_TSL_UL + req_2_TSL_UL + req_3_TSL_UL + req_4_TSL_UL)


Figure 15. Average number of requested UL timeslots, S9PS (msl_13)

Average number of requested DL timeslots, S9PS (msl_14)Known problems: If one phase access is used (MS on CCCH), only the requested

one single timeslot can be requested. Otherwise the MS classdefines how many timeslots are requested. This makes themeaning of the KPI less accurate.

sum(req_1_TSL_DL + 2*req_2_TSL_DL + 3*req_3_TSL_DL + 4*req_4_TSL_DL)--------------------------------------------------------------------

sum(req_1_TSL_DL + req_2_TSL_DL + req_3_TSL_DL + req_4_TSL_DL)


Figure 16. Average number of requested DL timeslots, S9PS (msl_14)

UL multislot allocation %, S9PS (msl_15a)Use: Indicates how well the requested multislots could be

allocated.Known problems: Works until there are MSs with multislot class greater than 4.

100* average allocated tsl / average requested tsl % =

sum(alloc_1_TSL_UL+2*alloc_2_TSL_UL+3*alloc_3_TSL_UL +4*alloc_4_TSL_UL)------------------------------------------------------------------

sum(alloc_1_TSL_UL+alloc_2_TSL_UL+alloc_3_TSL_UL+alloc_4_TSL_UL++NO_RADIO_RES_AVA_UL_TBF)

100* ------------------------------------------------------------------------- %sum(req_1_TSL_UL+2*req_2_TSL_UL+3*req_3_TSL_UL +4*req_4_TSL_UL)----------------------------------------------------------------

sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL+req_4_TSL_UL)


Figure 17. UL multislot allocation %, S9PS (msl_15a)44 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en


DL multislot allocation %, S9PS (msl_16a)Use: Indicates how well the requested multislots could beallocated.Known problems: Works until there are MSs with multislot class greater than 4.

100* average allocated tsl / average requested tsl % =

sum(alloc_1_TSL_DL+2*alloc_2_TSL_DL+3*alloc_3_TSL_DL +4*alloc_4_TSL_DL)------------------------------------------------------------------

sum(alloc_1_TSL_DL+alloc_2_TSL_DL+alloc_3_TSL_DL+alloc_4_TSL_DL+ NO_RADIO_RES_AVA_DL_TBF)

100* ------------------------------------------------------------------------- %sum(req_1_TSL_DL+2*req_2_TSL_DL+3*req_3_TSL_DL +4*req_4_TSL_DL)----------------------------------------------------------------

sum(req_1_TSL_DL+req_2_TSL_DL+req_3_TSL_DL+req_4_TSL_DL)


Figure 18. DL multislot allocation %, S9PS (msl_16a)

UL multislot requests, S9PS (msl_17)Use: Total number of multislot requests in UL.



Figure 19. UL multislot requests, S9PS (msl_17)

DL multislot requests, S9PS (msl_18)Use: Total number of multislot requests in DL.



Figure 20. DL multislot requests, S9PS (msl_18)

2.3 TBF (tbf)Average number of LLC blocks per UL TBF, S9PS (tbf_3)Use: Indicates the average number of LLC data blocks per

normally released TBF.DN98619493 Nokia Corporation 45 (302)Issue 2-3 en Nokia Proprietary and Confidential


sum(Ave_UL_LLC_per_TBF_sum)----------------------------sum(Ave_UL_LLC_per_TBF_den)


Figure 21. Average number of LLC blocks per UL TBF, S9PS (tbf_3)

Average number of LLC blocks per DL TBF, S9PS (tbf_4)Use: Indicates the average number of LLC data blocks per

normally released TBF.

sum(Ave_DL_LLC_per_TBF_sum)----------------------------

sum(Ave_DL_LLC_per_TBF_den)


Unit: second

Figure 22. Average number of LLC blocks per DL TBF, S9PS (tbf_4)

Average UL TBF duration, S9PS (tbf_5)Known problems: The unit has changed to 10 ms in BSC CD 1.2. After that

tbf_5a is needed.

sum(ave_dur_ul_tbf_sum)------------------------

sum(ave_dur_ul_tbf_den)


Unit: second

Figure 23. Average UL TBF duration, S9PS (tbf_5)

Average UL TBF duration, S9PS (tbf_5a)Use: Counted from the normally released TBFs.Known problems: Contains part of TBF establishment delays.

sum(ave_dur_ul_tbf_sum)/100----------------------------

sum(ave_dur_ul_tbf_den)

Counters from table(s):p_nbsc_packet_control_unit46 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en


Unit: secondFigure 24. Average UL TBF duration, S9PS (tbf_5a)

Average DL TBF duration, S9PS (tbf_6a)Use: Counted from the normally released TBFs.Known problems: Contains part of TBF establishment delays.

sum(ave_dur_dl_tbf_sum)/100---------------------------

sum(ave_dur_dl_tbf_den)


Unit: second

Figure 25. Average DL TBF duration, S9PS (tbf_6a)

Average UL TBF duration, unack mode, S9PS (tbf_7)

um(ave_dur_ul_tbf_unack_mode_sum/100)-------------------------------------

sum(ave_dur_ul_tbf_unack_mode_den)


Unit: second

Figure 26. Average UL TBF duration, unack mode, S9PS (tbf_7)

Average DL TBF duration, unack mode, S9PS (tbf_8)

sum(ave_dur_dl_tbf_unack_mode_sum/100)--------------------------------------

sum(ave_dur_dl_tbf_unack_mode_den)


Unit: second

Figure 27. Average DL TBF duration, unack mode, S9PS (tbf_8)DN98619493 Nokia Corporation 47 (302)Issue 2-3 en Nokia Proprietary and Confidential


UL mlslot allocation blocking, S9PS (tbf_15)Use: If the blocking is met regularly, there is a need either toexpand the territory (CS traffic low) or TCH capacity (CStraffic high).

Note: If the statistics show that there is blocking but no upgraderequests yet, the reason may be that the territory has beensmaller than the default setting defines (CS use). The PCUwill not make an upgrade request. This is because the CS sidewill return the default channels back to the PS territory assoon as the CS load allows that.

sum(NO_RADIO_RES_AVA_UL_TBF)100 * ------------------------------------------------------------------------- %



Figure 28. UL mlslot allocation blocking, S9PS (tbf_15)

DL mlslot allocation blocking, S9PS (tbf_16)Use: If the blocking is met regularly, there is a need either to

expand the territory (CS traffic low) or TCH capacity (CStraffic high).

Note: If the statistics show that there is blocking but no upgraderequests yet, the reason may be that the territory has beensmaller than the default setting defines (CS use). The PCUwill not make an upgrade request. This is because the CS sidewill return the default channels back to the PS territory assoon as the CS load allows that.

sum(NO_RADIO_RES_AVA_DL_TBF)100 * ------------------------------------------------------------------------- %



Figure 29. DL mlslot allocation blocking, S9PS (tbf_16)

UL TBF releases due to CS traffic %, S9PS (tbf_19)Use: In GPRS the CS takes priority over the radio interface

resources outside the dedicated territory. This KPI indicatesthe impact of CS traffic on PS (TBF drops) when radiointerface capacity (TCH) is not sufficient and CS traffic takesthe capacity from PS traffic by force.

sum(UL_TBF_rel_due_CSW_traffic)100 * -------------------------------- %

sum(Nbr_of_UL_TBF)48 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en


Counters from table(s):

p_nbsc_packet_control_unit

Figure 30. UL TBF releases due to CS traffic %, S9PS (tbf_19)

DL TBF releases due to CS traffic %, S9PS (tbf_20)Use: In GPRS the CS takes priority over the radio interface

resources outside the dedicated territory. This KPI indicatesthe impact of CS traffic on PS (TBF drops) when radiointerface capacity (TCH) is not sufficient and CS traffic takesthe capacity from PS traffic by force.

sum(DL_TBF_rel_due_CSW_traffic)100 * ---------------------------------- %

sum(Nbr_of_DL_TBF)


Figure 31. DL TBF releases due to CS traffic %, S9PS (tbf_20)

UL drops per 10 Kbytes, MS lost, S9PS (tbf_27a)Use: This KPI tries to build something similar that we are used to

seeing in the CS side to indicate the bad radio conditions thataffect the connection i.e. drops in ratio to volume.

Known problems: - Slow cell reselections (flushes) can increment thenumerator.- Combining TBF related information (numerator) to RLCblock information (numerator) causes problems because thebehaviour of TBFs is quite independent of the RLC blocks(TBF length varies strongly).- 1000 used for 1 kbyte instead of 1024.

sum(UL_TBF_rel_due_no_resp_MS)--------------------------------------------------------------------------

sum(rlc_data_blocks_ul_cs1*20 + rlc_data_blocks_ul_cs2*30 )/ 10000


Figure 32. UL drops per 10 Kbytes, MS lost, S9PS (tbf_27a)DN98619493 Nokia Corporation 49 (302)Issue 2-3 en Nokia Proprietary and Confidential


UL drops per 10 Kbytes, MS lost, S9PS (tbf_27b)Use: This KPI tries to build something similar that we are used toseeing in the CS side to indicate the bad radio conditions thataffect the connection i.e. drops in ratio to volume.

Known problems: - Slow cell reselections (flushes) can increment thenumerator.- Combining TBF related information (numerator) to RLCblock information (numerator) causes problems because thebehaviour of TBFs is quite independent of the RLC blocks(TBF length varies strongly).-In S10 the EGPRS modulation coding scheme counters haveto be added to the denominator.

sum(UL_TBF_rel_due_no_resp_MS)-----------------------------------------------------------------------

sum(rlc_data_blocks_ul_cs1*20 + rlc_data_blocks_ul_cs2*30 )/ 10240


Unit: drops per 10Kbytes

Figure 33. UL drops per 10 Kbytes, MS lost, S9PS (tbf_27b)

UL drops per 10 Kbytes, MS lost, S10.5PS (tbf_27c)Use: To indicate the bad radio conditions that affect the connection

i.e. drops in ratio to volume.Known problems: - Slow cell reselections (flushes) can increment the

numerator.- Combining TBF related information (numerator) to RLCblock information (numerator) causes problems, because thebehaviour of TBFs is quite independent of the RLC blocks(TBF length varies strongly).

sum(UL_TBF_rel_due_no_resp_MS)-----------------------------------------

(sum(rlc_data_blocks_ul_cs1*20+ rlc_data_blocks_ul_cs2*30+ sum over MCS-1 (xx)* 22++ sum over MCS-2 (xx)* 28++ sum over MCS-3 (xx)* 37++ sum over MCS-4 (xx)* 44++ sum over MCS-5 (xx)* 56++ sum over MCS-6 (xx)* 74++ sum over MCS-7 (xx/2)*112++ sum over MCS-8 (xx/2)*136++ sum over MCS-9 (xx/2)*148))/ 10240

Where xx = (UL_RLC_BLOCKS_IN_ACK_MODE + UL_RLC_BLOCKS_IN_UNACK_MODE)

Counters from table(s):p_nbsc_packet_control_unitp_nbsc_coding_scheme50 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en


Unit: drops per 10KbytesFigure 34. UL drops per 10 Kbytes, MS lost, S10.5PS (tbf_27c)

DL drops per 10 Kbytes, MS lost, S9PS (tbf_28a)Use: See tbf_27bKnown problems: - Slow cell reselections (flushes) can increment the

numerator.- Combining TBF related information (numerator) to RLCblock info (numerator) causes problems because thebehaviour of TBFs is quite independent of the RLC blocks(TBF length varies strongly).- In S10 the EGPRS modulation coding scheme counters haveto be added to the denominator.- 1000 used for 1 kbyte instead of 1024.

sum(DL_TBF_rel_due_no_resp_MS)---------------------------------------------------------------------------

sum(rlc_data_blocks_dl_cs1*20 + rlc_data_blocks_dl_cs2*30) / 10000


Figure 35. DL drops per 10 Kbytes, MS lost, S9PS (tbf_28a)

DL drops per 10 Kbytes, MS lost, S9PS (tbf_28b)Use: See tbf_27b.Known problems: - Slow cell reselections (flushes) can increment the

numerator.- Combining TBF related info (numerator) to RLC block info(numerator) causes problems because the behaviour of TBFsis quite independent of the RLC blocks (TBF length variesstrongly).- In S10 the EGPRS modulation coding scheme counters haveto be added to the denominator.

sum(DL_TBF_rel_due_no_resp_MS)--------------------------------------------------------------------------

sum(rlc_data_blocks_dl_cs1*20 + rlc_data_blocks_dl_cs2*30 )/ 10240

Counters from table(s):p_nbsc_packet_control_unitDN98619493 Nokia Corporation 51 (302)Issue 2-3 en Nokia Proprietary and Confidential


Unit: Drops per 10KbytesFigure 36. DL drops per 10 Kbytes, MS lost, S9PS (tbf_28b)

DL drops per 10 Kbytes, MS lost, S10.5PS (tbf_28c)Use: See tbf_27b.Known problems: - Slow cell reselections (flushes) can increment the

numerator.- Combining TBF related info (numerator) to RLC block info(numerator) causes problems because the behaviour of TBFsis quite independent of the RLC blocks (TBF length variesstrongly).

sum(DL_TBF_rel_due_no_resp_MS)----------------------------------------

(sum(rlc_data_blocks_dl_cs1*20+ rlc_data_blocks_dl_cs2*30+ sum over MCS-1 (yy)* 22++ sum over MCS-2 (yy)* 28++ sum over MCS-3 (yy)* 37++ sum over MCS-4 (yy)* 44+

+ sum over MCS-5 (yy)* 56++ sum over MCS-6 (yy)* 74++ sum over MCS-7 (yy/2)*112++ sum over MCS-8 (yy/2)*136++ sum over MCS-9 (yy/2)*148)) / 10240

Where yy = (DL_RLC_BLOCKS_IN_ACK_MODE + DL_RLC_BLOCKS_IN_UNACK_MODE)

Counters from table(s):p_nbsc_packet_control_unitp_nbsc_coding_schemes

Unit: drops per 10Kbytes

Figure 37. DL drops per 10 Kbytes, MS lost, S10.5PS (tbf_28c)

UL TBF reallocation failure ratio, S9PS (tbf_29)

sum(UL_TBF_REALLOC_FAILS)100 * ------------------------------------------------- %

sum(UL_TBF_RE_ALLOCATIONS + UL_TBF_REALLOC_FAILS)


Figure 38. UL TBF reallocation failure ratio, S9PS (tbf_29)52 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en


DL TBF reallocation failure ratio, S9PS (tbf_30)sum(DL_TBF_REALLOC_FAILS)100 * ------------------------------------------------- %

sum(DL_TBF_RE_ALLOCATIONS + DL_TBF_REALLOC_FAILS)


Figure 39. DL TBF reallocation failure ratio, S9PS (tbf_30)

UL TBF reallocation attempts, S9PS (tbf_31)

sum(UL_TBF_RE_ALLOCATIONS + UL_TBF_REALLOC_FAILS)


Figure 40. UL TBF reallocation attempts, S9PS (tbf_31)

DL TBF reallocation attempts, S9PS (tbf_32)

sum(DL_TBF_RE_ALLOCATIONS + DL_TBF_REALLOC_FAILS)


Figure 41. DL TBF reallocation attempts, S9PS (tbf_32)

TBF success % S9PS (tbf_34)Use: Also called TBF retainability.

This KPI is used to measure the quality of the radio interfacefor TBF sessions. The KPI measures purely the retainabilityof TBFs and is not dependent on interfaces and NEs outsideBSS.

Known problems: Not usable on BTS level in S10 if common a BCCH is usedbecause TBF can start in one BTS of a segment and end inanother.

100 - TBF failure % =

TBF establishments -Normal TBF releases- releases due to flush releases due to suspend

100 - 100 * -------------------------------------------------------- % =TBF establishments

- releases due to flush releases due to suspend

sum(NBR_OF_UL_TBF + NBR_OF_DL_TBF ;TBF establishments- decode(AVE_DUR_UL_TBF_SUM,0,0,AVE_DUR_UL_TBF_DEN)- decode(AVE_DUR_DL_TBF_SUM,0,0,AVE_DUR_DL_TBF_DEN)DN98619493 Nokia Corporation 53 (302)Issue 2-3 en Nokia Proprietary and Confidential


- UL_TBF_REL_DUE_TO_FLUSH - DL_TBF_REL_DUE_TO_FLUSH- UL_TBF_REL_DUE_TO_SUSPEND - DL_TBF_REL_DUE_TO_SUSPEND)

100 - 100 * ----------------------------------------------------------- %

sum(NBR_OF_UL_TBF + NBR_OF_DL_TBF

- UL_TBF_REL_DUE_TO_FLUSH - DL_TBF_REL_DUE_TO_FLUSH- UL_TBF_REL_DUE_TO_SUSPEND - DL_TBF_REL_DUE_TO_SUSPEND)


Figure 42. TBF success % S9PS (tbf_34)

UL TBF releases due to flush %, S9PS (tbf_35)Use: This KPI indicates that there is mobility from this cell to other

cells by cell reselection. Cell reselection affects thethroughput.

sum(UL_TBF_REL_DUE_TO_FLUSH)100 * -------------------------------- %

sum(Nbr_of_UL_TBF)


Figure 43. UL TBF releases due to flush %, S9PS (tbf_35)

DL TBF releases due to flush %, S9PS (tbf_36)Use: This KPI indicates that there is mobility from this cell to other

cells by cell reselection. Cell reselection affects thethroughput.

sum (DL_TBF_REL_DUE_TO_FLUSH)100 * ---------------------------------- %

sum(Nbr_of_DL_TBF)


Figure 44. DL TBF releases due to flush %, S9PS (tbf_36)

Average UL TBF per timeslot, S9PS (tbf_37b)Use: Indicates how many UL TBFs on average there are per

timeslot.

sum(aver_tbfs_per_tsl_ul_sum)/sum(aver_tbfs_per_tsl_ul_den)54 (302) Nokia Corporation DN98619493Nokia Proprietary and Confidential Issue 2-3en


Counters from table(s):p_nbsc_packet_control_unitFigure 45. Average UL TBF per timeslot, S9PS (tbf_37b)

Average DL TBF per timeslot, S9PS (tbf_38b)Use: Indicates how many DL TBFs on average there are per

timeslot.

sum(aver_tbfs_per_tsl_dl_sum)/sum(aver_tbfs_per_tsl_dl_den)

Co

bss network doctor formulas nokia

Documents

nokia logo

copyright nokia corporation

en nokia proprietary

handover success

handover failures hof

handover ho

failures sd

failures dcf