SlideShare uma empresa Scribd logo
1 de 206
Baixar para ler offline
BSS Network Doctor Formulas




DN98619493     © Nokia Networks Oy                  1 (206)
Issue 1-1 en   Nokia Proprietary and Confidential
BSS Network Doctor Formulas




          The information in this document is subject to change without notice and describes only the
          product defined in the introduction of this documentation. This document is intended for the
          use of Nokia Networks' customers only for the purposes of the agreement under which the
          document is submitted, and no part of it may be reproduced or transmitted in any form or
          means without the prior written permission of Nokia Networks. The document has been
          prepared to be used by professional and properly trained personnel, and the customer
          assumes full responsibility when using it. Nokia Networks welcomes customer comments as
          part of the process of continuous development and improvement of the documentation.
          The information or statements given in this document concerning the suitability, capacity, or
          performance of the mentioned hardware or software products cannot be considered binding
          but shall be defined in the agreement made between Nokia Networks and the customer.
          However, Nokia Networks has made all reasonable efforts to ensure that the instructions
          contained in the document are adequate and free of material errors and omissions. Nokia
          Networks will, if necessary, explain issues which may not be covered by the document.
          Nokia Networks' liability for any errors in the document is limited to the documentary correction
          of errors. Nokia Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN
          THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL
          (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the
          information in it.
          This document and the product it describes are considered protected by copyright according to
          the applicable laws.
          NOKIA logo is a registered trademark of Nokia Corporation.
          Other product names mentioned in this document may be trademarks of their respective
          companies, and they are mentioned for identification purposes only.


          Copyright © Nokia Networks Oy 2001. All rights reserved.




2 (206)   © Nokia Networks Oy                                                                DN98619493
          Nokia Proprietary and Confidential                                                  Issue 1-1 en
Contents


                   Contents 3

                   List of tables 5

                   List of figures 6

          1        About this manual 27
          1.1      What you need to know first 27
          1.2      Where to find more 28
          1.3      Typographic conventions 28
          1.3.1    Text styles 28
          1.4      Terms and concepts 29
          1.4.1    Abbreviations 29
          1.4.2    Terms 31

          2        BSS counter formulas 33
          2.1      Additional GPRS channels (ach) 33
          2.2      Multislot (msl) 35
          2.3      TBF (tbf) 38
          2.4      RLC (rlc) 42
          2.5      Frame relay (frl) 46
          2.6      Random access (rach) 47
          2.7      SDCCH drop failures (sd) 49
          2.7.1    SDCCH drop counters 50
          2.7.2    Problems with the SDCCH drop counters 52
          2.8      SDCCH drop ratio (sdr) 53
          2.9      Setup success ratio (cssr) 54
          2.10     TCH drop failures 55
          2.10.1   TCH drop call counters 55
          2.10.2   Drop call ratio 58
          2.10.3   Drop-out ratio 58
          2.10.4   Problems with the drop call counters 59
          2.11     Drop call failures (dcf) 59
          2.12     TCH drop call % (dcr) 60
          2.13     Handover (ho) 71
          2.14     Handover failure % (hfr) 83
          2.15     Handover success % (hsr) 108
          2.16     Handover failures (hof) 113
          2.17     Interference (itf) 117
          2.18     Congestion (cngt) 118
          2.19     Queuing (que) 120
          2.20     Blocking (blck) 123
          2.21     Traffic (trf) 133
          2.22     Traffic directions 160
          2.22.1   Mobile originated calls (moc) 160
          2.22.2   Mobile terminated calls (mtc) 162
          2.23     Paging (pgn) 164
          2.24     Short message service (sms) 166




DN98619493         © Nokia Networks Oy                        3 (206)
Issue 1-1 en       Nokia Proprietary and Confidential
BSS Network Doctor Formulas




          2.25     Directed retry (dr) 168
          2.26     Availability (ava) 170
          2.27     Unavailability (uav) 174
          2.28     Location updates (lu) 177
          2.29     LU success % (lsr) 177
          2.30     Emergency call (ec) 178
          2.31     Emergency call success % (ecs) 178
          2.32     Call re-establishment (re) 179
          2.33     Call re-establishment success % (res) 179
          2.34     Quality 179
          2.34.1   Downlink quality (dlq) 179
          2.34.2   Uplink quality (ulq) 180
          2.35     Downlink and uplink level 182
          2.35.1   Downlink level (dll) 182
          2.35.2   Uplink level (ull) 182
          2.36     Power (pwr) 182
          2.37     Level (lev) 183
          2.38     Distance (dis) 184
          2.39     Link balance, power, level (lb) 184
          2.40     Call success (csf) 187
          2.41     Configuration (cnf) 202

          3        Missing Counters 203
          3.1      XX1 203
          3.2      XX2 203
          3.3      XX3 203
          3.4      XX4 204

                   Index 205




4 (206)            © Nokia Networks Oy                                        DN98619493
                   Nokia Proprietary and Confidential                          Issue 1-1 en
List of tables


          Table 1.   Text styles in this document          29
          Table 2.   Abbreviations       29
          Table 3.   Terms used in this document           31
          Table 4.   SDCCH Drop Counters              51
          Table 5.   TCH drop call counters          56




DN98619493           © Nokia Networks Oy                        5 (206)
Issue 1-1 en         Nokia Proprietary and Confidential
BSS Network Doctor Formulas




List of figures


          Figure 1.   Additional GPRS channel use, S9PS (ach_1) 34
          Figure 2.   Average additional GPRS channel hold time, S9PS (ach_2) 34
          Figure 3.   Additional GPRS channels seized, S9PS (ach_3) 34
          Figure 4.   Total additional GPRS channel hold time, S9PS (ach_4) 34
          Figure 5.   Distribution of UL multislot requests, S9PS (msl_1) 35
          Figure 6.   Distribution of DL multislot requests, S9PS (msl_2) 35
          Figure 7.   Distribution of UL multislot allocations, S9PS (msl_3) 35
          Figure 8.   Distribution of DL multislot allocations, S9PS (msl_4) 36
          Figure 9.   UL multislot allocations, S9PS (msl_9) 36
          Figure 10. DL multislot allocations, S9PS (msl_10) 36
          Figure 11. Average number of allocated timeslots, UL S9PS (msl_11) 36
          Figure 12. Average number of allocated timeslots, DL S9PS (msl_13) 37
          Figure 13. Average number of requested UL timeslots, S9PS (msl_13) 37
          Figure 14. Average number of requested DL timeslots, S9PS (msl_14) 37
          Figure 15. UL multislot allocation %, S9PS (msl_15) 37
          Figure 16. DL multislot allocation %, S9PS (msl_16) 38
          Figure 17. UL multislot requests, S9PS (msl_17) 38
          Figure 18. DL multislot requests, S9PS (msl_18) 38
          Figure 19. Average number of LLC blocks per UL TBF, S9PS (tbf_3) 39
          Figure 20. Average number of LLC blocks per DL TBF, S9PS (tbf_4) 39
          Figure 21. Average UL TBF duration, S9PS (tbf_5) 39
          Figure 22. Average UL TBF duration, S9PS (tbf_5a) 39
          Figure 23. Average DL TBF duration, S9PS (tbf_6a) 40
          Figure 24. Average UL TBF duration, unack mode, S9PS (tbf_7) 40
          Figure 25. Average DL TBF duration, unack mode, S9PS (tbf_8) 40
          Figure 26. UL mlslot allocation blocking, S9PS (tbf_15) 40
          Figure 27. DL mlslot allocation blocking, S9PS 41
          Figure 28. Normally released UL TBF ratio, S9PS (tbf_25) 41
          Figure 29. Normally released DL TBF ratio, S9PS (tbf_26) 41




6 (206)               © Nokia Networks Oy                                             DN98619493
                      Nokia Proprietary and Confidential                               Issue 1-1 en
Figure 30. UL TBF reallocation failure ratio, S9PS (tbf_29) 42
          Figure 31. DL TBF reallocation failure ratio, S9PS (tbf_30) 42
          Figure 32. UL TBF reallocation attempts, S9PS (tbf_31) 42
          Figure 33. DL TBF reallocation attempts, S9PS (tbf_32) 42
          Figure 34. Ack.CS1 RLC blocks UL, S9PS (rlc_1) 43
          Figure 35. Ack.CS1 RLC blocks DL, S9PS (rlc_2) 43
          Figure 36. Ack. CS1 RLC DL Block error rate, S9PS (rlc_3a) 43
          Figure 37. Unack. CS1 RLC UL block error rate, S9PS (rlc_4a) 43
          Figure 38. Ack. CS1 RLC UL block error rate, S9PS (rlc_5a) 43
          Figure 39. UL CS1 RLC data share, S9PS (rlc_6) 44
          Figure 40. UL CS2 RLC data share, S9PS 44
          Figure 41. DL CS1 RLC data share, S9PS (rlc_8) 44
          Figure 42. DL CS2 RLC data share, S9PS (rlc_9) 44
          Figure 43. UL CS1 RLC block error rate, S9PS (rlc_10) 45
          Figure 44. UL CS2 RLC block error rate, S9PS (rlc_11) 45
          Figure 45. DL CS1 RLC block error rate, S9PS (rlc_12) 45
          Figure 46. DL CS2 RLC block error rate, S9PS (rlc_13) 45
          Figure 47. UL RLC blocks, S9PS (rlc_14) 46
          Figure 48. DL RLC blocks, S9PS (rlc_15) 46
          Figure 49. Bytes in discarded sent frames, S9PS (frl_5) 46
          Figure 50. Bytes in discarded received frames, S9PS (frl_6) 46
          Figure 51. Average RACH slot, S1 (rach_1) 47
          Figure 52. Peak RACH load, average, S1 (rach_2) 47
          Figure 53. Peak RACH load %, S1 (rach_3) 47
          Figure 54. Average RACH load %, S1 (rach_4) 48
          Figure 55. Average RACH busy, S1 (rach_5) 48
          Figure 56. RACH rejected due to illegal establishment, S5 (rach_6) 48
          Figure 57. Total RACH rejection ratio, S7 (rach_7) 49
          Figure 58. Ghosts detected on SDCCH and other failures, S1 (sd_1) 49
          Figure 59. Ghosts detected on SDCCH and other failures, S1 (sd_1a) 50
          Figure 60. Ghosts detected on SDCCH and other failures, S1 (sd_1b) 50




DN98619493           © Nokia Networks Oy                                          7 (206)
Issue 1-1 en         Nokia Proprietary and Confidential
BSS Network Doctor Formulas




          Figure 61. SDCCH Drop %, S3 (sdr_1a) 53
          Figure 62. SDCCH Drop %, abis fail excluded, S3 (sdr_2) 54
          Figure 63. Illegal establishment cause %, (sdr_3b) 54
          Figure 64. SDCCH, TCH Setup Success %, S4 (cssr_2) 55
          Figure 65. TCH drop calls in HO, S2 (dcf_2) 59
          Figure 66. TCH drop calls in BSC outgoing HO, S3 (dcf_3) 59
          Figure 67. TCH drop calls in intra-cell HO, S3 (dcf_4) 60
          Figure 68. TCH drop calls in intra BSC HO, S3 (dcf_6) 60
          Figure 69. Drop calls in BSC incoming HO, S3 (dcf_7) 60
          Figure 70. TCH drop call %, area, real, after re-establishment S3 (dcr_3f) 61
          Figure 71. TCH drop call %, area, real, before re-establishment, S3 (dcr_3g) 62
          Figure 72. TCH drop call %, area, real, after re-establishment, S7 (dcr_3h) 62
          Figure 73. TCH drop call %, area, real, before re-establishment, S3 (dcr_3i) 63
          Figure 74. TCH drop call %, area, real, after re-establishment, S7 (dcr_3j) 65
          Figure 75. TCH drop-out %, BTS level, before call re-establishment, S3 (dcr_4c) 65
          Figure 76. TCH drop-out %, BTS level, before call re-establishment, S3 (dcr_4d) 66
          Figure 77. TCH drop-out %, BTS level, before call re-establishment, S7 (dcr_4e) 66
          Figure 78. TCH drop-out %, BTS level, before call re-establishment, S7 (dcr_4f) 67
          Figure 79. TCH drop call (dropped conversation) %, BSC level, S4 (dcr_5) 68
          Figure 80. TCH dropped conversation %, area, re-establishment considered, S7
                       (dcr_5b) 69
          Figure 81. TCH drop call %, after TCH assignment, without re-establishment, area
                       level, S7 (dcr_8) 69
          Figure 82. TCH drop call %, after TCH assignment, with re-establishment, area level,
                       S7 (dcr_8b) 69
          Figure 83. Drops per erlang , before re-establishment, S4 (dcr_10) 70
          Figure 84. Drops per erlang , after re-establishment, S4 (dcr_10a) 70
          Figure 85. Drops per erlang , after re-establishment, S7 (dcr_10b) 71
          Figure 86. Return from super TRXs to regular TRX, S4 (ho_1) 71
          Figure 87. HO attempts from regular TRXs to super, S4 (ho_2) 71
          Figure 88. HO attempts from super to regular, S4 (ho_3) 71
          Figure 89. Share of HO attempts from super to regular due to DL Qual, S4
                       (ho_4) 72




8 (206)              © Nokia Networks Oy                                             DN98619493
                     Nokia Proprietary and Confidential                               Issue 1-1 en
Figure 90. Share of HO attempts from super to regular due to DL interference, S4
                       (ho_5) 72
          Figure 91. Share of HO attempts from super to regular due to UL interference, S4
                       (ho_6) 72
          Figure 92. Share of HO attempts from super to regular due to bad C/I, S4 (ho_7) 73
          Figure 93. MSC incoming HO attempts, (ho_8) 73
          Figure 94. MSC outgoing HO attempts, (ho_9) 73
          Figure 95. BSC incoming HO attempts, (ho_10) 73
          Figure 96. BSC outgoing HO attempts, (ho_11) 73
          Figure 97. Intra-cell HO attempts, S2 (ho_12a) 74
          Figure 98. HO attempts, , outgoing and intra-cell S4, (ho_13) 74
          Figure 99. HO attempts S3, (ho_13a) 74
          Figure 100. HO attempts, outgoing and intra-cell, S5, (ho_13c) 74
          Figure 101. HO attempts, outgoing and intra-cell, S6, (ho_13d) 75
          Figure 102. HO attempts , outgoing and intra-cell S3, (ho_13e) 75
          Figure 103. HO attempts , outgoing and intra-cell S9, (ho_13f) 75
          Figure 104. TCH requests for HO (ho_14a) 76
          Figure 105. TCH requests for HO (ho_14b) 76
          Figure 106. TCH seizures for HO (ho_15) 76
          Figure 107. TCH-TCH HO attempts (ho_16) 76
          Figure 108. SDCCH-TCH HO attempts (ho_17) 77
          Figure 109. SDCCH-SDCCH HO attempts (ho_18) 77
          Figure 110. TCH-TCH HO successes (ho_19) 77
          Figure 111. SDCCH-TCH HO successes (ho_20) 77
          Figure 112. SDCCH-SDCCH HO successes (ho_21) 78
          Figure 113. MSC controlled HO attempts (ho_22) 78
          Figure 114. BSC controlled HO attempts (ho_23) 78
          Figure 115. Intra-cell HO attempts (ho_24) 78
          Figure 116. MSC controlled HO successes (ho_25) 79
          Figure 117. BSC controlled HO successes (ho_26) 79
          Figure 118. Intra-cell HO successes (ho_27) 79
          Figure 119. MSC incoming HO successes (ho_28) 79




DN98619493           © Nokia Networks Oy                                              9 (206)
Issue 1-1 en         Nokia Proprietary and Confidential
BSS Network Doctor Formulas




           Figure 120. MSC outgoing HO successes (ho_29) 79
           Figure 121. BSC incoming HO successes (ho_30) 80
           Figure 122. BSC outgoing HO successes (ho_31) 80
           Figure 123. Incoming HO success (ho_32) 80
           Figure 124. Outgoing HO successes (ho_33) 80
           Figure 125. Outgoing HO attempts (ho_34) 80
           Figure 126. Incoming HO attempts (ho_35) 81
           Figure 127. Outgoing SDCCH-SDCCH HO attempts (ho_36) 81
           Figure 128. Incoming SDCCH-SDCCH HO attempts (ho_37) 81
           Figure 129. Outgoing SDCCH-TCH HO attempts (ho_38) 81
           Figure 130. Incoming SDCCH-TCH HO attempts (ho_39) 81
           Figure 131. Outgoing TCH-TCH HO attempts (ho_40) 82
           Figure 132. Incoming TCH-TCH HO attempts (ho_41) 82
           Figure 133. Outgoing SDCCH-SDCCH HO success (ho_42) 82
           Figure 134. Incoming SDCCH-SDCCH HO success (ho_43) 82
           Figure 135. Outgoing SDCCH-TCH HO success (ho_44) 82
           Figure 136. Incoming SDCCH-TCH HO success (ho_45) 83
           Figure 137. Outgoing TCH-TCH HO success (ho_46) 83
           Figure 138. Incoming TCH-TCH HO success (ho_47) 83
           Figure 139. Total HO failure %, S1 (hfr_1) 84
           Figure 140. Total HO failure %, S1 (hfr_2) 85
           Figure 141. Intra-cell HO failure share, S1 (hfr_3a) 85
           Figure 142. Intra-cell HO failure share, S1 (hfr_3b) 86
           Figure 143. Intra-cell HO failure share, S1 (hfr_3c) 86
           Figure 144. Intra-cell HO failure share, S1 (hfr_3d) 86
           Figure 145. Incoming MSC ctrl HO failure %, S1 (hfr_4) 87
           Figure 146. Incoming MSC ctrl HO failure share, S1 (hfr_4a) 87
           Figure 147. Incoming MSC ctrl HO failure share, S1 (hfr_4b) 88
           Figure 148. Incoming MSC ctrl HO failure share, S1 (hfr_4c) 88
           Figure 149. Incoming MSC ctrl HO failure share, S1 (hfr_4d) 88
           Figure 150. Outgoing MSC ctrl HO failure share %, S1 (hfr_5a) 89




10 (206)              © Nokia Networks Oy                                             DN98619493
                      Nokia Proprietary and Confidential                               Issue 1-1 en
Figure 151. Outgoing MSC ctrl HO failure share %, S1 (hfr_5b) 89
          Figure 152. Outgoing MSC ctrl HO failure share %, S1 (hfr_5c) 90
          Figure 153. Outgoing MSC ctrl HO failure share %, S1 (hfr_5d) 90
          Figure 154. Incoming BSC ctrl HO failure %, S1 (hfr_6) 90
          Figure 155. Incoming BSC ctrl HO failure share %, S1 (hfr_6a) 91
          Figure 156. Incoming BSC ctrl HO failure %, S1 (hfr_6b 91
          Figure 157. Incoming BSC ctrl HO failure share %, S1 (hfr_6c) 92
          Figure 158. Incoming BSC ctrl HO failure %, S1 (hfr_6d) 92
          Figure 159. Outgoing BSC ctrl HO failure share, S1 (hfr_7) 92
          Figure 160. Outgoing BSC ctrl HO failure share, S1 (hfr_7a) 93
          Figure 161. Outgoing BSC ctrl HO failure share, S1 (hfr_7b) 93
          Figure 162. Outgoing BSC ctrl HO failure share, S1 (hfr_7c) 94
          Figure 163. Outgoing BSC ctrl HO failure share, S1 (hfr_7d) 94
          Figure 164. Internal inter HO failure %, S4 (hfr_8) 94
          Figure 165. Internal intra HO failure %, S4 (hfr_9) 94
          Figure 166. External source HO failure %, S4 (hfr_10) 95
          Figure 167. HO failure % from super to regular, S4 (hfr_12) 95
          Figure 168. HO failure % from regular to super, S4 (hfr_13) 95
          Figure 169. Share of HO failures from regular to super due to return, S4 (hfr_14) 95
          Figure 170. Share of HO failures from regular to super due to MS lost, S4 (hfr_15) 96
          Figure 171. Share of HO failures from regular to super due to another cause, S4
                        (hfr_16) 96
          Figure 172. Share of HO failures from super to regular due to return, S4 (hfr_17) 96
          Figure 173. Share of HO failures from super to regular due to MS lost, S4 (hfr_18) 97
          Figure 174. Share of HO failures from super to regular due to another cause, S4
                        (hfr_19) 97
          Figure 175. SDCCH-SDCCH HO failure %, S2 (hfr_20) 97
          Figure 176. SDCCH-TCH HO failure %, S2 (hfr_21) 98
          Figure 177. TCH-TCH HO failure %, S2 (hfr_22) 98
          Figure 178. SDCCH-SDCCH incoming HO failure %, S2 (hfr_23) 98
          Figure 179. SDCCH-SDCCH outgoing HO failure ratio, S2 (hfr_24) 99
          Figure 180. SDCCH-TCH incoming HO failure %, S2 (hfr_25) 99




DN98619493           © Nokia Networks Oy                                                11 (206)
Issue 1-1 en         Nokia Proprietary and Confidential
BSS Network Doctor Formulas




           Figure 181. SDCCH-TCH outgoing HO failure %, S2 (hfr_26) 99
           Figure 182. TCH-TCH incoming HO failure %, S2 (hfr_27) 99
           Figure 183. TCH-TCH outgoing HO failure %, S2 (hfr_28) 100
           Figure 184. MSC ctrl HO failure %, blocking (hfr_29) 100
           Figure 185. MSC ctrl HO failure %, not allowed (hfr_30) 100
           Figure 186. MSC ctrl HO failure %, return to old (hfr_31) 100
           Figure 187. MSC ctrl HO failure %, call clear (hfr_32) 101
           Figure 188. MSC ctrl HO failure %, end HO (hfr_33) 101
           Figure 189. MSC ctrl HO failure %, end HO BSS (hfr_34) 101
           Figure 190. MSC ctrl HO failure %, wrong A interface (hfr_35) 101
           Figure 191. MSC ctrl HO failure %, adjacent cell error (hfr_36) 102
           Figure 192. BSC ctrl HO failure %, blocking (hfr_37) 102
           Figure 193. BSC ctrl HO failure %, not allowed (hfr_38) 102
           Figure 194. BSC ctrl HO failure %, return to old (hfr_39) 102
           Figure 195. BSC ctrl HO failure %, call clear (hfr_40) 103
           Figure 196. BSC ctrl HO failure %, end HO (hfr_41) 103
           Figure 197. BSC ctrl HO failure %, end HO BSS (hfr_42) 103
           Figure 198. BSC ctrl HO failure %, wrong A interface (hfr_43) 103
           Figure 199. BSC ctrl HO drop call %, (hfr_44) 104
           Figure 200. Intra-cell HO failure %, cell_fail_lack (hfr_45) 104
           Figure 201. Intra-cell HO failure %, not allowed (hfr_46) 104
           Figure 202. Intra-cell HO failure %, return to old (hfr_47) 104
           Figure 203. Intra-cell HO failure %, call clear (hfr_48) 105
           Figure 204. Intra-cell HO failure %, MS lost (hfr_49) 105
           Figure 205. Intra-cell HO failure %, BSS problem (hfr_50) 105
           Figure 206. Intra-cell HO failure %, drop call (hfr_51) 105
           Figure 207. HO failure % to adjacent cell (hfr_52) 106
           Figure 208. HO failure % from adjacent cell (hfr_53) 106
           Figure 209. HO failure %, blocking excluded (hfr_54a) 106
           Figure 210. HO failure % due to radio interface blocking (hfr_55) 107
           Figure 211. Intra-cell HO failure %, wrong A interface (hfr_56) 107




12 (206)              © Nokia Networks Oy                                                DN98619493
                      Nokia Proprietary and Confidential                                  Issue 1-1 en
Figure 212. Intra-cell HO failure % (hfr_57) 107
          Figure 213. HO failures to target cell, S6 (hfr_58) 108
          Figure 214. HO failures from target cell, S6 (hfr_59) 108
          Figure 215. MSC controlled outgoing SDCCH-SDCCH HO success %, S1
                       (hsr_1) 108
          Figure 216. MSC controlled outgoing SDCCH-TCH HO success %, S1 (hsr_2) 109
          Figure 217. MSC controlled outgoing TCH-TCH HO success %, S1 (hsr_3) 109
          Figure 218. BSC controlled outgoing SDCCH-SDCCH HO success %, S1
                        (hsr_4) 109
          Figure 219. BSC controlled outgoing SDCCH-TCH HO success %, S1 (hsr_5) 109
          Figure 220. BSC controlled outgoing TCH-TCH HO success %, S1 (hsr_6) 109
          Figure 221. Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_7) 110
          Figure 222. Intra-cell SDCCH-TCH HO success %, S1 (hsr_8) 110
          Figure 223. Intra-cell TCH-TCH HO success %, S1 (hsr_9) 110
          Figure 224. MSC controlled incoming SDCCH-SDCCH HO success %, S1
                       (hsr_10) 110
          Figure 225. MSC controlled incoming SDCCH-TCH HO success %, S1 (hsr_11) 110
          Figure 226. MSC controlled incoming TCH-TCH HO success %, S1 (hsr_12) 111
          Figure 227. BSC controlled incoming SDCCH-SDCCH HO success %, S1
                        (hsr_13) 111
          Figure 228. BSC controlled incoming SDCCH-TCH HO success %, S1 (hsr_14) 111
          Figure 229. BSC controlled incoming TCH-TCH HO success %, S1 (hsr_15) 111
          Figure 230. BSC controlled incoming HO success %, S1 (hsr_16) 111
          Figure 231. MSC controlled incoming HO success %, S1 (hsr_17) 112
          Figure 232. Incoming HO success %, S1 (hsr_18) 112
          Figure 233. Outgoing HO success %, S1 (hsr_19) 112
          Figure 234. Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_20) 112
          Figure 235. Intra-cell SDCCH-TCH HO success %, S1 (hsr_21) 113
          Figure 236. Intra-cell TCH-TCH HO success %, S1 (hsr_22) 113
          Figure 237. Outgoing HO failures due to lack of resources (hof_1) 113
          Figure 238. Incoming HO failures due to lack of resources (hof_2) 113
          Figure 239. TCH HO failures when return to old channel was successful (hof_3) 114
          Figure 240. SDCCH HO failures when return to old channel was successful




DN98619493           © Nokia Networks Oy                                            13 (206)
Issue 1-1 en         Nokia Proprietary and Confidential
BSS Network Doctor Formulas




                         (hof_4) 114
           Figure 241. MSC incoming HO failures (hof_5) 114
           Figure 242. MSC outgoing HO failures (hof_6) 114
           Figure 243. MSC outgoing HO failures (hof_6a) 115
           Figure 244. BSC incoming HO failures (hof_7) 115
           Figure 245. BSC incoming HO failures (hof_7a) 115
           Figure 246. BSC outgoing HO failures (hof_8) 115
           Figure 247. BSC outgoing HO failures (hof_8a) 115
           Figure 248. Intra-cell HO failures (hof_9a) 116
           Figure 249. Failed outgoing HO, return to old (hof_10) 116
           Figure 250. Outgoing HO failures (hof_12) 116
           Figure 251. Intra-cell HO failure, return to old channel (hof_13) 116
           Figure 252. Intra-cell HO failure, drop call (hof_14) 116
           Figure 253. Incoming HO failures (hof_15) 117
           Figure 254. UL interference, BTS level, S1 (itf_1) 117
           Figure 255. Idle TSL percentage of time in band X, TRX level, IUO, S4 (itf_2) 118
           Figure 256. UL interference from IUO, TRX level, S4 (itf_3) 118
           Figure 257. UL interference from Power Control, TRX level, S6 (itf_4) 118
           Figure 258. TCH congestion time, S1 (cngt_1) 119
           Figure 259. SDCCH congestion time, S1 (cngt_2) 119
           Figure 260. FTCH time congestion % (cngt_3a) 119
           Figure 261. FTCH time congestion % (cngt_3a) 119
           Figure 262. HTCH time congestion % (cngt_4a) 120
           Figure 263. HTCH time congestion % (cngt_4a) 120
           Figure 264. Queued, served TCH call requests % (que_1) 120
           Figure 265. Queued, served TCH HO requests % (que_2) 121
           Figure 266. Queued, served TCH HO requests %, (que_2a) 121
           Figure 267. Successful queued TCH requests (que_3) 121
           Figure 268. Successful non-queued TCH requests (que_4) 121
           Figure 269. Successful queued TCH HO requests (que_5) 122
           Figure 270. Successful non-queued TCH HO requests (que_6) 122




14 (206)              © Nokia Networks Oy                                              DN98619493
                      Nokia Proprietary and Confidential                                Issue 1-1 en
Figure 271. Non-queued, served TCH call requests % (que_7) 122
          Figure 272. Non-queued, served TCH HO requests % (que_8) 122
          Figure 273. Non-queued, served TCH HO requests %, (que_8a) 123
          Figure 274. TCH raw blocking, S1 (blck_1) 123
          Figure 275. SDCCH blocking %, S1 (blck_5) 123
          Figure 276. SDCCH real blocking %, S1 (blck_5a) 124
          Figure 277. TCH raw blocking % on super TRXs, S4 (blck_6) 124
          Figure 278. TCH raw blocking % on regular TRXs, S4 (blck_7) 124
          Figure 279. TCH call blocking, before DR, S2 (blck_8) 125
          Figure 280. TCH call blocking %, DR compensated, S2 (blck_8b) 126
          Figure 281. TCH call blocking %, DR and DAC compensated, EFR excluded, S5
                        (blck_8d) 127
          Figure 282. Blocked calls, S5 (blck_9b) 127
          Figure 283. Blocked calls , S5 (blck_9c) 128
          Figure 284. Blocked TCH HOs, S2 (blck_10a) 128
          Figure 285. Blocked TCH HOs, S5 (blck_10b) 128
          Figure 286. TCH HO blocking, S2 (blck_11a) 129
          Figure 287. TCH HO blocking without Q, S2 (blck_11b) 129
          Figure 288. TCH HO blocking, S5 (blck_11c) 129
          Figure 289. Blocked incoming and internal HO, S2 (blck_12) 130
          Figure 290. Blocked incoming and internal HO, S2 (blck_12a) 130
          Figure 291. AG blocking, S1 (blck_13) 130
          Figure 292. FCS blocking, S5 (blck_14) 130
          Figure 293. Blocked SDCCH seizure attempts, S5 (blck_15) 131
          Figure 294. HO blocking % (blck_16a) 131
          Figure 295. Handover blocking %, (blck_16b) 131
          Figure 296. Blocked FACCH call setup TCH requests, (blck_18) 132
          Figure 297. Handover blocking to target cell, (blck_19) 132
          Figure 298. Handover blocking from target cell, (blck_20) 132
          Figure 299. NACK ratio of p-immediate assignment, S9PS (blck_21) 132
          Figure 300. Territory upgrade rejection %, S9PS (blck_22) 133




DN98619493           © Nokia Networks Oy                                         15 (206)
Issue 1-1 en         Nokia Proprietary and Confidential
BSS Network Doctor Formulas




           Figure 301. TCH traffic sum, S1 (trf_1) 133
           Figure 302. TCH traffic sum, S1 (trf_1a) 134
           Figure 303. Average call length, S1 (trf_2d) 134
           Figure 304. TCH usage, S1 (trf_3) 135
           Figure 305. FTCH usage, S5 (trf_3b) 135
           Figure 306. Average SDCCH holding time, S1 (trf_4) 135
           Figure 307. Average FTCH holding time, S1 (trf_5) 136
           Figure 308. TCH seizures for new call (call bids), S1 (trf_6) 136
           Figure 309. SDCCH usage %, S1 (trf_7b) 136
           Figure 310. TCH traffic absorption on super, S4 (trf_8) 137
           Figure 311. TCH traffic absorption on super, S4 (trf_8a) 137
           Figure 312. Average cell TCH traffic from IUO, S4 (trf_9) 137
           Figure 313. Cell TCH traffic from IUO, S4 (trf_9a) 138
           Figure 314. Super TRX TCH traffic, S4 (trf_10) 138
           Figure 315. Sum of super TRX TCH traffic, S4 (trf_10a) 138
           Figure 316. Average SDCCH traffic, erlang, S2 (trf_11) 138
           Figure 317. Average SDCCH traffic, erlang, S2 (trf_11a) 139
           Figure 318. Average TCH traffic, erlang, S2 (trf_12) 139
           Figure 319. Average TCH traffic, erlang, S2 (trf_12a) 139
           Figure 320. Average TCH traffic, erlang, S2 (trf_12b) 139
           Figure 321. Handover/call %, (trf_13b) 140
           Figure 322. Intra-cell handover/call %, (trf_13c) 140
           Figure 323. Handover/call %, (trf_13d) 141
           Figure 324. IUO, average TCH seizure length on super TRXs, S4 (trf_14b) 141
           Figure 325. IUO, average TCH seizure length on regular TRXs, S4 (trf_15b) 141
           Figure 326. Average TRX traffic, IUO, S4 (trf_16) 142
           Figure 327. Average TRX TCH seizure length, IUO, S4 (trf_17a) 142
           Figure 328. Average TRX TCH seizure length, IUO, S4 (trf_17b) 142
           Figure 329. TCH requests for a new call, S3 (trf_18) 142
           Figure 330. TCH requests for a new call, S3 (trf_18a) 143
           Figure 331. Peak busy TCH (trf_19) 143




16 (206)              © Nokia Networks Oy                                               DN98619493
                      Nokia Proprietary and Confidential                                 Issue 1-1 en
Figure 332. Average unit load (trf_20) 143
          Figure 333. Call time difference between TRXs, S4 (trf_21) 144
          Figure 334. Call time difference between TRXs, S4 (trf_21a) 144
          Figure 335. Number of mobiles located in a cell, BSC, (trf_23a) 145
          Figure 336. Total TCH seizure time (call time in seconds) (trf_24b) 145
          Figure 337. Total TCH seizure time (call time in hours), (trf_24c) 145
          Figure 338. SDCCH true seizures (trf_25) 146
          Figure 339. SDCCH true seizures, S7 (trf_25a) 146
          Figure 340. SDCCH true seizures for call and SS (trf_26) 146
          Figure 341. SDCCH true seizures for call, SMS, SS (trf_27) 146
          Figure 342. Peak busy SDCCH seizures (trf_28) 147
          Figure 343. IUO layer usage % (trf_29) 147
          Figure 344. SDCCH seizures (trf_30) 147
          Figure 345. Call time (minutes) from p_nbsc_res_avail (trf_32) 147
          Figure 346. Call time from p_nbsc_rx_qual (trf_32a) 148
          Figure 347. Call time from p_nbsc_rx_statistics (trf_32b) 148
          Figure 348. SDCCH HO seizure % out of HO seizure attempts (trf_33) 148
          Figure 349. SDCCH assignment % out of HO seizure attempts (trf_34) 148
          Figure 350. TCH HO seizure % out of TCH HO seizure request (trf_35) 149
          Figure 351. TCH norm seizure % out of TCH call request (trf_36) 149
          Figure 352. TCH normal seizure % out of TCH call requests, (trf_36a) 149
          Figure 353. TCH FCS seizure % out of TCH FCS attempts (trf_37) 149
          Figure 354. TCH FCS seizure % out of congested SDCCH seizure attempts
                        (trf_38) 150
          Figure 355. TCH seizures for new calls (trf_39) 150
          Figure 356. TCH seizures for new calls (trf_39a) 150
          Figure 357. HTCH usage, S5 (trf_40) 151
          Figure 358. MOC rate, S6 (trf_41) 151
          Figure 359. MTC rate, S6 (trf_42) 151
          Figure 360. TCH single band subscriber holding time, S6 (trf_43) 151
          Figure 361. TCH dual band subscriber holding time, S6 (trf_44) 152




DN98619493           © Nokia Networks Oy                                             17 (206)
Issue 1-1 en         Nokia Proprietary and Confidential
BSS Network Doctor Formulas




           Figure 362. TCH data call seizures (trf_46) 152
           Figure 363. Share of single band traffic (trf_47) 152
           Figure 364. Share of dual band traffic (trf_48) 152
           Figure 365. Call retries due to A interface pool mismatch (trf_49) 153
           Figure 366. HO retries due to A interface pool mismatch (trf_50) 153
           Figure 367. TCH single band subscribers’ share of holding time, S6 (trf_51) 153
           Figure 368. TCH dual band subscribers’ share of holding time, S6 (trf_52) 154
           Figure 369. Calls started as FACCH call setup (trf_53) 154
           Figure 370. SDCCH seizures (trf_54) 154
           Figure 371. TCH normal seizures (trf_55) 154
           Figure 372. Total FTCH seizure time (trf_56) 154
           Figure 373. Total HTCH seizure time (trf_57) 155
           Figure 374. Average TCH hold time for HSCSD, S7 (trf_58) 155
           Figure 375. Total HSCSD TCH seizure time (call time, hours),(trf_61) 155
           Figure 376. Average upgrade pending time for HSCSD, (trf_62) 155
           Figure 377. Average upgrade pending time due to congestion, (trf_63) 156
           Figure 378. Total reporting time of ph1 and ph2 mobiles, (trf_64) 156
           Figure 379. Total TCH seizures, (trf_65) 156
           Figure 380. Net UL data traffic per timeslot, S9PS (trf_69a) 156
           Figure 381. Net DL data traffic per timeslot, S9PS (trf_70a) 157
           Figure 382. Average UL throughput per allocated timeslot, S9PS (trf_72b) 157
           Figure 383. Average DL throughput per allocated timeslot, S9PS (trf_73b) 158
           Figure 384. Total RLC data, S9PS (trf_74a) 158
           Figure 385. GPRS territory UL utilisation, S9PS (trf_76b) 158
           Figure 386. GPRS territory DL utilisation, S9PS (trf_77a) 159
           Figure 387. UL GPRS timeslot usage, S9PS (trf_78a) 159
           Figure 388. DL GPRS timeslot usage, S9PS (trf_79a) 160
           Figure 389. SDCCH seizures for MO calls, S2 (moc_1) 160
           Figure 390. Successful MO speech calls, S3 (moc_2) 161
           Figure 391. Successful MO data calls, S3 (moc_3) 161
           Figure 392. MO call success ratio, S6 (moc_4) 161




18 (206)              © Nokia Networks Oy                                              DN98619493
                      Nokia Proprietary and Confidential                                Issue 1-1 en
Figure 393. MO speech call attempts, S3 (moc_5) 162
          Figure 394. MO call bids, S2 (moc_6) 162
          Figure 395. SDCCH seizures for MT calls, S2 (mtc_1) 162
          Figure 396. Successful MT speech calls (mtc_2) 162
          Figure 397. Successful MT data calls, S3 (mtc_3) 163
          Figure 398. MT call success ratio, S6 (mtc_4) 163
          Figure 399. MT speech call attempts (mtc_5) 163
          Figure 400. MT call attempts, S2 (mtc_6) 163
          Figure 401. Number of paging messages sent, S2 (pgn_1) 164
          Figure 402. Paging buffer size average, S1 (pgn_2) 164
          Figure 403. Average paging buffer space, S1 (pgn_3) 165
          Figure 404. Paging success ratio, S1 (pgn_4) 165
          Figure 405. Average paging buffer Aif occpancy, S7 (pgn_5) 165
          Figure 406. Average paging buffer Gb occpancy, S7PS (pgn_6) 165
          Figure 407. Average DRX buffer occpancy due to paging, S7 (pgn_7) 166
          Figure 408. Average DRX buffer occpancy due to DRX AG, S7 (pgn_8) 166
          Figure 409. Average DRX buffer occpancy due to nonDRX AG, S7 (pgn_9) 166
          Figure 410. SMS establishment failure % (sms_1) 166
          Figure 411. SMS TCH establishment failure % (sms_2) 167
          Figure 412. SMS SDCCH establishment failure % (sms_3) 167
          Figure 413. SMS establishment attempts (sms_4) 167
          Figure 414. SMS SDCCH establishment attempts (sms_5) 167
          Figure 415. SMS TCH establishment attempts (sms_6) 168
          Figure 416. DR, outgoing attempts, S3 (dr_1) 168
          Figure 417. DR attempts, S3 (dr_1a) 168
          Figure 418. DR, incoming attempts, S3 (dr_2) 168
          Figure 419. DR, outgoing success to another cell, S3 (dr_3) 168
          Figure 420. DR, incoming success from another cell, S3 (dr_4) 169
          Figure 421. DR, intra-cell success, S3 (dr_5) 169
          Figure 422. % of new calls successfully handed over to another cell by DR, S3
                        (dr_6) 169




DN98619493           © Nokia Networks Oy                                              19 (206)
Issue 1-1 en         Nokia Proprietary and Confidential
BSS Network Doctor Formulas




           Figure 423. DR, outgoing to another cell, failed, S3 (dr_7) 169
           Figure 424. DR, intra-cell failed, S3 (dr_8) 170
           Figure 425. TCH availability %, S4 (ava_1a) 170
           Figure 426. TCH availability %, S9 (ava_1c) 170
           Figure 427. TCH availability %, S9 (ava_1d) 171
           Figure 428. Average available TCH, S1 (ava_2) 171
           Figure 429. Average available SDCCH, S1 (ava_3) 171
           Figure 430. SDCCH availability %, S4 (ava_4) 172
           Figure 431. Average available FTCH in area, S1 (ava_5) 172
           Figure 432. DMR availability %, S6 (ava_6) 172
           Figure 433. DN2 availability %, S6 (ava_7) 172
           Figure 434. TRU availability %, S6 (ava_8) 173
           Figure 435. Average available TCH in BTS, S9 (ava_15) 173
           Figure 436. Average available PDTCH in BTS, S9PS (ava_16) 173
           Figure 437. Average available dedicated GPRS channels, S9PS (ava_17) 173
           Figure 438. Average defined TCH, S1 (ava_18) 174
           Figure 439. Average unavailable TSL per BTS, S1 (uav_1) 174
           Figure 440. Average unavailable TSL per BTS, S1 (uav_1a) 174
           Figure 441. Average unavailable TSL per BTS, S1 (uav_1b) 174
           Figure 442. Total outage time, (uav_2) 175
           Figure 443. Number of outages, (uav_3) 175
           Figure 444. Share of unavailability due to user (uav_4) 175
           Figure 445. Share of unavailability due to internal reasons (uav_5) 176
           Figure 446. Share of unavailability due to external reasons (uav_6) 176
           Figure 447. TRX unavailability time due to user (uav_7) 176
           Figure 448. TRX unavailability time due to internal reasons (uav_8) 176
           Figure 449. TRX unavailability time due to external reasons (uav_9) 177
           Figure 450. Number of LU attempts, S1 (lu_1) 177
           Figure 451. Average of LU attempts per hour, S1 (lu_2) 177
           Figure 452. Number of LU attempts, S1 (lu_3) 177
           Figure 453. LU success %, S6 (lsr_2) 178




20 (206)              © Nokia Networks Oy                                               DN98619493
                      Nokia Proprietary and Confidential                                 Issue 1-1 en
Figure 454. Emergency calls, S6 (ec_1) 178
          Figure 455. Emergency call success %, S6 (ecs_1) 178
          Figure 456. Call re-establishment attempts, S6 (re_1) 179
          Figure 457. Call re-establishments, S6 (re_2) 179
          Figure 458. Call re-establishment success %, S6 (res_1) 179
          Figure 459. DL BER, S1 (dlq_1) 180
          Figure 460. DL cumulative quality % in class X, S1 (dlq_2) 180
          Figure 461. DL cumulative quality % in class X, S1 (dlq_2a) 180
          Figure 462. UL BER, S1 (ulq_1) 181
          Figure 463. UL cumulative quality % in class X, S1 (ulq_2) 181
          Figure 464. UL cumulative quality % in class X, S1 (ulq_2a) 181
          Figure 465. Share % per range, S4 (dll_1) 182
          Figure 466. Share % per range, S4 (ull_1) 182
          Figure 467. Average MS power, S2 (pwr_1) 182
          Figure 468. Average MS power, S2 (pwr_1b) 183
          Figure 469. Average BS power, S2 (pwr_2) 183
          Figure 470. Average DL signal strength, S2 (lev_1) 183
          Figure 471. Average DL signal strength, S2 (lev_1a) 183
          Figure 472. Average UL signal strength, S2 (lev_2) 184
          Figure 473. Average UL signal strength, S2 (lev_2a) 184
          Figure 474. Average MS-BS distance (dis_1) 184
          Figure 475. Link balance, S1 (lb_1) 185
          Figure 476. Share in acceptance range, S4 (lb_2) 185
          Figure 477. Share in normal, S4 (lb_3) 185
          Figure 478. Share in MS limited, S4 (lb_4) 185
          Figure 479. Share in BS limited, S4 (lb_5) 186
          Figure 480. Share in maximum power, S4 (lb_6) 186
          Figure 481. Average MS power attenuation, S2 (lb_7) 186
          Figure 482. Average MS power, S2 (lb_7b) 186
          Figure 483. Average UL signal strength, S2 (lb_9) 187
          Figure 484. Average DL signal strength, S2 (lb_10) 187




DN98619493           © Nokia Networks Oy                                    21 (206)
Issue 1-1 en         Nokia Proprietary and Confidential
BSS Network Doctor Formulas




           Figure 485. Average MS power attenuation, S2 (lb_11) 187
           Figure 486. Average BS power attenuation, S2 (lb_12) 187
           Figure 487. SDCCH access probability, before FCS (csf_1) 188
           Figure 488. SDCCH access probability (csf_1a) 188
           Figure 489. SDCCH success ratio (csf_2a) 189
           Figure 490. SDCCH success ratio, (csf_2c) 189
           Figure 491. SDCCH success ratio, BTS, S6 (csf_2g) 190
           Figure 492. SDCCH success ratio, BTS, (csf_2i) 191
           Figure 493. SDCCH success ratio, area, (csf_2j) 192
           Figure 494. SDCCH success ratio, BTS, (csf_2k) 193
           Figure 495. TCH access probability without DR (csf_3a) 193
           Figure 496. TCH access probability without DR and Q (csf_3b) 194
           Figure 497. TCH access probability without Q (csf_3c) 194
           Figure 498. TCH access probability, real (csf_3d) 194
           Figure 499. TCH access probability without DR, (csf_3i) 195
           Figure 500. TCH access probability without DR and Q, (csf_3j) 195
           Figure 501. TCH access probability, real, (csf_3k) 196
           Figure 502. TCH access probability, real (csf_3l) 196
           Figure 503. TCH access probability without DR and Q, (csf_3m) 197
           Figure 504. TCH success ratio, area, before call re-establisment (csf_4o) 197
           Figure 505. TCH success ratio, area, after call re-establishment, S6 (csf_4p) 198
           Figure 506. TCH success ratio, BTS, before call re-establisment (csf_4q) 199
           Figure 507. TCH success ratio, BTS, after call re-establishment (csf_4r) 199
           Figure 508. TCH success ratio, BTS, after call re-establishment, (csf_4t) 200
           Figure 509. TCH success ratio, area, before call re-establishment, S7(csf_4u) 200
           Figure 510. TCH success ratio, area, after call re-establishment, S7 (csf_4v) 201
           Figure 511. TCH success ratio, BTS, after call re-establishment, (csf_4x) 201
           Figure 512. TCH success ratio, BTS, before call re-establishment, (csf_4y) 202
           Figure 513. Reuse pattern (cnf_1) 202




22 (206)              © Nokia Networks Oy                                             DN98619493
                      Nokia Proprietary and Confidential                               Issue 1-1 en
Summary of changes

               In this Functionality Note (FN T1712)

               As a result of the changes made between BSS Network Doctor software versions
               12.0 and 12.1 the following changes have been made into this document:

               New formulas

               •      TBF (tbf)

                      -      UL TBF reallocation failure ratio, S9PS (tbf_29)
                      -      DL TBF reallocation failure ratio, S9PS (tbf_30)
                      -      UL TBF reallocation attempts, S9PS (tbf_31)
                      -      DL TBF reallocation attempts, S9PS (tbf_32)

               •      RLC (rlc)

                      -      UL RLC blocks, S9PS (rlc_14)
                      -      DL RLC blocks, S9PS (rlc_15)

               •      Frame Relay (frl), all formulas new

                      -      Bytes in discarded sent frames, S9PS (frl_5)
                      -      Bytes in discarded received frames, S9PS (frl_6)

               •      Random access (rach)

                      -      Total RACH rejection ratio, S7 (rach_7)

               •      SDCCH drop ratio (sdr)

                      -      SDCCH drop %, S3 (sdr_1a)
                      -      Illegal establishment cause %, (sdr_3b)

               •      TCH drop call (dcr)

                      -      TCH drop call %, after TCH assignment, w RE, area level, S7
                             (dcr_8b)

               •      Blocking (blck)

                      -      NACK ratio of p-immediate assignment, S9PS (blck_21)
                      -      Territory upgrade rejection %, S9PS (blck_22)

               •      Traffic (trf)

                      -      GPRS territory UL utilisation, S9PS (trf_76b)
                      -      UL GPRS timeslot usage, S9PS (trf_78a)
                      -      DL GPRS timeslot usage, S9PS (trf_79a)

               •      Call success (csf)




DN98619493     © Nokia Networks Oy                                                    23 (206)
Issue 1-1 en   Nokia Proprietary and Confidential
BSS Network Doctor Formulas




                  -      SDCCH success ratio, (csf_2c)

           Removed formulas

           •      sdr_1 replaced with sdr_1a

           •      sdr_3 replaced with sdr_3b

           •      dcr_8a replaced with sdr_8b

           •      trf_76a replaced with trf_76b

           •      csf_2b replaced with csf_2c

           In the previous Functionality Note (FN T1538)

           As a result of the changes made between BSS Network Doctor software versions
           11.2 and 12.0 the following changes have been made into this document:

           New formulas

           •      Additional GPRS channels (ach), all formulas new

           •      Multislot (msl), all formulas new

           •      TBF (tbf), all formulas new

           •      RLC (rlc), all formulas new

           •      Availability (ava)

                  -      ava_1c, TCH availability %, S9
                  -      ava_1d, TCH availability %, S9
                  -      ava_15, Average available TCH in BTS, S9
                  -      ava_16, Average available PDTCH in BTS, S9PS
                  -      ava_17, Average available dedicated GPRS channels, S9PS
                  -      ava_18, Average defined TCH, S1

           •      Call success (csf)

                  -      csf_2j, SDCCH success ratio, area, S9
                  -      csf_2k, SDCCH success ratio, BTS, S9

           •      Congestion (cngt)

                  -      cngt_3a, FTCH time congestion %
                  -      cngt_4a, HTCH time congestion %

           •      Handover (ho)

                  -      ho_13f, HO attempts, outgoing and intra-cell, S9




24 (206)   © Nokia Networks Oy                                                  DN98619493
           Nokia Proprietary and Confidential                                    Issue 1-1 en
•      Paging (pgn)

                      -      pgn_5, Average paging buffer Aif occupancy, S7
                      -      pgn_6, Average paging buffer Gb occupancy, S7PS
                      -      pgn_7, Average DRX buffer occupancy due to paging, S7
                      -      pgn_8, Average DRX buffer occupancy due to DRX AG, S7
                      -      pgn_9, Average DRX buffer occupancy due to nonDRX AG, S7

               •      Traffic (trf)

                      -      trf_61, Total HSCSD TCH seizure time (call time, hours)
                      -      trf_62, Average upgrade pending time for HSCSD
                      -      trf_63, Average upgrade pending time due to congestion
                      -      trf_64, Total reporting time of ph1 and ph2 mobile
                      -      trf_65, Total TCH seizures
                      -      trf_69a, Net UL data traffic per timeslot, S9PS
                      -      trf_70a, Net DL data traffic per timeslot, S9PS
                      -      trf_72b, Average UL throughput per allocated timeslot, S9PS
                      -      trf_73b, Average DL throughput per allocated timeslot, S9PS
                      -      trf_74a, Total RLC data, S9PS
                      -      trf_76a, GPRS territory UL utilisation, S9PS
                      -      trf_77a, GPRS territory DL utilisation, S9PS

               Removed formulas

               •      blck_8c replaced with blck_8d
               •      csf_2a replaced with csf_2b

               •      csf_2h replaced with csf_2j

               •      csf_4s replaced with csf_4v

               •      dcr_5a




DN98619493     © Nokia Networks Oy                                                     25 (206)
Issue 1-1 en   Nokia Proprietary and Confidential
BSS Network Doctor Formulas




26 (206)   © Nokia Networks Oy                                 DN98619493
           Nokia Proprietary and Confidential                   Issue 1-1 en
About this manual




1              About this manual
                  This document defines the formulas used to calculating the Key Performance
                  Indicators based on the Nokia NMS/2000 database.

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


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


                  The information contained in this document relates to BSS Network Doctor
                  software version 12.x, Nokia NMS release T12 and to release S9 of the Nokia
                  BSC software. This document should not be used with any other versions of the
                  Nokia NMS/2000 or Nokia BSC software.

                  This document is intended for the network operators of the Nokia NMS/2000.

                  This chapter covers the following topics:

                  •      What you need to know first

                  •      Where to find more

                  •      Typographic conventions

                  •      Concepts and terminology



1.1            What you need to know first
                  This document assumes that you are familiar with the following areas:




DN98619493        © Nokia Networks Oy                                                       27 (206)
Issue 1-1 en      Nokia Proprietary and Confidential
BSS Network Doctor Formulas




                •      The concepts of the Nokia NMS and GSM networks in general

                •      A text processing utility, such as vi or dtpad. These text processors are
                       used for editing certain configuration files.



1.2        Where to find more
                When you perform the user’s tasks described in this document, you may need to
                refer to other documentation for further information. Below is a list of manuals
                that you will find useful, as well as a brief description of the manual’s contents.

                BSS Network Doctor documentation

                •      BSS Network Doctor, Feature Overview, DN00308743, for a brief
                       overview on the application

                •      BSS Network Doctor, System Administrator’s Guide, DN98619369, for
                       system administrator’s tasks related to running Network Doctor
                •      BSS Network Doctor, User’s Guide, DN98614186, for a detailed
                       description on utilising the Network Doctor reports

                Other Nokia documents

                •      Database Description for BSC Measurements, DN98619454, for a
                       description of the structure of performance management (PM) tables in the
                       NMS/2000 database and the records, including counters, in each table.

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

                •      DX Cause Coding Mapping, DN9813878, for an explanation to the
                       relationship between DX cause codes and PM counters and for the analysis
                       of TCH and SDCCH observations.#2



1.3        Typographic conventions
                The following tables present the typographic conventions which have been used
                in this manual to describe different actions and restrictions.


1.3.1      Text styles

                The following table presents the typefaces and fonts and their indications.




28 (206)        © Nokia Networks Oy                                                    DN98619493
                Nokia Proprietary and Confidential                                      Issue 1-1 en
About this manual




                   Table 1.         Text styles in this document

                    Style                           Explanation
                    Initial Upper-case              Application names
                    Lettering

                    Italiced text                   Emphasis
                                                    State, status or mode

                    Courier                         File and directory names
                                                    Names of database tables
                                                    Parameters
                                                    User names
                                                    System output
                                                    User input

                    UPPER-CASE                      Keys on the keyboard (ALT, TAB, CTRL etc.)
                    LETTERING

                    Bold text                       User interface components

                    Initial Upper-case              Referenced documents
                    Lettering in Italics            Referenced sections and chapters within a document

                    <bracketed text>                Variable user input




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


1.4.1          Abbreviations


                   Table 2.         Abbreviations

                    Abbreviation                    Explanation
                    AG                              Access Grant

                    BCCH                            Broadcast Control Channel

                    BCF                             Base Control Function

                    BER                             Bit Error Ratio

                    BSC                             Base Station Controller




DN98619493         © Nokia Networks Oy                                                              29 (206)
Issue 1-1 en       Nokia Proprietary and Confidential
BSS Network Doctor Formulas




           Table 2.      Abbreviations (Continued)

            Abbreviation                  Explanation
            BSS                           Base Station Subsystem

            BTS                           Base Transceiver Station

            CI                            Cell Identity

            DL                            Downlink

            DR                            Directed Retry

            FCS                           Frame Check Sequence

            HO                            Handover

            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

            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

            TRX                           Transceiver

            TSL                           Timeslot

            UL                            Uplink




30 (206)   © Nokia Networks Oy                                                          DN98619493
           Nokia Proprietary and Confidential                                            Issue 1-1 en
About this manual




1.4.2                 Terms

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



                         Table 3.      Terms used in this document

 Term                                     Explanation
 AGCH                                     A downlink control channel that is used to carry a
                                          response to a mobile channel allocation request.
                                          The AGCH assigns the mobile to operate on a
                                          specific TDMA timeslot.

 Bit Error Ratio                          The ratio of the number of the bit errors to the total
                                          number 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 all
                                          mobile stations located in the cell coverage area.

 BTS group                                A predefined set of BTSs which can be created and
                                          handled for definition by Network Doctor.

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

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

 Day                                      The counting of data per day is based on the
                                          period_start_time field in the measurement
                                          tables. This field always tells the starting hour of the
                                          measurement period. Under one day there are hours
                                          from 00 to 23.

 Directed Retry                           A procedure used in a call set-up phase for
                                          assigning a mobile station to a traffic channel of a
                                          cell other than the serving cell when the traffic is
                                          congested.

 Frame Check Sequence                     Extra characters added to a frame for the purposes
                                          of error control. The FCS is used in HDCL, Frame
                                          Relay, and other data link layer protocols.

 Key Performance Indicator                The performance of the network is calculated from
                                          the NMS/2000 based on the Network Element
                                          counter information. Sometimes the plain counter as
                                          such describes an important performance aspect
                                          (number of calls, for example) of the network but
                                          sometimes a formula of counters is needed (e.g.
                                          drop call ratio).




DN98619493               © Nokia Networks Oy                                                                 31 (206)
Issue 1-1 en             Nokia Proprietary and Confidential
BSS Network Doctor Formulas




                          Table 3.      Terms used in this document (Continued)

 Term                                      Explanation
 Maintenance Region                        Each object in the NMS/2000 database belongs to
                                           one and only one Maintenance Region (MR).

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

 NMS/2000                                  A product of Nokia Telecommunications for the
                                           operation and maintenance of cellular networks.

 SQL*Plus                                  An interactive program for accessing the database.

 Stand-alone Dedicated Control             A control channel (CCH) used for roaming,
 Channel (SDCCH)                           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 station
                                           and primarily intended for conversation.

 Trunk Reservation                         A stochastic algorithm employed in a channel
                                           allocation from a cell.


                          For any other terms, refer to Glossary, DN9763965.




32 (206)                  © Nokia Networks Oy                                                         DN98619493
                          Nokia Proprietary and Confidential                                           Issue 1-1 en
BSS counter formulas




2              BSS counter formulas
                  This chapter lists all BSS Network Doctor formulas. The more commonly used
                  ones are described in further detail concerning their use or known problems with
                  them, for example. In connection with the name of a formula there is also a
                  reference to the BSC release (S1 to S6) since when the counters of the formula
                  have been available.

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


                  Note
                  When running the reports with newer counters, be careful especially when you
                  have two BSC software releases running in the network simultaneously. The
                  simplest way to avoid problems is to start to use new counters of a new BSC
                  release only when the new software release is used in the entire network under the
                  NMS/2000.




2.1            Additional GPRS channels (ach)
                  Additional GPRS channel use, S9PS (ach_1)
                  Use:                  Example: if value equals to 1 then in average 1 additional
                                        timeslot has been used for GPRS. If the situation continues it
                                        indicates need for extending the default or dedicated territory.
total hold time of all additional GPRS ch. seizures (sec)
----------------------------------------------------------- =
period duration

sum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100
---------------------------------------
sum(period_duration*60)

Counters from table(s):
p_nbsc_res_avail




DN98619493        © Nokia Networks Oy                                                           33 (206)
Issue 1-1 en      Nokia Proprietary and Confidential
BSS Network Doctor Formulas




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_avail
Unit: 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
                                        (territory downgrade).
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:                  If the value is high, more default area is needed.
sum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100

Counters from table(s):
p_nbsc_res_avail
Unit: sec



                  Figure 4.     Total additional GPRS channel hold time, S9PS (ach_4)




34 (206)          © Nokia Networks Oy                                                        DN98619493
                  Nokia Proprietary and Confidential                                          Issue 1-1 en
BSS counter formulas




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_UL
100 * -------------------------------------------------------------------------- %
       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 components of 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_DL
100 * -------------------------------------------------------------------------- %
       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.

Counters from table(s):
p_nbsc_packet_control_unit



                  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_UL
100 * -------------------------------------------------------- %
           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.

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 7.     Distribution of UL multislot allocations, S9PS (msl_3)




DN98619493        © Nokia Networks Oy                                                            35 (206)
Issue 1-1 en      Nokia Proprietary and Confidential
BSS Network Doctor Formulas




                  Distribution of DL multislot allocations, S9PS (msl_4)
                  Use:                  Indicates the share of a multislot request type to all multislot
                                        requests.
                     alloc_X_TSL_DL
100 * ------------------------------------------------------ %
        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.

Counters from table(s):
p_nbsc_packet_control_unit



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


                  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)

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 9.     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)

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 10. 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)

Counters from table(s):
p_nbsc_packet_control_unit



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




36 (206)          © Nokia Networks Oy                                                       DN98619493
                  Nokia Proprietary and Confidential                                         Issue 1-1 en
BSS counter formulas




                  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)

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 12. Average number of allocated timeslots, DL S9PS (msl_13)


                  Average number of requested UL timeslots, S9PS (msl_13)
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)

Counters from table(s):
p_nbsc_packet_control_unit



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


                  Average number of requested DL timeslots, S9PS (msl_14)
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)

Counters from table(s):
p_nbsc_packet_control_unit



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


                  UL multislot allocation %, S9PS (msl_15)
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)
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)

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 15. UL multislot allocation %, S9PS (msl_15)




DN98619493        © Nokia Networks Oy                                               37 (206)
Issue 1-1 en      Nokia Proprietary and Confidential
BSS Network Doctor Formulas




                  DL multislot allocation %, S9PS (msl_16)
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)
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)

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 16. DL multislot allocation %, S9PS (msl_16)


                  UL multislot requests, S9PS (msl_17)
                  Use:                  Total number of multislot requests in UL.
sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL +req_4_TSL_UL+ req_5_8_TSL_UL)

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 17. UL multislot requests, S9PS (msl_17)


                  DL multislot requests, S9PS (msl_18)
                  Use:                  Total number of multislot requests in DL.
sum(req_1_TSL_DL+req_2_TSL_DL+req_3_TSL_DL +req_4_TSL_DL+ req_5_8_TSL_DL)

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 18. 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.
sum(Ave_UL_LLC_per_TBF_sum)
----------------------------
sum(Ave_UL_LLC_per_TBF_den)




38 (206)          © Nokia Networks Oy                                                    DN98619493
                  Nokia Proprietary and Confidential                                      Issue 1-1 en
BSS counter formulas




Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 19. 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)

Counters from table(s):
p_nbsc_packet_control_unit

Unit: seconds



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


                  Average UL TBF duration, S9PS (tbf_5)
sum(ave_dur_ul_tbf_sum)
------------------------
sum(ave_dur_ul_tbf_den)

Counters from table(s):
p_nbsc_packet_control_unit

Unit: seconds



                  Figure 21. 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_unit

Unit: seconds



                  Figure 22. Average UL TBF duration, S9PS (tbf_5a)


                  Average DL TBF duration, S9PS (tbf_6a)
                  Use:                  Counted from the normally released TBFs.




DN98619493        © Nokia Networks Oy                                                         39 (206)
Issue 1-1 en      Nokia Proprietary and Confidential
BSS Network Doctor Formulas




                  Known problems: Contains part of TBF establishment delays.
sum(ave_dur_dl_tbf_sum)/100
---------------------------
sum(ave_dur_dl_tbf_den)

Counters from table(s):
p_nbsc_packet_control_unit

Unit: seconds



                  Figure 23. 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)

Counters from table(s):
p_nbsc_packet_control_unit

Unit: seconds



                  Figure 24. 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)

Counters from table(s):
p_nbsc_packet_control_unit

Unit: seconds



                  Figure 25. Average DL TBF duration, unack mode, S9PS (tbf_8)


                  UL mlslot allocation blocking, S9PS (tbf_15)
                  Known problems: Over 100 % values are met.
                   sum(NO_RADIO_RES_AVA_UL_TBF)
100 * ------------------------------------------------------------------------- %
    sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL +req_4_TSL_UL+ req_5_8_TSL_UL)

Counters from table(s):
p_nbsc_packet_control_unit



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




40 (206)          © Nokia Networks Oy                                              DN98619493
                  Nokia Proprietary and Confidential                                Issue 1-1 en
BSS counter formulas




                  DL mlslot allocation blocking, S9PS (tbf_16)
                  Known problems: Values of over 100% are met.
           sum(NO_RADIO_RES_AVA_DL_TBF)
100 * ------------------------------------------------------------------------- %
     sum(req_1_TSL_DL+req_2_TSL_DL+req_3_TSL_DL +req_4_TSL_DL+ req_5_8_TSL_DL)

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 27. DL mlslot allocation blocking, S9PS


                  Normally released UL TBF ratio, S9PS (tbf_25)
                  Experiences on use: Cases when TBF is not released normally:
                                    1) PCU receives a Channel Request, allocates resources and
                                    sends assignment but receives no blocks. These cases can
                                    occur if MS sends more than one Channel Request before it
                                    receives an Immediate Assignment.
                                    2) Ghost Accesses.
     normally released UL TBFs
100*---------------------------- % =
       established UL TBFs

     sum(AVE_DUR_UL_TBF_DEN)
100*--------------------------- %
       sum(NBR_OF_UL_TBF)

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 28. Normally released UL TBF ratio, S9PS (tbf_25)


                  Normally released DL TBF ratio, S9PS (tbf_26)
                  Use:                  DL TBF establishment is not completed normally, for
                                        example, if a response from a MS is not received. If the TBF
                                        is already running and the MS is not heard from, the counter
                                        DL_TBF_REL_DUE_NO_RESP_MS is triggered.

      normally released DL TBFs
100*---------------------------- % =
       established DL TBFs

     sum(AVE_DUR_DL_TBF_DEN)
100*---------------------------
       sum(NBR_OF_DL_TBF)

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 29. Normally released DL TBF ratio, S9PS (tbf_26)




DN98619493        © Nokia Networks Oy                                                        41 (206)
Issue 1-1 en      Nokia Proprietary and Confidential
BSS Network Doctor Formulas




                  UL TBF reallocation failure ratio, S9PS (tbf_29)

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

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 30. UL TBF reallocation failure ratio, S9PS (tbf_29)


                  DL TBF reallocation failure ratio, S9PS (tbf_30)

              sum(DL_TBF_REALLOC_FAILS)
100 * ----------------------------------------------- %
      sum(DL_TBF_RE_ALLOCATIONS+ DL_TBF_REALLOC_FAILS)

Counters from table(s):
p_nbsc_packet_control_unit



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


                  UL TBF reallocation attempts, S9PS (tbf_31)
sum(UL_TBF_RE_ALLOCATIONS+ UL_TBF_REALLOC_FAILS)

Counters from table(s):
p_nbsc_packet_control_unit



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


                  DL TBF reallocation attempts, S9PS (tbf_32)
sum(DL_TBF_RE_ALLOCATIONS+ DL_TBF_REALLOC_FAILS)

Counters from table(s):
p_nbsc_packet_control_unit



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



2.4          RLC (rlc)
                  Ack.CS1 RLC blocks UL, S9PS (rlc_1)
                  Use:                  Number of UL blocks in RLC ack mode using CS1.
                                        Retransmission is not included.




42 (206)          © Nokia Networks Oy                                                DN98619493
                  Nokia Proprietary and Confidential                                  Issue 1-1 en
BSS counter formulas




sum(RLC_DATA_BLOCKS_UL_CS1 - RLC_DATA_BLOCKS_UL_UNACK)



                  Figure 34. Ack.CS1 RLC blocks UL, S9PS (rlc_1)


                  Ack.CS1 RLC blocks DL, S9PS (rlc_2)
                  Use:                  Number of DL blocks in RLC ack mode using CS1.
                                        Retransmission is not included.
sum(RLC_DATA_BLOCKS_DL_CS1 - RLC_DATA_BLOCKS_DL_UNACK)



                  Figure 35. Ack.CS1 RLC blocks DL, S9PS (rlc_2)


                  Ack. CS1 RLC DL block error rate, S9PS (rlc_3a)
                  Use:                  Number of DL blocks in RLC ack mode using CS1.
      sum(BAD_FRAME_IND_UL_CS1 - BAD_FRAME_IND_UL_UNACK )
100 * ------------------------------------------------ %
      sum(RLC_DATA_BLOCKS_DL_CS1 - RLC_DATA_BLOCKS_DL_UNACK
        + BAD_FRAME_IND_UL_CS1 - BAD_FRAME_IND_UL_UNACK )



                  Figure 36. Ack. CS1 RLC DL Block error rate, S9PS (rlc_3a)


                  Unack. CS1 RLC UL block error rate, S9PS (rlc_4a)

                sum(BAD_FRAME_IND_UL_UNACK)
100 * ---------------------------------------------------- %
      sum(RLC_DATA_BLOCKS_UL_UNACK+ BAD_FRAME_IND_UL_UNACK)



                  Figure 37. Unack. CS1 RLC UL block error rate, S9PS (rlc_4a)


                  Ack. CS1 RLC UL block error rate, S9PS (rlc_5a)

                sum(BAD_FRAME_IND_UL_CS2)
100 * ------------------------------------------------- %
      sum(RLC_DATA_BLOCKS_UL_CS2+ BAD_FRAME_IND_UL_CS2)



                  Figure 38. Ack. CS1 RLC UL block error rate, S9PS (rlc_5a)


                  UL CS1 RLC data share, S9PS (rlc_6)

                sum(RLC_data_blocks_UL_CS1*22
100 * ---------------------------------------------------------- %
     (sum(RLC_data_blocks_UL_CS1*22+RLC_data_blocks_UL_CS2*32




DN98619493        © Nokia Networks Oy                                                    43 (206)
Issue 1-1 en      Nokia Proprietary and Confidential
BSS Network Doctor Formulas




           + RLC_data_blocks_DL_CS1*22+RLC_data_blocks_DL_CS2*32)

Counters from table(s):
p_nbsc_packet_control_unit

Unit: %



                     Figure 39. UL CS1 RLC data share, S9PS (rlc_6)


                     UL CS2 RLC data share, S9PS (rlc_7)

                sum(RLC_data_blocks_UL_CS2*22
100 * ---------------------------------------------------------- %
     (sum(RLC_data_blocks_UL_CS1*22+RLC_data_blocks_UL_CS2*32
        + RLC_data_blocks_DL_CS1*22+RLC_data_blocks_DL_CS2*32)

Counters from table(s):
p_nbsc_packet_control_unit

Unit: %



                     Figure 40. UL CS2 RLC data share, S9PS


                     DL CS1 RLC data share, S9PS (rlc_8)

                sum(RLC_data_blocks_DL_CS1*22
100 * ---------------------------------------------------------- %
     (sum(RLC_data_blocks_UL_CS1*22+RLC_data_blocks_UL_CS2*32
        + RLC_data_blocks_DL_CS1*22+RLC_data_blocks_DL_CS2*32)

Counters from table(s):
p_nbsc_packet_control_unit

Unit: %



                     Figure 41. DL CS1 RLC data share, S9PS (rlc_8)


                     DL CS2 RLC data share, S9PS (rlc_9)

                sum(RLC_data_blocks_DL_CS2*22
100 * ---------------------------------------------------------- %
     (sum(RLC_data_blocks_UL_CS1*22+RLC_data_blocks_UL_CS2*32
        + RLC_data_blocks_DL_CS1*22+RLC_data_blocks_DL_CS2*32)

Counters from table(s):
p_nbsc_packet_control_unit

Unit: %



                     Figure 42. DL CS2 RLC data share, S9PS (rlc_9)




44 (206)             © Nokia Networks Oy                                           DN98619493
                     Nokia Proprietary and Confidential                             Issue 1-1 en
BSS counter formulas




                  UL CS1 RLC block error rate, S9PS (rlc_10)
                  Known problems: 100% values met. 100% means that the MS has not responded
                                  to USF. The number of ignored RLC data blocks in uplink due
                                  to BSN in acknowledged mode should be subtracted, but there
                                  is no counter specifically for CS1.
             sum(BAD_FRAME_IND_UL_CS1)
100 * ------------------------------------------------- %
      sum(RLC_DATA_BLOCKS_UL_CS1+ BAD_FRAME_IND_UL_CS1)



                  Figure 43. UL CS1 RLC block error rate, S9PS (rlc_10)


                  UL CS2 RLC block error rate, S9PS (rlc_11)
                  Known problems: 100% means that there can be only failing accesses. The
                                  number of ignored RLC data blocks in downlink due to BSN
                                  in acknowledged mode should be subtracted, but there is no
                                  counter specifically for CS1.
             sum(BAD_FRAME_IND_UL_CS2)
100 * ------------------------------------------------- %
      sum(RLC_DATA_BLOCKS_UL_CS2+ BAD_FRAME_IND_UL_CS2)



                  Figure 44. UL CS2 RLC block error rate, S9PS (rlc_11)


                  DL CS1 RLC block error rate, S9PS (rlc_12)

             sum(RETRA_RLC_DATA_BLOCKS_DL_CS1)
100 * ------------------------------------------------- %
      sum(RLC_DATA_BLOCKS_DL_CS1+ RETRA_RLC_DATA_BLOCKS_DL_CS1)



                  Figure 45. DL CS1 RLC block error rate, S9PS (rlc_12)


                  DL CS2 RLC block error rate, S9PS (rlc_13)

             sum(RETRA_RLC_DATA_BLOCKS_DL_CS2)
100 * -------------------------------------------------------- %
      sum(RLC_DATA_BLOCKS_DL_CS2+ RETRA_RLC_DATA_BLOCKS_DL_CS2)



                  Figure 46. DL CS2 RLC block error rate, S9PS (rlc_13)


                  UL RLC blocks, S9PS (rlc_14)
                  Use:                  Total UL data volume as the number of RLC blocks.
sum(rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2
  + rlc_mac_cntrl_blocks_ul + bad_frame_ind_ul_cs1




DN98619493        © Nokia Networks Oy                                                       45 (206)
Issue 1-1 en      Nokia Proprietary and Confidential
BSS Network Doctor Formulas




  + bad_frame_ind_ul_cs2 + bad_frame_ind_ul_unack
  + ignor_rlc_data_bl_ul_due_bsn)

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 47. UL RLC blocks, S9PS (rlc_14)


                  DL RLC blocks, S9PS (rlc_15)
                  Use:                  Total DL data volume as the number of RLC blocks.
sum(rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2
  + rlc_mac_cntrl_blocks_dl + retra_rlc_data_blocks_dl_cs1
  + retra_rlc_data_blocks_dl_cs2)

Counters from table(s):
p_nbsc_packet_control_unit



                  Figure 48. DL RLC blocks, S9PS (rlc_15)



2.5          Frame relay (frl)
                  Bytes in discarded sent frames, S9PS (frl_5)
sum(dlci_1_bytes_sent+dlci_2_bytes_sent+dlci_3_bytes_sent+dlci_4_bytes_sent
+dlci_5_bytes_sent)

Counters from table(s):
p_nbsc_frame_relay



                  Figure 49. Bytes in discarded sent frames, S9PS (frl_5)


                  Bytes in discarded received frames, S9PS (frl_6)
sum(DLCI_1_BYTES_REC+DLCI_2_BYTES_REC+DLCI_3_BYTES_REC+DLCI_4_BYTES_REC
   +DLCI_5_BYTES_REC)

Counters from table(s):
p_nbsc_frame_relay



                  Figure 50. Bytes in discarded received frames, S9PS (frl_6)




46 (206)          © Nokia Networks Oy                                                  DN98619493
                  Nokia Proprietary and Confidential                                    Issue 1-1 en
BSS counter formulas




2.6            Random access (rach)
                  Average RACH slot, S1 (rach_1)
                  Use:                  Indicates the capacity of BTS for RACH burst handling.
                                        Normally shows a constant value because it is dependent on
                                        the BTS configuration which does not often change.
avg(ave_rach_slot/res_acc_denom1)

Counters from table(s):
p_nbsc_res_access



                  Figure 51. Average RACH slot, S1 (rach_1)


                  Peak RACH load, average, S1 (rach_2)
                  Use:              Indicates the absolute peak value during a measurement
                                    period. Correlates strongly with UL interference.
                  Experiences on use: High values may suggest that MSs have problems in
                                    accessing the BTS. High values do not mean high load on
                                    SDCCH because SDCCH is needed only if the RACH passes
                                    the detection in BTS.
                  Known problems: The peak value does not indicate yet how many times there
                                    have been other peaks during the measurement period.
                  Open questions: How serious the high values really are from the MS point of
                                    view?
avg(peak_rach_load)

Counters from table(s):
p_nbsc_res_access



                  Figure 52. Peak RACH load, average, S1 (rach_2)


                  Peak RACH load %, S1 (rach_3)
                  Use:                  This PI indicates how near to full capacity the peak use of
                                        RACH has been during the measurement period.
             max(peak_rach_load)
100 * -------------------------------------             %
       max(ave_rach_busy/res_acc_denom1)

Counters from table(s):
p_nbsc_res_access



                  Figure 53. Peak RACH load %, S1 (rach_3)




DN98619493        © Nokia Networks Oy                                                          47 (206)
Issue 1-1 en      Nokia Proprietary and Confidential
BSS Network Doctor Formulas




                  Average RACH load % , S1 (rach_4)
                  Use:              This PI indicates how high the RACH load is on average.
                  Experiences on use: If the value is to the order of tens of per cent, there probably
                                    are access problems and MS users get, more often than usual,
                                    3 beeps when trying to start calls. The probable reason is UL
                                    interference.
       avg(ave_rach_busy/res_acc_denom3)
100 * --------------------------------------           %
       avg(ave_rach_slot/res_acc_denom1)

Counters from table(s):
p_nbsc_res_access



                  Figure 54. Average RACH load %, S1 (rach_4)


                  Average RACH busy, S1 (rach_5)
                  Use:                  This PI indicates roughly the average of the used RACH slots.
                                        If the average approaches the xb2 average RACH slotxb2
                                        (rach_1) there probably are access problems and MS users
                                        get, more often than usual, 3 beeps when trying to start calls.
avg(ave_rach_busy/res_acc_denom3)

Counters from table(s):
p_nbsc_res_access



                  Figure 55. Average RACH busy, S1 (rach_5)


                  RACH rejected due to illegal establishment, S5 (rach_6)
                  Use:                  Most of the rejections are ghost accesses. Note that part of the
                                        ghosts have legal establishment cause and get further to
                                        SDCCH.
sum(ghost_ccch_res
- rej_seiz_att_due_dist)

Counters from table(s):
p_nbsc_res_access



                  Figure 56. RACH rejected due to illegal establishment, S5 (rach_6)


                  Total RACH rejection ratio, S7 (rach_7)
                  Use:                  Ratio of all RACH rejections to total nbr of channel required
                                        messages received.
                                        Note that the counter ghost_ccch_res contains both ghosts and
                                        rejections due to distance checking. The latter one is an
                                        optional feature of BSC.




48 (206)          © Nokia Networks Oy                                                       DN98619493
                  Nokia Proprietary and Confidential                                         Issue 1-1 en
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor
50267584 celldoctor

Mais conteúdo relacionado

Semelhante a 50267584 celldoctor

Ims call flow
Ims call flowIms call flow
Ims call flow
Morg
 
Rfc3984 rtp standart
Rfc3984 rtp standartRfc3984 rtp standart
Rfc3984 rtp standart
aotomruk
 
Manual FOX ABB Teleprotecciones.pdf
Manual FOX ABB Teleprotecciones.pdfManual FOX ABB Teleprotecciones.pdf
Manual FOX ABB Teleprotecciones.pdf
fredinho1
 
62_1553-csa12101_15-v2uen_b.pdf
62_1553-csa12101_15-v2uen_b.pdf62_1553-csa12101_15-v2uen_b.pdf
62_1553-csa12101_15-v2uen_b.pdf
snoc3team
 
71382704 mimo-of dm-wireless-communications-with-matlab-0470825618
71382704 mimo-of dm-wireless-communications-with-matlab-047082561871382704 mimo-of dm-wireless-communications-with-matlab-0470825618
71382704 mimo-of dm-wireless-communications-with-matlab-0470825618
nxtxxx
 
Technical Proposal - Longhaul Backbone Project
Technical Proposal - Longhaul Backbone ProjectTechnical Proposal - Longhaul Backbone Project
Technical Proposal - Longhaul Backbone Project
Khurram Shafique
 

Semelhante a 50267584 celldoctor (20)

Ims call flow
Ims call flowIms call flow
Ims call flow
 
NetSim Technology Library- Lte and-lte-a
NetSim Technology Library- Lte and-lte-aNetSim Technology Library- Lte and-lte-a
NetSim Technology Library- Lte and-lte-a
 
03 umts radio path and transmissionnew
03 umts radio path and transmissionnew03 umts radio path and transmissionnew
03 umts radio path and transmissionnew
 
Wcdma.For.Umts
Wcdma.For.UmtsWcdma.For.Umts
Wcdma.For.Umts
 
Rfc3984 rtp standart
Rfc3984 rtp standartRfc3984 rtp standart
Rfc3984 rtp standart
 
Manual FOX ABB Teleprotecciones.pdf
Manual FOX ABB Teleprotecciones.pdfManual FOX ABB Teleprotecciones.pdf
Manual FOX ABB Teleprotecciones.pdf
 
Umts signaling
Umts signalingUmts signaling
Umts signaling
 
Trace window for dropped calls nsn
Trace window for dropped calls nsnTrace window for dropped calls nsn
Trace window for dropped calls nsn
 
D0941824
D0941824D0941824
D0941824
 
vorlage
vorlagevorlage
vorlage
 
Bharat gargi final project report
Bharat gargi final project reportBharat gargi final project report
Bharat gargi final project report
 
03 ft48923 en02gla0_general topics_
03 ft48923 en02gla0_general topics_03 ft48923 en02gla0_general topics_
03 ft48923 en02gla0_general topics_
 
62_1553-csa12101_15-v2uen_b.pdf
62_1553-csa12101_15-v2uen_b.pdf62_1553-csa12101_15-v2uen_b.pdf
62_1553-csa12101_15-v2uen_b.pdf
 
NetSim Technology Library- Internetworks
NetSim Technology Library- InternetworksNetSim Technology Library- Internetworks
NetSim Technology Library- Internetworks
 
AES Proposal
AES ProposalAES Proposal
AES Proposal
 
71382704 mimo-of dm-wireless-communications-with-matlab-0470825618
71382704 mimo-of dm-wireless-communications-with-matlab-047082561871382704 mimo-of dm-wireless-communications-with-matlab-0470825618
71382704 mimo-of dm-wireless-communications-with-matlab-0470825618
 
Saudi Arabian Power Distribution Code 2020
Saudi Arabian Power Distribution Code 2020Saudi Arabian Power Distribution Code 2020
Saudi Arabian Power Distribution Code 2020
 
Technical Proposal - Longhaul Backbone Project
Technical Proposal - Longhaul Backbone ProjectTechnical Proposal - Longhaul Backbone Project
Technical Proposal - Longhaul Backbone Project
 
Rm10 2
Rm10 2Rm10 2
Rm10 2
 
Leica Viva_Technical_reference.pdf
Leica Viva_Technical_reference.pdfLeica Viva_Technical_reference.pdf
Leica Viva_Technical_reference.pdf
 

Último

+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
?#DUbAI#??##{{(☎️+971_581248768%)**%*]'#abortion pills for sale in dubai@
 

Último (20)

Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024
 
AWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of TerraformAWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of Terraform
 
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
 
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
 
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
TrustArc Webinar - Unlock the Power of AI-Driven Data DiscoveryTrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
 
From Event to Action: Accelerate Your Decision Making with Real-Time Automation
From Event to Action: Accelerate Your Decision Making with Real-Time AutomationFrom Event to Action: Accelerate Your Decision Making with Real-Time Automation
From Event to Action: Accelerate Your Decision Making with Real-Time Automation
 
A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)
 
Exploring the Future Potential of AI-Enabled Smartphone Processors
Exploring the Future Potential of AI-Enabled Smartphone ProcessorsExploring the Future Potential of AI-Enabled Smartphone Processors
Exploring the Future Potential of AI-Enabled Smartphone Processors
 
Partners Life - Insurer Innovation Award 2024
Partners Life - Insurer Innovation Award 2024Partners Life - Insurer Innovation Award 2024
Partners Life - Insurer Innovation Award 2024
 
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
 
Driving Behavioral Change for Information Management through Data-Driven Gree...
Driving Behavioral Change for Information Management through Data-Driven Gree...Driving Behavioral Change for Information Management through Data-Driven Gree...
Driving Behavioral Change for Information Management through Data-Driven Gree...
 
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected WorkerHow to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected Worker
 
Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024
Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024
Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024
 
Advantages of Hiring UIUX Design Service Providers for Your Business
Advantages of Hiring UIUX Design Service Providers for Your BusinessAdvantages of Hiring UIUX Design Service Providers for Your Business
Advantages of Hiring UIUX Design Service Providers for Your Business
 
Developing An App To Navigate The Roads of Brazil
Developing An App To Navigate The Roads of BrazilDeveloping An App To Navigate The Roads of Brazil
Developing An App To Navigate The Roads of Brazil
 
A Year of the Servo Reboot: Where Are We Now?
A Year of the Servo Reboot: Where Are We Now?A Year of the Servo Reboot: Where Are We Now?
A Year of the Servo Reboot: Where Are We Now?
 
Finology Group – Insurtech Innovation Award 2024
Finology Group – Insurtech Innovation Award 2024Finology Group – Insurtech Innovation Award 2024
Finology Group – Insurtech Innovation Award 2024
 
2024: Domino Containers - The Next Step. News from the Domino Container commu...
2024: Domino Containers - The Next Step. News from the Domino Container commu...2024: Domino Containers - The Next Step. News from the Domino Container commu...
2024: Domino Containers - The Next Step. News from the Domino Container commu...
 
Handwritten Text Recognition for manuscripts and early printed texts
Handwritten Text Recognition for manuscripts and early printed textsHandwritten Text Recognition for manuscripts and early printed texts
Handwritten Text Recognition for manuscripts and early printed texts
 
Powerful Google developer tools for immediate impact! (2023-24 C)
Powerful Google developer tools for immediate impact! (2023-24 C)Powerful Google developer tools for immediate impact! (2023-24 C)
Powerful Google developer tools for immediate impact! (2023-24 C)
 

50267584 celldoctor

  • 1. BSS Network Doctor Formulas DN98619493 © Nokia Networks Oy 1 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 2. BSS Network Doctor Formulas The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia Networks' customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia Networks. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia Networks and the customer. However, Nokia Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Networks will, if necessary, explain issues which may not be covered by the document. Nokia Networks' liability for any errors in the document is limited to the documentary correction of errors. Nokia Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it. This document and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright © Nokia Networks Oy 2001. All rights reserved. 2 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 3. Contents Contents 3 List of tables 5 List of figures 6 1 About this manual 27 1.1 What you need to know first 27 1.2 Where to find more 28 1.3 Typographic conventions 28 1.3.1 Text styles 28 1.4 Terms and concepts 29 1.4.1 Abbreviations 29 1.4.2 Terms 31 2 BSS counter formulas 33 2.1 Additional GPRS channels (ach) 33 2.2 Multislot (msl) 35 2.3 TBF (tbf) 38 2.4 RLC (rlc) 42 2.5 Frame relay (frl) 46 2.6 Random access (rach) 47 2.7 SDCCH drop failures (sd) 49 2.7.1 SDCCH drop counters 50 2.7.2 Problems with the SDCCH drop counters 52 2.8 SDCCH drop ratio (sdr) 53 2.9 Setup success ratio (cssr) 54 2.10 TCH drop failures 55 2.10.1 TCH drop call counters 55 2.10.2 Drop call ratio 58 2.10.3 Drop-out ratio 58 2.10.4 Problems with the drop call counters 59 2.11 Drop call failures (dcf) 59 2.12 TCH drop call % (dcr) 60 2.13 Handover (ho) 71 2.14 Handover failure % (hfr) 83 2.15 Handover success % (hsr) 108 2.16 Handover failures (hof) 113 2.17 Interference (itf) 117 2.18 Congestion (cngt) 118 2.19 Queuing (que) 120 2.20 Blocking (blck) 123 2.21 Traffic (trf) 133 2.22 Traffic directions 160 2.22.1 Mobile originated calls (moc) 160 2.22.2 Mobile terminated calls (mtc) 162 2.23 Paging (pgn) 164 2.24 Short message service (sms) 166 DN98619493 © Nokia Networks Oy 3 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 4. BSS Network Doctor Formulas 2.25 Directed retry (dr) 168 2.26 Availability (ava) 170 2.27 Unavailability (uav) 174 2.28 Location updates (lu) 177 2.29 LU success % (lsr) 177 2.30 Emergency call (ec) 178 2.31 Emergency call success % (ecs) 178 2.32 Call re-establishment (re) 179 2.33 Call re-establishment success % (res) 179 2.34 Quality 179 2.34.1 Downlink quality (dlq) 179 2.34.2 Uplink quality (ulq) 180 2.35 Downlink and uplink level 182 2.35.1 Downlink level (dll) 182 2.35.2 Uplink level (ull) 182 2.36 Power (pwr) 182 2.37 Level (lev) 183 2.38 Distance (dis) 184 2.39 Link balance, power, level (lb) 184 2.40 Call success (csf) 187 2.41 Configuration (cnf) 202 3 Missing Counters 203 3.1 XX1 203 3.2 XX2 203 3.3 XX3 203 3.4 XX4 204 Index 205 4 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 5. List of tables Table 1. Text styles in this document 29 Table 2. Abbreviations 29 Table 3. Terms used in this document 31 Table 4. SDCCH Drop Counters 51 Table 5. TCH drop call counters 56 DN98619493 © Nokia Networks Oy 5 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 6. BSS Network Doctor Formulas List of figures Figure 1. Additional GPRS channel use, S9PS (ach_1) 34 Figure 2. Average additional GPRS channel hold time, S9PS (ach_2) 34 Figure 3. Additional GPRS channels seized, S9PS (ach_3) 34 Figure 4. Total additional GPRS channel hold time, S9PS (ach_4) 34 Figure 5. Distribution of UL multislot requests, S9PS (msl_1) 35 Figure 6. Distribution of DL multislot requests, S9PS (msl_2) 35 Figure 7. Distribution of UL multislot allocations, S9PS (msl_3) 35 Figure 8. Distribution of DL multislot allocations, S9PS (msl_4) 36 Figure 9. UL multislot allocations, S9PS (msl_9) 36 Figure 10. DL multislot allocations, S9PS (msl_10) 36 Figure 11. Average number of allocated timeslots, UL S9PS (msl_11) 36 Figure 12. Average number of allocated timeslots, DL S9PS (msl_13) 37 Figure 13. Average number of requested UL timeslots, S9PS (msl_13) 37 Figure 14. Average number of requested DL timeslots, S9PS (msl_14) 37 Figure 15. UL multislot allocation %, S9PS (msl_15) 37 Figure 16. DL multislot allocation %, S9PS (msl_16) 38 Figure 17. UL multislot requests, S9PS (msl_17) 38 Figure 18. DL multislot requests, S9PS (msl_18) 38 Figure 19. Average number of LLC blocks per UL TBF, S9PS (tbf_3) 39 Figure 20. Average number of LLC blocks per DL TBF, S9PS (tbf_4) 39 Figure 21. Average UL TBF duration, S9PS (tbf_5) 39 Figure 22. Average UL TBF duration, S9PS (tbf_5a) 39 Figure 23. Average DL TBF duration, S9PS (tbf_6a) 40 Figure 24. Average UL TBF duration, unack mode, S9PS (tbf_7) 40 Figure 25. Average DL TBF duration, unack mode, S9PS (tbf_8) 40 Figure 26. UL mlslot allocation blocking, S9PS (tbf_15) 40 Figure 27. DL mlslot allocation blocking, S9PS 41 Figure 28. Normally released UL TBF ratio, S9PS (tbf_25) 41 Figure 29. Normally released DL TBF ratio, S9PS (tbf_26) 41 6 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 7. Figure 30. UL TBF reallocation failure ratio, S9PS (tbf_29) 42 Figure 31. DL TBF reallocation failure ratio, S9PS (tbf_30) 42 Figure 32. UL TBF reallocation attempts, S9PS (tbf_31) 42 Figure 33. DL TBF reallocation attempts, S9PS (tbf_32) 42 Figure 34. Ack.CS1 RLC blocks UL, S9PS (rlc_1) 43 Figure 35. Ack.CS1 RLC blocks DL, S9PS (rlc_2) 43 Figure 36. Ack. CS1 RLC DL Block error rate, S9PS (rlc_3a) 43 Figure 37. Unack. CS1 RLC UL block error rate, S9PS (rlc_4a) 43 Figure 38. Ack. CS1 RLC UL block error rate, S9PS (rlc_5a) 43 Figure 39. UL CS1 RLC data share, S9PS (rlc_6) 44 Figure 40. UL CS2 RLC data share, S9PS 44 Figure 41. DL CS1 RLC data share, S9PS (rlc_8) 44 Figure 42. DL CS2 RLC data share, S9PS (rlc_9) 44 Figure 43. UL CS1 RLC block error rate, S9PS (rlc_10) 45 Figure 44. UL CS2 RLC block error rate, S9PS (rlc_11) 45 Figure 45. DL CS1 RLC block error rate, S9PS (rlc_12) 45 Figure 46. DL CS2 RLC block error rate, S9PS (rlc_13) 45 Figure 47. UL RLC blocks, S9PS (rlc_14) 46 Figure 48. DL RLC blocks, S9PS (rlc_15) 46 Figure 49. Bytes in discarded sent frames, S9PS (frl_5) 46 Figure 50. Bytes in discarded received frames, S9PS (frl_6) 46 Figure 51. Average RACH slot, S1 (rach_1) 47 Figure 52. Peak RACH load, average, S1 (rach_2) 47 Figure 53. Peak RACH load %, S1 (rach_3) 47 Figure 54. Average RACH load %, S1 (rach_4) 48 Figure 55. Average RACH busy, S1 (rach_5) 48 Figure 56. RACH rejected due to illegal establishment, S5 (rach_6) 48 Figure 57. Total RACH rejection ratio, S7 (rach_7) 49 Figure 58. Ghosts detected on SDCCH and other failures, S1 (sd_1) 49 Figure 59. Ghosts detected on SDCCH and other failures, S1 (sd_1a) 50 Figure 60. Ghosts detected on SDCCH and other failures, S1 (sd_1b) 50 DN98619493 © Nokia Networks Oy 7 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 8. BSS Network Doctor Formulas Figure 61. SDCCH Drop %, S3 (sdr_1a) 53 Figure 62. SDCCH Drop %, abis fail excluded, S3 (sdr_2) 54 Figure 63. Illegal establishment cause %, (sdr_3b) 54 Figure 64. SDCCH, TCH Setup Success %, S4 (cssr_2) 55 Figure 65. TCH drop calls in HO, S2 (dcf_2) 59 Figure 66. TCH drop calls in BSC outgoing HO, S3 (dcf_3) 59 Figure 67. TCH drop calls in intra-cell HO, S3 (dcf_4) 60 Figure 68. TCH drop calls in intra BSC HO, S3 (dcf_6) 60 Figure 69. Drop calls in BSC incoming HO, S3 (dcf_7) 60 Figure 70. TCH drop call %, area, real, after re-establishment S3 (dcr_3f) 61 Figure 71. TCH drop call %, area, real, before re-establishment, S3 (dcr_3g) 62 Figure 72. TCH drop call %, area, real, after re-establishment, S7 (dcr_3h) 62 Figure 73. TCH drop call %, area, real, before re-establishment, S3 (dcr_3i) 63 Figure 74. TCH drop call %, area, real, after re-establishment, S7 (dcr_3j) 65 Figure 75. TCH drop-out %, BTS level, before call re-establishment, S3 (dcr_4c) 65 Figure 76. TCH drop-out %, BTS level, before call re-establishment, S3 (dcr_4d) 66 Figure 77. TCH drop-out %, BTS level, before call re-establishment, S7 (dcr_4e) 66 Figure 78. TCH drop-out %, BTS level, before call re-establishment, S7 (dcr_4f) 67 Figure 79. TCH drop call (dropped conversation) %, BSC level, S4 (dcr_5) 68 Figure 80. TCH dropped conversation %, area, re-establishment considered, S7 (dcr_5b) 69 Figure 81. TCH drop call %, after TCH assignment, without re-establishment, area level, S7 (dcr_8) 69 Figure 82. TCH drop call %, after TCH assignment, with re-establishment, area level, S7 (dcr_8b) 69 Figure 83. Drops per erlang , before re-establishment, S4 (dcr_10) 70 Figure 84. Drops per erlang , after re-establishment, S4 (dcr_10a) 70 Figure 85. Drops per erlang , after re-establishment, S7 (dcr_10b) 71 Figure 86. Return from super TRXs to regular TRX, S4 (ho_1) 71 Figure 87. HO attempts from regular TRXs to super, S4 (ho_2) 71 Figure 88. HO attempts from super to regular, S4 (ho_3) 71 Figure 89. Share of HO attempts from super to regular due to DL Qual, S4 (ho_4) 72 8 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 9. Figure 90. Share of HO attempts from super to regular due to DL interference, S4 (ho_5) 72 Figure 91. Share of HO attempts from super to regular due to UL interference, S4 (ho_6) 72 Figure 92. Share of HO attempts from super to regular due to bad C/I, S4 (ho_7) 73 Figure 93. MSC incoming HO attempts, (ho_8) 73 Figure 94. MSC outgoing HO attempts, (ho_9) 73 Figure 95. BSC incoming HO attempts, (ho_10) 73 Figure 96. BSC outgoing HO attempts, (ho_11) 73 Figure 97. Intra-cell HO attempts, S2 (ho_12a) 74 Figure 98. HO attempts, , outgoing and intra-cell S4, (ho_13) 74 Figure 99. HO attempts S3, (ho_13a) 74 Figure 100. HO attempts, outgoing and intra-cell, S5, (ho_13c) 74 Figure 101. HO attempts, outgoing and intra-cell, S6, (ho_13d) 75 Figure 102. HO attempts , outgoing and intra-cell S3, (ho_13e) 75 Figure 103. HO attempts , outgoing and intra-cell S9, (ho_13f) 75 Figure 104. TCH requests for HO (ho_14a) 76 Figure 105. TCH requests for HO (ho_14b) 76 Figure 106. TCH seizures for HO (ho_15) 76 Figure 107. TCH-TCH HO attempts (ho_16) 76 Figure 108. SDCCH-TCH HO attempts (ho_17) 77 Figure 109. SDCCH-SDCCH HO attempts (ho_18) 77 Figure 110. TCH-TCH HO successes (ho_19) 77 Figure 111. SDCCH-TCH HO successes (ho_20) 77 Figure 112. SDCCH-SDCCH HO successes (ho_21) 78 Figure 113. MSC controlled HO attempts (ho_22) 78 Figure 114. BSC controlled HO attempts (ho_23) 78 Figure 115. Intra-cell HO attempts (ho_24) 78 Figure 116. MSC controlled HO successes (ho_25) 79 Figure 117. BSC controlled HO successes (ho_26) 79 Figure 118. Intra-cell HO successes (ho_27) 79 Figure 119. MSC incoming HO successes (ho_28) 79 DN98619493 © Nokia Networks Oy 9 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 10. BSS Network Doctor Formulas Figure 120. MSC outgoing HO successes (ho_29) 79 Figure 121. BSC incoming HO successes (ho_30) 80 Figure 122. BSC outgoing HO successes (ho_31) 80 Figure 123. Incoming HO success (ho_32) 80 Figure 124. Outgoing HO successes (ho_33) 80 Figure 125. Outgoing HO attempts (ho_34) 80 Figure 126. Incoming HO attempts (ho_35) 81 Figure 127. Outgoing SDCCH-SDCCH HO attempts (ho_36) 81 Figure 128. Incoming SDCCH-SDCCH HO attempts (ho_37) 81 Figure 129. Outgoing SDCCH-TCH HO attempts (ho_38) 81 Figure 130. Incoming SDCCH-TCH HO attempts (ho_39) 81 Figure 131. Outgoing TCH-TCH HO attempts (ho_40) 82 Figure 132. Incoming TCH-TCH HO attempts (ho_41) 82 Figure 133. Outgoing SDCCH-SDCCH HO success (ho_42) 82 Figure 134. Incoming SDCCH-SDCCH HO success (ho_43) 82 Figure 135. Outgoing SDCCH-TCH HO success (ho_44) 82 Figure 136. Incoming SDCCH-TCH HO success (ho_45) 83 Figure 137. Outgoing TCH-TCH HO success (ho_46) 83 Figure 138. Incoming TCH-TCH HO success (ho_47) 83 Figure 139. Total HO failure %, S1 (hfr_1) 84 Figure 140. Total HO failure %, S1 (hfr_2) 85 Figure 141. Intra-cell HO failure share, S1 (hfr_3a) 85 Figure 142. Intra-cell HO failure share, S1 (hfr_3b) 86 Figure 143. Intra-cell HO failure share, S1 (hfr_3c) 86 Figure 144. Intra-cell HO failure share, S1 (hfr_3d) 86 Figure 145. Incoming MSC ctrl HO failure %, S1 (hfr_4) 87 Figure 146. Incoming MSC ctrl HO failure share, S1 (hfr_4a) 87 Figure 147. Incoming MSC ctrl HO failure share, S1 (hfr_4b) 88 Figure 148. Incoming MSC ctrl HO failure share, S1 (hfr_4c) 88 Figure 149. Incoming MSC ctrl HO failure share, S1 (hfr_4d) 88 Figure 150. Outgoing MSC ctrl HO failure share %, S1 (hfr_5a) 89 10 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 11. Figure 151. Outgoing MSC ctrl HO failure share %, S1 (hfr_5b) 89 Figure 152. Outgoing MSC ctrl HO failure share %, S1 (hfr_5c) 90 Figure 153. Outgoing MSC ctrl HO failure share %, S1 (hfr_5d) 90 Figure 154. Incoming BSC ctrl HO failure %, S1 (hfr_6) 90 Figure 155. Incoming BSC ctrl HO failure share %, S1 (hfr_6a) 91 Figure 156. Incoming BSC ctrl HO failure %, S1 (hfr_6b 91 Figure 157. Incoming BSC ctrl HO failure share %, S1 (hfr_6c) 92 Figure 158. Incoming BSC ctrl HO failure %, S1 (hfr_6d) 92 Figure 159. Outgoing BSC ctrl HO failure share, S1 (hfr_7) 92 Figure 160. Outgoing BSC ctrl HO failure share, S1 (hfr_7a) 93 Figure 161. Outgoing BSC ctrl HO failure share, S1 (hfr_7b) 93 Figure 162. Outgoing BSC ctrl HO failure share, S1 (hfr_7c) 94 Figure 163. Outgoing BSC ctrl HO failure share, S1 (hfr_7d) 94 Figure 164. Internal inter HO failure %, S4 (hfr_8) 94 Figure 165. Internal intra HO failure %, S4 (hfr_9) 94 Figure 166. External source HO failure %, S4 (hfr_10) 95 Figure 167. HO failure % from super to regular, S4 (hfr_12) 95 Figure 168. HO failure % from regular to super, S4 (hfr_13) 95 Figure 169. Share of HO failures from regular to super due to return, S4 (hfr_14) 95 Figure 170. Share of HO failures from regular to super due to MS lost, S4 (hfr_15) 96 Figure 171. Share of HO failures from regular to super due to another cause, S4 (hfr_16) 96 Figure 172. Share of HO failures from super to regular due to return, S4 (hfr_17) 96 Figure 173. Share of HO failures from super to regular due to MS lost, S4 (hfr_18) 97 Figure 174. Share of HO failures from super to regular due to another cause, S4 (hfr_19) 97 Figure 175. SDCCH-SDCCH HO failure %, S2 (hfr_20) 97 Figure 176. SDCCH-TCH HO failure %, S2 (hfr_21) 98 Figure 177. TCH-TCH HO failure %, S2 (hfr_22) 98 Figure 178. SDCCH-SDCCH incoming HO failure %, S2 (hfr_23) 98 Figure 179. SDCCH-SDCCH outgoing HO failure ratio, S2 (hfr_24) 99 Figure 180. SDCCH-TCH incoming HO failure %, S2 (hfr_25) 99 DN98619493 © Nokia Networks Oy 11 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 12. BSS Network Doctor Formulas Figure 181. SDCCH-TCH outgoing HO failure %, S2 (hfr_26) 99 Figure 182. TCH-TCH incoming HO failure %, S2 (hfr_27) 99 Figure 183. TCH-TCH outgoing HO failure %, S2 (hfr_28) 100 Figure 184. MSC ctrl HO failure %, blocking (hfr_29) 100 Figure 185. MSC ctrl HO failure %, not allowed (hfr_30) 100 Figure 186. MSC ctrl HO failure %, return to old (hfr_31) 100 Figure 187. MSC ctrl HO failure %, call clear (hfr_32) 101 Figure 188. MSC ctrl HO failure %, end HO (hfr_33) 101 Figure 189. MSC ctrl HO failure %, end HO BSS (hfr_34) 101 Figure 190. MSC ctrl HO failure %, wrong A interface (hfr_35) 101 Figure 191. MSC ctrl HO failure %, adjacent cell error (hfr_36) 102 Figure 192. BSC ctrl HO failure %, blocking (hfr_37) 102 Figure 193. BSC ctrl HO failure %, not allowed (hfr_38) 102 Figure 194. BSC ctrl HO failure %, return to old (hfr_39) 102 Figure 195. BSC ctrl HO failure %, call clear (hfr_40) 103 Figure 196. BSC ctrl HO failure %, end HO (hfr_41) 103 Figure 197. BSC ctrl HO failure %, end HO BSS (hfr_42) 103 Figure 198. BSC ctrl HO failure %, wrong A interface (hfr_43) 103 Figure 199. BSC ctrl HO drop call %, (hfr_44) 104 Figure 200. Intra-cell HO failure %, cell_fail_lack (hfr_45) 104 Figure 201. Intra-cell HO failure %, not allowed (hfr_46) 104 Figure 202. Intra-cell HO failure %, return to old (hfr_47) 104 Figure 203. Intra-cell HO failure %, call clear (hfr_48) 105 Figure 204. Intra-cell HO failure %, MS lost (hfr_49) 105 Figure 205. Intra-cell HO failure %, BSS problem (hfr_50) 105 Figure 206. Intra-cell HO failure %, drop call (hfr_51) 105 Figure 207. HO failure % to adjacent cell (hfr_52) 106 Figure 208. HO failure % from adjacent cell (hfr_53) 106 Figure 209. HO failure %, blocking excluded (hfr_54a) 106 Figure 210. HO failure % due to radio interface blocking (hfr_55) 107 Figure 211. Intra-cell HO failure %, wrong A interface (hfr_56) 107 12 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 13. Figure 212. Intra-cell HO failure % (hfr_57) 107 Figure 213. HO failures to target cell, S6 (hfr_58) 108 Figure 214. HO failures from target cell, S6 (hfr_59) 108 Figure 215. MSC controlled outgoing SDCCH-SDCCH HO success %, S1 (hsr_1) 108 Figure 216. MSC controlled outgoing SDCCH-TCH HO success %, S1 (hsr_2) 109 Figure 217. MSC controlled outgoing TCH-TCH HO success %, S1 (hsr_3) 109 Figure 218. BSC controlled outgoing SDCCH-SDCCH HO success %, S1 (hsr_4) 109 Figure 219. BSC controlled outgoing SDCCH-TCH HO success %, S1 (hsr_5) 109 Figure 220. BSC controlled outgoing TCH-TCH HO success %, S1 (hsr_6) 109 Figure 221. Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_7) 110 Figure 222. Intra-cell SDCCH-TCH HO success %, S1 (hsr_8) 110 Figure 223. Intra-cell TCH-TCH HO success %, S1 (hsr_9) 110 Figure 224. MSC controlled incoming SDCCH-SDCCH HO success %, S1 (hsr_10) 110 Figure 225. MSC controlled incoming SDCCH-TCH HO success %, S1 (hsr_11) 110 Figure 226. MSC controlled incoming TCH-TCH HO success %, S1 (hsr_12) 111 Figure 227. BSC controlled incoming SDCCH-SDCCH HO success %, S1 (hsr_13) 111 Figure 228. BSC controlled incoming SDCCH-TCH HO success %, S1 (hsr_14) 111 Figure 229. BSC controlled incoming TCH-TCH HO success %, S1 (hsr_15) 111 Figure 230. BSC controlled incoming HO success %, S1 (hsr_16) 111 Figure 231. MSC controlled incoming HO success %, S1 (hsr_17) 112 Figure 232. Incoming HO success %, S1 (hsr_18) 112 Figure 233. Outgoing HO success %, S1 (hsr_19) 112 Figure 234. Intra-cell SDCCH-SDCCH HO success %, S1 (hsr_20) 112 Figure 235. Intra-cell SDCCH-TCH HO success %, S1 (hsr_21) 113 Figure 236. Intra-cell TCH-TCH HO success %, S1 (hsr_22) 113 Figure 237. Outgoing HO failures due to lack of resources (hof_1) 113 Figure 238. Incoming HO failures due to lack of resources (hof_2) 113 Figure 239. TCH HO failures when return to old channel was successful (hof_3) 114 Figure 240. SDCCH HO failures when return to old channel was successful DN98619493 © Nokia Networks Oy 13 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 14. BSS Network Doctor Formulas (hof_4) 114 Figure 241. MSC incoming HO failures (hof_5) 114 Figure 242. MSC outgoing HO failures (hof_6) 114 Figure 243. MSC outgoing HO failures (hof_6a) 115 Figure 244. BSC incoming HO failures (hof_7) 115 Figure 245. BSC incoming HO failures (hof_7a) 115 Figure 246. BSC outgoing HO failures (hof_8) 115 Figure 247. BSC outgoing HO failures (hof_8a) 115 Figure 248. Intra-cell HO failures (hof_9a) 116 Figure 249. Failed outgoing HO, return to old (hof_10) 116 Figure 250. Outgoing HO failures (hof_12) 116 Figure 251. Intra-cell HO failure, return to old channel (hof_13) 116 Figure 252. Intra-cell HO failure, drop call (hof_14) 116 Figure 253. Incoming HO failures (hof_15) 117 Figure 254. UL interference, BTS level, S1 (itf_1) 117 Figure 255. Idle TSL percentage of time in band X, TRX level, IUO, S4 (itf_2) 118 Figure 256. UL interference from IUO, TRX level, S4 (itf_3) 118 Figure 257. UL interference from Power Control, TRX level, S6 (itf_4) 118 Figure 258. TCH congestion time, S1 (cngt_1) 119 Figure 259. SDCCH congestion time, S1 (cngt_2) 119 Figure 260. FTCH time congestion % (cngt_3a) 119 Figure 261. FTCH time congestion % (cngt_3a) 119 Figure 262. HTCH time congestion % (cngt_4a) 120 Figure 263. HTCH time congestion % (cngt_4a) 120 Figure 264. Queued, served TCH call requests % (que_1) 120 Figure 265. Queued, served TCH HO requests % (que_2) 121 Figure 266. Queued, served TCH HO requests %, (que_2a) 121 Figure 267. Successful queued TCH requests (que_3) 121 Figure 268. Successful non-queued TCH requests (que_4) 121 Figure 269. Successful queued TCH HO requests (que_5) 122 Figure 270. Successful non-queued TCH HO requests (que_6) 122 14 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 15. Figure 271. Non-queued, served TCH call requests % (que_7) 122 Figure 272. Non-queued, served TCH HO requests % (que_8) 122 Figure 273. Non-queued, served TCH HO requests %, (que_8a) 123 Figure 274. TCH raw blocking, S1 (blck_1) 123 Figure 275. SDCCH blocking %, S1 (blck_5) 123 Figure 276. SDCCH real blocking %, S1 (blck_5a) 124 Figure 277. TCH raw blocking % on super TRXs, S4 (blck_6) 124 Figure 278. TCH raw blocking % on regular TRXs, S4 (blck_7) 124 Figure 279. TCH call blocking, before DR, S2 (blck_8) 125 Figure 280. TCH call blocking %, DR compensated, S2 (blck_8b) 126 Figure 281. TCH call blocking %, DR and DAC compensated, EFR excluded, S5 (blck_8d) 127 Figure 282. Blocked calls, S5 (blck_9b) 127 Figure 283. Blocked calls , S5 (blck_9c) 128 Figure 284. Blocked TCH HOs, S2 (blck_10a) 128 Figure 285. Blocked TCH HOs, S5 (blck_10b) 128 Figure 286. TCH HO blocking, S2 (blck_11a) 129 Figure 287. TCH HO blocking without Q, S2 (blck_11b) 129 Figure 288. TCH HO blocking, S5 (blck_11c) 129 Figure 289. Blocked incoming and internal HO, S2 (blck_12) 130 Figure 290. Blocked incoming and internal HO, S2 (blck_12a) 130 Figure 291. AG blocking, S1 (blck_13) 130 Figure 292. FCS blocking, S5 (blck_14) 130 Figure 293. Blocked SDCCH seizure attempts, S5 (blck_15) 131 Figure 294. HO blocking % (blck_16a) 131 Figure 295. Handover blocking %, (blck_16b) 131 Figure 296. Blocked FACCH call setup TCH requests, (blck_18) 132 Figure 297. Handover blocking to target cell, (blck_19) 132 Figure 298. Handover blocking from target cell, (blck_20) 132 Figure 299. NACK ratio of p-immediate assignment, S9PS (blck_21) 132 Figure 300. Territory upgrade rejection %, S9PS (blck_22) 133 DN98619493 © Nokia Networks Oy 15 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 16. BSS Network Doctor Formulas Figure 301. TCH traffic sum, S1 (trf_1) 133 Figure 302. TCH traffic sum, S1 (trf_1a) 134 Figure 303. Average call length, S1 (trf_2d) 134 Figure 304. TCH usage, S1 (trf_3) 135 Figure 305. FTCH usage, S5 (trf_3b) 135 Figure 306. Average SDCCH holding time, S1 (trf_4) 135 Figure 307. Average FTCH holding time, S1 (trf_5) 136 Figure 308. TCH seizures for new call (call bids), S1 (trf_6) 136 Figure 309. SDCCH usage %, S1 (trf_7b) 136 Figure 310. TCH traffic absorption on super, S4 (trf_8) 137 Figure 311. TCH traffic absorption on super, S4 (trf_8a) 137 Figure 312. Average cell TCH traffic from IUO, S4 (trf_9) 137 Figure 313. Cell TCH traffic from IUO, S4 (trf_9a) 138 Figure 314. Super TRX TCH traffic, S4 (trf_10) 138 Figure 315. Sum of super TRX TCH traffic, S4 (trf_10a) 138 Figure 316. Average SDCCH traffic, erlang, S2 (trf_11) 138 Figure 317. Average SDCCH traffic, erlang, S2 (trf_11a) 139 Figure 318. Average TCH traffic, erlang, S2 (trf_12) 139 Figure 319. Average TCH traffic, erlang, S2 (trf_12a) 139 Figure 320. Average TCH traffic, erlang, S2 (trf_12b) 139 Figure 321. Handover/call %, (trf_13b) 140 Figure 322. Intra-cell handover/call %, (trf_13c) 140 Figure 323. Handover/call %, (trf_13d) 141 Figure 324. IUO, average TCH seizure length on super TRXs, S4 (trf_14b) 141 Figure 325. IUO, average TCH seizure length on regular TRXs, S4 (trf_15b) 141 Figure 326. Average TRX traffic, IUO, S4 (trf_16) 142 Figure 327. Average TRX TCH seizure length, IUO, S4 (trf_17a) 142 Figure 328. Average TRX TCH seizure length, IUO, S4 (trf_17b) 142 Figure 329. TCH requests for a new call, S3 (trf_18) 142 Figure 330. TCH requests for a new call, S3 (trf_18a) 143 Figure 331. Peak busy TCH (trf_19) 143 16 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 17. Figure 332. Average unit load (trf_20) 143 Figure 333. Call time difference between TRXs, S4 (trf_21) 144 Figure 334. Call time difference between TRXs, S4 (trf_21a) 144 Figure 335. Number of mobiles located in a cell, BSC, (trf_23a) 145 Figure 336. Total TCH seizure time (call time in seconds) (trf_24b) 145 Figure 337. Total TCH seizure time (call time in hours), (trf_24c) 145 Figure 338. SDCCH true seizures (trf_25) 146 Figure 339. SDCCH true seizures, S7 (trf_25a) 146 Figure 340. SDCCH true seizures for call and SS (trf_26) 146 Figure 341. SDCCH true seizures for call, SMS, SS (trf_27) 146 Figure 342. Peak busy SDCCH seizures (trf_28) 147 Figure 343. IUO layer usage % (trf_29) 147 Figure 344. SDCCH seizures (trf_30) 147 Figure 345. Call time (minutes) from p_nbsc_res_avail (trf_32) 147 Figure 346. Call time from p_nbsc_rx_qual (trf_32a) 148 Figure 347. Call time from p_nbsc_rx_statistics (trf_32b) 148 Figure 348. SDCCH HO seizure % out of HO seizure attempts (trf_33) 148 Figure 349. SDCCH assignment % out of HO seizure attempts (trf_34) 148 Figure 350. TCH HO seizure % out of TCH HO seizure request (trf_35) 149 Figure 351. TCH norm seizure % out of TCH call request (trf_36) 149 Figure 352. TCH normal seizure % out of TCH call requests, (trf_36a) 149 Figure 353. TCH FCS seizure % out of TCH FCS attempts (trf_37) 149 Figure 354. TCH FCS seizure % out of congested SDCCH seizure attempts (trf_38) 150 Figure 355. TCH seizures for new calls (trf_39) 150 Figure 356. TCH seizures for new calls (trf_39a) 150 Figure 357. HTCH usage, S5 (trf_40) 151 Figure 358. MOC rate, S6 (trf_41) 151 Figure 359. MTC rate, S6 (trf_42) 151 Figure 360. TCH single band subscriber holding time, S6 (trf_43) 151 Figure 361. TCH dual band subscriber holding time, S6 (trf_44) 152 DN98619493 © Nokia Networks Oy 17 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 18. BSS Network Doctor Formulas Figure 362. TCH data call seizures (trf_46) 152 Figure 363. Share of single band traffic (trf_47) 152 Figure 364. Share of dual band traffic (trf_48) 152 Figure 365. Call retries due to A interface pool mismatch (trf_49) 153 Figure 366. HO retries due to A interface pool mismatch (trf_50) 153 Figure 367. TCH single band subscribers’ share of holding time, S6 (trf_51) 153 Figure 368. TCH dual band subscribers’ share of holding time, S6 (trf_52) 154 Figure 369. Calls started as FACCH call setup (trf_53) 154 Figure 370. SDCCH seizures (trf_54) 154 Figure 371. TCH normal seizures (trf_55) 154 Figure 372. Total FTCH seizure time (trf_56) 154 Figure 373. Total HTCH seizure time (trf_57) 155 Figure 374. Average TCH hold time for HSCSD, S7 (trf_58) 155 Figure 375. Total HSCSD TCH seizure time (call time, hours),(trf_61) 155 Figure 376. Average upgrade pending time for HSCSD, (trf_62) 155 Figure 377. Average upgrade pending time due to congestion, (trf_63) 156 Figure 378. Total reporting time of ph1 and ph2 mobiles, (trf_64) 156 Figure 379. Total TCH seizures, (trf_65) 156 Figure 380. Net UL data traffic per timeslot, S9PS (trf_69a) 156 Figure 381. Net DL data traffic per timeslot, S9PS (trf_70a) 157 Figure 382. Average UL throughput per allocated timeslot, S9PS (trf_72b) 157 Figure 383. Average DL throughput per allocated timeslot, S9PS (trf_73b) 158 Figure 384. Total RLC data, S9PS (trf_74a) 158 Figure 385. GPRS territory UL utilisation, S9PS (trf_76b) 158 Figure 386. GPRS territory DL utilisation, S9PS (trf_77a) 159 Figure 387. UL GPRS timeslot usage, S9PS (trf_78a) 159 Figure 388. DL GPRS timeslot usage, S9PS (trf_79a) 160 Figure 389. SDCCH seizures for MO calls, S2 (moc_1) 160 Figure 390. Successful MO speech calls, S3 (moc_2) 161 Figure 391. Successful MO data calls, S3 (moc_3) 161 Figure 392. MO call success ratio, S6 (moc_4) 161 18 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 19. Figure 393. MO speech call attempts, S3 (moc_5) 162 Figure 394. MO call bids, S2 (moc_6) 162 Figure 395. SDCCH seizures for MT calls, S2 (mtc_1) 162 Figure 396. Successful MT speech calls (mtc_2) 162 Figure 397. Successful MT data calls, S3 (mtc_3) 163 Figure 398. MT call success ratio, S6 (mtc_4) 163 Figure 399. MT speech call attempts (mtc_5) 163 Figure 400. MT call attempts, S2 (mtc_6) 163 Figure 401. Number of paging messages sent, S2 (pgn_1) 164 Figure 402. Paging buffer size average, S1 (pgn_2) 164 Figure 403. Average paging buffer space, S1 (pgn_3) 165 Figure 404. Paging success ratio, S1 (pgn_4) 165 Figure 405. Average paging buffer Aif occpancy, S7 (pgn_5) 165 Figure 406. Average paging buffer Gb occpancy, S7PS (pgn_6) 165 Figure 407. Average DRX buffer occpancy due to paging, S7 (pgn_7) 166 Figure 408. Average DRX buffer occpancy due to DRX AG, S7 (pgn_8) 166 Figure 409. Average DRX buffer occpancy due to nonDRX AG, S7 (pgn_9) 166 Figure 410. SMS establishment failure % (sms_1) 166 Figure 411. SMS TCH establishment failure % (sms_2) 167 Figure 412. SMS SDCCH establishment failure % (sms_3) 167 Figure 413. SMS establishment attempts (sms_4) 167 Figure 414. SMS SDCCH establishment attempts (sms_5) 167 Figure 415. SMS TCH establishment attempts (sms_6) 168 Figure 416. DR, outgoing attempts, S3 (dr_1) 168 Figure 417. DR attempts, S3 (dr_1a) 168 Figure 418. DR, incoming attempts, S3 (dr_2) 168 Figure 419. DR, outgoing success to another cell, S3 (dr_3) 168 Figure 420. DR, incoming success from another cell, S3 (dr_4) 169 Figure 421. DR, intra-cell success, S3 (dr_5) 169 Figure 422. % of new calls successfully handed over to another cell by DR, S3 (dr_6) 169 DN98619493 © Nokia Networks Oy 19 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 20. BSS Network Doctor Formulas Figure 423. DR, outgoing to another cell, failed, S3 (dr_7) 169 Figure 424. DR, intra-cell failed, S3 (dr_8) 170 Figure 425. TCH availability %, S4 (ava_1a) 170 Figure 426. TCH availability %, S9 (ava_1c) 170 Figure 427. TCH availability %, S9 (ava_1d) 171 Figure 428. Average available TCH, S1 (ava_2) 171 Figure 429. Average available SDCCH, S1 (ava_3) 171 Figure 430. SDCCH availability %, S4 (ava_4) 172 Figure 431. Average available FTCH in area, S1 (ava_5) 172 Figure 432. DMR availability %, S6 (ava_6) 172 Figure 433. DN2 availability %, S6 (ava_7) 172 Figure 434. TRU availability %, S6 (ava_8) 173 Figure 435. Average available TCH in BTS, S9 (ava_15) 173 Figure 436. Average available PDTCH in BTS, S9PS (ava_16) 173 Figure 437. Average available dedicated GPRS channels, S9PS (ava_17) 173 Figure 438. Average defined TCH, S1 (ava_18) 174 Figure 439. Average unavailable TSL per BTS, S1 (uav_1) 174 Figure 440. Average unavailable TSL per BTS, S1 (uav_1a) 174 Figure 441. Average unavailable TSL per BTS, S1 (uav_1b) 174 Figure 442. Total outage time, (uav_2) 175 Figure 443. Number of outages, (uav_3) 175 Figure 444. Share of unavailability due to user (uav_4) 175 Figure 445. Share of unavailability due to internal reasons (uav_5) 176 Figure 446. Share of unavailability due to external reasons (uav_6) 176 Figure 447. TRX unavailability time due to user (uav_7) 176 Figure 448. TRX unavailability time due to internal reasons (uav_8) 176 Figure 449. TRX unavailability time due to external reasons (uav_9) 177 Figure 450. Number of LU attempts, S1 (lu_1) 177 Figure 451. Average of LU attempts per hour, S1 (lu_2) 177 Figure 452. Number of LU attempts, S1 (lu_3) 177 Figure 453. LU success %, S6 (lsr_2) 178 20 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 21. Figure 454. Emergency calls, S6 (ec_1) 178 Figure 455. Emergency call success %, S6 (ecs_1) 178 Figure 456. Call re-establishment attempts, S6 (re_1) 179 Figure 457. Call re-establishments, S6 (re_2) 179 Figure 458. Call re-establishment success %, S6 (res_1) 179 Figure 459. DL BER, S1 (dlq_1) 180 Figure 460. DL cumulative quality % in class X, S1 (dlq_2) 180 Figure 461. DL cumulative quality % in class X, S1 (dlq_2a) 180 Figure 462. UL BER, S1 (ulq_1) 181 Figure 463. UL cumulative quality % in class X, S1 (ulq_2) 181 Figure 464. UL cumulative quality % in class X, S1 (ulq_2a) 181 Figure 465. Share % per range, S4 (dll_1) 182 Figure 466. Share % per range, S4 (ull_1) 182 Figure 467. Average MS power, S2 (pwr_1) 182 Figure 468. Average MS power, S2 (pwr_1b) 183 Figure 469. Average BS power, S2 (pwr_2) 183 Figure 470. Average DL signal strength, S2 (lev_1) 183 Figure 471. Average DL signal strength, S2 (lev_1a) 183 Figure 472. Average UL signal strength, S2 (lev_2) 184 Figure 473. Average UL signal strength, S2 (lev_2a) 184 Figure 474. Average MS-BS distance (dis_1) 184 Figure 475. Link balance, S1 (lb_1) 185 Figure 476. Share in acceptance range, S4 (lb_2) 185 Figure 477. Share in normal, S4 (lb_3) 185 Figure 478. Share in MS limited, S4 (lb_4) 185 Figure 479. Share in BS limited, S4 (lb_5) 186 Figure 480. Share in maximum power, S4 (lb_6) 186 Figure 481. Average MS power attenuation, S2 (lb_7) 186 Figure 482. Average MS power, S2 (lb_7b) 186 Figure 483. Average UL signal strength, S2 (lb_9) 187 Figure 484. Average DL signal strength, S2 (lb_10) 187 DN98619493 © Nokia Networks Oy 21 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 22. BSS Network Doctor Formulas Figure 485. Average MS power attenuation, S2 (lb_11) 187 Figure 486. Average BS power attenuation, S2 (lb_12) 187 Figure 487. SDCCH access probability, before FCS (csf_1) 188 Figure 488. SDCCH access probability (csf_1a) 188 Figure 489. SDCCH success ratio (csf_2a) 189 Figure 490. SDCCH success ratio, (csf_2c) 189 Figure 491. SDCCH success ratio, BTS, S6 (csf_2g) 190 Figure 492. SDCCH success ratio, BTS, (csf_2i) 191 Figure 493. SDCCH success ratio, area, (csf_2j) 192 Figure 494. SDCCH success ratio, BTS, (csf_2k) 193 Figure 495. TCH access probability without DR (csf_3a) 193 Figure 496. TCH access probability without DR and Q (csf_3b) 194 Figure 497. TCH access probability without Q (csf_3c) 194 Figure 498. TCH access probability, real (csf_3d) 194 Figure 499. TCH access probability without DR, (csf_3i) 195 Figure 500. TCH access probability without DR and Q, (csf_3j) 195 Figure 501. TCH access probability, real, (csf_3k) 196 Figure 502. TCH access probability, real (csf_3l) 196 Figure 503. TCH access probability without DR and Q, (csf_3m) 197 Figure 504. TCH success ratio, area, before call re-establisment (csf_4o) 197 Figure 505. TCH success ratio, area, after call re-establishment, S6 (csf_4p) 198 Figure 506. TCH success ratio, BTS, before call re-establisment (csf_4q) 199 Figure 507. TCH success ratio, BTS, after call re-establishment (csf_4r) 199 Figure 508. TCH success ratio, BTS, after call re-establishment, (csf_4t) 200 Figure 509. TCH success ratio, area, before call re-establishment, S7(csf_4u) 200 Figure 510. TCH success ratio, area, after call re-establishment, S7 (csf_4v) 201 Figure 511. TCH success ratio, BTS, after call re-establishment, (csf_4x) 201 Figure 512. TCH success ratio, BTS, before call re-establishment, (csf_4y) 202 Figure 513. Reuse pattern (cnf_1) 202 22 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 23. Summary of changes In this Functionality Note (FN T1712) As a result of the changes made between BSS Network Doctor software versions 12.0 and 12.1 the following changes have been made into this document: New formulas • TBF (tbf) - UL TBF reallocation failure ratio, S9PS (tbf_29) - DL TBF reallocation failure ratio, S9PS (tbf_30) - UL TBF reallocation attempts, S9PS (tbf_31) - DL TBF reallocation attempts, S9PS (tbf_32) • RLC (rlc) - UL RLC blocks, S9PS (rlc_14) - DL RLC blocks, S9PS (rlc_15) • Frame Relay (frl), all formulas new - Bytes in discarded sent frames, S9PS (frl_5) - Bytes in discarded received frames, S9PS (frl_6) • Random access (rach) - Total RACH rejection ratio, S7 (rach_7) • SDCCH drop ratio (sdr) - SDCCH drop %, S3 (sdr_1a) - Illegal establishment cause %, (sdr_3b) • TCH drop call (dcr) - TCH drop call %, after TCH assignment, w RE, area level, S7 (dcr_8b) • Blocking (blck) - NACK ratio of p-immediate assignment, S9PS (blck_21) - Territory upgrade rejection %, S9PS (blck_22) • Traffic (trf) - GPRS territory UL utilisation, S9PS (trf_76b) - UL GPRS timeslot usage, S9PS (trf_78a) - DL GPRS timeslot usage, S9PS (trf_79a) • Call success (csf) DN98619493 © Nokia Networks Oy 23 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 24. BSS Network Doctor Formulas - SDCCH success ratio, (csf_2c) Removed formulas • sdr_1 replaced with sdr_1a • sdr_3 replaced with sdr_3b • dcr_8a replaced with sdr_8b • trf_76a replaced with trf_76b • csf_2b replaced with csf_2c In the previous Functionality Note (FN T1538) As a result of the changes made between BSS Network Doctor software versions 11.2 and 12.0 the following changes have been made into this document: New formulas • Additional GPRS channels (ach), all formulas new • Multislot (msl), all formulas new • TBF (tbf), all formulas new • RLC (rlc), all formulas new • Availability (ava) - ava_1c, TCH availability %, S9 - ava_1d, TCH availability %, S9 - ava_15, Average available TCH in BTS, S9 - ava_16, Average available PDTCH in BTS, S9PS - ava_17, Average available dedicated GPRS channels, S9PS - ava_18, Average defined TCH, S1 • Call success (csf) - csf_2j, SDCCH success ratio, area, S9 - csf_2k, SDCCH success ratio, BTS, S9 • Congestion (cngt) - cngt_3a, FTCH time congestion % - cngt_4a, HTCH time congestion % • Handover (ho) - ho_13f, HO attempts, outgoing and intra-cell, S9 24 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 25. Paging (pgn) - pgn_5, Average paging buffer Aif occupancy, S7 - pgn_6, Average paging buffer Gb occupancy, S7PS - pgn_7, Average DRX buffer occupancy due to paging, S7 - pgn_8, Average DRX buffer occupancy due to DRX AG, S7 - pgn_9, Average DRX buffer occupancy due to nonDRX AG, S7 • Traffic (trf) - trf_61, Total HSCSD TCH seizure time (call time, hours) - trf_62, Average upgrade pending time for HSCSD - trf_63, Average upgrade pending time due to congestion - trf_64, Total reporting time of ph1 and ph2 mobile - trf_65, Total TCH seizures - trf_69a, Net UL data traffic per timeslot, S9PS - trf_70a, Net DL data traffic per timeslot, S9PS - trf_72b, Average UL throughput per allocated timeslot, S9PS - trf_73b, Average DL throughput per allocated timeslot, S9PS - trf_74a, Total RLC data, S9PS - trf_76a, GPRS territory UL utilisation, S9PS - trf_77a, GPRS territory DL utilisation, S9PS Removed formulas • blck_8c replaced with blck_8d • csf_2a replaced with csf_2b • csf_2h replaced with csf_2j • csf_4s replaced with csf_4v • dcr_5a DN98619493 © Nokia Networks Oy 25 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 26. BSS Network Doctor Formulas 26 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 27. About this manual 1 About this manual This document defines the formulas used to calculating the Key Performance Indicators based on the Nokia NMS/2000 database. This document contains also formulas which are not used in any actual reports of the NMS/2000 post-processing tools. You can see the formulas used in post- processing from the actual reports of the tools. Note This document serves as a reference to the available formulas and does not include information on whether the formula is in use or not. The information contained in this document relates to BSS Network Doctor software version 12.x, Nokia NMS release T12 and to release S9 of the Nokia BSC software. This document should not be used with any other versions of the Nokia NMS/2000 or Nokia BSC software. This document is intended for the network operators of the Nokia NMS/2000. This chapter covers the following topics: • What you need to know first • Where to find more • Typographic conventions • Concepts and terminology 1.1 What you need to know first This document assumes that you are familiar with the following areas: DN98619493 © Nokia Networks Oy 27 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 28. BSS Network Doctor Formulas • The concepts of the Nokia NMS and GSM networks in general • A text processing utility, such as vi or dtpad. These text processors are used for editing certain configuration files. 1.2 Where to find more When you perform the user’s tasks described in this document, you may need to refer to other documentation for further information. Below is a list of manuals that you will find useful, as well as a brief description of the manual’s contents. BSS Network Doctor documentation • BSS Network Doctor, Feature Overview, DN00308743, for a brief overview on the application • BSS Network Doctor, System Administrator’s Guide, DN98619369, for system administrator’s tasks related to running Network Doctor • BSS Network Doctor, User’s Guide, DN98614186, for a detailed description on utilising the Network Doctor reports Other Nokia documents • Database Description for BSC Measurements, DN98619454, for a description of the structure of performance management (PM) tables in the NMS/2000 database and the records, including counters, in each table. • Call Related DX Causes in BSC, Functional Description, DN9814277, for an explanation of phases and for a list of causes in TCH and SDCCH observations to find details for dropping calls.#1 • DX Cause Coding Mapping, DN9813878, for an explanation to the relationship between DX cause codes and PM counters and for the analysis of TCH and SDCCH observations.#2 1.3 Typographic conventions The following tables present the typographic conventions which have been used in this manual to describe different actions and restrictions. 1.3.1 Text styles The following table presents the typefaces and fonts and their indications. 28 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 29. About this manual Table 1. Text styles in this document Style Explanation Initial Upper-case Application names Lettering Italiced text Emphasis State, status or mode Courier File and directory names Names of database tables Parameters User names System output User input UPPER-CASE Keys on the keyboard (ALT, TAB, CTRL etc.) LETTERING Bold text User interface components Initial Upper-case Referenced documents Lettering in Italics Referenced sections and chapters within a document <bracketed text> Variable user input 1.4 Terms and concepts The lists below presents the terms and abbreviations used in this document. 1.4.1 Abbreviations Table 2. Abbreviations Abbreviation Explanation AG Access Grant BCCH Broadcast Control Channel BCF Base Control Function BER Bit Error Ratio BSC Base Station Controller DN98619493 © Nokia Networks Oy 29 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 30. BSS Network Doctor Formulas Table 2. Abbreviations (Continued) Abbreviation Explanation BSS Base Station Subsystem BTS Base Transceiver Station CI Cell Identity DL Downlink DR Directed Retry FCS Frame Check Sequence HO Handover 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 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 TRX Transceiver TSL Timeslot UL Uplink 30 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 31. About this manual 1.4.2 Terms The lists below presents the abbreviations and terms used in this document. Table 3. Terms used in this document Term Explanation AGCH A downlink control channel that is used to carry a response to a mobile channel allocation request. The AGCH assigns the mobile to operate on a specific TDMA timeslot. Bit Error Ratio The ratio of the number of the bit errors to the total number 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 all mobile stations located in the cell coverage area. BTS group A predefined set of BTSs which can be created and handled for definition by Network Doctor. Cell Identity (CI) A number which identifies a cell to the networks within a location area (LA). Clear Code Code that describes why the call set-up or the call itself has been disconnected. Day The counting of data per day is based on the period_start_time field in the measurement tables. This field always tells the starting hour of the measurement period. Under one day there are hours from 00 to 23. Directed Retry A procedure used in a call set-up phase for assigning a mobile station to a traffic channel of a cell other than the serving cell when the traffic is congested. Frame Check Sequence Extra characters added to a frame for the purposes of error control. The FCS is used in HDCL, Frame Relay, and other data link layer protocols. Key Performance Indicator The performance of the network is calculated from the NMS/2000 based on the Network Element counter information. Sometimes the plain counter as such describes an important performance aspect (number of calls, for example) of the network but sometimes a formula of counters is needed (e.g. drop call ratio). DN98619493 © Nokia Networks Oy 31 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 32. BSS Network Doctor Formulas Table 3. Terms used in this document (Continued) Term Explanation Maintenance Region Each object in the NMS/2000 database belongs to one and only one Maintenance Region (MR). Mobile Terminated Call A call in which the called subscriber used a mobile telephone. NMS/2000 A product of Nokia Telecommunications for the operation and maintenance of cellular networks. SQL*Plus An interactive program for accessing the database. Stand-alone Dedicated Control A control channel (CCH) used for roaming, Channel (SDCCH) 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 station and primarily intended for conversation. Trunk Reservation A stochastic algorithm employed in a channel allocation from a cell. For any other terms, refer to Glossary, DN9763965. 32 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 33. BSS counter formulas 2 BSS counter formulas This chapter lists all BSS Network Doctor formulas. The more commonly used ones are described in further detail concerning their use or known problems with them, for example. In connection with the name of a formula there is also a reference to the BSC release (S1 to S6) since when the counters of the formula have been available. The use of formulas backwards, S4 formulas with S3 for example, gives either no results because the measurement is not available, or false results because some counters, which are new in S4, will be filled with value -1 by the OMC for S3 BSCs. Note When running the reports with newer counters, be careful especially when you have two BSC software releases running in the network simultaneously. The simplest way to avoid problems is to start to use new counters of a new BSC release only when the new software release is used in the entire network under the NMS/2000. 2.1 Additional GPRS channels (ach) Additional GPRS channel use, S9PS (ach_1) Use: Example: if value equals to 1 then in average 1 additional timeslot has been used for GPRS. If the situation continues it indicates need for extending the default or dedicated territory. total hold time of all additional GPRS ch. seizures (sec) ----------------------------------------------------------- = period duration sum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100 --------------------------------------- sum(period_duration*60) Counters from table(s): p_nbsc_res_avail DN98619493 © Nokia Networks Oy 33 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 34. BSS Network Doctor Formulas 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_avail Unit: 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 (territory downgrade). 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: If the value is high, more default area is needed. sum(AVE_ADD_GPRS_CH_HOLD_TIME_SUM)/100 Counters from table(s): p_nbsc_res_avail Unit: sec Figure 4. Total additional GPRS channel hold time, S9PS (ach_4) 34 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 35. BSS counter formulas 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_UL 100 * -------------------------------------------------------------------------- % 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 components of 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_DL 100 * -------------------------------------------------------------------------- % 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. Counters from table(s): p_nbsc_packet_control_unit 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_UL 100 * -------------------------------------------------------- % 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. Counters from table(s): p_nbsc_packet_control_unit Figure 7. Distribution of UL multislot allocations, S9PS (msl_3) DN98619493 © Nokia Networks Oy 35 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 36. BSS Network Doctor Formulas Distribution of DL multislot allocations, S9PS (msl_4) Use: Indicates the share of a multislot request type to all multislot requests. alloc_X_TSL_DL 100 * ------------------------------------------------------ % 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. Counters from table(s): p_nbsc_packet_control_unit Figure 8. Distribution of DL multislot allocations, S9PS (msl_4) 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) Counters from table(s): p_nbsc_packet_control_unit Figure 9. 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) Counters from table(s): p_nbsc_packet_control_unit Figure 10. 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) Counters from table(s): p_nbsc_packet_control_unit Figure 11. Average number of allocated timeslots, UL S9PS (msl_11) 36 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 37. BSS counter formulas 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) Counters from table(s): p_nbsc_packet_control_unit Figure 12. Average number of allocated timeslots, DL S9PS (msl_13) Average number of requested UL timeslots, S9PS (msl_13) 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) Counters from table(s): p_nbsc_packet_control_unit Figure 13. Average number of requested UL timeslots, S9PS (msl_13) Average number of requested DL timeslots, S9PS (msl_14) 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) Counters from table(s): p_nbsc_packet_control_unit Figure 14. Average number of requested DL timeslots, S9PS (msl_14) UL multislot allocation %, S9PS (msl_15) 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) 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) Counters from table(s): p_nbsc_packet_control_unit Figure 15. UL multislot allocation %, S9PS (msl_15) DN98619493 © Nokia Networks Oy 37 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 38. BSS Network Doctor Formulas DL multislot allocation %, S9PS (msl_16) 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) 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) Counters from table(s): p_nbsc_packet_control_unit Figure 16. DL multislot allocation %, S9PS (msl_16) UL multislot requests, S9PS (msl_17) Use: Total number of multislot requests in UL. sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL +req_4_TSL_UL+ req_5_8_TSL_UL) Counters from table(s): p_nbsc_packet_control_unit Figure 17. UL multislot requests, S9PS (msl_17) DL multislot requests, S9PS (msl_18) Use: Total number of multislot requests in DL. sum(req_1_TSL_DL+req_2_TSL_DL+req_3_TSL_DL +req_4_TSL_DL+ req_5_8_TSL_DL) Counters from table(s): p_nbsc_packet_control_unit Figure 18. 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. sum(Ave_UL_LLC_per_TBF_sum) ---------------------------- sum(Ave_UL_LLC_per_TBF_den) 38 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 39. BSS counter formulas Counters from table(s): p_nbsc_packet_control_unit Figure 19. 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) Counters from table(s): p_nbsc_packet_control_unit Unit: seconds Figure 20. Average number of LLC blocks per DL TBF, S9PS (tbf_4) Average UL TBF duration, S9PS (tbf_5) sum(ave_dur_ul_tbf_sum) ------------------------ sum(ave_dur_ul_tbf_den) Counters from table(s): p_nbsc_packet_control_unit Unit: seconds Figure 21. 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_unit Unit: seconds Figure 22. Average UL TBF duration, S9PS (tbf_5a) Average DL TBF duration, S9PS (tbf_6a) Use: Counted from the normally released TBFs. DN98619493 © Nokia Networks Oy 39 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 40. BSS Network Doctor Formulas Known problems: Contains part of TBF establishment delays. sum(ave_dur_dl_tbf_sum)/100 --------------------------- sum(ave_dur_dl_tbf_den) Counters from table(s): p_nbsc_packet_control_unit Unit: seconds Figure 23. 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) Counters from table(s): p_nbsc_packet_control_unit Unit: seconds Figure 24. 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) Counters from table(s): p_nbsc_packet_control_unit Unit: seconds Figure 25. Average DL TBF duration, unack mode, S9PS (tbf_8) UL mlslot allocation blocking, S9PS (tbf_15) Known problems: Over 100 % values are met. sum(NO_RADIO_RES_AVA_UL_TBF) 100 * ------------------------------------------------------------------------- % sum(req_1_TSL_UL+req_2_TSL_UL+req_3_TSL_UL +req_4_TSL_UL+ req_5_8_TSL_UL) Counters from table(s): p_nbsc_packet_control_unit Figure 26. UL mlslot allocation blocking, S9PS (tbf_15) 40 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 41. BSS counter formulas DL mlslot allocation blocking, S9PS (tbf_16) Known problems: Values of over 100% are met. sum(NO_RADIO_RES_AVA_DL_TBF) 100 * ------------------------------------------------------------------------- % sum(req_1_TSL_DL+req_2_TSL_DL+req_3_TSL_DL +req_4_TSL_DL+ req_5_8_TSL_DL) Counters from table(s): p_nbsc_packet_control_unit Figure 27. DL mlslot allocation blocking, S9PS Normally released UL TBF ratio, S9PS (tbf_25) Experiences on use: Cases when TBF is not released normally: 1) PCU receives a Channel Request, allocates resources and sends assignment but receives no blocks. These cases can occur if MS sends more than one Channel Request before it receives an Immediate Assignment. 2) Ghost Accesses. normally released UL TBFs 100*---------------------------- % = established UL TBFs sum(AVE_DUR_UL_TBF_DEN) 100*--------------------------- % sum(NBR_OF_UL_TBF) Counters from table(s): p_nbsc_packet_control_unit Figure 28. Normally released UL TBF ratio, S9PS (tbf_25) Normally released DL TBF ratio, S9PS (tbf_26) Use: DL TBF establishment is not completed normally, for example, if a response from a MS is not received. If the TBF is already running and the MS is not heard from, the counter DL_TBF_REL_DUE_NO_RESP_MS is triggered. normally released DL TBFs 100*---------------------------- % = established DL TBFs sum(AVE_DUR_DL_TBF_DEN) 100*--------------------------- sum(NBR_OF_DL_TBF) Counters from table(s): p_nbsc_packet_control_unit Figure 29. Normally released DL TBF ratio, S9PS (tbf_26) DN98619493 © Nokia Networks Oy 41 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 42. BSS Network Doctor Formulas UL TBF reallocation failure ratio, S9PS (tbf_29) sum(UL_TBF_REALLOC_FAILS) 100 * ----------------------------------------------- % sum(UL_TBF_RE_ALLOCATIONS+ UL_TBF_REALLOC_FAILS) Counters from table(s): p_nbsc_packet_control_unit Figure 30. UL TBF reallocation failure ratio, S9PS (tbf_29) DL TBF reallocation failure ratio, S9PS (tbf_30) sum(DL_TBF_REALLOC_FAILS) 100 * ----------------------------------------------- % sum(DL_TBF_RE_ALLOCATIONS+ DL_TBF_REALLOC_FAILS) Counters from table(s): p_nbsc_packet_control_unit Figure 31. DL TBF reallocation failure ratio, S9PS (tbf_30) UL TBF reallocation attempts, S9PS (tbf_31) sum(UL_TBF_RE_ALLOCATIONS+ UL_TBF_REALLOC_FAILS) Counters from table(s): p_nbsc_packet_control_unit Figure 32. UL TBF reallocation attempts, S9PS (tbf_31) DL TBF reallocation attempts, S9PS (tbf_32) sum(DL_TBF_RE_ALLOCATIONS+ DL_TBF_REALLOC_FAILS) Counters from table(s): p_nbsc_packet_control_unit Figure 33. DL TBF reallocation attempts, S9PS (tbf_32) 2.4 RLC (rlc) Ack.CS1 RLC blocks UL, S9PS (rlc_1) Use: Number of UL blocks in RLC ack mode using CS1. Retransmission is not included. 42 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 43. BSS counter formulas sum(RLC_DATA_BLOCKS_UL_CS1 - RLC_DATA_BLOCKS_UL_UNACK) Figure 34. Ack.CS1 RLC blocks UL, S9PS (rlc_1) Ack.CS1 RLC blocks DL, S9PS (rlc_2) Use: Number of DL blocks in RLC ack mode using CS1. Retransmission is not included. sum(RLC_DATA_BLOCKS_DL_CS1 - RLC_DATA_BLOCKS_DL_UNACK) Figure 35. Ack.CS1 RLC blocks DL, S9PS (rlc_2) Ack. CS1 RLC DL block error rate, S9PS (rlc_3a) Use: Number of DL blocks in RLC ack mode using CS1. sum(BAD_FRAME_IND_UL_CS1 - BAD_FRAME_IND_UL_UNACK ) 100 * ------------------------------------------------ % sum(RLC_DATA_BLOCKS_DL_CS1 - RLC_DATA_BLOCKS_DL_UNACK + BAD_FRAME_IND_UL_CS1 - BAD_FRAME_IND_UL_UNACK ) Figure 36. Ack. CS1 RLC DL Block error rate, S9PS (rlc_3a) Unack. CS1 RLC UL block error rate, S9PS (rlc_4a) sum(BAD_FRAME_IND_UL_UNACK) 100 * ---------------------------------------------------- % sum(RLC_DATA_BLOCKS_UL_UNACK+ BAD_FRAME_IND_UL_UNACK) Figure 37. Unack. CS1 RLC UL block error rate, S9PS (rlc_4a) Ack. CS1 RLC UL block error rate, S9PS (rlc_5a) sum(BAD_FRAME_IND_UL_CS2) 100 * ------------------------------------------------- % sum(RLC_DATA_BLOCKS_UL_CS2+ BAD_FRAME_IND_UL_CS2) Figure 38. Ack. CS1 RLC UL block error rate, S9PS (rlc_5a) UL CS1 RLC data share, S9PS (rlc_6) sum(RLC_data_blocks_UL_CS1*22 100 * ---------------------------------------------------------- % (sum(RLC_data_blocks_UL_CS1*22+RLC_data_blocks_UL_CS2*32 DN98619493 © Nokia Networks Oy 43 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 44. BSS Network Doctor Formulas + RLC_data_blocks_DL_CS1*22+RLC_data_blocks_DL_CS2*32) Counters from table(s): p_nbsc_packet_control_unit Unit: % Figure 39. UL CS1 RLC data share, S9PS (rlc_6) UL CS2 RLC data share, S9PS (rlc_7) sum(RLC_data_blocks_UL_CS2*22 100 * ---------------------------------------------------------- % (sum(RLC_data_blocks_UL_CS1*22+RLC_data_blocks_UL_CS2*32 + RLC_data_blocks_DL_CS1*22+RLC_data_blocks_DL_CS2*32) Counters from table(s): p_nbsc_packet_control_unit Unit: % Figure 40. UL CS2 RLC data share, S9PS DL CS1 RLC data share, S9PS (rlc_8) sum(RLC_data_blocks_DL_CS1*22 100 * ---------------------------------------------------------- % (sum(RLC_data_blocks_UL_CS1*22+RLC_data_blocks_UL_CS2*32 + RLC_data_blocks_DL_CS1*22+RLC_data_blocks_DL_CS2*32) Counters from table(s): p_nbsc_packet_control_unit Unit: % Figure 41. DL CS1 RLC data share, S9PS (rlc_8) DL CS2 RLC data share, S9PS (rlc_9) sum(RLC_data_blocks_DL_CS2*22 100 * ---------------------------------------------------------- % (sum(RLC_data_blocks_UL_CS1*22+RLC_data_blocks_UL_CS2*32 + RLC_data_blocks_DL_CS1*22+RLC_data_blocks_DL_CS2*32) Counters from table(s): p_nbsc_packet_control_unit Unit: % Figure 42. DL CS2 RLC data share, S9PS (rlc_9) 44 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 45. BSS counter formulas UL CS1 RLC block error rate, S9PS (rlc_10) Known problems: 100% values met. 100% means that the MS has not responded to USF. The number of ignored RLC data blocks in uplink due to BSN in acknowledged mode should be subtracted, but there is no counter specifically for CS1. sum(BAD_FRAME_IND_UL_CS1) 100 * ------------------------------------------------- % sum(RLC_DATA_BLOCKS_UL_CS1+ BAD_FRAME_IND_UL_CS1) Figure 43. UL CS1 RLC block error rate, S9PS (rlc_10) UL CS2 RLC block error rate, S9PS (rlc_11) Known problems: 100% means that there can be only failing accesses. The number of ignored RLC data blocks in downlink due to BSN in acknowledged mode should be subtracted, but there is no counter specifically for CS1. sum(BAD_FRAME_IND_UL_CS2) 100 * ------------------------------------------------- % sum(RLC_DATA_BLOCKS_UL_CS2+ BAD_FRAME_IND_UL_CS2) Figure 44. UL CS2 RLC block error rate, S9PS (rlc_11) DL CS1 RLC block error rate, S9PS (rlc_12) sum(RETRA_RLC_DATA_BLOCKS_DL_CS1) 100 * ------------------------------------------------- % sum(RLC_DATA_BLOCKS_DL_CS1+ RETRA_RLC_DATA_BLOCKS_DL_CS1) Figure 45. DL CS1 RLC block error rate, S9PS (rlc_12) DL CS2 RLC block error rate, S9PS (rlc_13) sum(RETRA_RLC_DATA_BLOCKS_DL_CS2) 100 * -------------------------------------------------------- % sum(RLC_DATA_BLOCKS_DL_CS2+ RETRA_RLC_DATA_BLOCKS_DL_CS2) Figure 46. DL CS2 RLC block error rate, S9PS (rlc_13) UL RLC blocks, S9PS (rlc_14) Use: Total UL data volume as the number of RLC blocks. sum(rlc_data_blocks_ul_cs1 + rlc_data_blocks_ul_cs2 + rlc_mac_cntrl_blocks_ul + bad_frame_ind_ul_cs1 DN98619493 © Nokia Networks Oy 45 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 46. BSS Network Doctor Formulas + bad_frame_ind_ul_cs2 + bad_frame_ind_ul_unack + ignor_rlc_data_bl_ul_due_bsn) Counters from table(s): p_nbsc_packet_control_unit Figure 47. UL RLC blocks, S9PS (rlc_14) DL RLC blocks, S9PS (rlc_15) Use: Total DL data volume as the number of RLC blocks. sum(rlc_data_blocks_dl_cs1 + rlc_data_blocks_dl_cs2 + rlc_mac_cntrl_blocks_dl + retra_rlc_data_blocks_dl_cs1 + retra_rlc_data_blocks_dl_cs2) Counters from table(s): p_nbsc_packet_control_unit Figure 48. DL RLC blocks, S9PS (rlc_15) 2.5 Frame relay (frl) Bytes in discarded sent frames, S9PS (frl_5) sum(dlci_1_bytes_sent+dlci_2_bytes_sent+dlci_3_bytes_sent+dlci_4_bytes_sent +dlci_5_bytes_sent) Counters from table(s): p_nbsc_frame_relay Figure 49. Bytes in discarded sent frames, S9PS (frl_5) Bytes in discarded received frames, S9PS (frl_6) sum(DLCI_1_BYTES_REC+DLCI_2_BYTES_REC+DLCI_3_BYTES_REC+DLCI_4_BYTES_REC +DLCI_5_BYTES_REC) Counters from table(s): p_nbsc_frame_relay Figure 50. Bytes in discarded received frames, S9PS (frl_6) 46 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en
  • 47. BSS counter formulas 2.6 Random access (rach) Average RACH slot, S1 (rach_1) Use: Indicates the capacity of BTS for RACH burst handling. Normally shows a constant value because it is dependent on the BTS configuration which does not often change. avg(ave_rach_slot/res_acc_denom1) Counters from table(s): p_nbsc_res_access Figure 51. Average RACH slot, S1 (rach_1) Peak RACH load, average, S1 (rach_2) Use: Indicates the absolute peak value during a measurement period. Correlates strongly with UL interference. Experiences on use: High values may suggest that MSs have problems in accessing the BTS. High values do not mean high load on SDCCH because SDCCH is needed only if the RACH passes the detection in BTS. Known problems: The peak value does not indicate yet how many times there have been other peaks during the measurement period. Open questions: How serious the high values really are from the MS point of view? avg(peak_rach_load) Counters from table(s): p_nbsc_res_access Figure 52. Peak RACH load, average, S1 (rach_2) Peak RACH load %, S1 (rach_3) Use: This PI indicates how near to full capacity the peak use of RACH has been during the measurement period. max(peak_rach_load) 100 * ------------------------------------- % max(ave_rach_busy/res_acc_denom1) Counters from table(s): p_nbsc_res_access Figure 53. Peak RACH load %, S1 (rach_3) DN98619493 © Nokia Networks Oy 47 (206) Issue 1-1 en Nokia Proprietary and Confidential
  • 48. BSS Network Doctor Formulas Average RACH load % , S1 (rach_4) Use: This PI indicates how high the RACH load is on average. Experiences on use: If the value is to the order of tens of per cent, there probably are access problems and MS users get, more often than usual, 3 beeps when trying to start calls. The probable reason is UL interference. avg(ave_rach_busy/res_acc_denom3) 100 * -------------------------------------- % avg(ave_rach_slot/res_acc_denom1) Counters from table(s): p_nbsc_res_access Figure 54. Average RACH load %, S1 (rach_4) Average RACH busy, S1 (rach_5) Use: This PI indicates roughly the average of the used RACH slots. If the average approaches the xb2 average RACH slotxb2 (rach_1) there probably are access problems and MS users get, more often than usual, 3 beeps when trying to start calls. avg(ave_rach_busy/res_acc_denom3) Counters from table(s): p_nbsc_res_access Figure 55. Average RACH busy, S1 (rach_5) RACH rejected due to illegal establishment, S5 (rach_6) Use: Most of the rejections are ghost accesses. Note that part of the ghosts have legal establishment cause and get further to SDCCH. sum(ghost_ccch_res - rej_seiz_att_due_dist) Counters from table(s): p_nbsc_res_access Figure 56. RACH rejected due to illegal establishment, S5 (rach_6) Total RACH rejection ratio, S7 (rach_7) Use: Ratio of all RACH rejections to total nbr of channel required messages received. Note that the counter ghost_ccch_res contains both ghosts and rejections due to distance checking. The latter one is an optional feature of BSC. 48 (206) © Nokia Networks Oy DN98619493 Nokia Proprietary and Confidential Issue 1-1 en